Deleting a spool file, limitations

When you delete a linked spool file with the PURGE command, the system removes the spool file immediately because the PURGE command opens the file with exclusive access.

This is different from what happens when you use SPOOLF ...;DELETE. If a spool file is not open, not printing, or not being stored, SPOOLF ...;DELETE removes the spool file immediately. Otherwise, it is put into the DELPND state. The system notifies any spooler process printing the spool file, and printing stops at that point. Then the system deletes the spool file when its last user (except the STORE program) closes the file.

The DELETE parameter of the SPOOLF command works for DATA input spool files in the READY state. It also works for all output spool files not in the CREATE state. It does not work for job $STDIN spool files. You must use the ABORTJOB command to delete job $STDIN spool files.

For more information, refer to the SPOOLF command with the DELETE parameter in chapter 4.

	NOTE: If the system cannot gain exclusive access to the file (for example, if a spooler is printing the file), PURGE fails.

The system deletes unlinked spool files in the same manner as it deletes any permanent disk files.