Tc perform the assembly in the CMS virtual machine, follow these
steps: 1. The CMS virtual lIachine (OSCMS) must have access to the supervisor
macro instructions in These macro instructions
reside on volume DLIBA2, owned by the OSVSSYS virtual machine. To
have access to these macro instructions, enter the following
commands from the OSCMS terminal:
cp link osvssys 351 351 rr
acc 351 b
filedef cmslib disk osgenlib maclib b dsn s1s1 agenlib
global maclib osgenlib
These com.ands can be placed into a CMS EXEC and given control by
use of a single command. For details about creating EXEC procedures, refer to the 2. The eMS assembler requires two special input files: • One eMS file to contain the job control
the syste. generation macro instructions.
fi1ena.e, such as STG1IN OJCL. statements that precede
File it with a unique • 0 ne eMS file
instructions, an
unique filename, ASSEMBLE. (The
statement file.)
to contain: the system generation macro END statement, and a 1* card. File it with a
such as STG1IN, and the required filetype of
file type identifies it as an assembler source With both requirements in step 2 met, assemble the stage I input in
the eMS virtual machine by issuing the CMS co.mand:
assemble stg1in
The assembly output is these two CMS files: STG lIN TEXT STG1IN LISTING (punch output)
(printer output)
The punched output is the job stream for stage II input. The printed
output documents the expansion of each specified macro instruction
including the punch statements that comprise the input to stage II. When assembling under eMS, eMS displays assembly errors on the
terminal. A user does not have to wait for the listing to be printed.
Before retrying the assembly, use the eMS editor to correct the source
file. When the assembly is finally error-free, the two output files
which reflect the final assembly can then be printed, punched, or used
to create jcb streams.
122 IBM VM/370 operating Systems in a Virtual Machine

To punch the required job stream for stage I execution to the as/vs
machine's virtual card reader, enter the following commands:
cp specl punch to osvssys cont punch stglin ojcl (noheader)
punch stglin assemble (noheader)
cp spoel punch nocont
cp close punch
By using the CONT operand in the SPOOL PUNCH command, a user
cencatenates multiple CMS files into one punch output file.
If, at the OS/VS machine, a user enters this CP command before
executing stage I: Icp spcel punch to oscms
and subsequently enters: Icp close punch VM/370 transfers the stage I output to the OSCMS virtual card reader. At the OSCHS terminal, issue this command:
readcard stglin text
This CMS file corresponds to the punched output of the stage I assembly
(STG1IN TEXT) performed in the OSCMS machine. VM/370 directs the
assembly listing, output, in the absence of any printer spooling te the real STAGE II PROCESSING The stage I output is a job stream that contains a number of individual
jobs. These jobs set up system data sets, assemble nucleus modules, and
copy modules from the distribution libraries to the new system residence
volume.
If the three object module utility data sets used by the assembler
during stage II have not been allocated and cataloged, a user can do
this by creating the appropriate job stream as a CMS file. Give it a
unique filename, such as STG2IN DSALLOC. To transfer the stage II input to the OS/iS machine, issue these commands: cp specl punch to osvssys cont punch stg2in dsalloc (noheader)
punch stg1in text (noheader)
cp speel punch nocont
cp close punch
Section 4. OS/VS in a Virtual Machine 123