IBM Support

Guardium STAP for IMS not initializing in IMS control region

Troubleshooting


Problem

Guardium stopped working after installing the RSU2109 level of maintenance for v10.1.3
It doesn't initialize correctly in these IMS regions anymore.
We have this level of maintenance installed in other sysplexes and it is working fine.

Diagnosing The Problem

We need to determine what (if any) AUI messages appear in the IMS control region, and take any action a warning or error message would indicate.
Check to see whether no AUI messages appear is that the IMS control, region STEP/JOBLIB concatenation has the AUI product library (AUIIMOD) 1st in the data set concatenation.  Another instance of logger exit DFSFLGX0 might be taking control.
Another is to ensure that the LOGWRT EXIT definition (if you are using that construct) in the DFSDFxxxx IMS proclib is in the correct format.
(EG: EXITDEF=(TYPE=LOGWRT,EXITS=(AUIFLGX0)))    

Resolving The Problem

Customer added “EXITDEF=(TYPE=LOGWRT,EXITS=(IRMFLGX0))” to DFSDF000 to use the BMC recon reorg process without realizing that it could would affect the STAP process.  After changing the EXITDEF settings, the STAP is now working correctly.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCJM6A","label":"IBM Security Guardium S-TAP for IMS on z\/OS - SSCJM6A"},"ARM Category":[{"code":"a8m0z000000Gp0IAAS","label":"STAP"}],"ARM Case Number":"TS008774652","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]

Document Information

Modified date:
11 January 2023

UID

ibm16854681