Yep, we saw this on our development LPARS last week.  We backed off
UA30836.  At the time we did the catalog restart which got us through
the day, until we could re-ipl minus that PTF.

Dave 


________________________________________________________
Dave Jousma
Principal Systems Programmer
[EMAIL PROTECTED]
616.653.8429


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Schwartz
Sent: Tuesday, January 16, 2007 1:51 PM
To: [email protected]
Subject: All Lpar ipl this morning

Perhaps I can save someone an outage.  We ipled a lot of preventative
maintenance in our production lpars Sunday.  This morning we started
getting severe enqueue conflicts for a number of catalogs.  We called
IBM and by just describing the symptoms the rep said "I think I know
your problem".  A hiper apar was released FRIDAY (OA19429):

SYSIGGV2 ENQ HANG WITH WAIT in module IGG0CLEG @ UA30836
  07/01/02 PTF PECHANGE
 
  Symptom ...... IN INCORROUT         Status ........... OPEN
  Severity ................... 1      Date Closed .........
  Component .......... 5695DF105      Duplicate of ........
  Reported Release ......... 1J0      Fixed Release ............
  Component Name ICF CATALOG & C      Special Notice    PE     HIPER
  Current Target Date ..07/02/17      Flags
  SCP ...................               FUNCTIONLOSS
  Platform ............
 
  Status Detail: DESIGN/CODE - APAR solution is being designed
                               and coded.
 
  PE PTF List:    UA30834 UA30835 UA30836 UA30838 UA30837
 
  PTF List:
 
  Tentative Affected Releases and Current Relief Available:
  Release 1G0   : Relief is available in the form of: AA19429
  Release 180   : Relief is available in the form of: AA19429
  Release 1H0   : Relief is available in the form of: AA19429
  Release 1J0   : Relief is available in the form of: AA19429
  Release 1K0   : Relief is available in the form of: AA19429
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  OA18860 introduces code that places us in a WAIT in order to
  complete IO for spanned record updates.  It has been found that
  the flag indicating us to go issue this WAIT may be ON
  unexpectedly.  This causes tasks to hang holding the SYSIGGV2
  resource.
  .
  TO VERIFY, review the holder of the SYSIGGV2 resource.  In the
  TCB's RB chain, you should see a WAIT.  This apar is a match if
  the WAIT was issued in module IGG0CLEG at level UA30834-30838.
 
 
  LOCAL FIX:
  Action should be taken to roll back PTFs for OA18860.
  F CATALOG,RESTART or F CATALOG,ABEND may temporarily resolve
  this issue.
  ++APARs are expected to be available no later than Jan 19,2007




This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

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

Reply via email to