RE: jobs in the system count-update

["Ketzes, Larry" <Larry.Ketzes@xxxxxxx>]

Interesting parameter.  Is there any reason NOT to clear incomplete joblogs
other that trying to troubleshoot a specific problem for a short period of
time?  Sounds to me like a default value that should be changed.

Thanks, Larry


Larry Ketzes
iSeries Senior Systems Administrator
American Life Insurance Company
One ALICO Plaza
600 King Street
Wilmington, DE 19801
Phone: 302-594-2146
Mobile: 302-559-1631
Fax: 302-830-4524
Email: larry.ketzes@xxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Tuesday, May 01, 2007 7:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: jobs in the system count-update

Changing the Ipl attribute:  Clear incomplete joblogs . . . .   *YES
and an ipl at 5am cleared the problems. All the jobs in job table
in status "ended", no job log, and cannot create a job log because it's 
ended,
were removed. Job table went from over 9000
to 2400 (which is normal). Note that all ended jobs with any output on
the system still remain, as they should.
Since system value for job logs is still *jobend, it seems like IBM
has a problem here, where your system table can accumulate thousands of
jobs that have ended, and will never produce a job log, but must have
some flag indicating it should.
jim franz

----- Original Message ----- 
From: <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, April 30, 2007 1:16 PM
Subject: Re: jobs in the system count


> Hey, but wasn't it cool that iNav helped you peg that right away?
>
> Rob Berendt
> rob@xxxxxxxxx
> Subject
> Re: jobs in the system count
>
> My "guess" is that a cold start IPL is a
> pwrdwnsys *immed restart(*NO)
> With emphasis on the restart(*NO).
> Followed by a push the button start.
>
> Rob Berendt
> -- 
> "Jim Franz" <franz400@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 04/30/2007 12:37 PM
> Subject
> Re: jobs in the system count
> The iNav view showing me many interactive jobs in status "ended" with no
> job
> log - detailed status = 'Ended - Device Error' - going back over a year.
> Same also for many writer jobs that ended abnormal.
> All have no job log, and in the Job Log tab and then click "job log", they
> show 'CPF2443 Job log not displayed or listed because job has ended'.
> Only problem is it still lists in Jobs In the System....
>
> The DSPJOBTBL cmd confirms this.
> So what happens when an ending job is supposed to produce a job log, but
> the job ends before job log produced??? Looks like it's stuck in the job
> table.
>
> Reading the doc Primer on Work Control Block Tables
http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/99
0f4112f46be48b86256b1e0073fabe?OpenDocument
> is helpful, but did not understand the reference to a cold start ipl that
> rebuilds the job table.
> I do see on ipl attributes the option to Clear Incomplete Job Logs.
> Will set that and ipl overnight and check this tomorrow.
> Did a 5 minute scan of ptfs and didn't see anything that clearly resolves
> this,
> but perhaps this ipl attribute is the fix?
> jim franz
>
> ----- Original Message ----- 
> From: <rob@xxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Monday, April 30, 2007 11:32 AM
> Subject: Re: jobs in the system count
>
>
> > Have you tried using iNav?  Basic Operations, Jobs, View, Customize this
> > View, Include.  Change user to all.  Make sure all three boxes in Status
> > are checked.  Basically, if it wants something typed in it, have it say
> > ALL.  If it can be checked, check it.  Bottom status line of result
> should
> > say something like 1-14 of 2214.  And that matches my WRKSYSACT "Jobs in
> > System".
> >
> > Remember, WRKACTJOB has it's own definition of "Active".  Read the help
> on
> > the title bar.  Also read the help on F14.
> >
> > Rob Berendt
> > -- 
>
> > "Jim Franz" <franz400@xxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 04/30/2007 11:04 AM
> >
> > Subject
> > Re: jobs in the system count
> > Rob - appreciate the response.
> > Jobq's are empty.
> > QLOGOUTPUT is *jobend
> > System not having any performance problem.
> > jim
> >
> > ----- Original Message ----- 
> > From: <rob@xxxxxxxxx>
> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> > Sent: Monday, April 30, 2007 10:48 AM
> > Subject: Re: jobs in the system count
> >
> >
> > > It is possible for jobs to end, not have any spool files, and still be
> > > there.  More likely in V5R4.  Especially if you set the new system
> value
> > > QLOGOUTPUT to *PND.
> > >
> > > Also, according to the help on "Jobs in System", you should also check
> > > o  All jobs on job queues waiting to be processed.
> > >
> > > Rob Berendt
> > > -- 
> > >
> > > "Jim Franz" <franz400@xxxxxxxxxxxx>
> > > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > > 04/30/2007 10:32 AM
> > > Subject
> > > jobs in the system count
>
> > > On the WRKSYSSTS screen the 'Jobs in the system' line says 9017.
> > > If I add up all the spooled files in outqs, there are 5400 and the
> > > WRKACTJOB says 238 active jobs (which is normal).
> > > About 20 user on, plus Apache web server.
> > > WRKSYSACT is nearly empty.
> > > So what else could make up the other 3000 or so jobs?
> > > Last ipl was Sat morning.
> > > i5 520 V5R4
> > > We did log an extended (hours) script attack (unsuccessful) at our ftp
> > > server
> > > over the weekend, but that is not unusual.
> > > jim franz