Re: Question about redirecting spooled output

I believe you can declare the file as USROPN. Execute the OVRPRTF command
before you open it and see if it gets created with your user profile when
you open the file and start writing output to it.

I think it should work, unless of course there are security limitations.

HTH

JS

El mar, 18 jun 2024 a las 14:34, Dan Bale (<dan.bale@xxxxxxxxxxxxxxxxxxxxx>)
escribió:

Do you mean something like:
OVRPRTF FILE(QPRINT) OUTQ(QUSRSYS/BALEOUT)
where BALEOUT is my personal outq.

Not sure if it's possible to change the owner of the spool file to you.
OVRPRTF has a SPLFOWN parameter, but you can't assign your own personal
profile to it. If you are trying to keep the user running the job from
viewing the spool file, you may be able to do that via authorities on the
outq you override to (per above).

Dan Bale

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
James H. H. Lampert via MIDRANGE-L
Sent: Tuesday, June 18, 2024 3:10 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Question about redirecting spooled output

EXTERNAL: This email originated from outside of the organization. Do not
click on any links or open any attachments unless you trust the sender and
know the content is safe.

I have an RPG program that generates spooled output. The F-spec looks like

FQPRINT O F 132 PRINTER

The job in which this runs is under an entirely different user profile,
and the spool file goes to QUSRSYS/PRT01.

On this particular system, QUSRSYS/PRT01 gets purged on a daily basis.

I'm pretty sure this can be sent to another queue with an OVRPRTF,
although I'm not entirely sure how (or what queue).

But is there also an easy way to have it spooled to me, rather than to the
user profile under which the job runs?

*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of the
recipients named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please return
it to the sender immediately and delete the original message and any copy
of it from your computer system. If you have any questions concerning this
message, please contact the sender. ***
--
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.