× 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.



What type of job is it, what subsystem is it running in, is it a Autostart
job or prestart job.

On Tue, Feb 22, 2011 at 8:19 AM, <rob@xxxxxxxxx> wrote:

Did you wait 10 minutes after ENDJOB before trying ENDJOBABN?

A simple posting of WRKPTFGRP is a start on ptf levels.

User job or system job?

You're on 6.1 so I am going to go out on a limb here and guess that you
are current on maintenance. Anything that came even close to requiring an
IPL I would be on the phone with IBM asking for resolution.

Don't even want to take that time because there's an angry mob outside
your door with pitchforks and torches? Then, at the minimum run
DSPJOB OUTPUT(*PRINT) JOB(...)
DSPJOBLOG JOB(...) OUTPUT(*PRINT)
STRSRVJOB JOB(...)
TRCJOB SET(*ON)
wait 2 minutes or so
TRCJOB SET(*OFF)
DMPJOB
which for a session that I just signed on and ran the command
generated a 3,668 page spool file
ENDSRVJOB
DSPPTF OUTPUT(*PRINT)
WRKPTFGRP <F6> to print
WRKACTJOB SBS(offending subsystem) OUTPUT(*PRINT)
WRKSYSSTS then F3 out of it (done only to start statistics)
WRKSYSSTS OUTPUT(*PRINT)
Write down the job name, user and number of the 5250 job which ran these
commands.
Then after your IPL connect back in with iNav, go into printer output and
use View to subset it to just that job you wrote down. Drag these spool
files into a folder on your PC. Zip them all together. Use the website
to open a pmr and attach this zip file.

I still recommend calling IBM first because it may then be that a trip
into SST to trace a few things may have been the ticket.

PMR website:
http://www.ibm.com/support/servicerequest

What PTF groups are out there
http://www-912.ibm.com/s_dir/sline003.NSF/GroupPTFs?OpenView&view=GroupPTFs

What cume is currently out?
http://www-912.ibm.com/s_dir/sline003.nsf/ALLPSPBYREL


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Åke Olsson <ake.olsson@xxxxxx>
To: " (midrange-l@xxxxxxxxxxxx)" <midrange-l@xxxxxxxxxxxx>
Date: 02/22/2011 02:33 AM
Subject: "Undead" Jobs
Sent by: midrange-l-bounces@xxxxxxxxxxxx



On a few occasions we have seen this happening in a batch subsystem (one
of many sbs on machine):


A job starts using way to much resources and needs to be put out of its
misery.
We try killing the job *immed.
It still stays on - forever - using up constantly around 30% of the CPU on
A 570 box.
Trying to use endjobabn does not help.
The subsystem cannot be stopped.
The "undead" job cannot be held or changed in any other way.

One peculiar thing about these "undead" jobs is that they show no program
stack despite the fact that they use both i/o (loads of open files) and
CPU.

The only solution seems to be to IPL the system, which is highly impopular
with the users.

The box is on V6R1. As for PTF level I do not know. I simply assume that
the sysadmins do their job with regards to installing critical and cum
ptf:s.

Any ideas? Does this ring a bell?

Med vänlig hälsning / Best regards

Åke H Olsson
[Description: cid:image001.png@01CA1FE6.387A03A0]
Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11
phone: +46 (0)36 342976 mobile: +46 (0)705 482976 fax: +46 (0)36 34 29
29
ake.olsson@xxxxxx<mailto:ake.olsson@xxxxxx> www.pdb.se




This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.--
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.


--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.