|
midrange.com
Hi Venu,
we wrote a CL that are called from a BPCS menu, which solved all our
Query/400 PRTF problems (Keep it Simple: don't change where it is not
necessary). Here is the code:
PGM
MONMSG MSGID(CPF0000)
OVRPRTF FILE(QPQUPRFIL) SECURE(*YES) OVRSCOPE(*CALLLVL)
WRKQRY
DLTOVR FILE(QPQUPRFIL) LVL(*)
RETURN
ENDPGM
I hope this helps
---------------------------------------------------------------------------
Roland Strauss
Clover - CIS (AA Team)
Tel: +27 11 758 5408
Fax: +27 11 758 5300
Cell: +27 84 764 3406
e-Mail (1): roland.strauss@xxxxxxxxxxxx
e-Mail (2): roland.strauss@xxxxxxxxxxx
Web (1): http://www.clover.co.za
Web (2): http://roland.jislaaik.com
---------------------------------------------------------------------------
"There is a vast difference between knowledge and expertise. Knowledge lets
you deduce the right thing to do; expertise makes the right thing a reflex,
hardly requiring conscious thought at all."
Venu Gopal
<vgopal@haynesint
l.com> To
Sent by: bpcs-l@xxxxxxxxxxxx
bpcs-l-bounces+ro cc
land.strauss=clov
er.co.za@midrange Subject
.com [BPCS-L] Problems with WRKQRY
command Invoked from BPCS Menu
2005/08/16 04:19
PM
Please respond to
"SSA's BPCS ERP
System"
<bpcs-l@midrange.
com>
Hello Everybody,
I am trying to eliminate the need for BPCS end-users to access the
WRKQRY command from the iSeries (AS/400) command-line. I need to have
their AS/400 user profiles set so that 'Limit Capabilities' is set to
'*YES'. For this I created a custom CL program that simply has WRKQRY
command in it. I stuck this CL program in a general purpose BPCS menu
that is available to all BPCS end users. However, when they access their
queries through the menu option that I set up, their reports are all
messed up. The outputs get truncated sometimes, or their run-time print
settings (such as specific printer to print to) that they specify in the
query itself at run-time is not honoured. I called up IBM software
help-desk and reported the problem. Based on their suggestion, I sent
them trace and debug logs by invoking WRKQRY both ways (i.e. via command
line and via BPCS menu). The job log showed the following override
command that was in the standard BPCS CL program:
-----------------------------------------------------------------------------------------------------------------------------
OVRPRTF FILE(*PRTF) PAGESIZE(66) LPI(6) CPI(10)
OVRFLW(59) OUTQ(BPCSUSR64/BPCSOUTQ) FORMTYPE('*STD')
COPIES(01)
SCHEDULE(*FILEEND) HOLD('*YES') SAVE('*NO') OUTPTY('5')
-----------------------------------------------------------------------------------------------------------------------------
Apparently, this override was messing up the WRKQRY settings when
invoked via BPCS menu. Hence I added the DLTOVR FILE (*PRTF) command in
my CL program just before the WRKQRY command and then tested it.
However, it did not seem to make a difference. Any ideas, anybody?
Thanks in Advance!
S.R. VenuGopal,
Programming Manager,
Information Technology,
Haynes International, Inc,
Phone: (765) 456-6770
E-mail: vgopal@xxxxxxxxxxxxxx
--
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
Delivered-To: roland.strauss@xxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.
