|
HHHMMMMM - your right. I dont know what I was thinking of, but I swore there were some spools that had been printed, now with a status of HLD. "I'm going mad I tell you. Mad" .... Pink Floyd - Dark Side of the moon. I cant believe its going to be that simple. Thanks for pointing this out. >>> "Carsten Flensburg" <flensburg@novasol.dk> 07/09/02 11:36AM >>> Alan, How would a spool file enter the HLD status after being successfully written? Best regards, Carsten Flensburg ----- Original Message ----- From: "alan shore" <SHOREA@dime.com> To: <midrange-l@midrange.com> Sent: Tuesday, July 09, 2002 4:41 PM Subject: Re: spool file status > Thanks for your reply. > I thought of that also, however, we are getting numerous spool files that have a status of HLD, and remain that way even after printing as well as before, but thanks for replying. > > >>> "Carsten Flensburg" <flensburg@novasol.dk> 07/08/02 05:27PM >>> > Hello Alan, > > If you do not want to delete spool files that hasn't been printed it should > be safe to delete only those having the status SAV. There are a number of > intermediate statuses but eventually a spool file - that has been printed - > will end up as either SAV (saved) or FIN (finished and deleted). > > Best regards, > Carsten Flensburg > > ----- Original Message ----- > From: "alan shore" <SHOREA@dime.com> > To: "<" <midrange-l@midrange.com> > Sent: Monday, July 08, 2002 10:54 PM > Subject: spool file status > > > > I'm trying to develop something to automatically delete old spool files (I > know DLTOLDSPLF resides in TAATOOL), but the spool file CANNOT be deleted if > it has'nt been printed. > > I know the commans WRKSPLSTS(?) (work with spool status) will display if > the spool has been printed, but this is a display of the data. > > I looked at the QUSRSPLA API, but this does not show if a spool has been > printed, and I cannot seem to locate the OS/400 Print API manual on the 'net > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.