15.10 - Mechanism-data-encoding - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

prodname
Call-Level Interface Version 2
vrm_release
15.10
category
Programming Reference
featnum
B035-2417-035K

If additional data is required by the specified Mechanism‑name, Mechanism‑data‑encoding optionally specifies the character set of the area addressed by Mechanism‑data‑ptr. If Mechanism‑data‑ptr is not specified, this option is validated but not otherwise processed. While the data may be encoded in any supported session character set, if overridden by this option, only UTF-8 and UTF-16 can be specified.

Mechanism‑data‑encoding exists only when DBCHINI had been called for a DBCAREA with Total‑length set to at least 640 (that is, the returned DBCAREA Level value is at least 1). For a smaller DBCAREA, Mechanism‑data‑encoding is ignored.

Note: Logon mechanisms are currently not supported for a mainframe‑connected system.

 

In this language...

The variable name for Mechanism‑data‑encoding is...

COBOL

MECHANISM‑DATA‑ENCODING

PL/I

MECHANISM_DATA_ENCODING

C

mechanismDataEncoding

IBM Assembler

DBCNIME

 

This routine...

Does this for Mechanism‑data‑encoding...

DBCHINI

writes

DBCHCL

reads (CON)

 

Mechanism‑data‑encoding is used by...

To...

applications

write

One of the following numeric values can be set before establishing a connection:

 

Value Used

Mechanism‑data‑encoding Settings and Mneumonics

Session character set default

0

DBCNIMES ('DBC_MechCodingSession' for C,
SESSION for COBOL, DBC_MECH_CODING_SESSION for PL/I)

UTF8

3

DBCNIMET ('DBC_MechCodingUTF8' for C,
UTF8 for COBOL, DBC_MECH_CODING_UTF8 for PL/I)

Also, when UTF-8 is specified, each character in Mechanism‑data‑ptr requires between one and three bytes.

UTF16

4

DBCNIME2 ('DBC_MechCodingUTF16' for C,
UTF16 for COBOL, DBC_MECH_CODING_UTF16 for PL/I)

Also, when UTF-16 is specified, each character in Mechanism‑data‑ptr requires two bytes.