Troubleshooting
Problems sometimes occur when you start BMC AMI Security Policy Manager for the first time. These are usually due to unresolved issues during the installation process. Many other problems are caused by RACF or Top Secret authority problems, or other post-installation setup issues.
As a starting point, check the printed output from SPM JESMSGLG, JESYSMSG, and RSSPRINT. Look for SPM prefixed error messages as these will often give you a clue to the problem. All SPM messages can be found in theMessage library. Also, check the MVS console output to see whether any error messages were issued there.
Check the following:
- SPM load library is APF authorized.
- Correct RACF or Top Secret resources and user READ authorities defined.
- If RACF or Top Secret resources are defined in anything other than FACILITY class, the alternative class is specified on the ClassName parameter in the configuration data set.
- JCL refers to the correct configuration data set (DD name RSSPARM).
- CustomerID and CustomerKey parameters are correct. SPM does not start up if the combination of these parameters is not valid and accurate.
Where to go from here
When SPM is running as expected, you are ready to configure parameters.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*