If I'm understanding correctly, I have done this many times, no overrides needed.
In the RPG program writing the report:
1) Manually open the printer file (USROPN) on the first call
2) Do not turn on LR after each of the 25k calls to this pgm, just do a return
3) When finished, call the pgm one final time w/ a parm to signal it to close the files by turning on LR.
Ron
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert via MIDRANGE-L
Sent: Monday, August 9, 2021 7:08 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Holding a print file open for an entire job
I've gotten past the DSPLY output problem; it seems that I'd done a "puts()" version of the program sometime last year.
Unfortunately the program would get called 25k times, and in tests, I get a new spool file for each invocation.
I vaguely recall doing *something* in the past, to hold a print file open and keep that from happening, but I can recall neither the circumstances nor the solution. It might have involved either OPNF or OVRPRTF.
I feel like a complete idiot this afternoon.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
