gtpm5m08Messages (Online)

APGM-AVSN

APGM0011IBEGIN DISPLAY OF FILE COPY FOR comp VERSION vv IN IMAGE name

Where:

comp
The name of the core image restart (CIMR) area component, initial program load (IPL) component, or CSECT.

vv
The version code of the component.
Note:
This displays only for for CIMR and IPL components, and CSECTs that have an associated version code.

name
The name of the image containing the CIMR component or CP CSECT. This is not shown for IPL components.

Explanation: This is the normal response to the ZAPGM command. This message is followed by a display of two lines of data.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAPGM command and an example of the informational display.

APPN0001ICP-CP SESSIONS ESTABLISHED WITH CP cpname

Where:

cpname
The name of the remote CP with which APPN CP-CP sessions have been established.

Explanation: This message is issued whenever CP-CP sessions have been established and were not done so due to a TPF operator request, which can happen in the following situations:

System Action: None.

User Response: None.

APPN0002IAPPN LU REGISTRATION HAS COMPLETED

Explanation: This message is issued when the TPF system has registered all of its LUs with the APPN network.

System Action: None.

User Response: None.

APPN0003ICP-CP SESSIONS WITH CP cpname HAVE BEEN DEACTIVATED

Where:

cpname
The name of the remote CP with which the TPF system had CP-CP sessions.

Explanation: CP-CP sessions between the TPF system and the specified remote CP were taken down by the remote operator.

System Action: None.

User Response: If you want to bring up new CP-CP sessions, enter a ZNETW ACT command.

See TPF Operations for more information about the ZNETW ACT command.

APPN0040WCYCLING DOWN WITH ACTIVE CP-CP SESSIONS

Explanation: This message is issued when the TPF processor with the CP-CP sessions cycles down to 1052 state and the TPF system is running loosely coupled. While this TPF processor is in 1052 state, no TPF processor in the loosely coupled complex can start any new LU-LU sessions in the APPN network.

System Action: None.

User Response: If new LU-LU sessions must be started, do one of the following:

APPN0050EUNABLE TO REGISTER LU luname IN APPN NETWORK, SENSE snscode

Where:

luname
The name of the TPF logical unit (LU) that was not registered successfully.

snscode
The sense code in the reply to the register request.

Explanation: This message is issued when the TPF system was not able to register one of its LUs in the APPN network.

System Action: None.

User Response: Use the sense code to determine the cause of the error.

APPN0051ECP-CP SESSIONS WITH CP cpname HAVE FAILED, ATTEMPTING RECOVERY

Where:

cpname
The name of the remote CP with which the TPF system had CP-CP sessions.

Explanation: CP-CP sessions between the TPF system and the specified remote CP failed unexpectedly.

System Action: The TPF system tries to reestablish CP-CP sessions automatically.

User Response: None.

APPN0052AAUTOMATIC CP-CP SESSION RECOVERY HAS FAILED

Explanation: CP-CP sessions failed unexpectedly and the TPF system was unable to reactivate the CP-CP sessions again.

System Action: None.

User Response: Do the following:

  1. Ensure there is at least 1 active APPN link that supports CP-CP sessions.
  2. Enter the ZNETW ACT command (or the equivalent message on the remote system) to activate the CP-CP sessions manually.

See TPF Operations for more information about the ZNETW ACT command.

APPN0053APROCESSOR x DEACTIVATED, CP-CP SESSIONS LOST

Where:

x
The CPU ID of the TPF processor that was deactivated.

Explanation: The TPF processor in the loosely coupled complex that has the CP-CP sessions was deactivated.

System Action: None.

User Response: Do the following:

  1. If the links to the deactivated TPF processor have not gone into automatic network shutdown (ANS) and the network thinks that the CP-CP sessions are still active, deactivate the CP-CP sessions from the remote operator console.
  2. Once the old CP-CP sessions are taken down, enter the ZNETW ACT command (or equivalent message from the remote console) to activate new CP-CP sessions.

See TPF Operations for more information about the ZNETW ACT command.

AREC0011IDISPLAY OF FILE ADDRESS fileaddr

Where:

fileaddr
The 16-digit hexadecimal file address.

Explanation: This is the normal response to the ZAREC command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAREC command and for an example of the informational display.

