Server runtime processing and the BTS NOCHECK option

The CICS® Service Flow Runtime supports the BTS NOCHECK processing option.

It is important to know the following information regarding the BTS NOCHECK option as it pertains to CICS Service Flow Runtime processing.
  • BTS NOCHECK option is only supported if the CICS Service Flow Runtime request property, MP-PERSISTENCE-IND, is set appropriately. For information on property settings, see Request properties.
  • CICS Service Flow Runtime passthrough processing is always run using the BTS NOCHECK option. For more information on Passthrough processing, see Passthrough processing
  • The CICS Service Flow Runtime BTS NOCHECK processing option should not be used if your deployed sequence flow has a compensation requirement.

    Pertinent CICS Service Flow Runtime data container information might not be available for any subsequent compensating flow. See Determine if compensation is necessary and How compensation processing works for further information.

  • The BTS NOCHECK option specifies that no record is to be written to the repository data set to reserve the name of the process. Using the BTS NOCHECK option improves BTS performance by removing the write to the repository and its associated logging.
  • If you use the BTS NOCHECK option, be aware that the error of specifying a non-unique process name no longer causes a PROCESSOR condition to be returned on the DEFINE PROCESS command. The error might not be discovered until much later when syncpoint occurs, making it much harder to debug.