This document covers the following topics:
By either entering the
MM direct command or selecting the
MM option on the ETP Maintenance Utility
Main Menu, the
Master File Definition Maintenance screen appears.
23:59:59 ***** ENTIRE TRANSACTION PROPAGATOR ***** 2000-12-24
Master File Definition Maintenance
AD Add master file definition
MO Modify master file definition
DI Display master file definition
DE Delete master file definition
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Last Flip Tech Canc
|
The master file tasks you select from this menu cause the screens described in the following section to appear.
By either entering the Add
MAster direct command or selecting the
AD option on the
Master File Definition
Maintenance menu, the following screen appears.
23:59:59 ***** ENTIRE TRANSACTION PROPAGATOR ***** 2000-12-24
Add master file definition
DBID FNR Verify FDT
Master file .. ______ ______ Y (Y/N)
Log file .. ______ Y (Y/N)
ADABAS field name of distribution key ..... __
NATURAL data format of distribution key ... ____
Call user exit before replication ......... N (Y/N)
Start program after ET .................... N (Y/N)
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Last Save Flip Tech Canc
|
To define an ETP master file, enter the information in the fields, as described below.
| Master File DBID/FNR | Enter the database ID and file number of the Adabas file that
becomes a master file. Specify Y (yes) under "Verify
FDT" to verify the file's Field Definition Table (FDT); otherwise, enter
N (no). You must make all entries; there are no defaults.
|
| Log File FNR | Enter the file number of the Adabas file that is or will be the
ETP log file. The log file must be on the same database as the master file. A
single log file can be used for more than one master file. Specify
Y (yes) under "Verify FDT" to verify the log file's
Field Definition Table (FDT); otherwise, enter N (no). To ensure
data consistency, the log file must be empty; otherwise, adding a master file
is not allowed.
|
| Adabas Field Name of Distribution Key |
When any of the replicate files for this master file contain
only a subset of master file records, one field must contain values or ranges
of values that uniquely identify each replicate file's subset, and therefore
the replicate file itself. Specify the two-letter Adabas field name of that
identifying field here. The distribution key field cannot be a multiple-value (MU), a periodic group (PE) or field within a PE group, or a phonetic descriptor field; otherwise, an error occurs either during FDT verification, or when writing to the log file during operation. |
| Natural Data Format of Distribution Key |
When you specify a field name for the Distribution Key field above, you must specify the field's Natural data type here (for example, A15 for a 15-byte alphanumeric field). Specifying the number of digits after the decimal point is not possible for numeric data types. |
| Call User Exit? | Specify Y (yes) if you want the
WADUSER2 subprogram (see Installing the Entire
Transaction Propagator in the Installation for
z/OS and Installation for z/VSE documentation)
called after ETP checks the current transaction record's distribution
key field, if any. ETP checks any distribution key to determine if a change to
the master file must also be made to a specific replicate file. The default is
N (no).
|
| Start Program after ET? | Specify Y (yes) if you want to execute the program
defined in the Modify System
Profile task screen. The default is N (no).
|
By either entering the MOdify
MAster direct command or selecting the
MO option on the
Master File Definition
Maintenance menu, the Modify Master File
Definition screen appears.
23:59:59 ***** ENTIRE TRANSACTION PROPAGATOR ***** 2000-12-24
Modify master file definition
DBID FNR Verify FDT
Master file ..* ______ ______ Y (Y/N)
Log file ... ______ Y (Y/N)
ADABAS field name of distribution key ..... __
NATURAL data format of distribution key ... ____
Call user exit before replication? ........ _ (Y/N)
Start program after ET .................... _ (Y/N)
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Last Save Flip Tech Canc
|
To change an existing master file's definition, enter the information in the fields as described below.
When the "Modify Master File Definition" screen is first
displayed, you must either enter (or have already selected) a master file;
otherwise, you cannot make entries in the rest of the fields. Once you have
selected a master file and pressed Enter, you cannot change your
selection unless you either exit and then re-enter the screen, or enter the
SAVE command.
| Master File DBID/FNR | Enter the database ID and file number of the existing master file. If you enter a wild card in either the database ID or file number field, a window appears from which you can select a single master file definition for modification. |
| Log File FNR | Enter a new log file file number here. The log file must be on the same database as the master file. Note that if the current log file is not empty, a new log file cannot be defined. |
| Adabas Field Name of Distribution Key |
When any of the replicate files for this master file contain
only a subset of master file records, one field must contain values or ranges
of values that uniquely identify each replicate file's subset, and therefore
the replicate file itself. If the distribution key field is being changed,
specify the two-letter Adabas field name of that field here. The distribution key field cannot be a multiple-value (MU), a periodic group (PE) or field within a PE group, or a phonetic descriptor field; otherwise, an error occurs either during FDT verification, or when writing to the log file during operation. Note that if any of the replicate files are still using the distribution key, it cannot be changed. |
| Natural Data Format of Distribution Key |
When you specify a new field name for theDistribution Key field, you must specify the field's Natural data type here (for example, A15 for an alphanumeric field of 15 bytes). Specifying the number of digits after the decimal point is not possible for numeric data types. |
| Call User Exit? | Specify Y(yes) if you want the
WADUSER2 subprogram (see Installing the Entire
Transaction Propagator in the Installation for
z/OS and Installation for z/VSE documentation)
called after ETP checks the current transaction record's distribution
key field, if any. ETP checks any distribution key to determine if a change to
the master file must also be made to a specific replicate file. The default is
N (no).
|
| Start Program after ET? | Specify Y (yes) if you want to execute the program
defined in the Modify System
Profile task screen. The default is N (no).
|
By either entering the DIsplay
MAster direct command or selecting the
DI option on the
Master File Definition
Maintenance menu, the Display Master File
Definition screen appears.
23:59:59 ***** ENTIRE TRANSACTION PROPAGATOR ***** 2000-12-24
Display master file definition
DBID FNR
Master file ..* ______ ______
Printer name .. ________ (' ' = terminal)
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Last Flip Tech Canc
|
To display a master file's definition, enter the information in the
fields as described below. To make changes to a master file's definition, enter
the MOdify MAster direct command on the command line
at the bottom of the screen.
| Master File DBID/FNR |
Enter the database ID and file number of the master file you want displayed. If you enter a wild card in either the database ID or file number field, a window appears from which you can select one or more master file definitions for display. |
| Printer Name | To print out the selected master file definitions, enter a valid printer ID here. Leave this field empty to display the master file definition on your terminal. |
By either entering the DElete
MAster direct command or selecting the
DE option on the
Master File Definition
Maintenance menu, the Delete Master File
Definition screen appears.
23:59:59 ***** ENTIRE TRANSACTION PROPAGATOR ***** 2000-12-24
Delete master file definition
DBID FNR
Delete master file ..* ______ ______
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Last Flip Tech Canc
|
Before you delete a master file definition, you must delete all related replicate files; the related log file must be empty.
 |
Warning: Deleting a master file only removes the master file definition from the ETP administration file. The file and its contents still exist as a normal Adabas file in its original database and with its original file number. |
To delete a master file's definition, enter the information in the
fields as described below. To make changes to a master file's definition, enter
the MODIFY MASTER direct command on the command line
at the bottom of the current screen.
| Delete Master File DBID/FNR |
Enter the database ID and file number of the master file you want to delete. If you enter a wild card in either the database ID or file number field, a window appears from which you can select one or more master file definitions for deletion. |
If you have requested the confirmation window using the Modify User Profile function, the confirmation window appears, asking you to confirm the deletion. If either of the following conditions exist:
The log file has entries for the master file;
A master file has one or more replicate files still defined.
- then a warning occurs, and the deletion request will be rejected.