gtpd1m1g | Database Reference |
You should have a complete knowledge of the database to be captured and be
able to:
- Define the system state the DBR run will operate in. Table 12 summarizes the operational requirements for starting a DBR
run.
- Define which record types can or cannot be captured.
- Define which pool records will be captured.
Table 12. Database Reorganization Operational Requirements
| Phase
| Record Type
| IPL
| State
| Other
|
1
| Input
| Fixed
| General file
| 1052
| None
|
2
| Input
| Pool
| Prime module
| 1052
| None
|
3
| Output
| Fixed
| Prime module
| 1052
| None
|
4
| Output
| Fixed
| Prime module
| NORM
| Logging
|
5
| Output
| Pool
| Prime module
| 1052
| None
|
6
| Output
| Pool
| Prime Module
| NORM
| Logging
|
For example:
- Line 3 shows that if you want to start a DBR run for the output phase of
fixed records, you must IPL the prime module and the TPF system must be in
1052 state.
- Lines 4 and 6 show that the system can enter NORM state only if record
logging for the capture and restore utility is active. See Capture and Restore for more information about capture and restore.
- Line 1 shows that if you want to start a DBR run for the input phase of
fixed records, you must IPL the general file and the TPF system must be in
1052 state.
These operational requirements apply only to the START and RESTART
functions; that is, the actual running of DBR. The other DBR
commands are not subject to these requirements.
Additional considerations include the following:
- If a processor is running DBR, you cannot start another DBR run on the
same processor.
- In a multiple database function (MDBF) system, whether loosely coupled or
not, you cannot start a DBR run for a subsystem that is currently running
DBR.
- In an MDBF system, whether loosely coupled or not, you cannot start a DBR
run for a subsystem user that is currently running DBR.
- In a loosely coupled MDBF system, 1 processor can run DBR for a given
subsystem user while another processor runs DBR for a different subsystem
user.
- In a loosely coupled MDBF system, 1 processor can run DBR for a given
subsystem while another processor runs DBR for a different subsystem.
- DBR cannot be run on tapes mounted in blocked mode.
If you want to run the DBR output phase with buffered tape devices, you
must do one of the following:
- Specify the DBRBUF=YES parameter on the CONFIG macro in your SIP stage 1
deck. See TPF System Generation for more
information about the CONFIG macro.
- Enter the ZSYSG command with the DBRBUF parameter.
Attention: Running the DBR output phase with buffered tape
devices will improve performance; however, if the system re-IPLs or tape
errors occur while DBR is in progress, you may lose data. Also, because
the switch that is set by the DBRBUF parameter is subsystem-shared, you can
specify ZSYSG with the DBRBUF parameter only from the basic subsystem
(BSS).
- DBR uses 2-byte hexadecimal record types and 8-byte ordinal numbers (up to
16 digits).
- Note:
- All input and output messages will handle ordinal numbers as hexadecimal
values rather than decimal values.