IBM Support

OA62658: SYSTEM LOGGER MANAGE HYPERWRITE ALLOWUSE (NO) DEFAULT NOT HONORED 22/01/06 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • APAR OA57408 changed the default setting for zHyperwrite in
    System Logger to inactive, i.e.  MANAGE HYPERWRITE ALLOWUSE
    (NO).  However, when no IXGCNFxx parmlib member is used for
    System Logger initialization, the default setting is not honored
    and zHyperwrite support is enabled.
    
    KNOWN IMPACT:
    When no IXGCNFxx parmlib member is used for System Logger
    initialization, System Logger will behave as if zHyperwrite
    support has been enabled.  As a result, unexpected IO to offline
    DASD devices in a PPRC configuration can occur.
    
    VERIFICATION STEPS:
    1) Verify no IXGCNFxx parmlib member is used for System Logger
    initialization.  The output of DISPLAY LOGGER,IXGCNF shows a
    value of "DEFAULT" for all parameters in the "SOURCE" column.
    
    2) Verify in the output of DISPLAY LOGGER,IXGCNF MANAGE
    HYPERWRITE ALLOWUSE (NO) is set.
    
    3) In a system dump, verify the 7th bit location in the byte at
    l 10?+8c?+120?+19 = 0.
    
    4) zHyperwrite activity by System Logger is observed when a
    zHyperwrite configuration is active.
    
    PE INFORMATION:
    USERS AFFECTED:
    All users of System Logger with:
    1) APAR OA57408 and HBB77B0 PTF UJ00118 or HBB77C0 PTF UJ00132
       applied,
    2) APAR OA58287 and HBB77B0 PTF UJ02181 applied, or
    3) APAR OA54815 and HBB77C0 PTF UJ00353 only applied
    that do not use an IXGCNFxx parmlib member.
    
    Note: HBB77A0 PTF UJ00354 and HBB77B0 PTF UJ00352 from APAR
    OA54815 are not included in this PE.
    
    
    USER IMPACT:
    APAR OA57408 did not completely fix the problem it reported.
    zHyperwrite remains enabled for System Logger by default if no
    IXGCNFxx parmlib member is used during System Logger
    initialization.
    

Local fix

  • BYPASS/CIRCUMVENTION:
    Specify an IXGCNFxx parmlib member to be used by System Logger
    containing the following parameter setting:
    
    MANAGE  HYPERWRITE
      ALLOWUSE(NO)
    
    This specification will force System Logger to make zHyperwrite
    inactive for System Logger IXGWRITE operations.
    
    RECOVERY ACTION:
    
    The following series of commands can be used to inactivate
    System Logger's use zHyperwrite immediately:
    
    SETLOGR MANAGE,HYPERWRITE,ALLOWUSE(YES)
    SETLOGR MANAGE,HYPERWRITE,ALLOWUSE(NO)
    
    Both commands must be issued in the order specified to cause
    zHyperwrite to be internally inactivated in System Logger.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All HBB77B0 and above System Logger                          *
    * environments with APAR OA57408 applied.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * System Logger's use of zHyperWrite is                        *
    * active, i.e. ALLOWUSE(YES), when an                          *
    * IXGCNFxx parmlib member is not                               *
    * specified at IPL time, despite the                           *
    * default being ALLOWUSE(NO).                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APAR OA57408 incorrectly attempted to change the default
    zHyperWrite setting from ALLOWUSE(YES) to ALLOWUSE(NO).
    Although the DISPLAY LOGGER,IXGCNF command response
    displays a default of NO for zHyperWrite, System Logger
    processes zHyperWrite requests as if it is active.
    
    Note; This only occurs when no IXGCNFxx parmlib member
    is specified at IPL time.
    

Problem conclusion

  • System Logger is changed to correctly honor the default
    zHyperWrite setting of ALLOWUSE(NO) when no IXGCNFxx
    parmlib member is specified at IPL time.
    
    The migration action in the "BCP: Evaluate the changed default
    for system logger's use of IBM zHyperwrite" section of the
    z/OS Upgrade Workflow has been updated to the following:
    
      Description:
        With the installation of APAR OA57408, the use of IBM
        zHyperWrite data replication by system logger is changed
        from enabled to disabled by default.
    
    |   APAR OA57408 only applied to systems that specify the
    |   IXGCNFxx parmlib member without the HYPERWRITE ALLOWUSE
    |   option specified.  With the installation of APAR OA62658,
    |   the use of IBM zHyperWrite data replication by system
    |   logger is changed from enabled to disabled by default for
    |   systems that do NOT specify the IXGCNFxx parmlib member.
    
        In parmlib member IXGCNFxx, this option is specified,
        as follows:
    |   MANAGE . . . HYPERWRITE ALLOWUSE(YES|NO)
    
        :
        :
    
       The following table provides more details about the
       upgrade action. Use this information to plan your
       changes to the system.
    
       Element or feature: BCP.
       When change was introduced: z/OS V2R3, with APAR OA57408
    |    and APAR OA62658 applied.
       Applies to upgrade from: z/OS V2R3, without APAR OA57408
    |    and APAR OA62658.
       Timing: Before the first IPL of z/OS V2R5.
       Is the upgrade action required? Yes, if you want system
         logger to use IBM zHyperwrite data replication.
       Target system hardware requirements: None.
       Target system software requirements: None.
       Other system (coexistence or fallback) requirements: None.
       Restrictions: None.
       System impacts: None.
       Related IBM Health Checker for z/OS check: None.
    
       Steps to take
       If you do not want system logger to use IBM zHyperwrite
       data replication, you have no action to take. When you
       install APAR OA57408, the use of IBM zHyperWrite data
       replication by system logger is disabled by default
    |  when the IXGCNFxx parmlib member is specified.  When
    |  you install APAR OA62658, the use of IBM zHyperWrite
    |  data replication by system logger is also disabled by
    |  default when the IXGCNFxx parmlib member is not specified.
    
       To enable system logger use of IBM zHyperwrite data
       replication, you can do either of the following:
          Enter the command SETLOGR MANAGE,HYPERWRITE,ALLOWUSE(YES)
          Update the IXGCNFxx parmlib member with
    |     HYPERWRITE ALLOWUSE(YES).
    
       Reference information
       For more information, see IXGCNFxx parmlib member in z/OS
       MVS Initialization and Tuning Reference
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA62658

  • Reported component name

    SYSTEM LOGGER

  • Reported component ID

    5752SCLOG

  • Reported release

    7C0

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-06

  • Closed date

    2022-03-10

  • Last modified date

    2022-06-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UJ07965 UJ07966 UJ07967

Modules/Macros

  • IXGE3CNF
    

Fix information

  • Fixed component name

    SYSTEM LOGGER

  • Fixed component ID

    5752SCLOG

Applicable component levels

  • R7B0 PSY UJ07965

       UP22/03/23 P F203 {

  • R7C0 PSY UJ07966

       UP22/03/23 P F203 {

  • R7D0 PSY UJ07967

       UP22/03/23 P F203 {

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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7C0"}]

Document Information

Modified date:
11 June 2022