Utility dataset name is truncated as it is too long resulting in error messages RMA229W and RMA178E

Products

• RC Compare for DB2 for z/OS
• RC/Migrator for DB2 for z/OS

Issue/Introduction

RC/Compare for Db2 for z/OS (RCC) Analysis fails with error RMA178E indicating that there is a problem with the data set names generated
by RC/Migrator for Db2 for z/OS (RCM) Model Services. The error message is preceded by warning messages RMA229W, reporting that
generated data set names have been truncated.

RMA178E DATASET NAME dataset_name IS USED BY TWO DIFFERENT UTILITIES IN THIS ANALYSIS OUTPUT.

RMA229W MODEL SERVICES GENERATED DSN HAS BEEN TRUNCATED TO 44 BYTES: dataset-name

It is the truncation of the data set names that is resulting in the RMA178E error.

Cause

The truncation of the data set names generated by Model Services for these utilities, is most likely caused by the customizing of the DSN Symbolic Variable in Model Services.

For example, if the DSN Symbolic Variable has been customized to include the %OBJECT conditional symbol then that could cause data set names to exceed the
allowable maximum of 44 characters, particularly for table related utilities.

Resolution

Review the DSN Symbolic Variable definition in the relevant Model Services utility model. 

Using the %OBJECT variable will result in possible truncation particularly for long table names, so we would not recommend the use of %OBJECT variable in table
related utilities such as FUNLD and FLOAD.

The default definition for the DSN symbol is:

DSN %USERID..%DSNQUAL2..%DSNQUAL3

For table related utilities the DSNQUAL2 and DSNQUAL3 variables equate to the following:

%DSNQUAL2 = database name

%DSNQUAL3 = table identifier TIDxxxxx

The default definition should provide a working solution without any truncation.