Message log data set (EQQMLOG)

The message log data set can be written to SYSOUT or a data set. The data control block (DCB) for this data set is defined by HCL Workload Automation for Z as follows:

EQQMLOG DCB attributes
DCB=(RECFM=VBA,LRECL=125,BLKSIZE=1632)

If the message log data set becomes full during initialization, or when a subtask is restarted, HCL Workload Automation for Z will abend with error code SD37. In either case, you must stop HCL Workload Automation for Z and reallocate the message log data set with more space. In all other circumstances, if the data set fills up, HCL Workload Automation for Z redirects messages to the system log instead.

Note: The scheduler ABENDs with error code sb37 or sd37 if the message log data set becomes full under any of the following circumstances:

During initialization
When a subtask is restarted
While processing any modify command which requires parsing of initialization parameters or specifies the newnoerr, noerrmem(member), or lstnoerr options

In the last case, the ABEND also occurs if the EQQMLOG is already full when any such command is issued. In all these cases you must reallocate more space to the message log data set. In all the other cases, if the data set fills up, the scheduler redirects messages to the system log instead.

EQQPCS02 contains two allocations for the EQQMLOG data set. For an HCL Workload Automation for Z address space, the data set is allocated with the low-level qualifier MLOG. For the scheduler server jobs, the data set is allocated with the low-level qualifier MLOGS.

Note: If you allocate the message log data set on DASD, define a different data set for HCL Workload Automation for Z batch program. The data set must also be different from the one used by each HCL Workload Automation for Z address space (controller, standby controller, tracker, and server). The data set cannot be shared.