|
Hey, but wasn't it cool that iNav helped you peg that right away?http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/99
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
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 thisshould
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
say something like 1-14 of 2214. And that matches my WRKSYSACT "Jobs inon
System".
Remember, WRKACTJOB has it's own definition of "Active". Read the help
the title bar. Also read the help on F14.
Rob Berendt
--
value
"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
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
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.
midrange.com
