Main libraries

Once the product has been installed, there are six main libraries.
  • #hlq.SBZULINK
  • #hlq.SBZULOAD
  • #hlq.SBZULMOD
  • #hlq.SBZULLEP
  • #hlq.SBZURESL
  • #hlq.SBZUSAMP

The #hlq.SBZULINK load library needs to be APF-authorized and loaded into the link list of the operating system. The main BZUPLAY program requires that it be authorized to support the replay. This load library is used during replay only.

The #hlq.SBZULOAD load library contains most of the standard load modules and is used as:

  • The DFHRPL library for CICS during collection
  • For all environments on the replay side

The #hlq.SBZULMOD load library contains the optional Db2-specific load modules used during the replay side.

The #hlq.SBZULLEP load library contains the optional COBOL runtime, batch MQ and LE-specific load modules used during the replay side.

The #hlq.SBZURESL load library contains the Db2 and IMS-specific load modules. IMS does not support PDSE’s, so this load library must be a standard PDS. This load library is used during collection only.

The #hlq.SBZUSAMP source library contains the sample JCL, templates and configuration files. Customized procedures have been created for your use, by the installation process. These procedure names start with BZUP.

The following table shows which libraries are used and when.
  #hlq.SBZULOAD #hlq.SBZULMOD #hlq.SBZULLEP #hlq.SBZURESL
CICS collection Yes      
Batch collection with BZUBCP Yes   Yes (4)  
Batch Db2 collection     Yes (4) Yes
Batch DL/I collection     Yes (4) Yes
Batch MQ collection     Yes (4)  
Batch file I/O collection     Yes (4)  
IMS/TM collection       Yes (1) (5)
IMS/BMP collection       Yes (5)
Replay Yes Yes (2) Yes (3)  
Note:
  • (1): The relinked DFSESPR0 and DFSPRH00 load modules are to be placed ahead of other load modules in the IMS Control Region’s STEPLIB, if using either IMS/TM or IMS/BMP.
  • (2): Only required for batch Db2 replay. If the replaying of the Db2 application gets the message: A SERIOUS ERROR HAS OCCURRED -- SQLSTATE = 57015, it is because the replay JCL needs to add #hlq.SBZULMOD to the STEPLIB.
  • (3): Only required for specific replay features, such as replaying with the recorded timestamp, replaying native file I/O calls, or replaying MQ calls. This load library should be left unused unless there is a requirement to replay COBOL and PL/I applications with the recorded date and time, through the native language date and time interface. For example, in COBOL this interface is the COBOL ACCEPT verb.
  • (4): Required for batch file I/O collection from COBOL programs or MQ collections.
  • (5): The #hlq.SBZURESL library is to be placed in the IMS message region’s STEPLIB ahead of the real IMS SDFSRESL library.
Important:
  • When installing a new version of IMS, Db2 or LE, you must rerun the link edit jobs for both the #hlq.SBZURESL and #hlq.SBZULLEP load libraries. This will keep this product’s thin-layer interfaces at the same level as the real IMS, Db2 or LE. These interfaces are used exclusively by this product. Failure to do this for the #hlq.SBZULLEP load library can cause a 4093-F8 LE abend which means: Language Environment has detected a mismatch of runtime modules. Check to ensure that runtime modules CEEBINIT, CEEPIPI, CEEBPICI, and CEEPLPKA are at the same release level.
  • When using CICS, this product is intended to perform its recording in a low volume environment. The process involves filtering records, but it is possible that this filtering will pick up many records is a short period of time. The VSAM common file for these interim collected record needs to be large enough to hold them. The size of this VSAM will vary from one environment to another, but the size of this VSAM file could be large.
  • In the CICS environment, common memory areas such as the CWA, TCTUA, TWA or COMMAREAs will be serialized and recorded. If these memory areas contain many pointers to other memory areas, it is possible that many serializations will take place. This could result in an AICA abend as CICS might think the process is in a loop. There are several configuration options provided to allow a user to define limits for these serializations. Refer to the configuration section of this documentation for more details.