Other CICS services used

Edit online

CICS® BAC also uses following CICS services. These services are:

  • Global user exits: CICS BAC uses the XFCSREQC global user exit to track state changes to VSAM files originating from CEMT or SPI commands. It also uses the XEISPOUT exit to track state change requests for transient data queues, programs, and transactions originating from CEMT or SPI commands. These two exits are automatically enabled by CICS BAC startup processor.
  • External CICS Interface (EXCI): CICS BAC uses EXCI to ship batch request utility requests to a target CICS region for processing. Ensure that you either (1) install the CICS-supplied sample resource definition group, DFH$EXCI, or (2) create and install similar definitions of your own, to provide the connection resource definitions that you need to support EXCI connections. Note that, if you create your own EXCI definitions, CICS BAC requires a generic connection definition. See the CICS External Interfaces Guide for information about defining CICS resource definitions for EXCI support.

    In addition to its own comprehensive security mechanisms to protect CICS BAC resources (see CICS BAC security), CICS BAC also uses CICS external interface (EXCI ) security; see CICS BAC support for CICS EXCI security.

  • CICS temporary storage: CICS BAC uses a CICS temporary storage queue to save CICS BAC control information pertaining to the CICS region in which it is running. The name of the CICS BAC temporary storage queue is CBKCTLQ1. There is one queue by this name in each CICS region where CICS BAC has been started since the last time the region was started. The queue is not deleted if CICS BAC is shut down in the region. It exists until the CICS region terminates. Also, the queue is region specific, and you should ensure that:
    • The queue is accessed by only one CICS region; it must not be shared by two or more CICS regions
    • The queue is local to the region in which CICS BAC is running. You must not use CICS function shipping to access the queue remotely from another region, such as a queue owning region (QOR).
    • The queue is not set up as a shared queue that can be shared by other CICS regions in a CICSPlex®.
    • The queue is not defined as a recoverable temporary storage queue.