Log Forwarder cannot gather job logs due to spool files purge

Edit online

Operations automation and tools that archive JES2 and JES3 spool files can affect how the Log Forwarder gathers job logs. If a JES spool file is purged in a short interval, the Log Forwarder cannot gather job logs.

Symptom

Spool files are purged, and the Log Forwarder cannot gather job logs.

Cause

The spool files might be purged in one of the following ways:
  • Spool files are purged automatically in a short interval (seconds).
  • All spool files are purged automatically according to output class.
  • Software products are used to offload spool files to another location immediately upon creation, for example, SAVRS (a product of Software Engineering of America (SEA (tm)).
If spool files are purged in a short interval, the following problems might occur and prevent the Log Forwarder from collecting job logs:
  • The job log spool file cannot be detected, though the configured filters are matched.
  • An error occurs while the spool file is read, or the spool file cannot be read, which results in data missing.
  • An abend occurs in the Log Forwarder with the following message in the SYSLOG:
    IEC292I CLOSE MACRO MAY HAVE BEEN USED WITH INCONSISTENT MODE SPECIFICATIONS
    and an abend code occurs:
    SYSTEM COMPLETION CODE=378 REASON CODE=0000001C

Solution

When you select data sources during configuration, consider how your operations impact the job logs that you are gathering from the JES spool. For all the job logs that the Log Forwarder is configured to collect, allow files to reside in the spool long enough for the Log Forwarder to gather its contents.

A best practice is to allow files to reside in the spool for a minimum of two minutes before offloading or purging them.