Netmaster OPSYSIDS fails with N85723 AOM START FAILED, REASON, SUBREASON 003-003

Products

• NetMaster Network Management for TCP/IP
• SOLVE:Operations Automation

Issue/Introduction

The OPSYSIDS parameter group failed with

13.36.29 STC39553  SETSSI ADD,SUBNAME=OPER

13.36.29.31  BG-SYS    NETMBSYS   N12804 SYSPARMS AOMSSID=OPER OPERAND ACCEPTED.

13.36.39.44  BG-SYS    NETMBSYS   AOM START
13.36.39.44  BG-SYS    NETMBSYS   N85704 AOM START COMMAND ACCEPTED.
13.36.39.44  *000327*  NETMBSYS   N85723 AOM START FAILED, REASON, SUBREASON 003-003.
13.36.39.44  *000327*  NETMBSYS   N85724 DESC: SSI (SSAB) SETUP FAILED, RC: NO SSCT FOUND (SSID BAD).
13.36.39.44  BG-SYS    NETMBSYS   N85723 AOM START FAILED, REASON, SUBREASON 003-003.
13.36.39.44  BG-SYS    NETMBSYS   N85724 DESC: SSI (SSAB) SETUP FAILED, RC: NO SSCT FOUND (SSID BAD).
13.36.39.44  BG-SYS    NETMBSYS   N85724 DESC: SSI (SSAB) SETUP FAILED, RC: NO SSCT FOUND (SSID BAD).

 

 

Environment

Release : 12.2

Component : CA NetMaster Network Management for TCP/IP

Resolution

AOM START failed because the SETSSI command for the AOMSSID failed. 

The messages N85723 and N85724 generally indicate that the SSID is not known to the system.

The SETESSI command is intended to dynamically generate the SSI on the system so no definition in IEFSSNxx is needed.

Check the SYSLOG for the results of the SETSSI command. If this shows
IEFJ023I SETSSI ADD COMMAND FOR SUBSYSTEM OPER COMPLETED WITH ERRORS 
IEFJ026I SUBSYSTEM OPER IS ALREADY DEFINED TO THE SSI 

then the SSI definition already exists.

If you get other errors, there may be a problem with security.

Ensure that the Netmaster STC userid has permission to issue the SETSSI command.