gtpm5m0pMessages (Online)

CLKS

CLKS0001ISYSTEM CLOCK IS NOW SET

Explanation: The TPF system clock was initialized based on an operational time-of-day (TOD) clock.

System Action: The restart procedure continues with an operational TOD clock.

User Response: None.

See TPF Operations for more information about the ZATIM command.

CLKS0003WCTKI RETRIEVAL ERROR

Explanation: Keypoint I (CTKI) could not be retrieved from disk during time-of-day (TOD) clock synchronization. Consequently, the number of leap seconds could not be moved into low core for this CPC.

If there is a nonzero value for the number of leap seconds in CTKI, Greenwich Mean Time (GMT) and local standard time calculations are off by the number of leap seconds because CTKI was not retrieved. (A nonzero value for the number of leap seconds in CTKI indicates that the TOD clock is using absolute time.)

System Action: The TOD clock synchronization process is continued.

User Response: Do the following:

  1. Determine why CTKI could not be retrieved from disk.
  2. Correct the retrieval problem.
  3. Resynchronize the CPC by entering the ZACOR command to correct the value of the number of leap seconds in low core.

    If a Sysplex Timer (STR) is available, determine the correct number of leap seconds from the STR device panel that displays offsets.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

CLKS0005WWAITING FOR CPC CLOCK CONFIRMATION

Explanation: The CPC is waiting for confirmation of its time with an external source. This message indicates that the time is required to complete validation of the current clock setting.

System Action: None.

User Response: If this is a loosely coupled TPF system and other confirmed CPCs are available, the time will be confirmed with the other confirmed CPCs. If not, you must confirm the time by entering a ZATIM command.

To reset the clock:

  1. Enter the ZDTIM SYS command to get the current time in the hh.mm format for use in step 2.
  2. Do one of the following:

If the TOD Clock Override facility is not present, the ATIM51A PRESS 'TOD ENABLE SET' KEY TO SYNC CPC TOD CLOCKS message is issued.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.
See TPF Operations for more information about the ZATIM command.

CLKS0010ITIME OF DAY CLOCK LOCAL STANDARD TIME TIME: hh.mm.ss DATE: mm/dd/yy

Where:

hh.mm.ss
The hour, minute, and second.

mm/dd/yy
The month, day, and year.

Explanation: The current value of the time-of-day (TOD) clock. This message is displayed when the TOD clock is being validated during restart and after it is confirmed with an external time source.

Part of the time value (hhmm) may be used as the baseline value for resetting the time (by entering the ZATIM command).

System Action: None.

User Response: This is purely an information message. No response is required. If the time or date is incorrect, it may be modified by entering the ZATIM command.

See TPF Operations for more information about the ZATIM and ZDTIM commands.

CLKS0011ATHE BSS WILL CHANGE DATE WHEN CYCLED UP TO CONTINUE OR TO CANCEL THE CYCLE UP -- ENTER A ZATME or ZCYCL COMMAND

Explanation: Entering the ZCYCL command to cycle the basic subsystem (BSS) above 1052 state involves testing the midnight boundary.

System Action: This message is sent to the operator if the BSS will cross a midnight boundary since the last time it was above 1052 state.

User Response: Do one of the following:

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0012ASUBSYSTEM ssname WILL CHANGE DATE WHEN CYCLED UP TO CONTINUE OR TO CANCEL THE CYCLE UP - ENTER A ZATME COMMAND

Where:

ssname
The subsystem name.

Explanation: Entering the ZCYCL command to cycle a subsystem above 1052 state results in testing the midnight boundary.

System Action: This message is sent to the operator if the subsystem crosses the midnight boundary since the last time it was above 1052 state.

User Response: Do one of the following:

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0012ITOD CLOCK stat

Where:

stat
One of the following:

Explanation: While trying to convert the time-of-day value for the CLKS0010I message, a store clock instruction has indicated that the TOD clock is in one of the previously listed states.

In the case of the IN ERROR display, this indicates a malfunctioning clock hardware error.

In the case of the NOT SET display the clock was simply not previously set. This is the case after a power on/reset, for example.

System Action: None.

User Response: If the TOD clock is able to be set after this message is displayed, then any error condition was transient.

If not, the TOD clock has a hardware error and have system programmer check the problem.

See TPF Operations for more information about the ZDTIM command.

CLKS0013ITHE BSS WILL CONTINUE TO CYCLE UP

