-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There were a bunch of PTFs for V5R4 that addressed similar issues. We
had the same problem for a while, and installing the latest CUME seemed
to cure it. Apparently there were issues with releasing job resources.
While we were struggling with it, I found that running ENDJOBABN seemed
to finally make the job go away, although even that took quite a while.

Pete Hall
pbhall@xxxxxxxxxxxxx
http://pbhall.us


Paul Nelson wrote:
Did you end it with loglmt(0)?

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
James.Hawkins@xxxxxxxxxx
Sent: Saturday, October 06, 2007 12:30 PM
To: midrange-l@xxxxxxxxxxxx
Subject: SBS not ending

We have a subsystem (qmqm) that was issued an end *immed command at 8:45
this morning (via a scheduled job), at 1:15 the subsystem and associated
job are in a status of ending. Unfortunately this was configured by my
predecessor so I haven't looked into the how/why of the configuration. It
is set up with minimal job logging.

Why would this job and subsystem not end?

How can I get the subsystem and job to end? (ENDSBS *IMMED or *CNTRLD
and ENJOB *IMMED or *CNTRLD have been unsuccessful)


Any thoughts out there? (or is everyone doing what I wish I were doing
and watching college football? lol)

Thanks in Advance
- Jim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHB80LpcZsDl8OX6kRAqfWAJ9SMTUc+nuWZw/hju5UE4qLzrEmzgCgqDjF
h176b7Dd/4w5z/8YWBhAnSQ=
=W78m
-----END PGP SIGNATURE-----

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].