Where allowed to run:
|
Parameters Examples Error messages |
Use the Add CICS Conversion Vector Table (ADDCICSCVT) command to add an entry to the CVT.
Conversion Vector Table (CVT) entries define templates for data conversion either from EBCDIC to ASCII, or when the code page and character set used by the other CICS system is different from that used by the iSeries system. The data conversion must be defined by the system sending the data. Data conversion is required for:
Data is converted according to templates that have been predefined in the CVT. A template describes the type of data, how it is arranged in the record, and the type of conversion required. If your data contains alphabetic and numeric fields, you may need to define a template for each field in the record.
There are three types of conversion templates:
| Top |
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| LIB | Library | Communications name, *LIBL, *CURLIB | Required, Positional 1 |
| GROUP | Group | Communications name | Required, Positional 2 |
| CMDTYPE | API command type | *FILE, *TDQUEUE, *TSQUEUE, *START, *LINK | Required, Positional 3 |
| RSRCID | Resource identifier | Character value | Required, Positional 4 |
| CNVCHRID | Character identifier | Element list | Required, Positional 5 |
| Element 1: Code page | 1-65535 | ||
| Element 2: Graphic character set | 0-65535, *CCSID | ||
| CNVINF | Conversion information | Values (up to 30 repetitions): Element list | Optional, Positional 6 |
| Element 1: Starting location | 0-65535, 0 | ||
| Element 2: Type of conversion | *CHAR, *PACKED, *BINARY, *IDC, *INTEL | ||
| Element 3: Length of conversion | 1-65535, 1 | ||
| Element 4: User specified DBCS data | *NO, *YES | ||
| KEYINF | Key conversion data | Values (up to 30 repetitions): Element list | Optional, Positional 7 |
| Element 1: Starting location | 0-65535, 0 | ||
| Element 2: Type of conversion | *CHAR, *PACKED, *BINARY, *IDC, *INTEL | ||
| Element 3: Length of conversion | 1-65535, 1 | ||
| Element 4: User specified DBCS data | *NO, *YES | ||
| SLTCTL | Selection criteria | Values (up to 30 repetitions): Element list | Optional, Positional 8 |
| Element 1: Starting location | 0-65535, 0 | ||
| Element 2: Character or hex format | *CHAR, *HEX | ||
| Element 3: Value to compare against | Character value | ||
| Element 4: Starting location | Values (up to 30 repetitions): 0-65535, 0 | ||
| Element 5: Type of conversion | Values (up to 30 repetitions): *CHAR, *PACKED, *BINARY, *IDC, *INTEL | ||
| Element 6: Length of conversion | Values (up to 30 repetitions): 1-65535, 1 | ||
| Element 7: User specified DBCS data | Values (up to 30 repetitions): *NO, *YES |
| Top |
Enter the name of the OS/400 library that contains the group. Possible values are:
| Top |
Enter the name of the group to which this CVT entry is to be added.
group-name: The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or one of the special characters, $, @, or #.
| Top |
Indicates the type of EXEC CICS command that will use this entry for user data conversion. This field is used with the resource identifier field to identify this CVT entry.
Possible values are:
| Top |
Enter the resource identifier associated with the EXEC CICS command type. This field is used with the command type field to identify this CVT entry. This resource identifier should have an entry in the appropriate table, as follows:
resource-identifier: For a command type of *TDQUEUE or *START, the maximum length of the resource identifier is 4 characters. For a command type of *FILE, *TSQUEUE, or *LINK, the maximum length of the resource identifier is 8 characters. Any characters on the keyboard can be entered, but lowercase letters and special characters should be enclosed in apostrophes.
When there is not enough space to enter the apostrophes, then enter an ampersand (&) in the first character position to get an extended field size that allows for the entry of additional characters. Blanks are accepted but, when the entry is defined to a control region, anything after the blank is ignored. For example, 'ab g' will be treated as 'ab' in the control region.
Hexadecimal characters should be enclosed in apostrophes and preceded by an uppercase X, for example X'A1A2A3A4'. Any hexadecimal value will be accepted, but, if the value is not a printable character, the entry will be rejected when it is defined to a control region.
| Top |
Enter the code page and character set for the character data representation that will be used by the remote system.
The representation may either be specified by a code page and character set pair, or by a CCSID
There are two elements to this field. Possible values are:
The code page or CCSID of the representation used by the remote system.
Enter the graphic character set to be used by the conversion, or the special value *CCSID if element 1 represents a CCSID rather than a code page
When installed into a control region, if translation tables for a given code page and character set pair can not be found, and the given code page is recognised as a supported CCSID, then the code page will be treated as if it had been specified as a CCSID.
| Top |
This field defines a default conversion template. Use this field to define conversion information for data that does not satisfy the selection criteria defined in the selection criteria field.
Note: Use the key information field for converting key fields.
Specify:
There are 4 elements to this field. Possible values are:
The position in the record of the start of the data to be converted.
Type of conversion to be done on the field.
The length in bytes of the field to be converted.
This element, which is valid only when type of *CHAR is specified for the field, indicates whether or not the data to be converted contains SO/SI delimiters. When SO/SI delimiters are used then only data prior to the SO delimiter and after the SI delimiter is converted, if the language is not an ideographic based one.
| Top |
This field defines the conversion template for one key field. Specify:
This parameter is only valid for a command type of *FILE is specified, and if the file is accessed using keys, that is it is a key-sequenced data set (KSDS).
Note: The FCT entry will define the location of the key.
Possible values are:
The position in the record of the key field.
The type of conversion to be done on the field.
The length in bytes of the field to be converted.
This element, which is valid only when type of *CHAR is specified for the field, indicates whether or not the data to be converted contains SO/SI delimiters. When SO/SI delimiters are used then only data prior to the SO delimiter and after the SI delimiter is converted, if the language is not an ideographic based one.
| Top |
Enter the selection criteria and the conversion information for each field in the user data that is to be sent from, or to, another CICS system. Selection criteria consists of the position and value to be checked in the user data in order to use the associated conversion information. The conversion information consists of position and length of the field and the type of conversion to be applied to it.
Note: When the user data did not satisfy the conditions that are specified by any of the selection criteria, then the conversion information (CNVINF) field is used to convert the user data.
Possible values are:
The position in the record where the comparison of data should start.
Indicates whether the selection data is character or hexadecimal data.
The value with which the data is to be compared, in order to use the associated conversion information.
Selection information (SLTINF)
The conversion information for each field in the user data to be used when the selection criteria is a match.
Possible values are:
The position in the record where conversion of data should start.
The type of conversion to be done on the field.
The length in bytes of the field to be converted.
This element, which is valid only when type of *CHAR is specified for the field, indicates whether or not the data to be converted contains SO/SI delimiters. When SO/SI delimiters are used then only data prior to the SO delimiter and after the SI delimiter is converted, if the language is not an ideographic based one.
| Top |
| Top |
| Top |