AREC0020IUNIQUE COPIES OF THIS RECORD EXIST FOR OTHER I-STREAMS, PROCESSORS, OR SUBSYSTEM USERS

Explanation: This is an informational message. The record being altered is not shared by all other I-streams, processors, and subsystem users (SSUs).

System Action: The physical record is altered for the current (default) I-stream, processor, and SSU name where the command was entered. Other copies, with different physical records, may exist for other I-streams, processors, or SSUs.

User Response: Use the IS-x CPUID-y SSU-zzzz optional keywords to alter the physical record for a specific I-stream, processor, or SSU.

See TPF Operations for more information about the ZAREC command.

ASER0000I- OK

Explanation: This is the normal response to the ZASER command.

System Action: None.

User Response: Enter the ZDSER command from the subsystem to determine which options are in effect.

See TPF Operations for more information about the ZASER and ZDSER commands.

ASER0041ENO PARAMETERS SPECIFIED

Explanation: The ZASER command requires at least one parameter.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZASER command.

ASER0042EINVALID PARAMETER -- parmx

Where:

parmx
The parameter that is not valid.

Explanation: The parameter shown is not among the list of valid ZASER parameters.

System Action: The ZASER request is ignored.

User Response: Enter the ZASER command again and specify valid parameters.

See TPF Operations for more information about the ZASER command.

ASER0097EICDF NOT LOADED -- ZASER PRT REQUEST REJECTED

Explanation: Dumps cannot be routed to the real-time printer if the in core dump formatter is not in the TPF system.

System Action: The ZASER command is rejected.

User Response: If dumps to the printer are desired, modify the SIPGEN CONFIG macro to cause ICDF to be included in the TPF system generation.

See TPF Operations for more information about the ZASER command.

ASER0098EUNABLE TO RETRIEVE KEYPOINT A -- ZASER REQUEST REJECTED

Explanation: Keypoint A is needed to save the system error option changes to file. If it cannot be found, then the file copy of the options cannot be updated.

System Action: The ZASER command is rejected.

User Response: Review the system dump generated by the CYYM keypoint retrieval program to determine the cause of the error and to correct it

See TPF Operations for more information about the ZASER command.

ASER0099EBSS NOT IN TEST MODE -- ZASER PRT REQUEST REJECTED

Explanation: Dumps cannot be routed to the real-time printer when the TPF subsystem is not in test mode.

System Action: The ZASER command is rejected.

User Response: None.

See TPF Operations for more information about the ZASER command.

ATIM0001ISUBSYSTEM xxxx LOCAL STANDARD TIME

Where:

xxxx
The subsystem name.

Explanation: This is a normal response to the ZATIM command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATIM command.

ATIM0002ITIME OF DAY CLOCK SET

Explanation: This is the normal response to the ZATIM command.

System Action: The ZATIM command completed successfully.

User Response: None.

See TPF Operations for more information about the ZATIM command.

ATIM0051EINVALID FORMAT

Explanation: The format of the ZATIM command is not correct.

System Action: The ZATIM command is rejected.

User Response: Do the following:

  1. Determine the correct format of the ZATIM command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZATIM command.

ATIM0052TFACE ERROR

Explanation: The file address compute program (FACE) returned an error code when trying to find the subsystem clock record.

System Action: The ZATIM command request is stopped or ended.

User Response: Report this error to your supervisor.

See TPF Operations for more information about the ZATIM command.

ATIM0053TFIND ERROR

Explanation: FIND returned an error code when trying to find the subsystem clock record.

System Action: The ZATIM command request is stopped or ended.

User Response: Report this error to your supervisor.

See TPF Operations for more information about the ZATIM command.

ATIM0054TTIME BASE ERROR -- DISPLAY TIME AND REENTER ZATIM REQUEST

Explanation: The time base did not match the saved HHMM portion from a previous ZDTIM local standard time clock message.

System Action: The ZATIM command request is stopped or ended.

User Response: Do the following:

  1. Display the desired clock again by entering the ZDTIM command.
  2. Enter a new alter time request.

See TPF Operations for more information about the ZDTIM command.

ATIM0055TTIME SPECIFIED FOR SET/ADD/TOD IS NOT VALID REQUEST

Explanation: The time specified for the set or add time-of-day (TOD) is not a valid request.

System Action: The ZATIM command request is stopped or ended.

User Response: None.

