gtpm5m2mMessages (Online)

UBKD-UVSN

UBKD0003IERROR CHECK ORDINAL NUMBER

Explanation: The ZRBKD command was entered specifying an incorrect ordinal number.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct ordinal number.
  2. Enter the ZRBKD command again specifying the correct ordinal number.

See TPF Operations for more information about the ZRBKD command.

UCTK0001ITPFDF CENTRAL DATABASE INIT COMPLETE

Explanation: TPF Database Facility (TPFDF) database definition (DBDEF) table initialization is completed.

System Action: None.

User Response: None.

See the TPFDF library for more information about the TPFDF product.

UCTK0002ITPFDF FAST-LINK DIRECTORY BUILD COMPLETE

Explanation: TPF Database Facility (TPFDF) fast-link table initalization is completed.

System Action: None.

User Response: None.

See the TPFDF library for more information about the TPFDF product.

UDRR0001EZRDRS FUNCTION IS NOT IMPLEMENTED AT THIS TIME

Explanation: You entered the ZRDRS command to activate user data recovery restore support; however, this support cannot be activated because it is not supported in your installation.

System Action: The TPF system ends the activate request.

User Response: Use the UDRR user exit for user data recovery restore support.

See TPF System Installation Support Reference for more information about the user data recovery support user exit.

UDRS0001EZFDRS FUNCTION IS NOT IMPLEMENTED AT THIS TIME

Explanation: You entered the ZFDRS command to activate user data recovery copy support; however, this support cannot be activated because it is not supported in your installation.

System Action: The TPF system ends the activate request.

User Response: Use the UDRS user exit for user data recovery copy support.

See TPF System Installation Support Reference for more information about the user data copy support user exit.

UIM10001EINVALID SCROLL REQUEST

Explanation: A scroll request command that is not valid was entered.

System Action: None.

User Response: Enter a valid scroll command.

See TPF Operations for more information about the Z Mxyy command.

UIM10002ESCROLL MAP NOT ACTIVE

Explanation: A scroll command was entered where is nothing to scroll.

System Action: None.

User Response: Only enter a a scroll command when the scroll bar is visible on the screen.

See TPF Operations for more information about the Z Mxyy command.

URIO0001Waddr CCW code1 SCSW value CC code2 SNS data INTERVENTION REQUIRED

Where:

addr
The physical device address.

code1
The last CCW command code issued. C'**' is printed if the CCW command code cannot be determined.

value
The SCSW at the time of error.

code2
The condition code for the SIOSC error.

data
The sense data associated with the error. Then length of data is device dependent and varies from 2 characters to 12 characters.

Explanation: The device specified in the message is in the Not Ready state and requires operator intervention. After this condition is corrected, the START button should be pressed and this job will start again or continue.

System Action: None.

User Response: With the information provided on the console printout, you should use the following publications for recommended error recovery procedures:

URIO0002Waddr CCW code1 SCSW value CC code2 SNS data CHECK DEVICE

Where:

addr
The physical device address.

code1
The last CCW command code issued. C'**' is printed if the CCW command code cannot be determined.

value
The SCSW at the time of error.

code2
The condition code for the SIOSC error.

data
The sense data associated with the error. The length of data is device dependent and varies from 2 characters to 12 characters.

Explanation: A hardware error condition was detected during the I/O operation and the error condition could be recovered by operator intervention.

Note:
Depending on the situation, the condition code or sense data might not be present.

System Action: None.

User Response: With the information provided on the console printout, you should use the following publications recommended error recovery procedures:

Example:

URIO0005Eaddr CCW code1 SCSW value CC code2 SNS data SIO ERROR

Where:

addr
The physical device address.

code1
The last CCW command code issued. C'**' is printed if the CCW command code cannot be determined.

value
The SCSW at the time of error.

code2
The condition code for the SIOSC error.

data
The sense data associated with the error. Then length of data is device dependent and varies from 2 characters to 12 characters.

