This chapter describes how to start the VM Client software.
The VM Client executes in its own CMS virtual machine, called the VM Client service machine. Chapter 3, "Installing VM Client" describes the setup of the VM Client service machine, and the installation of the VM Client service machine software.
Once the VM Client service machine is installed, the VM Client is started by issuing the distributed SMCSTART command. The SMCSTART command is an EXEC that initializes the VM Client virtual machine environment, and then executes the SMCBINT module.
The SMCBINT module reads the VM Client command files, and initializes the VM Client environment to receive TMI commands from other virtual machines. See "VM Client Command Files" for more information about the VM Client command files.
In addition to the VM Client command files, the SMCBINT module accepts optional command line parameters. The SMCBINT optional command line parameters allow VM Client OPERATOR and VM Client TRACE to be set before the VM Client command files are read, or to enable VM Client MAXRC processing at startup.
SMCBINT optional command line parameters are entered as keyword value pairs following the module name. For example, the following is an example of specifying SMCBINT parameters:
SMCBINT TRACE ON OPERATOR VMOPER MAXRC 4
Any errors encountered during command line parameter processing will result in termination of the VM Client initialization process.
The sections that follow describe each of the allowed keyword value pairs in detail.
TRACE{ON|OFF}specifies whether VM Client trace processing is to be activated before VM Client command file processing. ON specifies that VM Client TRACE is to be enabled as early as possible.
OPERATOR useridspecifies whether a VM Client operator is to be set before VM Client command file processing. userid specifies the name of the virtual machine to receive VM Client messages
MAXRC nnspecifies whether VM Client MAXRC processing is to be activated.
MAXRC processing determines whether the VM Client system is to be terminated on startup when the specified command return code is exceeded. If MAXRC is not specified, VM Client will always attempt to complete its initialization regardless of any startup command failure(s). This is the default behavior. The value nn specifies the highest allowed return code. If a VM Client command executed from the SMCPARMS or SMCCMDS data set exceeds this value, then the SMC0236 and SMC0237 messages will be produced, and the VM Client will be terminated. Allowable values are 0, 4, 8, and 12.
VM Client commands can be specified in the SMCPARMS and SMCCMDS command files. During VM Client initialization, these command files are read and the commands included in these files are executed. By convention, the command files are named as follows:
SMCPARMS FILE A1
SMCCMDS FILE A1
The FILEDEFs for SMCPARMS and SMCCMDS in the SMCSTART EXEC can be modified if different file names are to be used.
The control statements in the VM Client command files must conform to the standard conventions for control statements as described in "Control Statement Conventions".
The SMCPARMS command file is read first. It is used for user-configured items that cannot be changed while the VM Client is active. SMCPARMS cannot be reprocessed using the READ command.
The following is a sample SMCPARMS member entry:
OPERATOR ID(nnnn) LOGDISK ON MSGDEF CASE(MIXED) TCPIP TCPNAME(tcpname)
The SMCCMDS command file is used for user-configured items that can be changed while the VM Client is active. SMCCMDS can be reprocessed using the VM Client READ command. See "READ" for more information about this command.
The following is a sample SMCCMDS member entry:
TAPEPLEX NAME(tttttttt) SERVER NAME(ssssssss) TAPEPLEX(tttttttt) PORT(pppp) + IPADDRESS(nn.nn.nn.nn)
The VM Client provides the following customer exits which may be implemented as CMS EXECs.
SMCXIT00 Midnight Exit
If this exit is implemented, it executes each night at midnight.
See the installation sample SMCXIT00.samp for input parameters (if any), capabilities, and installation instructions.
SMCXIT01 Command Authorization Exit
If this exit is implemented, it executes when a VM Client command or TMI request is received and the VM Client command or TMI request is not authorized by an appropriate VM Client AUTHorize command.
See "AUTHorize" for information about the VM Client AUTHorize command. See the installation sample SMCXIT01.samp for input parameters (if any), capabilities, and installation instructions.
Note:
VMSES/E installation does not install these exits. Refer to the individual customer exit samples for installation instructions.The SMCPROP EXEC is provided for use as a PRogrammable OPerator (PROP) action routine to process all of the following type of messages, which CP sends to the system console:
TAPE raddr DETACHED....
VM (CP) causes a "Rewind Unload" command to be executed on any tape drive DETACHed by the CP commands LOGOFF, FORCE, or DETACH. This would leave any StorageTek DETACHed TapePlex volume in a "selected" state while still residing in an automated TapePlex transport. The volume would be unavailable to any requestor until removed (or DISMOUNTed) from the drive.
SMCPROP EXEC is an "action routine" which may be invoked from the VM PROP service to automatically issue VM Client DISMOUNT commands when a TapePlex transport is DETACHed from a virtual machine, enabling the volume to be available (that is, unselected) earlier than would otherwise be possible. RTABLE SAMPLE is provided to use the SMCPROP action routine with PROP. Refer to the IBM publication CMS Planning and Administration for information about the PROP service.
SMCPROP EXEC can also be used with VMOPERATOR to trap DETACH messages. LOGTABLE SAMPLE contains sample VMOPERATOR LOGTABLE statements to assist you. Consult VMOPERATOR documentation for information about tailoring the samples to your needs. The SMCPROP EXEC must be updated if the VM Client service machine user ID is not VMSMC.
SMCPROP EXEC must be available to the PROP/VMOPERATOR machine to operate properly.