search cancel

CA RC/Migrator for Db2 for Z/OS : Quick Migration Batch Only Option to use a Global Change Set

book

Article ID: 190687

calendar_today

Updated On:

Products

RC/Migrator for DB2 for z/OS

Issue/Introduction

The READGCS keyword is a new keyword that will force the use of an existing global change set when performing a Quick Migration in Batch.

The READGCS keyword is used to simplify the inclusion of global change specifications in batch mode only

When included in the job, this keyword enables global changes to be read from a stored , existing global change set.

Normally, the global change specifications that are contained in a global change set are expanded directly into the input parameter file stream at JCL generation time from the Quick Migration panels as below:

//PARMFILE DD   *
 STRTSSID ssid
 CREATOR  authid
 QUICKM
 DATABASE   authid DBCORP1
.
.
.
 PREFIX   authid
 MODEL4   @DEFAULT
 MODEL4C  authid
 GLBLNAME  MYGLBCHG
 GLBLCRTR  authid
 ALCR      P--D--1B__________   T--D--2B_
 ALCR      P--D--1B             T--D--2B
 ALCR      PITD--1B             TITD--2B
 ALCR      *                    AUTHID1
 TBPC      P--D--1B             T--D--2B
 TBTC      P--D--1B             T--D--2B
 VWTC      P--D--1B             T--D--2B
 VWTC      PB2D--1B             TB2D--2B
 VWTC      PITD--1B             TITD--2B
/*

Environment

Release: R19, R20

DB2 for Z/os

Resolution

The READGCS keyword will force the global change set identified by the GLBLCRTR and GLBLNAME parameters to be read from the subsystem when the job is submitted rather than when the JCL was generated.

Note that when the READGCS keyword is used, any input stream global change specifications continue to be supported and take precedence over the global change specifications that are read from the global change set.

//PARMFILE DD   *
 STRTSSID ssid
 CREATOR  authid
 QUICKMIE
 DATABASE   authid     DBCORP1
 QUICKEND
 TRGSSID  ssid
.
.
 PREFIX   authid
 MODEL4   @DEFAULT
 MODEL4C  authid
 READGCS
 GLBLNAME  MYGLBCHG
 GLBLCRTR  authid
/*


When the Analysis Output of the job is examined the Global Change Set details can be seen :

--Global Changes:
--
--  SET NAME          ===> MYGLBCHG
--  SET CREATOR       ===> authid
--
--  CODE   DESCRIPTION
--  AL     ALL OBJECT TYPES
--  ALCR    CREATOR
--   FROM P--D--1B__________                TO T--D--2B_
--  ALCR    CREATOR
--   FROM P--D--1B                          TO T--D--2B
--  ALCR    CREATOR
--   FROM PITD--1B                          TO TITD--2B
--  ALCR    CREATOR
--   FROM *                                 TO AUTHID1
--
--  TBPC    PARENT TABLE CREATOR
--   FROM P--D--1B                          TO T--D--2B
--  TBTC    TEXT CREATOR
--   FROM P--D--1B                          TO T--D--2B
--
--  VWTC    TEXT T/V CREATOR
--   FROM P--D--1B                          TO T--D--2B
--  VWTC    TEXT T/V CREATOR
--   FROM PB2D--1B                          TO TB2D--2B
--  VWTC    TEXT T/V CREATOR
--   FROM PITD--1B                          TO TITD--2B
--


If you get the Global Change Set name wrong in your PARMFILE parms this message is reported in the sysout of the job:


RMA212E GLOBAL CHANGE SET authid MYGLBCHX WAS NOT FOUND. PLEASE CREATE THE
       SET OR REMOVE IT FROM THE STRATEGY DEFINITION.

Note that if the READGCS parm is not used, the GLBLNAME and GLBLCRTR  parms are normally ignored by the analysis because the Global Change details are normally extracted at JCL generation time not at Job submission time. 

So, this means that the JCL that has been stored for a Quick migration does not have to be changed or regenerated if the associated Global Change set is changed.
It also means that changes to Global Change sets that are referenced in this way could inadvertently impact existing stored JCL.

Additional Information

New Quick Migration Batch Only Keywords

Quick Migration Batch Only Options