After upgrading Sysview for DB2 the errors DBG72032E Error Invoking IMOD and GRX0043I Execution Error occur
book
Article ID: 189233
calendar_today
Updated On:
Products
Bind Analyzer for DB2 for z/OSSQL-Ease for DB2 for z/OSSYSVIEW Performance Management Option for DB2 for z/OSPlan Analyzer for DB2 for z/OSSubsystem Analyzer for DB2 for z/OSDatabase Management for DB2 for z/OS - Performance SuiteDatabase Management for DB2 for z/OS - SQL Performance SuiteInsight Performance Monitor for DB2 UDB for z/OS
Issue/Introduction
After upgrading Sysview for DB2 the following error messages occur: DBG72032E DSN 08:20:19 ERROR INVOKING IMOD $DBGL_ILOGMSG ON ISERV ISRV (RC=-225-00000004) FOR THE FOLLOWING EXCEPTION: DBG11016I DSN 08:20:19 GSS ERROR: IMOD was not found. Also, the GSS task output showed: GRX0043I Execution Error....
Environment
Release : 19.0, 20.0
Component : CA Sysview for DB2 Performance Monitor (IDB2)
Cause
The cause of the DBG72032E error was due to the MSSUB parameter being specified in IDB2's sysparms not correctly referencing the GSS' SSNAME value. Also, the GRX0043I execution error message was caused by an old IMOD dataset being referenced.
Resolution
The DBG72032E error was corrected by changing the default MSSUB parameter value (ISRV) in IDB2's sysparms to the GSS task's SSNAME value of GSS1. The GRX043I Execution error message in the GSS task joblog was corrected by reloading the IDB2 IMOD dataset with current IMODs.