Explanation: This is the normal response to the ZATME GOOD command when it is entered in response to the CLKS0011A message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0014ISUBSYSTEM ssname WILL CONTINUE TO CYCLE UP

Where:

ssname
The subsystem name.

Explanation: This is the normal response to the ZATME GOOD command when it is entered in response to the CLKS0012A message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0015ITHE BSS CYCLE UP REQUEST CANCELLED

Explanation: This is the normal response to the ZATME CNC command when it is entered in response to the CLKS0011A message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0016ISUBSYSTEM ssname CYCLE UP REQUEST CANCELLED

Where:

ssname
The subsystem name.

Explanation: This is the normal response to the ZATME CNCL command when it is entered in response to the CLKS0012A message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0018ISTR TIME OF DAY LOCAL STANDARD TIME TIME: hh.mm.ss DATE: mm/dd/yy

Where:

hh.mm.ss
The hour, minute, and second.

mm/dd/yy
The month, day, and year.

Explanation: This is the current time-of-day (TOD) value from the Sysplex Timer (STR).

If the time or date is incorrect, it can be modified on the STR.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDTIM command.

CLKS0021WCONFLICTING ZATIM REQUESTS FOR SUBSYSTEM xxx VALIDATE THE SUBSYSTEM TIME ON ALL PROCESSORS. IF ANY IS INCORRECT -- ENTER A SINGLE ZATIM COMMAND

Where:

xxx
The subsystem name.

Explanation: One of the following errors occurred:

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME, ZCYCL, and ZATIM commands. See TPF Main Supervisor Reference for more information about clocks.

CLKS0023ISUBSTITUTE SSR USED xx

Where:

xx
The synchronous selection register (SSR).

Explanation: When a CPC is not found in keypoint I during restart, a substitute synchronous selection register (SSR) is created using the processor number. This allows more flexibility in the restart process.

Note:
The substitute SSR must not be used to establish synchronization with the time-of-day (TOD) RPQ. Doing so will result in irrecoverable synchronization errors.

System Action: None.

User Response: This is an informational message so no response is required.

See TPF Operations for more information about the ZATIM command.

CLKS0026IZATIM, ENTERED ON CPU ID cpu id, HAS RESET TOD CLOCK --STARTING TOD RESYNCH

Where:

cpu id
The central processing unit (CPU) ID.

Explanation: In a loosely coupled complex, allowing the CPC to alter the time-of-day (TOD) clocks is called the Master CPC. The Master CPC is originally the first processor IPLed in the loosely coupled complex.

The designation Master may be shifted to another CPC by altering the time on that CPC with the bypass option. Any CPCs in 1052 state at that time will have their TOD clocks reset to the new time automatically. Any CPCs not in 1052 state will be informed that to become synchronous with the loosely coupled complex a ZRIPL command must be entered or the non-synchronous CPC must be cycled to 1052 and the time reset. Refer to the CLKS56E message.

System Action: None.

User Response: Do one of the following:

See TPF Operations about the ZATIM command.

CLKS0027ITOD CLOCK TIME RESET

Explanation: When the time-of-day (TOD) clock was reset on another CPC, this CPC was found to be in 1052 state. Consequently, the TOD clocks on this CPC could be reset automatically.

This message is displayed when the reset process is complete.

System Action: The TOD clocks will be synchronous with the Master of the loosely coupled complex.

User Response: This is an information message. When this message is displayed, CPC TOD resynchronization is complete.

See TPF Operations for more information about the ZATIM command.

CLKS0043WINVALID IPC MESSAGE TYPE RECEIVED

Explanation: During the resynchronization of a loosely coupled CPC another loosely coupledCPC responded with a Interprocessor Communications (IPC) facility message that is not valid.

System Action: The message is rejected and another CPC is addressed with a status request.

User Response: None.

See TPF Operations for more information about the ZATIM command.

CLKS0044WSTATUS REQUEST RECEIVED FROM INACTIVE CPUID id

Where:

id
The central processing unit (CPU) ID.

Explanation: A request for time-of-day (TOD) clock status was received from a loosely coupled processor marked as inactive in Keypoint I.

System Action: None.

User Response: Determine whether the CPU specified is actually inactive.

If the CPU is not inactive, Keypoint I has an error that must be corrected.

See TPF Operations for more information about the ZATIM command.

CLKS0045WINVALID IPC MESSAGE NUMBER RECEIVED

