SHRLEVEL and DATA-AVAILABLE changes in RC/Migrator r20 REORG and Rapid Reorg Models
search cancel

SHRLEVEL and DATA-AVAILABLE changes in RC/Migrator r20 REORG and Rapid Reorg Models

book

Article ID: 92827

calendar_today

Updated On:

Products

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

Issue/Introduction

The (REORG and REORG_R) and (RREORG and RREORG_R) RC/Migrator for Db2 for z/OS (RCM) Utility models are used to generate JCL and Utility statements
for the IBM REORG and the Rapid Reorg for Db2 for z/OS (PRR) utilities respectively.

In the r20 release of RC/Migrator for Db2 for z/OS (RCM), the REORG and REORG_R utility models have been changed.  Where previously SHRLEVEL was NONE now SHRLEVEL is CHANGE.
Previously SHRLEVEL was omitted from the generated utility statements and thus defaulted to NONE. In r20 release the SHRLEVEL CHANGE keyword is use explicitly.

In the r20 release of RC/Migrator for Db2 for z/OS , the RREORG and RREORG_R  utility models have been changed. Where previously DATA-AVAILABLE was Normal, in r20  DATA-AVAILABLE is CRITICAL. This is equivalent to SHRLEVEL CHANGE in the IBM REORG. Previously DATA-AVAILABLE was omitted from the generated utility statements and thus defaulted to NORMAL. In the r20 release the DATA-AVAILABLE CRITICAL keyword is used explicitly.

Resolution

When upgrading to the r20 release consideration should be made if using the new @DEFAULT model created by r20.
A IBM REORG will now use SHRLEVEL CHANGE instead of NONE and Rapid Reorg will now use DATA-AVAILABLE CRITICAL instead of NORMAL.
If this change is an issue then take a copy of the new r20 model and alter these (REORG,  REORG_R, RREORG ,RREORG_R) so that they use the desired option.
Otherwise, be aware that the operation of the utilities will be different than for previous releases.

Additional Information

See section SHRLEVEL CHANGE Support in the r20 release notes......section Utility Model Services Enhancements