Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

DSRSEXIT variables

In addition to the variables common to all REXX exits, REORG PLUS passes other variables to the DSRSEXIT user exit.

The following table describes the variables specific to this exit, grouping the variables according to whether they apply to any object type, a table space only, or an index only. This table also lists the following information about these variables:

  • Variable name

  • Brief description of the variable

    If the variable is found in the DB2 catalog or in the integrated catalog facility (ICF), the table lists the corresponding DB2 or ICF column name. If the variable is specific to REORG PLUS, the table lists the values that you can enter.

  • Whether you can update the variable within the exit (yes or no)

For a more complete explanation of a variable and its valid values, refer to the IBM documentation. For more information about the variables that you can change, see Modifying the variables for resizing the data sets.

REORG PLUS re-initializes the REXX environment and all REXX variables each time it calls the exit. You can create any additional variables for the exit to use, but REORG PLUS does not retain the variables for subsequent exit calls.


Variables that REORG PLUS passes to DSRSEXIT

Variable name

Description and DB2 or ICF column name, or valid values

Update?

Variables that apply to all objects

BMC_HIGH_USED_RBA

High-used relative byte address (HURBA)

This field is accurate for VSAM data sets that are less than or equal to 4 GB. If the data set is greater than 4 GB, the value of this field is set to 4 GB and you should use the RBN field counterpart instead.

No

BMC_HIGH_ALLOC_RBA

High-allocated relative byte address

This field is accurate for VSAM data sets that are less than or equal to 4 GB. If the data set is greater than 4 GB, the value of this field is set to 4 GB, and you should use the RBN field counterpart, instead.

No

BMC_HIGH_USED_RBN

High-used relative block number (number of 4 KB blocks used in the data set)

This field is accurate for any size VSAM data set.

No

BMC_HIGH_ALLOC_RBN

High-allocated relative block number (number of 4 KB blocks allocated in the data set)

This field is accurate for any size VSAM data set.

No

BMC_PRIMARY_QUANTITY

Primary quantity, in 4-KB pages, to be allocated (PRIQTY)

Yes

BMC_SECONDARY_QUANTITY

Secondary quantity, in 4-KB pages, to be allocated (SECQTY)

Yes

BMC_PRIMARY_SPACE_ICF

Primary space currently being used (PRIMSPAC)

No

BMC_SECONDARY_SPACE_ICF

Secondary space currently being used (SCONSPAC)

No

BMC_NBR_EXTENTS

Number of extents (NOEXTNT)

No

BMC_ICF_ALLOC_TYPE

Allocation type in tracks (TRK), cylinders (CYL), or blocks (BLK) (SPACOPTN)

No

BMC_DB2_STORTYPE

VCAT (E) or STOGROUP (I) indicator (STORTYPE)

No

BMC_ESTIMATED_CARDINALITY

Estimate of the number of rows involved in the reorganization, from ANALYZE (integer)

No

BMC_OBJECT_PART_NUMBER

Current partition number of the table space or index (PARTITION)

No

BMC_OBJECT_COMPONENT_NUMBER

Data set number from the last node of the DB2 linear data set name (for example, 001 from .A001)

No

BMC_DB2_FREEPAGE

Number of pages loaded before a page is left as free space (FREEPAGE)

No

BMC_DB2_PCTFREE

Percentage of each page left as free space (PCTFREE)

No

BMC_DB2_VCATNAME

Data set name HLQ node of storage group or ICF catalog used for space allocation (VCAT NAME)

No

BMC_DB2_STORNAME

Storage group name (STORNAME)

No

BMC_DB2_DATACLAS

Name of the SMS DATACLAS, taken from the DSN6SPRM macro in DSNZPARM

No

BMC_DB2_MGMTCLAS

Specify the name of the SMS MGMTCLAS to add

Note: You cannot use the DSRSEXIT to change an existing specified SMS MGMTCLAS.

No

BMC_DB2_STORCLAS

Specify the name of the SMS STORCLAS to add

Note: You cannot use the DSRSEXIT to change an existing specified SMS STORCLAS.

No

BMC_DATASET_NAME

Fully qualified data set name

No

BMC_OBJECT_TYPE_IND

Table space (TS) or index space (IX)

No

BMC_ALTER_DB2_CATALOG

Whether to update the DB2 catalog (YES or NO)

The default is YES.

Yes

BMC_REDEFINE_OBJECT

Whether REORG PLUS should use REDEFINE YES (YES) or REDEFINE NO (NO) for the current object

The default is YES.

Yes

BMC_REORDER_STOGROUP_VOLUMES

Whether REORG PLUS should use the storage group volume list returned from the exit (YES) or ignore it (NO)

The default is NO.

Yes

BMC_STOGROUP_VOLUME.0

BMC_STOGROUP_VOLUME.n

Stem variable that contains the number of volumes in the storage group list.

BMC_STOGROUP_VOLUME.0= n, where n is the number of volumes.

BMC_STOGROUP_VOLUME.1 through BMC_STOGROUP_VOLUME. n contain the actual names of volumes in the storage group

Yes

Variables that apply only to a table space

BMC_SYSTABLESPACE_PARTITIONS

Number of partitions of the table space or index (PARTITIONS)

No

BMC_SYSTABLESPACE_PGSIZE

Size of pages in the table space in KB (PGSIZE)

No

BMC_SYSTABLESPACE_SEGSIZE

Number of pages in each segment of a segmented table space (0 if not segmented) (SEGSIZE)

No

BMC_SYSTABLESPACE_NTABLES

Number of tables defined in the table space (NTABLES)

No

BMC_SYSTABLESPACE_MAXROWS

Maximum number of rows that DB2 will place on a data page (MAXROWS)

No

BMC_SYSTABLESPACE_DSSIZE

Maximum size of a data set in KB (DSSIZE)

No

BMC_SYSTABLESPACE_NACTIVE

Number of active pages in the table space (NACTIVEF)

No

BMC_SYSTABLEPART_COMPRESSED

Indicator that table space is compressed (COMPRESS)

No

Variables that apply only to an index

BMC_SYSINDEXES_NAME

Name of the index (NAME)

No

BMC_SYSINDEXES_DBNAME

Name of the data base that contains the index (DBNAME)

No

BMC_SYSINDEXES_CREATOR

Authorization ID of the owner of the index (CREATOR)

No

BMC_SYSINDEXES_INDEXSPACE

Name of the index space (INDEXSPACE)

No

BMC_SYSINDEXES_CLUSTERING

Whether CLUSTER was specified when the index was created (CLUSTERING)

No

BMC_SYSINDEXES_CLUSTERED

Whether the table is actually clustered by the index (CLUSTERED)

No

BMC_SYSINDEXES_FULLKEYCARD

Number of distinct values of the key (FULLKEYCARD(F))

No

BMC_SYSINDEXES_UNIQUERULE

Whether the index is unique (UNIQUERULE)

No

BMC_SYSINDEXES_PIECESIZE

Maximum size of a data set in KB for nonpartitioned indexes (PIECESIZE)

No

BMC_SYSINDEXPART_LEAFDIST

100 times the average number of leaf pages between successive active leaf pages of the index (LEAFDIST)

No

If you restart a failed reorganization, REORG PLUS passes the original information to the exit for any object that is being redefined.



Was this page helpful? Yes No Submitting... Thank you

Comments