A dynamic BERT table

Figure 1 illustrates an alternative method of defining the BERT table from Figure 1 through use of a dynamic table.

Figure 1. Example of a Dynamic BERT Table

MYBRTTB  $BERTTAB TABLE=DYNAMIC.
         $BERTTAB CBTYPE=JQE,NAME=UNOTIFY,CBOFF=*,               X
                LEN=8
         $BERTTAB TABLE=END

To create the installation BERT table coded illustrated in Figure 1 or Figure 1, you need to code the following on the $BERTTAB macro:

Operand	Description
CBTYPE=JQE	The control block type with which the data is to be associated. In this case the data is to be associated with a JQE. You can also associate your own data with a Class Attribute Table (CAT), WLM Servic Class Queue head (WSCQ), or your own installation control block type. By convention, the JES2 table will not use CBTYPE= values beginning with the letters U or V. Installation CBTYPE= values should therefore begin with one of these two letters to avoid potential conflict with future JES2 types.
NAME=UNOTIFY	A unique name which identifies the specific date within the control block type. By convention, the JES2 table will not use NAME= values beginning with the letters U or V. Installation NAME= values should therefore begin with one of these two letters to avoid potential conflict with future JES2 types.
CBOFF=*	The offset within the control block of the data defined by this table. CBOFF=* indicates that the offset is to be determined at run time. The $DOGBERT ACTION=GETOFFSET macro should be coded (with CBTYPE= and NAME= equal to the specification on the $BERTTAB) to locate the data in the control block.
LEN=8	The length of the data area defined by the $BERTTAB.