Explanation: During the resynchronization of a loosely coupled CPC another loosely coupledCPC responded with a zero Interprocessor Communications (IPC) facility message.

System Action: The message is rejected and another CPC is addressed with a status request.

User Response: None.

See TPF Operations for more information about the ZATIM command.

CLKS0046ICPC CLOCK(S) LOCALLY SYNCHRONOUS

Explanation: This message occurs when:

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: If the processor is to be confirmed with a remote time source, you can re-IPL or enter the ZATIM command. Otherwise, no other action is required.

See TPF Operations for more information about the ZATIM command. See TPF Main Supervisor Reference for more information about time keeping considerations for loosely coupled processing.

CLKS0051APRESS 'TOD ENABLE SET' KEY TO SYNC CPC TOD CLOCKS

Explanation: If the time-of-day (TOD) Clock Override facility is not present, the TOD clock must be enabled to set the TOD clock. The architecture of the enable switch varies according to the type of processor. Once pressed, the TOD clock remains enabled for setting for approximately ten seconds. When the set key is not enabled, the TOD clock is known as secure. The TOD clock cannot be set when it is secure.

System Action: None.

User Response: Press the TOD clock enable switch.

See TPF Operations for more information about the ZATIM command.

CLKS0054WNOT ALL PROCESSORS IN 1052 STATE

Explanation: The time-of-day (TOD) clock on this CPC is useable and confirmed. There are no other confirmed TOD clocks in the complex on which to synchronize but there are other processors above 1052 state. External confirmation from the operator is required.

System Action: The CLKS0055A message follows.

User Response: Determine why there are other CPCs in the complex that have unconfirmed TOD clocks, yet are above 1052 state.

See TPF Operations for more information about the ZATIM command.

CLKS0055AALL OTHER ACTIVE PROCESSORS HAVE UNSYNCED TODS CURRENT TOD MSTR IS stat ACTIVE CPUID id CPU serial-no SET THE TOD CLOCK USING THE FORMAT: 'ZATIM HHMM TOD ...'

Where:

stat
Blank or NOT depending on the status.

id
The CPU ID.

serial-no
The serial number of the lowest available I-stream on the current Master.

Explanation: This processor complex could not find another processor complex with which to confirm its time. Consequently, external confirmation from the complex operator is required.

The master processor is not confirmed synchronous. If a Sysplex Timer (STR) is available for a synchronization source, then the CLKS87I and CLKS18I messages follow.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: Enter the ZATIM command to confirm the current clock setting.

See TPF Operations for more information about the ZATIM command.

CLKS0055EUNABLE TO SYNC THIS TOD ALL OTHER ACTIVE PROC'S HAVE UNSYNCED TODS CURRENT TOD MSTR IS stat ACTIVE CPUID id CPU serial-no 'ZATIM SET TOD' REQ'D ENTER FORMAT: 'ZATIM HHMM TOD HHMMSS MMDDYY'

Where:

stat
Blank or NOT.

id
The active central processing unit (CPU) ID.

serial-no
The serial number for the CPU.

Explanation: This processor complex could not find another processor complex with which to confirm its time. Consequently, external confirmation from the complex operator is required.

The master processor is not confirmed synchronous.

System Action: None.

User Response: Enter the ZATIM command to confirm the current clock setting.

See TPF Operations for more information about the ZATIM command.

CLKS0056EZATIM, ENTERED ON CPUID id, HAS RESET TOD CLOCK TO RESYNC THE TOD ON THIS CPU, EITHER REIPL OR CYCLE TO 1052 AND SET TOD CLOCK ON MASTER

Where:

id
The CPU ID.

Explanation: This message applies to loosely coupled TPF systems only. An interprocessor communications (IPC) message was received that indicates another processor has performed a set time request. The time-of-day (TOD) clock for this processor, therefore, is no longer correct.

Automatic resynchronization is prevented because this processor is not in 1052 state.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZATIM command.

CLKS0057ECTKI RETRIEVAL ERROR BY TOD SYNC DURING CYCLE, CYCLE ABORTED

Explanation: Keypoint I (CTKI) could not be retrieved from disk during a TPF system cycle up. Consequently, the set request sequence numbers could not be validated and time-of-day (TOD) synchronization may be in doubt.

System Action: None.

