RE: Query Definitions Using Printers

[Jerry Adams <Jerry@xxxxxxxxxxxxxxx>]

I think that option 6 on WRKQRY is more readable than DMPOBJ, Vern. .-)

To explain my need, if it helps, we have, shall we say, issues frequently with printers.  Many of our jobs route to specific printers in order fulfillment (aka warehouse).  When one of those printers go down, we dynamically re-route the output to a different printer using a command that I wrote.  It checks to see if a printer has a substitution printer defined.  This works even on legacy OCL procedures.  

I'm currently modifying *All procedures and processes to use this command.  Queries have a specific printer defined when printed output is defined.  Before I got here, if they wanted to change the printer to which a query went, they modified the query itself.  Now, if that change needs to be made, I just code an OVRPRTF to QPQUPRFIL before the RUNQRY.  But I could go a step further and, instead of a straight OVRPRTF, I could put my own command in its place and, if the printer is having issues, send the output to a the substitution printer.

Ergo, the reason for wanting to know which queries output to a printer, rather than a database table.

Jerry C. Adams
IBM System i Programmer/Analyst
I love California.  I grew up in Phoenix. - Dan Quayle