Re: jobs in the system count-update -- MIDRANGE-L

Jim -

I would suggest that if not already done that your customer set up the interactive users that come in from the Terminal Server machine to all be running in the same interactive subsystem.

Then, if it is necessary to reboot the terminal server, end the subsystem BEFORE rebooting the terminal server to end the interactive jobs in a more controlled fashion.

This will keep those interactive job entries from being hung in the system job table...

- Steve

----- Original Message ----- From: "Jim Franz" <franz400@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, May 01, 2007 4:41 PM
Subject: Re: jobs in the system count-update

<Rob wrote..You stated device errors and spool file errors was a cause.

Fact or hypothesis?

Earlier i wrote>
The iNav view showing me many interactive jobs in status "ended" with
no joblog - 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. </quote>

Rob - it's hard to say where would show in dspsyssts - my ipl with the ipl
attribute to Clear Incomplete Joblogs removed the jobs from the table.
This customer site has many users on a Terminal Server, & I know they
sometimes have to reboot it during prime time so all interactive jobs
suddenly have a device error. I imagine this is all the Device Errors. The
spool errors were actually writer errors & I didn't get the error text, but
same CPF2443 msg.
I do think what led me to this problem, that my total #spools plus
#active jobs plus jobs in queue was less than total jobs in the system.
Ended jobs with output may have multiple spools on disk so it will not
be "equal". But Total Jobs should not be more. It helped also that I
dug into the problem just after an ipl.
jim franz

----- Original Message ----- From: <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, May 01, 2007 4:44 PM
Subject: Re: jobs in the system count-update

I think the underlying situation is to find out why your jobs are ending
this way. You stated device errors and spool file errors was a cause.
Fact or hypothesis?

Here's something else. Instead of WRKSYSSTS, try DSPSYSSTS. Make sure
that you use F21 to select Basic mode. If you still have any of these
phantom jobs, where do they appear?

On my system,
DSPSYSSTS ASTLVL(*INTERMED) shows
Jobs in system . . . . . : 41370
DSPSYSSTS ASTLVL(*BASIC) shows
Users:
Signed on . . . . . . . . . . . . . . . . . . . . . . . : 330
Temporarily signed off . . . . . . . . . . . . . . . . . : 0
Suspended by system request or group jobs . . . . . . . : 1
Signed off with printer output waiting to print . . . . : 3622

Batch jobs:
Waiting for messages . . . . . . . . . . . . . . . . . . : 0
Running . . . . . . . . . . . . . . . . . . . . . . . . : 729
Held while running . . . . . . . . . . . . . . . . . . . : 0
Ending . . . . . . . . . . . . . . . . . . . . . . . . . : 0
Waiting to run/Scheduled . . . . . . . . . . . . . . . . : 1
Held on job queue . . . . . . . . . . . . . . . . . . . : 0
Waiting on held job queue . . . . . . . . . . . . . . . : 0
Waiting on not assigned job queue . . . . . . . . . . . : 0
Ended with printer output waiting to print . . . . . . . : 35658

I too, would like to know if I have these phantom jobs. We purge any
spool file over 90 days old - no exceptions.

Rob Berendt
--

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.