Rapid Reorg : How to Reorg Multiple Parts

Products

• Rapid Reorg for DB2 for z/OS

Issue/Introduction

What is the best way to code Rapid Reorg jobs that are processing individual multiple parts of a tablespace but not all parts.

 

Environment

Release: R20
Component: PRR

Resolution

Rapid Reorg allows for alternative ways to do this but the best way is to code a statement which will run within the same step and take advantage of multitasking.

The product syntax allows for various options when processing parts:

 

PART {ALL|nn|nn:nn|nn,nn,nn...}]

Note: The dots below represent other PRR keyword parms.

 

When using this variation: PART {ALL|nn|nn:nn|nn,nn,nn...}]

//SYSIN DD *
REORG TABLESPACE DBASE.TSPACE PART 2, 3, 5, 7
.
.
.
.
/*
//

or

 

When using this variation: PART {ALL|nn|nn:nn|nn,nn,nn...}]

//SYSIN DD *

REORG TABLESPACE DBASE.TSPACE PART 2:7
.
.
.
.
/*
//

If the different parms are to be used for each part which are also not the same as the defaults in parmlib then this format may be used:

When using this variation: PART {ALL|nn|nn:nn|nn,nn,nn...}]

//SYSIN DD *
REORG TABLESPACE DBASE.TSPACE PART 2
.
.
REORG TABLESPACE DBASE.TSPACE PART 3
.
.
REORG TABLESPACE DBASE.TSPACE PART 5
.
/*
//

This second method is less efficient than the first one and so if all the keyword parms for all parts are the same then the first format should be used.

Additional Information

If for example it is necessary to reorg quite a number of parts but still not all parts of a tablespace where the list may flow over one line there is no need for a continuation character. 

A maximum of 450 partitions can be defined. If more than 450 are required, then specify ALL instead.

 

Syntax like this is quite acceptable:

 

//SYSIN   DD  *

  REORG TABLESPACE DBASE.TSPACE PART 2,3,4,5,6,7,8,9,10,11,12,13,14,

       15,16, 17

.

.

.

/*

//

 

REORG Control Statement

 

PART—Specify Partitions to Reorganize