Specifying access to a CICS region control file

About this task

As discussed under The control file table, the ISPF administration interface is one of the CICS BAC components that needs access to the CICS BAC control file of each CICS® region. However, unlike its counterpart, the workstation administration client, the ISPF administration interface does not use the services of the communication server. Instead, the ISPF administration interface obtains access to the appropriate control file in one of the following ways:
  • Indirectly, through the owning CICS region by means of the CICS external communication interface (EXCI). In the normal course of events, the ISPF administration interface reads and updates the control file through the CICS BAC request server task in the CICS region, with which it communicates through EXCI requests. To enable the ISPF administration interface to have access to the EXCI function, ensure the EXCI load library, SDFHEXCI, is available to the interface. This means it must either be in the LINKLIST or included in the TSO logon PROC used by users of the ISPF administration interface.
    Note: If you add the SDFHEXCI load library to the logon PROC STEPLIB concatenation, it might have to be APF-authorized, depending on your system requirements. CICS BAC does not require SDFHEXCI to be APF-authorized, but it is possible that other TSO applications require all data sets in the STEPLIB concatenation to be APF-authorized.
  • Directly, by allocating the VSAM data set data in the event that CICS BAC is not active in the owning CICS region, or the owning CICS region is down.

If access to EXCI fails because the SDFHEXCI load library is not in either the linklist or the user TSO logon PROC, the ISPF administration interface fails with a system abend code 806, reason code 04.


Task Task

Feedback


Timestamp icon Last updated: Monday, 2 December 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic/com.ibm.cics.bac.doc/cbka1/cbka1h0014.html