How can unlike clients override package options such as NLSS sort sequences, system naming and separate date/time formats?
The IBM i operating system supports DRDA generic bind options.
Many environmental options are specific to a server and thus not available on the precompiling and binding commands provided from other products. DRDA provides for this shortcoming by allowing generic options to be passed on the bind request. The following is a list of the generic bind options supported by DB2®.
| Bind Option Name | Bind Option Values |
|---|---|
| CONCURRENTACCESSRESOLUTION | NO (Default), YES |
| DATEOVERIDE | ISO (Default), USA, EUR, JIS |
| EXTENDEDINDICATOR | NO (Default), YES |
| MINDIVSCALE | number-char |
| MAXSCALE | number-char |
| OS400NAMING | SQL (Default), SYSTEM |
| PATH | schema-names |
| ROUNDING | HALFEVEN (Default), CEILING, DOWN, FLOOR, HALFDOWN, HALFUP, UP |
| SORTSEQ | HEX (Default), JOBRUN |
| SYSTIMESENSITIVE | NO (Default), YES |
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. The following examples overrides the time format to Japanese Industrial Standard and date format to European. This is done since DATETIME is assumed to be the same format, which is not required on DB2. It is drawn from a Windows batch file:
DB2 PREP %1.SQC BINDFILE DATETIME JIS GENERIC "DATEOVERRIDE EUR"...
DB2 BIND %1.BND DATETIME JIS GENERIC "DATEOVERRIDE EUR"...