See TPF Operations for more information about the ZATIM command.

ATIM0056TSSU DORMANT -- ZATIM REQUEST FOR SS IS INVALID

Explanation: The first subsystem user (SSU) in this subsystem (SS) is dormant. The SS clocks may be set in this state.

System Action: The ZATIM command request is stopped or ended.

User Response: None.

See TPF Operations for more information about the ZATIM command.

ATIM0058TINVALID REQUEST -- SYSTEM NOT IN 1052 STATE

Explanation: A ZSTVS CLOCK RESTORE or SET hhmm mmddyy command was entered and the TPF system was not in 1052 state. The RESTORE and SET TIME/DATE options are valid only in 1052 state.

System Action: The ZATIM command request is stopped or ended.

User Response: Do the following:

  1. Cycle the TPF system to 1052 state.
  2. Enter the command again.

See TPF Operations for more information about the program test vehicle (PTV).

ATIM0059TINVALID TIME/DATE

Explanation: A ZSTVS CLOCK SET hhmm mmddyy command was entered with a time or date that is not valid. Either the date was prior to Jan. 04, 1966, or one of the time or date values exceeded the allowable limit (for example, month greater than 12).

System Action: The ZATIM command request is stopped or ended.

User Response: Enter the command again with the correct time and date.

See TPF Operations for more information about the program test vehicle (PTV).

ATIM0060TINVALID REQUEST -- SYSTEM NOT IN 1052 STATE

Explanation: A ZSTVS CLOCK RESTORE or ZSTVS CLOCK SET hhmm mmddyy command was entered before the TPF system was in 1052 state. The RESTORE and SET TIME/DATE options are valid only in 1052 state.

System Action: The ZATIM command request is stopped or ended.

User Response: Do the following:

  1. Cycle to 1052 state.
  2. Enter the command again.

See TPF Operations for more information about the program test vehicle (PTV).

ATIM0061TRESTORE COMPLETE

Explanation: A ZSTVS CLOCK RESTORE request was completed successfully. The times were saved by a ZSTVS CLOCK SET TIME/DATE request.

System Action: The ZATIM command request is stopped or ended.

User Response: None.

See TPF Operations for more information about the program test vehicle (PTV).

ATIM0061EONLY BSS USERS MAY ALTER THE TIME OF DAY CLOCK

Explanation: The Set Time request message was entered in a subsystem other than the basic subsystem (BSS). This is not allowed.

System Action: The ZATIM command request is stopped or ended.

User Response: Enter the request again in the BSS.

See TPF Operations for more information about the ZATIM command.

ATIM0062TUNABLE -- NO PREVIOUSLY SAVED TIMES

Explanation: A ZSTVS CLOCK RESTORE command was entered, however no previous times were saved by a ZSTVS CLOCK SET TIME/DATE request.

System Action: The ZATIM command request is stopped or ended.

User Response: None.

See TPF Operations for more information about the program test vehicle (PTV).

ATIM0063TALTER THE TIME OF DAY CLOCK IS INVALID AT THIS TIME

Explanation: The time-of-day (TOD) clock was not altered because the basic subsystem (BSS) is not in 1052 state or because the TOD clock is currently being updated.

System Action: The ZATIM command request is stopped or ended.

User Response: Wait until the previous set time request is finished.

See TPF Operations for more information about the ZATIM command.

ATIM0064TTIME OF DAY CLOCK WAS NOT ALTERED

Explanation: An error occurred during the setting of the time-of-day (TOD) clock. This display indicates that the value of the TOD clock was not changed.

System Action: The ZATIM command request is stopped or ended.

User Response: Do the following:

  1. Review any other error displays regarding setting of the TOD clock to determine the cause of the problem and to correct it.
  2. Enter the set time request again.

See TPF Operations for more information about the ZATIM command.

ATIM0070EINVALID REQUEST -- COMPLEX NOT USING STR TIME

