30.06.2013 Views

File Management - IBM

File Management - IBM

File Management - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2. A date and time field (time stamp).<br />

For output queues with SEQ(*JOBNBR) specified, the date and time that the job<br />

which created the spooled file entered the system are the date and time field.<br />

(A sequential job number is also assigned to the job when it enters the system.)<br />

For output queues with SEQ(*FIFO) specified, the date and time field is set to<br />

the current system date and time when any of the following occur:<br />

v A spooled file is created by opening a device file.<br />

v The output priority of the job which created the spooled file is changed.<br />

v The status of the spooled file changes from RDY to HLD, SAV, OPN, or CLO;<br />

or the status changes from HLD, SAV, OPN, or CLO to RDY.<br />

v A spooled file is moved to another output queue which has SEQ(*FIFO)<br />

specified.<br />

3. The SCHEDULE parameter value of the spooled file.<br />

<strong>File</strong>s with SCHEDULE(*JOBEND) specified are grouped together and placed<br />

after other spooled files of the same job that have SCHEDULE(*IMMED) or<br />

SCHEDULE(*FILEEND) specified.<br />

4. The spool number of the file.<br />

Because of the automatic sorting of spooled files, different results occur when<br />

SEQ(*JOBNBR) is specified for an output queue than when SEQ(*FIFO) is<br />

specified. For example, when a spooled file is held and then immediately released<br />

on an output queue with SEQ(*JOBNBR) specified, the file will end up where it<br />

started; but if the same file were held and then immediately released on an output<br />

queue with SEQ(*FIFO) specified, the file would be placed at the end of the<br />

spooled files which have the same priority and a status of RDY.<br />

Using multiple output queues<br />

You may want to create multiple output queues for:<br />

v Special forms printing<br />

v Output to be printed after normal working hours<br />

v Output that is not printed<br />

An output queue can be created to handle spooled files that need only to be<br />

displayed or copied to a database file. Care should be taken to remove<br />

unneeded spooled files.<br />

v Special uses<br />

For example, each programmer could be given a separate output queue.<br />

v Output of special <strong>IBM</strong> files<br />

You may want to consider separate queues for the following <strong>IBM</strong>-supplied files:<br />

– QPJOBLOG: You may want all job logs sent to a separate queue.<br />

– QPPGMDMP: You may want all program dumps sent to a separate queue so<br />

you can review and print them if needed or clear them daily.<br />

– QPSRVDMP: You may want all service dumps sent to a separate queue so the<br />

service representative can review them if needed.<br />

Output queue recovery<br />

If a job that has produced spooled files is running when the job or system stops<br />

abnormally, the files remain on the output queue. Some number of records written<br />

Chapter 5. Working with spooled files 155

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!