IBM Support

DY47777: WRONG DEVICE NUMBER (CUU) IN AOM MESSAGES AOMAP00I, AOMDR##I, AOMIO06I, ATTENTION-MSG AND AR/JCL MESSAGE 1YH1I

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The device number (CUU) shown in the asynchronous operations
    manager (AOM) messages AOMAP00I, AOMDR##I, AOMIO06I, and
    ATTENTION-MSG may be wrong when multiple AOM requests are
    processed in parallel.
    For example, when LIBSERV command and/or LBSERV macro
    MOUNT/RELEASE requests for multiple devices are processed in
    parallel, all of the AOMAP00I messages preceding the AOMAP20I
    (MOUNT) or AOMAP21I (RELEASE) completion messages may show the
    same device number of the last request.
    This results in the erroneous information that multiple
    partitions have mounted different volumes in the same tape
    library device at the same time.
    In case of the message ATTENTION-MSG, which is only printed with
    DEBUG ON, it may show the wrong device number, originating from
    the last request processed.
    Under rare circumstances the device number (CUU) shown in the
    AR/JCL message 1YH1I may be random data.
    For example when canceling a LBSERV macro request using the AR
    command LIBSERV CANCEL, which has been implicitly invoked by job
    control (JC) during end of job, the CUU shown in message 1YH1I
    may be random data (e.g. "OR,"):
    1YH1I  MOUNT CANCELED FOR UNIT OR,
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Wrong device number (CUU) in AOM        *
    *                      messages and AR/JCL message.            *
    ****************************************************************
    1. The device number (CUU) shown in the asynchronous operations
    manager (AOM) messages AOMAP00I, AOMDR##I, AOMIO06I, and
    ATTENTION-MSG may be wrong when multiple AOM requests are
    processed in parallel.
    For example, when LIBSERV command and/or LBSERV macro MOUNT/
    RELEASE requests for multiple devices are processed in parallel,
    all of the AOMAP00I messages preceding the AOMAP20I (MOUNT) or
    AOMAP21I (RELEASE) completion messages may show the same device
    number of the last request. This results in the erroneous
    information that multiple partitions have mounted different
    volumes in the same tape library device at the same time.
    In case of the message ATTENTION-MSG, which is only printed with
    DEBUG ON, it may show the wrong device number, originating from
    the last request processed.
    
    2. Under rare circumstances the device number (CUU) shown in the
    AR/JCL message 1YH1I may be random data.
    For example when canceling a LBSERV macro request using the AR
    command LIBSERV CANCEL, which has been implicitly invoked by
    job control (JC) during end of job, the CUU shown in message
    1YH1I may be random data (e.g. "OR,"):
        1YH1I  MOUNT CANCELED FOR UNIT OR,
    

Problem conclusion

  • 1. The device number (CUU) shown in AOM messages AOMAP00I,
    AOMDRnnI, AOMIO06I, and ATTENTION-MSG was taken from a global
    variable shared between all AOM requests. During initiation of
    an AOM request for a device its CUU was stored in this global
    variable in printable form. When multiple AOM requests were
    processed in parallel this caused the wrong CUU from another
    request to be shown in the aforementioned messages.
    
    2. AR LIBSERV CANCEL of LBSERV macro requests, for example those
    implicitly initiated by job control (e.g. LBSERV RELEASE during
    end-of-job (EOJ)), caused random data to be shown in the CUU
    field of the AR/JCL message 1YH1I. This was caused by addressing
    an appendage to the IJJLBSER control block that is not existing
    for those requests.
    

Temporary fix

Comments

APAR Information

  • APAR number

    DY47777

  • Reported component name

    VSE/AF SVR/BAM

  • Reported component ID

    5686VS606

  • Reported release

    61C

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-09

  • Closed date

    2018-07-26

  • Last modified date

    2018-08-20

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

    DY47776

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

    UD54330

Modules/Macros

  • IJBAOM   IJBSLIB
    

Fix information

  • Fixed component name

    VSE/AF SVR/BAM

  • Fixed component ID

    5686VS606

Applicable component levels

  • R61C PSY UD54330

       UP18/08/20 I 1000

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":"BU011","label":"Systems - zSystems software"}, "Product":{"code":"SG32M","label":"APARs - VSE/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"61C","Edition":""}]

Document Information

Modified date:
20 August 2018