Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see DASD MANAGER PLUS for DB2 13.1.

Specifying Rebind and Resize Object options


This topic familiarizes you with the Rebind and Resize options. The following panel displays these options:

--------------------------- Rebind Options -------------------------------------
 Rebind . . . . . . N        (Y/N/PG/PL - Rebind affected Packages or Plans,    
                             Y=Both)                                            
 Rebind Version . . L        (L/A - L=Latest version, A=All versions)           
                                                                               
 -------------------------- Resize Object Options ------------------------------
 Resize jobs  . . . Y        (Y/N - Split REORG/RESIZE into separate jobs)      
 Resize Down  . . . Y        (Y/N - Allow objects to be resized downward)       
 Resize % pqty  . . 0        (0-999 - Percentage increase over Reorgspace)      
 Resize % sqty  . . 0        (0-999 - Percentage of primary quantity)         
 Round qty by . . . A        (A/C - A=Allocation type, C=Cylinder)              
 Maximum pqty . . . 0        (0-67108864 - Max primary quantity in K)           
 Pqty % if max  . . 0        (0-100 - Pct of Reorgspace if pqty reaches max)

To use the Rebind options

The BMCTRIG Rebind option lets you generate Rebind commands for packages and plans for table spaces or indexes that corrective action jobs affect.

An affected object is one for which the utility updates the DB2 catalog statistics during execution of the corrective action job (for example, BMCREORG with UpdateDB2stats=Y). The following table lists the utilities that update DB2 catalog statistics.

Use the values in the table below to specify rebinds:

  • In the corrective action
  • With the parameters shown in the following table


Triggered Rebind utilities

Utility

Keyword

BMCLOAD

UPDATEDB2STATS = Yes

BMCREORG

UPDATEDB2STATS = Yes

BMCSTATS

UPDATE = All or Accesspath

BMCUPRS

UPDATEDB2STATS = Yes (default), All, or Accesspath

LOAD

ALL or UPDATEDB2STATS = Accesspath

AMICOPY

RUNSTATS = Yes or UPDATE = Accesspath

REORG

STATISTICS or UPDATE = Accesspath

RUNSTATS

ALLor UPDATE = All or Accesspath

Each table space or index space for which a utility runs is a rebind candidate. When the BMCTRIG job runs, BMCTRIG notes each rebind candidate object that uses the utilities and parameters that the preceding table lists. BMCTRIG generates the rebinds last. If Workload Balance is Y, the rebinds are placed in a separate job. At the end of utility generation, BMCTRIG checks each object for dependencies to find the related packages or plans to rebind.

Each plan or package is at the end of the worklist as part of a REBIND command (-REBD). A single -REBD command can contain up to 400 rebind statements. If a command requires more statements, the utility generates additional -REBD commands. If BMCTRIG does not find plans or packages for any of the rebind candidates, it issues the following message:

BMC17167I ** NO REBIND OBJECTS DETECTED **

The options in the following table are applicable if you are generating corrective actions.


Rebind options

Option

Description

Rebind

To rebind affected packages and plans, type Y in the Rebind field. To rebind packages only, type PG. To rebind plans only, type PL. Otherwise, type N.

Rebind Version

To include only the latest version for the value selected for Rebind, type L in the Rebind Version field. To include all versions, type A.

To specify Resize options

For all Resize options, the option is valid only when the service in the corrective action is a reorganization and the Resize option in the REORG utility is set to any value except N, or the service is RESIZE.

Apply the options in the following table if you are generating corrective actions:


Resize options

Option

Description

Resize jobs

If you specify Y for Resize jobs, BMCTRIG forces PARTLVL Y and MAXOBJECTS 1 and splits the REORG and RESIZE operations into separate jobs for each object and partition combination. Type N to consolidate REORG and RESIZE operations with other utilities into a single job in accordance with the Max Objects parameter on the JCL generation options panel.

Note

Consider the following additional information:

  • This option is valid only with Standard JCL.
  • If you specify Y for Resize jobs and N for Workload Balance, BMCTRIG cannot perform a grouped reorganization.

Resize Down

To allow objects to be resized down, specify Y in the Resize Down field. The Resize Down option in the BMCTRIG action specifies whether to allow downward resizing of objects.

Resize % pqty

To increase the Reorgspace by a certain percentage, type a number between 0 and 999 in the Resize % field. If you use 0, BMCTRIG uses the standard formula. The specified percentage overrides the standard formula for resizing, which is:

