HAVE YOU LOOKED UP "Wait State 082" in the MVS SYSTEM CODES manual?





" System action

The system entering the sysplex is partitioned from the sysplex and wait state 
X'082' is loaded on that system to prevent global sysplex data corruption.

For reason code X'00', message IEA002I is issued, either on the failing system 
or on an active system in the sysplex, indicating which system requires 
maintenance to be applied and the appropriate APAR to apply.

For reason code X'08', message IEA002I is issued on the failing system, 
indicating that the system requires maintenance. The system does not know the 
appropriate APAR to apply, so the text of the message is IEA002I APAR UNKNOWN 
IS NOT INSTALLED."






****************************************************************
* USERS AFFECTED: All users running at z/OS V1R12 (HBB7770)    *
*                 and above in a sysplex environment.          *
****************************************************************
* PROBLEM DESCRIPTION: See Problem Summary                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This APAR provides release toleration for new function
available in z/OS V2R1 (HBB7790).

    R750 PSN UA68601       UP13/04/17 P F304   z/OS 1.10
    R760 PSN UA68602       UP13/04/17 P F304   z/OS 1.11
    R770 PSY UA68603       UP13/04/17 P F304   z/OS 1.12
    R780 PSY UA68604       UP13/04/17 P F304   z/OS 1.13

This particular issue can be resolved by installing UA68602 on you z/OS 1.11 
system.





HOWEVER........
THERE WILL BE MANY OTHER ISSUES SUBSEQUENT TO GRS INITIALIZATION, INCLUDING, 
BUT NOT LIMITED TO:
A JES2 FAILING TO JOIN THE MAS. THE ALTERNATIVE IS MULTPLE JESPLEX(ES) with the 
SYSPLEX.

IT IS A WASTE OF EFFORT TO ATTEMPT TO MAKE z/OS 2.1  COEXIST IN A SYSPLEX with 
z/OS 1.11.
UPGRADE YOUR z/OS 1.11 system to z/OS 1.12 or higher.


The gap from z/OS 1.11 to z/OS 2.1 is almost 5 years (based on an annual 
release).
IBM has publically stated N-2 toleration and coexistence is the maximum 
supported.
N     = z/OS 2.1
N-1 = z/OS 1.13
N-2 = z/OS 1.12





<snip>
When I tried to IPL z/OS 2.1 stand alone, It works fine. Then I changed parmlib 
COUPLXX member and tried to make this z/OS 2.1 system as member of current 
SYSPLEX, I got below error in HMC Operating system message.

IEA002I APAR OA36207 is not installed on TST01. SYSTEM TST02 is being 
Partitioned .
IXC220W XCF is unable to continue . Wait State 082 REASON code 000.

EXTERNAL CALLER REQUESTED WAIT STATE TO BE LOADED.

*Note : In this message, TST01 is z/OS 1.11 system and TST02 is z/OS 2.1
LPAR.*

As all of you suggested that z/OS 1.11 can not work in same sysplex with z/OS 
2.1 then I am really not sure, why I am getting this message to apply
OA36207 APAR on z/OS 1.11( TST01) LPAR.

*Please suggest.*
</snip>



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to