IBM Support

II09201: INFO APAR FOR MULTISYSTEM MANAGER MSM V2 DOCUMENTATION CHANGES AND/OR ADDITIONS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • This APAR is to document MultiSystem Manager MSM V2 manual
    changes and/or additions.
    *
    All MultiSystem Manager V2 Manuals.
    Section:  Post-Installation Problem Determination Hints
    Addition:
    COMMAND TREE/2 FAILURES
    =======================
    IF YOU GET INTERMITTENT FAILURES WITH MSM COMMANDS ISSUED FROM
    GMF INDICATING THAT THE DESTINATION ADDRESS IS NOT KNOWN,
    THERE MAY BE PROBLEMS WITH THE WAY THE GETTOPO COMMANDS ARE
    BEING SPECIFIED.
    
    ONE SUCH PROBLEM MAY ARISE IF THE FOLLOWING GETTOPOS ARE
    ISSUED:
    
      GETTOPO XXXRES,SP=NETA.NETV1.LU1,......
      GETTOPO XXXRES,SP=NETB.NETV1.LU2,......
    HERE, THE SAME DOMAIN NAME (NETV1) IS BEING USED WITH SERVICE
    POINTS (LU1 AND LU2) WHICH RESIDE IN DIFFERENT NETWORKS
    (NETA AND NETB). THIS CAUSES PROBLEMS FOR COMMAND TREE/2 WHICH
    MAY RESULTS IN COMMANDS BEING ROUTED TO THE WRONG NETWORK.
    
    TO AVOID THIS PROBLEM, MAKE SURE THAT THE DOMAIN SPECIFIED
    IN THE GETTOPO COMMAND IS FOR THE DOMAIN WHICH OWNS THE
    SERVICE POINT.  FOR EXAMPLE:
    
      GETTOPO XXXRES,SP=NETA.NETV1.LU1,......
      GETTOPO XXXRES,SP=NETB.NETV2.LU2,......
    ***************************************************
    
    The MultiSystem Manager home page has moved from
    
        www.raleigh.ibm.com/svd/product/msmprod.htm
    
    It can now be accessed at
    
        www.networking.ibm.com/msm/msmprod.htm
    
    Wherever the old URL is documented,
    it should be replaced with the new URL.
    
    As an example; the NetView MultiSystem Manager manuals,
    Chapter 1, under 'Creating Applications to Manage New
    Topologies', in the section titled 'Learning More
    About MultiSystem Manager Tools'.
    All MultiSystem Manager V2 manuals.
    Chapter 4.  Operation
    Section:  Issuing Commands
    
    Addition:
    
    New paragraph at end of section.
    
    Generic Commands (Current Status, Activate, Inactivate,
    Recycle) are not supported by MultiSystem Manager.
    They can be implemented using the BLDVIEWS utility.
    For information on BLDVIEWS, see "Supplemental Tools
    and Utilities" in Chapter One of this manual.
    
    ************************************************************
    
    BLDVIEWS manual
    Section:  Other Functions
    
    Change:
    
    Under "Generic Commands" within the "Other Functions"
    section of the BLDVIEWS manual, the paragraph that discusses
    generic commands against aggregate resources should be
    replaced with the following paragraph:
    
    The NGMF command exit DUICNATV will not allow you to issue
    generic commands against aggregate resources.
    BLDVIEWS and NETVCMDX will allow you to set the generic
    commands on aggregate resources.
    NETVCMDX is available from MKTTOOLS.
    The MKTTOOLS repository can be accessed by your
    IBM representative by issuing the VM command
    'TOOLCAT MKTTOOLS' and then selecting the MSMCMD31 package.
    
    ************************************************************
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II09201

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1996-01-22

  • Closed date

  • Last modified date

    1997-04-17

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
17 April 1997