ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

OPSWEB--INIT FAILURE

book

Article ID: 112362

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

Upon activating the OPSWEB STC the failure screen is shown with message:

Current processing status: FAILURES

Cause

This is what happened during initialization:

N85723 AOM START FAILED, REASON, SUBREASON 003-003.

N85724 DESC: SSI (SSAB) SETUP FAILED, RC: NO SSCT FOUND
(SSID BAD).

NetMaster tried to initialize /PARM group OPSYSIDS--but could not find
(AOM) SSID=OPER defined     on the system.

From the online help of N85724 (for 003-003):

003 SSI (SSAB) SETUP FAILED. RC: reason

SSAB is the NetMaster SubSystem Anchor Block. There is one SSAB for each
SSI acquired by NetMaster, pointed to by the operating system SSCT (Sub-
System Communications vector Table) for the SSI. When AOM attempt-
ed to perform SSI setup, an error occurred. The following errors
are possible.

NO SSCT FOUND (SSID BAD). The supplied AOMSSID cannot be
found. Possibly, it is misspelt, or not in the subsystem definition
member (for example, IEFSSNnn on MVS systems).

-

Environment

OS: z/OS.

Resolution

The OPER subsystem was created dynamically and the problem was resolved.