Adds one byte to the record length for the printer control character. This option might be useful to programmers who use WRITE. . .ADVANCING in their source files. The first character of the record does not have to be explicitly reserved by the programmer.
Does not adjust the record length for WRITE. . .ADVANCING. The compiler uses the first character of the specified record area to place the printer control character. The application programmer must ensure that the record description allows for this additional byte.
1. With ADV=YES, the record length on the physical device is one byte larger than the record description length in the source program.
2. If the record length for the output file is not defined in the source code, COBOL ensures that the DCB parameters are appropriately set.
3. If ADV=YES is specified, and the record length for the output file has been defined in the source code, the programmer must specify the record description length as one byte larger than the source program record description. The programmer must also specify the block size in correct multiples of the larger record size.
4. If the LINAGE clause is specified in a file description (FD), the compiler treats that file as if ADV=YES has been specified.
Specifies 18 digits as the maximum precision for decimal data.
Specifies 31 digits as the maximum precision for decimal data.
When the NO option is specified, any CICS statements that are found in the source program are diagnosed and discarded.
If a COBOL source program contains CICS statements and has not been preprocessed by the CICS translator, the YES option must be specified.
The CICS compiler option can contain CICS suboptions. The CICS suboptions delimiter can be quotes or apostrophes. CICS suboptions cannot be specified as a COBOL installation default.
You can specify the CICS compiler option in any of the compiler option sources: installation defaults, compiler invocation, or PROCESS or CBL statements.
Indicates that you want full compilation, including diagnostics and object code.
Indicates that you want only a syntax check.
Specifies an error message level: W is warning; E is error; S is severe. When an error of the level specified or of a more severe level occurs, compilation stops, and only syntax checking is done for the balance of the compilation.
Note: Specifying NOCOMPILE might affect the Associated Data file by stopping compilation prematurely, resulting in loss of specific messages.
Places the generated object code in a file defined by SYSPUNCH.
Sends no object code to SYSPUNCH.
Causes the compiler to issue a severity-4 (warning) diagnostic message for MOVE statements with numeric receivers when the receiving data item has fewer integer positions than the sending data item or literal.
Does not cause the compiler to produce a severity-4 message.
The diagnostic is also issued for moves to numeric receivers from alphanumeric data names or literal senders, except when the sending field is reference modified. There is no diagnostic for COMP-5 receivers, nor for binary receivers when you specify the TRUNC(BIN) option.
Dynamically loads subprograms that are invoked through the CALL literal statement.
Performance consideration: Using DYNAM=YES eases subprogram maintenance because the application is not relink-edited if the subprogram is changed. However, individual applications with CALL literal statements can experience some performance degradation due to a longer path length.
Includes, in the calling program, the text files of subprograms called with a CALL literal statement into a single module file.
The DYNAM option has no effect on the CALL identifier statement at compile time. The CALL identifier statement always compiles to a dynamic call.
Do not specify DYNAM=YES for applications running under CICS.
Note: The second severity level used in this syntax must be equal to or higher than the first.
Specifies that errors at or above the severity level specified are flagged and written at the end of the source listing.
ID Type Return Code
I Information 0
W Warning 4
E Error 8
S Severe error 12
U Unrecoverable error 16
The optional second severity level specifies the level of syntax messages embedded in the source listing in addition to being at the end of the listing.
Indicates that no error messages are flagged.
If the messages are to be embedded, SOURCE must be specified at compile time. Embedded messages enhance productivity because they are placed after the referenced source statement.
Specification of FLAG(W|E|S) might result in the loss of entire classes of messages from the Events records in the Associated Date file. See Enterprise COBOL for z/OS Programming Guide for more information.
Indicates that the source program contains COPY or BASIS statements.
Indicates that the source program doesn’t contain COPY or BASIS statements.
Produces a listing that includes:
The assembler-language expansion of source code
Information about working storage
Suppresses this listing.
Note: The LIST and OFFSET compiler options are mutually exclusive. Setting OFFSET=YES and LIST=YES results in a nonzero return code and an error message during assembly of the customization macro.
Uses the line numbers from the source program rather than compiler-generated line numbers for error messages and procedure maps.
Uses the compiler-generated line numbers for error messages and procedure maps.
If COBOL programmers use COPY statements and NUM=YES is in effect, they must ensure that the source program line numbers and the COPY member line numbers are coordinated.
Indicates that you want a listing of the source statements in the compiler-generated output. This listing also includes any statements embedded by COPY.
Source statements do not appear in the output.
Note: The SOURCE compiler option must be in effect at compile time if you want embedded messages in the source listing.
Specify to have any SQL statements found in the source program diagnosed and discarded.
Use SQL=NO if your COBOL source programs do not contain SQL statements, or if the separate SQL preprocessor will be used to process SQL statements before invocation of the COBOL compiler.
Use to enable the DB2 coprocessor capability and to specify DB2 suboptions. You must specify the SQL option if your COBOL source program contains SQL statements and it has not been processed by the DB2 precompiler.
1. You can specify the SQL option in any of the compiler option sources: compiler invocation, PROCESS/CBL statements, or installation defaults.
2. Use either quotes or apostrophes to delimit the string of DB2 suboptions.
3. DB2 suboptions cannot be specified as part of customizing the SQL option. (DB2 suboptions are supported only when the SQL compiler option is specified as an invocation option or on a CBLor PROCESS card.) However, default DB2 options can be specified when you customize the DB2 product installation defaults.
4. The SQL=YES option conflicts with the LIB=NO option.
Generates code that checks subscripts, reference modifications, variable-length group ranges, and indexes in the source program at run time to ensure that they do not refer to storage outside the area assigned. It also verifies that a table with ALL subscripting, specified as a function argument, contains at least one occurrence in the table.
The generated code also checks that a variable-length item does not exceed its defined maximum length as a result of incorrect setting of the OCCURS DEPENDING ON object.
Performance consideration: If SSRANGE=YES at compile time, object code size is increased and there will be an increase in runtime overhead to accomplish the range checking.
No code is generated to perform subscript or index checking at run time.
If the SSRANGE option is in effect at compile time, the range-checking code is generated.
Range-checking can be inhibited at run time by specifying the Language Environment runtime option CHECK(OFF). However, the range-checking code still requires overhead and is dormant within the object code.
The range-checking code can be used optionally to aid in resolving any unexpected errors without recompilation.
Produces a cross-reference of all verb types in a source program to the line numbers where they are found. VBREF=YES also produces a summary of how many times each verb was used in the program.
Does not produce a cross-reference or verb-summary listing.
For More Options, Look into