gtps1m37System Macros

IDOTB-Dump Override Table Build

Use this system macro to identify main storage areas for inclusion in a dump for a particular system error or range of system errors. These areas are in addition to those specified in the SLIST parameter of the SERRC macro. The areas are identified by means of a bitmap.

Each IDOTB macro call generates an entry in a portion of the dump override table called the static override bitmap table (SOBT). The dump overrides are defined by means of a bitmap. There are two sets of IDOTB macro calls in the TPF system:

See TPF General Macros for more information about the SERRC macro.

Format




PREFIX
This parameter is required. Specify one of the following:

letter
An uppercase alphabetic character, coded on the SERRC macro, that is concatenated with the system error number in the console message and in the dump. The letters I and W through Z are reserved for IBM use.

NONE
The designated override will take effect only if no prefix appears in the SERRC macro expansion; that is, the SERRC macro call resulted from a C language perror or exit function call.

SENUM=senum | (senum1-senum2) | MD
The six-digit system error number used to identify the dump. The values specified may be coded two ways:

Use MD to define the overrides for a manual dump. If this parameter is coded, the override will only take effect if the system error number for the error matches the value specified, or falls within the range senum1-senum2.

Note:
No check is made to ensure that senum2 is greater than senum1.

PGMS=(pgm1 [,...,pgmn])
One or more ECB-controlled program names to be associated with this override. If this parameter is coded, the override will only take effect if the system error was issued by one or more ECB-controlled programs specified.

Each program name must consist of a four-character segment name and a 2-character version code. A version code of ** will cause the override to be in effect for all program versions.

Notes:

  1. Due to a limitation of the macro language, only 255 characters may be input per macro call. If more program names are required, code multiple IDOTB macros.

  2. Overrides having an exact match on the failing program version code will take priority over those coded with **.

INCLUDE=(key1 [,...,keyn])
The selective memory dump table (SMDT) values that identify the areas of main storage to be included. See IDATB-Build Selective Memory Dump Table for a list of valid values. This parameter is required.

Because of macro language limitations, only 255 characters may be coded. If you want more characters, use the INCLUD2 parameter.

INCLUD2=(key1 [,...,keyn])
This handles the overflow from the INCLUDE parameter. See the INCLUDE parameter for more information.

COPIES
A single copy or multiple copies of a storage area can be specified, when there are multiple copies for each I-steam or MDBF subsystem.

ONE
Only the copy for the subsystem or I-stream where the error occurred will appear in the dump.

ALL
All copies of the storage area will appear in the dump.

The default is COPIES=ONE.

Note:
This parameter also applies to storage areas defined using more than one pair of start/end addresses on the IDATG macro.

DSECT=YES
This form of the macro is used to generate DSECTs and equates describing the SOBT data structure. It is intended for CP use only.

BUILD
This parameter must be coded by itself and is used to identify the end of the set of IDOTB macro calls. It causes the previous calls to be validated, and if no errors are detected, the static override table will be built.

Entry Requirements

None.

Return Conditions

None.

Programming Considerations

Examples

The operands on multiple IDOTB calls may overlap. When this occurs, system error processing will determine which override to use based on an established priority. Consider the following: