|
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
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.