SET VTOD
Authorization
Privilege Class: A, B, G
Purpose
- enables a user to set their virtual TOD clock to a different date and time,
- enables a user to synchronize the virtual TOD clock of a message processor user to the issuing user's virtual TOD clock,
- enables a user to synchronize their virtual TOD clock with the virtual TOD clock of another user ID,
- resets the user's virtual TOD clock to the system TOD clock.
Operands
- SYSTEM
- the user's virtual machine TOD clock will be set to the current system value. This is the default value that is set at LOGON.
- DATE mm/dd/yyyy
- DATE yyyy-mm-dd
- specifies the new date to be used for this virtual machine's TOD clock. If the TIME operand is not specified, the date is changed and the time remains unchanged. The date entered must be in a range from 01/01/1942 to 12/31/2041.
- TIME hh:mm:ss
- specifies the new time to be used for this virtual machine's TOD clock. If the DATE operand is not specified, the time is changed and the date remains unchanged.
- 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 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 statement.
Regardless of privilege class, the specified message processor user must have the TODENABLE operand of the OPTION directory 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.
Usage Notes
- 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.
- The virtual TOD clock will be changed for all virtual CPUs of the affected configuration.
- 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.
Responses
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.
Response 2:
To set the TOD clock of the message processor CFCC2 to your virtual machine's TOD clock, enter the following:
set vtod msgp cfcc2
HCPMFM2809I Restart of message processor CFCC2 by SHARE1 initiated.
Message processor CFCC2 will automatically be restarted. HCP2809I will be displayed to both the message processor and the user who issued the SET VTOD MSGP CFCC2 command.
Messages
- HCP002E Invalid operand – operand
- HCP003E Invalid option – command contains extra option(s) starting with option
- HCP020E Userid missing or invalid
- HCP045E userid not logged on
- HCP1014E A required option is missing.
- HCP2805E Message processor msgprocid does not exist in your I/O configuration.
- HCP2809I Restart of message processor msgprocid by userid initiated.
- HCP2812E User userid does not have operand authorization on statement directory statement
- HCP6704E Missing token at end of line
- HCP6706E Invalid string – string
- HCP6706E Invalid time – time
- HCP6706E Invalid date – date
