z/OS JES2 Initialization and Tuning Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Offloading held jobs and data sets

z/OS JES2 Initialization and Tuning Guide
SA32-0991-00

An installation can offload held jobs. This is a useful tool you can use to free up spool space. Offload jobs by specifying HOLD=YES and WS=(HOLD/) on the job transmitter (OFF(n).JT). Note that you can also transmit held jobs to the offload data set if you do not add HOLD to the work selection list. JES2 does not change the hold status when you receive the offloaded job. Of course, the operator can purge (or otherwise alter its disposition) it if held for longer than an installation determines to be an appropriate length of time. Or, the operator can release the job with the $A J operator command.

An installation can also offload held data sets. As with held jobs, JES2 remembers the held attribute across the offload operation. However, for data sets held at the local node, only the job-level work selection criteria on for the OFF(n).ST statement apply. You must explicitly request transmission of held data sets. If you add OUTDISP=(HOLD,LEAVE) to the OFF(n).ST statement, the offload device can then select held data sets. A request of this type means JES2 will transmit all held data sets for a particular job.

JES2 treats data sets held at the destination node (the target system of the offload operation) as normal SYSOUT subject to the work selection criteria for a SYSOUT transmitter.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014