MFASM

Use the MFASM command to assemble and link Assembler applications in one step, producing executable subroutines, and debugging modules.

Syntax:

MFASM filename.mlc [option ...][;]

Parameters:

filename: The name of an Assembler source file.
option: An Assembler compiler directive

Comments:

MFASM produces the following files:

filename.obj - An object module used by the assembler linker
filename.idf and filename.idx - debugging files used by the Assembler debugger
filename.390 - An executable Assembler program.

The most commonly-used Assembler compiler directives are:

NOANIM
NOLIST
BAL
AMODE(31)

Examples:

MFASM test.mlc NOANIM

Here the NOANIM option is also used to suppress the generation of unnecessary debug files. To ensure that the resulting executable file, in this example TEST.390, is picked up by the COBOL runtime, move it to the same subdirectory as other COBOL executables in the application. At CALL time, the COBOL runtime searches for and loads executables with the .390 file extension as it would any other executable file with extensions such as .dll.

Example 2 - Producing Assembler Data Tables

Assembler data tables are produced by using the OMF (MOD) directive to generate files with the .mod extension as follows:

MFASM test.mlc OMF(MOD)NOANIM NOLIST

To ensure that the resulting .mod file, in this example test.mod, is loaded into memory along with other CICS programs by use of the EXEC CICS LOAD command, move it to the same subdirectory as other COBOL executables in the application.