Skip to main content

Compiling a .PCO file using procobol/cblsql using the following command line in windows

cobol test.pco noobj int(%INTPATH%) COBIDY(%IDYPATH%) LISTPATH(%LISTPATH%) inticall(oracle11) P(COBSQL) cobsqltype==Oracle NOMAKESYN end-c MODE=ANSI PICX=CHARF P(CP) SY ENDP

test.lis has PCB-S-00400 error at End Program statements of cblproto.cpy program

Any idea why this error is cropping up in cblproto.cpy in test.lis file?

Note: test.pco has cblproto.cpy in a copy statement before the start of IDENTIFICATION DIVISION

Compiling a .PCO file using procobol/cblsql using the following command line in windows

cobol test.pco noobj int(%INTPATH%) COBIDY(%IDYPATH%) LISTPATH(%LISTPATH%) inticall(oracle11) P(COBSQL) cobsqltype==Oracle NOMAKESYN end-c MODE=ANSI PICX=CHARF P(CP) SY ENDP

test.lis has PCB-S-00400 error at End Program statements of cblproto.cpy program

Any idea why this error is cropping up in cblproto.cpy in test.lis file?

Note: test.pco has cblproto.cpy in a copy statement before the start of IDENTIFICATION DIVISION

Pro*COBOL doesn't appear to support multiple source programs within the same source file. It does support nested programs but not programs like cblproto.cpy which have a separate program-id and end program header. This error will occur even if you run the procob command at the command line without having COBSQL or the COBOL compiler involved.

You would have to talk to Oracle about the apparent lack of support for this type of functionality.
The Micro Focus OpenESQL precompiler does not have a problem supporting this.

Thanks

Compiling a .PCO file using procobol/cblsql using the following command line in windows

cobol test.pco noobj int(%INTPATH%) COBIDY(%IDYPATH%) LISTPATH(%LISTPATH%) inticall(oracle11) P(COBSQL) cobsqltype==Oracle NOMAKESYN end-c MODE=ANSI PICX=CHARF P(CP) SY ENDP

test.lis has PCB-S-00400 error at End Program statements of cblproto.cpy program

Any idea why this error is cropping up in cblproto.cpy in test.lis file?

Note: test.pco has cblproto.cpy in a copy statement before the start of IDENTIFICATION DIVISION

Thanks Chris for you valuable input
Terms & ConditionsAccessibility statement