Error GIM39201S ABEND CODE: 106 REASON CODE: 0C applying CARS2207 via z/OSMF
search cancel

Error GIM39201S ABEND CODE: 106 REASON CODE: 0C applying CARS2207 via z/OSMF

book

Article ID: 248978

calendar_today

Updated On:

Products

DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

Applying the CARS2207 level for Database Management Solutions for Db2 for z/OS with z/OSMF Software Update, got the following SMP/E error message:

GIM39201S ** DICTIONARY MODULE GIMCPDS COULD NOT BE LOADED. SMP/E COMPACTION SERVICE PROCESSING IS STOPPED. ABEND CODE:
             106 REASON CODE: 0C
GIM22601I    APPLY PROCESSING FAILED FOR SYSMOD LU02151. 
 
GIM20501I    APPLY PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 12.                         
 
GIM20502I    SMP/E PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 12. SMP/E IS AT LEVEL 37.11.

Then PTF LU02151 was applied separately, but got the same error with next PTF in row. 
  
Module GIMCPDS was in link-list so there should be no problem in the load. 

Environment

Release : 20.0

Component : DB2 Common Components

Resolution

The explanation about ABEND CODE: 106 REASON CODE: 0C was as follows:
  
106 
  
Explanation
An error occurred during processing of a LINK(X), LOAD, ATTACH(X), or XCTL(X) macro.

An error was detected by the control program when it attempted to fetch the requested program into virtual storage. The return code in register 15 identifies the error; see accompanying messages IEW4005I, CSV031I, and CSV028I to determine the reason code. For PMLOADER internal errors not listed, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.

Code
Explanation
0B
An error occurred during FETCH processing or in one of the routines that gets control as a result of FETCH processing.
0C
Not enough storage was available for FETCH to get storage for the module or control blocks.

Increased the z/OSMF Region from 50M to 128M as described in the following IBM link: 
  
IZUPRMxx reference information
 
With the new Region size the z/OSMF Apply worked fine.