System Image Version Number could not be changed on NetMaster region restart

Products

• NetMaster Network Automation
• NetMaster Network Management for SNA
• NetMaster Network Management for TCP/IP
• NetMaster File Transfer Management

Issue/Introduction

Our customer created a new System Image using Version Number 0005.  He changed it from 0002 to 0005 on group AUTOIDS - Automation Identifiers (issue

/PARMS and then select $RM AUTOIDS).  It was saved with PF3.

-

It was expected that, by the next startup of NetMaster, Version Number 0005 would be loaded.  But when they looked again in $RM AUTOIDS, after

NetMaster was recycled, Version Number was back to 0002--and it was loaded.  

Environment

OS: z/OS.

Cause

-

Resolution

It was found out that INIFILE was being used on the NetMaster startup and in it there was an entry which caused Version Number 0002 to be loaded when

NetMaster was started up.  It was going to be changed to the right Version Number--and the NetMaster region restarted.

Additional Information

See more INIFILE information here:

NetMaster 12.2:  Deploy and Configure on Multiple Systems .

NetMaster 13.0:  Configure Your Region to Start From an Initialization File .