User Response: Do the following:

  1. Determine why keypoint I could not be retrieved from disk and correct the problem.
  2. Try to cycle the TPF system again.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0058ETOD SYNC CHECK HAS OCCURRED ISTREAMS (PHYSICAL ID) is-list MASTER CPU SERIAL NUMBER IS serial-no MASTER CPU IS stat1 ACTIVE MASTER CPU-ID IS id MASTER STR ID: str id NETWORK ID: network id

Where:

is-list
The 16-byte list of I-stream physical addresses, which are displayed as a hexadecimal number.

serial-no
The serial number of the lowest available I-stream on the current Master.

stat1
Blank or NOT depending on the status.

id
The master CPU ID.

str id
The Sysplex Timer (STR) ID.

network id
The network ID.

Explanation: A confirmed synchronization check has occurred. The instruction steams that took synchronization checks are listed along with the serial number and CPU ID of the master processor (whether the master processor is active) and the master STR information.

Notes:

  1. The serial number of the master processor is displayed but the CPU address portion of the serial number (the rightmost two bytes) corresponds to the lowest available instruction stream on the processor and not the IPLed or main instruction stream.

  2. On a TPF system without a time-of-day (TOD) RPQ or an STR, only the first two lines of this message are displayed and a CTL-67B follows if unable to obtain local synchronization.

  3. On a TPF system with a TOD RPQ or an STR, a CTL-67B follows if unable to obtain local synchronization.

  4. The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection(ESCON) Architecture.

System Action: None.

User Response: If the processor is loosely coupled, the processor complex may become internally synchronous. In this case, the processor continues running but will not be synchronous with the external time source.

A re-IPL is required to synchronize the complex in a loosely coupled TPF system.

See TPF Main Supervisor Reference for more information about time keeping considerations for loosely coupled processing.

CLKS0059ETOD SYNC CHECK HAS OCCURRED ISTREAMS (PHYSICAL ID) is-list TOD SYNC SEL. ADDR IS ssa MASTER CPU SERIAL NUMBER IS serial-no MASTER CPU IS stat1 ACTIVE MASTER CPU-ID IS id TOD SYNC INTERFACE IS stat2 OPERATIONAL

Where:

is-list
The 16-byte list of I-stream physical addresses, which are displayed as a hexadecimal number.

ssa
The synchronization selection address.

serial-no
The serial number of lowest available I-stream on the current master.

stat1, stat2
Blank or NOT depending on the status.

id
The master CPU ID.

Explanation: A confirmed synchronization check occurred. The instruction streams that took synchronous checks are listed, along with the synchronization selection address in use at the time, the serial number, and the CPU ID of the master processor, whether the master processor is active, and whether the time-of-day (TOD) RPQ is operational.

Notes:

  1. The serial number of the master processor is displayed but the CPU address portion of the serial number, the rightmost two bytes, corresponds to the lowest available instruction stream on the processor, not the IPLed or main instruction stream.

  2. On a TPF system without a TOD RPQ or an STR, only the first two lines of this message are displayed and a CTL-67B follows if unable to obtain local synchronization.

  3. On a TPF system with a TOD RPQ or an STR, a CTL-67B follows if unable to obtain local synchronization.

  4. The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection(ESCON) Architecture.

System Action: None.

User Response: If the processor is loosely coupled, the processor complex may become internally synchronous. In this case the processor continues running but will not be synchronous with the external time source.

A re-IPL is required to synchronize the complex in a loosely coupled TPF system.

See TPF Main Supervisor Reference for more information about time keeping considerations for loosely coupled processing.

CLKS0060ETOD SET SEQUENCE NUMBER IN CORE DOES NOT MATCH CTKI TOD VALUE MAY BE INCORRECT CYCLE ABORTED

Explanation: The number of SST time requests made to the TPF systemis kept in keypoint I. Each processor complex also keeps its own number of set time requests.

If the number of requests for the processor complex does not match the number in the TPF system, the processor complex has missed a TPF system set time request. This would cause the processor to be out of synchronization with the TPF system.

System Action: Cycling from 1052 state is ended when the ECB is exited.

User Response: Do the following:

  1. Enter a set time request.
  2. Try to recycle the TPF system. If cycling fails again, re-IPL the processor complex.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0061ETOD CLOCK NOT SYNCHRONIZED CYCLE ABORTED

Explanation: An error occurred that caused a time-of-day (TOD) clock not to be synchronized. A hard synchronization check in 1052 state, for example, would create this situation.

System Action: The ECB is exited.

User Response: The TOD clock must be set before cycling above 1052 state. Enter a set time request for the processor complex.

