gtpm4m19 | Messages (System Error and Offline) |
Program: Displayed on the console and in the dump
Error Message: CORE DUMP REQUESTED
Explanation: A core dump was requested by the user of the current test unit.
System Action: A full core dump is issued after the end of the affected test unit (the result of the CDMP PTV option).
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: LINE NUMBER NOT FOUND IN SIMULATED LINE TABLE
Explanation: An input message that is not valid was found on the input tape (TUT). The line number is not in the Program Test Vehicle (PTV) simulated line table.
System Action: A SNAPC dump is issued with a return option and bypasses the message.
User Response: Do the following:
Program: Displayed on the console and in the dump
Error Message: INVALID MESSAGE BLOCK SIZE ON TUT
Explanation: The input block from the system test compiler (STC) is larger than the system-generated buffer size.
System Action: A system error dump is issued and the program is exited.
User Response: Load the TPF system again.
Program: CRTT/CCUTIL
Error Message: RTT CORE DEPLETION EXISTS
Explanation: During a trace, the real-time trace (RTT) facility found that the core frame levels in the TPF system are depleted.
System Action: The trace data is no longer collected. CXFRC is done to activate ZSTOP processing.
User Response: Verify whether the problem is due to RTT alone or whether there is any other problem in the TPF system that results in depleted core frames.
If RTT is causing the problem, consider reducing the rate of output using additional options on the RTT start message.
See TPF Program Development Support Reference for more information about RTT.
Program: BMD1
Error Message: CORE DEPLECTED DURING SFT/SFD RECORD DUMPING
Explanation: While writing records to tape for selective file dump/selective file trace (SFD/SFT), a core frame depletion condition was detected.
System Action: Writing the requested records to tape is aborted. An SFT stop message or an SFD complete message is sent after this dump and then the TPF system is exited.
User Response: Determine whether too many records were requested for SFD/SFT. This condition occurs mainly with SFD.
Program: Displayed on the console and in the dump.
Error Message: BACKWARD TAPE READ ERROR ON DATA BASE RESTORE TAPE
Explanation: A backward tape read error occurred on the database restore tape.
System Action: The record is bypassed and the next record on the database restore tape is processed.
User Response: Check for a possible hardware malfunction.
Program: Displayed on the console and in the dump
Error Message: ERROR IN FILING DATA RECORD
Explanation: There was an error in filing a data record to a database restore tape.
System Action: The record is bypassed and the next record is processed.
User Response: Check for a possible hardware malfunction.
Program: Displayed on the console and in the dump.
Error Message: MSG TOO SMALL, TEST UNIT TERMINATED
Explanation: The input message read from the input tape is too short to be a valid message.
System Action: The test unit ends and the TPF system is IPLed again.
User Response: Do the following:
Program: PTVE
Error Message: SUBSYSTEM USER NOT AVAILABLE
Explanation: The subsystem user is not active.
System Action: A catastrophic system error is issued and the TPF system is IPLed again.
User Response: None.
Program: JPTV
Error Message: ERROR WRITING PTV OUTPUT, RTL NOT AVAILABLE
Explanation: An error occurred while writing the program test vehicle (PTV) output. The real-time (RTL) tape is not available.
System Action: A system error dump is issued with the return option. Tape write is bypassed.
User Response: Do the following:
Program: PTVG
Error Message: ERROR READING TUT, PTV ABORTED
Explanation: During program test vehicle (PTV) initialization, an error occurred while reading the test unit tape (TUT).
System Action: PTV processing is ended.
User Response: Do the following:
Program:
Error Message: PROGRAM LOADS NO SUPPORTED
Explanation: The test unit tape (TUT) may be back level.
System Action: Program test vehicle (PTV) process is bypassed.
User Response: Do the following:
Program: PTVG
Error Message: Test unit tape (TUT) input following the current RUNID contains no messages.
Explanation: There are no messages on the tape after RUNID.
System Action: The test unit is ended and the TPF system is IPLed.
User Response: Check to be sure that correct tape is being used.
See TPF Program Development Support Reference for more information.
Program: BMD0
Error Message: None.
Explanation: BMD0 builds a table of validated file addresses for selective file dump and trace (SFDT) processing and maintains a counter of the number of entries in that table. This error indicates that the counter is zero upon completion of the table build process. Normally, a file address that is not valid is reported to the operator and the ECB is exited prior to testing the counter. Therefore, either the counter was corrupted or a logic error occurred.
System Action: An system error is issued and the ECB is exited.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: CTSF/CCUTIL
Error Message: SFT log buffer write error. Tape not mounted or offline.
Explanation: The selective file dump and trace (SFDT) function is unable to write the filled log buffer to the real-time (RTL) tape because the tape is not mounted or the tape is offline.
System Action: The SFDT function is continued. New log information is not collected and is lost until the tape is mounted and the filled buffer is written to tape.
User Response: Do one of the following:
See TPF Operations for more information about the ZTHLT command.
Program: BMD0, BMD5
Error Message: None.
Explanation: An error occurred because the number of records in the input message exceeded the maximum allowed by the TPF system. The number of records may not exceed 82 for a type A address format and 420 for type N and S address formats.
System Action: The entry is exited.
User Response: Enter the message again and specify a valid number of records.
Program: PTVC
Error Message: None.
Explanation: The test unit tape (TUT) has an improper RUNID header.
System Action: Exit the ECB.
User Response: Check the input tape and verify the RUNID.
Program: PTV3
Error Message: UNABLE TO FIND PTVA KEYPOINT
Explanation: The PTV3 program tried to retrieve the program test vehicle (PTV) keypoint and was unable to do so.
System Action: A catastrophic system error is issued and the TPF system is IPLed again.
User Response: Do the following:
Program: PTV4
Error Message: UNABLE TO FILE PTVA KEYPOINT
Explanation: The PTV4 program tried to write to DASD and was unable to do so.
System Action: A catastrophic system error is issued and the TPF system is IPLed again.
User Response: Do the following:
Program: PTVH
Error Message: None.
Explanation: An error occurred during a reading of the test unit tape (TUT) while the program test vehicle (PTV) program was running.
System Action: PTV processing is ended.
User Response: Have your system programmer review the system error dump to determine cause of the error and to correct it.
Program: PTV3
Error Message: FACE ERROR ON PTVA KEYPOINT
Explanation: A file address compute program (FACE) error occurred on the PTVA keypoint.
System Action: A catastrophic system error is issued, except during restart.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: PTVR
Error Message: None.
Explanation: There are no active program test vehicle (PTV) entries in the MIP table.
System Action: The entry control block (ECB) is exited and the PTV is aborted.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.