gtpm5m0f | Messages (Online) |
BRYD0001I | RECOUP GENERAL FILE NOT REQUESTED PLEASE DISMOUNT - RECOUP CONTINUING |
Explanation: The recoup general file is mounted but has not been requested for this recoup run.
System Action: Recoup processing continues.
User Response: Dismount the recoup general file.
BRYD0002I | RECOUP DIRECTORY CAPTURE TIMEOUT LIMIT REACHED - RECOUP ABORTING |
Explanation: Recoup directory capture processing exceeded the processing timeout limit.
System Action: Recoup processing ends abnormally.
User Response: Do the following:
BRYL0013W | MOUNT RPE TAPE FOR INPUT |
Explanation: Recoup is in phase 3 and is looking for the RPE tape to read the pseudo directories, but the tape is not mounted.
System Action: Recoup processing waits until the RPE tape is mounted.
User Response: Mount the RPE tape.
BUFC0001I | RC CONTROL UNIT CACHE ALLOCATIONS |
Explanation: This is the normal response to the ZBUFC ALLOCATE DISPLAY command. Following this message is a display that contains the current and target cache allocation values for 3880 Record Cache Control Units in the complex.
If you entered the ZBUFC ALLOCATE DISPLAY command without any options or with the ALL option, then the BUFC02I message accompanies this message.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC ALLOCATE DISPLAY command and an example of the informational display. See TPF Database Reference for more information about record caching.
BUFC0002I | RCS CONTROL UNIT CACHE ALLOCATIONS |
Explanation: This is the normal response to the ZBUFC ALLOCATE DISPLAY command. Following this message is a display that contains the current and target cache allocation values for 3990 Record Cache Subsystem Control Units and the concurrency filter lock facility.
If you entered the ZBUFC ALLOCATE DISPLAY command without any options or with the ALL option, then the BUFC0001I message accompanies this message.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC ALLOCATE DISPLAY command and an example of the informational display. See TPF Database Reference for more information about record caching.
BUFC0003I | STORAGE DIRECTOR/DEVICE ADDRESS - xxxx |
Where:
Explanation: This is the normal response to the ZBUFC STATUS command when the ZBUFC function determines that a record caching device is attached to a 3880 Record Cache Control Unit.
The SS STATUS field in the display is an 8-bit field. Bits 0 and 1 have the following meanings:
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0004I | STATUS FOR DEVICE -- dddd RCS SSID -- ssss |
Where:
Explanation: This is the normal response to the ZBUFC STATUS command when the ZBUFC function determines that the record caching device is attached to a 3990 Record Cache Subsystem Control Unit.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command and for an example of the informational display. See TPF Database Reference for more information about record caching.
BUFC0005I | RCS GLOBAL STATUS DISPLAY |
Explanation: This is the normal response to the ZBUFC STATUS RCS command. Following this message is a display that contains data obtained from the 3990 record cache subsystem status table header.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command and for an example of the informational display. See TPF Database Reference for more information about record caching.
BUFC0006I | SCAN COMPLETED FOR CHANNEL xxx |
Where:
Explanation: The ZBUFC ALLOCATE IMPLEMNT request completed initializing all 3880 Record Cache Control Units on the specified channel.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0007I | NO CACHE RC DEVICE FOUND ON CHANNEL xxx |
Where:
Explanation: The ZBUFC ALLOCATE IMPLEMNT request completed scanning the specified channel and did not find any 3880 Record Cache Control Units in use on the channel.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0008E | INITIALIZATION FAILED FOR RC DEVICE dddd |
Where:
Explanation: A new ratio value or a new buffer value was specified for the 3880 Record Cache Control Units. However, the program found an error while trying to initialize device dddd with these new values.
System Action: Device dddd continues to run with the old values or in direct mode. The program continues with the next device.
User Response: See your system support personnel if corrective action is required.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0009E | INITIALIZATION TIMED OUT FOR RC DEVICE dddd |
Where:
Explanation: A new ratio value or a new buffer value was specified for the 3880 Record Cache Control Units. However, the initialization input/output (I/O) request for the control unit for device dddd did not complete within 3 minutes.
System Action: The program continues with the next control unit on the channel.
User Response: See your system support personnel if corrective action is required.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0011I | RCS DEVICE I/O QUEUE THRESHLD VALUE -- nnnnn |
Where:
If you did not specify a value for the queue depth in the command, then the queue depth referenced in this message represents the current threshold value.
Explanation: This is the normal response to the ZBUFC THRESHLD command. The value of the queue depth is used to compute overall I/O queue threshold value for the 3990 Record Cache Subsystem. This overall value is then used to monitor the device I/O queues whenever the subsystem is operating in a degraded state.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0012I | DEVICE dddd ATTACHED TO RCS SSID ssss |
Where:
Explanation: This is the normal response to the ZBUFC MAP DEVICE command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0013I | ATTACHED DEVICE RANGE(S) FOR RCS SSID ssss |
Where:
Explanation: This is the normal response to the ZBUFC MAP command. Following this message is a display of the device ranges associated with 3990 Record Cache Subsystem referenced in the message.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0014I | PINNED TRACK REPORT FOR DEVICE dddd ON RCS SSID ssss |
Where:
Explanation: This is the normal response to the ZBUFC PINNED DISPLAY command. Pinned data is reported by the track address (CCCCHHHH) and includes a description of the type of pinned data that exists.
If a starting track address was not specified in the input message, the report begins with the track address CCCCHHHH=0.
Up to eight track addresses can be displayed with each report. Since additional pinned data tracks may exist beyond the last track address displayed in the report, the last address is marked with two asterisks (**) and the following message is appended to the display:
MORE PINNED DATA TRACKS EXIST USE (**) CCCCHHHH FOR NEXT REQUEST
In this case, you may specify this starting address in a subsequent ZBUFC PINNED DISPLAY command to get the next eight pinned track addresses.
The END OF RCS PINNED DATA REPORT message is appended to the display to indicate the end of the report.
The NO PINNED DATA TRACKS REPORTED message is appended to the header if no pinned data tracks exist for the specified device.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command and an example of the informational display. See TPF Database Reference for more information about record caching.
Also see the IBM 3990 Transaction Processing Facility Support RPQs for a description of the pinned track data report.
BUFC0035E | UNABLE TO WRITE KEYPOINT 0 |
Explanation: The ZBUFC command found an error while trying to file the new current and target ratios in keypoint 0. The error occurred while processing the ZBUFC ALLOCATE IMPLEMNT command.
System Action: The request is exited.
User Response: See your system support personnel to report this error.
See TPF Operations for more information about the ZBUFC ALLOCATE IMPLEMNT command. See TPF Database Reference for more information about record caching.
BUFC0036E | ERROR FILING RCS SSST |
Explanation: The ZBUFC command found an error while trying to file the new current and target ratios in the record cache subsystem status table. The error occurred while processing the ZBUFC ALLOCATE IMPLEMNT command.
System Action: The request is exited.
User Response: See your system support personnel to report this error.
See TPF Operations for more information about the ZBUFC ALLOCATE IMPLEMNT command. See TPF Database Reference for more information about record caching.
BUFC0037I | ALLOCATE -- CACHE ALLOCATION PENDING |
Explanation: This is the normal response to the ZBUFC ALLOCATE command. It indicates one of the following:
The allocation values you specify are not applied until you enter the ZBUFC ALLOCATE IMPLEMNT command for the specified control units.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC ALLOCATE command. See TPF Database Reference for more information about record caching.
BUFC0038I | ALLOCATE -- RC CACHE ALLOCATION COMPLETE |
Explanation: This is the normal response to the ZBUFC ALLOCATE IMPLEMNT command for the 3880 Record Cache control units in the TPF system.
If you specified the ALL option on this command, BUFC0039I accompanies this message.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0039I | ALLOCATE -- RCS CACHE ALLOCATION COMPLETE |
Explanation: This is the normal response to the ZBUFC ALLOCATE IMPLEMNT command for the 3990 Record Cache Subsystem control units in the TPF system
If you specified the ALL option on the command, BUFC0038I accompanies this message.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC ALLOCATE IMPLEMNT command. See TPF Database Reference for more information about record caching.
BUFC0040W | RC IMPLEMENT CURRENTLY IN PROGRESS |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC ALLOCATE command while a ZBUFC ALLOCATE IMPLEMNT command is being processed for the 3880 Record Cache control units in the TPF system.
System Action: The request is exited.
User Response: Wait until the ZBUFC ALLOCATE IMPLEMNT command is processed and then enter the ZBUFC ALLOCATE command again, if required.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0041W | RCS IMPLEMENT CURRENTLY IN PROGRESS |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC ALLOCATE command while a ZBUFC ALLOCATE IMPLEMNT command is being processed for the 3990 Record Cache Subsystem control units in the TPF system.
System Action: The request is exited.
User Response: Wait until the ZBUFC ALLOCATE IMPLEMNT command is processed and then enter the ZBUFC ALLOCATE command again, if required.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0042I | ZBUFC FILE RCS SSID ssss COMPLETE |
Where:
Explanation: This is the normal response to the ZBUFC FILE command. The 3990 Record Cache Subsystem SSID, which is referenced in the message, is associated with the device referenced in the message. This device is disabled for cache and DASD fast-write functions. Any modified data in the record cache subsystem (RCS) is destaged to the DASD surface for all attached devices associated ssss.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC FILE command. See TPF Database Reference for more information about record caching.
BUFC0043I | ZBUFC FILE ALL COMPLETE |
Explanation: This is the normal response to the ZBUFC FILE command. Cache and DASD fast-write functions are disabled for all 3990 Record Cache Subsystems currently active in the system. Any modified data in the record cache subsystem (RCS) complex is destaged to the DASD surface for all attached devices.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC FILE command. See TPF Database Reference for more information about record caching.
BUFC0044I | ZBUFC ENABLE RCS SSID ssss COMPLETE |
Where:
Explanation: This is the normal response to the ZBUFC ENABLE command. The 3990 Record Cache Subsystem that is referenced in the message and all attached devices are enabled for full record caching capability, including cache and DASD fast-write functions.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC ENABLE command. See TPF Database Reference for more information about record caching.
BUFC0045I | ZBUFC ENABLE ALL COMPLETE |
Explanation: This is the normal response to the ZBUFC ENABLE command. All 3990 Record Cache Subsystems and attached devices are enabled for full record caching capability, including cache and DASD fast-write functions.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC ENABLE command. See TPF Database Reference for more information about record caching.
BUFC0046I | RCS SHUTDOWN STARTED |
Explanation: This is the normal response to the ZPSMS PR DEACTIVATE command entered on the last active TPF processor when any 3990 Record Cache Subsystems are configured. Any modified data in the record cache subsystem (RCS) complex is destaged to the DASD surface for all attached devices. The BUFC0047I message is issued when this process is completed.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZPSMS command. See TPF Database Reference for more information about record caching.
BUFC0047I | RCS SHUTDOWN COMPLETED |
Explanation: A record cache subsystem (RCS) shutdown operation, which started as a result of a ZPSMS PR DEACTIVATE command, completed. (See the BUFC0046I message.)
System Action: None.
User Response: None.
See TPF Operations for more information about the ZPSMS command. See TPF Database Reference for more information about record caching.
BUFC0048E | BUFC REQUEST NOT VALID AT THIS TIME |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC command during a general file initial program load (IPL) or before the record cache subsystem (RCS) restart function is completed.
System Action: The request is exited.
User Response: Do the following:
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0049E | BUFC REQUEST ONLY VALID FROM THE BSS |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC command from a TPF subsystem other than the basic subsystem (BSS).
System Action: The request is exited.
User Response: Enter the ZBUFC command again from the BSS.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0050E | DEVICE ADDRESS IS NOT A CACHING DEVICE OR IS INVALID |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC command with a device address that is not valid or one that is not attached to any record caching control unit.
System Action: The request is exited.
User Response: Enter the ZBUFC command again with a valid device address.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0051E | BUFC UTILITY NOT OWNED BY THIS PROCESSOR |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC FILE, ENABLE or IMPLEMNT command from a processor in a loosely coupled TPF system and the processor does not currently own the BUFC utility.
System Action: The ZBUFC command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZPROT commands. See TPF Database Reference for more information about record caching.
BUFC0052E | RCS TRACK RATIO VALUE OUTSIDE ACCEPTABLE RANGE |
Explanation: The value specified for the RCSBUF parameter in the ZBUFC ALLOCATE command is not within the 5 to 25 percent range.
System Action: The request is exited.
User Response: Enter the command again and specify a cache allocation value ranging from 5 to 25 percent for the track slot value.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0053E | UNABLE TO READ KEYPOINT 0 |
Explanation: An unrecoverable error occurred while trying to read keypoint 0 to store the new ratio or buffer values.
System Action: The request is exited.
User Response: See your system support personnel to report this error.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0054E | INPUT NON NUMERIC OR INVALID |
Explanation: You specified a value that is not valid on a ZBUFC command request.
System Action: The request is exited.
User Response: Enter the command again with valid values.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0055E | RC RATIO VALUE IS ZERO |
Explanation: One of the allocation ratios specified in the ZBUFC ALLOCATE command is equal to 0.
System Action: The request is exited.
User Response: Enter the command again and specify allocation ratios in the range 1 to 255 for record slots and 1 to 16 for track slots.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0056E | INVALID ZBUFC COMMAND REQUEST ENTER: ZBUFC ? OR ZBUFC HELP FOR MESSAGE FORMAT |
Explanation: You entered a ZBUFC command that is not valid.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0057E | I/O ERROR ENCOUNTERED ON DEVICE dddd |
Where:
Explanation: A hardware error occurred when a ZBUFC command was entered to a 3880 Record Cache Control Unit.
System Action: The request is exited.
User Response: Enter the ZBUFC command again. If the error continues, notify your IBM service representative.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0058E | RCS RATIO VALUE EXCEEDS MAXIMUM |
Explanation: One of the allocation values specified in the ZBUFC ALLOCATE command exceeds the maximum percentage allowed.
System Action: The request is exited.
User Response: Enter the command again with the correct allocation ratios.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0059I | CACHE RECOVERY REQUEST INITIATED ON DEVICE dddd RCS SSID ssss |
Where:
Explanation: This is the normal response to the ZBUFC PINNED DISCARD or the ZBUFC SETCACHE command request used for record cache subsystem (RCS) cache error recovery operations. (Optionally, 3990 Record Cache Subsystem state change messages may be reported by the CYEA segment when the reporting function is enabled.)
System Action: None.
User Response: None.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0060E | TOTAL ALLOCATION NOT 100 PERCENT |
Explanation: The total percentage for all slot allocations specified in the ZBUFC ALLOCATE command is not equal to 100.
System Action: The request is exited.
User Response: Enter the request again with slot allocation values that add up to exactly 100 percent.
See TPF Operations for more information about the ZBUFC ALLOCATE command. See TPF Database Reference for more information about record caching.
BUFC0061I | BUFC UTILITY OPERATION(S) STARTED TO SSID ssss |
Where:
Explanation: One of the ZBUFC commands (FILE, ENABLE, or IMPLEMNT) started input/output (I/O) operations to the 3990 Record Cache Subsystem SSID referenced in the message.
System Action: The ZBUFC function is continued.
User Response: None.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0062E | ALLOCATE INIT OPTION NOT VALID AT THIS TIME |
Explanation: You specified the INIT parameter for the ZBUFC ALLOCATE command under one of the following conditions:
System Action: The ZBUFC command is rejected.
User Response: You cannot enter the command again unless the TPF system is in restart and the CSS00020A output message is displayed.
If the TPF system is not in restart, enter the ZBUFC ALLOCATE command (without the INIT parameter).
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0063E | I/O ERROR ENCOUNTERED FOR DEVICE dddd ON RCS SSID ssss |
Where:
Explanation: A hardware error occurred while trying to issue input/output (I/O) to a 3990 Record Cache Subsystem Control Unit through a ZBUFC command.
System Action: The request is exited.
User Response: Try the request again. If the error continues, see your IBM service representative.
See TPF Operations for more information about the ZBUFC command. See TPF Database Reference for more information about record caching.
BUFC0064E | BUFC UTILITY CURRENTLY ACTIVE |
Explanation: This message is issued if:
System Action: The request is exited.
User Response: Enter the ZBUFC command again when the currently active ZBUFC function is completed.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0065E | RCS SUBSYSTEM(S) NOT DISABLED |
Explanation: The ZBUFC function issues this message when you enter a ZBUFC ALLOCATE IMPLEMNT command but a subsystem ID (SSID) entry in the 3990 record cache subsystem status table (SSST) indicates that a fast-write disable request was not issued to it through a ZBUFC FILE command request.
System Action: The request is exited.
User Response: Do the following:
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0066E | DESTAGE MAY BE INCOMPLETE FOR RCS SSID ssss |
Where:
Explanation: A ZBUFC FILE command is requested but the destage of a 3990 Record Cache Subsystem did not complete successfully. This message may also occur during record cache subsystem (RCS) shutdown as the result of a ZPSMS PR DEACTIVATE command request.
System Action: Processing is continued.
User Response: Display the status of the associated RCS subsystem ID (SSID) to determine whether pinned data exists.
If pinned data exists, enter the ZBUFC PINNED DISPLAY command to determine the extent of the pinned data for the attached devices.
Also see the IBM 3990 Transaction Processing Facility Support RPQs for a description of pinned data.
BUFC0067E | FUNCTION NOT SUPPORTED FOR THIS CONTROL UNIT |
Explanation: This message occurs when a ZBUFC command is entered to a device that is not a valid 3990 Record Cache Subsystem attached device.
System Action: The request is exited.
User Response: Enter the ZBUFC command again to a valid 3990 Record Cache Subsystem device.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0068E | NO REAL-TIME MODS ATTACHED TO RCS CONTROL UNIT |
Explanation: A ZBUFC command was entered for a device associated with a 3990 Record Cache Subsystem subsystem ID (SSID) that has no real-time modules attached.
System Action: The request is exited.
User Response: Enter the ZBUFC command again, if required, to a device associated with a 3990 Record Cache Subsystem that has real-time modules attached.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0069E | ZBUFC FUNCTION COMPLETED WITH ERRORS |
Explanation: A ZBUFC function completed with prior errors found.
System Action: The request is exited.
User Response: Note any related error conditions and see your system support personnel to report the error.
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0070W | NO RCS SUBSYSTEM(S) CONFIGURED |
Explanation: A ZBUFC command request was entered requiring access to a 3990 Record Caching Subsystem but no 3990 Record Cache Subsystems are currently configured in the TPF system.
System Action: The ZBUFC command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZBUFC commands. See TPF Database Reference for more information about record caching.
BUFC0071W | LOCKS PARAMETER IGNORED FOR NON-L/C SYSTEM |
Explanation: A ZBUFC ALLOCATE command request was entered with the LOCKS parameter specified but the TPF system is not using DASD locking because it was generated without the SDPS feature.
System Action: The LOCKS parameter is ignored and processing of the request is continued.
User Response: None.
See TPF Operations for more information about the ZBUFC ALLOCATE command. See TPF Database Reference for more information about record caching.
BWRA0001E | FACE ERROR - faceid / ordnum |
Where:
Explanation: During recoup processing, an error condition was detected by a FACE-type call while trying to retrieve a record.
System Action: Recoup processing continues.
User Response: Determine the cause of the problem.
See TPF System Macros and TPF Application Programming for more information about the file address compute (FACE) program and the FACE interface.
BWRA0400E | SELECTIVE CHAIN CHASE REQUIRED FOR: IDrecid VSN vsn /FILEADDR faddr originid |
Where:
Explanation: Recoup processing detected a timeout error while chain chasing a record.
System Action: Recoup processing fails for this record but continues chain chasing the next record.
User Response: Do the following:
See TPF Operations for more information about the ZRECP DISPLAY command. See TPF Database Reference for more information about selective recoup processing.
BWRA0402W | RECOUP HANG IN BPM1 AUTO PAUSE INITIATED originid |
Where:
Explanation: Recoup has detected a hung condition and internally pauses until the currently active entry control blocks (ECBs) are completed.
System Action: Recoup pauses.
User Response: None.
BWRA0403I | AUTO PAUSE COMPLETE-RECOUP WILL RESUME originid |
Where:
Explanation: A hung condition in recoup has cleared and recoup processing resumes.
System Action: None.
User Response: None.
BWRA0501E | LAST 8 FINDS: faddrfaddr faddrfaddr faddrfaddr faddrfaddr originid |
Where:
Explanation: Recoup processing detected a timeout error while chain chasing a record and displays the file addresses of the last eight timeout errors to assist in problem determination.
System Action: Recoup processing fails for this record but continues chain chasing the next record.
User Response: Do the following:
See TPF Operations for more information about the ZRECP DISPLAY command.
BWRF0001I | DISPLAY PROCESSING STARTED |
Explanation: This is the normal response to the ZRECP DISPLAY command with the REFFROM-FARF parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZRECP DISPLAY command.
BWRF0002I | FROM ID SEEK ID COUNT |
Explanation: This is the normal response to the ZRECP DISPLAY command with the REFFROM-FARF parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZRECP DISPLAY command.
BWRF0007E | SRM61A8 FACE ERROR - ABORTED |
Explanation: The ZRECP DISPLAY command was entered with the REFFROM-FARF parameter specified, but a FACE-type error occurred.
System Action: The command fails.
User Response: None.
See TPF Operations for more information about the ZRECP DISPLAY command.
BWRF0008E | SRM61A8 FIND ERROR - ABORTED |
Explanation: The ZRECP DISPLAY command was entered with the REFFROM-FARF parameter specified, but a FIND-type error occurred.
System Action: The command fails.
User Response: None.
See TPF Operations for more information about the ZRECP DISPLAY command.
BWRF0009E | NOT VALID WITHOUT TPFDF INSTALLED |
Explanation: The ZRECP DISPLAY command was entered with the REFFROM-FARF parameter specified, but TPFDF is not installed.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZRECP DISPLAY command.
BXAR0001A | FCAP RESTRT REQ'D |
Explanation: The capture function was active before the TPF system was IPLed and must be functionally restarted to continue the process.
System Action: None.
User Response: None.
See TPF Database Reference for more information about the capture and restore utility.
BXAR0002A | FRST RESTRT REQ'D |
Explanation: The restore function was active before the TPF system was IPLed and must be functionally restarted to continue the process.
System Action: None.
User Response: None.
See TPF Database Reference for more information about the capture and restore utility.
BXAR0003E | CAP/RST KYPT RD ERR. - NO RESTRT |
Explanation: The working copy of the capture and restore utility keypoint keypoint cannot be accessed from file. The functions included in the capture and restore utility were not restarted.
User Response: Determine the cause of the DDCT read error and correct it.
See TPF Database Reference for more information about the capture and restore utility.
BXAR0004E | CAP/RST DDCT RD ERR. -- NO RESTRT |
Explanation: The DDCT, a logical extension of the capture and restore utility keypoint, cannot be accessed from file. The functions included in the capture and restore utility were not restarted.
System Action: None.
User Response: Determine the cause of the DDCT read error and correct it.
See TPF Database Reference for more information about the capture and restore utility.
BXAR0006E | CAP/RST KYPT, DDCT SYNC FIELDS UNEQUAL NO RESTRT |
Explanation: The synchronization fields that are maintained in the capture and restore utility keypoint and the DDCT, a logical extension of the keypoint, are not equal. This indicates that on a keypoint update request both records did not get filed before the TPF system was IPLed again.
System Action: None.
User Response: Your system programmer should determine the cause of the error and correct it.
One safe method you can use to respond is to initialize the capture and restore utility keypoint again, dismount all associated tapes, and start all functions that were active.
See TPF Database Reference for more information about the capture and restore utility.
BXAR0007A | START XCP RECORDING |
Explanation: While this processor was down, the capture function was started on another processor. In order to have a complete capture of the TPF system, exception recording must be started in this processor.
System Action: The cycle up is suspended until exception recording is started.
User Response: Start exception recording on this processor.
See TPF Database Reference for more information about the capture and restore utility.
BXAR0008E | INVALID DEVICE TYPE |
Explanation: While setting up the keypoint parameters for the various device types, the restart program detected a device type that is no longer supported. The functions included in the capture and restore utility were not restarted.
User Response: Do the following:
See TPF Database Reference for more information about the capture and restore utility.
BXAR0009A | START LOGGING |
Explanation: While this processor was down, the logging function was started on another processor. In order to have a complete logging file for the TPF system, recording logging must be started on this processor.
System Action: None.
User Response: None.
See TPF Database Reference for more information about the capture and restore utility.
B0P00001E | UNABLE TO COMPLY - NO PSEUDO DIRECTORIES AVAILABLE |
Explanation: The ZRECP FLUSH or ZRECP START command was entered specifying the PROC parameter, but the specified processor has no pseudo directories available.
System Action: Recoup processing ends.
User Response: Do the following:
See TPF Operations for more information about the ZRECP FLUSH and ZRECP START commands.
B0P00002E | UNABLE TO COMPLY - PSEUDO DIRECTORIES NOT YET INITIALIZED FOR REQUESTED PROCESSOR |
Explanation: The ZRECP FLUSH or ZRECP START command was entered specifying the PROC parameter, but no pseudo directories for the specified processor have been initialized.
System Action: Recoup processing ends.
User Response: Do the following:
See TPF Operations for more information about the ZRECP FLUSH and ZRECP START commands.
B0P00003I | ZRECP FLUSH HAS BEEN SENT TO PROCESSOR - cpuid |
Where:
Explanation: This is the normal response to the ZRECP FLUSH or ZRECP START command specifying the PROC parameter, indicating that the command has been sent to the specified processor.
System Action: None.
User Response: None.
B0P00004I | ZRECP FLUSH COMPLETE |
Explanation: This is the normal response to the ZRECP FLUSH command.
System Action: None.
User Response: None.
B0P00005E | UNABLE TO COMPLY - NO ID TABLE RECORDS AVAILABLE FOR PROCESSOR cpuid |
Where:
Explanation: The ZRECP START command was entered specifying the PROC parameter, but there are no ID table records available for the requested processor.
System Action: Recoup processing ends.
User Response: Do the following:
See TPF Operations for more information about the ZRECP START command.
B0P00006E | ONLY FIRST 8 PROCESSORS IN THE COMPLEX MAY PARTICIPATE IN RECOUP |
Explanation: When entering the ZRECP PROCEED command, only one of the first eight processors in the loosely coupled complex may be specified, and only the first eight processors can particpate in a recoup run.
System Action: The ZRECP PROCEED command is rejected.
User Response: Enter the ZRECP PROCEED command again specifying one of the first eight processors in the complex.
See the TPF Operations for more information about the ZRECP PROCEED command.