See TPF Operations for more information about the ZATME and ZCYCL commands.

CLKS0063ESYNCHRONIZATION ERROR WITH SYNC SEL ADDR ssa EXTERNAL SYNCH FAILED -- CPC SYNCHD LOCALLY

Where:

ssa
The synchronization selection address (SSA).

Explanation: An error occurred during restart because synchronization could not take place along the path specified. There may be an incorrect synchronization selection address (SSA) value or an incorrect representation of the selection addresses in the cabling of the time-of-day (TOD) RPQ.

The loosely coupled processor complex succeeded in becoming internally (locally) synchronous. Keypoint I contains the synchronization selection addresses (SSA) associated with the various processors.

System Action: TOD clock validation during restart is ended.

User Response: The synchronization selection address being used may be incorrect. The selection address may be determined by entering the ZDTIM TOD command.

If it is incorrect, modify keypoint I with the correct SSA and enter the set time request again. Ensure that the TOD RPQ or the TOD Synchronization Compatibility (TSC) hardware is cabled correctly to each of the processors according to the selection addresses in keypoint I. Also, re-IPL the TPF system.

Enter the ZATIM command again to set the time after a ZATIM TSC migration message is entered.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.
See TPF Operations for more information about the ZATIM command. See TPF Main Supervisor Reference for more information about time keeping considerations for loosely coupled processing.

CLKS0068ETOD CLOCK NOT OPERATIONAL -- ISTREAM lid ( pid )

Where:

lid
The logical identifier (ID), which is displayed as a decimal number.

pid
The physical identifier (ID), which is displayed as a hexadecimal number.

Explanation: During the time-of-day (TOD) clock hardware validation, a TOD clock in the processor complex was found to have a permanent hardware error that caused it not to be operational. All TOD clocks in a processor complex must be operational.

System Action: None.

User Response: Do the following:

  1. Remove the TOD clock from the process complex, if possible.
  2. Re-IPL the TPF system.
  3. See your IBM service representative to check the TOD clock error.

See TPF Operations for more information about the ZATIM command.

CLKS0069TRESTART SCHEDULER EXITED

Explanation: This message informs you that an error occurred during restart that forces its termination. The message is preceded by a dump that provides information as to the actual problem found.

System Action: None.

User Response: Do the following:

  1. Review the system error dump to determine the cause of the error.
  2. Correct the error.
  3. Re-IPL the TPF system.

See TPF Operations for more information about the ZATIM command.

CLKS0072WINITIAL SET VALIDATION FAILED

Explanation: This message informs you that the validation of the processor complex time-of-day (TOD) clocks failed. The tightly coupled clocks running in a processor complex must be high-order and low-border synchronous, as well as being free from hardware errors, to be valid. Validation is trying again in case the cause of the problem was transient.

System Action: None.

User Response: This warning message may indicate underlying timing problems between instruction streams.

If the problem continues, have your system programmer determine the cause of the inter-I-stream response time and correct it.

See TPF Operations for more information about the ZATIM command.

CLKS0073TUNABLE TO LOCALLY SYNCHRONIZE THIS CPC

Explanation: The computer processor complex was not able to be made internally synchronous. The attempt to set the time-of-day (TOD) clocks on the CPC is ended. The processor remains in 1052 state.

System Action: An irrecoverable system error is issued.

User Response: Re-IPL the processor. If it fails again, have your system programmer check the instruction stream status table to determine which TOD clock is failing to become synchronous.

See TPF Operations for more information about the ZATIM command.

CLKS0074WUNDETERMINED CLOCK ERROR

Explanation: The time-of-day (TOD) clock error message segment was invoked but no message was indicated. This indicates that a logic error occurred in the TOD clock code.

System Action: None.

User Response: See your IBM service representative, and provide a dump and console sheet information for analysis.

See TPF Operations for more information about the ZATIM command.

CLKS0075EUNABLE TO SYNCH TO STR - CPC WILL SYNC LOCALLY

Explanation: An error occurred after entering the ZATIM STR command. The processor could not synchronize to the external synchronization source, which is STR.

This error may have occurred for any of the following reasons:

System Action: The time of day (TOD) clock synchronizes locally.

User Response: Check the STR to ensure that the:

CLKS0081ISOURCE: src SSR: ssr STATUS: status MASTER-- CPUID: id SERIAL: serial MODEL: model SSA: ssa MASTER SYNC SOURCE -- STR NETWORK ID: network id

