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



Thanks a lot Jim for the reply.
Let me explain things more ..
 
PRG65 is an PRG program and PRG66 is an RPGLE Program.
So the activaition comes into picture only with PRG66 which runs in the Default 
activation group i.e., *DFTACTGRP...
still do u feel that this will make any influence on this issue?.
 
Also, Since the override gets executed via QCMDEXEC, any special authority 
lacking could cause these problems??
 
I couldnt find out the direction of the solution for this issue so far..
 
Thanks
Siva


Jim Franz <franz400@xxxxxxxxxxxx> wrote:
I am assuming that the print file in PRG66 is "PRT1", otherwise the override
is
useless. If it is PRT1, my next question is if there is a difference between
PRG65 and
PRG66 in the activation group they run in? I cannot explain why (but I know
some
on this list can), but I have found that when I had in one clp an ovrprtf
before a SQLRPGLE with a report followed by an ovrprtf before a RPGIII
report (both using print file qsysprt), I had to delete the current override
after the SQLRPGLE, and then do the override for 2nd pgm. Both pgms compiled
with v5r2 compiler defaults. So I would add a "DLTOVR PRT1" before the
ovrprtf before calling PRG66.
hth
jim

----- Original Message ----- 
From: "AS400 MAILS" 
To: "Midrange Systems Technical Discussion" 
Sent: Sunday, April 10, 2005 4:43 AM
Subject: Re: Issue in OVRPRTF...


> Sorry... the program actually conatins a call to QCMDEXEC after the
RTVDTAARA from DA2... I only forgot to mention that in my earlier post... In
general QCMDEXEC was called before the call made to any report generation
program.
>
> Even after the override pf PRT1 gets executed coreclty, the problem
generates only one copy in the printer
> .
> Please see the correct code below...
>
> RTVDTAARA DTAARA(DA1) RTNVAR(&VAR1)
> >
> > /* DA1 Contains the command : OVRPRTF
> > FILE(LIB1/PRT1) + */
> >
> > /* COPIES(1) SAVE(*YES) OUTQ(OUTPUT1) */
> >
> > CALL PGM(QCMDEXEC) PARM(&VAR1 90)
> >
> > Call PGM(PRG65) /* call to PRG65 to generate a
> > Report PRT1*/.
> >
> >
> > RTVDTAARA DTAARA(DA2) RTNVAR(&VAR1)
> >
> > /* DA1 Contains the command : OVRPRTF
> > FILE(LIB1/PRT1) + */
> >
> > /* COPIES(2) SAVE(*YES) OUTQ(OUTPUT1) */
> >
> > CALL PGM(QCMDEXEC) PARM(&VAR1 90)
>
> > Call PGM(PRG66) /* call to PRG66 to generate a
> > Report PRT1 .
>
> Thanks
> Siva.
>
> Jeffrey Young wrote:
> Siva,
> The CL programyou have in your message is missing a
> call to QCMDEXC after the second RTVDTAARA.
> That is why the next program is not seeing the
> override.
>
> Jeff Young
>
> --- AS400 MAILS wrote:
> > Hi
> >
> > I ma having a CLP program as like below which is
> > submitted as a batch. It calls PRG1, PRG2, PRG3,
> > ..... PRG100 to genearte 100 reports.
> > In one point in the program, consier a below code..
> >
> > RTVDTAARA DTAARA(DA1) RTNVAR(&VAR1)
> >
> > /* DA1 Contains the command : OVRPRTF
> > FILE(LIB1/PRT1) + */
> >
> > /* COPIES(1) SAVE(*YES) OUTQ(OUTPUT1) */
> >
> > CALL PGM(QCMDEXEC) PARM(&VAR1 90)
> >
> > Call PGM(PRG65) /* call to PRG65 to generate a
> > Report PRT1*/.
> >
> >
> > RTVDTAARA DTAARA(DA2) RTNVAR(&VAR1)
> >
> > /* DA1 Contains the command : OVRPRTF
> > FILE(LIB1/PRT1) + */
> >
> > /* COPIES(2) SAVE(*YES) OUTQ(OUTPUT1) */
> >
> >
> >
> > Call PGM(PRG66) /* call to PRG66 to generate a
> > Report PRT1 .
> >
> >
> >
> > The problem is PRG66 is not printing two copies of
> > PRT1. Able to get only one
> >
> > copy of PRT1. The override done using the second
> > statement is not getting
> >
> > reflected while calling the program PRG66..
> >
> >
> >
> > Any idea why this happen. Any general Override done
> > will skip this?.
> >
> > The printer file PRT1 gets overridden with differnt
> > COPIES and OUTQ values in
> >
> > various places in the program ( from calling PRG1 to
> > PRG64 and alos after PRG66)
> >
> > Anyone has faced similr issue like this?
> >
> >
> >
> >
> >
> > Thanks
> >
> > Siva
> >
> >
> >
> >
> > ---------------------------------
> > Do you Yahoo!?
> > Yahoo! Small Business - Try our new resources site!
> >
> > -- 
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> >
> http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the
> > archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - Find what you need with new enhanced search. Learn more.
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


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


                
---------------------------------
Do you Yahoo!?
 Yahoo! Small Business - Try our new resources site! 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.