This article explains what is needed for current SSM users to go to CA OPS/MVS 12.3 and when they should set SSMVERSION=3.
- What do I need to do to my existing SSM configuration just to get OPS/MVS upgraded to release 12.3?
- Why would I need to set the SSMVERSION parm to ‘3’ in release 12.3?
- When migrating to r12.3, no changes or actions are needed to your existing SSM environment or OPS/MVS SSM related parameters. Meaning, it is not necessary to run any SSM conversion utility and no need to set the SSMVERSION parameter to ‘3’. Your existing SSM configuration will continue to run as-is without any processing issues.
- The SSM Policy Manager (OPSVIEW 4.11.P) was added in r12.3 and provides a series of walk through panels to assist in the configuration and maintenance of SSM Started Task resources (not intended to be used for any non STC related SSM table). It is primarily to be used by new SSM users that are looking to implement a simple but effective SSM component. If you have an existing SSM configuration AND you are interested in possibly utilizing the SSM Policy Manager, then as instructed within the ‘Converting to SSM V 3 documentation, you will be setting the SSMVERSION parm to ‘3’. Included within this conversion documentation, are be details of using the SSM Policy Manager with an existing environment.
Important Note: If you are not familiar with the details of any end user site specific customizations made to your existing SSM environment (specifically with the CURRENT_STATE rule packets, EOM detection that triggers your failure automation and your SSMBEGIN startup setup), then it is not recommended for you to convert to the SSM Policy Manager methodology. Doing so may result in SSM component/logic failures. You should continue to maintain and configure your SSM STC resources using the existing OPSVIEW utilities and any in-house documentation/procedures that you have been utilizing.