Re: CRTDUPOBJ and OVRPRTF command.

[Pete Hall <peteh@xxxxxxxxxx>]

At 02:33 PM 6/19/98 -0500, Rick Baird wrote:
>We are about to go thru a huge battery of tests on a huge number of
>program changes at one of our clients.  Our problem is that during
>these tests, a huge number of reports will be printed, all on
>production printers (because of ovrprtf commands throughout each job).
>
>Since our testing will be done during regular business hours, so all
>these extra reports may confuse the rank and file.  
>
>What I thought I could do was to create my own version of OVRPRTF that
>would ignore the "DEV" and "OUTQ" parameters, but process the others,
>and put it above QSYS during testing.
>
>I'm having trouble creating the CPP for the command though.
>
>Is there some way of knowing how and what parameters are passed to the
>regular CPP and in what order?  It doesn't seem to be working the way
>I thought.

Rick,

I'd go with the suggestion to create duplicate output queues in another library 
and include the library in your test library list if possible, but you could 
probably figure out the parameters by creating an RPG program with a bunch of 
256 byte parameters, and dumping it. The dump is a bit confusing, since the 
parameter data will overlap, but since you can control the data, too, it's not 
terribly difficult to figure out. Use things like "FILENAME" for the filename 
parameter. Do an F14 to get the formatted command string and print key it for 
reference.

You could also create your own version of the command, in which case you would 
know exactly what the parameters are, do your own processing and then execute 
QSYS/OVRPRTF.

You will need to watch the scope of the override in either case, since you will 
be at a higher invocation stack level than the application program intended. If 
you can figure out the parameters in the IBM command, a custom validity checker 
could be used that would allow you to adjust things and not disturb the 
invocation level. Don't modify the IBM command though. Make a copy of it and 
modify that.

hth
Pete



Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---