Getting the SSM#CNTLGRP column not in STCTBL error in OPS/MVS; we did not convert to SSM version 3 (SSM V3).
Article ID: 6278
Updated On:
Products
Issue/Introduction
I am upgrading from an older release of OPS/MVS to a current release, and I am receiving error messages upon execution of command: SSM SG GRP=DB4. This group is defined under column GROUPNAME. It apparently is looking for column SSM#CNTLGRP. Did I miss something in the release notes? I only noted that this column requirement is for the System State Manager version 3(SSM V3) conversion. We are currently running SSM version 2 with no intention to convert to version 3.
Messages follow:
12:25:29.70 CVD5215 00000210 SSM SG GRP=DB4
12:25:29.70 TSU00636 00000210 OPS1370H CVD5215 X'0000' X'0000' X'0000' CVD5215 300 OPSNTFY900 SSMS procedures to set group DB4 to UP initiated.
12:25:29.70 TSU00636 00000010 OPSNTFY900 SSM procedures to set group DB4 to UP initiated.
12:25:29.70 STC00582 00000010 OPS3092H OI P(SSMGROUP) ARG(GRP(DB4) REQ(UP) TBL(STCTBL) CNN(CVD5215))
12:25:29.92 STC00582 00000210 OPS1370H OPSOSFT X'0000' X'4000' X'0000' CVD5215 300 OPSNOTIFYS SSM#CNTLGRP column not in STCTBL
12:25:29.92 STC00582 00000010 *OPSNOTIFY SSM#CNTLGRP column not in STCTBL
12:25:29.95 STC00582 00000210 OPS1370H OPSOSFT X'0000' X'4000' X'0000' CVD5215 300 OPSNOTIFY NoS tables selected
12:25:29.95 STC00582 00000010 *OPSNOTIFY No tables selected
12:25:30.02 STC00582 00000010 OPS3092H READY
Environment
OPS/MVS Event Management & Automation-for JES2
Cause
The OPS/MVS default SSMGROUP REXX rule program member was being called instead of the user modified SSMCNTL REXX rule program member.
Resolution
Take the following actions to remedy this situation:
1. In the SSMCNTL rule, find code for the group commands. This calls SSMGROUP OPS/REXX program.
2. Change SSMGROUP to SSMGRPU or some other name like it.
3. Re-enable and auto-enable the SSMCNTL rule.
4. In your user.OPSMVS.REXX dataset, change the member name SSMGROUP to SSMGRPU or your other chosen name.
5. Test this for positive results.
This should result in using your user modified SSMCNTL REXX rule program member instead of the Broadcom default SSMGROUP REXX rule program.
Additional Information
Feedback
