VM/370 UTILITY PROGRAMS A user should also consider the VM/370 utility and service programs. Many of these programs perform functions that are practically identical
to the as/vs utilities: • DDR: The VM/370 DASD dump restore (DDR) service prograa can be obtained by running it in stand-alone mode. • IBCDASDI: The VM/370 IBCDASDI program is available on the system aIsk:--It has a filename of IPL and a fi1etype of IBCDASDI. An added
feature cf the VM/370 version is its ability to initialize virtual
disks (minidisks). • The VM/370 ICAPRTBL program is available by using the CP commands LOADBUF and LOADVFCB. Use the class D command LOADBUF to
load the universal character set buffer (UCSB) or forms control
buffer (FCB) for specific real printers. (For details about the LOADBUF command, refer to the Also, use
the class G command LOADVFCB to load an FCB for specific virtual
printers. (For details about the LOADVFCB com.and, refer to For a description of the DDR and IBCDASDI programs and their operating
procedures, refer to the STAGE I PROCESSING IN THE CMS VIRTUAL MACHINE
To precess stage I, the eMS virtual machine can be used to:
1. Create the stage I input job stream (job control statements and
system generation macro instructions) • 2. Execute a single assembly.
3. Check the assembly listing for errors.
If any errors occur, repeat all three steps of the stage I procedure. The stage I assembly can actually be executed in either the CS/VS or CMS virtual machine, whichever is more convenient. Use the CMS editor to create and store the stage I input. The job
stream can then be punched to the OSVSSYS machine's virtual reader for assembly under the OS/VS starter system. The CMS editor also allows the
user to edit the job stream, make changes to it, and file the modified
copy under a different name. Section 4e as/vs in a Virtual Machine 121

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