Explanation: The Unit Record Support CSECT detected an error condition (nonzero condition code) on an SIOSC macro to initiate input/output (I/O) on the device and the job is aborted.

A device that is not operational would be indicated in the unit record status table.

System Action: None.

User Response: Enter the display unit record status table command. No other operator action is required.

URIO0014Eaddr CCW code1 SCSW value CC code2 SNS data JOB ABORTED -- CHECK DEVICE

Where:

addr
The physical device address.

code1
The last CCW command code issued. C'**' is printed if the CCW command code cannot be determined.

value
The SCSW at the time of error.

code2
The condition code for the SIOSC error.

data
The sense data associated with the error. Then length of data is device dependent and varies from 2 characters to 12 characters.

Explanation: An unrecoverable device error occurred and the job is aborted.

Note:
Depending on the situation, the condition code or sense data might not be present.

System Action: None.

User Response: With the information provided on the console printout, you should use the following publications for recommended error recovery procedures:

UVSN0001I999 MIGRATION DRIVER STARTED FOR SS ssname

Where:

ssname
The subsystem name.

Explanation: Keypoint V indicates that the 999 migration driver, UVSN, must be run for this subsystem. This means there are volume serial numbers in AAANNN format (where A is an alphanumeric character and N is a numeric character) that need to be converted to CCNNNN format (where C is an alphabetic character). UVSN makes use of the value for CCN contained in keypoint V when constructing the new volume serial number (VSN). The CCN value is generated from input to the SIP user macro, ONLFIL.

System Action: Program processing continues converting online DASD VSNs to the CCNNNN format.

User Response: None.

See TPF System Generation for more information about the UVSN listing, the ONLFIL macro, and the keypoint V DSECT (IDSCKV).

UVSN0002EERROR READING CTKV - VSNS FOR SS ssname MAY BE INVALID

Where:

ssname
The subsystem name.

Explanation: This message is issued when an error occurs while reading keypoint V. The 999 UVSN migration driver requires information from Keypoint V to convert the volume serial numbers from AAANNN format to CCNNNN format. Therefore, the volume serial numbers (VSNs) are not converted for this subsystem. See the UVSNO1I message for a description of the AAANNN and CCNNNN formats.

This subsystem remains in migration mode. That is, the migration indicator was not turned off in keypoint V. Therefore, UVSN will be processed again during restart on the next IPL.

System Action: UVSN is ended and the restart schedule is continued.

User Response: The error may be a result of a hardware or software error. Contact your system programmer if it is not a hardware error. After the problem is corrected, the system must be IPLed again.

See TPF System Generation for more information about the UVSN listing and Keypoint V DSECT (IDSCKV).

UVSN0003I999 MIGRATION DRIVER HAS ENDED FOR SS ssname

Where:

ssname
The subsystem name.

Explanation: This message indicates that the 999 UVSN migration driver completed processing.

System Action: The restart schedule is continued.

User Response: None.

See TPF System Generation for more information about the UVSN listing.

UVSN0004ISS ssname IS NO LONGER IN 999 MIGRATION MODE

Where:

ssname
The subsystem name.

Explanation: This message indicates that all volume serial numbers (VSNs) were converted from AAANNN format to CCNNNN format. See the UVSN0001I message for a description of these formats.

The online copy of keypoint V was updated to turn the migration indicator off. The UVSN migration driver will not be processed again during restart as a result of a prime module IPL.

System Action: The UVSN migration driver is completed and the restart schedule is continued.

User Response: None.

See TPF System Generation for more information about the UVSN listing and the keypoint V DSECT (IDSCKV).

UVSN0005EUNABLE TO READ VSN RECORD FROM REL MOD modnum -- VSN IS NOT IN CORRECT >999 FORMAT

Where:

modnum
The relative module number.

Explanation: This message is issued when an error occurs during an attempt to read the volume serial number (VSN) of this module while changing its format from AAANNN to CCNNNN. See the UVSN0001I message for a description of these formats.

