Creating a package on a database other than DB2 UDB for iSeries
When you create a program or an SQL package on a database other than DB2® UDB for iSeries™, and try to use SQL statements that are unique to the other database, set the GENLVL parameter on the Create SQL (CRTSQLxxx) commands to 30.
The program will be created unless a message with a severity level of greater than 30 is issued. If a message is issued with a severity level of greater than 30, the statement is probably not valid for any relational database. For example, undefined or unusable host variables or constants that are not valid generate a message severity greater than 30.
The precompiler listing should be checked for unexpected messages when running with a GENLVL greater than 10. When you are creating a package for a DB2 Universal Database™, set the GENLVL parameter to a value less than 20.
If the RDB parameter specifies a system that is not a DB2 UDB for iSeries system, then the following options should not be used on the CRTSQLxxx command:
- COMMIT(*NONE)
- OPTION(*SYS)
- DATFMT(*MDY)
- DATFMT(*DMY)
- DATFMT(*JUL)
- DATFMT(*YMD)
- DATFMT(*JOB)
- DYNUSRPRF(*OWNER)
- TIMFMT(*HMS) if TIMSEP(*BLANK) or TIMSEP(',') is specified
- SRTSEQ(*JOBRUN)
- SRTSEQ(*LANGIDUNQ)
- SRTSEQ(*LANGIDSHR)
- SRTSEQ(library-name/table-name)
When you connect to a DB2 Universal Database server, the following additional rules apply:
- The specified date and time formats must be the same format
- A value of *BLANK must be used for the TEXT parameter
- Default schemas (DFTRDBCOL) are not supported
- The CCSID of the source program from which the package is being created must not be 65535; if 65535 is used, an empty package is created.
Parent topic:
Considerations for creating an SQL package