Where:

src
One of the following:

REMOTE
This processor is synchronized to a remote source.

MASTER
This processor is the synchronization source.

LOCAL
This processor is not synchronized to an external source.

ssr
Two hexadecimal digits in networks with a time-of-day (TOD) RPQ. If a Sysplex Timer (STR) is available, this field may have a default value. If the network has no TOD RPQ, this field is not included.

status
One of the following:

CONFIRMED
The time verified with an external source.

CLOCK SECURE
The TOD is not enabled for setting.

WAITING FOR CONFIRMATION
The CPC is waiting for time verification from an external source.

LOCALLY SYNCHRONOUS
The CPC clocks are internally synchronous.

NOT LOCALLY SYNCHRONOUS
The CPC is not internally synchronous.

CLOCK ERROR
A TOD clock is not operational.

id
The CPU ID for the Master CPC.

serial
The serial for the Master CPC.

model
The model for the Master CPC.

ssa
Two hexadecimal digits in the synchronization selection address (SSA) SSA field of the TOD master in networks with a TOD RPQ. If a Sysplex Timer (STR) is available, this field may have a default value. If the network has no TOD RPQ, then this field is not included.

network id
The STR network ID. If the master synchronous source is not an STR, then the last line of this CLKS0081I message is not included.

Explanation: The term confirmed has two meanings with loosely coupled processors:

If a processor is confirmed local, it is internally synchronous but not synchronized with the complex. If a processor is confirmed remote, the processor is continually being verified through the TOD RPQ or an STR.

As a condition for operation, a tightly coupled processor complex must be internally synchronous. That is, all the I-streams are synchronous with the main instruction stream.

The master processor is locally confirmed, if the TOD RPQ is used. The master processor remotely confirmed, if an STR is used.

When the CPU ID is indicated by a period (.), the processor is not active.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDTIM command. See TPF Main Supervisor Reference for more information about clocks.

CLKS0082ESTR ERROR - PORT port number NOT OPERATIONAL

Where:

port number
One of the two CPC stepping ports.

Explanation: During restart, the CPC stepping port was not operational. This port is not able to receive the Sysplex Timer (STR) oscillator signal.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: See your IBM service representative.

CLKS0083ITWO STRS INSTALLED IN UNCOUPLED MODE

Explanation: Each CPC stepping port on this CPC is connected to a Sysplex Timer (STR) The two STRs are not in high-availability mode because they are uncoupled. One of the ports is disabled. This ensures that fallback does not occur automatically to an STR that is not synchronized with the STR on the primary port.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: Determine whether the CPC configuration is correct or whether the two STRs should be coupled. If the STRs remain uncoupled, the CLKS0087I message is displayed twice (once for the alternate port and once for the primary port). You may then select the STR that you want for the synchronization source. The port connected to the other STR becomes disabled.

CLKS0084EILLEGAL I-STREAM SELECTED -- NO TOD SSA IN CTKI

Explanation: The chosen I-stream does not have a synchronization selection address (SSA) defined in keypoint I.

System Action: None.

User Response: Do one of the following:

CLKS0085ESTR ERROR -- UNABLE TO READ STR DATA

Explanation: One of the following errors occurred:

System Action: One of the following actions occurs:

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

User Response: See your IBM service representative to check the possible problem with the processor controller.

CLKS0086IINCOMPATIBLE WITH MASTER SYNC SOURCE CPC SYNCHRONIZED LOCALLY

Explanation: This CPC is operating in one of the following scenarios:

System Action: In any of the previous cases, the CPC is synchronized locally because the CPC is not able to use the master synchronization source.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

User Response: Determine whether one of the following problems exists and take the appropriate action:

See TPF Operations for more information about the ZATIM command.

CLKS0087ISTR AVAILABLE ON type port PORT: STR ID=str id NETID=network id

Where:

type port
The alternate or primary port.

str id
The Sysplex Timer (STR) ID.

network id
The network ID.

Explanation: The time-of-day (TOD) clock for this CPC is unconfirmed. If this is a loosely coupled complex, there are no other confirmed CPCs. This message is issued to inform you that an STR is available for use as a time and synchronization source. When the message is issued for the alternate port, it indicates that the two CPC stepping ports are connected to two different, uncoupled STRs.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: If you want to use the STR time, enter the ZATIM command with the STR parameter when confirming the TOD clock. The STR is then used automatically as the synchronization source.

