Specifying unique image copy names in the Database Management Post Install ssid0000 Compare task
search cancel

Specifying unique image copy names in the Database Management Post Install ssid0000 Compare task

book

Article ID: 269654

calendar_today

Updated On:

Products

RC/Migrator for DB2 for z/OS DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite

Issue/Introduction

How to change the name generated for image copies by the Post Install Compare task, ssid0000. The generated names do not guarantee unique datasets
resulting in failure of the ssid0001 Create task, as the image copies already exist.

The default mask is %USERID..%DSNQUAL2..%DSNQUAL3..%TOSSID 

Can the utility model be changed to specify a GDG or something else to guarantee uniqueness.

Resolution

The Compare task uses it's own utility models so you will not be able to change the model or create your own alternative model for this task.
However, when you generate the JCL through the panels, you have the option to override the default dataset name mask.


Update the Dataset Name Mask field.             
                                                       
The name mask is used by Model Services to generate sequential datasets used for utility execution, such as UNLOAD, LOAD, or IMAGE COPY. 
                                                       
To guarantee uniqueness, you can use the mask with the a Date/Time qualifier, for example %DTQUAL.

%USERID..%DSNQUAL2..%DSNQUAL3..%DTQUAL      


If you then browse the generated SSID0000 JCL member you will see the mask generated as follows in the MODDSNMK parameter 

MODDSNMK %USERID..%DSNQUAL2..%DSNQUAL3..%DTQUAL


This parameter is used in both the COMPRT and DDLCOMP steps to control the dataset naming.