Troubleshooting

Issues sometimes occur when you start RSS for the first time. These are almost always due to unresolved issues during the installation process. Many other issues are caused by issues with RACF authority or other postinstallation setup issues.

As a starting point, check the printed output from RSS JESMSGLG, JESYSMSG, and SYSPRINT. Look for RSS prefixed error messages, as these often give you a clue to the issue. All RSS messages can be found in the Message library.  Also, check the MVS console output for error messages. Make sure that you have completed all the steps in Installing. 

Related topics

Installing

Messages

Check the following:

  • RSS load library has been APF authorized
  • Correct RACF resources and user READ authorities to those resources have been appropriately defined
  • If your RACF resources are defined in anything other than FACILITY class, that 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. RSS does not start up without the combination of these parameters being valid and accurate.

To debug connectivity and data exchange issues, activate RSS HTTPTrace, which traces HTTP traffic generated by user interactions with the RSS browser interface.

For application-specific diagnostic information, activate the RSS APPTrace.

For user interface issues, activate the ISPF trace.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*