SOLVE:ACCESS - reduce the spool usage in JES2

book

Article ID: 195704

calendar_today

Updated On:

Products

CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:FTS CA SOLVE CA Mainframe Connector for Linux on System z CA SOLVE

Issue/Introduction

We have some very long running SOLVE started tasks and the logs are taking up a great deal of spool space,  we don't recycle these started tasks as we always have users on them.  I want to reduce the spool usage, as the spool percentage is getting high. How do I do this without recycling the started tasks
 

 

Environment

Release : 5.0

Component : CA SOLVE:Access Session Management

Resolution

For SOLVE:Access 5.0 region, the standard SOLVE install provides LOG1 to LOG9 as JES output datasets. They are normally allocated with FREE=CLOSE.

The LOGSWAP command is used to close the current dataset and open the next.

This method relies on the user to implement timer commands to reallocate the LOGx DD.



The alternative is that JES2 can do it automatically via the SPIN operand (since z/OS 1.12).



For example JES can free the output for processing after a line limit is reached -

//ddname DD SYSOUT=&SYSOUT,SPIN=(UNALLOC,100K)



When SPIN=UNALLOC is used the JES2 $Txnnnnn,SPIN,DDNAME= command can be used to split the output at a particular time. (x is J for job, S for STC)