Bug with Pro*Cobol and FETCH limits
Hi,
we think we have found a bug with Pro*Cobol and FETCH limits (Oracle Database 11g2, Windows 7 and AIX 6.1). We were able to create a very simple example that illustrates the problem:
$SET p(cobsql) CSQLT=ORACLE8 end-c endp
IDENTIFICATION DIVISION.
PROGRAM-ID. "MY".
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
DATA DIVISION.
WORKING-STORAGE SECTION.
EXEC SQL INCLUDE SQLCA END-EXEC.
01 DBNAME PIC X(20).
01 DBUSER PIC X(20).
01 DBPWD PIC X(20).
01 STMT-STRING PIC X(100).
01 FETCH-LIMIT PIC S9(5) COMP-5.
01 RESULT OCCURS 20.
10 DEPTNO PIC X(2).
10 EMPNO PIC X(4).
PROCEDURE DIVISION.
MOVE "TEST_DB" TO DBNAME
MOVE "scott" TO DBUSER
MOVE "tiger " TO DBPWD
EXEC SQL
CONNECT :DBUSER IDENTIFIED BY :DBPWD
we think we have found a bug with Pro*Cobol and FETCH limits (Oracle Database 11g2, Windows 7 and AIX 6.1). We were able to create a very simple example that illustrates the problem:
$SET p(cobsql) CSQLT=ORACLE8 end-c endp
IDENTIFICATION DIVISION.
PROGRAM-ID. "MY".
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
DATA DIVISION.
WORKING-STORAGE SECTION.
EXEC SQL INCLUDE SQLCA END-EXEC.
01 DBNAME PIC X(20).
01 DBUSER PIC X(20).
01 DBPWD PIC X(20).
01 STMT-STRING PIC X(100).
01 FETCH-LIMIT PIC S9(5) COMP-5.
01 RESULT OCCURS 20.
10 DEPTNO PIC X(2).
10 EMPNO PIC X(4).
PROCEDURE DIVISION.
MOVE "TEST_DB" TO DBNAME
MOVE "scott" TO DBUSER
MOVE "tiger " TO DBPWD
EXEC SQL
CONNECT :DBUSER IDENTIFIED BY :DBPWD
0