IBM Support

DY47682: DEVICE-SPECIFIC MIH VALUE (EXAMPLE: SIR MIH,181=10M) OVERRULES GENERAL MIH VALUE ONLY ONCE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a device-specific MIH interval has been defined (for
    example SIR MIH,181=10M) and an interrupt becomes missing for
    this device, the operator msg
    AR+0013 0E04D P        DEVICE 181    LOST DEVICE END
    is issued after the device-specific MIH interval.
    If the interrupt continues to be missing, the device-specific
    MIH interval is not used anymore to trigger the next occurrence
    MSG0E04D. Instead, the overall MIH time interval (which is
    usually much lower) is used.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of SIR MIH command.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect logic when calculating a      *
    *                      device missing interrupt time and       *
    *                      comparing it with the device-specific   *
    *                      SIR MIH value.                          *
    ****************************************************************
    * RECOMMENDATION: Apply APAR.                                  *
    ****************************************************************
    When a device-specific MIH interval has been defined (for
    example SIR MIH,181=10M) and an interrupt becomes missing for
    this device, the operator msg
    AR+0013 0E04D P        DEVICE 181    LOST DEVICE END
    is issued after the device-specific MIH interval.
    If the interrupt continues to be missing, the device-specific
    MIH interval is not used anymore to trigger the next occurrence
    of MSG0E04D. Instead, the overall MIH time interval (which is
    usually much lower) is used.
    With the second (and all following) missing interrupt interval
    the device missing interrupt time was incorrectly calculated
    and compared with the device-specific SIR MIH,181=tt value.
    

Problem conclusion

  • Incorrect logic for calculating the device missing interrupt
    time has been corrected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    DY47682

  • 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

    2016-08-11

  • Closed date

    2016-08-15

  • Last modified date

    2016-08-23

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

    DY47676

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

    UD54204 UD54205

Modules/Macros

  • $$A$SUPI SGMIH    SGSRVLVL
    

Fix information

  • Fixed component name

    VSE/AF SVR/BAM

  • Fixed component ID

    5686VS606

Applicable component levels

  • R61C PSY UD54204

       UP16/08/23 I 1000

  • R61J PSY UD54205

       UP16/08/23 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"61C","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
11 December 2020