Create CICS Program (CRTCICSCBL)

The Create CICS COBOL (CRTCICSCBL) command calls the CICS precompiler, which precompiles either OPM or ILE COBOL source containing CICS statements and produces a temporary source member. (At this time COBOL copybooks are not expanded in the Cobol source.) If the source program also contains Structured Query Language (SQL) commands, it optionally calls the SQL precompiler following a successful CICS precompile. The resulting precompiler output is placed into a temporary source member. Following the CICS precompilation and the optional SQL precompilation, the COBOL compiler may optionally be called to compile the program.

Note: It is possible to precompile your SQL statements first by running the CRTSQLCBL command and specifying the *NOGEN option on the OPTION parameter. This puts the SQL precompiler output in QSQLTEMP in library QTEMP. You must then run the CRTCICSCBL command specifying SRCFILE as QTEMP/QSQLTEMP; the SRCMBR name can be obtained by looking in this file for your SQL precompiled program source. The rest of the parameters on CRTCICSCBL can be entered as normal.

It is not recommended that applications be compiled in this way but, if necessary, it can be done.

Parameters

Program (PGM)

Specifies the qualified name by which the compiled program is known.

The possible library values are:

• *CURLIB: If a library is not specified, the program is created in the current library. If no current library entry exists in the library list, QGPL is used.
• library-name: Specify the name of the library where the compiled program is created.

program-name: Specify the name of the program being created that contains the CICS statements.

Note: If the program name you specify is the same name as an existing program, your new program replaces the existing one if the REPLACE parameter is specified as *YES (the default). If *MODULE is specified for the OBJTYPE parameter, the qualified name specified for this parameter is the name of the module object to be created.

Source file (SRCFILE)

Specifies the qualified name of the source file that contains the COBOL source with the EXEC CICS or EXEC SQL statements.

The possible library values are:

• *LIBL: Specifies that the library list is used to locate the source file.
• *CURLIB: Specifies that the current library for the job is used to locate the source file. If no current library entry exists in the library list, QGPL is used.
• library-name: Specify the library where the source file is located.

QLBLSRC: If a COBOL source file name is not specified, the supplied source file QLBLSRC contains the COBOL source.

source-file-name: Specify the name of the source file that contains the COBOL source. This source file should have a record length of 92 bytes. The source file can be a database file, device file, or an inline data file.

Source member (SRCMBR)

Specifies the name of the source file member that contains the COBOL source. This parameter is only specified if the source file name in the SRCFILE parameter is that of a database file.

• *PGM: Specifies that the COBOL source is in the source file member that has the same member name as that specified in the PGM parameter for the precompiler command.
• source-file-member-name: Specify the name of the source file member that contains the COBOL source.

Commitment control (COMMIT)

Specifies whether SQL statements in the compiled program are run under commitment control. Files referred to in the host language source are not affected by this parameter. Only SQL tables, views, and SQL packages referred to in SQL statements are affected.

• *CHG (change): Specifies the objects referred to in SQL COMMENT ON, CREATE, DROP, GRANT, LABEL ON, and REVOKE statements and the rows updated, deleted, and inserted are locked until the end of the unit of work (transaction). Uncommitted changes in other jobs can be seen.
• *CS (cursor stability): Specifies that objects referred to in SQL COMMENT ON, CREATE, DROP, GRANT, LABEL ON, and REVOKE statements and the rows updated, deleted, and inserted are locked until the end of the unit of work (transaction). A row that is selected, but not updated, is locked until the next row is selected. Uncommitted changes in other jobs cannot be seen.
• *ALL: Specifies that objects referred to in SQL COMMENT ON, CREATE, DROP, GRANT, LABEL ON, and REVOKE statements and the rows updated, deleted, and inserted are locked until the end of the unit of work (transaction). Uncommitted changes in other jobs cannot be seen.
• *NONE: Specifies that commitment control is not used. COMMIT and ROLLBACK statements are not allowed. Uncommitted changes in other jobs can be seen. If the SQL DROP COLLECTION statement is included in the program, *NONE must be used.

  Note: If *CHG, *CS, or *ALL is specified, DROP COLLECTION cannot be included in the application. The default for this parameter for the Start SQL (STRSQL) command is *NONE.

