SSM STCTBL IPL State Audit

book

Article ID: 212959

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

We seem to be having issues with the IPL state for started tasks defined in STCTBL being changed to IPL.  I think we have someone changing things they do not know about, but I was wondering if you had ever heard of such a thing.  We only IPL our LPARs once a quarter, so we have a lot of quiet time in between.  Is there a way to audit changes to STCTBL perhaps?

Environment

Release : 13.0 13.5 14.0

Component : OPS/MVS

Resolution

The IPL_STATE column is not monitored by default but you can use the SSMMONITOREDCOLx parameters that in combination with SSMAUDIT set to YES will produce OPS7914T messages in the OPSLOG every time the value of this column changes. Sample message:

OPS7914T SSMv2 AUDIT: STCTBL.resource UPDATED by userid TABLE-EDITOR IPL_STATE=IPL     

You can change both parameters dynamically at the OPSVIEW panel 4.1.1:

OPS/MVS Parms ------ XE65 --- O P S V I E W ------------------- Subsys
Command ===>                                                   Scroll 
================================ Display Profile =====================
Name: SSMMONITOR    Value:                 Type:          Group:      
Description:                                              System: *LOC
======================================================================
 Line commands: S Show additional information                         
  Name                Value               Description          Row 1 o
_ SSMMONITOREDCOL1    'IPL_STATE'         SSM MONITORED COLUMN NAME 1 
_ SSMMONITOREDCOL2    ''                  SSM MONITORED COLUMN NAME 2 
_ SSMMONITOREDCOL3    ''                  SSM MONITORED COLUMN NAME 3 
_ SSMMONITOREDCOL4    ''                  SSM MONITORED COLUMN NAME 4 
_ SSMMONITOREDCOL5    ''                  SSM MONITORED COLUMN NAME 5 

The same for the SSMAUDIT parameter.