Why does CA NetMaster issue a "D M=CPU" command while initializing?
Article ID: 188856
Updated On:
Products
CMDB for z/OS
NetSpy Network Performance
NetMaster Network Automation
NetMaster Network Management for SNA
NetMaster Network Management for TCP/IP
NetMaster File Transfer Management
SOLVE
Issue/Introduction
The NetMaster region issues a D M=CPU command during the initialization phase. What is the reason that command is issued?
Environment
Release : 12.2
Component : CA NetMaster Network Management for TCP/IP
Resolution
The reason NetMaster does this is to try to ascertain the CSS and MIF information for the Local system, which is then used for correlating information required by Netmaster OSA monitoring. PTF RO98166 introduced this behaviour.
Basically, without this information, monitoring of OSA SNMP based attributes fails when running under LPARs defined with LCSS IDs (Logical Channel Subsystem ID) not equal to zero.
The pair of values (LCSS ID + MIF ID) represents an LPAR which is then used in SNMP requests to determine the appropriate OSA values.
Basically, without this information, monitoring of OSA SNMP based attributes fails when running under LPARs defined with LCSS IDs (Logical Channel Subsystem ID) not equal to zero.
The pair of values (LCSS ID + MIF ID) represents an LPAR which is then used in SNMP requests to determine the appropriate OSA values.
Additional Information
If NetMaster is not authorized to issue this command, CA Top Secret returns the following messages:
D M=CPU
IEE345I DISPLAY AUTHORITY INVALID, FAILED BY SECURITY PRODUCT
TSS7250E 136 J=nmstc A=nmacid TYPE=OPERCMDS RESOURCE=MVS.DISPLAY.M
TSS7251E Access Denied to OPERCMDS <MVS.DISPLAY.M>
Feedback
Yes
No
Powered by
