The Database Management Post Install bind customization task failed when upgrading to r20 and Db2 12
Article ID: 209747
Updated On:
Products
Issue/Introduction
When running the Database Management solutions for Db2 for z/OS Bind Product Plans and Packages Customization task, ssid0002, it can fail with one of the following errors:
1. The GENRBIND step can fail with RC 12 and the following error messages:
**** ERROR
**** INSRSET rc= 12 SSID= ssid
**** Parmlib member SETUP00 contains an invalid value for
**** SSIDVER and/or SSIDMODE. You must correct the invalid
**** value then resubmit this job.
2. The FULLBIND step can fail with RC 08 and the following messages are issued for every BIND PACKAGE statement:
BIND PACKAGE(DGL1xxx_PUT_PFR) MEMBER(FRA@CHP) APPLCOMPAT ( ) VALIDATE ( RUN ) ISOLATION ( CS
) FLAG ( I ) RELEASE ( COMMIT ) DYNAMICRULES ( BIND ) DBPROTOCOL ( DRDA )
ENCODING ( EBCDIC ) EXPLAIN ( NO ) ;
IKJ56701I MISSING APPLCOMPAT LEVEL:++
IKJ56701I MISSING UP TO 9 CHARACTERS
Note the APPLCOMPAT parameter is blank.
Cause
There are incorrect Db2 version and mode definitions in the SETUP Parmlib member for this subsystem.
Resolution
Review the SETUPxx hlq.CDBAPARM member that is being used in this environment. Check whether the subsystem definition
includes SSIDVER and SSIDMODE parameters similar to the following:
SSIDVER (V12)
SSIDMODE (NFM)
SSIDVERF (V12R1M100)
SSIDVERC (V12R1M500)
If Function Level and Catalog Level are specified, do not specify values for Version and Mode.
These values are mutually exclusive and should not be used together.
For DB2 12 use Function Level (SSIDVERF) and Catalog Level (SSIDVERC). For example:
SSIDVERF (V12R1M100)
SSIDVERC (V12R1M500)
For DB2 11 use Version (SSIDVER) and Mode (SSIDMODE).
SSIDVER (V11)
SSIDMODE (NFM)
If the subsystem is a member of a data sharing Group, then ensure that the definitions for the
data sharing Group as well as for each of the data sharing members are also correct.
Additional Information
Feedback