Explanation: A ZATIM xxxx STR GOOD command was entered on a processor to resynchronize it back into a complex that is using the Sysplex Timer (STR) as the synchronous source and the time value from the STR. However, the request is rejected because it found that the complex is not using the time value from the STR (for example, a ZATIM xxxx TOD hhmmss ddmmyy command or a ZATIM xxxx TOD GOOD command may have been used when establishing the synchronous source in the complex.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZATIM command.

ATIM0071TCTKI RETRIEVAL ERROR; UNABLE TO DETERMINE TIME SOURCE

Explanation: Keypoint I (CTKI) could not be retrieved and the TPF system is unable to determine whether the complex was synchronized to the time of the Sysplex Timer (STR).

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

System Action: None.

User Response: Do the following:

  1. Determine why CTKI could not be retrieved from disk.
  2. Correct the problem.

See TPF Operations for more information about the ZATIM command.

ATIM0073EPROCESSOR NOT IN 1052 STATE

Explanation: The processor needs to be in restart or 1052 state.

System Action: None.

User Response: Do the following:

  1. Cycle the processor to 1052 state.
  2. Enter the ZATIM command again.

See TPF Operations for more information about the ZATIM command.

ATIM0075EFORMAT ERROR

Explanation: There was a format error on the input TOD message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATIM command.

ATIM0076EINVALID TIME/DATE

Explanation: The time or date specified for setting the time-of-day (TOD) clock was not valid. The time must be specified using the 24-hour clock in the form the form of HHMMSS. The date must be specified using the form of MMDDYY.

Specifying numbers outside the 24-hour clock range or dates outside the true calendar are flagged as incorrect. For example, 022983 is not correct because 1983 was not a leap year.

System Action: None.

User Response: Do the following:

  1. Determine whether the time or date was incorrect.
  2. Correct the time or date.
  3. Enter the ZATIM command with the correct time or date.

See TPF Operations for more information about the ZATIM command.

ATIM0077AUNABLE TO CONFIRM-- TOD CLOCK NOT SET 'ZATIM SET TOD' REQ'D-- ENTER FORMAT: 'ZATIM HHMM TOD HHMMSS MMDDYY'

Explanation: A GOOD parameter for the time was specified during a set time request but the time-of-day (TOD) clock found an error condition when it tried to store the current time. The TOD is inoperative, not running, in error, or not set.

System Action: None.

User Response: Try to set the time (by entering the ZATIM command), giving a time and date rather than a GOOD parameter. If the TOD clock can be started or be set, it is done by the set time request.

See TPF Operations for more information about the ZATIM command.

ATIM0078EDATE MUST BE LATER THAN MAY 11, 1971

Explanation: Either the date specified through the time-of-day (TOD) message or the date retrieved from the Sysplex Timer (STR) was not later than the date allowed by the high-order bits in the TOD clock (May 11, 1971).

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

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZATIM command. See 370/XA Principles of Operation for more information about the time-of-day (TOD) clock.

ATIM0080TINVALID PARAMETER IN ZATIM TSC REQUEST

Explanation: One of the following problems occurred in the input message:

System Action: None.

User Response: Enter the ZATIM TSC command again in the correct format.

See TPF Operations for more information about the ZATIM command. See TPF System Generation for more information about migration aids.

ATIM0081TZATIM TSC REQUEST IS ONLY ALLOWED ON AN HPO SYSTEM

Explanation: The time-of-day (TOD) synchronization compatibility (TSC) hardware is only intended for use on a loosely coupled TPF system where there are CPCs capable of being directly attached to a Sysplex Timer (STR) and CPCs that require the TOD RPQ in the complex at the same time. Because this is not a loosely coupled TPF system, the ZATIM TSC command is rejected.

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 ZATIM command. See TPF System Generation for more information about migration aids.

ATIM0082ITOD SYNCHRONIZATION COMPATIBILITY (TSC) INFORMATION ADDED TO CTKI

Explanation: This message indicates the successful completion of the ZATIM TSC request. The time-of-day (TOD) synchronization compatibility (TSC) information was added to keypoint I. The Sysplex Timer (STR) can now be used as a synchronization source. For TOD RPQ processors connected to an STR through the TSC hardware, the STRNM parameter must be included in the ZATIM TOD command.

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 ZATIM command. See TPF System Generation for more information about migration aids.

ATIM0083TCTKI RETRIEVAL ERROR; UNABLE TO ADD TOD SYNCHRONIZATION COMPATIBILITY (TSC) INFORMATION.

Explanation: An unsuccessful attempt was made to retrieve keypoint I by using the CYYM keypoint retrieval program. This occurred during processing of a ZATIM TSC command.

System Action: None.

User Response: Determine the cause of the CTKI error and correct it.

See TPF Operations for more information about the ZATIM command. See TPF System Generation for more information about migration aids.

ATIM0084TNO AVAILABLE ENTRIES IN CTKI; UNABLE TO ADD TOD SYNCHRONIZATION COMPATIBILITY (TSC) INFORMATION

Explanation: The synchronization selection address (SSA) specified in the ZATIM TSC command does not exist in Keypoint I (CTKI) The time-of-day (TOD) synchronization compatibility (TSC) information cannot be added to CTKI because all the entries are in use. This problem could occur if an SSA is used in more than one CTKI entry.

System Action: None.

User Response: Enter the ZDFIL command to display the TOD clock synchronization CPC identification table at the end of CTKI.

If an SSA is being used in more than one table entry, enter the ZAFIL command to correct the problem. Then, enter the ZATIM TSC command again.

Otherwise, enter the ZAFIL command to add the TSC information to CTKI.

See TPF Operations for more information about the ZATIM command. See TPF System Generation for more information about migration aids.

ATIM0085ESOME PROCESSORS NOT IN 1052 STATE

Explanation: All processors in the TPF system must be in 1052 state for a time-of-day (TOD) clock to be set, unless the BP option was specified. The TOD clock is the basis of the other clocks in the TPF system. The other clocks are set with respect to the TOD clock during cycling to NORM state. The loosely coupled master determines the setting on the TPF system TOD clock.

If the BP option is invoked, the loosely coupled master switches to the processor setting the time. The other processors in the loosely coupled TPF system are informed that the TOD clock was reset. Those in 1052 state will reset their times.

System Action: None.

User Response: If this is not a loosely coupled TPF system, cycle the TPF system to 1052 state and enter the set time request again.

If this is a loosely coupled TPF system, determine first whether the processor where the set time request was entered is or is to become the master. If it is not to become the master, switch to the processor of the loosely coupled master. Use the BP option to force the set time request or cycle all the processors in the TPF system to 1052 state.

See TPF Operations for more information about the ZATIM command.

ATIM0086ECYCLE ALREADY DISABLED IN THIS PROCESSOR

Explanation: The TPF system issues this message when you enter a set time request before a previous set time request finished or some other process disabled the TPF system from cycling.

System Action: None.

User Response: Wait until the previous set time request is finished. If, due to an error condition, there is no previous request outstanding enter the ZPSMS CYCLE ENABLE BP command to enable cycling again.

During set time requests, cycling is disabled, so enter the set time request again.

See TPF Operations for more information about the ZATIM command.

ATIM0087EUNABLE TO INHIBIT CYCLE

Explanation: Processing of the set time request was unable to inhibit cycling above 1052 state. The set time request was ended to preserve the integrity of the TPF system clocks.

System Action: None.

User Response: Cycle the TPF system to 1052 state or enable cycling again by entering the ZPSMS CYCLE ENABLE BP command.

See TPF Operations for more information about the ZATIM command.

ATIM0088ECTKI RETRIEVAL ERROR

Explanation: Keypoint CTKI could not be retrieved to update the time-of-day (TOD) clock synchronization fields.

System Action: None.

User Response: Report the problem to your system programmer.

See TPF Operations for more information about the ZATIM command.

ATIM0089EZATIM TOD VALID ONLY FROM CPU-ID x

Where:

x
The CPU ID.

Explanation: A time-of-day (TOD) message was issued on a processor that is currently not the master for TOD time and date in a loosely coupled TPF system.

The current master is the processor identified by x.

System Action: None.

User Response: Enter the TOD message again with the BP option on this CPU or enter the message on the processor identified by x.

If the message is entered again on this CPU with the BP option, this processor becomes the master for TOD date and time.

See TPF Operations for more information about the ZATIM command.

ATIM0090AKEYPOINT INDICATES ALL PROCESSORS ARE NOT IN 1052 STATE ENTER 'ZATME CONT' TO CONTINUE OR 'ZATME CNCL' TO CANCEL THE ZATIM REQUEST

Explanation: There are processors in the complex that are above 1052 state.

System Action: None.

User Response: Enter a ZATME CONT command to continue the ZATIM TOD operation or enter a ZATME CNCL command to cancel the ZATIM TOD request.

See TPF Operations for more information about the ZATME command.

ATIM0091EINVALID REQUEST -- ALTPORT PARAMETER NOT ALLOWED

Explanation: There are two cases when the ALTPORT parameter is not allowed:

System Action: None.

User Response: Enter the ZATIM command again without the ALTPORT parameter.

See TPF Operations for more information about the ZATIM command.

ATIM0092EINVALID REQUEST -- STRNM PARAMETER NOT ALLOWED

Explanation: The STRNM parameter is used to specify that the time-of-day (TOD) synchronization compatibility (TSC) hardware is connected to this CPC. In order for the TSC to be connected, the TOD RPQ must exist on this CPC. This message is entered because the TOD RPQ is not present.

System Action: None.

User Response: Enter the ZATIM command again without the STRNM parameter.

See TPF Operations for more information about the ZATIM command.

ATIM0093EINVALID REQUEST -- STR PARAMETER NOT ALLOWED

Explanation: The time given by the Sysplex Timer (STR) can only be used to set up the time-of-day (TOD) clocks on CPCs that are directly connected to an STR.

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 again one of the following formats:

See TPF Operations for more information about the ZATIM command

ATIM0094AUNABLE TO RETRIEVE STR TIME RELIABLY ZATIM SET TOD REQ'D ENTER ONE OF THE FOLLOWING FORMATS 'ZATIM HHMM TOD HHMMSS MMDDYY' OR 'ZATIM HHMM TOD GOOD'

Explanation: 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: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZATIM command.

ATIM0095ESERIAL NUMBER/SSA NOT FOUND IN CTKI -'STRNM- ' PARM REQUIRED

Explanation: In a loosely coupled complex on a CPC with a time-of-day (TOD) RPQ, a synchronization selection address (SSA) is required. An SSA could not be associated with this CPC because the serial number for the CPC was not found in keypoint I. However, the TOD synchronization compatibility (TSC) hardware information was found, and therefore, the STRNM parameter was expected on the ZATIM command to indicate the port connected to a TSC should be used. Because the STRNM parameter was not included in the input message, no SSA could be assigned.

System Action: None.

User Response: If the CPC is connected to a TSC, enter the ZATIM command again with the STRNM parameter.

Otherwise, determine why the serial number for this CPC was not found in keypoint I. The online commands ZDKAT and ZDFIL can be used to determine the file address and content of keypoint I. The ZAFIL command can be used to modify the content of keypoint I after you have determined the cause of the problem.

See TPF Operations for more information about the ZATIM command.

ATIM0096WSYNC SOURCE SWITCHING FROM STR TO TOD RPQ

Explanation: The master synchronization source was a Sysplex Timer (STR). Because this CPC has a time-of-day RPQ, and the STRNM parameter was not specified on the ZATIM command, the TOD RPQ becomes the new synchronization source.

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

System Action: None.

User Response: If you want the TOD RPQ to be the new synchronization source, then no action is necessary. However, if you want the Sysplex Timer (STR) to remain the synchronization source and this CPC is connected to an STR through the TOD synchronization compatibility (TSC) hardware, enter the ZATIM command again with the STRNM parameter.

If you want the STR to remain the synchronization source and this CPC is not connected to a TSC, then enter the ZATIM command again from another CPC.

See TPF Operations for more information about the ZATIM command.

ATIM0097ESTRNM DEFINITION NOT FOUND IN CTKI

Explanation: The name specified in the STRNM parameter was not found in keypoint I.

System Action: None.

User Response: Do the following:

  1. Specify an STRNM name that is in keypoint I.
  2. Enter the ZATIM command again.

See TPF Operations for more information about the ZATIM command.

ATIM0098EBP OR STRNM OPTIONS REQD SINCE STR IS SYNC SOURCE

Explanation: Currently, a Sysplex Timer (STR) is the synchronization source. This CPC has a time-of-day (TOD) RPQ but the STRNM parameter was not specified on the ZATIM command.

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 again with the bypass option (BP) to switch the synchronization source from the Sysplex Timer (STR) to the TOD RPQ. Otherwise, enter the ZATIM command again with the STRNM parameter to keep the STR as the synchronization source when there is TOD synchronization compatibility (TSC) hardware connected to the CPC.

See TPF Operations for more information about the ZATIM command.

ATIM0099EINVALID NUMBER OF LEAP SECONDS IN CTKI

Explanation: A nonzero value for the number of leap seconds in keypoint I (CTKI) indicates that the time-of-day (TOD) clock is using absolute time. The ZATIM request was not processed because the number of leap seconds in keypoint I is greater than 50.

System Action: None.

User Response: Use the ZDKAT and ZDFIL commands to determine the file address and content of keypoint I. The ZAFIL command can be used to modify the number of leap seconds in keypoint I. If a Sysplex Timer (STR) is available, determine the correct number of leap seconds from the STR device panel that displays offsets. After altering keypoint I, enter the ZATIM command.

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.

ATME0001IZCYCL WILL CONTINUE AS REQUESTED

Explanation: This is a normal message for the ZATME command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME command.

ATME0002IZCYCL CANCELLED AS REQUESTED

Explanation: This is a normal message for the ZATME command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME command.

ATME0003IZATIM WILL CONTINUE AS REQUESTED

Explanation: This is a normal message for the ZATME command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME command.

ATME0004IZATIM CANCELLED AS REQUESTED

Explanation: This is a normal message for the ZATME command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME command.

ATME0051EINVALID FORMAT

Explanation: This message results when the ZATME command is entered in an incorrect format.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME command and its format.

ATME0052EZATME COMMAND IS NOT VALID AT THIS TIME

Explanation: The ZATME command was not entered in response to a date change command or a ZATIM continue command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZATME command.

AURS0006EINPUT FORMAT ERROR

Explanation: The ZAURS command was entered incorrectly.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0007EINVALID DEVICE ADDRESS

Explanation: The address specified in the command contains hexadecimal characters that are not valid or the address is not in the unit record status table.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0008EDEVICE NOT IN U/R STATUS TABLE

Explanation: The device specified in the input message is not in the status table or the status table has no entries. The symbolic name is not in the unit record status table.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0009EINVALID DEVICE TYPE

Explanation: The device type specified in the input message is not valid.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0010EERROR IN FINDING BUFFER TABLE

Explanation: CUAB found an error on the FIND of the buffer for the type of printer specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0011EINVALID BUFFER NAME

Explanation: The buffer name was not found in the table associated with the device at the input address.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0012EERROR ON BUFFER LOAD

Explanation: While trying to run a URCTC macro (which causes the user-provided CCCWs) to be processed to a specified unit record device) a hardware error occurred. The device was suspended.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0013IFCB LOADED-RESET FORM TO LINE 1

