Why do I receive a "BMC256855E MAINVIEW/IP TACSNMPM module not found" message after upgrading to MainView for IP version 3.5.00?

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView for IP



    QUESTION:

    Why do I receive a "BMC256855E MAINVIEW/IP TACSNMPM module not found" message after upgrading to MainView for IP version 3.5.00?
    The following message is issued during the startup of MainView for IP 3.5.00:
    BMC256855E MAINVIEW/IP TACSNMPM module not found, verify STEPLIB contains TOSZLINK libs, SNMP API failed


    ANSWER:

    The reason for this is that MainView for IP 3.5 now uses the IBM SNMP API Manager interface to collect OSA and SNMP statistics. The TOSZLINK library is now required in the STEPLIB DD of the MainView for IP PAS for the SNMP API interface to gather data.

    The SNMP Manager API is used to collect both SNMP MIBs and OSA MIBs (MIB = Management Information Base). The SNMP Manager API requires an SNMP Manager API configuration file only if using SNMPv3. The configuration file must be a z/OS UNIX file. It is defined on the MVIPCNFD view.
    The MainView for IP PAS will now require the hlq.TOSZLINK dataset in STEPLIB along with the hlq.BBLINK dataset. The SYS1.SIEALNKE file must reside in the LNKLIST as well.

    Further details are available in the MainView for IP Customization guide and also the following Technical Bulletin: http://documents.bmc.com/supportu/documents/09/12/480912/480912.pdf


    Article Number:

    000146069


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles