I've seen it Justin. More than once.
But it's not every time I apply PTFs. Just sometimes.
On Tue, Jun 17, 2014 at 1:52 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:
This has been a persistent annoyance since we went to 7.1. I figured
someone else must have seen it and maybe knew the fix.
I'll try the OVRPRTF next month.
From: CRPence [mailto:CRPbottle@xxxxxxxxx]
Sent: Tuesday, June 17, 2014 11:37 AM
Subject: Re: REQUESTROL print-out from PTF's
On 16-Jun-2014 14:34 -0500, Justin Taylor wrote:
Every time I put on PTFs, the system printer prints a "Run SQL
Statements REQUESTROL" document. Any way to force that to be on hold?
No mention of which job actually produced the /document/, but if that
printed data was produced within the job performing the PTF activity, then
precede that PTF activity with the following request to force the spooling
of the data into a Spool File (SPLF) with the HELD status:
OVRPRTF *PRTF HOLD(*YES) OUTQ(QPRINTS) SAVE(*YES) OVRSCOPE(*JOB)
Then after that PTF activity completes, look for the spooled file, and
gather the Work With Spooled File Attributes (WRKSPLFA) details.
Those details can be used to determine how to effect the necessary
change(s) either with a Change Printer File (CHGPRTF) request or a more
specific\directed Override to Printer File (OVRPRTF) request [than to every
printer file per the *PRTF specification used originally], to affect just
that one printer file.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives