CA RC/Migrator for DB2 for Z/OS : RM093 RM093E: Duplicate Strategy Name, please specify another. - BUT IT'S NOT!

book

Article ID: 223590

calendar_today

Updated On:

Products

CA RC/Migrator for DB2 for z/OS

Issue/Introduction

RM093  RM093E - DUPLICATE STRATEGY NAME - BUT IT'S NOT!

A alteration strategy , authid1/TESTTAB1 was being saved & received message :

RM093 RM093E: Duplicate Strategy Name, please specify another.  HELP for
more info.

But, on the strategy list the strategy name is not listed and appears not to exist.

RMS1 20.0   -------------- RC/M Strategy Services -------------- yy/mm/yy hh:ss
COMMAND ===>                                                  SCROLL ===> CSR

DB2 SSID ===> ssid
STRATEGY ===> TESTTAB1 CREATOR ===> authid1 TYPE ===> A    SRC SSID ===> *
--------------------------------------------------------------------- authid1

                                              T S SRC  +---- LAST UPDATE ----+
O STRATEGY DESCRIPTION               CREATOR  P O SSID   USER     DATE   TIME
_ ________ _________________________ authid1  _ N ____ <== STRATEGY CREATION

Cause

Strategy names must be unique by the combination of the name and creator. There can't be strategy-name/creator combinations used with different strategy types at the same time. 

 

Resolution

In the header fields for strategy services, an "A" had been inserted into the TYPE field which only lists Alteration strategies. In this case another strategy type was being created, an "M" type with the same authid1/TESTTAB1 combination. 

The recommendation is to filter on DB2 SSID , CREATOR and STRATEGY and leave all other header fields as '*'. When this is done a strategy matching the new name being saved is listed but it is an existing COMPARE strategy!!

That means that it rightly is not listed when an "A" TYPE is used in the header field. The "*" is a wildcard for all strategy types in this case.

RMS1 20.0   -------------- RC/M Strategy Services -------------- yy/mm/yy hh:ss
COMMAND ===>                                                  SCROLL ===> CSR

DB2 SSID ===> ssid
STRATEGY ===> TESTTAB1 CREATOR ===> authid1 TYPE ===> *    SRC SSID ===> *
--------------------------------------------------------------------- authid1

                                              T S SRC  +---- LAST UPDATE ----+
O STRATEGY DESCRIPTION               CREATOR  P O SSID   USER     DATE   TIME
_ ________ _________________________ authid1  _ N ____ <== STRATEGY CREATION
_ TESTTAB1                           authid1  C N ssid authid1  yy/mm/dd hh:mm

This filtering misunderstanding can also happen with the SRC SSID field. It may appear like the strategy name does not exist but in fact the strategy is not listed due to the value of the TYPE  and/or SRC SSID being set instead of a wildcard. 

With this information the authid1/TESTTAB1 combination could be changed to authid1/TESTTAB2 to create the new strategy.

 

Additional Information

Manage Strategy Services