IBM Support

VM65693: MISCELLANEOUS FIXES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • (1) Building a production IODF with HCM fails to assign default
    CHID values for IQD channels
    (2) Incremental migration incorrectly sets the maximum number
        of devices in a subchannel set
    (3) The proposed number of devices of a CF connection via
        CS5 channels is incorrect
    (4) Missing warning when changing the lowest channel subsystem
        of a CF connection via CS5 channels
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: all HCD users                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. When building a production IODF      *
    *                         with HCM:                            *
    *                         IQD channels on 2964 processors      *
    *                         without a defined virtual            *
    *                         channel ID (CHID) do not get         *
    *                         default virtual channel IDs          *
    *                         assigned.                            *
    *                      2. When migrating an IOCP deck          *
    *                         incrementally:                       *
    *                         HCD fails to migrate the MAXDEV      *
    *                         parameter of the RESOURCE statement  *
    *                         correctly and sets the maximum       *
    *                         number of devices in a subchannel    *
    *                         set to zero.                         *
    *                      3. (z/VM V5R4 only)                     *
    *                         When connecting a coupling channel   *
    *                         of type CS5:                         *
    *                         HCM incorrectly proposes 7 as the    *
    *                         default number of CF devices.        *
    *                         Accepting the proposed value with    *
    *                         ENTER leads to error message         *
    *                         CBDG427I (MSGCBDG427I).              *
    *                      4. When working with a coupling         *
    *                         connection between distinct          *
    *                         processors over spanned CS5          *
    *                         channels:                            *
    *                         when changing the lowest channel     *
    *                         subsystem on one end of the          *
    *                         connection(by adding / removing      *
    *                         an LPAR to/from the access list      *
    *                         of the channel),                     *
    *                         HCD fails to warn that this may      *
    *                         require an activation of the         *
    *                         connected processor.                 *
    ****************************************************************
    * RECOMMENDATION: 1. When building a production IODF           *
    *                    with HCM:                                 *
    *                    IQD channels on 2964 processors           *
    *                    without a defined virtual                 *
    *                    channel ID (CHID) now get                 *
    *                    default virtual channel IDs               *
    *                    assigned.                                 *
    *                    Message CBDG560I is shown for each        *
    *                    such assignment (MSGCBDG560I).            *
    *                 2. When migrating an IOCP deck for a         *
    *                    newer processor                           *
    *                    (requiring a maximal HSA definition):     *
    *                    HCD ignores the MAXDEV parameter of       *
    *                    the RESOURCE statement in the deck        *
    *                    and sets the maximum number of            *
    *                    devices to the predefined maximum         *
    *                    for the processor type.                   *
    *                    When migrating for older processor        *
    *                    types: complete migration behaves         *
    *                    as described above.                       *
    *                    Incremental migration sets the            *
    *                    maximum number of devices as              *
    *                    specified in the deck.                    *
    *                    If 0 (zero) is specified in the deck,     *
    *                    incremental migration leaves the          *
    *                    existing value unchanged.                 *
    *                 3. (z/VM V5R4 only)                          *
    *                    When connecting a coupling channel        *
    *                    of type CS5:                              *
    *                    HCM now correctly proposes 8 as the       *
    *                    default number of CF devices              *
    *                 4. When working with a coupling connection   *
    *                    between distinct processors over          *
    *                    spanned CS5 channels:                     *
    *                    when changing the lowest channel          *
    *                    subsystem on one end of the connection    *
    *                    (by adding / removing an LPAR to/from     *
    *                    the access list of the channel),          *
    *                    HCD now warns with message CBDG422I       *
    *                    that this may require an activation of    *
    *                    the connected processor. The wording      *
    *                    of message CBDG422I (MSGCBDG422I)is       *
    *                    generalized to refer to 'coupling'        *
    *                    chpids (rather than specifically to       *
    *                    CIB chpids).                              *
    *                                                              *
    *                 KEYWORDS: D/T2964                            *
    ****************************************************************
    Various fixes
    

Problem conclusion

Temporary fix

Comments

  • n/a
    

APAR Information

  • APAR number

    VM65693

  • Reported component name

    HCD/HCM

  • Reported component ID

    568411219

  • Reported release

    540

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-26

  • Closed date

    2015-03-25

  • Last modified date

    2016-12-02

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

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

    UM34573 UM34574

Modules/Macros

  • CBDEM00G CBDG422  CBDG422I CBDMDCPP CBDMDCP3 CBDMGCP0 CBDMGPR0
    CBDMMPRC CBDMSVCH
    

Fix information

  • Fixed component name

    HCD/HCM

  • Fixed component ID

    568411219

Applicable component levels

  • R540 PSY UM34573

       UP15/03/26 P 1501

  • R620 PSY UM34574

       UP15/03/26 P 1601

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":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"540","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
02 December 2016