If you have IMS regions that have SMU terminal security definitions, evaluate whether you need to convert the SMU security definitions to CA Top Secret, and whether the CA Top Secret should be user-based or terminal-based.
If you are converting the SMU terminal security for an IMS region that also uses the CA Top Secret IMS interface for command and transaction security, you already have security policy defined for your IMS transactions and commands. Examine the CA Top Secret policy to determine if the SMU terminal-based security definitions are redundant and can be eliminated.
If you are converting an IMS region that does not already use the CA Top Secret IMS security interface, or if CA Top Secret security for transactions or commands has been disabled in the IMS region, you probably do not have security policy defined for your IMS transactions and commands. The best practice implementation for CA Top Secret for IMS transactions and commands is a user-based security implementation. Determine who your IMS users are and what IMS transactions and commands they should have access to, and write your security policy accordingly. This is a manual process and the SMU terminal security definitions are usually of little help. If you decide on a terminal-based security implementation using automatic terminal signon, the SMU terminal security definitions provide the roadmap for the security policy.
Use the TSSISMU4 conversion program to migrate from SMU terminal security to CA Top Secret.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|