s0C4-4 on RULES Command after upgrading definitions for R17

Products

• SYSVIEW Performance Management

Issue/Introduction

In the process of installing SYSVIEW R17.  Attempt to follow the UpGrade MQ Channel Definitions Documentation.  I have exported the R16 Definitions 'MQSTHRSH and MQSSTATE.  When attempting to load updated Definitions to R17 Doc tells me to run the New Command Rules.  When I attempt to run the Rules command I get the following:

GSVX451E Abend S0C4-04 in RULES command
GSVX472I Userid NNNNNN Terminal XXXXXXXX Interface TSO
GSVX452I SYSVIEW SRB in control at entry to abend
GSVX453I Diagnostics for SRB in control at entry to abend
GSVX457I Psw 078C4000 930C9F40 Ilc 6 Intc 04
GSVX477I Key 8 State SUP Am 31 Asc AR
GSVX458I Module GSVXNUC  Addr 12AE2000 Offset 005E7F40
GSVX458I NucMod GSVXDSPR Addr 130C41A8 Offset 00005D98
GSVX450I FixLvl BASE
GSVX473I Routne BRWS$$   Addr 130C9CE0 Offset 00000260
GSVX459I Data at PSW addr 130C9F3A
GSVX460I E330200C 0017B902 00334780
GSVX455I General registers at entry to abend
GSVX467I   R0-R1   00000000_00000000 00000000_00000000
GSVX467I   R2-R3   00000000_00001000 00000000_00000000
GSVX467I   R4-R5   00000000_00000000 00000000_00000000
GSVX467I   R6-R7   00000000_126394D0 00000000_127BDB80
GSVX467I   R8-R9   00000000_1252CF44 00000000_1252C060
GSVX467I  R10-R11  00000000_130CC090 00000000_124D2000
GSVX467I  R12-R13  00000000_130C9CE0 00000000_12518AA8
GSVX467I  R14-R15  00000000_930C9E40 00000000_00000000
GSVX475I Access registers at entry to abend
GSVX461I  AR0-AR3  00000000 00000000 00000000 00000000
GSVX461I  AR4-AR7  00000000 00000000 00000000 00000000
GSVX461I  AR8-AR11 00000000 00000000 00000000 00000000
GSVX461I AR12-AR15 00000000 00000000 00000000 00000000

 

Going to need some assistance to get past this issue.

 

 

Environment

Release : 17.0

Cause

The abend was due to the SYSVIEW STC pointing to the same SECONDARY option parmlib member as the SYSVUSER STC.  

Resolution

The SYSVIEW STC task should be started using **.CNM4BRM(SVW$MAIN) containing the PRIMARY option identifier.   

The SYSVUSER STC task should be pointing to **.CNM4BPRM(SVW$USER) which contains the SECONDARY option identifier.   

In this case both tasks were pointing to the same member which had the SECONDARY option identifier.