Adding the CICS EXCI library to the BBI-SS startup procedure

The SDFHEXCI data set must be available to the 

BMC AMI Ops Automation for CICS

 and 

BMC AMI Ops Monitor for CICS

 BBI-SS PAS for normal system searches.To add the CICS EXCI library to the BBI-SS startup procedure

1. If the SDFHEXCI data set is not defined to the system LINKLIST, add it with a DD statement in the STEPLIB concatenation for the BBI-SS PAS.The data set must be APF authorized.

   IBM recommends that you specify the CICS data set of the latest version of CICS that communicates with the BBI-SS PAS. For example, if you are running a CICS 4.1.0 and a CICS 5.1.0 system that both communicate with the BBI-SS PAS, the JCL update might look like this example:

   //STEPLIB DD DISP=SHR,DSN=hlq.BBLINK
   //        DD DISP=SHR,DSN=CICS510.SDFHEXCI (FOR EXCI)

2. Include a SYSMDUMP DD statement in the BBI-SS PAS start up JCL.The external CICS interface uses SYSMDUMP for some error conditions and BMC recommends that you include a SYSMDUMP DD statement in the BBI-SS PAS start up JCL.

   Example

   //SYSMDUMP DD SYSOUT=*

3. If you start the BBI-SS PAS before JES, ensure that you add the DD statement for SYSMDUMP to the list of data sets that must point to real data sets, and enter the SYSMDUMP statement as follows:

   //SYSMDUMP DD DISP=SHR,DSN=sysmdump.dataset,VOLSER=....,UNIT=....
4. The REGION parameter must specify a region large enough to accommodate the internal trace table that is specified by the TRACESZE parameter (the default setting is 16K) in the DFHXCOPT macro, EXCI options table.For more information, see the IBM space CICS External Interfaces Guide.