STATESET errors in OPS/MVS Event Management and Automation SSM
search cancel

STATESET errors in OPS/MVS Event Management and Automation SSM

book

Article ID: 73204

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

When attempting to use the 'W' option for a resource in SSM 4.11.2, the following error message is displayed. The process continues with the confirmation dialog and will shutdown the locally defined resources but it will not shutdown cross-system subrequisites.  

STATESET01 OPS/REXX EXEC OP411002 FAILED - DIAGNOSTIC DATA FOLLOWS                                  
STATESET02 OPS/REXX EXEC OP411002 FAILED - FAILING STMT # - 1  : 1099                               
STATESET03 OPS/REXX EXEC OP411002 FAILED - FAILING STMT - 1    :                                    
STATESET02 OPS/REXX EXEC OP411002 FAILED - FAILING STMT #      : 1100                               
STATESET03 OPS/REXX EXEC OP411002 FAILED - FAILING STMT        :                                    
STATESET04 OPS/REXX EXEC OP411002 FAILED - FAILING STMT RC     : 8                                  
OPS3730I STCTBL.ESPSYS RESOURCE: CURRENT=UP DESIRED=UP MODE=ACTIVE PMD=ACTIVE RMD=ACTIVE AMD=ACTIVE 
OPS7160E ERROR NEAR 'CSTATE FROM  WHERE NAME' INVALID TABLE NAME: WHERE  

Environment

OPS/MVS: 14.0; 13.5
        z/OS:   2.5; 2.4; 2.3

Cause

STATESET01-04 diagnostic errors will occur from OPSVIEW 4.11.2 and from direct invocations of the STATESET exec, however the code will continue to work and perform it's intended action/s.

Resolution

Users who ran across this issue in previous releases were advised to apply corrective maintenance to resolve a situation where diagnostic errors were produced; however, some additional steps were identified. This document aids the user community in gathering the documentation necessary to identify and resolve the issue. Once gathered, open a case with Support who will engage SE and provide a solution.

Step 1: Verify Maintenance

Ensure that all related maintenance is applied to all OPS/MVS systems. 

Maintenance Published Description Comments
LU03011 23 SEP 2021 SUBREQ sysplex variables not using the primary system name.  There were 2 bugs in SGUPDPRE that could cause the variables to get corrupted when cross system prereqs were changed or deleted. 

 

Step 2: Gathering Global Variable Documentation

After confirming maintenance, gather the following:

  • OPSVIEW 4.8 display of the sysplex variables that match these masks:
GLVPLXTS.'ssmplex'.'xstbl'.'xsres'.SSM#MOVMOD
GLVPLXTS.'ssmplex'.'xssys'.'xstbl'.'xsres'.SSM#MOVMOD
GLVPLXTS.MVSGPLEX variables from the impacted system(s)
GLVPLXTS.SUBREQ variables
  • Review the following REXX execs for changes:
SGUPDPRE and SGUPPLVA (found in your CCLXEXEC dataset)


Step 3: Gathering Sysplex Variable Documentation

Use the attached sample REXX below to gather sysplex variables from the impacted system(s)

  • Set the SSMPLEX var in the first instruction to your value and execute this from the system(s) experiencing the error
  • Rexx can be executed from your TSO session or in a server, which ever may be easier for you to gather and send the output

Additional Information

  • The error and documentation only impacts customers running SSMGAV2

Attachments

1660659766682__SPLEXVAR.txt get_app