Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837 3850 MSS DEFINING THE MSS COMMUNICATION DEVICE The VM/370 control program initiates an MSS mount or demount request by generating an attention interruption on a specified device. This device
must be specified in the directory of the virtual machine as a unit
record output device, for example: SPOOL 017 2540 PUNCH The same device address must be specified on the job control language
used to start DMKMSS in VS, for example: //MSSCOMM DD UNIT=017 This device address must be constructed in VS at the same time as the IOGEN for the 3330Vs. The address chosen must not correspond to an
actual device that VS will attempt to use for any other purpose: This
is done by specifying the device as a DUMMY in the VS IOGEN. For
example: IODEVICE ADDRESS=017,UNIT=DUMMY,DEVTYPE=nnnnnnnn The value of nnnnnnnn
requirement to provide
example:
is any valid hexadecimal code.
a UNITNAME statement for this UNITNAME NAME=017,UNIT=017 T.HE MASS STORAGE CONTROL TABLES It is a
device, VS for
This topic is provided for those installations that intend to run VS systems in a virtual machine and access the MSS (under control of VS) from those systems. If you run only one VS virtual machine that has MSS support, and that virtual machine will access the MSS only upon request
from VM/370, then this section does not apply. However, you must follow
the guidelines in this topic if you have a virtual machine that has 3330Vs dedicated to it (that is, you intend to run more than one MSS virtual machine or to run VS MSS jobs in the MSS communication virtual
machine).
The MSC is driven from tables that reside on DASD. These tables are
used, among other things, to define the MSS configuration. This
configuration includes such items as the addresses to be used for all
components of the system, and the available paths from all connected
hosts to all these component devices. Thus, the MSC tables define the
allowable paths from any host (as defined by that host's CPUID to a 3330V where the 3330V is defined in terms of the Staging Adapter address
and the specific S/370 channel attachment to the Staging Adapter). Part 1. Planning for System Generation 74.1
n 1:"............ .,
74.2 IBM VM/370 Planning and System Generation Guide
Previous Page Next Page