N21103 PRODUCT SNAACCESS NOT AUTHORIZED ON SECURITY AND SYSTEM SERVICES VERSION

book

Article ID: 104084

calendar_today

Updated On:

Products

CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:CA Mainframe Connector CA SOLVE:FTS CA SOLVE

Issue/Introduction

Trying to upgrade Solve Access Session Management to 5.0.

At region startup I see this message
N21103 PRODUCT SNAACCESS NOT AUTHORIZED ON SECURITY AND SYSTEM SERVICES VERSION V7.1 LEVEL 1108
Then region shuts down.
Following the message explanation, I find a PPREF='PROD=SNAACCESS' parameter in RUNSYSIN but this is the product I need to run.

Cause

This message 
N21103 PRODUCT SNAACCESS NOT AUTHORIZED ON SECURITY AND SYSTEM SERVICES VERSION V7.1 LEVEL 1108 

indicates that you are somehow pulling in an incorrect release of Management Services. That means there is a problem with which CC2DLOAD you are accessing. 

Management Services r7.1 is used for SOLVE:Operations 11.9 and will not function with SOLVE:Access. 
You may be seeing a different release - i.e. 5.4, 7.8 or something else; the results will be the same.
This always indicates that you are accessing an incorrect load library for the product you want to run.

Environment

Release: SLACCS00200-5.0-SOLVE:Access-Session Management
Component:

Resolution

Multiple products use Management Services (System Services) as the base product.
Examples: Netmaster, SOLVE:Access, SOLVE:Operations, SOLVE:Central, OPSWeb, Linux Connector, HISRV.

Our documentation for all such products states that the load library (it may be MSLOAD, CC2DLOAD or CC2DPLD) should be in the STEPLIB, never linklisted.

Possible causes:
1. Check the STEPLIB of your STC JCL to ensure that the STEPLIB is pointing to the correct dataset.
2. If you use aliases, please ensure that is set up correctly and you are pointing to the correct alias for your product.
3. Some customers combine all load module into one library. If that is the case, your version of the modules may have been overwritten.
4. Check your linklist for conflicting modules using ISRDDN.
    To do so, issue TSO ISRDDN from the command line in TSO.  Hit enter.
     Issue LINKLIST from the command line. Hit enter.
     Issue MEMBER NM001 from the command line. Hit enter.
     A warning screen will pop up. Change 'Type yes to proceed' to YES and hit enter.
     It will now search through all datasets in your linklist for the requested module and display the first library where it is located.

If none of the above is helpful, please open a case at support.ca.com for further assistance.