RMA545W when migrating statistics following Db2 13 upgrade using RC/Migrator

Products

• RC/Migrator for DB2 for z/OS

Issue/Introduction

A RC/Migrator for Db2 for z/OS (RCM) statistics only migration was done after upgrading to Db2 13 V13R1M100. The analysis showed repeated RMA545W messages on many SYSIBM tables.

Example:

RMA545W ONE OR MORE COLUMNS OF TABLE SYSIBM.EXPLAIN_MAINT_SQL HAVE
         LOST THEIR MIXED ATTRIBUTE, DUE TO CREATION ON A SYSTEM THAT
         DOESN'T PERMIT MIXED DATA IN A NON-UNICODE TABLE.

The target SSID did not have an entry in the SETUPxx member, therefore the TRGVERS parameter was needed to specify the version of the target SSID.

Resolution

PTF LU13541 was found to be the resolution.  

The TRGVERS string is 9 characters which is too long; V13R1M100.  The workaround was to enter 13R1M100.

Since the TRGVERS entered on the analysis JCL parmfile was not being recognized, the Target SSID's version was not known, which in turn caused the RMA545W messages.

Target SSID Indicates the ID of the Db2 subsystem to which the objects are to be migrated. A valid Db2 SSID
 must be entered. If the specified target Db2 SSID does not exist in the parmlib, a window appears, letting 
you specify the version of Db2 for which the DDL is written. This version is inserted into the jobstream
 as TRGVERS. For a list of all valid SSIDs and their locations, enter a question mark (?).

 

Additional Information

Per the documentation, all Db2 SSID's can be defined in the SETUPxx members.

Create a Global SETUP Parmlib member

If you use separate SETUP members for each LPAR, define all member names and data sharing group names, 
group attachment names, or subgroup attachment names in each SETUP member. Doing so lets the Database 
Management Solutions for Db2 access information about all the subsystems within the group. When you edit
an existing SETUP member, you can edit group-wide options for all data sharing group members
simultaneously. For more information, see Data Sharing Requirements.