You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this issue is similar to #104 but procob targeted sources commonly work (DB2 not "in some places"), so I'd suggest this issue be tackled first and the other one later (but possibly keep its options in mind).
The following code does pass the preparser, but the resulting code isn't valid COBOL.
EXEC SQL AT :CON DECLARE CSKEYTAB CURSOR FORSELECT TABID, STAMP FROM TABORDER BY USERIDASC END-EXEC.
EXEC SQL AT :CON OPEN CSKEYTAB END-EXEC.
*IF SQLCODE NOT=0MOVE'BAD SQLOPEN'TO ERROR-SQL
PERFORM ERROR-SQL
END-IF*
DO-FETCH.
*INITIALIZE T02-FETCHTAB
EXEC SQL AT :CON FETCH CSKEYTAB INTO:T02-ID,:T02-STAMP END-EXEC.
* SQLERRD(3) stores number of retrieved rows - with each fetch* it will be therefore incremented (if more data is there)IF SQLCODE NOT=0MOVE0TO CUR-MAX
ELSEMOVEFUNCTIONMOD (SQLERRD(3), 10) INTO CUR-MAX
IF CUR-MAX =0MOVE10TO CUR-MAX.
PERFORMVARYING TAB-IDX FROM1BY1UNTIL TAB-IDX > CUR-MAX
....
END-PERFORMIF CUR-MAX =10GO TO DO-FETCH.
EXEC SQL AT :CON CLOSE CSKEYTAB END-EXEC.
What currently happens is that the preprarser generates the reference "as it got", so the subscript is missing:
some checking in the gixsql code showed that the preparser knows about the OCCURS attribute, but I have no clue if there's something in the runtime that could handle that.
The text was updated successfully, but these errors were encountered:
this issue is similar to #104 but procob targeted sources commonly work (DB2 not "in some places"), so I'd suggest this issue be tackled first and the other one later (but possibly keep its options in mind).
The following code does pass the preparser, but the resulting code isn't valid COBOL.
Given the table
and the code
What currently happens is that the preprarser generates the reference "as it got", so the subscript is missing:
which, of course raises a compiler error on both
BY REFERENCE
just for reference - this is what procob does:
some checking in the gixsql code showed that the preparser knows about the
OCCURS
attribute, but I have no clue if there's something in the runtime that could handle that.The text was updated successfully, but these errors were encountered: