|
Hi Thomas,
There are a few different solutions mentioned by different people in this
post so I'm not sure which program you are asking to share - which fits
your need best?
My own program was written a long time ago and mostly just to clean up my
own spool.
I use it as described in my first response.
The parameters allow me to specify a user profile and an OUTQ but mostly I
let it default to my own profile and ALL out queues.
It runs fast. I'm in the habit of using it frequently throughout the day as
I work.
You mention that you are trying to clean up job log files but I'm not sure
what selection parameters you want to apply.
E.g User that created the spool or age of the spooled file?
Could you potentially just clear a single OUTQ?
The DLTSPLF command needs:
- Spooled File Name
- Spooled File Number
- Qualified Job Name (Name, User and Nbr)
Depending on what version of the OS you are on, this information is easily
retrievable via the DB2 Services as described in the above posts -
certainly easier to get at than using the QUSLSPL Api.
However when I tried to use the OUTPUT_QUEUE_ENTRIES view using selection
of only USER_NAME it was very slow.
This probably wouldn't matter to you if you were just running something in
a JOBSCDE overnight etc but it wouldn't work for me as I use my utility
frequently throughout the day to get rid of my spool from compiles and
joblogs etc.
My utility is not just a standalone program though, it requires a service
program I wrote to perform all of the user space processing - creating the
space, retrieving the standard header to find where the list starts etc.
What is your criteria for deleting the job logs (what selection parameters)
and when/how do you see it being used?
regards,
Craig
On Wed, 20 Mar 2019 at 21:25, Thomas Burrows <
thomas.burrows.1957@xxxxxxxxx>
wrote:
Could you share the program? Could send a gift card if that would help.them
On Wed, Mar 20, 2019 at 8:50 AM (WalzCraft) Jerry Forss <
JForss@xxxxxxxxxxxxx> wrote:
When I started here there were over 230,000 spool files on the system.
Nothing was ever cleaned up and no one knew how to figure out what was
there.
We had an incident where payroll spool files were left. Someone saw
fileand tried to get raise. Person no longer here.file
I wrote a spool manager that decides what should happen to each spool
the moment it is created. The processes include archiving it to the IFSis
(takes 10% of the space), emailing the report and deleting it. After it
in the IFS for say 90 days for job logs, it is deleted.
Now spool files are on the IBMi in that format for only a second.
The basics are CrtDtaQ and AddEnvVar to add entry to DtaQ when spool
Thomasis created. I have a pgm that monitors the DataQ.
Works extremely well here.
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
USERBurrows
Sent: Tuesday, March 19, 2019 4:49 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <
rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: help deleting spool files
When doing a DLTSPLF I cannot figure out a way to input the changing
characterDATA or JOB from the spool file information. I can give my six
privilegednumber a starting point and then increment. With a stopping point.
But how would I delete a mass of say joblogs that being dumped into a
spool file everyday to hold down on system space.
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
isinformation that is protected by law. The information contained herein
thistransmitted for the sole use of the intended recipient(s) and should"only"
pertain to "WalzCraft" company matters. If you are not the intendedare
recipient or designated agent of the recipient of such information, you
hereby notified that any use, dissemination, copying or retention of
mayemail or the information contained herein is strictly prohibited and
receivedsubject you to penalties under federal and/or state law. If you
permanentlythis email in error, please notify the sender immediately and
--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
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.