Can a DB2 for Linux, UNIX, and Windows user specify that the NLSS sort sequence table of the DRDA job on i5/OS be used instead of the usual EBCDIC sequence?

 

The i5/OS® operating system recognizes a generic bind option. If you want to run a program from clients that support generic bind options, such as DB2® for Linux®, UNIX®, and Windows®, you can request that i5/OS use the NLSS sort sequence associated with the corresponding DRDA® server job.

This function is enabled by PTF SI00174 in V5R1. It is in the base operating system for subsequent releases.

If you choose to take advantage of this enhancement, recreate any SQL packages on DB2 Universal Database™ for which the new sort sequence option is desired by using the generic bind option SORTSEQ with a value of JOBRUN from the client system.

The bind option enables a user to specify that the NLSS sort sequence table of the DRDA job on the i5/OS operating system should be used instead of the usual EBCDIC sequence. Previously, only the default *HEX option, which causes the EBCDIC sequence to be used, has been available when connecting from unlike DRDA clients.

This feature is available from DRDA application requesters that support the DRDA generic bind function. It has undergone limited testing using DB2 Universal Database for Linux, UNIX, and Windows 6.1 FixPak 1 running on Windows as a client development platform and run environment. DB2 for Linux, UNIX and Windows supports the specification of generic bind options on two of its program preparation commands, the precompile (PREP) command and the (BIND) command. JOBRUN sort sequence can be specified on either of them as in the following examples drawn from a Windows batch file:

DB2 PREP %1.SQC BINDFILE SORTSEQ JOBRUN...
DB2 BIND %1.BND SORTSEQ JOBRUN...

On the Windows development platform, single quotation marks are used around the generic option name/value pair, but on an AIX® or UNIX platform, quotation marks should be used.

The only other valid value for the SORTSEQ option is HEX, which is the default value and is the only possible option from a non-i5/OS client before the introduction of this feature.

 

Parent topic:

User FAQs