Batch-loader reports

The only report produced by the batch loader is a list of messages, written to the data set specified by the EQQMLOG DD statement. Refer to this report to find syntax or validation errors in your control statements. The batch-loader message log must not be the same message log that your IBM Z Workload Scheduler subsystem uses, but if you have directed the batch-loader output to an IBM Z Workload Scheduler subsystem, some messages might be written to the EQQMLOG data set that is allocated to that subsystem. Errors related to the request itself, such as a syntax error in a parameter argument, result in a message being written only to the EQQMLOG that is allocated in the batch-loader JCL.

If the batch loader terminates with message EQQX268W, the database is being used by another function. When the batch loader has a completed database record to store, it enqueues on the database. If the database is busy, the batch loader waits for a maximum of 90 seconds for the database to become available. Normally, only the planning programs or mass update hold the database for more than 90 seconds.

To avoid failures like this, allocate a data set such as the dump data set with disposition OLD or MOD in all IBM Z Workload Scheduler batch programs. This ensures that if there is a severe error, multiple dumps are not overwritten, and a beneficial side effect is serialization of batch programs requiring access to the databases.

To verify that the AD, OI, or RG information that has been created accurately reflects your environment, use the IBM Z Workload Scheduler ISPF panel to print application descriptions or operator instructions. Several reports are available.