Compatibility

bms_ascii_attributes

Specifies whether XCICS BMS must consider the BMS attributes specified into User programs to be treated as EBCDIC or ASCII.

Allowed values are “yes” or “no”. The default value is “no” and means that attributes are handled in EBCDIC format. When "yes" is specified, BMS attributes are translated into EBCDIC before to get handled.

Syntax

set bms_ascii_attributes=(yes|no)

bms_convert_attribute_space

Specifies whether XCICS BMS must treat a BMS field attribute of value 0x20 (ASCII space) as 0x40 (EBCDIC space).

Allowed values are “yes” or “no”. The default value is “no” and means that an attributes of value 0x20 is managed as is. When "yes" is specified, the value 0x20 is managed as 0x40.

Syntax

set bms_convert_attribute_space=(yes|no)

bms_ascii_tioadba

Specifies whether XCICS BMS must supply the formatted output area (TIOADBA) return by the SEND MAP SET command in ASCII encoding.

Allowed values are “yes” or “no”. The default value is “yes” and means that the TIOADBA area is encoded in ASCII. When "no" is specified, the TIOADBA area is encoded in EBCDIC format.

Syntax

set bms_ascii_tioadba=(yes|no)

assume_getmain_shared

If set to yes, XCICS assumes that all GETMAIN operation have to be allocated in shared memory, instead of having task-only allocation.

Default is no.

Syntax

set assume_getmain_shared=<yes|no>

force_little_endian_api

If set to yes, XCICS handles binary fields used in by the COBOL API interface as COMP-5 data type. This setting has effect only on little-endian systems, such as Linux and Windows on Intel CPUs. Handling binary field as COMP-5 is useful when you must globally handle all binary fields in a COBOL program as machine dependent binaries , due to the usage of third party software that requires native binary interface and you cannot manually change the program. A typical scenario is the usage of the Oracle pre-compiler on little-endian systems: to allow a correct management of binary fields in the Oracle API interface, you may instruct the COBOL compiler to manage all COMP file as COMP-5. Therefore, you also have to instruct XCICS/TS to expect COMP-5 data in its API interface (EXEC CICS).

Deafult is NO.

Syntax

set force_little_endian_api=<yes|no>

force_bms_comp_length

If set to yes, XCICS assumes length field in BMS communication areas, have to be handled as big endian binaty fields (COMP)  instead of system dependent fields (COMP-5).

Deafult is NO.

Syntax

set force_bms_comp_length=<yes|no>

default_date_format

Defines the default format for the date/fulldate returned by FORMATTIME command.

Admittable values:

Syntax

set default_date_format=<eu|us|iso>

reset_trigger_on_error

If set to yes, XCICS reset the TD trigger to 0 (zero) when an abend occurs on the triggered transaction. By default XCICS does not reset trigger on error.

Syntax

set reset_trigger_on_error=(yes|no)

preserve_connection_on_dump

If set to yes, XCICS mantains the connection with the terminal even if a signal or a COBOL error is detected.

Default is YES.

Syntax

set preserve_connection_on_error=(yes|no)