× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I agree, that's the hammer that I've used for these problems in the past.
For academic purposes, I'm trying to understand why the OUTQ setting on a
user profile should prevent my attempt to override OUTQ for this program.
It appears that if the job's OUTQ attribute is not *DEV, then overrides to
OUTQ are not applied. ??!  I'm missing something here.  

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Michael Naughton [mailto:mnaughton@juddwire.com]
Sent: Wednesday, January 15, 2003 12:11 PM
To: midrange-l@midrange.com
Subject: Re: Wierd behavior on OVRPRTF


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

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.