SYSTEM IMAGE VERSION CANNOT BE CHANGED
Article ID: 115283
Updated On:
Products
CMDB for z/OS
NetSpy Network Performance
NetMaster Network Automation
SOLVE
NetMaster Network Management for SNA
NetMaster Network Management for TCP/IP
NetMaster File Transfer Management
Issue/Introduction
Cust created a new system image: Version 0005. Cust changed this from version
0002 to 0005 in the AUTOIDS - Automation Identifiers (/PARMS then select
$RM AUTOIDS). It was saved with PF4 or PF3 (cust tried both).
So cust expected by the next startup of NetMaster that image 0005 would be load-
ed. But when they looked again in the $RM AUTOIDS, after NetMaster was
recycled, the version was back to 0002 and image 0002 was loaded.
0002 to 0005 in the AUTOIDS - Automation Identifiers (/PARMS then select
$RM AUTOIDS). It was saved with PF4 or PF3 (cust tried both).
So cust expected by the next startup of NetMaster that image 0005 would be load-
ed. But when they looked again in the $RM AUTOIDS, after NetMaster was
recycled, the version was back to 0002 and image 0002 was loaded.
Environment
OS: z/OS.
Resolution
Indeed cust found--from CA Support verification suggestion--that INIFILE was
being used on the NM startup and in it there was an entry which caused image
0002 to be loaded when NetMaster was started up. Cust was going to change
that to the right image.
being used on the NM startup and in it there was an entry which caused image
0002 to be loaded when NetMaster was started up. Cust was going to change
that to the right image.
Additional Information
See Product Region NCL Parameters on the NetMaster documentation for the
INIFILE parm details.
INIFILE parm details.
Feedback
Yes
No
Powered by
