IBM Support

OA42277: FAILED CHANNEL PROGRAM NOT RECOGNIZED BY MM AND IO SEEMS TO COMPLETE WITH CC=0. DB2 DETECTS ERROR IN IT'S PAGES.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Client was running large ZDMF migration of DB2 data sets. DB2
    detected "broken" pages (incorrect pages on DASD) and gives
    message  DSNI012I Page Logically Broken. Also get DSNB224I
    Abend04E 00C90101 from DB2.
    For a Media Manager channel program, ICYNRM turns off
    bits in the IOSB indicating the channel program had an error. A
    permanent error is not recognized by MM and the IO
    request completes with CC=00, even though the DB2 Page did
    not get written. Later, DB2 gives a variety of page errors
    trying to read the page. DB2 could give abend04E-00C90101,
    DSNB224I I/O error, DSNI012I PAGE LOGICALLY BROKEN, and
    DSNI010I BROKEN PAGE ACCESSED, among others.
    

Local fix

  • none yet.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: The problem can occur with data sets         *
    *                 accessed by DB2 release 10.  The problem     *
    *                 can also occur when accessing PDSE data      *
    *                 sets.  The problem exposure is               *
    *                 exacerbated when the data set resides on a   *
    *                 zHPF capable device and zDMF is in use to    *
    *                 move the data set.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: There are certain situations where      *
    *                      Media Manager will redrive failed       *
    *                      channel programs such as a failed       *
    *                      zHPF channel program or a failed        *
    *                      RTD CCW with MIDAWs.  The Media Manager *
    *                      will redrive the failed channel program *
    *                      with a different type of channel        *
    *                      program.                                *
    *                                                              *
    *                      In the case fixed by this APAR, the     *
    *                      Media Manager had started two channel   *
    *                      programs in parallel.  The first        *
    *                      channel program fails and drives IOS    *
    *                      Post Status.  The Media Manager         *
    *                      abnormal end module fails to set a bit  *
    *                      to indicates that the IO failed.  When  *
    *                      the second IO finishes the Media        *
    *                      Manager incorrectly concludes that all  *
    *                      the IO for the request is complete and  *
    *                      causes the requester to be posted that  *
    *                      the IO is complete.  Therefore the      *
    *                      failed IO is not redriven and no        *
    *                      error is surfaced.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Media Manager module ICYNRM is modified to set a bit
    to indicate that the IO has failed. This will allow for the
    successful redrive of the failed IO.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA42277

  • Reported component name

    DFSMS MEDIA MAN

  • Reported component ID

    5695DF126

  • Reported release

    D10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-13

  • Closed date

    2013-05-28

  • Last modified date

    2013-07-02

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

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

    UA69274 UA69275 UA69276

Modules/Macros

  • ICYDIE   ICYNRM   ICYPGAD
    

Fix information

  • Fixed component name

    DFSMS MEDIA MAN

  • Fixed component ID

    5695DF126

Applicable component levels

  • RC10 PSY UA69274

       UP13/06/05 P F306

  • RD10 PSY UA69275

       UP13/06/05 P F306

  • R210 PSY UA69276

       UP13/06/05 P F306

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":"D10","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 July 2013