Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
STU2 (Package) CCMS for DB2 for OS/390
Basic Data
| Data Element | DB2RTSMRO |
| Short Description | MAXRO parameter of the REORG utility |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Maxro |
| Medium | 15 | Maxro |
| Long | 20 | Maxro |
| Heading | 8 | Maxro |
Documentation
Definition
Specifies the maximum amount of time for the last iteration of log processing in seconds. During that iteration, applications have read-only access.
The actual execution time of the last iteration might exceed the value specified with MAXRO.
The ALTER UTILITY command can change the value of MAXRO.
The default is 300 seconds. The value must be an integer.
Specifying a small positive value reduces the length of the period of read-only access, but it might increase the elapsed time for REORG to complete. If you specify a huge positive value, the second iteration of log processing is probably the last iteration.
DEFER
Specifies that the iterations of log processing with read/write
access can continue indefinitely. REORG never begins the final
iteration with read-only access, unless you change the MAXRO value
with ALTER UTILITY.
If you specify DEFER, you should also specify LONGLOG CONTINUE.
If you specify DEFER, and DB2 determines that the actual time for
an iteration and the estimated time for the next iteration are both
less than 5 seconds, DB2 adds a 5 second pause to the next
iteration. This pause reduces consumption of processor time. The
first time this situation occurs for a given execution of REORG,
DB2 sends message DSNU362I to the console. The message states that
the number of log records that must be processed is small and that
the pause will occur. The message also suggests that this would be
an appropriate time to execute ALTER UTILITY to change the MAXRO
value and thus cause REORG to finish. DB2 adds the pause whenever
the situation occurs; however, DB2 sends the message only if 30
minutes have elapsed since the last message was sent for a given
execution of REORG.
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in | 700 |
