OK so in this case they are still all going to OutqB.
Where should I put the SECURE?
the first cl:
 
 OVRPRTF    FILE(REPORT) PRTTXT(BLANK) OUTQ(OutqA) +      
              FORMTYPE(INV) HOLD(*YES) SAVE(*YES) +      
              OVRSCOPE(*CALLLVL)                            

 CALL       PGM(ProgramA) /* PRINT A */ 
                            
                                                     
 DLTOVR *ALL                                               
 CALL PGM(ProgramB)
 
ENDPGM
 
 
(CL)   ProgramB:
 
   DLTOVR     FILE(*ALL)                                 
   OVRPRTF    FILE(REPORT) PRTTXT(BLANK) OUTQ(OutqB) +  
                FORMTYPE(INV) HOLD(*YES) SAVE(*YES) +  
                OUTPTY(1) OVRSCOPE(*JOB)                  
               
Call PGM(ProgramB)

--- On Thu, 9/11/08, Terrence Enger <tenger@xxxxxxxxxxxxxxxx> wrote:

From: Terrence Enger <tenger@xxxxxxxxxxxxxxxx>
Subject: Re: Problem with ovrprtf
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Thursday, September 11, 2008, 9:13 PM

On Thu, 2008-09-11 at 14:54 -0500, John McKee wrote:
After rpgprogramA completes, DLTOVR printer_file_name

I am wondering if you are also including on the first OVRPRTF
SECURE(*YES). Doing that stops the override in program B from having
any effect.

Sorry, John, but I think it is the other way around, so to speak: it is
the (implicit) SECURE(*NO) on the the override in program B which makes
the override in program B ineffective. Consider ...

Outer program ...

pgm

/* three overrides, only the last one secure(*yes) */
ovrprtf one outq( a_outer )
ovrprtf two outq( b_outer )
ovrprtf three outq( c_outer ) secure(*yes)

/* call inner program */
call aa4382

endpgm

inner program ...

pgm

/* three overrides, only the second one secure(*yes) */
ovrprtf one outq( a_inner )
ovrprtf two outq( b_inner ) secure(*yes)
ovrprtf three outq( c_inner )

/* show results */
dspovr

endpgm

and screen images ...

Display All Merged File Overrides
Call level . . . . . . . . . . . : *
Type options, press Enter.
5=Display override details 8=Display contributing file overrides
Opt File Type Keyword Specifications
THREE PRT OUTQ(*LIBL/C_OUTER) SECURE(*YES)
TWO PRT OUTQ(*LIBL/B_INNER) SECURE(*YES)
ONE PRT OUTQ(*LIBL/A_OUTER)

Display Contributing File Overrides
File . . . . . . . . . . . . . . : THREE
Call level . . . . . . . . . . . : *
Type options, press Enter.
5=Display override details
Opt Level Type Keyword Specifications
7 PRT OUTQ(*LIBL/C_INNER)
6 PRT OUTQ(*LIBL/C_OUTER) SECURE(*YES)


Display Contributing File Overrides
File . . . . . . . . . . . . . . : TWO
Call level . . . . . . . . . . . : *
Type options, press Enter.
5=Display override details
Opt Level Type Keyword Specifications
7 PRT OUTQ(*LIBL/B_INNER) SECURE(*YES)

Display Contributing File Overrides
File . . . . . . . . . . . . . . : ONE
Call level . . . . . . . . . . . : *
Type options, press Enter.
5=Display override details
Opt Level Type Keyword Specifications
7 PRT OUTQ(*LIBL/A_INNER)
6 PRT OUTQ(*LIBL/A_OUTER)

hth,
Terry.

John McKee

Quoting Adam West <adamster@xxxxxxxxx>:

I have CL program-A,
pgm
program-A.

Overprtf outq(A)
Call rpgprogramA




Call program-B ( a CL PROGRAM)

Endpgm



This is program-B
pgm
Overprtf outq(B)
Call rpgprogramB
endpgm
BUT the outq of the second CL goes to the first outq - outq A

I need them to split. I have played around with the Ovrscope
parameter but then when I make that *job or *Calllvl, the both
outputs go to Outq B.

WHat am I missing to have them split off?




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