OA45662: NEW FUNCTION - IBM ZHYPERWRITE SUPPORT IN I/O SUPERVISOR

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New Function APAR
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users at HBB7790 and above                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: New function to provide support in the  *
  *                      I/O Supervisor component for the IBM    *
  *                      zHyperWrite function in disk storage    *
  *                      controllers.  D/T2107                   *
  ****************************************************************
  * RECOMMENDATION: The I/O Supervisor provides support for IBM  *
  *                 zHyperWrite function.  For full IBM          *
  *                 zHyperWrite support, additional APARs        *
  *                 (OA45125,OA44973,PI25747) and disk           *
  *                 controller microcode (see hold for           *
  *                 engineering change) are required.            *
  ****************************************************************
  New function to provide support for IBM zHyperWrite.
  In environments where HyperSwap-managed metro mirror replication
  is used for business continuity, an opportunity to reduce
  I/O latency exists by using software mirroring for certain
  I/Os using the IBM zHyperWrite feature in some storage
  controllers.
  

Problem conclusion

Temporary fix

Comments

• New function to provide support for IBM zHyperWrite.
  The I/O Supervisor provides support for IBM zHyperWrite
  function.  For full IBM zHyperWrite support, additional APARs
  (OA45125,OA44973,PI25747) and disk controller microcode
  (see hold for engineering change) are required.
  
  The following documentation changes are made:
     In MVS Initialization and Tuning Reference (SA23-1380)
  
     Chapter 55. IECIOSxx (I/O related parameters)
     ...
     - Specify whether the HyperPAV facility is disabled,
       enabled or in base only mode. (HYPERPAV parameter)
   | - Specify whether IBM zHyperWrite data replication is
   |   enabled or disabled.  (HYPERWRITE parameter)
     ...
     You can change the FICON, STORAGE, CAPTUCB, MIDAW,
   | HYPERPAV, HYPERWRITE, EKM, RECOVERY, and ZHPF parameters
     dynamically using the SETIOS command. See z/OS MVS System
     Commands.
     ...
     Syntax rules for IECIOSxx
     ...
     The following rules apply to the creation of IECIOSxx:
     ...
     - Each record must start with MIH, HOTIO, TERMINAL, FICON,
       STORAGE, CAPTUCB, EKM, or RECOVERY followed by one or
       more blanks, or must be a valid CTRACE, MIDAW, HYPERPAV,
   |   HYPERWRITE, or ZHPF specification in the format given as
       follows.
  
     - If duplicate keywords are found, the last occurrence of
       the keyword is used.
  
     - Two different verbs cannot be specified in the same
       record.
  
     - The format for each record is as follows.
       ...
         HYPERPAV=parameter
   |     HYPERWRITE=parameter
         EKM parameter
     ...
   |
   | HYPERWRITE
   |
   |  Use the HYPERWRITE statement to enable or disable IBM
   |  zHyperWrite data replication on a system. If no HYPERWRITE
   |  statement is specified, IBM zHyperWrite data replication
   |  is enabled on the system by default.
   |
   |  HYPERWRITE=YES|NO
   |   Specifies whether IBM zHyperWrite data replication is
   |   enabled or disabled on a system-wide basis.
   |
   |   Note: Certain exploiting applications, such as DB2, may
   |   also provide their own controls to enable or disable the
   |   use of this function.  IBM zHyperWrite processing can be
   |   used by I/O drivers, such as Media Manager, for certain
   |   write I/O operations to perform software mirroring to
   |   peer-to-peer remote copy (PPRC) devices that are
   |   monitored for HyperSwap processing (with GDPS or TPC-R).
   |   IBM zHyperWrite data replication can be used to reduce
   |   latency in these HyperSwap environments. For maximum
   |   benefit, IBM zHyperWrite data replication should only be
   |   used when all synchronously mirrored relationships are
   |   managed by HyperSwap. Devices support IBM zHyperWrite
   |   data replication when the following conditions are true:
   |
   |   - The devices support IBM zHyperWrite data replication.
   |     Both the primary and secondary devices in a synchronous
   |     PPRC relationship must support this function.
   |   - The devices in the synchronous PPRC relationship are
   |     managed by HyperSwap (either GDPS HyperSwap or TPC-R
   |     HyperSwap).
   |
   |   YES   IBM zHyperWrite data replication is enabled system-
   |         wide.
   |   NO    IBM zHyperWrite data replication is disabled.
   |   Default: YES
  
     In MVS System Commands (SA38-0666)
  
      In the DISPLAY IOS command section:
  
   |
   |  Displaying the IBM zHyperWrite data replication status
   |
   |   Use the DISPLAY IOS,HYPERWRITE command to display the
   |   current IBM zHyperWrite data replication enablement
   |   status.
   |
   |   D IOS,HYPERWRITE ,L={a|name|name-a}
   |
   |     The system displays whether IBM zHyperWrite data
   |     replication is enabled or disabled on a system-wide
   |     basis.
   |
   |     Note: Certain exploiting applications, such as DB2,
   |     may also provide their own controls to enable or
   |     disable the use of this function.
   |
   |     L=a, name, or name-a
   |
   |      Specifies the display area (a), console name (name),
   |      or both (name-a) where the display is to appear.  If
   |      you omit this operand, the display is presented in the
   |      first available display area or the message area of
   |      the console through which you enter the command.
   |
      In the SETIOS command section:
  
   |
      In addition, you can use the SETIOS command to do the
      following:
     ...
      - Enable or disable the zHPF facility.
   |  - Enable or disable IBM zHyperWrite data replication.
  
     ...
     SYNTAX:
     SETIOS  MIH ,class=mm:ss ,class=mm:ss ...
     ...
             ZHPF={YES|NO}
   |         HYPERWRITE={YES|NO}
     ...
   |
   |    HYPERWRITE={YES or NO}
   |      Indicates whether IBM zHyperWrite data replication
   |      should be enabled or disabled on a system-wide basis.
   |
   |      Note: Certain exploiting applications, such as DB2,
   |      may also provide their own controls to enable or
   |      disable the use of this function.  IBM zHyperWrite
   |      processing can be used by I/O drivers, such as Media
   |      Manager, for certain write I/O operations to perform
   |      software mirroring to peer-to-peer remote copy (PPRC)
   |      devices that are monitored for HyperSwap processing
   |      (with GDPS or TPC-R). IBM zHyperWrite data replication
   |      can be used to reduce latency in these HyperSwap
   |      environments. In order to have maximum benefit, IBM
   |      zHyperWrite data replication should only be used when
   |      all synchronously mirrored relationships are managed
   |      by HyperSwap.  Devices support IBM zHyperWrite data
   |      replication when the following conditions are true:
   |
   |      - The devices support IBM zHyperWrite data
   |        replication. Both the primary and secondary devices
   |        in a synchronous PPRC relationship must support this
   |        function.
   |      - The devices in the synchronous PPRC relationship are
   |        managed by HyperSwap (either GDPS HyperSwap or TPC-R
   |        HyperSwap).
   |
   |      YES  IBM zHyperWrite data replication is to be enabled
   |           system-wide.
   |
   |      NO   IBM zHyperWrite data replication is to be
   |           disabled.
   |
   |      Default: YES
  
     In MVS System Messages, Vol. 9 (IGF-IWM) (SA38-0676)
  
     > Changed Message IOS090I
       IOS090I {IECIOSxx. | SETIOS. text UPDATE(S) COMPLETE}
  
       Explanation:  Where text is one of the following:
       ...
   |     In response to the SET IOS=xx or SETIOS command,
   |     the system displays this message.
  
         In the message text:
         ...
         SETIOS
   |     The operator entered the SETIOS MIH | HYPERWRITE |
   |     FICON | STORAGE | CAPTUCB | MIDAW | EKM | HYPERPAV |
   |     RECOVERY command..
         ...
         text
         One of the following:
         ...
         - RECOVERY
         - ZHPF
   |     - HYPERWRITE
       ...
  
       New message IOS634I is added as follows:
   |    IOS634I IOS SYSTEM OPTION
   |            HYPERWRITE IS status
   |
   |    Explanation: The system displays this message in
   |    response to a DISPLAY IOS command when one of the
   |    following options are specified:
   |
   |    - HYPERWRITE
   |       For information about how to change the current
   |       option for the specified keyword, see the SETIOS
   |       command in z/OS MVS System Commands.
   |
   |       In the message text:
   |         HYPERWRITE IS status
   |         Indicates the status of IBM zHyperWrite data
   |         replication on a system-wide basis.  Note: Certain
   |         exploiting applications, such as DB2, may also
   |         provide their own controls to enable or disable the
   |         use of this function.
   |
   |         HYPERWRITE IS ENABLED
   |         Indicates that IBM zHyperWrite data replication is
   |         enabled system-wide. IBM zHyperWrite data
   |         replication allows I/O drivers to write to both
   |         primary and secondary devices for some or all of
   |         the write I/O operations that are performed. This
   |         can provide improvements in I/O latency.
   |
   |         HYPERWRITE IS DISABLED
   |         Indicates that IBM zHyperWrite data replication is
   |         disabled.
   |
   |    System action: None.
   |    Operator response: None.
   |    System programmer response: None.
   |    Problem determination: None.
   |    Source: I/O Supervisor
   |    Module: IOSCPARZ
   |    Routing code: 2
   |    Descriptor code: 12
  
     In MVS Authorized Assembler Services Guide (SA23-1371),
     In table 21, "ENF Macro Event Codes", add the following for
     ENF code 33, and in MVS Authorized Assembler Services
     Reference (EDT-IXG) (SA23-1373), table 3,
     "ENF Macro Event Codes", add the following for ENF code 33:
  
   |    Column 2 in the table has the following new reason for
   |              ENF 33:
   |      - A device requires monitoring.
   |
   |    Column 3 in the table has the following new description
   |    for ENF 33:
   |
   |      ENF signal 33 subtype DACHMONC
   |      (DACHTYPE = DACHMONC) is issued when a
   |      change in device monitoring is requested. This
   |      signal may be generated for secondary devices
   |      monitored for HyperSwap configurations for
   |      which I/O operations may begin to be started.
   |      This signal may also be received when devices
   |      that were previously identified by ENF 33
   |      subtype DACHMONC no longer require
   |      monitoring.
   |
   |      Programs such as RMF may choose to monitor
   |      this ENF 33 signal to know when to begin
   |      collecting data for these devices which might
   |      otherwise see only insignificant amounts of I/O
   |      activity. For the DACHMONC subtype:
   |
   |      - For a device that requires monitoring, the
   |        following fields are set:
   |         DACH_IO_QUAL=DACH_IO_QUAL_MONC_ON
   |         DACH_IO_DEVN=Device number
   |         DACH_IO_SSID=Subchannel set identifier
   |         DACH_IO_DTYP=Contents of the UCBTYP field from the
   |             UCB
   |         DACHUCBC=Device class
   |         DACHQN=Either DACHIO or DACHIO_AS
   |        Each device receives a separate signal to begin
   |        monitoring. When monitoring is requested, the
   |        UCBCMONR bit is set on in the UCB.
   |      - When one or more devices no longer require
   |        monitoring, a single ENF 33 DACHTYPE =
   |        DACHMONC, DACHQN = DACHIO signal is
   |        given with DACH_IO_QUAL =
   |        DACH_IO_QUAL_MONC_OFF. This is
   |        typically done after a HyperSwap occurs or
   |        when a configuration is purged from the
   |        HyperSwap manager. When this signal is
   |        received, a UCBSCAN can be done to detect
   |        devices for which the UCBCMONR bit is no
   |        longer set on. DACH_IO_DEVN and
   |        DACH_IO_SSID are not used for this signal.
  
     In MVS Data Areas, Volume 3 (IEFALCXT-IRARENF1)
     (GA32-0937) also has changes.  Refer to the
     changes identified in the hold for documentation
     changes.
   KEYWORDS: HYPERSWP/K
  

APAR Information

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

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

  UA90746 UA90747

Modules/Macros

• HBB7790J IECDIOSB IOSCPARZ IOSDDACH IOSDDEVI
  IOSDIOBE IOSDUCBC IOSHSSUB IOSIOSEN IOSIOSJP IOSRMIHP IOSVDATA
  IOSVENFS IOSVIRBD IOSVMOD1 IOSVQSCD IOSVSSCH IOSVSWAP IOSVUSER
  

Fix information

• Fixed component name

  IOS

• Fixed component ID

  5752SC1C3

Applicable component levels

• R790 PSY UA90746

     UP15/01/10 P F501

• R79J PSY UA90747

     UP15/01/10 P F501

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.