In addition to coding the installation BERT table, you need to do the following:

• Code Exit 0. Exit 0 code must:
  • Obtain the $UCT and place the $UCT's address in the $HCT.
  • Initialize the $UCT.
  • Place the installation work selection table address in the MCTBRTTU field in the $MCT in module HASPTABS. This is not necessary for dynamic tables. Dynamic tables should be linked to the table pair by placing a LOAD initialization statement in your JES2 initialization stream for the module containing the dynamic BERT table.
• Provide routines (such as installation exits) that fill in or use the BERT data. These routines should access the data as follows:
  • For extensions to the JQE (CBTYPE=JQE):
    • Access the JQA using the $DOGJQE macro.
    • Determine the offset of the data within the JQA using the $DOGBERT ACTION=GETOFFSET service. The address of the data can then be computed by adding this offset to the JQA address.
  • For extensions to the CAT (CBTYPE=CAT):
    • Access the CAT using the $DOGCAT macro.
    • Determine the offset of the data within the CAT using the $DOGBERT ACTION=GETOFFSET service. The address of the data can then be computed by adding this offset to the CAT address.
  • For installation-defined CBTYPE values:
    • Obtain storage to contain the control block and a PREBERT. The PREBERT must precede the control block in this storage. The length of the control block (without the PREBERT) can be obtained using the $DOGBERT ACTION=GETLENGTH macro.
    • Access the data using the $DOGBERT macro. Use ACTION=FETCH to read the BERT data from the checkpoint and ACTION=RETURN to return it to the checkpoint.