Explanation: This is the normal response to the ZAURS FCBL command.

While trying to process a URCTC macro (which causes the user-provided CCWs to be processed to a specified unit record device) a hardware error occurred. The device was suspended.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS FCBL command.

AURS0015IUCSB LOADED

Explanation: This message is issued if the universal character set buffer is loaded successfully on a specified unit record device.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0016EDEVICE IN USE

Explanation: The device is in use by another application program.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0017EJOB NOT IN U/R JOB TABLE

Explanation: The job specified in the input message is not in one of the job tables.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands. See TPF Database Reference for more information about the unit record message editor.

AURS0018ESYSTEM ACTIVITY TOO HIGH -- JOB NOT STARTED

Explanation: The TPF system activity is too high so the job is not started.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands. See TPF Database Reference for more information about the unit record message editor.

AURS0019ETOO MANY SYM NAMES SPECIFIED

Explanation: The number of symbolic names specified in the input message is more than the number of unit record devices in the TPF system.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0020ENO DEVICES AVAILABLE

Explanation: One or more of the requested unit record devices were not available.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0021ETAPE HARDWARE ERROR

Explanation: An unexpected error occurred during tape processing.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0022ELENGTH ERR- JOB ABORTED

Explanation: A long length record error was found by the Tape to Print utility while reading a tape device. The utility request is aborted.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0050IUNIT RECORD STATUS

