Welcome to the wonderful world of spooling! If the final destination of a report has to be changed, the first thing you have to know is the name of the report (the 'FILE' name how it appears in your spooled files) this is usually the name of the printer file used to create the report.
You could specify the out queue right there, but this would mean that this report would always be sent to that queue -- for every user. This could be just fine for some spooled files (i.e. invoices to be send out can be printed on the invoice printer that is filled with special paper.)
You can also use job descriptions to send the spooled files to the correct out queue (i.e. all prints requested in the test environment could be send to a test queue that has no printer attached. Most reports would have to be printed on different printers based on the user who requested the printout (i.e. department printers.) Another option is to print based on the workstation (i.e. prints requested by any user working on the computer at the loading dock.)
We have four areas that we steer the spooled file to: PRTF, JOBD, USRPRF, and DEVD. If that is not enough for you, these four areas all have two values that can control your spooling: out queue name and printer device. Sounds complicated but it's not really that bad. Look at the graphical flow of the spooled file here.
Simply follow the arrows and you will end up on some out queue or printer. The red values are the defaults when creating the various objects.
Note: If all objects have been created with default values for the out queue and the printer, you will end up in the printer specified in the system value QPRTDEV.
================================== MORE INFORMATION ON THIS TOPIC ==================================
The Best Web Links: Tips, tutorials and more.
Visit the ITKnowledge Exchange and get answers to your systems management questions fast.
Read this Search400.com Featured Topic: Take control of your iSeries.
Ask the Experts yourself: Our systems management gurus are waiting to answer your technical questions.
This was first published in February 2005