Page encoding (UNLD command)

You can encode unloaded data in your UNLD command using a variety of code pages.

Encoding data applies only to single-byte character strings (SBCS) in fields defined as CHAR or VARCHAR. External numeric, date, and time fields are also subject to the encoding process. Character fields defined as BIT data are excluded. Double-byte character strings (DBCS) are also excluded.

Use one of the following options to specify how BMC AMI Unload encodes unloaded data code pages. The CCSID option takes precedence over the others.

Related topics

DATEFMT (UNLD syntax)

TIMEFMT (UNLD syntax)

UNLD-CCSID 

Format delimiters

Format delimiters are not subject to encoding. BMC AMI Unload uses them as is, without any changes. You can override defaults with the appropriate encoded delimiters.

Format delimiters are as follows:

  • NULLCHAR
  • FIELDSEP
  • CHARFLDDLM
  • NULLSTRING
  • COLDEL
  • CHARDEL
  • DECPT

The following table summarizes the behaviors of various data types. For additional information, see BMC-AMI-Utilities-SQL-language.

Data type behaviors

Data type

Encoded?

Behavior

DATE, TIME, and TIMESTAMP formats

Yes

BMC AMI Unload encodes all DATEFMT, TIMEFMT, and TSFMT skeletons from a CCSID of 37 to the desired CCSID.

HEX constants

No

BMC AMI Unload encodes HEX constants in a SELECT statement and treats them as BIT data. For example: SELECT x'c1c2' from B

Padding

Yes

BMC AMI Unload encodes pad characters.

In FORMAT DSNTIAUL or FORMAT EXTERNAL, BMC AMI Unload pads VARCHAR fields as follows:

  • EBCDIC blanks in EBCDIC
  • ASCII blanks in ASCII
  • Unicode blanks in Unicode


 

  • 13.1
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*