IV31586: REQUESTING DOCUMENTATION CLARIFICATION FOR MMCV2/MMCV4

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Issue: The distinct naming convention using the hardware name of
    MMCv2
    and the current trend for customers to upgrade the MMCv4(s) is
    confusing the customer.  It s unclear if the MMCv2 counts
    Triggers
    (PCALCs) and Limits are applicable for use with MMCv4 entities.
    The
    customers are attempting to do searches on MMCv4 and are only
    getting a
    few hits.
    
    This issue was introduced starting with Release 37.0 when MMCv4
    first
    were being FOA.  However, it s not until know that the
    deployment of
    MMCv4(s) is being more common.
    
    Speaking with the System Design Engineers and they indicated
    that it
    would be best just to update the documentation verses attempting
    to
    change or add new counts/names.
    

Local fix

Problem summary

  • PROBLEM DESCRIPTION:
    The distinct naming convention using the hardware name of MMCv2
    and the current trend for customers to upgrade the MMCv4(s) is
    confusing the customer.  It's unclear if the MMCv2 counts
    Triggers (PCALCs) and Limits are applicable for use with MMCv4
    entities. The customers are attempting to do searches on MMCv4
    and are only getting a few hits.
    This issue was introduced starting with Release 37.0 when MMCv4
    first were being FOA.  However, it's not until now that the
    deployment of MMCv4(s) is being more common.
    Documentation updates are requested for critical triggers/limits
    related to MMCv2 and MMCv4 for consistency, rather than
    attempting to change or add new counts/names.
    PROBLEM SUMMARY:
    Confused naming convention in current critical triggers/limits
    related to MMCv2, when MMCv4 is later introduced but missing
    MMCv4 keyword in documentation - resulting in inaccuracy
    searches by customer when the deployment of MMCv4(s) is being
    more common. Documentation to include both keywords, MMCv2 and
    MMCv4, in its corresponding critical trigger/limit.
    RESOLUTION:
    
    Updates to PDR documentation (Customer Description) for critical
    triggers/limits below - to accommodate meaningful descriptions
    related to both MMCv2 and MMCv4 for consistency purpose.
    
    " T_CDMA_MMCv2_AS_PO_%
    " T_CDMA_MMCv2_CDN_PO_%
    " T_CDMA_MMCv2_HLVR_PO_%
    " T_CDMA_MMCv2_RCS_AUX_PO_%
    " T_CDMA_MMCv2_SS7_PO_%
    " T_CDMA_MMCv2_UX_IPMGR_PO_%
    " L_CDMA_MMCv2_AS_PO_%
    " L_CDMA_MMCv2_CDN_PO_%
    " L_CDMA_MMCv2_HLVR_PO_%
    " L_CDMA_MMCv2_RCS_AUX_PO_%
    " L_CDMA_MMCv2_SS7_PO_%
    " L_CDMA_MMCv2_UX_IPMGR_PO_%
    CONCLUSION:
    This is projected to be fixed in R40.1. Note that this is
    subject to change at the discretion of IBM.
    TEMPORARY FIX:
    NA
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV31586

  • Reported component name

    PROSPECT ALLUC

  • Reported component ID

    572POEMAL

  • Reported release

    R34

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-07

  • Closed date

    2012-11-27

  • Last modified date

    2012-11-27

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

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

Fix information

Applicable component levels

  • RR40 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Prospect

Software version:

R34

Reference #:

IV31586

Modified date:

2012-11-27

Translate my page

Machine Translation

Content navigation