What I do is a more global process of handling spool files.
When ANY spool file is created an entry is put into a dataq. There is an exception for job logs but I handle that.
I have a pgm that monitors the dataq and decides what to do with it.
This includes moving it to a specific outq, converting to a PDF, emailing or deleting.
For example, all queries are converted to PDF and emailed to the user that created it.
It can handle spool files by a specific user/outq or regardless of it.
On generic spool files like QSYSPRT, I interrogate the contents of the spool file to determine anything special about it.
In the end, if I am unable to determine what to do with it, it just sits where it is.
Most spool files reside on the system for only a few seconds.
In your case the spool file could be converted to PDF and email or archived in the IFS.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Wednesday, June 19, 2024 9:33 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: External Re: Question about redirecting spooled output
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi, Michael,
That is very clever. The main "gotcha" is the requirement for the users to be enrolled in the system directory. Nowadays, since many shops no longer use SNADS, this could become an issue.
You may also want to try the (newer) SNDTCPSPLF command, vis:
SNDTCPSPLF RMTSYS(LOCALHOST) PRTQ('yourlib/youroutq') FILE(A) + DESTTYP(*AS400) TRANSFORM(*NO) SEPPAGE(*NO)
Note the use of "localhost" to send the spool file to a user on the same system. There are other optional parameters available.
All the best,
Mark S. Waterbury
On Wednesday, June 19, 2024 at 10:03:15 PM EDT, Michael Quigley <michaelquigley@xxxxxxxxxx> wrote:
I don't know if some else already put this out there, but I think the best bet would be to try using the SNDNETSPLF command once the spoolfile is generated.
Michael Quigley
Computer Services
The Way international
www.TheWay.org
-----Original Message-----
message: 2
date: Tue, 18 Jun 2024 20:34:10 +0000
from: Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
subject: RE: Question about redirecting spooled output
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?
--
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.
--
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.
Subject to Change Notice:
WalzCraft reserves the right to improve designs, and to change specifications without notice.
Confidentiality Notice:
This message and any attachments may contain confidential and privileged information that is protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s) and should "only" pertain to "WalzCraft" company matters. If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this email or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this email in error, please notify the sender immediately and permanently delete this email. Thank You
WalzCraft PO Box 1748 La Crosse, WI, 54602-1748
www.walzcraft.com<
http://www.walzcraft.com> Phone: 1-800-237-1326
midrange.com
