Re: Multiple programs printing to 1 spool file.

On 24 Jan 2013 13:40, Jeff Young wrote:

<<SNIP>> using the Share(*YES) on OVRPRTF.
You would need to ensure that each program in the stack did not
close the print file before calling the next one down, and all
programs would need to use the same print file name.

On Thu, Jan 24, 2013 at 4:38 PM, Horn, Jim wrote:

In an RPG and or CL can you override a print file to something
open the spool or ?
call several programs adding to the spool close the spool?

With program-described printer files declared for both the original ODP and the other openers, I have done that.

If the first open has the open-scope defined and does not close before each other shared open occurs, then each later requester of a shared open can close their [shared] open; leaving the original Open Data Path active to be shared again. Properly scoped overrides can even handle multiple file names referred to by the shared openers; i.e. if the "several programs" already exist and open\close particular printer files, they can be induced to write into an existing ODP by using sharing.