Explanation: This is the normal response to the ZAURS DURT command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS DURT command and for an example of the informational display.

AURS0051IREQUEST SUMMARY NOT ABORTED: xxx ABORT STARTED ON: vxxx SUSPENDED AND ABORT STARTED: xxx

Explanation: This is the normal response to the ZAURS ABRT command.

System Action: None.

User Response: None.

AURS0052IOPTION xx COMPLETED

Where:

xx
The option name.

Explanation: This is the normal response to the ZAURS command with the UTIL parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0053WOPT xx ABORTED

Where:

xx
The option name.

Explanation: An input/output (I/O) error occurred while processing the ZAURS UTIL command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AURS0054E1055 BYTES OF SOME RCDS PRINTED

Explanation: The first 1055 bytes of a record greater than 1055 bytes were printed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAURS commands.

AVSN0000IVSN ON DISK ccud IS vvvvvv

Where:

ccud
The device address.

vvvvvv
The volume serial number (VSN).

Explanation: The function issues this message upon normal completion of a ZAVSN request. This messages displays the volume serial number (VSN) prior to the alter. This message is followed by the AVSN0001I message after the VSN is changed.

System Action: Processing of the ZAVSN command is continued.

User Response: None.

See TPF Operations for more information about the ZAVSN command.

AVSN0001IALTER OF VSN COMPLETE

