Chapter 12 CLOCK Messages

The messages in this chapter are sent by the time management component of the operating system. The subsystem ID displayed for these messages includes CLOCK as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

100

System time reset due to DST transition

Cause The system time was automatically reset because of a daylight-saving time change.

Effect The timestamp on the message indicates the new system time.

Recovery Informational message only; no corrective action is needed.

101

System time reset from SP clock

Cause The operating system has set the system time from the service processor (SP) clock (on G-series RVUs) or the Remote Maintenance Interface (RMI) clock (on D‑series systems) after a system cold load or power outage.

Effect None.

Recovery Informational message only; no corrective action is needed.

102

System time reset

Cause The command SETTIME or a call to procedure SETSYSTEMCLOCK has reset system time.

Effect None.

Recovery Informational message only; no corrective action is needed.

103

System time reset during measurement

Cause The system time was reset while a Measure measurement was active.

Effect Certain counters might be invalid.

Recovery Informational message only; no corrective action is needed.

104

Error reading Service Processor clock SP error code: status

status

indicates why the error occurred. The status values are as shown in Table 12-1:

Table 12-1 status Values for CLOCK Message 104 (G-Series RVUs)

status Value	Description
0-1091	File-system error. If the value is 12, another process had exclusive use of the SP at the time the operating system tried to set the SP clock. For a list of file-system errors, refer to Appendix B.
negative value	SPIOLIB error.

Cause The operating system encountered an error when reading the service processor (SP) clock. Check the status code for the reason why the error occurred. The SP clock might have failed. This message applies to G-series RVUs.

Effect On the next system load, the time might not be correct.

Recovery Enter a SETTIME command that correctly specifies the date and time. To repair the failing SP, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

104 (D-Series RVUs)

Error reading Remote Maintenance Interface clock RMI error code: status

status

indicates why the error occurred. The status values are as shown in Table 12-2:

Table 12-2 status Values for CLOCK Message 104 (D-Series RVUs)

status Value	Description
0-1091	File-system error. If the value is 12, another process, such as TMDS, had exclusive use of the RMI at the time the operating system tried to set the RMI clock. For a list of file-system errors, refer to Appendix B.
-3	The maximum number of retries allowed to read the RMI clock was exceeded.
-4	The RMI clock was not set.
-5	The maximum amount of time allowed to set the RMI clock was exceeded.
-6	An invalid Julian timestamp was passed to the RMI clock.
-7	An invalid year was passed to the RMI clock.
-8	The maximum number of retries while trying to set the RMI clock was exceeded.
-9	The RMI clock was not set correctly.
other	A bad value was returned from the RMI clock.

Cause The operating system encountered an error when reading the Remote Maintenance Interface (RMI) clock while trying to reset the system time. Check the status code for the reason why the error occurred.

Effect The system time is not automatically initialized. The RMI clock might have failed.

Recovery Enter a SETTIME command that correctly specifies the date and time. To repair the failing RMI, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

105

Error Setting Service Processor Clock, SP error code: status

status

For G-series RVUs, indicates why the SP clock could not be set. The status values are as shown in Table 12-3:

Table 12-3 status Values for CLOCK Message 105 (G-Series RVUs)

status Value	Description
0-1091	File-system error. If the value is 12, another process had exclusive use of the SP at the time the operating system tried to set the SP clock. For a list of file-system errors, refer to Appendix B.
negative value	SPIOLIB error.

Cause The operating system could not set the service processor (SP) clock. Check the status code for the reason why the SP clock could not be set.

Effect The SP time might not be synchronized with the system time. If the system power fails or a system load is performed, the system time is reset to agree with the SP time. However, both times might be incorrect.

Recovery If there is a hardware problem, ask the Global NonStop Solution Center (GNSC) to check the clock batteries and the SP hardware.

If error 12 was returned and you had tried to execute SETTIME before the error occurred, retry the SETTIME command. If you didn’t try to execute SETTIME, no corrective action is needed.

If there is a software problem, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

105 (D-Series RVUs)

Error Setting Remote Maintenance Interface Clock, RMI error code: status

status

indicates why the RMI clock could not be set. The status values are as shown in Table 12-4:

Table 12-4 status Values for CLOCK Message 105 (D-Series RVUs)

status Value	Description
0-1091	File-system error. If the value is 12, another process, such as TMDS, had exclusive use of the RMI at the time the operating system tried to set the RMI clock. For a list of file-system errors, refer to Appendix B.
-3	The maximum number of retries allowed to read the RMI clock was exceeded.
-4	The RMI clock was not set.
-5	The maximum amount of time allowed to set the RMI clock was exceeded.
-6	An invalid Julian timestamp was passed to the RMI clock.
-7	An invalid year was passed to the RMI clock.
-8	The maximum number of retries while trying to set the RMI clock was exceeded.
-9	The RMI clock was not set correctly.
other	A bad value was returned from the RMI clock.

Cause The operating system could not set the Remote Maintenance Interface (RMI) clock. Check the status code for the reason why the RMI clock could not be set.

Effect The RMI time might not be synchronized with the system time. If the system power fails or a system load is performed, the system time is reset to agree with the RMI time. However, both times might be incorrect.

Recovery If there is a hardware problem, ask the Global NonStop Solution Center (GNSC) to check the clock batteries and the RMI hardware.

If error 12 was returned and you had tried to execute SETTIME before the error occurred, retry the SETTIME command. If you didn’t try to execute SETTIME, no corrective action is needed.

If there is a software problem, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

106

System cold load complete

Cause The system time was initialized during system load. A system load is considered complete after system time initialization is attempted.

Effect None.

Recovery Informational message only; no corrective action is needed.

107

System time adjusted

Cause After a call to SETSYSTEMCLOCK, the operating system initiated a system time adjustment.

Effect The time is adjusted.

Recovery Informational message only; no corrective action is needed.

108

CPU clock is not synchronized with system time

Cause A hardware problem probably occurred.

Effect Processes running in the processor obtain timestamps that differ from the system time by at least 100 milliseconds.

Recovery Contact your the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

109

CPU clock resynchronized with system time during powerfail recovery

Cause After a power failure, the clocks were resynchronized.

Effect None.

Recovery Informational message only; no corrective action is needed.

110

CPU clock has been resynchronized with system time

Cause The operating system has resynchronized the clock with system time. The clock and system times are synchronized to within 100 milliseconds.

Effect Processes running in the processor obtain timestamps that are within 100 milliseconds of the system time.

Recovery Informational message only; no corrective action is needed.

111

SP clock is not synchronized with system time

Cause On G-series RVUs, the service processor (SP) clock differs from the system time by more than five seconds.

Effect The operating system tries to recover. If recovery is successful, the operating system sets the SP clock to system time.

If recovery is not successful, the operating system generates clock operator message 105. (The operating system could not set the SP clock.)

Recovery This message might indicate an SP clock hardware problem.

Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

111 (D-Series RVUs)

RMI clock is not synchronized with system time

Cause The Remote Maintenance Interface (RMI) clock differs from the system time by more than five seconds.

Effect The operating system tries to recover. If recovery is successful, the operating system sets the RMI clock to system time.

If recovery is not successful, the operating system generates clock operator message 105. (The operating system could not set the RMI clock.)

Recovery This message might indicate an RMI clock hardware problem.

Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

112

SP clock invalid when trying to reset system clock after power failure

Cause On G-series RVUs, when trying to set the system clock after a power failure, the Service Processor (SP) detected a large time discrepancy between the values from the SP clock and the system clock.

Effect The system clock time continues from the time of the power failure, missing the time that power was off.

Recovery Enter a SETTIME command to set the correct system time or, if the SP clock has failed, contact the Global NonStop Solution Center (GNSC) to file and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

112 (D-Series RVUs)

RMI clock invalid when trying to reset system clock after power failure

Cause When trying to set the system clock after a power failure, the Remote Maintenance Interface (RMI) detected a large time discrepancy between the values from the RMI clock and the system clock.

Effect The system clock time continues from the time of the power failure, missing the time that power was off.

Recovery Enter a SETTIME command to set the correct system time or, if the RMI clock has failed, contact your the Global NonStop Solution Center (GNSC) to file and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.