You don't require the job table to be cleaned up at each IPL. You can set
CHGIPLA CPRJOBTBL(*NONE) or even set it to *ABNORMAL so it doesn't do it
everytime you IPL, which seems excessive. At a few of our customers, we
have a job that runs every quarter that does a CHGIPLA CPRJOBTBL(*NEXT).
Then on the next IPL it compresses the job table, and then sets the value to
*NONE.
Pete Massiello
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Monday, April 21, 2008 11:39 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: IPL Job Table Cleanup
Is there a way to cleanup job tables prior to an IPL while the system is
running? I happen to be here to watch our IPL this past weekend when we
switched to long passwords and noticed that the Job Table Cleanup step was
the part of the IPL that took the longest (14 minutes). Is was wondering if
there might be way to do this cleanup task prior to an IPL so the IPL does
not take as long. I found a few documents (this one being the best
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/experience/ipla2.pdf
) about reducing the IPL time and some talked about how to reduce the number
of job table entries but the latest info was from 2004. Maybe something
newer in V5R4 or V6R1?
midrange.com
