Copy an Open Spooled File

In the past, you could not copy a spooled file when it was still open; if you attempted the copy, it would fail with CPF3482, “Copy request failed. Spool file &1 is open.” The spooled file had to be completed before the copy would be allowed.

With IBM i 7.3, you can now copy an open spooled file.


Sending a Spooled File via TCP When Working With Spooled Files

You can work with spooled files through a variety of command interfaces: Work with Spooled Files (WRKSPLF), Work with Output Queue (WRKOUTQ), and Work with Job (WKRJOB) option 4 (aka WRKJOB OPTION(*SPLF)). These interfaces have option 1=Send, which can be used to send spooled files to another system; this send option invokes Send Network Spooled File (SNDNETSPLF).


Working With Your Spooled Output

In recent blog articles I wrote about Job Log Pending and the Job Log Output attribute that can be used to prevent the generation of spooled job logs. In addition, in a prior blog, I also wrote how to Detach Spooled Files from a job.

These all can be very helpful features, but one common concern I hear when I discuss these configuration options with clients is how to find their spooled files and job logs. Taking advantage of these features means you will likely need to change your approach to finding spooled files, but the capability to do so has been built into the operating system.


Job Log Output

Last week I wrote about Job Log Pending. With job log pending, you do not have to write job logs to spooled files.

At the end of that blog, I mentioned how you can use the Log Output (QLOGOUTPUT) system value or job attribute to take advantage of job log pending. This week, I’ll explain the values available for “Log output” and give some general recommendations.