RC/Migrator : How do I correct an RC/Migrator analysis that allocates the same dataset twice?

Products

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

Issue/Introduction

How do I correct an RC/Migrator analysis that allocates the same dataset twice?

Environment

Release: R20
Component: RCM

Resolution

When multiple utilities are executed within the same analysis, work datasets of the same name can be generated by the model whether using IBM utilities or CA utilities.

For example: A REORG and a COPY utility are executed within the same analysis. Both model utilities might generate a COPYDSN with the same name.

Steps to correct the problem:

1. Review the MODEL that is being used when analysing the strategy and identify the utility and DD statement in the job output that is producing a duplicate name. You would know that you have a conflicting name in the generated analysis when the analysis is executed. This is because MVS errors will be received at execution time. Identify the two or more utilities where the same dataset name is being generated then look in the model to find the symbol that is being used in both. The two model elements might in fact be using different symbol names producing the same duplicate result so be aware of this too. These symbols are substitution variables that can contain any value. 
   
   In this example the COPYDSN symbol name is used in two model utilities. Having identified the location of the duplicate symbols we can then go into the model and change it. 
   
   
2. From the Product Main Menu, Select Option 2 (RC/Migrator). 
   
   
3. Select Option 0 (Profile). 
   
   
4. Select Option 6 (Utility Model Services) 
   
   
5. Browse the @DEFAULT MODEL ID that is being used with the "B" line command. 
   
   
6. On the General Model Utilities screen, display the Symbols for the COPY utility using the "S" line command. 
   
   Take notice of the construction of the COPYDSN symbol.

   UTILITY OBJ DESCRIPTION SIZE    COPY TS IMAGE COPY RPI

   CMD SYMBOL ERR REPLACEMENT VALUE         COPYDSN %DSN..COPY

7. PF3 back out to the General Model Utilities screen. 
   
   
8. Display the Symbols for the REORG utility using the "S" line command.

   UTILITY OBJ DESCRIPTIONC SIZE        REORG TS REORG RPI

   CMD SYMBOL ERR REPLACEMENT VALUE        COPYDSN %DSN..COPY

9. Compare the REPLACEMENT VALUE for the SYMBOL that caused the error in the job. (In this example COPYDSN) 
   
   Notice that they are both using "%DSN..COPY". This will produce the same dataset name. 
   
   
10. PF3 back out to General Model Services and select to update the model using the "U" line command. 
    
    Select the utility that must be modified and use the "S" line command to display the symbols. 
    
    
11. Change the REPLACEMENT VALUE for the SYMBOL in one of the utilities and save the change. (Ex: %DSN..COPY2). In this way the analysis won't generate the same name for the symbol in question again. There are other symbolic variables listed in the RC/Migrator Manual that can be used to construct a dataset name such as a date/time based value. 
    
    
12. Go back and Re-Analyse the Strategy using this changed MODEL. The code generated now won't have conflicting dataset names. 
    
    Note that any change made to a MODEL will impact other users of that model and so caution should be taken when doing this.

Additional Information

See the RC/Migrator User Guide, Manage Profile Options, Utility Model Services.