RMA178E in DDLCOMP step of Post Install Compare(ssid0000) job

Document ID : KB000032859
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

The CA DB2 Post Install Tailoring for DB2 for z/OS (INS) ssid0000 Compare job is failing with message:

RMA178E DATASET NAME xxxxxxx.xxxx.DATA.E
IS USED BY TWO DIFFERENT UTILITIES IN THIS ANALYSIS OUTPUT.

 

Solution:

If  message RMA178E occurs in the DDLCOMP step there is something wrong with the Dataset Name Mask being used.  This mask is used to generate the dataset names used for utilities in the script such as UNLOAD, LOAD, and COPY.

When generating the COMPARE (ssid0000) job within Post Install a screen is presented with parameters one of them is:

     Dataset Name Mask.........> %USERID..%DSNQUAL2..%DSNQUAL3..%TOSSID

This should not be modified, these are automatic symbolics that will get resolved when executed.  In the generated JCL the mask shows in the DDLCOMP PARMFILE as:

   MODDSNMK %USERID..%DSNQUAL2..%DSNQUAL3..%TOSSID

If this is accidentally changed it could cause the data set naming to be incorrect and create duplicates if all the qualifiers do not exist.

The RC/Migrator Guide/Wiki documents how the automatic symbolics above are populated:

·         USERID - Identifies the TSO ID that submitted the analysis.

 

·         TOSSID - Identifies the To subsystem name.

 

·         %DSNQUAL2 – Used in data set name qualification and set to a value as follows:

For table- and index-related utilities, this value is the database name (the same as  %DBNAME).

For all other utilities, this value is the object creator (the same as  %CREATOR).

 

 ·         %DSNQUAL3 -  Used in data set name qualification and set to a value as follows:

For table-related utilities, this value is the 3-byte literal TID followed by the object identifier for the table in 5-byte character format. 

For index-related utilities, this value is the index space name (same as %TSNAME).