If the message is issued for the alternate port, as well as the primary port, and you want to use the STR on the alternate stepping port as the synchronization source, enter the ZATIM command with the ALTPORT parameter when confirming the TOD clock.

Do not include the ALTPORT parameter if you want to use the STR on the primary stepping port.

See TPF Operations for more information about the ZATIM command.

CLKS0088ESTR ERROR -- UNABLE TO READ STR DATA

Explanation: An unsuccessful attempt was made to retrieve the Sysplex Timer (STR) time. Therefore, the STR time could not be displayed on the console.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: Determine whether the CPC stepping port is operational or if there is a problem with the processor controller on the CPC.

CLKS0089IUNABLE TO READ STR ALTERNATE PORT INFORMATION CANNOT DETERMINE IF THE STR COMPLEX IS IN HIGH AVAILABILITY MODE

Explanation: To determine whether the CPC is connected to two coupled Sysplex Timers (STRs), the STR ID and the STR network ID on each CPC stepping port must be read. Because an unsuccessful attempt was made to read the data on the alternate CPC stepping port, the high-availability mode determination cannot be made. If two STRs are coupled, high-availability mode exists. If the CPC is connected to two uncoupled STRs, then one port is not disabled.

Either the CLKS0082E or the CLKS0085E message should accompany this message.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: The TPF system continues the IPL process.

User Response: See your IBM service representative.

CLKS0090ISTRID: str id NETWORK ID: network id PORT NUMBER: port number

Where:

str id
The Sysplex Timer (STR) ID.

network id
The network ID.

port number
The CPC stepping port that is receiving the STR oscillator signal.

Explanation: This informational message, which is issued with the CLKS0018I message, provides details about the STR when a ZDTIM STR command is entered.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZDTIM command.

CLKS0091ASUBSYSTEM xxx ZATIM REQUEST NOT TRANSMITTED TO ALL ACTIVE PROCESSORS BECAUSE OF SIPC TIMEOUT ENTER A ZATIM SET REQUEST TO SYNCHRONIZE THE SUBSYSTEM CLOCKS

Where:

xxx
The subsystem name.

Explanation: The clocks for the subsystem referenced in the message are not synchronized across all active processors because a timeout condition occurred during system interprocessor communications (SIPC) transmission.

System Action: None.

User Response: Enter the ZATIM SET command to cause the TPF system to try to synchronize the subsystem clocks again on all active processors.

See TPF Operations for more information about the ZATME, ZCYCL, and ZATIM commands.

CLKS0092ECANNOT SEND TOD CLOCK IPC MESSAGES TO PROCESSOR x TOD CLOCK IPC MESSAGE LOST

Where:

x
The processor name.

Explanation: More than 25 consecutive time-of-day (TOD) clock messages were returned for the processor referenced in the message.

System Action: The interprocessor communications (IPC) message is not transmitted again.

User Response: Determine why the processor is not receiving its TOD clock IPC messages. You may need to enter a new ZATIM TOD command to synchronize the TOD clock on all of the processors.

See TPF Operations for more information about the ZATIM command.

CLKS0093ISTR IS NOT IN HIGH AVAILABILITY MODE

Explanation: This message informs you that both CPC stepping ports are connected to the same Sysplex Timer (STR)

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: None.

User Response: Determine whether the configuration is correct or whether each CPC stepping port should be connected to a unique STR.

CLKS0094ESTR ERROR -- LOTE VALUE IS ZERO

Explanation: This message informs you that an unsuccessful attempt was made to retrieve the sysplex timer (STR) time.

Note:
The IBM 9037 Sysplex Timer is part of the IBM Enterprise Systems Connection (ESCON) Architecture.

System Action: Processing is continued.

User Response: None.

CLKS0095IRESYNCED CLOCK DUE TO SYNC CHECK

Explanation: The clock has been resynchronized successfully because of a required synchronous check that may have occurred with a port availability change.

System Action: None.

User Response: None.

CLKS0096WRESYNC DUE TO SYNC CHECK FAILED

Explanation: An attempt to resynchronize the clocks because of a synchronization check was not successful. The synchronization check error may have occurred because of a port availability change.

System Action: A synchronization check message follows this message, and the clocks will now go local.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Correct the error, keeping in mind it may be necessary to enter the ZATIM command from 1052 state to bring the clock back to a remote confirmed state.

See TPF Operations for more information about the ZATIM command.