SSID, SSI SSID, AOMSSID....which one is what?

book

Article ID: 53274

calendar_today

Updated On:

Products

CA CMDB for z/OS CA NetSpy Network Performance CA NetMaster Network Automation CA SOLVE CA NetMaster Network Management for SNA CA NetMaster Network Management for TCP/IP CA NetMaster File Transfer Management CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:FTS CA SOLVE

Issue/Introduction

Description:

Describe the various Subsystem IDs (SSIDs) and their use within SOLVE/Netmaster.

Solution:

The definition and utilization of the various Subsystem IDs within Netmaster can be confusing.
Here is a description of the various SSID definitions and their functions.

  1. In the NetMaster SSI Started task, the SSISYSIN or SSIPARMS defines a Subsystem ID with the parameter SSID=xxxx.

    The Reference Guide states

    For each region that you want to connect to the SOLVE SSI, specify the SSID in either the Sub-System Interface ID field of the SSI parameter group in Customizer, or the JCL parameter in the region's RUNSYSIN member.

    Please note that by default it may appear in both places at this point. Plans are in place to change that in future.

    and further....

    SSID={ * | name }
    Specifies the subsystem ID (SSID) that this invocation of the SSI is to use.

    Note: The SSID does not need to be defined explicitly, but can be defined automatically.

    Limits: If an asterisk (*) is specified (the default), the first 4 characters of the SSI job name are used.
    If name is used, it must be a valid 1- to 4 character name. The first character must be alphabetic or national and the remainder alphanumeric or national.

    Note also this related parameter that causes an action to occur by default:

    ADDSSID={ YES | NO }
    Specifies whether the SSID is defined automatically if an SSID is not found when SOLVE SSI starts.

    If YES is specified, the SSID is defined automatically. If NO is specified, the SSID must be defined manually in the SYS1.PARMLIB(IEFSSNxx) member.

  2. In the NetMaster region, the RUNSYSIN defines a subsystem ID with the parameter PPREF='SSID=xxxx' to facilitate connection of the region to your SSI.

    The Reference Guide states

    SSID={ NO | * | name }
    Specifies whether to establish a connection to a SOLVE Subsystem Interface (SSI) during initialization.

    If NO is specified, then no connection to a SOLVE SSI is attempted. The connection is started (or attempted) only if the SSI parameter group requests a connection. If an asterisk (*) is specified, then an SSID of the first four characters of your product region's job name is used.

    If name is specified, then a specific SSID must be entered. If * or name is specified, then an attempt to connect to the SSI is made immediately. If it fails, it retries every n seconds, depending on the value in the SSI parameter group.

  3. Then we have the AOMSSI, which will be located in the /PARMS OPSYSIDS parameter group once the region has been started. Its purpose is to enable system commands to be issued from within Netmaster.

    Please note that when installing, even if you elect to migrate your VFS file, the proper value for this parameter must be entered during selection of the install parameters when building the region.

    The Reference Guide states

    AOMSSID={ * | sub-system-id }

    Specifies the subsystem ID to be used by SYSCMD facility. The asterisk (*) uses the first four characters of the job name or started task (STC) name.
    Default: NETM

    Please be aware that the default value stated is currently incorrect; at this point in time, the value defaults to OPER. The doc and code will be aligned in the next release.

So in actuality, there is one SSID for the Netmaster SSI address space, and an AOMSSID for the SOLVE/Netmaster region. The confusing factor lies in the fact that you must point the region to the SSID of the SSI Started task, then define another subsystem ID that the Netmaster region actually uses itself.

Environment

Release: ESBNSP99000-11.6-NetSpy-Premier Support
Component: