|
Are you opening the printer file as user controlled? Otherwise if it's
already opened it may be a bit late to override it.
Have you tried displaying cmd in debug? Gut says it looks good though.
Unless one of your variables is wonky, such as output queue or it's
library.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com<http://www.dekko.com>
From: "a4g atl" <a4ginatl2@xxxxxxxxx<mailto:a4ginatl2@xxxxxxxxx>>
To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>
Date: 05/25/2018 01:28 PM
Subject: Problem with OVRPRTF in SQLRPGLE program
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>
Not sure which forum to post to but here's my problem.
I have embedded the following CL command in an RPG program. The program is
on our production system but it is called from our test box using
SBMRMTCMD.
The program works but the OVRPRTF seems to be ignored and definitely does
not work.
OVRPRTF BCLABELS OUTQ(*LIBL/LBOXTLDR) FORMTYPE(*STD) SECURE(*YES)
OPNSCOPE(*JOB)
Cmd = 'OVRPRTF ' + %trim(PRT_File) + ' OUTQ('
+ %trim(Prt_OutqL)
+ '/'
+ %trim(Label_Outq)
+ ') FORMTYPE(*STD) SECURE(*YES) OPNSCOPE(*JOB)';
CmdLen = %len(%trim(Cmd));
callp QcmdExc (Cmd : CmdLen );
I am monitoring the job in debug and the command is executed with no
errors. When I do a DSPJOB option 15, the OVRPRTF is not showing. Yes, I
have the correct job.
Anyone have any ideas on what the issue is?
TIA
Darryl Freinkel
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com<http://midrange.com> by shopping at amazon.com<http://amazon.com> with our affiliate
link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com<http://midrange.com> by shopping at amazon.com<http://amazon.com> with our affiliate
link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>
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.
midrange.com