NEW PRIQTY = REORGSPACE + (2*SQTY)

Resize % sqty

Use this option to change the secondary quantity allocation to a percent of the calculated primary quantity. If you do not specify a value, the secondary quantity is not changed.

Round qty by

Type A to round by the allocated type as noted in the BMCSTATS tables (the default) or C to calculate on a cylinder boundary.

Maximum pqty

Use this option to provide an upper limit for the calculated primary quantity when resizing.

Note

Note that DB2 rules for the maximum data set size always apply, no matter what value you set. However, if you use this option, you can specify Pqty % if max as an alternate value to apply to Reorgspace, if the calculated primary quantity exceeds this limit.

Pqty % if max

Type a value to specify the percent to apply to the Reorgspace to adjust the primary quantity, if the calculated primary quantity meets or exceeds Maximum pqty value.

The Resize option in the corrective action for the IBM REORG and BMCREORG functions specifies the scope of the resizing. The following figure shows the Resize option on the first IBM REORG utility panel. If the corrective action contains a RESIZE service, it applies to all generated VCAT or storage group objects.


REORG with Resize option

DEGG                   REORG   TABLESPACE DEMO.%             Row 36 to 72 of 108
Command ===>                                                  Scroll ===> CSR  
                                                                              
Service Syntax: REORG.DEMO                                          
                                                                              
Type Service Syntax options. Then press End.                        More: + -  
-------------------------- Reorg Options --------------------------------------
REUSE  . . . . . . N        (Y/N Reuse and reset data sets)                    
SCOPE  . . . . . . A        (A/P A-All, P-Pending)                             
REBALANCE  . . . . Y        (Y/N Rebalance partitions)                         
 SORTCLUSTER . . . Y        (Y/N Data records explicitly sorted)               
LOG  . . . . . . . Y        (Y/N Log records during reload phase)              
SORTNPSI . . . . . Y        (A/Y/N A-AUTO, Y-YES, N-NO)                        
UNLOAD . . . . . . C        (C/P C-Continue, P-Pause)                          
KEEPDICTIONARY . . N        (Y/N Keep compression dictionary)                  
PREFORMAT  . . . . N        (Y/N Preformat remaining pages up to HARBA)        
ROWFORMAT  . . . .          (B/R B-Basic Row Format, R-Reorder Row Format)     
RBALRSN_CONVERSION E        (N/B/E N-NONE, B-BASIC, E-EXTENDED)                
Resize . . . . . . N        (N/T/I/A N-No T-Tablespaces I-Indexes A-All)       
Restart  . . . . . N        (Y/N Generate Restart Phase)                       
AUTOESTSPACE . . . Y        (Y/N Auto Estimate Space)

The following tale lists valid values for the Resize option and the corresponding instruction to the BMCTRIG program.

Value

Instruction to BMCTRIG

N

(default value)

Do not resize any table space or index objects. Use this value when generating an index or table space object.

T

Evaluate all table space partitions qualified for generation to determine whether to resize them. If so, generate the appropriate utility commands to resize the data sets during the reorganization.

I

Evaluate all index partitions qualified for generation to determine whether to resize them. If so, generate the appropriate utility commands to resize the data sets during the reorganization.

A

Evaluate all objects qualified for generation (table space and index partitions) to determine whether to resize them. If so, generate the appropriate utility commands to resize the data sets during the reorganization. If the table space or table space partition is generated, associated indexes or partitions are resized.

Selection of DB2 data sets for resizing is based on the latest BMCSTATS data. The product expands or contracts the primary space quantity based on the primary quantity that BMCTRIG calculates. You can set or change the quantity by providing a resize exit. If the return value is not zero, BMCTRIG uses the return value as the primary quantity. If BMCTRIG does not find a resize exit, it uses calculations and user options instead. The shipped default for the resize exit uses the following formula to calculate primary quantity:

PRIQTY = REORGSPACE + (2*SQTY)

Note

You should also consider the following:

  • DB2 rules determine the maximum primary quantity.
  • If the value for SQTY is zero, the new primary quantity is a percentage of the old primary quantity.

    If the new primary quantity is equal to the old primary quantity value, the product does not resize the object.

For more information about data set allocation rules for the ALTER and CREATE statements, see the IBM SQL Reference.

For more information about table space and index design, see the IBM DB2 Administration Guide.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*