Explanation: The function issues this message after the volume serial number (VSN) was changed due to a ZAVSN request. This message follows the AVSN00I message, which displays the VSN before it was altered.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZAVSN command.

AVSN0058TI/O ERROR READING VSN

Explanation: The function issues this message when an input/output (I/O) error occurs while trying to read the existing volume serial number (VSN).

System Action: Program processing is ended and the volume serial number (VSN) on the device is not altered.

User Response: See your system programmer or IBM service representative to determine the cause of the error and to correct the hardware problem.

See TPF Operations for more information about the ZAVSN command.

AVSN0061TINPUT VSN IS NON-STANDARD

Explanation: This message is issued when you specify a volume serial number (VSN) with characters that are not valid.

Valid characters are:

Nonstandard characters are allowed only when they are framed with apostrophes as the first and last characters.

System Action: Program processing is ended and the volume serial number (VSN) on the device is not altered.

User Response: Enter the ZAVSN command again with a VSN that conforms to the standards.

See TPF Operations for more information about the ZAVSN command.

AVSN0062TI/O ERROR WRITING VSN

Explanation: This message occurs when the new volume serial number (VSN) cannot be written to the device.

System Action: Program processing is ended and the volume serial number (VSN) on the device is not altered.

User Response: See your system programmer or an IBM service representative to determine the source of the error and to correct the hardware problem.

