NCAL
LET
ALIGN2
NE OL RENT REUS REFR OVLY XCAL 3704/3705 Control Program suppresses the automatic library call function of the
linkage editor.
suppresses marking of the load module "not executable" in
the event of some linkage editor error condition.
indicates that boundary
linkage editor input file
of 2048-byte boundaries.
alignment is performed
boundaries.
alignment specified in the
is to be performed on the basis
If this option is omitted,
on the basis of 4096-byte marks the load module output as "not to be edited" such
that it cannot be processed again by the linkage editor.
marks the load module output "only loadable".
marks the load module reenterable.
marks the load module reuseable.
marks the load module refreshable.
processes an overlay structure.
allows valid exclusive CALLs in the overlay structure. NAME membername
is the member name to be used for the load module
created. The member name specified here overrides the
default name, but it cannot override a name specified via
the linkage editor NAME control statement.
LIBE libraryname XREF MAP NOTER!! PRINT NOPRINT is the filename of a LOADLIB file where the output load
module is to be placed. The LOADLIB file specified here
may also be used for auxiliary input to the linkage
editor via the INCLUDE statement.
produces an external symbol cross-reference for the modules being processed.
produces only a module map for the processed module(s).
includes only linkage editor control messages in the
printed output file.
displays any linkage editor diagnostic messages at the
user terminal.
suppresses the displaying of diagnostic messages.
spools the linkage editor printed output file to the
printer.
stores the linkage editor output in a eMS disk file with
a filetype of LKEDIT.
produces no output file. Part 4. Generating the 3704/3705 Control Program 309

3704/3705 Control Program Only a subset of the possible linkage editor control statements are
meaningful in C"S. .Since the CMS interface program cannot examine the
input data for the LKED command, all of the control statements are
allowed, even though several of them result in the creation of a load
module file which cannot be used under CMS. For both command options and control statements, see the publication sB£ l!oader. !E"PORAR! The LKED ,command produces one tempora ry file:
fname SYSUTl This file is temporarily created for each link-edit steo: any existina
file with the same file identifier is erased at the beginning of the link edit. This file is placed on the read/write disk with the most
available space. Work space is automatically allocated as needed during
the link edit and returned to available status when the link edit is
complete. Insufficient space causes abnormal termination of the link
edit. PER!!!EN! The LKED command produces two permanent files:
fname LOADLIB
fname LKEDIT
The 'fname LOADLIB' file contains the load created by the
linkage editor. This file is in C"S simulated partitioned data set
format, as created by the CMS OS data management macros. The filename
of the input file becomes the filename of the LOADLIB file, unless the
LIBE option is specified. The filename of the input file also becomes
the member name of the output load module, unless either the NAME option
or a NAME control statement is used. One or more load modules may be
created during a single LKED command execution if the NAME linkage
editor control statement is used in the input file. When the NAME control statement is used, that name becomes the member name in the
LOADLIB file. The replace option of the NAME statement determines
whether existing members with the same name are replaced or retained.
The 'fname LKEDIT' file contains the printed output listing produced
according to the IREF, MAP, or LIST options. This file is created on
disk unless the PRINT or NOPRINT option is specified. The LOADLIB and
LKEDIT files are placed on (1) the disk from which the input file was
read, (2) the parent disk, or (3) the primary disk. Failure to obtain
sufficient space for these files results in abnormal termination of the
linkage editor. Step 9. Save the 3704/3705 Control Program Image on Disk
If you specified SAVE on the GEN3705 command, this step is executed for
you. If you did not specify SAVE on the GEN3105 command, you must issue
the SAVENCP command yourself. The VM/370 command privilege class A, B, or C is required to use
the SAVENCP command. 310 IBM VM/370 Planning and System Generation Guide