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

3704/3705 Control Program
A separate ASM3705 file is created for each assembly job step in the
stage 2 input file. Each ASM3705 file created by GEN3705 is given a
unique filename of the form 'fnamenn'. The first characters of the
input filename are concatenated with a two-digit number. For example,
if the input file is NCP320 TEXT, the output files are NCP32000 ASM3705, NCP32001 ASM3705, ••• , NCP320nn ASM3705. These files are used as input
to the 3705 Assembler when it is invoked by the stage 2 EXEC procedure.
The GEN3705 program creates several TEXT files. These files contain
only linkage editor control statements, those statements necessary to
build the load module file for the 3704/3705 control program. Each of
the TEXT files created is given a unique filename of the form 'fnameLn'.
The first six characters of the input filename are concatenated with the
letter L and a number. For example, if the input file is NCP320 TEXT, the linkage editor output files are NCP320LO TEXT, NCP320Ll NCP320Ln TEXT. The filenames assigned to the linkage editor and assembler files must
be different. If the filenames were the same, when the ASK3705 files
are later assembled, TEXT files would be produced which would have file
identifiers that conflict with the linkage editor files.
The EXEC macro file created contains the CKS commands necessary to
invoke the ASM3705 command for each of the ASK3105 files, and to
subsequently invoke the linkage editor for each of the Assembler TEXT files. If the SAVE option is specified, the EXEC file also contains the SAVENCP command which loads the 3704/3705 control program image into
virtual storage and creates the page-format copy of it on a CP-owned volume. The filename of the stage 2 input file is used as the 'ncpname'
operand for the SAVENCP command. SPECIAL CONSIDERATIONS FOR THE STAGE 2 GENERATION PROCEDURE VM/370 recommends that you specify the RUN option. When the RUN option
is specified, GEN3705 stacks a CKS command line to cause the EXEC file
to execute following the completion of the GEN3705 program. This
technique minimizes the virtual storage overhead during the EXEC file
execution.
If you do not specify the SAVE option, you have to explicitly issue
the SAVENCP command. If you do specify the SAVE option, be sure that
the input file has the same filename as the entry reserved in the system
name table. The system name table is created when a NAKENCP macro is
issued during a VM/310 system generation. The NAKENCP macro is
described in "Part 2. Defining Your VK/370 System" and the building of
the system name table is described in "Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS)." Step 8. Invoke the EXEC Procedure Created in Step 7
If you specified RUN on the GEN3105 command, this step is executed for
you. If you did not specify RUN on the GEN3705 command, you must invoke
the EXEC procedure that the GEN3705 program created.
Part 4. Generating the 3704/3705 Control Program 307