Why? If you delete spool files from outqueues the system spoolfile cleanup routines will cleanup these spool file database files. If you query these you will see mulitple members that contain information and attributes of spooled files. If the spooled files are deleted the system will remove these qspl/q* files for you without damaging queues. =========================================================== Although you don't say what version/release you're running of the operating system, we have to assume that you are reasonably current. It's <b>possible</b> that deleting the file won't cause serious damage, but I wouldn't bet my career on it like you might be close to doing. In earlier releases, it was possible to significantly affect the spooling subsystem simply by reading those files. IIRC, IBM has done work to limit the negative effects as new releases come out; but it is still unwise to attempt to manipulate the spooler database files directly. You should use the supplied interfaces for manipulating spool storage. The spooler subsystem maintains its locks and indexes for those files, and you don't want to interfere with those. If spool storage has become too large, review and use the RCLSPLSTG command. Also, review and use the QRCLSPLSTG system value. You might consider asking a question that describes why you are considering deleting this file. Answers might supply better procedures. Tom

Why? If you delete spool files from outqueues the system spoolfile cleanup routines will cleanup these spool file database files. If you query these you will see mulitple members that contain information and attributes of spooled files. If the spooled files are deleted the system will remove these qspl/q* files for you without damaging queues. =========================================================== Although you don't say what version/release you're running of the operating system, we have to assume that you are reasonably current. It's <b>possible</b> that deleting the file won't cause serious damage, but I wouldn't bet my career on it like you might be close to doing. In earlier releases, it was possible to significantly affect the spooling subsystem simply by reading those files. IIRC, IBM has done work to limit the negative effects as new releases come out; but it is still unwise to attempt to manipulate the spooler database files directly. You should use the supplied interfaces for manipulating spool storage. The spooler subsystem maintains its locks and indexes for those files, and you don't want to interfere with those. If spool storage has become too large, review and use the RCLSPLSTG command. Also, review and use the QRCLSPLSTG system value. You might consider asking a question that describes why you are considering deleting this file. Answers might supply better procedures. Tom