JES2 Checkpoint Lock Held

2006-04-07 Thread Dean Montevago
Hi,

I had a problem where one system in the MAS had the JES2 chkpt lock
held. There are 2 systems in the MAS. In this situation can you reset
the lock being held without doing further damage ? Please advise.

Thanks
Dean

Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: JES2 Checkpoint Lock Held

2006-04-07 Thread McKown, John
 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:[EMAIL PROTECTED] On Behalf Of Dean Montevago
 Sent: Friday, April 07, 2006 10:24 AM
 To: IBM-MAIN@BAMA.UA.EDU
 Subject: JES2 Checkpoint Lock Held
 
 
 Hi,
 
 I had a problem where one system in the MAS had the JES2 chkpt lock
 held. There are 2 systems in the MAS. In this situation can you reset
 the lock being held without doing further damage ? Please advise.
 
 Thanks
 Dean
 
 Dean Montevago

The big question is WHY did the other system have the lock held? If
the other system is DEAD and DOWN (i.e. an IPL is going to be done on
it), then resetting the checkpoint lock is OK. If the other system is
suspended for some reason (such as lack of CPU due to being in a
low-priority LPAR or DASD reserve or ???), then resetting the lock might
cause data corruption on the SPOOL. JES2 will likely recover from this,
but the affect job/tso/stc might die.

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law.  If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited. 
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: JES2 Checkpoint Lock Held

2006-04-07 Thread Dean Montevago
I was bringing down an ISV product that monitors our DASD. JES2 was
suspended not dead. ok now the truthI was bringing down this
software on one system and started to bring it down on the other before
the first shutdown was complete. This software issues reserves for some
reason and I think that since 2 shutdowns were taking place at the
sometime had something to do with it. It was a timing thing.

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of McKown, John
Sent: Friday, April 07, 2006 11:46 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES2 Checkpoint Lock Held


 -Original Message-
 From: IBM Mainframe Discussion List
 [mailto:[EMAIL PROTECTED] On Behalf Of Dean Montevago
 Sent: Friday, April 07, 2006 10:24 AM
 To: IBM-MAIN@BAMA.UA.EDU
 Subject: JES2 Checkpoint Lock Held
 
 
 Hi,
 
 I had a problem where one system in the MAS had the JES2 chkpt lock 
 held. There are 2 systems in the MAS. In this situation can you reset 
 the lock being held without doing further damage ? Please advise.
 
 Thanks
 Dean
 
 Dean Montevago

The big question is WHY did the other system have the lock held? If
the other system is DEAD and DOWN (i.e. an IPL is going to be done on
it), then resetting the checkpoint lock is OK. If the other system is
suspended for some reason (such as lack of CPU due to being in a
low-priority LPAR or DASD reserve or ???), then resetting the lock might
cause data corruption on the SPOOL. JES2 will likely recover from this,
but the affect job/tso/stc might die.

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law.  If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited. 
 

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html