page of GC20-1806-9 Is Updated April 1, 1981 by TNL GN25-0834 Mass Storage System Initialization If an !ISS port is attached to a virtual machine running as/vs with !ISS support and the !ISS communicator program is running in the virtual
.achine, the control program can cause automatic 3330V volume mount and demount in response to any of the following: • 1 virtual machine logs on with a minidisk defined on a system disk
that is not mounted. The control program attempts to mount an SSS volume with the correct volume label. • 1 virtual machine logs
specifying a vo1id for a program again atteapts to
volulle label.
on having a dedicate directory statement
volume that is not mounted. The control mount an KSS volume with the specified • In operator ATTACH com.and is issued specifying a device address that
is an SSS 3330V address and volid. The control program attempts to mount the vo1id on the device address as part of the ATTACH
process ing • • The operator DEFINE command is used to change the feature (SYSVIRT or VIRTUAL) of a 3330V containing a mounted volume. The control program
demounts the volume before completing the DEFINE process. • 1 virtual machine issues a LINK command to link to a virtual device
that is all or part of a 3330V volume. The control program attempts
to mount the volume as part of the LINK process.
The VK/370 control program does not issue orders directly to the mass
storage control (IISC). Bather, it passes requests to an as/vs system
with !ISS support that is operating in a virtual machine with an SSC port
dedicated to it. The CS/iS system then issues orders to the KSC and
passes response information back to the control program.
In order for the installation to run with full KSS support, an as/vs
system must be IPLed in a virtual machine. An KSC port must be
dedicated to this virtual machine. There are no special requirements
for this IPL. The standard installation procedures for IPLing as/vs in
a virtual machine should be followed. Ifter the system is IPLed, the VII/370 communicator program must be started. If the standard
installation procedures as documented in the VK/370 System Generation-Guide have been followed, the communicator program is started
in the virtual machine through the OS/VS operator command:
start dmkmss {.pn]
The (.pn] operand is used only in OS/VS1 systems to specify the
partition in Which the program is to be started.
The absence of error messages received from DKKSSS indicates that KSS support is initialized. The communicator virtual machine may now be
disconnected if the installation desires.
There are five error messages that the D!lKKSS program can produce.
If any of these messages are received, then the VK/370 control program will not be able to communicate with the KSS. The messages are as
follows:
Section 2. Initiating V8/370 aperation 17

Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 DKKKSS ENDING ERROR - MSS NOT INITIALIZED ExplanatiQn: The KSS did not get initialized as it should during
the OS/VS IPL process. Either the virtual machine does not have
access to the MSC, or there was an MSS error. OperatQ£ response: Correct the problem, use the OS/VS VARY command
to initialize the KSS, then reissue the "start dmkmss" command. DKKMSS ENDING ERROR - DCB FOR COMM. DEVICE NOT OPENED ExplanatiQn: The DMKMSS program was not able to establish
communication with the VK/370 control program because the OS/VS DCB
control block could not be opened. The probable cause is the
definition of the communicator device for the virtual machine. contact the system programmer. After the
problem has been corrected, reissue the "start dmkmss" command. DMK!SS ERROR READING !SS CONFIGURATION TABLE DMK!SS attempted to read one of the !SS configuration
tables (Configuration Index/Manufacturer's ID Conversion table or
the Configuration Data Block) and an error was encountered. Contact the MSS system programmer. After the
problem has been corrected, reissue the START D!KKSS command. DMKKSS CPUID NOT FOUND IN MSS CONFIGURATION TABLES DMKKSS has read one of the MSS configuration tables
(the Configuration Index/Manufacturer's ID Conversion table) and
searched it for a match to this cpuid, but no match was found. Contact the !SS system programmer. The !SS configuration tables may need to be updated. After the problem has
been corrected, reissue the START DMKKSS command. D!KKSS ERROR CREATING !5S CONFIGURATION TABLE Expla.nation: DKK!SS has given CP a list of VUAs associated with the
central server cpuid. CP has attempted to create its shared and
nonshared SDG tables, but has encountered an error. OperaiQ£ Contact the system programmer. After the
problem has been corrected, reissue the START D!KMSS command.
Attached Processor Initialization In order for the installation to run with an attached processor, it must
do the following: • Specify AP=YES in the SYSCOR macro during VK/370 system generation • Have the attached processor online during system IPL 18 VM/370 Operator's Guide