Compile type (OBJTYPE)

Specifies the type of object to be created.

The possible values are:

• *PGM: Specifies that the translated CICS source is passed to the CRTCBLPGM command to create an OPM COBOL program object.
• *BNDPGM: Specifies that the translated CICS source is passed to the CRTBNDCBL command to create a bound ILE COBOL program object.
• *MODULE: Specifies that the translated CICS source is passed to the CRTCBLMOD command to create an ILE COBOL module object.

Text description (TEXT)

Allows you to enter text that describes the compiled module or program and its function.

• *SRCMBRTXT: Specifies that the text is taken from the source-file member being used to create the module or program. Text for a database source member can be added or changed by using the Source Entry Utility (STRSEU) command, or by using either the Add Physical File Member (ADDPFM) or Change Physical File Member (CHGPFM) command. If the source file is an inline file or a device file, the text is blank.
• *BLANK: No text is specified.
• 'description': Specify no more than 50 characters of text, enclosed in apostrophes.

CICS Options (CICSOPT)

Specifies whether one or more of the following options are used when either the OPM or ILE COBOL source is CICS precompiled. If an option is specified more than once, or if two options conflict, the last option specified that does not conflict with the Compile type is used. If an option is not specified, then the default is used.

Source Listing Options

• *NOSRC: or *NOSOURCE: Specifies that a source listing is not produced by the CICS precompiler.
• *SRC: or *SOURCE: Specifies that a source listing is produced by the CICS precompiler, consisting of the all the source input and error messages.

String Delimiter and Literal Options

