DB statement

The maximum number of DB statements that can be specified is 100.

The following subsections describe the syntax of the first line and the second line of the DB statement.

DB statement: Line 1

This statement can be specified for both HALDB and non-HALDB. It gives the values of changing randomizing parameters for a database, and controls reports to be printed.

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
--------------------------------------------------------------------------------
dbdname kpmod      rbn      anch blksz  kst  kln  bytes  HDAM PARTINI--S
                                                         PHDAMPARTDELPSH
                                                              AUTOINI

Position

Description

1

Required. Left-aligned. The name of the DBD for the database to be processed.

9

Optional. This field can contain either of the following two codes:

1

The keys for this database are skipped.

Blank

The keys for this database are processed. Blank is the default value.

10

Optional. This field can contain either of the following two codes:

1

Discontinue reading the control statements. Any control statements that follow this control statement are not effective.

Blank

Continue reading the control statements. Blank is the default value.

11

Optional. 1 - 8 characters, left-aligned. The name of a user-supplied randomizing module. This field is used to override the (default) DBD value.

20

Optional. Used to override the (default) DBD value. It must contain the maximum relative block number that you want to allow a randomizing module to produce for this database. This value determines the number of control intervals or blocks in the root addressable area. It must be a 7-digit, unsigned decimal integer (with leading zeros if needed).¹

29

Optional. Used to override the (default) DBD value. It contains the number of RAPs desired in each control interval or block in the root addressable area. It must be a 3-digit, unsigned decimal integer (with leading zeros if needed).¹

34

Optional. Used to override the (default) DBD value. It contains the database block size (or control interval size). It must be a 5-digit, unsigned decimal integer (with leading zeros if needed).¹

41

Optional. Used to override the (default) DBD value. This value must be the starting position of the key field in bytes relative to the beginning of the segment. It must be a 3-digit, unsigned decimal integer (with leading zeros if needed). The starting position for the first byte of a fixed-length segment is 001.

46

Optional. Used to override the (default) DBD value. This value must be the length of the root segment’s key field in bytes. It must be a 3-digit, unsigned decimal integer (with leading zeros if needed).

51

Optional. Used to override the (default) DBD value. This must be the maximum number of bytes of a database record that can be stored in the root addressable area. It also must be continuous, and not interrupted by calls to another database record. It must be a 5-digit, unsigned decimal integer (with leading zeros if needed).¹

58

Optional. This field can contain one of the following three kinds of strings:

HDAM

This entry indicates that the input DBD is not HDAM. This optional field is used to override the database organization that is specified in DBD. If the input DBD is not HDAM, but must be simulated as HDAM, this field is required.

PHDAM

This entry indicates that the input DBD is not PHDAM. This optional field is used to override the database organization that is specified in the DBD. If the input DBD is not PHDAM, but must be simulated as PHDAM, this field is required. The PARTINI or AUTOINI is also required at column 63.

Blank

No override of the database organization. Blank is the default value.

Requirement: If HDAM or PHDAM is coded in column 58, all DBD parameters must be specified in the DB statement or the PART statement.

63

Optional. This option is effective when the database simulates as PHDAM. This field can contain one of the following four kinds of strings:

PARTINI

This entry indicates that each partition definition must be followed and simulated as a PHDAM database. The partition definitions using PART statements are needed for all partitions.

PARTDEL

This entry indicates that the input DBD is PHDAM or PHIDAM and simulated as an HDAM database. No following PART statement is needed.

AUTOINI

This entry indicates HD Tuning Aid to assign the partition names automatically, and to simulate a PHDAM database. Only partition high keys or partition selection strings are required in the PART statement. ²

Blank

Blank means that there is to be no partition deletion or partition initialization. Blank is the default.

70

Optional. This option is effective when the database simulates as PHDAM. This field can contain one of the following three codes:

-

This option requests that the DBD Parameters and Overrides reports are not printed.

P

This option requests that the DBD Parameters and Overrides reports be printed with partition override information.

Blank

This option requests that the DBD Parameters and Overrides reports be printed without the partition information. Blank is the default value.

71

Optional. This statement is effect when the database simulates as PHDAM. This field can contain one of the following three codes:

-

This option requests that the HALDB Process Summary report not be printed.

S

This option requests that the HALDB Process Summary report be printed with all partition information.

Blank

This option requests that HALDB Process Summary report be printed with any root key assigned partition information. Blank is the default value.

72

Optional. This statement is effective when the database simulates as PHDAM. If the input DBD is not PHDAM, S or H is required. This field can contain one of three codes:

S

This option requests that the partition selection exit module name be changed or that the partition selection method be replaced with the partition selection exit.

Requirement: The name of the new partition selection exit module must be defined on the second line of the DB statement.

H

This option requests that the method for partition selection be replaced with the high key method.

Blank

This option requests that the method for partition selection not be replaced.

DB statement: Line 2

This statement is effective when the database simulates a PHDAM.

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
--------------------------------------------------------------------------------
          pselexnm

Position

Description

11

Optional. 1 - 8 characters, left-aligned. The name of a user-supplied partition selection exit module. It is used to override the value in the RECON data set. If "S" is specified in column 72 of the preceding DB statement, this field is required.