The VSN is not changed. This subsystem remains in migration mode, which means the migration indicator was not turned off in keypoint V. Therefore, the UVSN migration driver is processed again during restart on the next IPL.

System Action: The 999 UVSN migration driver continues converting other VSNs as necessary. Once completed, the restart schedule is continued.

User Response: Do the following:

  1. See your system programmer or your IBM service representative to determine the source of the error and to correct the hardware problem.
  2. IPL the TPF system again.

See TPF System Generation for more information about the UVSN listing and the keypoint V DSECT (IDSCKV).

UVSN0006EUNABLE TO FILE MODIFIED VSN RECORD TO REL MOD modnum -- VSN IS NOT IN CORRECT >999 FORMAT

Where:

modnum
The relative module number.

Explanation: This message is issued when an error occurs during an attempt to file the volume serial number (VSN) of this module while changing its format from AAANNN to CCNNNN. See the UVSN0001I message for a description of these formats. The VSN is not changed. This subsystem remains in migration mode, which means the migration indicator was not turned off in keypoint V. Therefore, the migration driver is processed again during restart on the next IPL.

System Action: The migration driver continues converting other VSNs as necessary. Once completed, the restart schedule is continued.

User Response: Do the following:

  1. See your system programmer or your IBM service representative to determine the source of the error and to correct the hardware problem.
  2. IPL the TPF system again.

See TPF System Generation for more information about the UVSN listing and the keypoint V DSECT (IDSCKV).

UVSN0007EALL VSNs SUCCESSFULLY MODIFIED FOR SS ssname -- ERROR FILING CTKV -- STILL IN MIGRATION MODE

Where:

ssname
The subsystem name.

Explanation: This message indicates that all volume serial numbers (VSNs) that were in AAANNN format were converted to CCNNNN format. See the UVSN0001I message for a description of these formats. However, an input/output (I/O) error occurred while trying to take the subsystem out of migration mode by filing keypoint V with the migration indicator off. The migration driver is processed again during restart on the next IPL. The VSNs are not converted during the next processing.

This may be a hardware or software error.

System Action: The migration driver is completed and the restart schedule is continued.

User Response: Do the following:

  1. See your system programmer to determine the cause of the error.
  2. Correct the error.
  3. Do one of the following:

See TPF System Generation for more information about the UVSN listing and the keypoint V DSECT (IDSCKV).

UVSN0008IALL VSNS FOR SS ssname SUCCESSFULLY MODIFIED -- LGF STILL IN >999 MIGRATION MODE.

Where:

ssname
The subsystem name.

Explanation: This message indicates that all volume serial numbers (VSNs) that were in AAANNN format were converted to CCNNNN format. See the UVSN0001I message for a description of these formats. Since the CYYA keypoint update program is not capable of filing keypoints to the loader general file, the migration indicator is not turned off in the loader general file version of keypoint V. The online copy of keypoint V still indicates that the associated subsystem is in migration mode. The UVSN migration driver is processed again during restart as a result of a prime module IPL. However, no VSNs will are changed. At this point, the migration indicator is turned off in the online version of keypoint V.

System Action: The migration driver is completed and the restart schedule is continued.

User Response: Load CTKV again with the migration bit off to prevent the UVSN migration driver from being entered during restart as result of a loader general file IPL.

See TPF System Generation for more information about the UVSN listing and the Keypoint V DSECT (IDSCKV).

UVSN0009EVSN OF IPL DEVICE FOR SS ssname MIGRATED -- UNABLE TO UPDATE FILE COPY OF CTKM

Where:

ssname
The subsystem name.

Explanation: The volume serial number (VSN) of the IPL device was converted from AAANNN format to CCNNNN format. See the UVSN0001I message for a description of these formats. The migration driver tried to update keypoint M with the new VSN for the IPL device but an error occurred while filing keypoint M.

System Action: The migration driver is completed and the restart schedule is continued.

User Response: The error may be a result of a hardware or software error. See your system programmer if it is not a hardware problem. A hardware IPL must be performed on the system.

See TPF System Generation for more information about the UVSN listing.