z/VM: CP Commands and Utilities Reference - z/VM - IBM

Usage Notes
Responses
The user must be authorized to use this operand via the TODENABLE operand
of the OPTION Directory Control Statement. Without authorization, the virtual
machine’s TOD clock will not be changed and an error message is presented.
FROMUSER userid
the user’s virtual machine TOD clock will be set exactly to the specified user
ID’s TOD clock.
The user must be authorized to use this operand via the TODENABLE operand
of the OPTION Directory Control Statement. Without authorization, the virtual
machine’s TOD clock will not be changed and an error message is presented.
MSGPROC msgprocid
the virtual TOD clock of the specified message processor user will be set
exactly to the issuer’s virtual TOD clock.
If you have Class G privilege only, the message processor that you specify
must be currently in your I/O configuration. A message processor may be
defined in your I/O configuration by either the DEFINE MSGPROC command or
the SPECIAL directory statement.
If you have Class A or Class B privilege, the specified message processor user
must have the CFVM operand of the OPTION Directory Control Statement.
Regardless of privilege class, the specified message processor user must have
the TODENABLE operand of the OPTION Directory Control Statement.
CAUTION: Setting the TOD clock of the message processor will cause a
RESTART MSGPROC command to be executed on the specified message
processor. The RESTART MSGPROC command will cause the message
processor to be re-IPLed, thus causing all structures within the Coupling Facility
to be lost and will affect all coupled guests connected to the message
processor. See the RESTART MSGPROC command for more information.
1. A system reset will occur for the virtual machine whose virtual TOD clock value
has changed. If the virtual TOD clock of a message processor is changed, the
message processor’s virtual machine is restarted.
2. The virtual machine whose TOD clock you want to change may not be in
ESA/XC mode.
3. The virtual TOD clock will be changed for all of the virtual CPUs in the affected
user’s base configuration.
4. This command does not affect the time and date information that is returned
from DIAG X'000C', DIAG X'270', REXX DATE(), REXX TIME(), or PIPE
TIMESTAMP functions. The EXEC2 &TIME and &DATE functions are affected.
This command is NOT intended to allow an ordinary CMS user to run their
virtual machine with a date and time that is different than the system date and
time. This command is to allow guest operating systems running on VM to
synchronize their virtual TOD clocks in order to participate in a parallel sysplex
environment.
Response 1:
To modify the date of your virtual machine’s TOD clock, enter the following:
set vtod date 12/31/1999
Storage cleared - system reset.
SET VTOD
Chapter 2. CP Commands 1427