See TPF Operations for more information about the ZAVSN command.

AVSN0066TVOLUME LABEL NOT SPECIFIED FOR AN ALTER

Explanation: This message is issued when you do not specify a volume serial number (VSN) after the device address in the ZAVSN command.

System Action: Program processing is ended and the volume serial number (VSN) on the device is not altered.

User Response: Enter the ZAVSN command again with a volume serial number (VSN) specified.

See TPF Operations for more information about the ZAVSN command.

AVSN0067TALTER FOR AN IN--USE DEVICE NOT ALLOWED

Explanation: You cannot alter the volume serial number (VSN) on an online device. This restriction is in place to preserve the relationship between the device relative module number and its VSN. You can only alter the VSNs for offline devices.

System Action: Program processing is ended and the volume serial number (VSN) on the device is not altered.

User Response: If it is necessary to alter the volume serial number of this device, take it offline and enter the ZAVSN command again.

See TPF Operations for more information about the ZAVSN command.

AVSN0088TTO DEVICE IS UNUSABLE

Explanation: This error occurred during processing of the ZAVSN command. An attempt was made to mount a device through CPAB, but an input/output (I/O) error occurred during an attempt to mount the 3990 Record Cache Subsystem device.

System Action: Program processing is ended and the volume serial number (VSN) on the device is not altered.

User Response: See your IBM service representative to help you determine the cause of the error.

See TPF Operations for more information about the ZAVSN command.

AVSN0090TATTEMPT TO MOUNT REQUESTED VOLUME ccud FAILED

Where:

ccud
The device address.

Explanation: The error occurred during processing of the ZAVSN command. An attempt was made to mount the requested volume through CPAA but an error occurred during mount processing. Because of this error, the volume could not be used.

At the time the problem was detected, a more detailed diagnostic message was issued by CPAA to describe the reason that the volume could not be mounted to the TPF system. That message, which has a CPAA prefix, will precede the AVSN0090T message on your console.

System Action: Program processing is ended. The volume serial number (VSN) on the device is not altered.

User Response: None.

See TPF Operations for more information about the ZAVSN command.