M.AD Values

Perform the following steps to set up the M.AD entries (M.AD Values):

Add a component Type to an application in M.AD for the load libraries and define the load library names in the Names section. Example Names entries are shown in the M.AD Names Entries for LOAD figure.
Add a component Type to an application in M.AD for the source libraries required for load-only processing. Example Name entries are shown in the M.AD Names Entries for LCTL figure.
Add a Generate association for the LCTL component Type to indicate that a LOAD will be generated and to point to the component type of the (LOAD) libraries to be used. An example entry is shown in the M.AD Associations Entry for LCTL figure.
The flags in M.AD for the test level should be set up so that associations are moved to the HOLD level. However, at least the test level generate needs to be done so the module has been copied. An example entry is shown in the M.AD Flags Screen for LCTL figure.

Names Entries for LOAD

Example M.AD Names entries are shown in the following figure for application component type LOAD.

M.AD Names Entries for LOAD

WZZMADD D/N BLM LIBRARY NAMES TABLE (PROD) BROWSE MODE
Command ===>   Scroll ===> CSR

List Commands: L Locate Entry, U Update Mode

                   Lib     Library
Type Clas   Lev    Type    Name

LOAD        FIXH   PDS     BLM.FIXH.LOADLIB
LOAD        FIXT   PDS     BLM.FIXT.LOADLIB
LOAD        HOLD   PDS     BLM.HOLD.LOADLIB
LOAD        PROD   PDS     BLM.PROD.LOADLIB
LOAD        TEST   PDS     BLM.TEST.LOADLIB
****************************** Bottom of data *******************************

Name Entries for LCTL

Example M.AD Names entries are shown in the following figure for application component type LCTL.

M.AD Names Entries for LCTL

WZZMADD D/N BLM LIBRARY NAMES TABLE (PROD) BROWSE MODE
Command ===>    Scroll ===> CSR

List Commands: L Locate Entry, U Update Mode

                   Lib     Library
Type Clas   Lev    Type    Name

LCTL        FIXH   PDS     BLM.FIXH.CHKOUT.EMPTYSRC
LCTL        FIXT   PDS     BLM.FIXT.CHKOUT.EMPTYSRC
LCTL        HOLD   PDS     BLM.HOLD.CHKOUT.EMPTYSRC
LCTL        PROD   PDS     BLM.PROD.CHKOUT.EMPTYSRC
LCTL        TEST   PDS     BLM.TEST.CHKOUT.EMPTYSRC
****************************** Bottom of data *******************************

Association Entry for LCTL

An example M.AD Associations entry is shown in the following figure for application component type LCTL.

M.AD Associations Entry for LCTL

WZZMADA D/A BLM ASSOCIATIONS TABLE (PROD) UPDATE MODE
Command ===>    Scroll ===> CSR

List Commands: A Add Entry, L Locate Entry, B Browse Mode
Line Commands: D Delete

                             Target               Assoc   Assoc   Assoc
   Type    Clas   Association Env.   Set   Seq. Appl    Type    Clas

   LCTL                G              LOAD   1    BLM     LOAD
****************************** Bottom of data ********************************

Flag Entries for LCTL

An example M.AD Flags screen is shown in the following figure for application component type LCTL.

M.AD Flags Screen for LCTL

WZZMADF D/F SAMP CONTROL FLAGS TABLE (PROD) BROWSE MODE
Command ===>    Scroll ===> CSR

List Commands: L Locate Entry, U Update Mode

                  Promote   Version   Generate   Implement   Pack Keep
Type Clas   Lev   Method    Control   Opt Chk   Opt   Chk   Src Memb

LCTL        FIXH    A         N
LCTL        FIXT    A                  R    Y
LCTL        HOLD    A         N
LCTL        PROD              N
LCTL        TEST    A                  R    Y

These flag settings will force a successful Generate to be done at the TEST levels, and then on the promotes, the LOAD will be moved up with the component. The Version Control flags are set to N in this case, because it represents the situation where the component versions are not checked out based upon another version, but instead delivered from an external source.