GENMOD GENMOD Use the command to generate a nonrelocatable (MODULE) file on a eMS disk. The format of the command is: r I r , I Genmod [fn r MODULE I fm I ]] I !l I ( (options ... [) ]] I I I I fn
L .J Q£iiQ!!§: [ FROM entryl ] [ TO entry2 ]
r ,
r ,
_______ -1 is the filename of the MODULE file being created. If fn
specified, the file created has a filename equal to that
first entry point in the LOAD MAP. is not
of the
fm is the filemode of the MODULE file being created. If fm is not
specified, is assumed. QQtiQn§: If conflicting options are specified, the last one entered
is used. FROM entry1 specifies an entry point or a control section name that
represents the starting virtual storage location from
which the nonrelocatable copy is generated. T:> entry2 NOMAP STR specifies an entry point or a control section name that
represents the ending virtual storage location from which
the nonrelocatable copy is generated.
includes a load map in the MODULE file, excluding
transient modules. The load map is a variable-length
record placed at the end of the load module.
specifies that a load map is not to be contained in the MODULE file. A module generated with the N)MAP option can later
be invoked as a command; that is, it can be invoked if
its filename is entered. However, subsequent use of the eMS command to load the module may not produce
desirable results. Without a load map, adequate
information is not available for the START command to
execute properly or for issuing another GENMOD command
after debugging has been performed.
invokes the eMS storage initialization routine when the MODULE file is subsequently loaded (see the LOADMOD command description). This routine frees any storage
remaining from a previous program. STR is the default
setting if the MODULE is to be loaded at tbe beginning of
available user storage. If you have issued eMS SET ON, STR causes eMS storage initialization to
release the remaining pages of storage. Section 2. eMS Commands 101
GENMOD NOSTR SYSTEM DOS ALL !21g: If a program running in the user area calls a
transient routine that was generated with the 5TR option,
the user area storage pointers will be reset. This reset
condition could cause errors upon return to the original
program (for example, when OS macros are
issued in the user program) indicates that, when the MODULE is loaded, free storage
pointers are not reset for any storage currently in use. NOSTR is the default setting if the MODULE file is to be
loaded at a location other than the default load address.
indicates that when the MODULE file is subsequently
loaded, it is to have a storage protect key of zero.
indicates that the program may contain macros and,
therefore, should be executed only when eMS/DOS is not
indicates that the program contains DOS macros; CMS/DOS must be active (that is, SET DOS ON must have been
previously invoked) in order for this program to execute. (See Usage Note 2).
indicates that the program: Contains CMS macros and must be capable of running
regardless of whether CMS/DOS is active or not Contains no DOS or as macros Preserves and resets the DOS flag in the eMS nucleus Does its own setting of DOS flags The ALL option is primarily for use by eMS system
programmers. CMS system routines are aware of which
environment is active and will preserve and reset the DOS flag in the CMS nucleus.
1. The GENMOD command is usually invoked following the LOAD command,
and possibly the INCLUDE command. For example, the sequence:
load myprog
genmod testprog
loads the file MYPROG TEXT into virtual storage and creates a
nonrelocatable load module named TESTPROG MODULE. TESTPROG may now
be invoked as a user-written command from the environment.
2. The execution of MODULE files created from programs is not
supported and may give undesirable results. GENMOD is intended for
use with the LOAD command, not the FETCH command. Storage initialization for FETCH is different from that for LOAD. 3. Before the file is written, undefined symbols are set to location
zero and the common reference control section is initialized. The
undefined symbols are not retained as unresolved symbols in the MODULE Therefore, once the file is generated, those
references cannot be resolved and may cause undesirable results
during execution. VM/37Q eMS Command and Macro Reference
Previous Page Next Page