3704/3705 Control Program FI1ES One or two permanent files may be created during a
successful assembly:
fn TEXT fn LISTING
The fn TEXT file contains the output object module if the LOAD option is
in effect. The fn LISTING file contains a listing of source statements,
assembled machine code, and other associated information based on the
options selected. This file is created unless the NOPRINT or NOLIST options are selected. The LISTING and TEXT files are placed on (1) the
disk from which the source file vas read, (2) its parent or (3) the
primary disk, unless you created a file definition for these files
placing them on a non-DASD device. Failure to obtain sufficient space
for these files results in abnormal termination of the assembly. SPECIAL CONSIDERATIONS FOR THE STAGE 1 ASSEMBLY The Stage 1 assembly can be very The amount of time the
Assembler takes depends upon the macro options selected and th"e number
of users on the V"/370 system.
The LISTING file produced by the Stage 1 assembly is quite large. If
you let the ASM3705 command option default to DISK, much of the space on
your A-disk is used. Therefore, V"/370 recommends that you specify the PRINT option when you issue the AS"3705 command. Also, there are many
macro expansions that make the LISTING file larger. V"/370 recommends
that you insert a 'PRINT NOGEN' assembler statement in front of the
first macro instruction in the input file to suppress the printing of
the macro expansions and reduce the size of the LISTING file. You should examine the output of the Stage 1 assembly carefully and
produce a list of resource IDs, with their characteristics, for the
operations personnel. The cross-reference list for operations should
include: • • I • • Resource ID
Type of resource (line or terminal)
Type of line (EP-mode or variable)
Location Step 7. The Stage 2 Generation Procedure
During the Stage 2 generation procedure the TEXT file produced in Step 6
is scanned. That TEXT file contains several job steps of 3705 Assembler
source statements with embedded as JCt statements. The Jet statements
are removed and a unique C"S 3705 Assembler source file is created for
each job step in the input file. An EXEC procedure is also created to
assemble and link edit the source files. When the EXEC procedure is
invoked, it produces the load module file (and, optionally, saves a copy
of the control program in page-format on a CP-owned volume). Part 4. Generating the 3704/3705 Control Program 305

3704/3 7 05 Control Program THE GEN3705 COMMAND Use the CMS GEN3705 command to invoke the stage 2 service program.
Command options let you determine whether or not GEN3705 includes a
command in the EXEC procedure to save a copy of the load module on disk,
or if GEN3705 invokes the EXEC procedure automatically. The format of the GEN3705 command is: r----------------------.--------------------------------------.----------------------------- I GEN3105 fname fty pe [fmode] [ (options ••• [) ]] I I I I , I L- options:
r , IRUN I I NORUNI L .I r , I SAVE I INOSAVEI L .I fname specifies the filename of the Stage 2 input stream produced by the Stage 1 assembly. The file must contain fixed-length,
SO-character records.
ftype
fmode
specifies the filetype of the stage 2 input stream.
filetype is normally TEXT. specifies the filemode.
The
If duplicate or conflicting options are specified, the last option
entered on the command line is in effect. RUN causes the output EXEC file to be executed at the
conclusion of the GEN3705 processing. NORUl! SAVE suppresses the execution of the output EXEC file.
includes a SAVENCP command create a page-format copy of
on a VM/370 CP-owned volume.
in the output EXEC file to
the 3704/3705 control program
If you are generating a 3705 Emulator control program with
a Type 4 channel adapter, do not use the SAVE option; an
error message will result from the SAVENCP command. In
this case, you must specify the SAVENCP command yourself,
specifying the CAMOD option.
does not include the SAVENCP command in the output EXEC file.
Three types of permanent files are created when the GEN3705 command
successfully executes: ASK3705, TEXT, and EXEC files. fnameOO ASK3705 fnameO 1 ASM3705 fnamenn ASM3705 fnam eLO TEXT fnam eLO TEXT fnam eLn TEXT 306 IBM VM/370 Planning and System Generation Guide
fname EXEC