Code Conversion (CSNBXEA and CSNBXAE)

Use these utilities to convert ASCII data to EBCDIC data (CSNBXAE) or EBCDIC data to ASCII data (CSNBXEA).

These utilities do not support invocation in AMODE(64).

Format

CALL CSNBXAE(
             return_code,
             reason_code,
             exit_data_length,
             exit_data,
             text_length,
             source_text,
             target_text,
             code_table)
CALL CSNBXEA(
             return_code,
             reason_code,
             exit_data_length,
             exit_data,
             text_length,
             source_text,
             target_text,
             code_table)

Parameters

return_code
Direction Type
Output Integer

The return code specifies the general result of the callable service. ICSF and cryptographic coprocessor return and reason codes lists the return codes.

reason_code
Direction Type
Output Integer

The reason code specifies the result of the callable service that is returned to the application program. Each return code has different reason codes assigned to it that indicate specific processing problems. ICSF and cryptographic coprocessor return and reason codes lists the reason codes.

exit_data_length
Direction Type
Ignored Integer

This field is ignored. It is recommended to specify 0 for this parameter.

exit_data
Direction Type
Ignored String

This field is ignored.

text_length
Direction Type
Input Integer

The text_length contains an integer that is the length of the source_text. The length must be a positive nonzero value.

source_text
Direction Type
Input String
This parameter contains the string to convert.
target_text
Direction Type
Output String

The converted text that the callable service returns.

code_table
Direction Type
Input String

A 256-byte conversion table. To use the default code table, you need to pass a full word of hexadecimal zero's. See EBCDIC and ASCII Default Conversion Tables for contents of the default table.

Note: The Transaction Security System code table has 2 additional 8-byte fields that are not used in the conversion process. ICSF accepts either a 256-byte or a 272-byte code table, but uses only the first 256 bytes in the conversion.

Usage notes

These services are structured differently than the other services. They run in the caller's address space in the caller's key and mode. ICSF need not be active for you to run either of these services. No pre- or post-processing exits are enabled for these services, and no calls to RACF are issued when you run these services.

Required hardware

No cryptographic hardware is required by this callable service.