Database Management Post Install processing job ssid0001 Create Required Db2 Objects fails IKJ56241I SPECIFIED UNIT IS UNDEFINED

Products

• Database Management for DB2 for z/OS - Administration Suite
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - Recovery Suite
• Database Management for DB2 for z/OS - SQL Performance Suite
• Database Management for DB2 for z/OS - Utilities Suite
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

What could be the reason why the Database Management Solutions post install processing job ssid0001 Create Required DB2 Objects fail with:

.SYNC 180       'UNLOAD TABLE PTI.PDT_DYNAMREQ_180'
.AUTH authid
.ALLOC FI(SYSCTL00) DUMMY 
.ALLOC FI(SYSREC00)                                                    + 
       DA('xxxx.xxxx.PTDB.TID1109.xxxx.RDATA')                         + 
       LABEL(1,SL)                                                     + 
       UNIT(CART)                                                      + 
       RETAIN                                                          + 
       NEW CATALOG
IKJ56241I DATA SET xxxx.xxxx.PTDB.TID1109.xxxx.RDATA NOT ALLOCATED+ 
IKJ56241I SPECIFIED UNIT IS UNDEFINED

Cause

Invalid UNIT for the current site is generated in the allocation statement.

Resolution

1. Check the generated DDL for errors during the .CALL SNAPSHOT due to the ssid0000 Compare job runs with the Recovery = Y option.
2. Any of the unload processes that are dynamically generated during the .CALL SNAPSHOT recovery are very difficult to control. 
   Please rerun the ssid0000 Compare with Recovery = N instead to eliminate the .CALL SNAPSHOT process.
3. Delete the .CALL SNAPSHOT control cards in the ssidDDL member down to the .SYNC x and resubmit the ssid0001 job restarting at the EXECRBP2 step.
4. The ssidDDL member should be updated to correct the CART unit so that a valid UNIT is being used. The install job uses a internal Utility Model. It is internal because at this Post Install the models have not been created for RC/Migrator yet. The actual text of the model can be found on hlq.CDBASAMP(RMMODTXT). It is called MODELDBA as you can see in the sysout.

Model ID ===> @DEFAULT
Model Creator ===> MODELDBA

Control of the dataset allocations are difficult because so much is done dynamically that you cannot see in the ssidDDL member for the SNAPSHOT process.

The SNAPSHOT process dynamic allocation process uses model RMMODTXC (Broadcom utilities) or RMMODTXI (IBM utilities). These models can be found in library CDBASAMP.
The tape unit is hardcoded as CART.

Customization of the TAPE UNIT of CART is difficult with this configuration.  We do not recommend editing the RMMODTXC / RMMODTXI members.

Additional Information