A fix is available
APAR status
Closed as program error.
Error description
PE issues affecting systems with OA44240 applied. User's Affected: --------------- After applying PTFs UA90740 (HBB7780) or UA990741 (HBB7790) for APAR OA44240, the following issues have been reported: For users of Basic HyperSwap, the following issues may occur: 1- Inconsistent policy information reported by different members in the SYSPLEX. This issue will be observed when a DISPLAY HS,STATUS command is issued on each member of the SYSPLEX after one or more members are introduced into the SYSPLEX while at least one other member with the PTF applied is already active in the SYSPLEX. The inconsistency may result in incorrect action being taken by the system and may cause systems to be removed from the SYSPLEX in the event of a HyperSwap. External Symptoms: D HS,STATUS will show the following settings, no matter what the TPC-R settings were: - New member configuration load failed: Partition - Planned swap recovery: Disable - Unplanned swap recovery: Partition - FreezeAll: No 2- After a system is IPL'ed into the SYSPLEX and then becomes the Master member it does not recognize a configuration being active on all SYSPLEX members, causing existing SYSPLEX members that do not have the PTFs applied to be targeted for removal as a result of an unplanned HyperSwap. External Symptoms: This issue will be observed when the response to a DISPLAY HS,CONFIG command includes a non-zero count for the 'Impacted Systems'. 3- ABEND0C4-10 is possible in IOSHMEPT when a system is IPL'ed into the SYSPLEX while the Master member does not have the PTFs applied. 4- In a SYSPLEX consisting of members with and without the PTFs applied, a SETHS SWAP command issued on a member without the PTF applied will not be processed. The planned HyperSwap can still be initiated via the TPC-R interface or by issuing the SETHS SWAP command on a system with the PTF applied. External Symptoms: IOSHM0399I SETHS command rejected - name not found 5- Diagnostic ABEND2E0-00100001 or ABEND2E0-00070003 may occur when a system with the PTF applied is introduced into the SYSPLEX while another system without the PTF applied is currently active as the Master member. The new system will take over the Master role while requests are being queued to the old Master member which will take the abend to document the fact that it is no longer the Master member and can not process the queued requests. The system continues to operate normally and the queued requests will be eventually reissued to the current Master member. 6- In a SYSPLEX consisting of members with and without the PTFs applied, a system without the PTFs may incorrectly be counted as ineligible for HyperSwap due to having no PPRC Secondary Connectivity, regardless of the actual connectivity to the secondary devices. External Symtpoms: TPC-R will be disabled with "IWNR5422E Basic HyperSwap or z/OS Hardened Freeze is disabled with session status code 1000000" Verification steps: SYSIOS CTRACE will show HS API call x'00' every 5 minutes without call x'0F' on the systems without OA44240 For users of both Basic HyperSwap and GDPS HyperSwap, the following issue may occur: 7- ABEND878-4 may be taken in IOSHSAPI during loading of a configuration (VaryOn). This will cause the configuration load to fail, resulting in the disablement of HyperSwap function. User Impact: ----------- APAR OA44240 provided new functions but introduced new problems as described above. Customers are better off with APAR OA44240 on their systems for the following reasons: - APAR OA44240 provided infrastructure updates to IOS and Basic HyperSwap to allow new enhancements such as Multi-Target PPRC and other IOS functions. - Since the updates in APAR OA44240 have been used as the basis for other IOS enhancements, removing the PTFs for APAR OA44240 would require the removal of other PTFs as well. - Most of the problems described above can be rectified by a restart of the Basic HyperSwap Management address space on the affected systems or a reload of the HyperSwap configuration from TPC-R after the PTFs for OA44240 have been applied to all systems in the SYSPLEX.
Local fix
Local Fix: --------- For issues 1 and 6 above, terminate and reload the HyperSwap configuration from TPC-R panel. This is done through TPC-R by selecting "stop" for the configuration, followed by Start H1->H2. For issues 2 and 5 above, stop and restart the Basic HyperSwap Management address space on the system without the PTFs applied. For issues 3 and 4 above, there will be no impact other than the abends and dumps generated. For issue 7 above, no local fix exists
Problem summary
**************************************************************** * USERS AFFECTED: Users at HBB7780 and above that use Basic * * HyperSwap or GDPS HyperSwap function and * * have PTFs UA90740, UA90741 or UA90742 * * applied. * **************************************************************** * PROBLEM DESCRIPTION: In Basic HyperSwap environment, the * * following issues may be encountered: * * - Inconsistent configuration policy * * information among members of the * * SYSPLEX. * * - Some members of the SYSPLEX may be * * targeted for removal during a * * HyperSwap because the active * * configuration is not considered * * active on those members. * * - ABEND0C4 in IOSHMEPT after a new * * member becomes active and the * * current Master member does not * * support multi-target (at z/OS 1.13 * * or z/OS 2.1 level without the PTFs * * UA90740, UA90741 or UA90742 applied * * or z/OS 1.12). * * - SETHS SWAP command issued on a system * * that does not support multi-target * * is rejected by a Master system that * * has the PTF for APAR OA44240 applied * * (MSGIOSHM0399I). * * - ABEND2E0-00100001 or * * ABEND2E0-00070003 may occur when * * new systems are introduced into the * * SYSPLEX with an existing system * * already acting as Basic HyperSwap * * Master member. * * * * In both Basic HyperSwap and GDPS * * HyperSwap environments, intermittent * * ABEND878-4 may occur in IOSHSAPI. * **************************************************************** * RECOMMENDATION: * **************************************************************** If PTFs for APAR OA44240 are applied and Basic HyperSwap is in use, the following issues may occur: - If a new system is IPL'ed into the SYSPLEX, or having the Basic HyperSwap Management address space restarted, after a configuration has been loaded, the new system may not have correct configuration policy options regarding PPRC suspension and HyperSwap failure processing. - Similarly, after a system is IPL'ed into the SYSPLEX, or having the Basic HyperSwap Management address space restarted, and then becomes the Master member it does not recognize a configuration being active on all SYSPLEX members, causing existing SYSPLEX members to be targeted for removal when an unplanned HyperSwap is triggered. - ABEND0C4-10 is possible in IOSHMEPT when a system is IPL'ed into the SYSPLEX, or having the Basic HyperSwap Management address space restarted, while the Master member does not support multi-target (z/OS 1.13 or z/OS 2.1 without the PTFs applied or z/OS 1.12). - SETHS SWAP command issued on a system that does not support multi-target is rejected by a Master system that has the PTFs for APAR OA44240 applied. The following message is issued: IOSHM0399I SETHS command rejected - name not found - ABEND2E0-00100001 or ABEND2E0-00070003 my occur when new systems in the SYSPLEX attempt to take over as the Basic HyperSwap Master member. If PTFs for APAR OA44240 are applied, the following issue may occur in either Basic HyperSwap or GDPS HyperSwap environment: - Intermittent ABEND878-4 in IOSHSAPI when it incorrectly attempts to obtain a large amount of storage for a configuration data array. The storage amount was miscalculated due to a input half-word parameter instead of a full-word.
Problem conclusion
- Ensure new systems in the SYSPLEX are given correct configuration policy options. - Ensure active configuration is recognized correctly among all SYSPLEX members. - Ensure a valid configuration is used to perform the Test Secondary request. - The preferred configuration, if any, will be used when SETHS SWAP command is issued from a system that does not support multi-target PPRC. - Ensure Master take over process is better synchronized between systems. - Ensure IOSHSAPI obtains the correct amount of storage. The following issues are also fixed with this APAR: - Potential ABEND0C4 in IOSHMCFG when processing a Purge request. - Basic HyperSwap may be disabled after the HyperSwap API address space is terminated on one of the systems in the SYSPLEX. Messages MSGIOSHM0304I and MSGIOSHM0819I may be issued with incorrect reason 'Ineligible by JES3'. - After a PPRC suspension event, a system that does not support multi-target may not be able to load another configuration. KEYWORDS: HYPERSWP/K
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
OA47113
Reported component name
IOS
Reported component ID
5752SC1C3
Reported release
790
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-02-16
Closed date
2015-02-25
Last modified date
2015-04-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA76439 UA76440
Modules/Macros
IOSHMCFG IOSHMCF2 IOSHMCMT IOSHMEPT IOSHMHST IOSHMXUS IOSHSAPI
Fix information
Fixed component name
IOS
Fixed component ID
5752SC1C3
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 April 2015