OA32551 recently closed with PTFs available. 

http://www-01.ibm.com/support/docview.wss?crawler=1&uid=isg1OA32551 

We have been debating internally if we will change our deployment of 1.11 into 
the remaining Sysplex here that is 1.10 only based on this problem.  The 
prospect of getting outages on all the 1.10 systems so we could implement this 
one last toleration fix compared to migrating the whole Sysplex to 1.11 the 
same morning is not an easy choice.  We were exposed but never saw this problem 
manifest in two other Sysplex which ran mixed levels.   

CAPTUCB protection is now the default. Is anyone running with CAPTUCB disabled 
at this point?  Why?


        Best Regards, 

                Sam Knutson, GEICO 
                System z Team Leader 
                mailto:[email protected] 
                (office)  301.986.3574 
                (cell) 301.996.1318  
            
"Think big, act bold, start simple, grow fast..." 


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Brian Peterson
Sent: Thursday, August 19, 2010 11:49 AM
To: [email protected]
Subject: Heads Up: JES2 APAR OA32551 "Undiscovered Toleration"

Nearly two decades ago, I first met Toby from IBM at SHARE.  At that time,
she represented DFSMS Level 2 at SHARE.

Among many fond recollections from that time, I recall a phrase I first
heard Toby use to describe an APAR that addressed a release-to-release
toleration fix that was NOT published prior to GA but was instead discovered
in the field.  She called such APARs "undiscovered toleration".  The film
"Star Trek IV: The Undiscovered Country", which was released in 1991,
undoubtedly was an influence for this particular phrase.  The film, of
course, took the phrase from Shakespeare:
http://www.enotes.com/shakespeare-quotes/not-that-question

JES2 APAR OA32551 is an APAR which I would call "undiscovered toleration". 
This APAR describes an incompatibility between JES2 systems in a MAS, if
there are systems at the JES2 z/OS 1.11 and pre-1.11 level present in the
MAS.  If a job is converted at one JES2 level, and then viewed using SDSF
from a system at another JES2 level (for example, converted on 1.11 and
viewed on 1.10, or visa versa), abends and/or UCB overlays can occur.

So, if you have a JES2 MAS where some members are z/OS JES2 1.11 *and* other
members of the same MAS are pre-1.11, you are likely exposed to this problem.

The APAR is currently open, and an APAR fix is available from JES2 level 2.
 Fixes are required for both JES2 1.10 and JES2 1.11 levels, for some reason.

Brian

====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

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