Feature toggles

Feature toggles make it easier for you to make the configuration changes that are necessary to enable new capabilities, particularly for capabilities that are delivered between releases of CICS. This page lists the feature toggles available in CICS® TS 5.4.

For an introduction to feature toggles, see CICS feature toggles and continuous delivery.
For a summary of changes to feature toggles by release, see Toggle-enabled features, support by release.
For configuration information, see Specifying feature toggles and the information that is linked for each feature toggle below.

Feature toggles for CICS Transaction Server for z/OS®

Feature toggle

Capability

com.ibm.cics.bms.ids={true|false}

Allows CICS to detect if a 3270 emulator has invalidly modified a protected field generated by a BMS map.

Find out more: BMS 3270 Intrusion Detection Service

com.ibm.cics.cmci.jvmserver={true|false}

Allows you to set up the CMCI without the CMCI JVM server.

Find out more: Setting up access for CICS Explorer

com.ibm.cics.cpsm.bas.largecicsplex={true|false}

Allows you to constrain large resource deployments lists for BAS to a single data space instead of spreading across multiple data spaces.

com.ibm.cics.cpsm.wlm.botrsupd.enabled={true|false}

Allows you to disable updates to the Coupling Facility when the task load falls below the lower tier threshold of the CICSPlex SM tuning parameter, BOTRSUPD.

Find out more: Region status server, bottom-tier parameter (BOTRSUPD)

com.ibm.cics.cpsm.wlm.surgeresist={true|false}

When applied to CICSPlex SM WLM routing regions, this feature toggle takes effect for the QUEUE and GOAL WLM algorithms when using CICSPlex SM sysplex optimized workload routing. It has no effect when applied to target regions.

When the feature toggle is set to true, surges of extremely high frequency, short duration transactions can be mitigated by reducing the likelihood that recently selected target regions are reselected. Enabling this feature toggle increases the average routing cost per transaction, but restores the routing behavior of CICSPlex SM before APAR PH30768 is applied.

Find out more: Learn more about the changes to CICSPlex SM sysplex optimized workload routing behavior in What's New.

com.ibm.cics.db2.origindata={true|false}

Enables or disables the passing of adapter origin data to Db2® for adapter tracking.

Find out more: Transaction tracking

com.ibm.cics.http.options.handler={program_name}

Allows you to specify the name of the HTTP Options handler program.

Find out more: HTTP method reference for CICS web support

com.ibm.cics.rls.delete.ridfld={true|false}

To support migration from non-RLS to RLS access mode, allows you to achieve the local VSAM CILOCK=NO behavior for RLS files. This avoids the potential of AFCG abends when you use DELETE RIDFLD on RLS files.

Find out more: VSAM RLS

com.ibm.cics.tls.minimumkeystrength={1024|2048}

If the feature toggle value is set to 2048 CICS will use a minimum key size of 256 for ECC keys and 2048 for RSA, DSA and Diffie-Hellman keys during TLS handshakes.

CICS will use a minimum key size of 256 for ECC keys and 2048 for RSA, DSA and Diffie-Hellman keys during TLS handshakes.

The following System SSL settings will be in effect:

GSK_CLIENT_ECURVE_LIST=00250024002300300029

GSK_SERVER_ALLOWED_KEX_ECURVES=00250024002300300029

GSK_CLIENT_EPHEMERAL_DH_GROUP_SIZE=2048

GSK_SERVER_EPHEMERAL_DH_GROUP_SIZE=2048

GSK_PEER_DH_MIN_KEY_SIZE=2048

GSK_PEER_DSA_MIN_KEY_SIZE=2048

GSK_PEER_ECC_MIN_KEY_SIZE=256

GSK_PEER_RSA_MIN_KEY_SIZE=2048

If the feature toggle value is set to 1024 or is not set, then the System SSL default values will be used for the key sizes and set of elliptical curves. For more information about the SSL default values, see gsk_environment_open() in z/OS documentation.