SET-REORGANIZE-PPP-PARAMETERS sets the parameters which are needed to enable a REORGPPP DML to be executed. PPP reorganization takes place in a sequence of reorganization actions that are executed in one or more consecutive online utility runs. Here the DBH internally maintains the cross-transaction information on the progress of the PPP reorganization, e.g. current page number. This information is lost when the session or session section ends or when the database of the realm concerned is detached.
SET-REORGANIZE-PPP-PARAMETERS | ||
SUBSCHEMA-NAME = <structured-name 1..30>
|
SUBSCHEMA-NAME = <structured-name 1..30>
Name of the subschema. Only names of user subschemas are permitted.
REALM-NAME = <structured-name 1..30>
Name of the realm. The realm name must be a valid name in the defined subschema. Only names of user realms are permitted. Names of temporary realms are not permitted. The subschema must also include all realms which contain the DBTTs whose entries refer to records and tables in the realm where probable position pointers are to be updated. The corresponding check takes only place when the DMLs are executed. Record types and sets of the realm, on the other hand, need not be fully contained in the specified subschema. To this extent the reorganization of pointers in records and tables takes place independently of the specifications in the subschema.
INITIALIZE =
Defines the behaviour of the REORGPPP DML when PPP reorganization in a realm is distributed over multiple online utility runs.
Initialization of the current page takes place when INITIALIZE = *ANY or *YES. In particular, after a complete PPP reorganization the current page number is not automatically re-initialized. Further execution of PPP reorganization actions using INITIALIZE = *NO or INITIALIZE = *ANY results in the return information that there is nothing more to do.
INITIALIZE = *ANY
The current page number is re-initialized in accordance with the following conditions:
If PPP reorganization has already been started in a previous utility routine run, this reorganization is continued. The current page number is not re-initialized.
If no PPP reorganization has been started in a previous online utility run in this session section or in the period since the realm concerned was last attached, the first PPP reorganization action implicitly leads to the current page number being initialized.
INITIALIZE = *YES
The current page number is always re-initialized.
The PPP reorganization consequently begins again.
You can use this setting to reorganize PPP in these pages retroactively above all when a previous CLASH-HANDLING=*SKIP-PAGE means that access conflicts with other user transactions have resulted in some pages being skipped.
INITIALIZE = *NO
The current page number is not re-initialized.
A PPP reorganization which has already been started in the previous online utility run is continued. If no PPP reorganization has been started, the current page number is not initialized.
PAGES-PER-DML = <integer 1..16777215>
Specifies the maximum number of pages where PPPs are to be updated with a REORGPPP DML. Default value: 1.
CLASH-HANDLING =
Defines how the REORGPPP DML behaves when a page which is locked by another transaction is to be processed.
CLASH-HANDLING = *BREAK-DML
The REORGPPP DML is aborted, but any PPP reorganizations already performed in this DML or in previous DMLs of the same transaction are retained. With the next REORGPPP DML - as a rule in a new transaction -, possibly after a delay in the UDS online utility, it is attempted again to perform PPP reorganization in this page.
When CLASH-HANDLING=*BREAK-DML, PPP in all required pages are updated if the last page in realm is reached. However, if conflicts occur it is possible that additional REORGPPP DMLs are required for this purpose.
CLASH-HANDLING = *SKIP-PAGE
The page is skipped. It is not attempted in a subsequent DML to repeat PPP reorganization for this page. However, if too many pages are skipped in a REORGPPP DML, the DML is aborted.
When CLASH-HANDLING=*SKIP-PAGE, the required number of pages (PAGES-PER-DML parameter) is generally handled with a REORGPPP DML. However, it can happen that not all required pages are handled within a REORGPPP cycle. In this case a follow-up action (INITIALIZE=*YES) can be used to complete the PPP reorganization later when, for example, corresponding conflicts are less likely.
CLASH-HANDLING = *WAIT-FOR-TRANSACTION
REORGPPP transaction is waiting until the locked page is released by the locking transaction.