Setup for batch with Db2

The setup for collecting batch/Db2 calls is straightforward. No special configuration is required, outside of the standard installation of Virtual Test Platform, although a relink of a Db2 module is required.

The sample data set with a member name of BZULDB2 will give an example of how to relink the Db2 load module. This load module must be placed in the batch job’s STEPLIB ahead of DSN.SDSNRESL, so that DSNACAF, DSNECP10 and DSNARRS are taken from the relinked load library.

Typically, batch/Db2 programs are executed through batch/TSO execution, using the IKJEFT01 program. This will continue to be the case for collecting batch/Db2 calls. The #hlq.SBZURESL load library must be placed in the job’s STEPLIB. Db2/CAF programs are supported and are usually invoked directly through the EXEC PGM JCL statement.

If native file I/O collection is desired for QSAM or VSAM (KSDS, ESDS or RRDS), then the #hlq.SBZULLEP load library must be placed in the job’s STEPLIB.

If program-to-program interceptions are wanted, then the configuration file must be pointed to by the BZUCFG DD statement in the batch/TSO JCL. This configuration file can be a sequential data set or a PDS member. A sample configuration file is in the sample data set with a member name of BZUSCFG.

The output of the data collection is written to a variable-blocked sequential data set with block size of 32760 and logical record length of 32756, or a fixed-block sequential data set with logical record length of a reasonable size balancing both the average size of the records and the amount of wasted space there will be. A reasonable recommendation is 256 bytes. This data set will be pointed to by the BZUPLAY DD statement.

For more information, see Recording from batch with Db2.