Configure OM Spool to Retain JES2 Spool SYSOUT After Transmission

Products

• OM Spool

Issue/Introduction

When transmitting mainframe SYSOUT to a VPSX server, the default behavior of CA Spool is to purge the original JES2 spool entries after the transmission completes

Environment

• Output Management Spool - 14.0

Cause

OM Spool executes file transfer operations through its XFER interface based on the global XFEROPT initialization setting. By default, XFEROPT flags are set to release or purge the source JES2 spool files once the data handoff succeeds.

Resolution

to prevent the system from purging the transferred file from the JES queue after the transfer is complete, follow these steps:

1. Locate the ESFPARM configuration member used by your CA Spool started task.
2. Add the following line to the configuration: XFEROPT=11
   (Option 11 specifies that transferred JES SYSOUT files are retained on the JES spool rather than purged upon successful transmission.)
3. If you currently have an XFEROPT statement (e.g., XFEROPT=##), you can keep it and add the new XFEROPT=11 line directly above or under it.
4. Recycle the CA Spool started task for the changes to take effect.

Additional Information

For additional guidance on the Initialisation Option - XFEROPT, see the [OM Spool documentation] (https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-spool/14-0/administrating/initialization-options/xferopt.html)

For further assistance with the Initialisation Option - XFER, see the [OM Spool documentation] (https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-spool/14-0/administrating/initialization-options/xfer.html)