CA Spool is not capturing sysouts from JES spool even though they have the correct work selection attributes as class and destination.
Article ID: 40489
Updated On:
Products
Issue/Introduction
Symptoms:
CA Spool is not capturing sysouts from JES spool even though they have the correct work selection attributes as class and destination.
Cause:
The CA Spool XFER interface may have abended due to a previous error. You can check the status of the XFER interface by issuing the DX CA Spool command. One of the ways of doing so is by using the MODIFY console command against the CA Spool started task name:
F caspool-stc-name,DX
ESF832 FILE TRANSFER SUBTASK IS ACTIVE
ESF832 ESF->JES INTERFACE IS ACTIVE
ESF832 SAPI JES->ESF INTERFACE IS ABENDED
Where caspool-stc-name is the name of the CA Spool started task.
Resolution/Workaround:
1. Check if there is a huge sysout in JES2 spool that may have caused this error. You may need to put this sysout on hold or purge it before restarting the XFER interface
2. Issue the command SX,JESTOESF to restart the JES to ESF interface. For example, using the MODIFY console command:
F caspool-stc-name,SX,JESTOESF
Where caspool-stc-name is the name of the CA Spool started task.
You should see this message in response to the command above:
ESF838 JES->ESF INTERFACE STARTED
3. Just issue the DX command again to confirm the interface is in active status:
F caspool-stc-name,DX
ESF832 FILE TRANSFER SUBTASK IS ACTIVE
ESF832 ESF->JES INTERFACE IS ACTIVE
ESF832 SAPI JES->ESF INTERFACE IS ACTIVE
Additional Information:
CA Spool - Operations - DX Command - Display XFER Interface Status
CA Spool - Operations - SX Command - Start XFER Interface
CA Spool - Customization - XFER Interface
Environment
Component:
Feedback
