Why did RC/Merger create HOLD tablespace

Products

• RC/Merger for DB2 for z/OS

Issue/Introduction

Why does RC/Merger for Db2 for z/OS (RMM) generate the following messages:

RCM0214I - GROUP ATTACH NAME ssid PROVIDED. MEMBER NAME ssid 
WILL BE USED FOR DB2 CONNECTIONS. 

RCM0139I - CREATING CA-DB2 HOLD TABLESPACE &DBNAME..CADB2TS. 
RCM0137I - TABLESPACE CREATED SUCCESSFULLY. SQLCODE = 0. 

RCM0140I - CREATING CA-DB2 HOLD TABLE CADB2ID.#####00017xxxxxxx. 
RCM0137I - TABLE CREATED SUCCESSFULLY. SQLCODE = 0.

Resolution

This is expected behavior as part of RESERVE OBID call in RC/Merger. 
RC/Merger reserve the OBID of the target table space and table to match with the OBIDs of the source table space and table. 
These HOLD table space and table objects will be deleted in RC/Merger TABLE CALL. See the information messages below. 

RCM0134I - DROPPING CA-DB2 HOLD TABLE CADB2ID.#####00003xxxxxxx. 
RCM0125I - DROPPING THE CA-DB2 TABLESPACE dbname.tsname. 

RESERVE CALL example: 

.CALL RCMERGER PARM(ssid,RESERVE) 
.DATA 
DATABASE (dbname) 
RESOBID (00003) 
.ENDDATA 

RCM0100I - RC/MERGER BEGINNING. 

RCM0139I - CREATING CA-DB2 HOLD TABLESPACE &DBNAME..CADB2TS. 
RCM0137I - TABLESPACE CREATED SUCCESSFULLY. SQLCODE = 0. 

RCM0140I - CREATING CA-DB2 HOLD TABLE CADB2ID.#####00003xxxxxxx. 
RCM0137I - TABLE CREATED SUCCESSFULLY. SQLCODE = 0. 

RCM0101I - RC/MERGER COMPLETED SUCCESSFULLY. 
RETCODE = 0 


TABLE CALL example: 

.CALL RCMERGER PARM(ssid,TABLE) 
.DATA 
.AUTH xxxxx 
CREATE TABLE xxxxxx.xxxxxxxxx 
( COL1 INTEGER 
, COL2 INTEGER 
.... 
.ENDDATA 

Execution of above TABLE call will delete the HOLD tablespace and table objects before creating the actual target table space and table objects.