I think ENDJOBABN might cause you more problems than it solves. As I
recall, after any ENDJOBABN, the system will not process a normal IPL.
Rob has beat this one senseless in numerous threads, so it might be a
good idea to scan the archives for more info.
QZLSFILE is used by IBM NetServer. There is one of these for each
client that is connecting to an IFS share. It sounds to me like you
have an external job that is holding a lock on a file in the IFS share.
Can you review that job to see if you can identify the client that is
holding this connection? I think someone had open source utility that
would show IFS locks... Maybe Bryan Dietz?
Hth,
Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Salter, James
Sent: Monday, December 15, 2008 9:31 AM
To: midrange-l@xxxxxxxxxxxx
Subject: ENDSBS *ALL *IMMED jobs not ending
Has anyone else had any situations where not all jobs were ended as a
result of an ENDBS *ALL *IMMED?
Over the years, there have been several instances where there was a
straggler job that wouldn't end.
Well, our weekly backups start after the system has been taken down in a
restricted state, so these problems just cause a lot of problems.
I am thinking about writing a CL that I can put on the job scheduler to
run about 20 minutes or so prior to the regular weekly backups.
Within the job, if I do not get a good shutdown after a few minutes, I
will then do an ENDJOBABN on the remaining jobs.
This instance was a QZLSFILE job that did not end. I looked this up,
yet there is no apparent reason why it did not end properly.
I know that this will work, but I just wanted your thoughts on what
experiences you have had & what you have done.
Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Company
phone (205) 325-3033
fax (205) 307-3833
_________Confidentiality Notice_______________________ This e-mail and
any files transmitted with it is confidential and is intended solely for
the use of the individual(s) or entity(ies) to whom this e-mail is
addressed. If you are not the intended recipient or the person
responsible for delivering the e-mail to the intended recipient, be
advised that you have received this e-mail in error, and that any use,
disclosure, dissemination, forwarding, printing, retention or copying of
this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return this e-mail to the sender and delete
the e-mail from your system.
Thank you.
--
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.
midrange.com
