Format of the BBESIN control statement

The BBESIN control statement defines the user description of the GLOBAL command and the DATABASE command, both of which control the behavior of the DB Sensor process.

The commands and their keywords must be specified in the BBESIN data set. This data set usually resides in the input stream. However, it can also be defined as a sequential data set or as a member of a partitioned data set. It must contain 80-byte, fixed-length records. BLKSIZE, if coded, must be a multiple of 80.

The following example shows the correct syntax for the control statement in the BBESIN data set.

Figure 1. Format of the BBESIN control statement
This figure shows the format of the BBESIN control statement. The details are described after this figure.
A BBESIN control statement must conform to the following format:
GLOBAL command
  • Only one GLOBAL command can be specified.
  • The GLOBAL command keywords and their parameters follow the GLOBAL command.
  • A GLOBAL command keyword and its parameter must be connected with an equal sign (=).
  • Each GLOBAL command keyword and value pair must be separated by a comma.
  • Multiple keyword and parameter pairs can be specified.

    Keyword and parameter pairs can span more than one line; type a comma as a continuation character at the end of the first line, and continue the next keyword and parameter pair on the next line.

  • A line that starts with an asterisk (*) is treated as a comment line.
  • The first column must be blank.
DATABASE command
  • One or more DATABASE commands can be specified.
  • The DATABASE command keywords and their parameters follow the DATABASE command.
  • A DATABASE command keyword and its parameter must be connected with an equal sign (=).
  • Each DATABASE command keyword and value pair must be separated by a comma.
  • Multiple keyword and parameter pairs can be specified.

    Keyword and parameter pairs can span more than one line; type a comma as a continuation character at the end of the first line, and continue the next keyword and parameter pair on the next line.

  • A line that starts with an asterisk (*) is treated as a comment line.
  • The first column must be blank.