× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



5.0.1 (Intl)|16
  July 1999) at 01/14/2000 01:16:00 PM,
        Serialize complete at 01/14/2000 01:16:00 PM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-midrange-l@midrange.com
Precedence: bulk
Reply-To: MIDRANGE-L@midrange.com
Errors-To: list-errors@midrange.com
X-List-Name: Midrange Systems Mailing List (MIDRANGE-L@midrange.com)

I fixed this problem.   First of all, there is a bug.  It is addressed by
PTF SF60638 for V4R3.  Unfortunately, this PTF does not make spool files
that are already "invisible" reappear, it just keeps it from happening to
new spool files.

To get rid of these job logs, I ran a WRKUSRJOB *ALL *OUTQ *PRINT.  I then
copied this spool file to a physical file, and ran a query over it to give
me an outfile with three fields - Job name, number and user.   I used this
outfile to place all of these files on hold, since when I found one of
these spool files and placed it on hold, it would reappear when doing
WRKOUTQ.

About 25,000 new spool files showed up in HLD status on QEZJOBLOG.  The
cleanup job worked appropriately and deleted the ones that were old. Total
jobs on our system dropped by about 25,000!

If you have a large system that is running reasonably close to maximum
jobs (do a DSPJOBTBL to see), you might want to see if this bug is
effecting you.  Check the server jobs (like QTGTELNETS) and see if there
are any very old instances out there.  If there are and if these jobs have
a job log in RDY status, see if you can see that job log when doing
WRKOUTQ.  You may want to do this to *PRINT if the QEZJOBLOG outq is
large.


Jeff Carey
Technical Specialist
AS/400 Technology
Transaction Processing Systems
DF5-1W





jeff_carey@baxter.com
Sent by: owner-midrange-l@midrange.com
01/11/00 02:09 PM
Please respond to MIDRANGE-L


         To:     MIDRANGE-L@midrange.com
         cc:
         Subject:        Mystery Spool Files


When looking at our old QTGTELNETS jobs, I noticed some old joblogs out
there from April and May.  They show as being in RDY status on
QUSRSYS/QEZJOBLOG.  From the work with jobs display, I can see them,
display them and delete then.

However, when I look at the outq QUSRSYS/QEZJOBLOG, I cannot find them.  I
even did a WRKOUTQ to a spooled file
(since we have many joblogs) and searched for them in the list.  They
don't show up.

What's worse, they shouldn't be there at all, since we have a job that
deletes old joblogs.

Is there some limit to how many records can be displayed in a given outq?


Jeff Carey
Technical Specialist
AS/400 Technology
Transaction Processing Systems
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.