COBSQL Question

Hi All,

Is there any solution to use COBSQL directives with oracle pro*cobol with FREE or VARIABLE source format?

I've tried with variable sourceformat. The precompiled source (.cs9) is ok but the second phase of the compilation hang....

I'm sad to keep fixed format in Visual COBOL

Platform:Visual COBOL for eclipse with hub on linux.

Thanks.
Franck.

Parents
  • Hi Chris,

    Thanks for your answer.

    In pro*cobol 11gr2, we have now 3 formats for the source ansi/terminal/variable.

    Here's the 11gr2 doc...

    Coding Areas

    The precompiler option FORMAT, specifies the format of your source code. If you specify FORMAT=ANSI (the default), you are conforming as much as possible to the ANSI standard. In this format, columns 1 through 6 can contain an optional sequence number, and column 7 (indicator area) can indicate comments or continuation lines.

    Division headers, section headers, paragraph names, FD and 01 statements begin in columns 8 through 11 (area A). Other statements, including EXEC SQL and EXEC ORACLE statements, must be placed in area B (columns 12 through 72). These guidelines for source code format can be overridden by your compiler's rules.

    If you specify FORMAT=TERMINAL, COBOL statements can begin in column 1 (the left-most column), or column 1 can be the indicator area. This format is also subject to the rules of your compiler.

    You can specify FORMAT=VARIABLE to allow Flexible B Area Length.

    Consult your COBOL compiler documentation for your own platform to determine the actual acceptable formats for COBOL statements.

    If i use a source with $set SOURCEFORMAT(VARIABLE) set in the source itself (not in the cobol.dir file). The source generated is by pro*cobol is OK. but it failed after.

    So...

    Thanks.

Reply
  • Hi Chris,

    Thanks for your answer.

    In pro*cobol 11gr2, we have now 3 formats for the source ansi/terminal/variable.

    Here's the 11gr2 doc...

    Coding Areas

    The precompiler option FORMAT, specifies the format of your source code. If you specify FORMAT=ANSI (the default), you are conforming as much as possible to the ANSI standard. In this format, columns 1 through 6 can contain an optional sequence number, and column 7 (indicator area) can indicate comments or continuation lines.

    Division headers, section headers, paragraph names, FD and 01 statements begin in columns 8 through 11 (area A). Other statements, including EXEC SQL and EXEC ORACLE statements, must be placed in area B (columns 12 through 72). These guidelines for source code format can be overridden by your compiler's rules.

    If you specify FORMAT=TERMINAL, COBOL statements can begin in column 1 (the left-most column), or column 1 can be the indicator area. This format is also subject to the rules of your compiler.

    You can specify FORMAT=VARIABLE to allow Flexible B Area Length.

    Consult your COBOL compiler documentation for your own platform to determine the actual acceptable formats for COBOL statements.

    If i use a source with $set SOURCEFORMAT(VARIABLE) set in the source itself (not in the cobol.dir file). The source generated is by pro*cobol is OK. but it failed after.

    So...

    Thanks.

Children
No Data