• *QUOTE: Specifies that a double quotation mark (") is used for string delimiters within CICS statements, and also nonnumeric literals and Boolean literals in the COBOL statements.
• *APOST: Specifies that an apostrophe (') is used for string delimiters within CICS statements, and also for non-numeric literal and Boolean literals in the COBOL statements.

Cross-Reference Options

• *NOVBREF or *NOXREFCICS: Specifies that the CICS precompiler does not produce a cross-reference of EXEC CICS names.
• *VBREF: or XREFCICS: Specifies that the CICS precompiler produces a cross-reference between EXEC CICS names in the program and the statement numbers in the program that refer to them.

Debug options

• *NODEBUG: The precompiler will not produce code that will be passed through to CICS to be displayed by the CICS execution diagnostic facility (EDF).
• *DEBUG: The precompiler produces code that will be passed through to CICS to be displayed by EDF.

SQL precompiler option

• *GEN: The SQL precompiler or COBOL compiler will be called after a successful CICS precompilation.

  Note: The SQL precompiler will only be called if during the CICS precompilation stage an EXEC SQL statement was found in the COBOL source code being CICS precompiled.

• *NOGEN: Job will terminate at the end of the CICS precompile.

Second level help text

• *NOSECLVL: No second level help text will be printed.
• *SECLVL: The second-level help text will be printed along with the first-level help text.

  Note: The first-level help text is printed each time an error occurs.

DBCS enablement

• *GRAPHIC: The precompiler will accept double byte data. This data can only appear in columns 7 through 72. See the CICS Application Programming Guide for restrictions and examples of the use of double byte data.

  *NOPICXGRAPHIC: DBCS-graphic data types are declared as FILLER fields. This option is only valid for ILE COBOL objects.

  *PICXGRAPHIC: Fixed-length DBCS-graphic data types are declared as fixed-length alphanumeric fields, and are accessible to the ILE COBOL source program. This option is only valid for ILE COBOL objects.

  When the *VARCHAR option is also in use, variable-length DBCS-graphic data types are declared as fixed-length group items, and are accessible to the ILE COBOL source program.

  *PICGGRAPHIC: Fixed-length DBCS-graphic data types are declared as fixed-length G-type fields, and are accessible to the ILE COBOL source program. This option is only valid for ILE COBOL objects.

  When the *VARCHAR option is also in use, variable-length DBCS-graphic data types are declared as fixed-length group items (made of a numeric field followed by G type field), and are accessible to the ILE COBOL source program.

  *NOPICGGRAPHIC: DBCS-graphic data types are declared as FILLER fields. This option is only valid for ILE COBOL objects.

SQL Options (SQLOPT)

Specifies whether one or more of the following options are used when either the OPM or ILE COBOL source is SQL precompiled. If an option is specified more than once, or if two options conflict, the last option specified that does not conflict with the Compile type is used. If an option is not specified then the default is used.

Source Listing Options

• *NOSRC: or *NOSOURCE: Specifies that a source listing is not produced by the SQL precompiler.
• *SRC: or *SOURCE: Specifies that a source listing is produced by the SQL precompiler, consisting of the source and error messages.

Cross-Reference Options

• *NOXREF: Specifies that the SQL precompiler does not produce a cross-reference of EXEC SQL names.
• *XREF: Specifies that the SQL precompiler produces a cross-reference between items in the program and the numbers of the statements in the program that refer to these items.

Program Creation Options

• *GEN: The COBOL compiler will be called after a successful SQL precompilation.
• *NOGEN: Compilation will be complete at the end of the SQL precompilation.

Decimal point options

• *JOB: The representation for the decimal point specified for the job at precompile time is used. This option is only valid for ILE COBOL objects.

  Note: If QDECFMT specifies that the value used as the decimal point is a comma, any numeric constants in lists (such as in the SELECT clause and VALUES clause) must be separated by a comma followed by a blank. For example, VALUES(1,1, 2,23, 4,1) is equivalent to VALUES(1.1,2.23,4.1) where the decimal point is the period.

  *SYSVAL: Specifies that the value used as the decimal point is from the QDECFMT system value.

  Note: If QDECFMT specifies that the value used as the decimal point is a comma, any numeric constants in lists (such as in the SELECT clause or the VALUES clause) must be separated by a comma followed by a blank. For example, VALUES(1,1, 2,23, 4,1) is equivalent to VALUES(1.1,2.23,4.1) in which the decimal point is a period.

• *PERIOD: Specifies that the value used as a decimal point is a period.
• *COMMA: Specifies that the value used as a decimal point is a comma.

  Note: Any numeric constants in lists (such as in the SELECT clause, the VALUES clause, and so on ) must be separated by a comma followed by a blank. For example, VALUES(1,1, 2,23, 4,1) is equivalent to VALUES(1.1,2.23,4.1) where the decimal point is the period.

SQL String Delimiter Options

• *QUOTESQL: Specifies that a double quotation mark (") is used for string delimiters within SQL statements.
• *APOSTSQL: Specifies that an apostrophe (') is used for the string delimiters within SQL statements.

  Note: If this option and the string delimiter option in CICSOPT are not set for the same delimiter, unexpected results may occur.

COBOL String Delimiter Options

• *QUOTE: The character used for nonnumeric literals and Boolean literals in the COBOL statements is the quote (").
• *APOST: The character used for nonnumeric literals and Boolean literals in the COBOL statements is the apostrophe (').

Naming Convention Option

• *SYS: Specifies that the IBM i naming convention will be used, ( library-name/file-name ).
• *SQL: Specifies that the SQL naming convention will be used ( collection-name.table-name ).

Second level help text

• *NOSECLVL: No second level help text will be printed.
• *SECLVL: The second-level help text will be printed along with the first-level help text.

  Note: The first-level help text is printed each time an error occurs.

COBOL options (CBLOPT)

Specifies the options to use when the object program is created. The listing may be required if a problem occurs in COBOL. Note that unpredictable results could occur when mixing CICS and COBOL file access.

Some possible values are listed below. Refer to the CICS documentation for a complete list of options that are supported.

Source Listing Options

• *NOSRC: or *NOSOURCE: Specifies that a source listing is not produced by the compiler.
• *SRC or *SOURCE: Specifies that a source listing is produced by the compiler, consisting of all the source input and error messages.

Verify Ranges

• *RANGE: At run-time, the system verifies that subscripts are within the correct ranges, but does not verify index ranges. It also checks for reference modification and compiler-generated substring operations.
• *NORANGE: Does not verify ranges at run-time.

Optimization

• *NOOPTIMIZE: The compiler performs only standard optimizations for the program.
• *OPTIMIZE: The program object created may run more efficiently and may require less storage. However, specifying *OPTIMIZE can substantially increase the time required to compile a program.

CODE product options

• *NOLSTDBG: This option determines the kind of information you see on your programmable work station when using the IBM CoOperative Development Environment product.

  The compiler does not produce a listing view, or listing-level debugging information.

• *LSTDBG: This option determines the kind of information you see on your programmable work station when using the IBM CoOperative Development Environment product.

  The compiler produces a listing view, source-level error information, and listing-level debugging information.

Data truncation

• *STDTRUNC: This option applies only to USAGE BINARY data. When *STDTRUNC is selected, USAGE BINARY data is truncated to the number of digits in the PICTURE clause of the BINARY receiving field. This option is only valid for ILE COBOL objects.
• *NOSTDTRUNC: This option applies only to USAGE BINARY data. When *NOSTDTRUNC is selected, BINARY receiving fields are truncated only at half-word, full-word, or double-word boundaries. BINARY sending fields are also handled as half-words, full-words, or double-words. Thus, the full binary content of the field is significant. Also, the DISPLAY statement will convert the entire content of a BINARY field, with no truncation. This option is only valid for ILE COBOL objects.

Cross Reference

• *NOXREF: The compiler does not produce a cross-reference listing for the COBOL source program.
• *XREF: The compiler produces a cross-reference listing for the COBOL source program.

Data Division Map

• *NOMAP: The compiler does not list the Data Division map.
• *MAP: The compiler lists the Data Division map.

Unreferenced data items

• *NOUNREF: Unreferenced data items are not included in the compiled program. This reduces the amount storage used, allowing a larger program to be compiled. You cannot look at or assign to an unreferenced data item during debugging when the *NOUNREF option is chosen. The unreferenced data items still appear in the cross-reference listings produced through the *XREF option.
• *UNREF: Unreferenced data items are included in the compiled program.

CICS Output file (OUTFILE)

Specifies the qualified name of the intermediate precompiler output.

The possible library values are:

• *LIBL: Specifies that all libraries in the user and system portions of the job's library list are to be searched.
• *CURLIB: Specifies that the current library is to be searched. If no library is specified as the current library for the job, the QGPL library is used.
• library-name: Specify the name of the library in which the intermediate precompiler output is to be placed.

source-file-name: Specify the name of the source file that is to contain the intermediate precompiler output.

QTEMP/QACYCICS: If an output source file name is not specified, the supplied source file QTEMP/QACYCICS is to contain the intermediate precompiler output.

CICS Output member (OUTMBR)

Specifies the name of the source file member that is to contain the intermediate precompiler output. If this parameter is not specified, the program name specified on the PGM parameter is used.

• *PGM: Specifies that the intermediate precompiler output has the same member name as that specified in the PGM parameter.
• source-member-name: Specify the name of the source file member to which the intermediate precompiler output should be copied.

Target release (TGTRLS)

Specifies the release level of the operating system on which you intend to use the object being created. In the examples given for the *CURRENT and *PRV values, and when specifying the target-release value, the format VxRxMx is used specify release, where Vx is the version, Rx is the release, and Mx is the modification level. For example, V5R3M0 is Version 5, Release 3, Modification 0.

Valid values for this parameter change every release.

The possible values are:

• *CURRENT: The object is to be used on the release of the operating system currently running on your system. The object can also be used on a system with any subsequent release of the operating system installed.
• *PRV: The object is to be used on the previous release with modification level 0 of the operating system. The object can also be used on a system with any subsequent release of the operating system installed.
• release-level: Specify the release level in the format VxRxMx. The object can be used on a system with the specified release or with any subsequent release of the operating system installed.

  Valid values depend on the current version, release, and modification level, and they change with each new release.

Activation group (ACTGRP)

Specifies the activation group this program is associated with when it is called. It only works when the OBJTYPE parameter is *BNDPGM and the source program does not contain any SQL statement.

• QILE: When this program is called, it is activated into the named activation group QILE. This is the default.
• *NEW: When this program is called, it is activated into a new activation group.
• *CALLER: When this program is called, it is activated into the caller's activation group.
• activation-group-name: Specify the name of the activation group to be used when this program is called.

INCLUDE file (INCFILE)

Specifies the qualified name of the source file that contains the members included in the program with any SQL INCLUDE statement.

The possible library values are:

• *LIBL: Specifies that the library list is used to locate the source file.
• *CURLIB: Specifies that the current library for the job is used to locate the source file. If no current library entry exists in the library list, QGPL is used.
• library-name: Specify the name of the library where the source file is located.
• *SRCFILE: Specifies the qualified source file you specified in the SRCFILE parameter that contains the source file members specified on any SQL INCLUDE statement.
• source-file-name: Specify the name of the source file that contains the source file members specified on any SQL INCLUDE statement. The record length of the source file you specify here must be no less than the record length of the source file you specified for the SRCFILE parameter.

Allow copy of data (ALWCPYDTA)

Specifies whether a copy of the data is allowed in a SELECT statement.

• *YES: A copy of the data can only be used, if necessary, to run a SELECT statement.
• *OPTIMIZE: The system chooses whether or not to use the data retrieved directly from the database or to use a copy of the data. The decision is based on which choice will provide the best performance.

  This value decreases the time required for the total query. Because the copy of the data must be made before returning the first row of the result table, the time to retrieve the first row may be increased.

  Note: If *CS or *ALL is specified on the COMMIT parameter, SQL run time ignores this parameter and uses current data.

• *NO: A copy of the data is not allowed. This option could return an negative SQLCODE if the clauses in the SELECT statement require a copy of the data. If the SELECT statement runs successfully, then current data was used.

Allow blocking (ALWBLK)

Specifies whether the database manager can use record blocking and the extent to which blocking can be used for read-only cursors.

*READ: Records are blocked for read-only retrieval of data for cursors when:

• *NONE is specified on the COMMIT parameter, to indicate that commitment control is not used.
• The cursor is declared with a FOR FETCH ONLY clause or there are no dynamic statements that could run a positioned UPDATE or DELETE statement for the cursor.

Specifying *READ can improve the overall performance of queries that meet the above conditions and retrieve a large number or records.

*NONE: Rows are not blocked for retrieval of data for cursors. Specifying *NONE:

• Guarantees that the data retrieved is current.
• May reduce the amount of time required to retrieve the first row of data for a query.
• Stops the database manager from retrieving a block of data rows that is not used by the program when only the first few rows of a query are retrieved before the query is closed.
• Can degrade the overall performance of a query that retrieves a large number of rows.

Delay PREPARE (DLYPRP)

Specifies whether the dynamic statement validation for a PREPARE statement is delayed until an OPEN, EXECUTE, or DESCRIBE statement is run. Delaying validation improves performance by eliminating duplicate validation.

• *NO: Dynamic statement validation is not delayed. When the dynamic statement is prepared, the access plan is validated. When the dynamic statement is used in an OPEN or EXECUTE statement, the access plan is revalidated. Because the authority or the existence of objects referred to by the dynamic statement may change, you must still check the SQLCODE or SQLSTATE after issuing the OPEN or EXECUTE statement to ensure that the dynamic statement is still valid.
• *YES: Dynamic statement validation is delayed until the dynamic statement is used in an OPEN, EXECUTE, or DESCRIBE SQL statement. When the dynamic statement is used, the validation is completed and an access plan is built. If you specify *YES on this parameter for precompiled programs, you should check the SQLCODE and SQLSTATE after running an OPEN, EXECUTE, or DESCRIBE statement to ensure that the dynamic statement is valid. If you specify *YES, performance is not improved if the INTO clause is used on the PREPARE statement or if a DESCRIBE statement uses the dynamic statement before an OPEN is issued for the statement.

Close SQL cursor (CLOSQLCSR)

Specifies when SQL cursors are implicitly closed, SQL prepared statements are implicitly discarded, and LOCK TABLE locks are released. SQL cursors are explicitly closed by issuing the CLOSE, COMMIT (without HOLD), or ROLLBACK (without HOLD) SQL statements.

• *OBJTYPE: Specifies that SQL cursors are handled according to the value defined in the *OBJTYPE parameter. If *PGM was specified then CRTCBLPGM uses *ENDPGM. If *BNDPGM was specified then CRTBNDCBL uses *ENDACTGRP.
• *ENDPGM: Specifies that SQL cursors are closed, SQL prepared statements are discarded, and LOCK TABLE locks are released when the program ends.
• *ENDSQL: Specifies that SQL cursors remain open between calls and can be fetched without running another SQL OPEN. One of the programs higher on the call stack must have run at least one SQL statement. SQL cursors are closed, SQL prepared statements discarded, and LOCK TABLE locks released when the first SQL program on the call stack ends. If *ENDSQL is specified for a program that is the first SQL program called (the first SQL program on the call stack), the program is treated as if *ENDPGM were specified.
• *ENDJOB: Specifies that SQL cursors remain open between calls and can be fetched without running another SQL OPEN. None of the programs higher on the call stack need to have run SQL statements. SQL cursors are left open, SQL prepared statements are preserved, and LOCK TABLE locks are held when the first SQL program on the call stack ends. SQL cursors are closed, SQL prepared statements are discarded, and LOCK TABLE locks are released when the job ends. If you are running distributed database and connected remotely, the connection is dropped.
• *ENDACTGRP: SQL cursors are closed and SQL prepared statements are implicitly discarded, and LOCK TABLE locks are released when the activation group ends. This option is only valid for ILE COBOL objects.
• *ENDMOD: SQL cursors are closed and SQL prepared statements are implicitly discarded when the module is exited. LOCK TABLE locks are released when the first SQL program on the call stack ends. This option is only valid for ILE COBOL objects.

CICS gen. severity level (CICSGENLVL)

Specifies a level of CICS precompiler errors. If errors occur with a severity level greater than the value specified in this parameter, either the SQL precompiler is not called (if the CICS precompiler located any SQL in the source) or the COBOL compiler is not called.

• 10: If a severity level value is not specified, the default severity level is 10.
• severity-level: Specify a number from 0 through 40. Some suggested values are listed below:
  • 10 The level value for warnings.
  • 20 The level value for general error messages.
  • 30 The level value for serious error messages.
  • 40 The level value for system detected error messages.

  Note: The value of CICSGENLVL only applies to messages generated as a result of CICS precompile errors. The specified CICSGENLVL value is not passed to the SQL precompiler or COBOL compiler.

COBOL gen. severity level (CBLGENLVL)

Specifies a level of COBOL compiler errors. If errors occur with a severity level greater than the value specified in this parameter, then the COBOL program object is not created.

• 29: If a severity level value is not specified, the default severity level is 29.
• severity-level: Specify a number from 0 through 29.

SQL gen. severity level (SQLGENLVL)

Specifies a level of SQL precompiler errors. If errors occur with a severity level greater than the value specified in the parameter, then the COBOL compiler is not called.

• 10: If no value is specified, the default severity level is 10.
• severity-level: Specify a number in the range 0 through 40. Some suggested values are listed below:
  • 10 The level value for warnings.
  • 20 The level value for general error messages.
  • 30 The level value for serious error messages.
  • 40 The level value for system detected error messages.

  Note: The value of SQLGENLVL only applies to messages generated as a result of SQL precompilation errors. The specified SQLGENLVL value is not passed to the COBOL compiler.

SAA Flagging (SAAFLAG)

Specifies whether SQL statements that do not SAA Level 2 Database standards are flagged. This parameter allows the user to flag SQL statements to verify that they conform to SAA Level 2 Database standards.

• *NOFLAG: Specifies that the precompiler will not check for SAA standards.
• *FLAG: Specifies that the precompiler will check for SAA standards.

ANS Flagging (FLAGSTD)

Specifies whether nonstandard statements are flagged. This parameter allows you to flag SQL statements to verify if they have conformed to ANSI X3.135-1-1989, ANSI X3.168-1989, ISO 9075-1989, and FIPS 127.1 standards.

• *NONE: Specifies that the precompiler will not check for ANSI standards.
• *ANS: Specifies that the precompiler checks for conformity to ANSI standards.

Flagging severity (FLAG)

Specifies the minimum severity level of messages to be printed. The possible values area:

• 0 All messages are printed.
• severity-level: Enter a one or two-digit number that specifies the minimum severity level of messages that are printed. Messages that have severity levels of the specified value or higher ar listed.

Sort sequence (SRTSEQ)

Specifies the sort sequence used when NLSSORT is associated with an alphabet-name in the ALPHABET clause. The SRTSEQ parameter is used in conjunction with the LANGID parameter to determine which system- defined or user-defined sort sequence table the program will use. The possible values are:

• *HEX: No sort sequence table will be used, and the hexadecimal values of the characters will be used to determine the sort sequence.
• *JOB: The sort sequence of the program will be resolved and associated with the program at compile time. The sort sequence table must exist in the system at compile time.
• *JOBRUN: The sort sequence of the program will be resolved and associated with the program at compile time. At compile time, the compiler will associate the sort sequence of the compile job with the program. At run time, this sort sequence will be replaced by the sort sequence associated with the job at run time.
• *LANGIDUNQ: Specifies that the sort sequence table being used must contain a unique weight for each character in the code page. The sort sequence table used will be the unique weighted table associated with the language specified in the LANGID parameter.
• *LANGIDSHR: Specifies that the sort sequence table being used can contain the same weight for multiple characters in the code page. The sort sequence table used will be the shared weighted table associated with the language specified in the LANGID parameter.
• table-name: Enter the name of the sort sequence table to be used. The table contains weights for all characters in a given code page. A weight is associated with the character that is defined at the code point. When using a sort sequence table name, the library in which the table resides can be specified. The valid values are:
  • *LIBL: The library list is searched to find the library where the sort sequence table is located.
  • *CURLIB: The current library is searched. If you have not assigned a library as the current library, QGPL is used.
  • library-name: Enter the name of the library where the sort not sequence table is found.
• Note: The valid PROCESS statement options for SRTSEQ are SRTSEQ(HEX), SRTSEQ(JOB), SRTSEQ(JOBRUN), STRSEQ(LANGIDUNQ), SRTSEQ(LANGIDSHR), SRTSEQ("table-name"), SRTSEQ("library-name/table-name"), SRTSEQ("LIBL/table-name"), and SRTSEQ("CURLIB/table-name").

Language identifier (LANGID)

Specifies the language identifier which is used in conjunction with the sort sequence. The LANGID parameter is used only when the SRTSEQ value in effect is *LANGIDUNQ or *LANGIDSHR. The possible values are:

• *JOBRUN: The language identifier of the program will be resolved at run time. When the compiled program is run, the language identifier of the job is used. This value allows a program to be compiled once and used with different language identifiers at run time.
• *JOB: The language identifier of the program will be resolved at compile time.
• language-identifier: Enter a valid 3 character language identifier.
• Note: The valid PROCESS statement options for LANGID are LANGID(JOBRUN), LANGID(JOB), and LANGID("language-identifier").

Date Format (DATFMT)

Specifies the format used when accessing date result columns. All output date fields are returned in the specified format. For input date strings, the specified value is used to determine if the date is in a valid format.

Note: An input date string that uses format *USA, *ISO, *EUR, or *JIS is always valid. If you connect to a relational database that is on a system that is not an IBM i, *USA, *ISO, *EUR, or *JIS must be used.

• *JOB: Specifies the format used for the job at precompilation. Use the Display Job (DSPJOB) command to determine the current date format for the job.
• *USA: The United States date format mm/dd/yyyy is used.
• *ISO: The International Organization for Standardization (ISO) date format yyyy-mm-dd is used.
• *EUR: The European date format dd.mm.yyyy is used.
• *JIS: The Japanese Industrial Standard date format yyyy-mm-dd is used.
• *MDY: The date format mm/dd/yy is used.
• *DMY: The date format dd/mm/yy is used.
• *YMD: The date format yy/mm/dd is used.
• *JUL: The Julian date format yy/ddd is used.

Time Format (TIMFMT)

Specifies the format used when accessing time result columns. All output time fields are returned in the specified format. For input time strings, the specified value is used to determine if the time is specified in a valid format.

Note: An input time string that uses the format *USA, *ISO, *EUR, or *JIS is always valid. If you connect to a relational database that is on a system that is not an IBM i, the time format must be *USA, *ISO, *EUR, *JIS, or *HMS with a time separator of colon or period.

• *HMS: The hh:mm:ss format is used.
• *USA: The United States time format hh:mm xx is used, where xx is AM or PM.
• *ISO: The International Organization for Standardization (ISO) time format hh.mm.ss is used.
• *EUR: The European time format hh.mm.ss is used.
• *JIS: The Japanese Industrial standard time format hh:mm:ss is used.

Time separator character (TIMSEP)

Specifies the separator used when accessing time result columns.

Note: This parameter applies only when *HMS is specified on the TIMFMT parameter.

• *JOB The time separator specified for the job at precompile time is used. Use the Display Job (DSPJOB) command to determine the current value for the job.
• ":": A colon (:) is used as the time separator.
• ".": A period (.) is used as the time separator.
• ",": A comma (,) is used as the time separator.
• " ": A blank space is used as the time separator.
• *BLANK A blank is used as the time separator.

Date separator character (DATSEP)

Specifies the separator used when accessing date result columns.

• *JOB The date separator for the job at the precompile time is used. Use the Display Job (DSPJOB) command to determine the current value for the job.
• "/": A slash (/) is used as the date separator.
• ".": A period (.) is used as the date separator.
• ",": A comma (,) is used as the date separator.
• "-": A hyphen (-) is used as the date separator.
• " ": A blank space is used as the date separator.
• *BLANK A blank is used as the time separator.

Replace (REPLACE)

Specifies whether a SQL program is created when there is an existing SQL program the same name in the same library. The value of this parameter is passed to the CRTCBLPGM command.

• *YES A CICS/SQL program is created, any existing program of the same name in the specified library is moved to QRPLOBJ. The *YES value is passed to the CRTCBLPGM command that creates the CICS/SQL program.
• *NO A CICS/SQL program is not created if a CICS/SQL program of the same name already exists in the specified library.

Default collection (DFTRDBCOL)

Specifies the name of the collection identifier to be used for unqualified names of tables, views, indexes, and SQL packages. This parameter applies only to static SQL statements.

• *NONE: The naming convention specified on the SQLOPT parameter is used.
• collection name: Specifies the name of the collection identifier to be used instead of the naming convention specified on the SQLOPT parameter.

Examples

Error messages