Building some members requires that multiple workstation commands be issued. The FLMLTWST translator issues a workstation command for each action it finds. The first action is the one specified by the ACTION parameter to FLMLTWST in the language definition, or the default action if none is specified. Additional actions can be performed by using the architecture CMD statement with the ACTION keyword. The ACTION keyword must be followed by an action defined in the FLMLTWST translator.

Figure 1 shows an architecture member that links two object modules together and then runs another workstation command before transferring the outputs to the MVS™ system. In this example, the second command runs the OS/2 resource compiler to add the information from a binary resource file to the .exe generated by the link.

*
LKED EXE                 * link language
*
KREF OBJ                 * include generated object modules
*
INCL  MAHJONGC ARCHDEF   * archdef that produces MAHJONGG OBJBIN
INCL  TILE     ARCHDEF   * archdef that produces TILE OBJBIN
SINC  MAHJONGG DEF       * DEF source
*
LOAD  MAHJONGG EXEBIN    * Generated .exe file
LMAP  MAHJONGG MAP       * Generated .map file
*
* Run resource compiler after the link completes
*
CMD ACTION RCEXE
*
KREF OUT1                * include generated .res file
*
INCLD MAHJONGG RC        * Source that produces MAHJONGG RESBIN
*

The order of the INCL and INCLD statements in the previous example is not important. The FLMLTWST translator determines which files are inputs to each step based on information defined in the translator. The appropriate options are also added for each of the inputs and outputs by the FLMLTWST translator.