Applying maintenance. Compare step receives RMA256E MODEL REQUESTED NOT FOUND. MODELID @DEFAULT CREATOR MODELDBA
Article ID: 410459
Updated On:
Products
Issue/Introduction
RMA383I MODEL4 @DEFAULT
RMA383I MODEL4C MODELDBA
RMA383I MODDSNMK %USERID..%DSNQUAL2..%DSNQUAL3..%TOSSID
RMA383I MODLARGE 1000000
RMA383I MODDISK SYSALLDA
RMA383I MODTAPE 3490
RMA256E MODEL REQUESTED NOT FOUND. MODELID @DEFAULT CREATOR MODELDBA
POST INSTALL ANALYSIS COMPLETED, RETURN CODE = 16
Environment
DB2 for Z/OS
Cause
hlq.CDBASAMP(RMMODTXT) was missing.
Resolution
The way this works is that the COMPARE step of the Post Install has to be generated to produce any DDL statements and utility statements to make the requisite updates to the PTDB database in support of the PTF's being applied.
The COMPARE step calls RC/Compare which is part of RC/Migrator. RC/Compare uses utility MODELS to generate the required utility statements like unloads, loads etc to complete the updates on PTDB.
Normally when using RC/Compare these models are already installed for users to use.
During a Post Install or an initial install the install process can't assume that the RC/Migrator models have been installed.
So, what it does is it has its own "internal use only" model on hlq.CDBASAMP(RMMODTXT) which is used just for Installs and Post Installs when the COMPARE step is carried out. It comes with the install files. It must be there.
RMMODTXT contains a model called MODELDBA.@DEFAULT.
It never exists on RC/Migrator but is only used during the COMPARE step by the Post Install so don't look for it on RC/Migrator Utility Models because it won't be there.
Error message RMA256E MODEL REQUESTED NOT FOUND. MODELID @DEFAULT CREATOR MODELDBA
Indicates that MODELDBA.@DEFAULT was not found in order to complete the Compare step.
Additional Information
In previous releases member RMMODTXT used to be found on hlq.SRCLIB instead of the current hlq.CDBASAMP
The JCL in the Post Install job ssid0000 should look like:
//QIMODTXT DD DISP=SHR,
// DSN=hlq.CDBASAMP(RMMODTXT)
Feedback
