ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to resolve DBG11015E: IMOD ERROR RETURN CODE 16 REASON 22 error message?

book

Article ID: 127081

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

After changes over GSS got several DBG11015E error messages.
    
DBG11015E DB2A 16:00:16 IMOD ERROR RETURN CODE 16 REASON 22
DBG11016I DB2A 16:00:16 GSS ERROR: PC table entry not found
DBG11015E DB2A 16:02:36 IMOD ERROR RETURN CODE 16 REASON 22
DBG11016I DB2A 16:02:36 GSS ERROR: PC table entry not found
DBG11015E DB2A 16:09:50 IMOD ERROR RETURN CODE 16 REASON 22
DBG11016I DB2A 16:09:50 GSS ERROR: PC table entry not found
 
Checked the MSSUB paramater to identify the GSS SSID in CA SYSVIEW for DB2 Data Collector and GSS started task but all the names were correct.

Environment

Release:
Component: IDB2

Resolution

The GSS started task was executed by program SRVSYS, the SRVSYS program is used to bring up a secondary GSS address space. There must also be a primary GSS address space. If this GSS started task is the only GSS address space running on the LPAR, you must change the JCL and execute PGM=GSSMAIN instead of SRVSYS.
Powered by Wolken Software