370Q/3 7 05 Control Program
If duplicate or conflicting options are specified, the last one
entered in the command line is the one in effect. NOXREF RENT
DECK NOLOAD NOLIST PRINT NOPRINT includes a cross-reference symbol table in the LISTING
file.
suppresses the cross-reference symbol table.
checks the source file to see if it satisfies reentrancy
requirements.
suppresses the
requirements.
ch eck for sa tisfact ion of reentrancy
spools the output object module, fn TEXT, to the punch.
suppresses the spooling of the output object module, fn TEXT, to the creates a TEXT file on disk for the program that was
assembled.
suppresses the creation of a TEXT file on disk for the
program that was assembled.
produces a LISTING file.
produces no LISTING file.
spools the LISTING file to the printer.
puts the LISTING file on disk.
produces no LISTING file. LINECOUN nn
specifies the number of lines per output printer page. A
default of 55 lines is assumed.
Note: All of the options of the 3705 XF Assembler are supported and may
be used with the ASM3705 command, with the exception of ALIGN/NOALIGN
and TEST/NOTEST. Three files are temporarily created for each
assembly:
fn SYSUTl fn SYSUT2 fn SYSUT3 Any existing files with the same file identifiers are erased at the
beginning of the assembly. These files are placed on the read/write
disk with the most available space. Work space is automatically
allocated as needed during the assembly and returned to available status
when the assembly is complete. Insufficient space causes abnormal
termination of the assembly. 304 IBM VM/370 Planning and System Generation Guide

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