Example: Using MF370CTL.CFG to Set Locations

Restriction: This topic applies to Windows environments only.

The following example illustrates how to use a MF370CTL.CFG file to configure project file locations.

Consider the following project directory structure:

Project directory: c:\bugs\envtest
Source code directory: c:\bugs\envtest\source
Listing file directory: c:\bugs\envtest\listing
Object and executable file directory: c:\bugs\envtest\debug

Setting the following environment variables configures this structure:

SYSLIN=.\DEBUG
SYSLIST=.\LISTING
SYSLMOD=.\DEBUG

If run from the current directory command line the command:

RUN MF370CHK SOURCE\BR14 NOANIM LIST;

results in BR14.OBJ and BR14.390 placed in \debug, while the listing file BR14.PRN is placed in \listing.

To use a MF370CTL.CFG file to make these settings, you would configure the file as follows:

*------------------------------------------------------------
* The following environment variables take a single directory:
* SYSIN - Macro input .MLC files
SYSIN=.
*
* SYSLIST  - Assemble and Link listing files .MAT .PRN .LST
SYSLIST=.\listing
* SYSWORK  - Assemble, Link and Animator/370 work files .BAL .IDF/.IDX
SYSWORK=.
* SYSPUNCH - Assemble output .PCH files for PUNCH statements
SYSPUNCH=.
* SYSMPC   - Assemble input precompiled macros .MPC
SYSMPC=.
* SYSLIN   - Link input .LIN files and Assemble output .OBJ files
SYSLIN=.\debug
* SYSLMOD  - Link output load-member .390 files
SYSLMOD=.\debug