Re: Wierd behavior on OVRPRTF

["Michael Naughton" <mnaughton@xxxxxxxxxxxx>]

Eric,

IMNAE (I am not an expert), but this seems as if it should work. I've been
bitten by print file overrides in ILE programs, though, and I've always
been able to eliminate them by adding an OVRSCOPE(*JOB) to the override
(and then -- of course -- deleting the override when I'm finished with it).

hth

midrange-l@midrange.com writes:
>One of our programmers asked me to help with a problem involving outq
>overrides.  PGM_A prompts for invoice number, issues an OVRPRTF via
>QCMDEXC,
>then calles PGM_B which prints the invoice.  All works as expected UNLESS
>the user profile that calls PGM_A  has a default OUTQ defined.  In this
>case, the override does not seems to "stick", and the output is created in
>the wrong outq.  
>
>Some specifics:
>V4R4
>ILE (PGM_A Actgrp(*New), PGM_B Actgrp(*Caller))
>Print file >> QPRINT program described (O spec)
>Override being issued: OVRPRTF FILE(QPRINT) OUTQ(ARINVPRT)
>
>We got around the problem by creating QPRINTINV which targets the static
>outq that is needed.  No override needed now.  That's fine, but I'd like
>to
>know why an OVRPRTF failed for jobs having a default OUTQ.  It does not
>seem
>to be related to OVRSCOPE issues, since it works correctly when the job's
>OUTQ is *DEV.  Any ideas?  
>
>tia,
>
>Eric DeLong
>Sally Beauty Company
>MIS-Project Manager (BSG)
>940-898-7863 or ext. 1863


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com