You can execute this command in either Single User or with the MUF active. Execute the RETIX function using the following command format.
Rebuilding a Full Index Area
►►─ RETIX DBID=n ─┬────────────────────────┬─┬─────────────────────────┬──────► └─ ,OPTIMIZE= ─┬─ NO ──┬─┘ └─ ,OPTION1= ─┬─ NOF ◄ ─┬─┘ └─ YES ─┘ ├─ '(I)' ─┤ └─ '(U)' ─┘ ►─ ,SORT=n ─┬───────────────────────┬─┬─────────────┬─┬─────────────┬────────► └─ ,VERIFY= ─┬─ NO ◄ ─┬─┘ └─ ,SORTDD=c ─┘ └─ ,SORTWK=n ─┘ └─ YES ──┘ ►┬───────────┬──┬─────────────────────────┬──────────────────────────────────►◄ └─ ,UNIT=c ─┘ └─ ,SORTDFLT= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘
Rebuilding an Area's Index in Single User
►►─ RETIX DBID=n,AREA=a ─┬────────────────────────┬───────────────────────────► └─ ,OPTIMIZE= ─┬─ NO ──┬─┘ └─ YES ─┘ ►─┬─────────────────────────┬─ ,SORT=n ─┬───────────────────────┬────────────► └─ ,OPTION1= ─┬─ NOF ◄ ─┬─┘ └─ ,VERIFY= ─┬─ NO ◄ ─┬─┘ ├─ '(I)' ─┤ └─ YES ──┘ └─ '(U)' ─┘ ►─┬─────────────┬─┬─────────────┬─┬───────────┬─┬───────────────┬────────────► └─ ,SORTDD=n ─┘ └─ ,SORTWK=n ─┘ └─ ,UNIT=c ─┘ └─ ,MULTUSE=NO ─┘ ►─┬────────────────────────┬─────────────────────────────────────────────────►◄ └─ ,MINIMAL= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘
Rebuild an Area's Index Area in MUF
►►─ RETIX DBID=n,AREA=a,SORT=n ─ ,MULTUSE=YES ────────────────────────────────► ►─┬─────────────────────────┬─┬─────────────┬─┬─────────────┬────────────────► └─ ,OPTION1= ─┬─ NOF ◄ ─┬─┘ └─ ,SORTDD=n ─┘ └─ ,SORTWK=n ─┘ ├─ '(I)' ─┤ └─ '(U)' ─┘ ►─┬───────────┬─┬────────────────────────┬───────────────────────────────────►◄ └─ ,UNIT=c ─┘ └─ ,MINIMAL= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘
Command
Invokes the function to rebuild a data space index or Index Area.
Required Keywords
Specifies the database for which the Index Area is to be rebuilt.
DATACOM-ID of the database
(No default)
Optional Keywords
Identifies the data area or all areas in the database for which the Index Area is to be rebuilt. If this parameter is omitted, all areas are processed.
DATACOM-NAME of the area in the database
All areas are processed
Specifying MINIMAL=NO (the default) requires the RETIX function to perform everything it did in previous releases. If MINIMAL=YES is specified, however, RETIX does only the minimal actions necessary to correct the key definition index for tables in the area.
Note: MINIMAL=YES requires SORT= to be specified with a value greater than 0 (zero).
For key definitions marked not-loaded, only those keys participate in the normal RETIX process.
For key entries in the index that have no current key definition, the low-level (DXX) blocks of the index are sequentially searched for pointers that need to be deleted.
MINIMAL=YES is only allowed at the area level (full database processing is invalid), and is only available for areas that are loaded in the URI format. When you specify MINIMAL=YES, make certain that every table in the area is loaded and has its URI index loaded.
Messages DB13283E is related to the use of the MINIMAL= keyword. For details about this message, see the CA Datacom/DB Message Reference Guide.
For information about changes in the RETIX report when MINIMAL= is used, see RETIX Report Changes Related to MINIMAL=.
YES or NO
NO
Specifying MULTUSE=YES allows a single area in a database to have its index rebuilt, with no loss of read and update access to other areas in the database. When MULTUSE=YES, the function executes in a new format that is a combination of MUF and Single User modes. The database involved must be able to be opened for update in the MUF address space. The area, however, must have no tables open. If the database is currently open, CA Datacom/DB closes this area with the area close (you would need to close the area yourself only if the database is open and you need the MUF to close it, so that any type of open data set lock can be released, which could be necessary in order to scratch and reallocate the data set). Once started, the function does not allow other tasks to open any tables in the area being processed. Other tables in the involved database, but not in the area, may be open for read or update in the same MUF. With MULTUSE=YES:
When MULTUSE=YES, the SORT= option must be specified but not as zero (0). When MULTUSE=YES, the following options are not allowed to be specified: OPTIMIZE= and VERIFY=.
When MULTUSE=NO is specified or is allowed to default in the LOAD and RETIX functions, the functions execute with the index and data areas data sets in the DBUTLTY address space.
For more information on area level DBUTLTY control, see Area Level DBUTLTY Control.
NO or YES
NO
Specifies whether the Index entry creation optimization option is to be used. When YES is selected, if this Index Retrieve fails for any reason, reinitialize the Index Area. If any other data areas are already loaded, re-create the Index entries using this function of DBUTLTY, or reload all areas. If you select YES, you must also specify a value in the SORT= parameter.
All Index entries are to be validated as they are created.
All Index entries are not to be completed until the Index retrieve terminates. Selection of this option enhances performance by deferring Index pointer validation and complete Index structure update.
Note: Do not specify this option if MULTUSE=YES is specified.
NO or YES
NO (if one area is specified)
YES (if the full database is processed)
(z/OS only) Specifies the statistics display option to be passed to the sort program (see the SORT parameter).
Corresponds to the NOFLAG parameter of the IBM sort. Only critical messages are to be displayed on the console.
Specifies that informational and critical messages are to be displayed on the printer and the console.
Specifies that only critical messages are to be directed to both the printer and the console.
NOF, '(I)', and '(U)' correspond to the Syncsort MSG options of CC, SC, and CB respectively. The DBUTLTY LOAD function also accepts any 3-character (including the surrounding parentheses) FLAG parameter that can be processed by the IBM sort. See your IBM sort documentation for details.
NOF, '(I)', or '(U)'
NOF
Activates the Index Area (IXX) entry sort option. When you specify a value, no IXX entries are created as the data is retrieved. The required IXX entries are sorted at the end of the data retrieval and merged into the Index Area in ascending sequence. Selecting this option enhances the performance of the Index Retrieve process for large databases, and we recommend it when the number of records exceeds several hundred.
Note: The SORT option is required when specifying the RETIX function for the full database, or if you specify VERIFY=YES, OPTIMIZE=YES, or MULTUSE=YES. The SORT option is also required when running a DBUTLTY RETIX of a data area that includes any tables with a key larger than 180 bytes.
This parameter's value specifies the estimated number of entries to be sorted. Sort treats each entry as a record. To determine the number of entries:
DBUTLTY passes the value specified for this parameter to the sort routine. Therefore, the value specified for SORT= can affect the amount of runtime used by the sort. If a number is supplied to the sort, the Index Area entries in the Index Area are not deleted by a separate Index Area pass. The Index Area is updated and only the Index Area blocks that reflect change are written. This option is strongly recommended since it can improve performance. The OPTION1= parameter is also highly recommended to obtain warning and critical messages if a problem occurs.
Note: Do not specify over 99 million unless you verify that the sort package you are using allows a larger number. Specifying SORT=0 (or any number of zeros) is the same as not specifying the keyword.
Many features introduced in previous releases require a non-zero value for SORT=, and the following two features that are also blocked during RETIX executions when the sort option is not being used are as follows:
Most user-JCL is expected to already have a non-zero value for SORT= specified. If, however, a user has a LOAD or RETIX function coded in their JCL with SORT=0 specified or defaulted (SORT= not specified at all), this information is added to the history report, and the first time in each MUF execution that an area is opened in a database that has a LOAD or RETIX coded without the sort option, an informational message is generated. The message alerts you to the condition and can therefore help you know to first add the sort option, then see the results.
Two messages related to using LOAD and RETIX without the sort option are messages DB02809I and DB13128E. For details about these messages, see the CA Datacom/DB Message Reference Guide.
0 to 99999999999
(No default)
Specifies an optional DD statement, provided to the SORT that redirects SYSPRINT-type output from the SYSPRINT DD (used by DBUTLTY) to this optional DD statement.
printed output directed to optional DD statement
printed output directed to SYSPRINT, intermixed with DBUTLTY output
(z/OS only) Specify SORTDFLT=YES when you want the DBUTLTY SORT= value to be overridden with what is expected to be a more accurate number.
SORTDFLT= can be set to YES or NO (the default). If SORTDFLT=YES, the SORT= value is required to be greater than zero.
The keyword, SORTDFLT= allows the SORT value, when specified as greater than zero (0) for a RETIX to be overridden with an estimate expected to be more accurate. SORTDFLT= can only be used in conjunction with the SORT= keyword. When set as SORTDFLT=YES, the RETIX uses the current CXX count of records and definition to calculate a value for the SORT= override. If the count is zero (no records) for all tables to be loaded, the SORT=n value is used and not overwritten. Verify that it is in the appropriate range to allow a successful RETIX.
The record count and the number of key definitions per table are multiplied for each table to be loaded, and the products are summed as the estimate for record index entries. Based on the areas space management (DSOP) options, additional counts are added to verify a successful sort.
When using this DBUTLTY RETIX keyword, take into consideration that the number of records in a table after a MUF outage is likely to be inaccurate.
NO or YES
NO or YES
Specifies the number of sort work areas. The parameter is always edited, but is only used when the SORT= parameter is specified as not zero.
Note: Do not specify a 2-digit number unless the sort package you are using allows a 2-digit number. Sort packages that do not support a 2-digit number can fail in an unpredictable manner, if you specify a 2-digit number.
0 to 99
Note: Do not use two-digit numbers unless the SORT package to be used supports the larger number.
3
(z/OS only) Specifies the unit name for sort work areas. The parameter is always edited, but is only used when the SORT= parameter is specified as not zero.
1- to 8-character unit name
SYSDA
Verifies if the Index Area and data area are in exact agreement. It is only used when the SORT= parameter is specified as not zero.
Specify VERIFY=YES to activate the search for differences in the current Index and the Index being built. If a difference is detected, a Master List dump is produced. Only the first five differences cause a dump. Any additional differences are ignored.
The dumps have no effect on the execution of the RETIX function which continues to successful completion regardless of the value specified for the VERIFY option.
If you specify VERIFY=YES, you must specify the SORT option. If you do not specify SORT= when using VERIFY=YES, the first five records found cause a Master List dump whether or not a difference is found between the current Index and the Index being built.
Do not specify VERIFY=YES if you are using the RETIX function for the full database. Using the VERIFY is also not recommended for non-URI areas because records that have been moved are dumped, even though this condition is not an error.
Note: Do not specify this option if MULTUSE=YES is specified.
NO or YES
NO
|
Copyright © 2014 CA.
All rights reserved.
|
|