bdfi1m0fInstallation and Customization

Activating the TPFDF Product

The following provides detailed steps to get the TPFDF product into operational status.

Note:
Multiple database facility (MDBF) users must repeat these instructions for each subsystem.

Initialize the TPFDF Files

Attention:
Do not initialize the files listed in Table 7 or in Table 8 if you have already installed the TPFDF product on this TPF system because you will lose the current contents of these files.

If the TPFDF product will be used in a multiple database function (MDBF) environment, all TPFDF files must be initialized in every subsystem and, for those that are subsystem user unique, for every subsystem user.

Table 7. Control Files Required by TPFDF

DSECT RECORD TYPE REC ID SIZE NBR ORDINAL SSU *
GR31SR #IDFUS FDFF L1 1 #GR31SRF-#GR31SRL unique
GR0VSR #IDFU4 FDFB L4 1 #GR0VSRF-#GR0VSRL unique
GR0YSR #IDFU4 FDF9 L4 1 #GR0YSRF-#GR0YSRL unique
GR27SR #IDFU4 FDF8 L4 1 #GR27SRF-#GR27SRL unique
Note:
* In a Non-MDBF environment define all the records as common.

Initializing the TPFDF Control Files Using ZAREC

Before you can use TPFDF commands (including ZUDFM OAINIT), you must initialize some control files on the real-time database. These files, shown in Table 7, are initialized using the TPF command, ZAREC.

  1. Initialize GR31SR (ordinal number 0, file type #IDFUS, and record ID FDFF).
    ZAREC LIDFUS.0 0 FDFF0000C3E5C2C3
     
    ZAREC LIDFUS.0 8 0000000000000000
     
    ZAREC LIDFUS.0 10 001A000000000000
    
  2. Initialize GR0VSR (ordinal number 0, file type #IDFU4, and record ID FDFB).
    ZAREC LIDFU4.0 0 FDFB0000C3E5C2C3
     
    ZAREC LIDFU4.0 8 0000000000000000
     
    ZAREC LIDFU4.0 10 001A000000000000
    
  3. Initialize GR0YSR (ordinal number 1, file type #IDFU4, and record ID FDF9).
    ZAREC LIDFU4.1 0 FDF90000C3E5C2C3
     
    ZAREC LIDFU4.1 8 0000000000000000
     
    ZAREC LIDFU4.1 10 001A000000000000
    
  4. Initialize GR27SR (ordinal number 2, file type #IDFU4, and record ID FDF8).
    ZAREC LIDFU4.2 0 FDF80000C3E5C2C3
     
    ZAREC LIDFU4.2 8 0000000000000000
     
    ZAREC LIDFU4.2 10 001A000000000000
    

TPF Operations provides a full description of the ZAREC command.

Initializing Noncontrol Files Using ZUDFM

Use the ZUDFM OAINIT command to initialize the fixed files described in Table 8.

See TPFDF Utilities for more information about how to use ZUDFM OAINIT and other ZUDFM commands.

Table 8. Non-Control Files Required by TPFDF

DSECT RECORD TYPE REC ID SIZE NBR ORDINAL/TYPE SSU 2
GR0ZSR3 #GR0ZSR FDF4 L2 30 0-29 per processor common
GR25SR #IDFU4 FDF6 L4 1 #GR25SRF-#GR25SRL unique
GR26SR POOL FD00 L4 N/A LT unique
GR28SR #IDFC4 FDF7 L4 1 #GR28SRF-#GR28SRL common
GR29SR POOL FD01 L4 N/A LT common
GR3MSR #GR3MSR FDF3 L2 99 0-98 common
GR3NSR POOL FD03 L4 N/A LT common
GR3OSR #IDFC4 FDF5 L4 1 #GR3OSRF-#GR3OSRL common
GR32SR #IDFCL FDFD L2 1 #GR32SRF-#GR32SRL common
IRA5DF #IDFC4 FDA5 L4 1 #IRA5DFF-#IRA5DFL common
IRCADF #IDFC4 FD1C L4 1 #IRCADFF-#IRCADFL common
IRCBDF #IRCBDF FD1D L4 200 One Ordinal per CRUISE ordinal table common
IRCCDF #IDFC4 FD1E L4 1 #IRCCDFF-#IRCCDFL common
IRCDDF #IDFC4 FD1F L4 1 #IRCDDFF-#IRCDDFL common
IRCEDF POOL FD21 L4 N/A LT common
IRCFDF 3 #IRCFDF FD16 L4 499 0-498 per processor common
IRCGDF 3 #IRCGDF FD17 L4 499 0-498 per processor common
IRCHDF #IRCHDF FD18 L4 32 0-31 common
IRCIDF 3 #IRCIDF FD19 L4 499 0-498 per processor common
IRCJDF #IRCJDF FD1A L4 32 0-31 common
IRCKDF #IRCKDF FD1B L4 200 One Ordinal per CRUISE ordinal table common
IRCMDF 4 #IRCMDF FD22 L4 997 0-996 per processor common
IRCTDF POOL FD23 L4 N/A LT common
IRCXDF POOL FD24 L4 N/A LT common
IRDCDF POOL FD0A L4 N/A LT common
IRDIDF 1 #IRDIDF FDE5 L4 256 0-255 per (processor+1) common
IRDKDF #IDFCS FDE4 L1 1 #IRDKDFF-#IRDKDFL common
SRCK1P POOL FD10 L2 N/A LT common
SRHH1P #SRHH1P FDDF L4 10 0-9 common
SRMP1A #SRMP1A FDE0 L4 10 0-9 common
SRM31A #SRM31A FDDC L4 10 0-9 common
SRM41A1 #SRM41A FDDE L4 59 0-58 per processor up to the first 8 processors common
SRM51A1 #SRM51A FDDD L4 59 0-58 per processor up to the first 8 processors common
SRM61A #SRM61A FDE1 L4 10 0-9 common
SR54BA #IDFC4 FDDB L4 1 #@SR54BA common
IR00DF POOL FD08 L1 N/A LT common
IR01DF #IDFCL FDE1 L2 1 #IR01DFF-#IR01DFL common
IR02DF #IR02DF FDE7 L1 26 0-25 common
IR03DF #IR03DF FDE6 L1 26 0-25 common
IR04DF POOL FD09 L1 N/A LT common
Note:
IR00DF-IR04DF are used for TPFDF education.
Note:
1 This is a partitioned file and the ordinals are spread out over the partitions. The number of ordinals listed is the number for each partition. Set the number of partitions in the DSECT to 1 plus the number of loosely-coupled processors.
Note:
2 In a non-MDBF environment, define all the records as common.
Note:
3 This is a partitioned file and the ordinals are spread out over the partitions. The number of ordinals listed is the number for each partition. Set the number of partitions in the database definition (DBDEF) macro to the number of loosely coupled processors.
Note:
4 Use the following formula to calculate the number of ordinals when using CRUISE with MRC support:
#ord = prime (mr / 267 / avgch)

where,

#ord
is the ordinal, which is a prime number, to use for the #IRCMDF file.

prime
is the function to calculate the closest prime number.

mr
is the maximum estimated number of multiple references in a file. You can use the RCI count from the recoup phase 1 activity log as a reference.

267
specifies the number of LRECs that are in a data block for the MRC subfile.

avgch
is the average number of overflow blocks for each ordinal number in the #IRCMDF database. When using multiple reference check (MRC) support, the recommended number of chains to balance performance and resource (fixed files) requirements is 1.5. The greater the avgch value, the fewer ordinal (fixed files) requirements needed and the more CRUISE capture and restore processing time increases. If you decrease the avgch value, the ordinal (fixed files) requirements needed increases and CRUISE capture and restore processing time decreases. See your database administrator for more information about specifying the avgch value. See TPFDF Utilities for more information about MRC.

Initialize Command Help

Enter ZUDFM OAHINIT to initialize the help facility, which allows you to get online help for commands.

Initialize Database Information Displays

Enter ZUDFM OAI/DBTAB/REL/CREATE to initialize the relations database, which allows you to display information about the relationship of files in the database. After the TPFDF product is initialized, enter the command any time you add or change a file on the TPFDF database.

Creating a Parameter Table Index

To create a parameter table index, do the following:

Defining Tape Labels for the TPFDF Product

The following tapes, used by the TPFDF product, require that tape labels are defined. This is done with the TPF command, ZTLBL. See TPF Operations for more information.

SPR
input/output

BFA
input/output

Creating the Macro Label Set (MLS) Program

To run the offline MLS program, see member MLS in the sample JCL that is shipped with the TPFDF product. The sample JCL assembles the data macros and the runs segment UF0F, which creates the MLS.

Note:
UF0F is assembled and link-edited by SIP.

Defining the Database Definition (DBDEF) Program

The DBDEF program must be defined in main storage before being accessed by an application. To ensure this, define the DBDEF programs using the PRELOAD option in IBMPAL. Otherwise, DBDEF programs are defined using E-type loaders and could be treated as file resident by the TPFDF product if the core resident program areas are full.