Dumps

TPF Database Facility
Messages (System Error, Online, Offline)

Release 1
BDFM-1MST-16
ii
TPFDF Messages (System Error, Online, Offline)
Contents
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Guidelines . . . . . . . . . . . . Types of Messages. . . . . . . . . System Errors. . . . . . . . . . . Analyze a System Error . . . . . . Example of System Errors . . . . . Online and Offline Messages . . . . . Message Formats . . . . . . . . Locate an Online or Offline Message . Analyze an Online or Offline Message . Standard Message Example . . . . Non-Standard Message Example . . System Errors . . 0000000FFFFF . . 1000001FFFFF . DB0000DB9999 . DBA000DBFFFF . F00000FFFFFF . Online Messages . BGAC . . . . . BGAD . . . . . BGAE . . . . . BGAH . . . . . BGAK . . . . . BGAO . . . . . BGA3 . . . . . BGA5 . . . . . BGA7 . . . . . FCRU . . . . . RECP . . . . . UDFC . . . . . UDFM . . . . . UFB7 . . . . . UFDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 1 2 2 2 3 4 5 5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 7 . . 7 . . 12 . . 14 . . 38 . . 50 . . . . . . . . . . . . . .
. 51 . 51 . 51 . 51 . 52 . 52 . 52 . 53 . 53 . 53 . 54 . 81 . 91 . 99 . . . . . . . . . . . . . . . . . . . . . . . 129 . . . . . . . . . . . . . . . . . . . . . . . 129
Offline Messages . . . . . . . . . . . . . . . . . . . . . . . 131 UFOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Copyright IBM Corp. 2002, 2009
iii
iv
Tables
1. 2. 3. Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Format of a Standard Message . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Format of a Non-Standard Message . . . . . . . . . . . . . . . . . . . . . . . . 3
vi
Guidelines
Use the following guidelines to better understand the different types of messages that can occur while using the TPF Database Facility (TPFDF) product.
Types of Messages
The TPF Database Facility (TPFDF) product issues the following types of messages: v System errors v Online v Offline. See TPF Messages (System Error, Offline, and Program Status Word) and TPF Messages (Online) for information about messages that are issued by the TPF system. See ALCS Messages and Codes for information about messages that are issued by the ALCS environment. Note: ALCS is also referred to as TPF/MVS.
System Errors
System error messages are sent by the SERRC system error macro and are accompanied by a dump and possibly a system shutdown. The TPFDF product issues these messages while running in an IBM Transaction Processing Facility (TPF) environment or an IBM Airline Control System (ALCS) environment.
Analyze a System Error

Once you locate the system error message, you will notice that the system error number is framed in a box for quick access. Below each system error message you will find the following information to help you analyze the message. v Program Indicates the name of the program that found the error when that program is not available to the TPFDF product for display on the console and in the dump. v Error Message Provides the text of the system error message that is displayed on your screen and printed in the dump, if there is any. If there are supplementary messages appearing in the dump, you will find more than one error message for each system error message.In the message text, variable information is shown in italicized lowercase letters. When a system error actually occurs, specific information is provided for the variable information in the message that is displayed on your screen or printed in the dump. Explanations of the variable information are described immediately following the message text. If there is no error message text, the word None is printed. v Explanation Provides a brief description of the error conditions and the reason why an error occurred. A description of any variable information that is included in the message text may also be included in this explanation. If there is no explanation necessary, the word None is printed. v System Action
Indicates the action taken by the TPFDF product, TPF system, or ALCS environment as a result of the error and provides an explanation that indicates the results of the error. If there is no system action taken, the word None is printed. v User Response Provides suggestions for a user action to correct the problem. Bulleted lists and numbered lists may be used to present this information to you. A bulleted list is used to present several different actions you can perform to resolve the problem. These actions are ordered from the least severe to the most severe. A numbered list is used whenever you must follow a procedure in sequential order to resolve a problem. If there is no user response necessary, the word None is printed. The user responses are suggestions. Verify any action with your system support personnel first.
Example of System Errors

The following is an example of how system error messages and their associated information are presented.
000820 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when a data level specified with a DFSSU macro already has a block attached. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Modify the program that caused the error to use a different data level on the DFSSU macro. v Release the block that is attached to the data level before the DFSSU macro call.
Online and Offline Messages

Online messages and offline messages result from less severe conditions than system error messages, can originate from online or offline processes, and are not normally accompanied by dumps. Like system error messages, online messages are issued by the TPFDF product when running in a TPF system or in an ALCS environment, while offline messages occur in programs under IBM MVS control. The severity of the error determines whether a message is a system error message or an online message. Online messages are usually those issued by a TPFDF utility, such as TPFDF data collection (ZUDFC).
Message Formats
When you see an online or offline message on your screen or read it in a dump, you will notice that the message has one of the following formats.
Table 1. Message Format Format ppppnnnnx hh.mm.ss text text Description Message with the standard message ID. Message without the standard message ID.
Standard Messages
Messages with the standard message ID have the following format: ppppnnnnx hh.mm.ss text
When reading from left to right, this format contains the following parts.
Table 2. Format of a Standard Message Part ppppnnnnx Description The standard message ID, which has the following parts: v pppp, which represents the first 4 characters of the segment name or the secondary action code of the associated input message. v nnnn, which represents a unique messae number. v x, which represents one of the following severity codes: I for information only, which indicates the message is a normal response. A for action required, which indicates that additional operator action is required. W for attention, which indicates an error that could require additional user action. E for error, which indicates an error without program shutdown. T for termination, which indicates an error with program shutdown. hh.mm.ss The time stamp, which represents the time that the message was built. When you look up a message, ignore the time stamp. The text of the message.
text
Non-Standard Messages
Messages without the standard message ID are shown with the following format: ttttttttt text When reading from left to right, this format contains the following parts.
Table 3. Format of a Non-Standard Message Part ttttttttt Description The nonstandard message ID that is used for publication purposes only and is represented as 000000000. This message ID is not coded with the message text. The text of the message.
text
Locate an Online or Offline Message

In the top outer corner of each page you will find the range of message IDs listed on that page (for example, UDFC0016E v UDFC0019E). This means that the first online or offline message on the page is UDFC0016E and the last online or offline message on the page is UDFC0019E.
Guidelines
There are two ways to locate an online or offline message depending on whether the message does or does not have the standard message ID.
Standard Messages
If a message has the standard message ID, the message IDs are listed in increasing numeric order preceded by their alphabetic prefix. To find a message with the standard message ID, record the message ID from the message; for example, UDFC0061E. Then, use the first 4 characters of the message ID to locate the section where these messages are listed. Finally, use the remaining numbers and characters that make up the message ID to find the message. In this example, the first 4 characters are UDFC while the remaining numbers and characters are 0061E.
Non-Standard Messages
If a message does not have the standard message ID, the message is listed with a message ID of 000000000 and then presented in alphabetic order based on the initial message text. To find a message without the standard message ID, record the message text from the message; for example, UNABLE TO PROCESS - LOG FILE CORRUPTED. Then, locate the section where the messages with a message ID of 000000000 are listed. Finally, use the message text to find the message.
Analyze an Online or Offline Message

Once you locate a message, you will notice that the message ID and the message text are framed in a box for quick access. In the message text, variable information is shown in italicized lowercase letters. When a message actually occurs, specific information is provided for the variable information in the message that is displayed on your screen or printed in the dump. Explanations of the variable information are described immediately following the message text or in the actual explanation of the message. Below each message you will find the following information to help you analyze the message. v Explanation Provides a brief description of the error conditions and the reason why an error occurred. A description of any variable information that is included in the message text may also be included in this explanation. If there is no explanation necessary, the word None is printed. v System Action Indicates the action taken by the TPFDF product, TPF system, or ALCS environment as a result of the error and provides an explanation indicating the results of the error. If there is no system action taken or the possibilities are too variable, the word None is printed. v User Response Provides suggestions for a user action to correct the problem. Bulleted lists and numbered lists may be used to present this information to you. A bulleted list is used to present several different actions you can perform to resolve the problem. These actions are ordered from the least severe to the most severe. A numbered list is used whenever a procedure must be followed in sequential order to resolve a problem. In addition, cross-references to other messages or other additional
information may be provided if applicable. If there is no user response necessary, the word None is printed.The user responses are suggestions. Verify any action with your system support personnel first.
Standard Message Example

The following is an example of how an online or offline message with a standard message ID and its associated information is presented.
UDFC0061E PROGC ERROR RETRIEVING UF0A/UFA2 PAT ADDRESS
Explanation: Data collection cannot be started because an error occurred while retrieving the program allocation table (PAT) address of UF0A or UFA2. Without this address, data collection cannot determine if these programs are in an active loadset. System Action: Data collection is not started. User Response: Do the following: 1. Verify that these programs are allocated correctly in the subsystem attempting to run data collection. 2. Correct the problem. 3. Enter the ZUDFC START command again. See TPFDF Commands for more information about the ZUDFC START command.
Non-Standard Message Example

The following is an example of how an online or offline message without a standard message ID and its associated information is presented.
000000000 Where: operation The ZFCRU operation. Explanation: An error occurred when you entered a ZFRCRU command because no pool records are available. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Free up additional pool records. 2. Enter the ZFCRU command again. See TPFDF Commands for more information about the ZFCRU commands. ZFCRU- operation IMPOSSIBLE TO EXECUTE - NO POOL AVAILABLE
Guidelines
System Errors
0000000FFFFF
000820 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when a data event control block (DECB) or a data level is specified with a DFSSU macro that already has a block attached. System Action: The DECB or the entry control block (ECB) exits. User Response: Do one of the following: v Modify the program that caused the error to use a different DECB or data level on the DFSSU macro. v Release the block that is attached to the DECB or data level before the DFSSU macro call. 0DF001 Program: Displayed on the console and in the dump. Error Message: CENTRAL DESCRIPTOR CORRUPTION Explanation: TPFDF recoup initialization found that the central descriptor table was corrupted. System Action: Recoup processing is forced to stop before completing. User Response: See your system programmer to correct the problem. 0DF002 Program: Displayed on the console and in the dump. Error Message: FACE ERROR FINDING MPRECP Explanation: Recoup processing attempted to get the file address for the recoup keypoint, but a file address compute (FACE) program error occurred. System Action: Recoup processing is forced to stop before completing. User Response: Check the status of the FACE table (FCTB) to ensure that enough #IBMM4 and #MPRECP records are allocated. 0DF003 Program: Displayed on the console and in the dump. Error Message: TPF RECOUP DID NOT COMPLETE Explanation: TPFDF recoup processing began to start on the primary processor but TPF recoup has not completed. System Action: Recoup processing continues. User Response: See your system programmer to determine why TPFDF recoup processing was initiated on the primary processor before TPF recoup processing was completed. 0DF004 Program: Displayed on the console and in the dump. Error Message: FACE ERROR RETRIEVING RECOUP KEYPOINT Explanation: Recoup processing attempted to get the file address for the recoup keypoint, but a file address compute (FACE) program error occurred. System Action: Recoup processing is forced to stop before completing. User Response: Check the status of the FACE table (FCTB) to ensure that enough #IBMM4 and #MPRECP records are allocated. Program: Displayed on the console and in the dump. Copyright IBM Corp. 2002, 2009
0DF005 0DF008
Error Message: FIND ERROR RETRIEVING RECOUP KEYPOINT! Explanation: Recoup processing attempted to find the recoup keypoint, but the find failed. System Action: Recoup processing is forced to stop before completing. User Response: Examine the dump to determine why the error occurred. Program: Displayed on the console and in the dump. Error Message: ERROR FILING #MPRECP (INVALID @BRCPF ADDRESS Explanation: TPFDF recoup processing attempted to file the recoup keypoint, but when it checked the keypoint file address, the file address was not valid. System Action: Recoup processing is forced to stop before completing. User Response: Determine why the file address in recoup global @BRCPF is no longer valid. This usually occurs because recoup processing is forced to stop before completing. Program: Displayed on the console and in the dump. Error Message: ERROR RETRIEVING FILECOPY OF KEYPOINT Explanation: A ZRECP REPORT command was entered, but the file copy of the recoup keypoint could not be retrieved. System Action: Recoup processing is forced to stop before completing. User Response: Examine the dump to determine why the error occurred. 0DF005 Program: Displayed on the console and in the dump. Error Message: PROCESSOR NOT VALID Explanation: TPFDF recoup processing attempted to send a SIPCC request to a processor that is not participating in the recoup run and is not active. System Action: Recoup processing is forced to stop before completing. User Response: This should not occur. See your system programmer. 0DF006 Program: Displayed on the console and in the dump. Error Message: INVALID RECOUP KEYPOINT Explanation: During completion or initialization of recoup processing on a target processor, the processor keypoint became not valid. System Action: Recoup processing is forced to stop before completing. User Response: Determine why the core address in recoup global @BRCPE is no longer valid. This usually occurs because recoup processing is forced to stop before completing. 0DF007 Program: Displayed on the console and in the dump. Error Message: RECOUP NOT ACTIVE Explanation: During recoup chain chase processing, the core address of the recoup keypoint became not valid. System Action: Recoup processing is forced to stop before completing. User Response: Determine why the core address in recoup global @BRCPE is no longer valid. This usually occurs because recoup processing is forced to stop before completing. 0DF008 Program: Displayed on the console and in the dump. Error Message: RECORD ID TABLE CORRUPTED Explanation: A TPFDF macro failed while trying to access the TPFDF recoup records (#SRMP1A) file.
0DF009 0DF013
System Action: Recoup processing is forced to stop before completing. User Response: Determine why the TPFDF recoup records (#SRMP1A) file could not be accessed. 0DF009 Program: Displayed on the console and in the dump. Error Message: TPFDF - RECP PROCESSOR cpuid ABNORMAL ABORTED. Where: cpuid The processor identifier (ID). Explanation: TPFDF recoup processing was forced to stop on a secondary processor before completing. System Action: Recoup processing continues on other processors, and any records that were in the process of being chain chased will be chain chased on another processor. User Response: Determine why TPFDF recoup processing stopped before completing. 0DF010 Program: Displayed on the console and in the dump. Error Message: INVALID PROCESSOR PASSED TO CONVERT Explanation: A processor ID conversion routine in BGA8 was called incorrectly. System Action: TPFDF recoup processing continues. User Response: Examine the dump to determine why the error occurred. The macro trace will indicate the calling program. 0DF011 Program: Displayed on the console and in the dump. Error Message: REQUESTED PROCESSOR IS NOT ACTIVE Explanation: A processor ID conversion routine in BGA8 was called and the target processor was not active. System Action: TPFDF recoup processing continues. User Response: Examine the dump to determine why the error occurred. The macro trace will indicate the calling program. 0DF012 Program: Displayed on the console and in the dump. Error Message: NOT A VALID PROCESSOR TYPE TO CONVERT TO Explanation: A processor ID conversion routine in segment BGA8 was called incorrectly. System Action: Recoup processing continues. User Response: Examine the dump to determine why the error occurred. The macro trace will indicate the calling program. 0DF013 Program: Displayed on the console and in the dump. Error Message: RECORD ID NOT FOUND Explanation: The ZRECP STOP command was entered specifying the PROC parameter but the entry control block (ECB) could not locate the record ID of the TPFDF file that was being chain chased. System Action: Recoup processing is forced to stop before completing. User Response: See your system programmer to correct the problem. Program: Displayed on the console and in the dump. Error Message: RECORD ID NOT FOUND Explanation: An error occurred while attempting to read from the TPFDF recoup records (#SRMP1A) database. System Errors
0DF014 0DF017
System Action: Recoup processing is forced to stop before completing. User Response: See your system programmer to correct the problem. See TPF Operations for more information about the ZRECP STOP command. 0DF014 Program: Displayed on the console and in the dump. Error Message: RECORD ID DOES NOT MATCH Explanation: The ZRECP STOP command was entered specifying the PROC parameter, or chain chase processing was completing on a TPFDF file, but the logical record (LREC) that was read does not match the LREC that should be completing. System Action: Recoup processing is forced to stop before completing. User Response: See your system programmer to correct the problem. See TPF Operations for more information about the ZRECP STOP command. 0DF015 Program: Displayed on the console and in the dump. Error Message: DBDEF CONTAINS INVALID MPRECD=recid RECORD ID. IGNORED. Where: recid The record ID specified with the MPRECD parameter. Explanation: TPFDF recoup processing found a DBDEF macro statement specifying the MPRECD parameter with an incorrect record ID. System Action: TPFDF recoup processing ignores the MPRECD parameter and continues to run. User Response: Correct the error and load the DBDEF macro statement again. See TPFDF Database Administration for more information about the DBDEF macro. 0DF016 Program: Displayed on the console and in the dump. Error Message: INDICATOR SRMPIND CORRUPTED Explanation: The SRMPIND value in record FDE0 does not match the current DBDEF macro statement that is loaded. Either a different version of the DBDEF macro statement was loaded during recoup, or there is a software problem. System Action: Recoup processing is forced to stop before completing. User Response: See your system programmer. 0DF017 Program: Displayed on the console and in the dump. Error Message: DBDEF CONTAINS INVALID MPRECD=filename TPFDF FILE. IGNORED. Where: filename The name of the TPFDF file specified with the MPRECD parameter. Explanation: TPFDF recoup processing found a DBDEF macro statement specifying the MPRECD parameter with an incorrect TPFDF macro file name. System Action: Recoup processing ignores the MPRECD parameter and continues to run. User Response: Correct the error and load the DBDEF macro statement again. See TPFDF Database Administration for more information about the DBDEF macro.
10
0DF018 0DF022
0DF018 Program: Displayed on the console and in the dump. Error Message: DEAD LOCK SITUATION WITH MPRECD Explanation: An error occurred because of conflicting MPRECD parameter values for a DBDEF macro statement and TPFDF recoup was unable to correct it. System Action: Recoup processing is forced to stop before completing. User Response: Correct the error, load the DBDEF macro statement again, and run recoup processing again. See TPFDF Database Administration for more information about the DBDEF macro. 0DF020 Program: Displayed on the console and in the dump. Error Message: TPFDF - RECP SIPCC TIMEOUT OCCURED. MESSAGE: servroutine Where: servroutine The name of a SIPCC macro service routine. Explanation: Recoup processing attempted to send a SIPCC message that had previously failed to another processor, but the SIPCC message again failed. System Action: Recoup processing continues and sends the SIPCC message again. User Response: Check the status of all processors in the complex and call your system programmer. 0DF021 Program: Displayed on the console and in the dump. Error Message: TPFDF - RECP SIPCC MESSAGE: servroutine IGNORED Where: servroutine The name of a SIPCC macro service routine. Explanation: Recoup processing attempted to send, to another processor, a SIPCC message that had previously failed, but the SIPCC message failed and will not be sent again. System Action: Recoup processing is forced to stop before completing. User Response: Check the status of all processors in the complex and call your system programmer. 0DF022 Program: Displayed on the console and in the dump. Error Message: MPNXTD= ID WAS PROCESSED OR NOT FOUND Explanation: TPFDF recoup processing found a DBDEF macro statement specifying an ID on the MPNXTD parameter that cannot be found or has already been chain chased. System Action: TPFDF recoup processing continues with the next DBDEF macro statement. User Response: Correct the DBDEF macro statement before the next recoup run. See TPFDF Database Administration for more information about the DBDEF macro. Program: Displayed on the console and in the dump. Error Message: MPNXTD= ID CANNOT BE STARTED Explanation: TPFDF recoup processing found a DBDEF macro statement specifying the ID of a file (on the MPNXTD parameter) that cannot start chain chase processing. System Action: Recoup processing continues with the next DBDEF macro statement. User Response: Correct the DBDEF statement of the ID that was targeted to be chain chased before the next recoup run to ensure that it can be chain chased as requested. System Errors
11
0DF023 141300
See TPFDF Database Administration for more information about the DBDEF macro. 0DF023 Program: Displayed on the console and in the dump. Error Message: ERROR ACCESSING SRMP1A DATABASE Explanation: The ZRECP SEL command was entered, but the TPFDF multiprocessor recoup table (file #SRMP1A) was found to be corrupted and recoup processing could not check the table for the record ID being processed. System Action: Recoup processing continues. User Response: Do the following: 1. Determine the cause of the corrupted SRMP1A file. 2. Correct the problem. 3. Enter the ZRECP SEL command again to repeat selective recoup processing. See TPF Operations for more information about the ZRECP SEL command.
1000001FFFFF
11F01B Program: Displayed on the console and in the dump. Error Message: None. Explanation: The format output message segment (MOSG) received an error while attempting to retrieve the prime output message (OMSG) block. System Action: Control returns to the program that called MOSG with an error indicated in register 2. User Response: Examine the dump to determine the type of error that caused the retrieval to fail. 11FFFF Program: Displayed on the console and in the dump. Error Message: None. Explanation: A program called MOSG with a number of characters less than zero. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine the program that called MOSG. 2. Correct the program so it passes control to MOSG with a number of characters greater than zero. 141300 Program: Displayed on the console and in the dump. Error Message: None. Explanation: An entry control block (ECB) is trying to update recoup statistics, but a previous ECB did not release the lock. System Action: The core lock is released and recoup continues to update the statistic. Therefore, the chain counters for the structure that is currently being processed may not be completely accurate. User Response: Do the following: 1. Examine the dump to determine the cause of the error. 2. Run the operation again, if necessary.
12
141302 141361
141302 Program: Displayed on the console and in the dump. Error Message: ID-fileid FVN-version NOT IN DBTAB Where: fileid The file identifier (ID). version The version of the file. Explanation: During recoup, the DBTAB macro failed to locate the database definition (DBDEF) for a referenced ID. System Action: The recoup utility ends. User Response: Do one of the following: v If recoup is required for the referenced file, code a DBDEF macro for the file. v If recoup is not required for the referenced file, remove the file as a referenced ID from all other DBDEFs. 141303 Program: Displayed on the console and in the dump. Error Message: ID-fileid FVN-version NO REC INFO Where: fileid The file identifier (ID). version The version of the file. Explanation: A referenced ID has no recoup information defined in the database definition (DBDEF). System Action: The recoup utility ends. User Response: Do one of the following: v If recoup is required for the referenced file, add recoup information to the DBDEF for the file. v If recoup is not required for the referenced file, remove the file as a referenced ID from all other DBDEFs. 14130B Program: Displayed on the console and in the dump. Error Message: None. Explanation: A recoup item was located past the end of a block. System Action: The recoup utility ends. User Response: Examine the dump to determine why the item was located past the end of the data block. 141361 Program: Displayed on the console and in the dump. Error Message: None. Explanation: One or more subitems were detected outside of the item size. System Action: References outside the length of the item are ignored and processing continues with the next item. User Response: Examine the dump to determine why the subitems were located past the length of the item.
System Errors
13
141362 DB0102
141362 Program: Displayed on the console and in the dump. Error Message: None. Explanation: During TPFDF recoup chain chase processing, the current item position exceeds the block size because the item count value at the count location (CPT=) is not correct. System Action: Recoup processing stops at the maximum number of items and continues with the next block. User Response: Examine the dump and correct the counter value in the subfile.
DB0000DB9999
DB0100 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An error occurred while trying to retrieve a record using the FINWC or FIWHC macros. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. User Response: Examine the dump to determine why the error occurred. DB0101 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A logical record (LREC) was found that contains an incorrect item size. System Action: Control returns to the application program with bit 4 of SW00RTN set to 1. User Response: Examine the dump to determine how the logical record was corrupted. DB0102 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID).
14
DB0104 DB0105
pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An error occurred while calculating the file address of a record using the file address compute program (FACE). System Action: Control returns to the application program with bit 2 of SW00RTN set to 1, which indicates a FACE error. User Response: Examine the dump to determine why the error occurred. This error may indicate that the DSECT macro for the file was not coded correctly. DB0104 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A block was found that contains an incorrect next available byte (NAB). System Action: Control returns to the application program with bit 4 of SW00RTN set to 1. User Response: Examine the dump to determine how the block was corrupted. DB0105 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: The sequence of TPFDF macro or function calls in the application program is not valid. For example, one of the following macros was called without a preceding DBRED macro: v DBADD macro with the AFTER parameter specified v DBADD macro with the BEFORE parameter specified v DBREP macro. System Action: The entry control block (ECB) exits. User Response: Correct the sequence of TPFDF macro or functions calls in the application program.
System Errors
15
DB0106 DB0109
DB0106 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The base of the SW00SR slot was not found in general register 3 (R3). This could be the result of R3 containing an incorrect value, or the SW00SR slot referenced by R3 being corrupt. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine why the base of the SW00SR slot is not in R3. This error may indicate that an application program has corrupted R3 while processing multiple TPFDF macro calls. DB0107 Program: Displayed on the console and in the dump. Error Message: None. Explanation: An error occurred while trying to retrieve a record using the FINWC macro. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine why the error occurred. The file address of the record being retrieved in in the DECB whose address is in field SW00DFS. If the error occurred in segment UWBP (which handles FARF6 migration using a ZFCRU command), the DECB address is in field SW00DFP. See TPFDF Commands for more information about the ZFCRU commands. See TPF General Macros for more information about the FINWC macro. DB0108 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An error occurred while trying to file a record using the FILNC macro. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. User Response: Examine the dump to determine why the error occurred. DB0109 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The maximum number of open (and accessed) files for one entry control block (ECB) was exceeded. System Action: The ECB exits. User Response: Do one of the following: v Verify that the application program is not opening files incorrectly in a loop. v Update the value of variable #TPFDBMO in ACPDBE. See TPFDF Programming Concepts and Reference for more information about how return-optional TPFDF system errors should return control.
16
DB010A DB010C
DB010A Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A database definition (DBDEF) was not found for a file ID. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Create a DBDEF for the file ID. v Update the application program to use another file ID. DB010B Program: Displayed on the console and in the dump. Error Message: None. Explanation: An error was returned while processing a DBDSP macro or dfdsp function. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. In addition, bit 1 of SW00RT2 is set to 1, which indicates a display error. The output message is not displayed. User Response: Examine the dump to determine why the error occurred. DB010C Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: One of the following: v An application program updated a file without specifying the HOLD parameter on the DBOPN macro. v An application program updated a file without specifying the DFOPN_HOLD option on the dfopn function. System Action: The file or subfile is updated and control is returned to the application program. User Response: Do one of the following: v Correct the DBOPN macro or dfopn function in the application program. v Remove the code from the application program that updates the file.
System Errors
17
DB010D DB0110
DB010D Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An incorrect next available byte (NAB) was found while processing a FILNC or FILEC macro. System Action: The block is not filed and control is returned to the application program with bit 4 of SW00RTN set to 1. User Response: Examine the dump to determine how the NAB was corrupted. DB010E Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An ATTAC macro was issued, but no block was found to attach. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine why a block was not available for the ATTAC macro. DB010F Program: Displayed on the console and in the dump. Error Message: None. Explanation: An incorrect logical record (LREC) size or next available byte (NAB) was found. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine how the LREC size or NAB was corrupted. DB0110 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check.
18
DB0111 DB0115
cfaddr The current file address. Explanation: A DBCRE macro or dfcre function was issued, but other TPFDF macros or functions have been issued since the subfile was opened. If a subfile needs to be created, it must be done before any other TPFDF macros or functions are issued. System Action: The entry control block (ECB) exits. User Response: Update the application program so that the subfile is created before any other TPFDF macros or functions are issued. DB0111 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A TPFDF macro or function was issued that requires a tape name, but one of the following occurred: v The application program did not specify a tape name. v An incorrect tape name was specified. v A valid tape name was specified, but the tape is not mounted. This error can occur when using the following: v DBTRD macro v DBTLG macro v DBOPN macro with the TAPE parameter v dftrd function v dftlg function v dfopn function with the tape name parameter. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Ensure the application program is specifying a valid tape name. 2. Verify that the tape is properly mounted before running the application program. DB0112 Program: Displayed on the console and in the dump Error Message: None. Explanation: A program tried to exit with one or more TPFDF files open. System Action: The program is exited. User Response: Update the program so that all TPFDF files are closed before exiting. DB0115 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPFDF macro or function was issued without first opening a subfile using the DBOPN macro or dfopn function. System Action: The entry control block (ECB) exits.
System Errors
19
DB0116 DB0119
User Response: Update the application program so that a subfile is opened before issuing other TPFDF macros or functions. DB0116 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: One of the following: v An incorrect algorithm was specified by symbol &SW00RBV in a DSECT. v An incorrect algorithm was specified by the RBV parameter on a DBDEF macro statement. v User exit UF0G was not updated correctly to implement an installation-specific algorithm. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Update symbol &SW00RBV in the DSECT of the file in error. v Update the RBV parameter on the DBDEF macro statement for the file in error. v Verify that any installation-specific algorithms are implemented correctly in user exit UF0G. DB0117 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: When processing a DBADD macro or dfadd function on a file with default keys defined in the DBDEF macro, the TPFDF product was unable to find the key definition for the logical record (LREC) to be added. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Update the application program so that LRECs are added with a primary key (and a data identifier, if adding an extended LREC) defined in the DBDEF macro. v Update the DBDEF macro to include a default key definition for the primary key (and data identifier, if adding an extended LREC) of the record being added. DB0119 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where:
20
DB011B DB011E
fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: While processing a DBTRD macro or dftrd function, one of the following occurred: v A block was read from the input tape with a different size than the size indicated in the DSECT or DBDEF macro for the file in error. v An I/O error was indicated while reading the input tape. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. User Response: Do the following: 1. Verify that the correct input tape is mounted. 2. Verify that the correct block sizes have been coded in the DSECT and DBDEF macro for the file in error. 3. Examine the dump to determine if an I/O error occurred, and the cause of the error. DB011B Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An FINWC macro error occurred while releasing a chain of pool records. System Action: Processing continues without releasing additional records. User Response: Examine the dump to determine the reason for the FINWC macro error. DB011C Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPFDF macro or function was issued with the FADDR parameter specified, but the file address does not match the file address of the prime block of the subfile being referenced. Note: The FADDR parameter for TPFDF functions is coded using the function name. For example, the DFDEL_FADDR parameter is used with the dfdel function. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1. User Response: Update the application program so that it uses the correct file address with the FADDR parameter. DB011E Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where:
System Errors
21
DB0120 DB0123
fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: The amount of storage requested by a DBOPN macro or dfopn function was too high. The SPACE and SPACEB parameters are used to request storage with the DBOPN macro, while the dft_sps parameter is used with the dfopn function. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Update the application program to use a smaller amount of storage. v Update the application program to use an alternate method of obtaining storage. DB0120 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A loop was detected in a chain of blocks when the TPFDF product attempted to pack a file. System Action: The pack operation stops. User Response: Examine the dump to determine the reason for the loop in the chain of blocks. It may be necessary to correct the chain manually using TPF commands or ALCS commands (for example, ZAFIL). See TPF Operations for more information about the TPF commands. See ALCS Operation and Maintenance for more information about the ALCS commands. DB0121 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The maximum number of keys that can be used with a key list has been exceeded. A key list is used with the following: v DBKEY macro v KEYLIST parameter on a TPFDF macro v dfkey function. System Action: The entry control block (ECB) exits. User Response: Update the application program to use no more than the maximum number of keys. See TPFDF Programming Concepts and Reference for more information about key lists. DB0123 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An application program attempted to do one of the following on an index retrieval path that is not valid:
22
DB0124 DB0126
v Create an index entry with a DBIDX macro or dfidx function. v Remove an index entry with a DBDIX macro or dfdix function. System Action: Control returns to the application program with bit 4 of SW00RTN set to 1. User Response: Do one of the following: v Update the application program so it does not attempt to create or remove an index entry on an index retrieval path that is not valid. v Correct the index retrieval path for the file in error using the DBDEF macro. DB0124 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A TPFDF macro or function, or a parameter on a macro or function, was issued that is not valid for P-type files. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Update the application program so it uses only valid parameters, macros, and functions with the P-type file. v Convert the P-type file to another type of file. File types are defined in the DSECT or DBDEF macro. DB0125 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A record was added to a P-type file causing the prime block to split into an overflow block. However, the P-type file is defined without a forward chain field. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Update the application program so that records are not added that cause the prime block to split. v Update the DSECT and database definition (DBDEF) so that a forward chain field is defined with the same length and displacement as field STDFCH in the standard block header (see DSECT STDHD or C header file C$STDHD). DB0126 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A DBUKY macro or dfuky function was issued, but the maximum unique key value has been exceeded. System Errors
23
DB0127 DB0129
System Action: Control returns to the application program with the value of the unique key set to zero. User Response: Examine the dump to determine the reason for the error, which may indicate that the unique key value in the subfile has been corrupted. The current unique key value is maintained in field STDFUK (see DSECT STDHD or C header file C$STDHD) in the standard header of the prime block. DB0127 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: The size of an index logical record (LREC) is too large. System Action: Control returns to the application program with bit 3 of SW00RTN set to 1. User Response: Update the DSECT and DBDEF macro of the index file to reduce the size of the index LREC. DB0128 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: A DBREP macro or dfrep function was issued, but the file was opened using the DBOPN macro and the TAPE parameter, or the dfopn function and the tape name parameter. System Action: No blocks are written to the tape. User Response: Update the application program so that DBREP macros or dfrep functions are not issued when the file is opened with a tape parameter. DB0129 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address.
24
DB012B DB0131
Explanation: The displacement and length of user data to be extracted from an index logical record (LREC) exceeds the total of the size of the record. User data is extracted from an index LREC when the AREA parameter is used on the DBRED macro or dfred function. System Action: Control returns to the application program with bit 3 of SW00RTN set to 1. User Response: Do one of the following: v Update the DBDEF macro for the file in error. The displacement and length of user data for an index LREC is determined by the LDI and LLE parameters of the DBDEF macro. v Update the application program so it creates logical records with a size large enough for the user data. DB012B Program: Displayed on the console and in the dump. Error Message: fileid fvn FAD faddr UNABLE TO INITIALIZE Where: fileid The file identifier (ID). fvn The file version. faddr The file address. Explanation: A FIWHC error occurred while processing a ZUDFM OAINIT command. System Action: The ZUDFM OAINIT command processing stops. User Response: Examine the dump to determine the reason for the FIWHC error. DB0130 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error was caused by one of the following: v The TPFDF product has not been generated correctly in an ALCS environment, or a fast-link segment that has been called is not loaded. v TPFDF tried to build the DBDEF directory during restart or as a result of a ZUDFM DEF command with the INIT parameter specified, but the DBDEF directory base could not be accessed because it was not carved out correctly by CTIN. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Determine if the TPFDF=YES parameter is specified in the ALCS system configuration table. If not, specify the TPFDF=YES parameter and run the ALCS system configuration table. v Examine the dump to find the location contained in register 14 (R14). Verify that the program name residing at that location is loaded on your system. v If ALCS was generated correctly and the fast-link segment was loaded, contact your IBM Service Representative. DB0131 Program: Displayed on the console and in the dump. Error Message: hh.mm.ss prgm DUPL FIL DEF / WRONG ID tblname dsect Where: hh.mm.ss The time stamp. prgm The program stamp. tblname The DBDEF table name.
System Errors
25
DB0132 DB0134
dsect The DSECT name. Explanation: A duplicate file ID was defined using the DBDEF macro. System Action: The duplicate definition is ignored. User Response: Update the DBDEF macros so that each file ID is defined only once. DB0132 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: An error occurred while processing a TSYNC macro. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine the reason for the TSYNC error. DB0133 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: One of the following was issued with input and output P-type files, but the files have different sizes: v DBCPY macro v DBRST macro v dfcpy function v dfrst function. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Update the DSECT and DBDEF macro of one of the files so that both files have the same size. v Update the application program so it does not issue a copy or restore operation on P-type files with different sizes. DB0134 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The subsystem or subsystem user indicated in SW00SR does not match the subsystem or subsystem user indicated in the entry control block (ECB).
26
DB0135 DB0138
System Action: The ECB exits. User Response: Examine the dump to determine why the subsystem or subsystem user information in the SW00SR and ECB do not match. DB0135 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The number of subsystem user items in a database definition (DBDEF) table is not valid. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine why the number of subsystem user items is not valid. This error may indicate that field SW02SSS of a DBDEF table (see the SW02SR DSECT) has been corrupted. DB0136 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A DBDEF table indicates that subsystem user override items have been coded on the DBDEF macro, but the number of override items is zero. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine the reason for the inconsistent information in the DBDEF table. The number of subsystem user override items is contained in field SW02SIT of the DBDEF table (see the SW02SR DSECT). DB0137 Program: Displayed on the console and in the dump. Error Message: None. Explanation: An attempt was made to open a file that is excluded from the subsystem user (SSU) of the entry control block (ECB) running the application program. System Action: The ECB exits. User Response: Do one of the following: v Run the application program from a different subsystem user. v Update the application program so it does not access the file that has been excluded from the subsystem user. v Update the DBDEF macro for the file in error so that the subsystem user is not excluded. See TPFDF Installation and Customization for more information about excluding subsystem users. DB0138 Program: Displayed on the console and in the dump. Error Message: fileid PFA pfaddr rcc CFA cfaddr Where: fileid The file identifier (ID). pfaddr The prime file address. rcc The record code check. cfaddr The current file address. Explanation: The application program attempted to access a pool record that was previously released by this application program or another TPFDF application program. Symbol &DB0138 in the DBLCL macro controls whether the TPFDF product issues this error. If you set &DB0138 to 0, this error is always issued. If you set &DB0138 to 1, this error is only issued if the file was opened with the HOLD parameter (DBOPN macro) or
System Errors
27
DB0139 DB013C
the dfopn_hold option (dfopn function). The initial setting is 0. See TPFDF Installation and Customization for more information about the DBLCL macro and global symbols. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1. User Response: Update the application program so it does not access pool records that have been released. DB0139 Program: Displayed on the console and in the dump. Error Message: None. Explanation: One of the following: v An attempt was made to replace or modify a logical record (LREC) with changed keys when the DBDEF macro was coded with the KEYCHECK=YES parameter specified. v When using global modification (DBMOD macro or dfmodfunction with the ALL parameter specified), one of the fields being modified overlaps a default key field for that primary key in the file. System Action: Control returns to the application program with bit 1 of SW00RTN set to 1. For global modification, processing ends and all records that were changed before the processing ended remain changed. User Response: One of the following: v Update the application program so that keys are not altered by replace, modify, or global modification operations. v Code KEYCHECK=NO on the DBDEF macro for the file in error. DB013A Program: Displayed on the console and in the dump. Error Message: None. Explanation: A DBRED macro was issued with the BACKWARD parameter or a dfred function was issued with the DFRED_BACKWARD option, but the file being accessed does not use full backward chaining. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Set bit 0 of &SW00OP1 in the DSECT of the file being accessed to use full backward chaining. v Set symbol &DB013A in the DBLCL macro to 1. v Use another method to read the file. DB013B Program: Displayed on the console and in the dump. Error Message: None. Explanation: A DBMOD macro or dfmod function with the ALL parameter was issued that used a modification operation code that was not valid for one of the key sets in the modification key list. System Action: The entry control block (ECB) exits. User Response: Update the application program so that the DBMOD macro or dfmod function uses a valid modification operation code. See TPFDF Programming Concepts and Reference for more information about using modification key lists and modification operation codes. DB013C Program: Displayed on the console and in the dump. Error Message: None. Explanation: An application program attempted to access or add a technical logical record (TLREC). TLRECs are reserved for IBM use. System Action: The entry control block (ECB) exits. User Response: Update the application program so that a valid LREC is accessed.
28
DB013E DB0141
DB013E Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when an application program issues a DBADD macro with the UNIQUE parameter specified or a dfadd function with the DFADD_UNIQUE option specified when the following conditions are true: v The file has no organization (that is, it is defined as NOORG) v There are no default keys defined with the DBDEF macro for the file in error v There are no active keys. You must have default keys defined or have active keys when adding a unique logical record (LREC) to a file that is not organized. System Action: Symbol &DB013E in the DBLCL macro controls whether the TPFDF product returns control to the application program or exits the entry control block (ECB) after issuing this error. If you set &DB013E to 0, which is the default setting, the ECB exits. If you set &DB013E to 1, control is returned to the application program. User Response: Do one of the following: v Update the DBDEF macro for the file to define default keys. v Update the application program to specify keys or a key list. v Update the application program to specify an UP or DOWN organization for the file. See TPFDF Programming Concepts and Reference for more information about the DBADD macro and dfadd function. See TPFDF Database Administration for more information about the DBDEF macro. See TPFDF Installation and Customization for more information about the DBLCL macro. DB013F Program: Displayed on the console and in the dump. Error Message: None. Explanation: An application program attempted to access the database for a TPF subsystem user (SSU) when the SSU was not available. System Action: The entry control block (ECB) exits. User Response: Determine why the SSU is not available. See TPF Operations for more information about how check the status of an SSU. DB0140 Program: Displayed on the console and in the dump. Error Message: None. Where: Explanation: An error occurred when the ATTAC macro was issued to attach a block of a W-type file that is in DETAC mode. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. User Response: Examine the dump to determine why the error occurred. DB0141 Program: Displayed on the console and in the dump. Error Message: None. Where: Explanation: An error occurred while initializing the central database table during restart or while processing the ZUDFM OAI/DBTAB command with the INIT parameter specified. During the initialization process, a TPF subsystem user (SSU) defined by the DBDEF SSU parameter was found not to exist. System Action: Central database table initialization processing continues. User Response: Determine which SSU does not exist by comparing the DBDEF SSU table pointed to by register 4 with the SSU table from UATBC pointed to by register 14. System Errors
29
DB0142 DB0145
See TPFDF Database Administration for more information about the DBDEF macro. See TPF Operations for more information about how to check the status of an SSU. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. DB0142 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPFDF application program attempted to add a null logical record (LREC) to a subfile with default keys defined. Null LRECs are added using the NULLREC parameter on the DBADD macro or the DFADD_NULLREC option on the dfadd function. System Action: The entry control block (ECB) exits. User Response: Update the application program so that null LRECs are not added to files with default keys defined. DB0143 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when a TPFDF application attempts to issue a macro or function after an I/O error has been indicated for a file. An I/O error is indicated when SW00RTN bit 0 is set to 1. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Determine why the I/O error occurred. 2. Update the TPFDF application to stop processing a file once an I/O error has occurred. DB0144 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A DBDEL macro with the INCLUDE parameter specified, or dfdel function with the DFDEL_INCLUDE parameter specified, was issued that included a file that the TPFDF product cannot process. There are 2 types of files that can cause this error, as follows: v Non-TPFDF files, which are specified by coding NO for the ACPDB parameter on the DBDEF macro. v P-type files without standard forward chaining, which is indicated by setting the INB parameter on the DBDEF macro to less than or equal to 8. System Action: The entry control block (ECB) exits. User Response: Update the application program so that it does not include non-TPFDF files and P-type files without standard forward chaining. SeeTPFDF Programming Concepts and Reference for more information about the DBDEL macro and dfdel function. See TPFDF Database Administration for more information about the DBDEF macro. DB0145 Program: Displayed on the console and in the dump. Error Message: TPFDF MACRO ISSUED IN THE WRONG COMMIT SCOPE Explanation: A TPFDF macro was issued on a file that was not opened in the current commit scope. System Action: The entry control block (ECB) exits. User Response: Ensure that the file you are referencing with TPFDF macros is in the same commit scope as when the file was opened. See TPFDF Programming Concepts and Reference for more information about commit scopes.
30
DB0146 DB0149
DB0146 Program: Displayed on the console and in the dump. Error Message: OPEN TPFDF FILE IS DETECTED WHILE CLOSING THE COMMIT SCOPE Explanation: When trying to commit or end the commit scope, the system detected a file that was not closed. All TPFDF files must be opened and closed in the same commit scope. System Action: The entry control block (ECB) exits. User Response: Update the application program to ensure that all paths close the file before the commit scope is committed or ended. See TPFDF Programming Concepts and Reference for more information about commit scopes. DB0147 Program: Displayed on the console and in the dump. Error Message: TPFDF DETAC MODE INITIATING USE OF SHORT TERM POOLS (STP) Explanation: This message occurs when the defined maximum number of working storage blocks is exceeded while processing TPFDF files in detac mode. This message is accompanied by a dump of the contents of the enhanced detac table and the SW00SR that was being processed when the system error occurred. System Action: Processing continues using short-term pool storage to buffer updates. User Response: Do one of the following: v Checkpoint the files more often v Close the files more often v Increase the number of storage blocks by using the #DFDET_MAX set symbol in the ACPDBE macro. See TPFDF Programming Concepts and Reference for more information about commit scopes. See TPFDF Installation and Customization for more information about defining the maximum number of storage blocks by using set symbol #DFDET_MAX in the ACPDBE macro. DB0148 Program: Displayed on the console and in the dump. Error Message: NO HEAP FOR TPFDF DETAC TABLE Explanation: This error occurs when the allocated heap storage buffer fails to allocate necessary storage for the TPFDF detac table. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine why there was not enough heap storage allocated for the TPFDF detac table. 2. Correct the problem. See TPFDF Programming Concepts and Reference for more information about commit scopes. DB0149 Program: Displayed on the console and in the dump. Error Message: NO HEAP FOR TPFDF DETAC TABLE Explanation: This error occurs when both the current and increased allocated heap storage buffer fails to allocate the necessary storage for the TPFDF detac table. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine why there was not enough heap storage allocated for the TPFDF detac table. 2. Correct the problem. See TPFDF Programming Concepts and Reference for more information about commit scopes. System Errors
31
DB0151 DB0166
DB0151 Program: Displayed on the console and in the dump. Error Message: FIND ERROR ON TPFDF BUFFER BLOCK ENTRY EXITED Explanation: An input/output (I/O) error occurred on a TPFDF buffer block that contains user data. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine why the I/O error occurred. 2. Correct the problem. See TPFDF Programming Concepts and Reference for more information about commit scopes. DB0161 Program: Displayed on the console and in the dump. Error Message: None. Explanation: An application called the DBRET macro or dfret function, causing the maximum number of logical record (LREC) positions to be exceeded for the entry control block (ECB). The maximum number of LREC positions that can be retained for each ECB is 250. System Action: The ECB exits. User Response: Change the application so that it does not retain more than 250 LREC positions in any active ECB. DB0163 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A fast-link case number that does not exist has been called. System Action: The entry control block (ECB) exits. User Response: Do one of the following: 1. Change the calling segment to use a different fast-link case number. 2. Add the missing fast-link case number by using the DFLNK macro. See TPFDF Programming Concepts and Reference for more information about the DFLNK macro. DB0164 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The fast-link initializer segment cannot find the specified fast-link segment. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump and search for register 2 (R2) because it contains the name of the program that cannot be found. 2. Update the program allocation table (PAT) with the missing program. See TPFDF Programming Concepts and Reference for more information about the DFCAS and DFLNK macros. DB0166 Program: Displayed on the console and in the dump. Error Message: LREC TOO LARGE SUBFILE MIGRATION CANCELED Explanation: An existing LREC was too large to fit into a pool record with 8-byte file address headers.
32
DB0167 DB016B
System Action: Migration for the subfile containing the specified LREC is canceled, and the subfile is restored to its original state. Migration processing continues for the next subfile. User Response: Evaluate truncating the LREC so that the subfile can be migrated to 8-byte addressing. See TPFDF Database Administration for more information about 8-byte addressing. DB0167 Program: Displayed on the console and in the dump. Error Message: POOL WITH 8-BYTE FILE ADDR HEADER REFERENCED FROM 4-BYTE FIELD Explanation: During TPFDF processing, a 4-byte index reference was found to a file that is requesting FARF6 file addresses for prime blocks (F6PRP=YES parameter specified on the DBDEF macro). This warning message was generated because the F6WARN=YES parameter was specified in the DBDEF macro for the referenced file. System Action: Processing continues. User Response: Be sure that all references to the target file have been migrated to 8-byte file addresses before enabling FARF6 file addressing in the target file. See TPFDF Database Administration for more information about 8-byte addressing. DB0168 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A FIND error occurred when retrieving a large logical record (LLR) block. System Action: Control is returned to the application program with bit 0 of SW00RTN and bit 2 of SW00RT3 set to 1 to indicate an LLR index block (LLIB) or LLR data block (LLDB) find error. User Response: Analyze the dump to determine which LLR block is in error and correct the problem. You can use the ZUDFM OA* command with the LR parameter specified to display information about the LLR. DB0169 Program: Displayed on the console and in the dump. Error Message: None. Explanation: An error occurred when the TPFDF product attempted to allocate ECB heap (malloc storage). System Action: Control is returned to the application program with bit 0 of SW00RTN and bit 6 of SW00RT2 is set to 1 to indicate a heap allocation error. If the error occurred while processing a buffered access mode (BAM) API request, bit 3 of SW00RT3 is also set to 1. User Response: Analyze the dump to determine the cause of the heap allocation error and correct the problem. DB016A Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPFDF DBTLG tape macro was issued and a large logical record (LLR) was found while writing a subfile to tape or a sequential data set. The DBTLG macro cannot be used with LLRs. System Action: Control is returned to the application program with bit 0 of SW00RTN and bit 5 of SW00RT3 set to 1 to indicate an error. User Response: Check the subfile for LLRs before issuing the DBTLG macro. DB016B Program: Displayed on the console and in the dump. Error Message: None. Explanation: A DBMOD macro was used to modify a large logical record (LLR). You cannot use the DBMOD macro to modify LLRs. System Errors
33
DB016C DB016F
System Action: The application program exits with a system error. User Response: Use the DBREP macro to modify an LLR. DB016C Program: Displayed on the console and in the dump. Error Message: None. Explanation: The application program attempted to add, modify, or replace a large logical record (LLR), but the LLR buffer address specified by the RECADDR parameter is not valid. System Action: Control is returned to the application program with bit 0 of SW00RTN and bit 1 of SW00RT3 set to 1 to indicate that the buffer address is not valid. User Response: Do the following: 1. Analyze the system dump to determine why the buffer address is not valid. 2. Check that the value of SW00LRL in the system error is the intended size. 3. Correct the problem. DB016D Program: Displayed on the console and in the dump. Error Message: None. Explanation: The application program attempted to add or replace a large logical record (LLR), but the LLR input length specified by the RECLEN parameter is not equal to the actual length of the LLR. System Action: Control is returned to the application program with bit 0 of SW00RTN and bit 0 of SW00RT3 set to 1 to indicate that the buffer size is not valid. User Response: Do the following: 1. Analyze the system dump to determine why the LLR length is not valid. 2. Check that the value of SW00LRL in the system error is the intended size. 3. Correct the problem. DB016E Program: Displayed on the console and in the dump. Error Message: INDEX MIGRATION WANTED BUT NO INDEX SUB-TABLE FOUND Explanation: While migrating a subfile to FARF6 file addresses, the DBDEF macro options were set to migrate the index logical records (LRECs), but an index sub-table or an index retrieval path was not found for the detail file. System Action: Processing continues, but the index LRECs are not changed, and the data is copied without being reformatted. User Response: Do the following: 1. Check the DBDEF macro bit settings to ensure that the definitions for the index structure are correct and make any necessary changes to the F6MIGIDX parameter. 2. If the DBDEF macro settings are correct for the index file, update the detail file DBDEF macro to make sure that there is a valid index path description to the parent index LREC. See TPFDF Database Administration for more information about the DBDEF macro. DB016F Program: Displayed on the console and in the dump. Error Message: None. Explanation: While processing a DBRET macro or a dfret function, heap storage could not be obtained. System Action: Control is returned to the application program with bit 0 of SW00RTN and bit 6 of SW00RT2 set to 1 to indicate a failure to allocate heap storage. User Response: Do the following: 1. Analyze the system dump to determine why heap storage was not available.
34
DB0170 DB0177
2. Correct the problem. DB0170 Program: Displayed on the console and in the dump. Error Message: DUPLICATE REFERENCE NAME FOUND *refname* Where: refname The reference name that is found more than once. Explanation: A search for a reference name was done and more than one SW00SR slot with that reference name was found. It is unpredictable which SW00SR slot is returned to the application. System Action: Control returns to the application. User Response: Examine the dump to determine why the error occurred. Do not specify the same reference name more than once using the REF parameter on the DBOPN macro for TPFDF files that are open at the same time. DB0174 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs because TPFDF was unable to create a data event control block (DECB) in response to a request for service by an application. System Action: The entry control block (ECB) exits. User Response: Report the problem to your IBM service representative. DB0175 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPF TXBGC macro did not successfully begin a commit scope. This may be the result of an internal error with the TPFDF product. System Action: The entry control block (ECB) exits. User Response: Report the problem to your IBM service representative. See TPF General Macros for more information about the TXBGC macro. DB0176 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPF TXCMC macro did not successfully commit a transaction. This may be the result of an internal error with the TPFDF product. System Action: The entry control block (ECB) exits. User Response: Report the problem to your IBM service representative. See TPF General Macros for more information about the TXCMC macro. DB0177 Program: Displayed on the console and in the dump. Error Message: None. Explanation: A TPF TXRBC macro did not successfully rollback a transaction. This may be the result of an internal error with the TPFDF product. System Action: The entry control block (ECB) exits.
System Errors
35
DB0178 DB017C
User Response: Report the problem to your IBM service representative. See TPF General Macros for more information about the TXRBC macro. DB0178 Program: Displayed on the console and in the dump. Error Message: None. Explanation: Resource managers were not opened when the TPF TXBGC macro was issued. This may be the result of an internal error with the TPFDF product. System Action: The entry control block (ECB) exits. User Response: Report the problem to your IBM service representative. See TPF General Macros for more information about the TXBGC macro. DB0179 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The TPF commit and rollback functions were not issued in the correct sequence. A TPF TXCMC maco was issued, but no previous TPF TXBGC macro was issued. This may be the result of an internal error with the TPFDF product. System Action: The entry control block (ECB) exits. User Response: Report the problem to your IBM service representative. See TPF General Macros for more information about the TXCMC and TXBGC macros. DB017A Program: Displayed on the console and in the dump. Error Message: None. Explanation: The TPF commit and rollback functions were not issued in the correct sequence. A TPF TXRBC macro was issued, but no previous TPF TXBGC macro was issued. This may be the result of an internal error with the TPFDF product. System Action: The entry control block (ECB) exits. User Response: Report the problem to your IBM service representative. See TPF General Macros for more information about the TXRBD and TXBGC macros. DB017B Program: Displayed on the console and in the dump. Error Message: RETAINED LREC POSITION MIGHT NOT BE VALID ANYMORE Explanation: The application program tried to read an LREC using the STACKREF parameter without having opened the file with HOLD or DETAC. Because the open was not done with HOLD or DETAC, the retained LREC position may not be valid. System Action: Processing continues normally. Symbol &DB017B in the DBLCL macro specifies whether the TPFDF product informs you that an application program tried to read an LREC by using the STACKREF parameter without having opened the subfile with HOLD or DETAC. If you set &DB017B to 0, this error is suppressed. If you set &DB017B to 1, the error is issued. User Response: Ensure that your application program opens the subfile with HOLD or DETAC. SeeTPFDF Programming Concepts and Reference for more information about the DBRED and DBOPN macros, and the dfred and dfopn functions. See TPFDF Installation and Customization for more information about the DBLCL macro and global symbols. DB017C Program: Displayed on the console and in the dump. Error Message: READ PREVIOUS WITH STACKREF ISSUED, BUT NO RETAIN DONE Explanation: The application program tried to read an LREC using the STACKREF parameter before retaining an LREC using the STACKREF parameter.
36
DB017D DB0181
System Action: Control returns to the application program with bit 1 of SW00RTN set to 1 to indicate a NOT FOUND error. Symbol &DB017C in the DBLCL macro specifies whether the TPFDF product informs you that an application program tried to read an LREC by using the STACKREF parameter before retaining an LREC with the STACKREF parameter. If you set &DB017C to 0, the error is suppressed. If you set &DB017C to 1, the error is issued. User Response: Ensure that your application program retains an LREC by using the STACKREF parameter before trying to retrieve an LREC using the STACKREF parameter. See TPFDF Programming Concepts and Reference for more information about the DBRED and DBRET macros, and the dfred and dfret functions. See TPFDF Installation and Customization for more information about the DBLCL macro and global symbols. DB017D Program: Displayed on the console and in the dump. Error Message: INCORRECT BLOCK SIZE INDICATOR Explanation: An incorrect block size indicator was found in the SW00WRS, SW00ARS, or SW00BKS SW00SR field. This error could have occurred because storage is being overwritten. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the system dump to determine what process updated the SW00WRS, SW00ARS, or SW00BKS SW00SR field with an incorrect block size. 2. Correct the error. l DB017E Program: Displayed on the console and in the dump. Error Message: None. Explanation: An application program issued the DBRET macro or the dfret function before the DBRED macro or the dfred function was issued successfully. System Action: The entry control block (ECB) exits. User Response: Ensure that the macro or function calls are issued in the required sequence in the application program. See TPFDF Programming Concepts and Reference for more information about the DBRET and DBRED macros, and the dfret and dfred functions. DB017F Program: Displayed on the console and in the dump. Error Message: SEQ OPTION ON DBRST/DFRST REQUIRES SEQUPDT=YES IN DBDEF Explanation: This error occurs when the SEQ parameter is specified on the DBRST macro or the DFRST_SEQ value is specified on the dfrst function, but the corresponding DBDEF macro does not have the SEQUPDT parameter set to YES (SW02OP1 #BIT7 turned on). For integrity reasons, this parameter must be set. If the parameter is not set, changes on chains will not be reflected in the sequence number on the prime block and changes from the DBRST macro or the dfrst function may be lost. System Action: Control returns to the application program. The application programming interface (API) completed normally. User Response: Set the SEQUPDT parameter to YES on the DBDEF macro. See TPFDF Programming Concepts and Reference for more information about the DBRST macro and the dfrst function, and TPFDF Database Administration for more information about the DBDEF macro. DB0181 Program: Displayed on the console and in the dump. Error Message: MAXIMUM NUMBER OF SW00SR SLOTS FOR ECB EXCEEDED Explanation: The number of SW00SR slots created for one entry control block (ECB) is greater than 256, which is the maximum allowed. This could occur from closing files multiple times with the REUSE or NORELEASE option, then issuing open APIs on the same file instead of just accessing the file again. This can also occur if an excessive number of W-type files are opened in DETAC mode. System Errors
37
DBA001 DBB100
System Action: The ECB exits. User Response: Verify that the application program opens and closes files correctly. For example, verify that the application program does not issue an open API on a file that has been closed with the REUSE or NORELEASE option, or that an excessive number of W-type files are open in DETAC mode.
DBA000DBFFFF
DBA001 Program: Displayed on the console and in the dump. Error Message: None. Explanation: During ALCS recoup processing, one of the following conditions occurred: v A file ID was not located in the TPFDF definition (DBDEF) table. v The slot associated with the file ID was not located in the DBDEF table. v The customer descriptor area contains an incorrect displacement into the TPFDF recoup user exit. v An unsupported ALCS recoup user exit has been entered. System Action: The entry control block (ECB) exits. User Response: Ensure that the TPFDF DBDEFs are coded correctly for ALCS recoup processing. DBA002 Program: Displayed on the console and in the dump. Error Message: None. Explanation: The segment ARD2 was called with an incorrect case number. This error indicates an incorrect condition during ALCS recoup user exit processing. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine why an incorrect case number was passed to segment ARD2. DBB100 Program: Displayed on the console and in the dump. Error Message: ERROR FILING BTREE NODES Explanation: The B+Tree base code could not write nodes out to DASD. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. In addition, bit 4 of SW00RT2 is set to 1, which indicates a B+Tree error. User Response: Examine the dump to determine why the error occurred. Error Message: FIND ERROR IN BTREE NODES Explanation: The B+Tree base code could not read nodes from DASD. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. In addition, bit 4 of SW00RT2 is set to 1, which indicates a B+Tree error. User Response: Examine the dump to determine why the error occurred. This error may indicate that the nodes have been corrupted. Error Message: GETFC ERROR IN BTREE NODES Explanation: The B+Tree base code could not acquire a new pool file address. System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. In addition, bit 4 of SW00RT2 is set to 1, which indicates a B+Tree error. User Response: Examine the dump to determine why the error occurred. Error Message: KEY NOT FOUND IN BTREE NODES Explanation: The B+Tree nodes contain inconsistent data.
38
DBB200 DBB600
System Action: Control returns to the application program with bit 0 of SW00RTN set to 1, which indicates an I/O error. In addition, bit 4 of SW00RT2 is set to 1, which indicates a B+Tree error. User Response: Use the ZUDFM OAP command to re-create and pack the nodes. See TPFDF Commands for more information about the ZUDFM OAP command. DBB200 Program: Displayed on the console and in the dump. Error Message: MAXIMUM BUFFER ALLOTMENT EXCEEDED Explanation: Too many nodes were accessed without issuing a DBCLS macro. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Change the application program to issue a DBCLS macro more often. v Allow more technical logical records (TLRECs) in the nodes by increasing the node size or reducing the key size. DBB300 Program: Displayed on the console and in the dump. Error Message: MAXIMUM DETAC ALLOTMENT EXCEEDED Explanation: Too many data blocks were accessed without issuing a DBCLS macro. System Action: The entry control block (ECB) exits. User Response: Change the application program to issue a DBCLS macro more often. DBB400 Program: Displayed on the console and in the dump. Error Message: KEY SIZE TOO LARGE Explanation: Each B+Tree node block must be large enough to contain at least 4 technical logical records (TLRECs). This error occurs if the size of the keys is too large or the size of the node is too small to allow 4 TLRECs to fit in the node. System Action: The entry control block (ECB) exits. User Response: Do one of the following: v Reduce the key size. v Increase the node size. DBB500 Program: Displayed on the console and in the dump. Error Message: INVALID PARSED OPCODE Explanation: The TPFDF product detected an operation code that is not valid. This can be caused by a key list that is set up incorrectly. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Check the program and correct any problems with the key list. 2. If the error occurs again, analyze the dump and report the problem to your IBM service representative. DBB600 Program: Displayed on the console and in the dump. Error Message: INVALID PARSED BRANCH OPCODE Explanation: The TPFDF product found an unexpected branch operation code. This can be caused by a key list that is set up incorrectly.
System Errors
39
DBB700 DBC010
System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Check the program and correct any problems with the key list. 2. If the error occurs again, analyze the dump and report the problem to your IBM service representative. DBB700 Program: Displayed on the console and in the dump. Error Message: BTREE STORAGE ALLOCATION ERROR Explanation: During B+Tree processing the TPFDF product was not able to allocate work area storage. System Action: The entry control block (ECB) exits. User Response: Examine the dump to determine why the TPFDF product was unable to allocate work area storage during B+Tree processing. DBC000 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFADD FUNCTION v INVALID SW00SR POINTER IN DFADD FUNCTION v INCOMPATIBLE OPTIONS IN DFADD FUNCTION Explanation: This error occurs when a dfadd function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfadd function. DBC001 Program: Displayed on the console and in the dump. Error Message: DFSETBAM REQUIRED BEFORE DFADD WITH DFT_BAM OPTION Explanation: This error occurs when the buffered access mode (BAM) parameter list is not defined before calling the dfadd function with the DFADD_BAM option. System Action: The entry control block (ECB) exits. User Response: Correct the application program by using the dfsetbam function to define the buffered access mode parameters before calling the dfadd function. DBC010 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFADR FUNCTION v INVALID SW00SR POINTER IN DFADR FUNCTION v INCOMPATIBLE OPTIONS IN DFADR FUNCTION Explanation: This error occurs when a dfadr function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfadr function.
40
DBC020 DBC050
DBC020 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFCKP FUNCTION v INVALID SW00SR POINTER IN DFCKP FUNCTION Explanation: This error occurs when a dfckp function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfckp function. DBC040 Program: Displayed on the console and in the dump. Error Message: One of the following: v INCOMPATIBLE OPTIONS IN DFCLS FUNCTION v INVALID ACTION SPECIFIED IN DFCLS FUNCTION v INVALID SW00SR POINTER IN DFCLS FUNCTION Explanation: This error occurs when a dfcls function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which options are incompatible. 2. Examine the dump to determine which parameter is not valid. 3. Update the application program to use the correct parameters with the dfcls function.
| DBC043 | Program: Displayed on the console and in the dump. | Error Message: DFCLS - HEAP STORAGE UNAVAILABLE | Explanation: While processing a dfcls function, heap storage could not be obtained. This dump is only valid in an Airline Control | System (ALCS) environment. | System Action: The entry control block (ECB) exits. | User Response: Do the following: | 1. Analyze the system dump to determine why heap storage was not available. | 2. Correct the problem.
DBC050 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFCPY FUNCTION v INVALID SW00SR POINTER IN DFCPY FUNCTION v INCOMPATIBLE OPTIONS IN DFCPY FUNCTION Explanation: This error occurs when a dfcpy function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfcpy function.
System Errors
41
DBC060 DBC090
DBC060 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION PASSED TO DFCRE FUNCTION v INVALID SW00SR POINTER IN DFCRE FUNCTION Explanation: This error occurs when a dfcre function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfcre function. DBC070 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFDEL FUNCTION v INVALID SW00SR POINTER IN DFDEL FUNCTION Explanation: This error occurs when a dfdel function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfdel function. DBC080 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION PASSED TO THE DFDIX FUNCTION v INVALID SW00SR POINTER IN DFDIX FUNCTION Explanation: This error occurs when a dfdix function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfdix function. DBC090 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFDSP FUNCTION v INVALID SW00SR POINTER IN DFDSP FUNCTION v INCOMPATIBLE OPTIONS IN DFDSP FUNCTION Explanation: This error occurs when a dfdsp function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfdsp function.
42
DBC100 DBC123
DBC100 Program: Displayed on the console and in the dump. Error Message: INVALID ACTION SPECIFIED IN DFFRL FUNCTION Explanation: This error occurs when a dffrl function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dffrl function. DBC101 Program: Displayed on the console and in the dump. Error Message: DFFRL FUNCTION OBSOLETE - PLEASE REMOVE Explanation: The dffrl function is issued, but it is obsolete. System Action: Control is returned to the application program. User Response: Remove the dffrl function from the application program. DBC110 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION PASSED TO DFIDX FUNCTION v INVALID SW00SR POINTER IN DFIDX FUNCTION Explanation: This error occurs when a dfidx function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfidx function. DBC120 Program: Displayed on the console and in the dump. Error Message: INVALID ACTION SPECIFIED IN DFIFB FUNCTION Explanation: This error occurs when a dfifb function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfifb function.
| DBC123 | Program: Displayed on the console and in the dump. | Error Message: DFIFB -- HEAP STORAGE UNAVAILABLE | Explanation: While processing a dfifb function, heap storage could not be obtained. | System Action: The entry control block (ECB) exits. | User Response: Do the following: | 1. Analyze the system dump to determine why heap storage was not available. | 2. Correct the problem.
System Errors
43
DBC130 DBC163
DBC130 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFKEY FUNCTION v INVALID SW00SR POINTER IN DFKEY FUNCTION Explanation: This error occurs when a dfkey function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfkey function. DBC140 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN THE DFMOD FUNCTION v INVALID SW00SR POINTER IN DFMOD FUNCTION Explanation: This error occurs when a dfmod function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfmod function. DBC150 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFMRG FUNCTION v INVALID SW00SR POINTER IN DFMRG FUNCTION Explanation: This error occurs when a dfmrg function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfmrg function. DBC160 Program: Displayed on the console and in the dump. Error Message: INVALID ACTION SPECIFIED IN DFOPN FUNCTION Explanation: This error occurs when a dfopn function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfopn function.
| DBC163 | Program: Displayed on the console and in the dump. | Error Message: DFOPN -- HEAP STORAGE UNAVAILABLE | Explanation: While processing a dfopn function, heap storage could not be obtained.
44
DBC170 DBC181
| System Action: The entry control block (ECB) exits. | User Response: Do the following: | 1. Analyze the system dump to determine why heap storage was not available. | 2. Correct the problem.
DBC170 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFRED FUNCTION v INVALID SW00SR POINTER IN DFRED FUNCTION Explanation: This error occurs when a dfred function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfred function. DBC171 Program: Displayed on the console and in the dump. Error Message: DFSETBAM REQUIRED BEFORE DFRED WITH DFT_BAM OPTION Explanation: This error occurs when the buffered access mode (BAM) parameter list is not defined before calling the dfred function with the DFRED_BAM option. System Action: The entry control block (ECB) exits. User Response: Correct the application program by using the dfsetbam function to define the buffered access mode parameters before calling the dfred function. DBC180 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFREP FUNCTION v INVALID SW00SR POINTER IN DFREP FUNCTION Explanation: This error occurs when a dfrep function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfrep function. DBC181 Program: Displayed on the console and in the dump. Error Message: DFSETBAM REQUIRED BEFORE DFREP WITH DFT_BAM OPTION Explanation: This error occurs when the buffered access mode (BAM) parameter list is not defined before calling the dfrep function with the DFREP_BAM option. System Action: The entry control block (ECB) exits. User Response: Correct the application program by using the dfsetbam function to define the buffered access mode parameters before calling the dfrep function.
System Errors
45
DBC190 DBC220
DBC190 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFRET FUNCTION v INVALID SW00SR POINTER IN DFRET FUNCTION Explanation: This error occurs when a dfret function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfret function. DBC200 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFRST FUNCTION v INVALID SW00SR POINTER IN DFRST FUNCTION Explanation: This error occurs when a dfrst function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfrst function. DBC210 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFSPA FUNCTION v INVALID SW00SR POINTER IN DFSPA FUNCTION Explanation: This error occurs when a dfspa function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfspa function. DBC220 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFSRT FUNCTION v INVALID SW00SR POINTER IN DFSRT FUNCTION Explanation: This error occurs when a dfsrt function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfsrt function.
46
DBC230 DBC260
DBC230 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFTLD FUNCTION v INVALID SW00SR POINTER IN DFTLD FUNCTION Explanation: This error occurs when a dftld function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dftld function. DBC240 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFTLG FUNCTION v INVALID SW00SR POINTER IN DFTLG FUNCTION Explanation: This error occurs when a dftlg function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dftlg function. DBC250 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN THE DFTRD FUNCTION v INVALID SW00SR POINTER IN DFTRD FUNCTION Explanation: This error occurs when a dftrd function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dftrd function. DBC260 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN THE DFUKY FUNCTION v INVALID SW00SR POINTER IN DFUKY FUNCTION Explanation: This error occurs when a dfuky function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfuky function.
System Errors
47
DBC270 DBD002
DBC270 Program: Displayed on the console and in the dump. Error Message: One of the following: v INVALID ACTION SPECIFIED IN DFOPT FUNCTION v INVALID SW00SR POINTER IN DFOPT FUNCTION Explanation: This error occurs when a dfopt function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dfopt function. DBC271 Program: Displayed on the console and in the dump. Error Message: PATH ONLY ALLOWED FOR INDEXED FILES Explanation: This error occurs when a dfred function with the pth parameter or a dfopt function with the pth parameter is coded on a file that is not indexed. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Update the application program to remove the pth parameter from the dfred or dfopt function call. 2. Update the application program to use an indexed file on the dfred or dfopt function call. 3. Update the DBDEF to add an index to the file referenced on the dfred or dfopt function call. See TPFDF Database Administration for more information about DBDEFs. See TPFDF Programming Concepts and Reference for more information about the dfred and dfopt functions. DBC290 Program: Displayed on the console and in the dump. Error Message: INVALID ACTION SPECIFIED IN DFTAB FUNCTION Explanation: This error occurs when a dftab function is coded with a parameter that is not valid. System Action: The entry control block (ECB) exits. User Response: Do the following: 1. Examine the dump to determine which parameter is not valid. 2. Update the application program to use the correct parameters with the dftab function. DBD001 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when there is a retrieval error in the file address exchange routine. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function continues. User Response: Check the corresponding file. DBD002 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when the item size in a data record is not valid. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function continues.
48
DBD003 DBD012
User Response: Examine the dump and determine why the error occurred. DBD003 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when the common parameter block is not found. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function ends. User Response: Examine the dump to determine the common block handling, but do not restart the CRUISE function. DBD004 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when the subitem count or number of subitems is not valid. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function continues. User Response: Examine the dump to determine the corresponding file structure. DBD005 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs when the dynamic ID displacement exceeds the block size. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function continues. User Response: Examine the dump to determine the corresponding database definition (DBDEF), but do not restart the CRUISE function. DBD006 Program: Displayed on the console and in the dump. Error Message: Different messages. Explanation: This error occurs because of an internal programming error. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function ends. User Response: Examine the dump to determine to the dump append message, but do not restart the CRUISE function. DBD011 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs because of an internal programming error. System Action: Processing of the capture/restore utility, information and statistics environment (CRUISE) function ends. User Response: Report the problem to your IBM service representative. DBD012 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs because the capture/restore utility, information and statistics environment (CRUISE) was unable to retrieve the BXAX capture and restore keypoint during selective restore processing. System Action: Processing of the CRUISE function ends. User Response: Report the problem to your IBM service representative. System Errors
49
DBD013 F00000
DBD013 Program: Displayed on the console and in the dump. Error Message: None. Explanation: This error occurs because the capture/restore utility, information and statistics environment (CRUISE) was unable to create a data event control block (DECB). System Action: Processing of the CRUISE function ends. User Response: Report the problem to your IBM service representative. DBD014 Program: Displayed on the console and in the dump. Error Message: None. Explanation: During TPFDF CRUISE chain chase processing, the current item position exceeds the block size because the item count value at the count location (CPT=) is not correct. System Action: CRUISE processing stops at the maximum number of items and continues with the next block. User Response: Examine the dump and correct the counter value in the subfile. DBFFFF Program: Displayed on the console and in the dump. Error Message: None. Explanation: The help text contained in the program that issued the system error has exceeded the maximum block size. System Action: The help text is ignored. User Response: Report the problem to your IBM service representative.
F00000FFFFFF
F00000 Program: Displayed on the console and in the dump. Explanation: An error occurred while trying to process an FMSGS macro. System Action: The entry control block (ECB) exits unless the FMSGS macro was issued with the ERROR=R parameter specified. If the ERROR=R parameter was specified, control returns to the program. User Response: Examine the dump to determine why the error occurred. General register 14 (R14) will contain an error code set by program FMSG.
50
Online Messages
BGAC
BGAC0001I Where: recid The ID of a record that contains a DBDEF macro statement that conflicts with a DBDEF macro statement for a different record. Explanation: The MPRECD or MPPRCD parameters for two or more DBDEF macro statements conflict in a way that prevents all of them from running. System Action: TPFDF recoup clears the deadlock condition and chain chases the records with incorrect DBDEF macro statements. User Response: Do the following: 1. Correct the incorrect DBDEF macro statements. 2. Load the DBDEF macro statements again. See TPFDF Database Administration for more information about the MPRECD and MPPRCD parameters of the DBDEF macro. BGAC0002E TPFDF - RECP ABORTING DUE TO MPRECD=/MPPRCD= DEADLOCK PROC DEPENDENT ID-Xrecid WILL BE PROCESSED BY POOL OWNER
Explanation: TPFDF recoup attempted to clear conflicting DBDEF macro values, but was unable to do so. System Action: TPFDF recoup processing is forced to stop before completing. User Response: Do the following: 1. Correct the incorrect DBDEF macro statements. 2. Load the DBDEF macro statements again. See TPFDF Database Administration for more information about the MPRECD and MPPRCD parameters of the DBDEF macro.
BGAD
BGAD0001W -MPPREP COMPLETE- IPC TO PRIME PROC FAILED.
Explanation: A secondary processor has completed TPFDF recoup, but at least three attempts to send a message to the primary processor by using the SIPCC macro were not successful. System Action: None. User Response: Do the following: 1. Determine the cause of the failure. 2. Take the appropriate corrective action. See TPF System Macros for more information about the SIPCC macro.
BGAE
BGAE0001I Error on read/corruption of SRMP1A ZRECP MPLOG display incomplete
Explanation: The ZRECP MPLOG command was entered, but there was an error condition trying to read the SRMP1A TPFDF database. System Action: The entry control block (ECB) exits. User Response: Determine the cause of the corruption of the SRMP1A TPFDF TPFDF.
51
BGAE0002I BGAO0002I
BGAE0002I TPFDF MULTIPROCESSOR LOG DISPLAY
Explanation: This is the normal response to the ZRECP MPLOG command. This message is followed by a display of the processing status of all TPFDF files during recoup. System Action: None. User Response: None.
BGAH
BGAH0001I Where: numdbdefs The number of DBDEF structures that will be reprocessed. Explanation: The ZRECP EXIT command was entered specifying the PROC parameter while TPFDF recoup was running. System Action: The target processor will be exited from the recoup run and the DBDEF structures will be chain chased again on the remaining participating processors. User Response: None. See TPF Operations for more information about the ZRECP EXIT command. TPFDF RECOUP : numdbdefs STRUCTURES WILL BE REPROCESSED
BGAK
BGAK0001I Where: errnum The number of fixed errors. cpuid The processor ID. Explanation: Recoup processing has been completed on a secondary processor and the fixed error counts from that processor are being added to fixed error counts of the primary processor. System Action: Recoup processing continues on other processors. User Response: None. errnum FIXED ERRORS OCCURRED ON PROCESSOR: cpuid FIXED ERRORS ADDED TO PRIMARY FIXED ERROR COUNTS
BGAO
BGAO0001I TPFDF - MULTIPROCESSOR RECOUP STARTED
Explanation: This is a normal response during TPFDF recoup processing indicating that TPFDF recoup has started on the primary processor. System Action: None. User Response: None. BGAO0002I TPFDF - RECOUP STARTING ON SECONDARY PROCESSOR.
Explanation: This is a normal response during TPFDF recoup processing indicating that TPFDF recoup has started on a secondary processor. System Action: None. User Response: None.
52
BGA30001I BGA70001I
BGA3
BGA30001I MULTI PROCESSOR TPFDF RECOUP ABORTED
Explanation: TPFDF recoup processing has been forced to stop before completing. System Action: None. User Response: Look at the system dump that preceded this message to determine the cause of the error.
BGA5
BGA50001I TPFDF - RECP WAITING FOR SECONDARY PROCESSOR TO COMPLETE
Explanation: This is a normal response during TPFDF recoup processing indicating that TPFDF recoup has been completed on the primary processor and is waiting for all secondary processors to be completed. System Action: None. User Response: None. BGA50002I TPFDF - MULTIPROCESSOR RECOUP COMPLETED
Explanation: This is a normal response during TPFDF recoup processing indicating that TPFDF recoup processing has been completed on all processors. System Action: TPF recoup continues and starts recoup phase 2. User Response: None. BGA50003I TPFDF - RECP COMPLETE ON THIS PROCESSOR
Explanation: This is a normal message indicating that TPFDF recoup has ended on a secondary processor. System Action: The RCP tape is dismounted. User Response: None. BGA50004W TPFDF COMPLETE- IPC TO PRIME PROC FAILED
Explanation: A secondary processor has completed TPFDF recoup, but at least three attempts to send a message to the primary processor by using the SIPCC macro were not successful. System Action: None. User Response: Do the following: 1. Determine the cause of the failure. 2. Take the appropriate corrective action. See TPF System Macros for more information about the SIPCC macro.
BGA7
BGA70001I Where: cpuid The processor ID. Explanation: TPFDF recoup has ended on a secondary processor. System Action: The RCP tape is dismounted. User Response: None. TPFDF - RECP COMPLETED ON PROCESSOR cpuid
Online Messages
53
BGA70002A FCRU0000I
BGA70002A TPFDF - RECP: MOUNT RCP TAPE
Explanation: TPFDF recoup processing requires that an RCP tape is mounted on all participating processors. System Action: None. User Response: Ensure that an RCP tape is mounted on all participating processors. BGA70003I Where: numdbdefs The number of DBDEF structures that will be reprocessed. Explanation: This is a normal response to the ZRECP STOP or ZRECP EXIT command indicating that all database structures that were being chain chased on a secondary processor will be chain chased on another processor. System Action: None. User Response: None. See TPF Operations for more information about the ZRECP STOP and ZRECP EXIT commands. BGA70004A Where: cpuid The processor ID. Explanation: TPFDF recoup processing determined that a secondary processor that was running recoup is not responding to a status check. System Action: None. User Response: Do one of the following: v Enter the ZRECP EXIT command specifying the PROC parameter to exit and nullify recoup on the secondary processor. v Enter the ZRECP RESTART command specifying the PROC parameter to restart recoup on the secondary processor. See TPF Operations for more information about the ZRECP EXIT and ZRECP RESTART commands. BGA70005A Where: cpuid The processor ID. Explanation: TPFDF recoup requires the RCP tape to be mounted on all participating processors. System Action: None. User Response: Ensure that an RCP tape is mounted on all participating processors. TPFDF - RECP MOUNT RCP TAPE ON PROCESSOR cpuid TPFDF - RECP IS NOT PROCESSING ON PROCESSOR cpuid ZRECP PROC cpuid RESTART OR EXIT REQUIRED TPFDF - RECP : numdbdefs STRUCTURES WILL BE REPROCESSED.
FCRU
FCRU0000I Where: lines The header and end of a specified display. Explanation: This is the normal response to a ZFCRU command when the parameter table or default parameter table is displayed. For example, this message is displayed after you lock a parameter with the ZFCRU LOCK command. System Action: None. User Response: None. lines
54
FCRU0001E FCRU0004E
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0001E Where: keyword The specified parameter. Explanation: An error occurred when you entered a ZFCRU command because the required value for a parameter was not specified. System Action: The ZFCRU command is rejected. User Response: Enter the ZFCRU command again and specify a required value for the parameter. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0002E Where: keyword The specified parameter. keywordvalue The parameter value. Explanation: An error occurred when you entered a ZFCRU command because the parameter value is not valid. For example, v A valid range is exceeded. v A YES or NO value is required. System Action: The ZFCRU command is rejected. User Response: Enter the ZFCRU command again and specify a valid parameter value. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0003E NO PARAMETER TABLE NAME GIVEN INVALID keyword OPTION keywordvalue NO keyword OPTION GIVEN
Explanation: An error occurred because you did not specify a parameter table name with a ZFCRU command. For example, you entered the ZFCRU START command without the required parameter table name. System Action: The ZFCRU command is rejected. User Response: Enter the ZFCRU command again and specify a parameter table name. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0004E Where: name The parameter table name. Explanation: An error occurred when you specified an existing parameter table name with one of the following capture/restore utility, information and statistics environment (CRUISE) commands: v ZFCRU COPY v ZFCRU LOCK. System Action: The ZFCRU COPY or ZFCRU LOCK command is rejected. User Response: Enter the ZFCRU COPY or ZFCRU LOCK command again and specify a valid parameter table name. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU COPY or ZFCRU LOCK command. INVALID PARAMETER TABLE NAME - name GIVEN
Online Messages
55
FCRU0005E FCRU0008E
FCRU0005E Where: name The parameter table name that is already locked. Explanation: An error occurred when you entered a ZFCRU command because a parameter table is locked to your terminal address. For example, you entered the ZFCRU LOCK command with a parameter table that is already locked to your terminal, or to another parameter table that is locked. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU UNLOCK command to unlock the parameter table. 2. Enter the ZFCRU LOCK command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0006E Where: fileid The file identifier (ID). filever The file version. Explanation: This message indicates that when you entered the ZFCRU SETUP command to add a file ID to the capture/restore utility, information and statistics environment (CRUISE) parameter table, the file ID was not defined in the database definition (DBDEF). System Action: The file ID is added to the CRUISE parameter table and processing continues. User Response: Check if the file ID specified in this message is defined correctly . If the file ID is not defined correctly , do one of the following: v Load the DBDEF with the file ID. v Enter the ZFCRU DELETE command and remove the file ID from the CRUISE parameter table. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU SETUP and ZFCRU DELETE commands. FCRU0007E Where: name The parameter table name being used by a capture/restore utility, information and statistics environment (CRUISE) function. Explanation: An error occurred when you entered the ZFCRU LOCK command because the specified parameter table is active, running, paused, or stopped. System Action: The ZFCRU LOCK command is rejected. User Response: Enter the ZFCRU LOCK command again after the processing of the parameter table has completed successfully. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU LOCK command. FCRU0008E NO SPARE TABLES - CLEAN UP FIRST TABLE - name - IN USE BY CRUISE ID fileid, FVN filever NOT DEFINED IN DBDEF TABLE - name - ALREADY LOCKED
Explanation: An error occurred when you entered the ZFCRU LOCK command because there are no parameter tables available. System Action: The ZFCRU LOCK command is rejected. User Response: Do one of the following: v Use the ZFCRU DELETE command to remove parameter tables that are no longer being used. v Increase the number of ordinals for file address compute program (FACE) type #IRCBDF and then enter the ZFCRU EXPAND command.
56
FCRU0009I FCRU0012E
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0009I Where: name The parameter table name or EXPANSION when the ZFCRU EXPAND command is entered. command The CRUISE function that ended successfully or COMPLETED when the ZFCRU EXPAND command is entered. Explanation: This is the normal response when the processing of the following commands that have ended successfully: v ZFCRU COPY v ZFCRU DELETE v ZFCRU EXPAND v ZFCRU UNLOCK. System Action: None. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0010E NO PARAMETER TABLE LOCKED OK TABLE - name - command
Explanation: An error occurred when you entered a ZFCRU command because there is no parameter table locked to your terminal address. For example, you entered the ZFCRU SETUP command without the parameter table being locked. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU LOCK command and specify a parameter table name. 2. Enter the ZFCRU command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0011E Where: keyword The specified parameter table. Explanation: An error occurred when you entered the ZFCRU SETUP command because the format of the specified parameter is not valid. System Action: The ZFCRU SETUP command is rejected. User Response: Enter the ZFCRU SETUP command and specify a valid parameter table name format. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU SETUP command. FCRU0012E Where: tablename The parameter table name. Explanation: An error occurred when you entered a ZFCRU command because the length of the specified parameter table name is too long. System Action: The ZFCRU command is rejected. User Response: Enter the ZFCRU command again and specify a valid parameter table name. tablename IS TOO LONG INVALID keyword FORMAT
Online Messages
57
FCRU0013E FCRU0017E
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0013E Where: name The parameter table name. Explanation: An error occurred when you entered a ZFCRU command because the specified parameter table name was not found. For example, you entered the ZFCRU COPY command with a parameter table name that is incorrect. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command with the ALL parameter specified to view a list of all existing parameter tables. 2. Enter the ZFCRU command again and specify the name of an existing parameter table. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0014E INTERNAL ERROR - CONTACT DB-ADMINISTRATION TABLE - name - NOT FOUND
Explanation: An error occurred when you entered a ZFCRU command because of an internal database error. System Action: The TPFDF product will issue a system error. User Response: Report the problem to your IBM service representative. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0015E NO DEFAULT VALUES - SET DEFAULTS FIRST
Explanation: An error occurred when you entered the ZFCRU LOCK command because there are no parameter table default values set up. System Action: The ZFCRU LOCK command is rejected. User Response: Do the following: 1. Enter the ZFCRU DEFAULT command and set up the default values. 2. Enter the ZFCRU LOCK command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU LOCK commands. FCRU0016E INVALID DEFAULTS VALUE - REFER TO HELP
Explanation: An error occurred when you entered the ZFCRU DEFAULT command because the parameter value is not valid. System Action: The ZFCRU DEFAULT command is rejected. User Response: Enter the ZFCRU DEFAULT command again and specify a valid parameter value. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT command. FCRU0017E ITEM TO DELETE NOT FOUND
Explanation: An error occurred when you entered the ZFCRU DELETE command because the specified parameter keyword value could not be found within the currently locked parameter table. System Action: The ZFCRU DELETE command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command to display the contents of a specified parameter table. 2. Enter the ZFCRU DELETE command again and specify the correct parameter.
58
FCRU0018E FCRU0021E
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DELETE and ZFCRU DISPLAY commands. FCRU0018E Where: idtype Is either REFERENCEID or WANTEDID. Explanation: An error occurred when you entered a ZFCRU command because the ID range had been previously set up with a WID or reference ID. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command to display the contents of the specified parameter table. 2. Enter the ZFCRU DELETE command to delete the duplicate file ID range. 3. Use the correct ID range and enter the ZFCRU command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0019E Where: subparameters The subparameters specified with the reference identifier (ID) or wanted ID (WID) parameter. Explanation: An error occurred when you entered a ZFCRU command because a specified subparameter of the reference ID or WID parameter is duplicated. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command to display the contents of the specified parameter table. 2. Enter the ZFCRU DELETE command to delete the duplicate file ID range. 3. Use the correct subparameter of the reference ID or WID and enter the ZFCRU command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0020E INVALID PARAMETER SEQUENCE KEYWORD subparameters FOUND TWICE DUPLICATE idtype ID
Explanation: An error occurred when you entered a ZFCRU command because the reference identifier (ID) or wanted ID (WID) parameter is used with the ALL value of the FVN parameter. System Action: The ZFCRU command is rejected. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0021E Where: name The parameter table name. Explanation: An error occurred when you entered a ZFCRU COPY command because the specified target parameter table name already exists. System Action: The ZFCRU COPY command is rejected. User Response: Enter the ZFCRU COPY command again and specify a target parameter table name that does not already exist. TABLE - name - ALREADY EXISTS
Online Messages
59
FCRU0022E FCRU0027E
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU COPY command. FCRU0022E Where: keyword The parameter table keyword. Explanation: An error occurred when you entered a ZFCRU command because the number of keyword parameters exceeds the maximum number of 24. System Action: The ZFCRU command is rejected. User Response: Create another table using the additional keywords and enter the ZFCRU command again. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0023E NO TARGET TABLE NAME GIVEN TOO MANY keyword ITEMS GIVEN MAXIMUM NUMBER IS 24
Explanation: An error occurred when you entered the ZFCRU COPY command because a target parameter table name was not specified or the command syntax was not entered correctly. System Action: The ZFCRU COPY command is rejected. User Response: Do the following: 1. Check the command syntax. 2. Check the parameter table name. 3. Enter the ZFCRU COPY command again and specify a target parameter table name. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU COPY command. FCRU0026E Where: cccc The file identifier (ID). version The version of the file. Explanation: An error occurred when you entered a ZFCRU command because there are no statistics available for this file ID. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command with the STATISTIC parameter specified. 2. Enter the ZFCRU command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0027E Where: name The target parameter table name. Explanation: An error occurred when you entered the ZFCRU START command because the specified parameter table has already been activated. System Action: The ZFCRU START command is rejected. User Response: Do one of the following: v Wait for the active parameter table to be completed. v Process the parameter table on another processor. TABLE -name- ALREADY IN USE NO STATISTICS AVAILABLE FOR ID-cccc FVN-version
60
FCRU0028E FCRU0031E
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU START command. FCRU0028E ERROR IN DECB CREATE
Explanation: An error occurred when you entered a ZFCRU command because the capture/restore utility, information and statistics environment (CRUISE) was unable to create a data event control block (DECB). System Action: Processing of the CRUISE function ends. User Response: Report the problem to your IBM service representative. FCRU0029E CRUISE NOT ACTIVE ON THIS CPU/SSU
Explanation: An error occurred because one of the following commands has been entered without a capture/restore utility, information and statistics environment (CRUISE) function that is currently running: v ZFCRU ABORT v ZFCRU ECB v ZFCRU LOGGING v ZFCRU OUTPUT v ZFCRU PAUSE v ZFCRU PRINT v ZFCRU RESTART v ZFCRU STOP. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU START command twice to put CRUISE in the state of running. 2. Enter the ZFCRU command again. See TPFDF Commands and TPFDF Utilities for more information about CRUISE, the ZFCRU START command, and other ZFCRU commands. FCRU0030E RESTART NOT POSSIBLE - CHECK PARAMETER TABLE
Explanation: An error occurred when you entered a ZFCRU RESTART command, and there is no capture/restore utility, information and statistics environment (CRUISE) function to be restarted. A CRUISE function can be restarted under the following conditions: v When an unexpected system interruption occurs during the processing of a CRUISE function. v When the parameter table status is in pause state. System Action: The ZFCRU RESTART command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command with the ALL parameter specified to verify the status of a CRUISE function. 2. Enter the ZFCRU RESTART command again. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU DISPLAY and ZFCRU RESTART commands. FCRU0031E ERROR IN FACE ROUTINE
Explanation: An error occurred when you entered a ZFCRU START command because a previous error existed with the capture/restore utility, information and statistics environment (CRUISE) environment accessing the keypoint file address compute program (FACE). CRUISE is not installed correctly. System Action: The ZFCRU START command is rejected and the CRUISE function ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU START command.
Online Messages
61
FCRU0034E FCRU0039E
FCRU0034E INVALID PROGRAM ACTIVATION - CONTACT DB-ADMINISTRATION
Explanation: An error occurred when you entered a ZFCRU command because of an internal programming error. System Action: The ZFCRU command is rejected. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0036E Where: command The ZFCRU PAUSE or ZFCRU STOP command. Explanation: An error occurred when you entered a ZFCRU PAUSE or ZFCRU STOP command, but there is no capture/restore utility, information and statistics environment (CRUISE) function to stop or pause. System Action: The ZFCRU command is rejected. User Response: Do the following: 1. Enter the ZFCRU DISPLAY command with the ALL parameter specified to verify the status of a CRUISE function. 2. Enter the ZFCRU PAUSE command or the ZFCRU STOP again. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU PAUSE or ZFCRU STOP command. FCRU0037E INVALID ENTRY, SEE ZFCRU HELP DIS OPTION - command- NOT ALLOWED - CHECK CRUISE STATUS
Explanation: An error occurred when you entered a ZFCRU DISPLAY or a ZFCRU HELP command with an incorrect syntax entry. System Action: The ZFCRU DISPLAY or the ZFCRU HELP command is rejected. User Response: Do the following: 1. Enter the ZFCRU HELP command with the DISPLAY parameter specified for the correct syntax. 2. Enter the ZFCRU DISPLAY or the ZFCRU HELP command again and specify the correct syntax. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DISPLAY and ZFCRU HELP commands. FCRU0038E Where: n A predefined maximum entry control block (ECB) level for the capture/restore utility, information and statistics environment (CRUISE). This level is defined as CRU_DEF_MAX_ECB in C$CRUUSR. ECB PERCENTAGE IS NOT VALID ENTER A VALUE FROM 1 - n
Explanation: An error occurred when the ZFCRU DEFAULT, ZFCRU ECB, or ZFCRU RESTART command was entered because the specified ECB parameter value was not in the range 1 - n%. System Action: The command is rejected. User Response: Enter the correct ZFCRU command again and specify an ECB parameter value in the range 1 - n%. See TPFDF Commands for more information about the ZFCRU commands and seeTPFDF Utilities for more information about CRUISE. FCRU0039E INVALID NUMBER OF PRINTER MESSAGES, ENTER A VALUE FROM 1100 OR ALL
Explanation: The ZFCRU PRINT command was entered by the specified number of CRUISE messages to print is not valid. System Action: The ZFCRU PRINT command is rejected. User Response: Enter the ZFCRU PRINT command again and specify a value in the range 1100 or ALL. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands.
62
FCRU0040E FCRU0046W
FCRU0040E INVALID NUMBER OF LOGGING MESSAGES, ENTER A VALUE FROM 1100 OR ALL
Explanation: The ZFCRU LOGGING command was entered but the specified number of CRUISE messages to log is not valid. System Action: The ZFCRU LOGGING command is rejected. User Response: Enter the ZFCRU LOGGING command again and specify a value in the range 1100 or ALL. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU LOGGING command. FCRU0042I MODIFIED
Explanation: This is the normal response when you enter the ZFCRU DEFAULT or ZFCRU SETUP command. System Action: The message is logged to the CRUISE parameter table logging file and the parameter table or default parameter table is modified as specified. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT or ZFCRU SETUP command. FCRU0043I TABLE LOCKED
Explanation: This is the normal response when you enter the ZFCRU LOCK command. System Action: The message is logged to the CRUISE parameter table logging file and the specified parameter table is locked. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU LOCK command. FCRU0044I Where: lines The header and end of a specified display. Explanation: This is the normal response when you enter the ZFCRU UNLOCK command and a parameter table verification check error has occurred. System Action: The message is logged to the CRUISE parameter table logging file and the parameter table is unlocked. User Response: To use this parameter table to process a CRUISE function, you must correct the verification check errors. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU UNLOCK command. FCRU0045I NO CRUISE PARAMETER TABLES FOUND lines
Explanation: The ZFCRU DISPLAY command was entered, but there were no capture/restore utility, information and statistics environment (CRUISE) parameter tables to display. System Action: Processing of the ZFCRU DISPLAY command ends. User Response: If CRUISE parameter tables are needed, enter the ZFCRU LOCK command to create the parameter tables and the ZFCRU SETUP command to setup the parameters in the tables. See TPFDF Commands and TPFDF Utilities for more information about CRUISE parameter tables and the ZFCRU DISPLAY, ZFCRU LOCK, and ZFCRU SETUP commands. FCRU0046W THE PARAMETER TABLE CANNOT BE STARTED
Explanation: A parameter table verification check error occurred after the ZFCRU START command was entered for the first time. System Action: The command is rejected. User Response: Do the following: 1. Enter the ZFCRU LOCK command with the parameter table that was specified with the ZFCRU START command. 2. Enter the ZFCRU SETUP command and correct the incorrect parameter values or enter the parameter values that are missing. Online Messages
63
FCRU0100I FCRU0102I
3. Enter the ZFCRU UNLOCK command with the parameter table that was specified with the ZFCRU LOCK command. 4. Enter the ZFCRU START command again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0100I Where: cpuid The processor ID. tablename The parameter table name. function A capture/restore utility, information and statistics environment (CRUISE) function; for example, capture, pack, restore, and verify. Explanation: This is the normal response when you enter the ZFCRU START command a second time. System Action: The CRUISE function continues processing. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU START command. FCRU0101I Where: tablename The parameter table name. oo nn The entry control block (ECB) percentage that was used before a restart. The ECB percentage that is currently in use. TABLE -tablename- RESTARTED - ECB PERCENTAGE CHANGED FROM oo TO nn cpuid TABLE -tablename- FUNCTION-function STARTED
Explanation: This is the normal response to the ZFCRU RESTART command when the ECB percentage has been specified. System Action: The message is logged to the CRUISE parameter table logging file and the ECB percentage has been changed as specified. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE), and the ZFCRU ECB and ZFCRU RESTART commands. FCRU0102I Where: cpuid The processor ID. tablename The parameter table name. Explanation: This is the normal response to the ZFCRU RESTART command. System Action: CRUISE parameter table processing is restarted. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU RESTART command. cpuid TABLE -tablename- RESTARTED
64
FCRU0103I FCRU0106I
FCRU0103I Where: cpuid The processor ID. tablename The parameter table name. Explanation: This is the normal response to the ZFCRU PAUSE command. System Action: CRUISE parameter table processing is paused. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU PAUSE command. FCRU0104I Where: cpuid The processor ID. oo nn The entry control block (ECB) percentage that was previously in use. The ECB percentage that is currently in use. cpuid ECB PERCENTAGE CHANGED FROM oo TO nn cpuid TABLE -tablename- PAUSED
Explanation: This is the normal response to the ZFCRU ECB command when the capture/restore utility, information and statistics environment (CRUISE) function is in running state. System Action: The message is logged and the percentage of ECBs allocated is changed for the CRUISE function in running state. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU ECB command. FCRU0105I Where: cpuid The processor ID. Explanation: This is the normal response when the ZFCRU PRINT command is entered with the ALL parameter specified when the ALL parameter value was already specified. System Action: The message is logged to the CRUISE parameter table logging file. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU PRINT command. FCRU0106I Where: cpuid The processor ID. nn The number of CRUISE printer messages, in the range 1100, that are currently in use. cpuid NUMBER OF PRINTER MESSAGES CHANGED FROM ALL TO nn cpuid NUMBER OF PRINTER MESSAGES CHANGED FROM ALL TO ALL
Explanation: This is the normal response to the ZFCRU PRINT command when a capture/restore utility, information and statistics environment (CRUISE) function is in running state and the ALL parameter has been changed to a specified number of printed messages. System Action: The message is logged to the CRUISE parameter table logging file and the number of messages to print is changed to the specified number of messages for a CRUISE function in running state. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU PRINT command. Online Messages
65
FCRU0107I FCRU0110I
FCRU0107I Where: cpuid The processor ID. oo The number of printer messages, in the range 1100, to be printed before CRUISE message printing stops. cpuid NUMBER OF PRINTER MESSAGES CHANGED FROM oo TO ALL
Explanation: This is the normal response to the ZFCRU PRINT command with the ALL parameter specified when the CRUISE function is in running state. System Action: The message is logged to the CRUISE parameter table logging file and all messages will be printed. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU PRINT command. FCRU0108I Where: cpuid The processor ID. oo nn The previous number of messages to print before CRUISE message printing ends. The number of CRUISE printer messages, in the range 1100, currently in use. cpuid NUMBER OF PRINTER MESSAGES CHANGED FROM oo TO nn
Explanation: This is the normal response when the ZFCRU PRINT command is entered when the capture/restore utility, information and statistics environment (CRUISE) function is in running state. System Action: The message is logged to the CRUISE parameter table logging file and the specified number of messages will now print before CRUISE message printing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU PRINT command. FCRU0109I Where: cpuid The processor ID. Explanation: This is the normal response when the ZFCRU LOGGING command is entered with the ALL parameter specified when the ALL parameter value was already specified. System Action: The message is logged to the CRUISE parameter table logging file. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU LOGGING command. FCRU0110I Where: cpuid The processor ID. nn The number of CRUISE messages to log in the range 1100. cpuid NUMBER OF LOGGING MESSAGES CHANGED FROM ALL TO nn cpuid NUMBER OF LOGGING MESSAGES CHANGED FROM ALL TO ALL
Explanation: This is the normal response to the ZFCRU LOGGING command when the capture/restore utility, information and statistics environment (CRUISE) function is in running state and the ALL parameter has been changed to a specified number of log messages. System Action: The message is logged to the CRUISE parameter table logging file. The number of messages to log is changed for the CRUISE function in running state. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU LOGGING command.
66
FCRU0111I FCRU0114E
FCRU0111I Where: cpuid The processor ID. oo The previous number of messages to log before CRUISE message printing ends. cpuid NUMBER OF LOGGING MESSAGES CHANGED FROM oo TO ALL
Explanation: This is the normal response to the ZFCRU LOGGING command with the ALL parameter specified when a capture/restore utility, information and statistics environment (CRUISE) function is in running state. System Action: The message is logged to the CRUISE parameter table logging file. All messages will be logged. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU LOGGING command. FCRU0112I Where: cpuid The processor ID. oo nn The previous number of messages to log before CRUISE message logging ends. The number of CRUISE messages, in the range 1100, currently in use that will be logged. cpuid NUMBER OF LOGGING MESSAGES CHANGED FROM oo TO nn
Explanation: This is the normal response to the ZFCRU LOGGING command when a capture/restore utility, information and statistics environment (CRUISE) function is in running state. System Action: The message is logged to the CRUISE parameter table logging file. CRUISE messages will now be logged until the specified number is reached. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU LOGGING command. FCRU0113E Where: filename An internal file that is used by the capture/restore utility, information and statistics environment (CRUISE). Explanation: An internal CRUISE database error occurred when a ZFCRU command was entered and a CRUISE function was in running state. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function in running state is ended. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0114E RESTART NOT POSSIBLE ABORT AND START OVER TPFDF ERROR WITH filename - CONTACT DB-ADMINISTRATION
Explanation: An error occurred when you entered the ZFCRU RESTART command in an ALCS environment for CRUISE restore function processing, which had been stopped with the ZFCRU STOP command or ended because of an unexpected interruption. System Action: The ZFCRU RESTART command is rejected. User Response: Do the following: 1. Enter the ZFCRU ABORT command. 2. Enter the ZFCRU START command and start the CRUISE restore function again. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU ABORT, ZFCRU RESTART, ZFCRU START, and ZFCRU STOP commands.
Online Messages
67
FCRU0115I FCRU0117I
FCRU0115I Where: cpuid The processor ID. addrold1 A previous printer address specified before this message, where addrold1 is previous printer address 1. addrold2 A previous printer address specified before this message, where addrold2 is previous printer address 2. addrold3 A previous printer address specified before this message, where addrold3 is previous printer address 3. addrnew1 The printer address currently in use, where addrnew1 is current printer address 1. addrnew2 The printer address currently in use, where addrnew2 is current printer address 2. addrnew3 The printer address currently in use, where addrnew3 is current printer address 3. Explanation: This is the normal response to the ZFCRU OUTPUT command when the capture/restore utility, information and statistics environment (CRUISE) function is in running state. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE messages will be sent to the current printer addresses. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU OUTPUT command. FCRU0116I Where: nn The number of records read from tape. nn RECORDS READ FROM TAPE tapename xx RECORDS SELECTED yy RECORDS RESTORED zz RECORDS DETECTED cpuid PRINTER ADDRESSES CHANGED FROM 1:addrold1 2:addrold2 3:addrold3 TO 1:addrnew1 2:addrnew2 3:addrnew3
tapename The name of the tape read. xx yy zz The number of records selected. The number of records restored. The number of records detected.
Explanation: This is the normal response when CRUISE restore processing ends. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore processing has ended. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0117I Where: xx yy zz ee The number of from-references processed. The number of addresses exchanged. The number of fixed files restored. The number of errors detected. FILE ADDRESS EXCHANGE xx FROM REFERENCES PROCESSED yy ADDRESSES EXCHANGED zz FIX FILES RESTORED ee ERRORS DETECTED
Explanation: This is the normal response when CRUISE restore processing ends. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore processing has ended.
68
FCRU0118I FCRU0122E
User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0118I TAPE BACKSPACED 100 BLOCKS
Explanation: This is the normal response when CRUISE restore processing has been restarted. The restore tape is backspaced 100 blocks and restore processing starts again. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore processing continues. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0119E INVALID CRUISE FUNCTION
Explanation: A capture/restore utility, information and statistics environment (CRUISE) function in active state that is not valid has been detected. System Action: The message is logged, a system error (DBA006) is issued, and the CRUISE function in active state ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0120E REQUESTED TAPE MOUNTED FOR INPUT
Explanation: An error occurred when you entered the ZFCRU START or the ZFCRU RESTART command with CRUISE capture in active state because the requested tape is mounted as an input tape. System Action: The message is logged to the CRUISE parameter table logging file. CRUISE capture processing has ended and a restart is no longer possible. User Response: Do the following: 1. Mount the capture tape as an output tape. 2. Enter the ZFCRU START command twice to start CRUISE function processing. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE), and the ZFCRU START and ZFCRU RESTART commands. FCRU0121E REQUESTED TAPE NOT ACTIVE
Explanation: An error occurred when you entered the ZFCRU START command or the ZFCRU RESTART command with CRUISE capture or restore in active state because the requested tape is not mounted. System Action: The message is logged to the CRUISE parameter table logging file. CRUISE capture or restore parameter table processing ends; a restart is no longer possible. User Response: Do the following: 1. Mount the capture or restore tape. 2. Enter the ZFCRU START command twice to start CRUISE function processing. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU START or the ZFCRU RESTART command. FCRU0122E REQUESTED TAPE MOUNTED FOR OUTPUT
Explanation: An error occurred when you entered the ZFCRU START or the ZFCRU RESTART command with CRUISE restore specified in active state because the requested tape is mounted as an output tape. System Action: The message is logged to the CRUISE parameter table logging file. CRUISE parameter table processing ends; a restart is no longer possible. User Response: Do the following: 1. Mount the restore tape as an input tape. 2. Enter the ZFCRU START command twice to start CRUISE restore processing. Online Messages
69
FCRU0123E FCRU0127I
See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU START or the ZFCRU RESTART command. FCRU0123E ERROR BACKSPACING TAPE
Explanation: An error occurred when you entered the ZFCRU RESTART command with CRUISE restore specified in active state because the requested tape could not be backspaced. System Action: The message is logged to the CRUISE parameter table logging file. CRUISE parameter table processing ends; a restart is no longer possible. User Response: Do the following: 1. Mount the restore tape as an input tape. 2. Enter the ZFCRU START command twice to start CRUISE restore processing. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU ABORT, ZFCRU RESTART, and ZFCRU START commands. FCRU0125I Where: nn yy The number of records found. The number of file addresses for which the setinuse user exit has been called. nn RECORDS FOUND-yy FILE ADDRESSES SET IN USE
Explanation: This is the normal response when CRUISE restore and verify processing has ended and the SETINUSE parameter is specified with the YES value. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore or verify processing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FCRU0126I Where: cpuid The processor ID. nn The number of records found. cpuid nn RECORDS FOUND
Explanation: This is the normal response when CRUISE verify processing ends. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE verify processing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0127I Where: nn yy The number of records found. The number of records written to tape. nn RECORDS FOUND yy RECORDS WRITTEN TO tapename
tapename The name of the tape. Explanation: This is the normal response when CRUISE capture processing has ended. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE capture processing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands.
70
FCRU0128I FCRU0131E
FCRU0128I Where: nn yy The number of records found. The number of files packed. nn RECORDS FOUND yy FILES PACKED
Explanation: This is the normal response when CRUISE pack processing has ended. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE pack processing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0129I Where: nn yy The number of records found. The number of file addresses exchanged. nn RECORDS FOUND yy FILE ADDRESSES EXCHANGED
Explanation: This is the normal response when CRUISE restore processing has ended. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore processing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0130E Where: fileid The file identifier (ID) to be processed. Explanation: An error occurred when you entered a ZFCRU command, but the file ID to be processed is not defined in the database definition (DBDEF). System Action: The message is logged to the CRUISE parameter table logging file, the error counter is increased by 1, and CRUISE capture processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0131E Where: fileaddr The file address to be processed. fileid The file identifier (ID) to be processed. Explanation: An error occurred during CRUISE capture processing when you entered the ZFCRU START command while writing a block to tape because the file address is no longer valid. System Action: The message is logged to the CRUISE parameter table logging file, the error counter is increased by 1, and CRUISE capture processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. BLOCK TO CAPTURE NO LONGER FOUND - FAD-fileaddr ID-fileid ID fileid NOT DEFINED IN DBDEF
Online Messages
71
FCRU0132I FCRU0135E
FCRU0132I Where: tablename The parameter table name. function The name of the capture/restore utility, information and statistics environment (CRUISE) function. nn The number of errors detected. TABLE -tablename- FUNCTION-function COMPLETED - nn ERRORS DETECTED
Explanation: This is the normal response to a CRUISE function that has ended. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0133E FAD EXCHANGE RETRIEVAL ERROR
Explanation: An error occurred when you entered a ZFCRU command during CRUISE restore processing. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0134I Where: fileaddr1 The restored top file address. fileaddr2 The target top file address. Explanation: This is the normal response during CRUISE parameter table processing when the RESTORE parameter is specified with the REBUILD value and only the top file addresses were captured. System Action: The message is logged and CRUISE restore processing continues. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FCRU0135E Where: ordnbr The ordinal number to be processed. fileid The file identifier (ID) to be processed. Explanation: A file address compute program (FACE) error occurred with the capture/restore utility, information and statistics environment (CRUISE) function in running state. System Action: The message is logged to the CRUISE parameter table logging file, the error counter is increased by 1, and the CRUISE function continues in active state. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FACE ERROR ORDINAL ordnbr OF ID fileid IS INVALID TOP FILE FAD-fileaddr1 RESTORED TO fileaddr2
72
FCRU0136E FCRU0138E
FCRU0136E Where: fileaddr1 The restored top file address. fileaddr2 The target restored top file address. Explanation: An error occurred during the processing of a CRUISE parameter table when the RESTORE parameter is specified with the REBUILD value and the top file addresses are not found. System Action: The message is logged, the error counter is increased by 1, and the CRUISE parameter table processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FCRU0137E Where: fileaddr1 The new file address. fileaddr2 The previous file address. fileaddr3 The referenced address. Explanation: An internal error occurred during the processing of a CRUISE parameter table because the RESTORE parameter is specified with the REBUILD or NEW value and the reference file address is not found. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE parameter table processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FCRU0138E Where: fileaddr1 The new file address. fileaddr2 The previous file address. fileaddr3 The referenced address. Explanation: An internal error occurred during the processing of a CRUISE parameter table because the RESTORE parameter is specified with the NEW or REBUILD value and the reference file address is not found. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE parameter table processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FILE ADDRESS EXCHANGE ERROR FAD-fileaddr2 NEW-fileaddr1 FROM-fileaddr3 FROM REFERENCE NOT FOUND FAD-fileaddr2 NEW-fileaddr1 FROM-fileaddr3 TOP REFERENCE NOT FOUND FAD-fileaddr2 NEW-fileaddr1
Online Messages
73
FCRU0139E FCRU0142I
FCRU0139E Where: fileaddr The file address to be processed. fileid The file identifier (ID) to be processed. Explanation: An internal error occurred during the processing of a CRUISE parameter table because the RESTORE parameter is specified with the OLD value and the previous file address is not valid. System Action: The message is logged to the CRUISE parameter table logging table and CRUISE parameter table processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FCRU0140E ERROR DURING RESTORE RESTORE-OLD FIND ERROR FAD-fileaddr OF ID-fileid
Explanation: An internal error occurred during CRUISE restore processing because the previous file address is not valid. System Action: The message is logged to the CRUISE parameter table logging file, a system error is issued, the error counter is increased by 1, and the CRUISE parameter table processing in active state is paused. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0141I Where: fileaddr1 The captured file address. fileaddr2 The target file for a restored file address. Explanation: This is the normal response to the RESTORE parameter specified with the NOREBUILD value. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE parameter table processing continues. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU DEFAULT and ZFCRU SETUP commands. FCRU0142I Where: cpuid The processor ID. action An action that results in a capture/restore utility, information and statistics environment (CRUISE) function that will end, pause, or stop. Explanation: This is the normal response to the ZFCRU ABORT, ZFCRU PAUSE, or ZFCRU STOP command entered when the CRUISE function is in running state. System Action: The message is logged to the CRUISE parameter table logging file. This message indicates the running CRUISE function will end, stop, or pause. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU ABORT, ZFCRU PAUSE and ZFCRU STOP commands. cpuid CRUISE IS action FILE FAD-fileaddr1 RESTORED TO fileaddr2
74
FCRU0143I FCRU0146E
FCRU0143I Where: cpuid The processor ID. tablename The parameter table name. Explanation: This is the normal response to the ZFCRU STOP command. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function is stopped. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU STOP command. FCRU0144E Where: fileaddr The file address to be processed. Explanation: An error occurred during a file address retrieval of a capture/restore utility, information and statistics environment (CRUISE) function in running state. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE parameter table processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0145E Where: fileid The file identifier (ID) to be processed. version The version of the file ID to be processed. Explanation: A error occurred because when the capture/restore utility, information and statistics environment (CRUISE) function was in running state, a record type for a file ID was not defined in the TPF file address compute program (FACE). System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function continues processing. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0146E Where: range The ordinal number range to be processed. fileid The file identifier (ID) to be processed. Explanation: An error occurred when the capture/restore utility, information and statistics environment (CRUISE) function was in running state and an ordinal range for a file ID was not correct. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE parameter table processing continues. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. ORDINAL range RANGE OF ID fileid IS INVALID RECORD TYPE FOR ID fileid (version) NOT DEFINED IN FACE-TABLE FILE ADDRESS fileaddr RETRIEVAL ERROR cpuid TABLE -tablename- STOPPED
Online Messages
75
FCRU0147E FCRU0151W
FCRU0147E Where: nn fileid The file identifier (ID) to be processed. Explanation: An error occurred when a capture/restore utility, information and statistics environment (CRUISE) function was in running state and a partition or an interleave number for a file identifier (ID) was not correct. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function continues processing. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0148I Where: cpuid The processor ID. tablename The parameter table name. Explanation: This is the normal response to a ZFCRU ABORT command that has ended successfully. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU ABORT command. FCRU0149I Where: cpuid The processor ID. name The parameter table name. Explanation: This is the normal response when the ZFCRU START command is entered the first time for a specified parameter table. System Action: The capture/restore utility, information and statistics environment (CRUISE) function is changed to active state. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU START command. FCRU0150I CPU SELECTIVE RESTORE COULD NOT COMPLETE DATA CAPTURED USING MRC cpuid TABLE -name- ACTIVATED cpuid TABLE -tablename- ABORTED The partition or interleave number to be processed. PARTITION/INTERLEAVE nn OF ID fileid IS INVALID
Explanation: This is the normal response when you enter the ZFCRU SETUP command and specify the ADR or WID parameter with multiple reference check (MRC) support. System Action: Capture/Restore Utility, Information and Statistics Environment (CRUISE) restore processing ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the ZFCRU SETUP command and MRC support. FCRU0151W Where: cpuid The processor ID where the capture/restore utility, information and statistics environment (CRUISE) is running. cpuid ID refid FVN fvn NOT DEFINED IN DBDEF
76
FCRU0152E FCRU0154I
refid The file reference name. fvn The file version. Explanation: This message indicates that during CRUISE parameter table processing, the file reference name is not defined in the database definition (DBDEF). System Action: CRUISE parameter table processing continues. User Response: Check if the file reference name specified in this message is defined correctly. If the file reference name is not defined correctly, do one of the following: v Load the DBDEF with the file reference name. v Enter the ZFCRU DELETE command to remove the file reference name from the CRUISE parameter table. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU SETUP and ZFCRU DELETE commands. FCRU0152E DECB CREATE ERROR
Explanation: An error occurred when you entered a ZFCRU command because the capture/restore utility, information and statistics environment (CRUISE) was unable to create a data event control block (DECB). System Action: Processing of the CRUISE function ends. User Response: Report the problem to your IBM service representative. FCRU0153I CPUB MRC FILE INITIALIZATION COMPLETED
Explanation: This is the normal response when you enter the ZFCRU SETUP command and multiple reference check (MRC) capture processing has completed. System Action: None. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the ZFCRU SETUP command and MRC support. FCRU0154I Where: recid The record ID being captured or selectively restored. Explanation: This is the normal response when the ZFCRU START command is entered to capture a database with more than eight levels of data or to selectively restore from tape a database with more that eight levels of data. Although a full restore will restore the complete database, only the first eight data levels can be restored by using a selective restore. System Action: One of the following occurs: v If the condition occurs during capture, processing continues. Although all data levels of the database are written to tape, only the first eight levels of the database are written to the capture/restore utility, information and statistics environment (CRUISE) control block on tape. v If the condition occurs during a selective restore, processing continues. If the file ID specified by the wanted ID (WID) is not for one of the eight data levels stored in the CRUISE control block on tape, the restored data will not be complete. User Response: Do one the following: v If you are doing a capture, there is no more action to be taken. v If you are doing a selective restore for a data level that is not stored in the CRUISE control block, do a full restore to restore the complete database. See TPFDF Commands for more information about the ZFCRU commands and see TPFDF Utilities for more information about CRUISE procedures. TOO MANY DATA LEVELS FOR ID -recid- SELECTIVE RESTORE COULD BE INCOMPLETE
Online Messages
77
FCRU0155E FCRU0165I
FCRU0155E DIFFERENT SUBSYSTEM ID RESTORE NOT ALLOWED
Explanation: An error occurred because an attempt was made to restore data on a subsystem other than the subsystem where data was captured. System Action: Capture/restore utility, information and statistics environment (CRUISE) restore processing ends. User Response: None. See TPFDF Utilities for more information about CRUISE. FCRU0161W FILE FOUND WITH ALGINFOID= BUT NO ALG INFO FILE CAPTURED
Explanation: During a CRUISE capture operation, a detail file with an associated algorithm information file (indicated the ALGINFOID parameter in the DBDEF macro) was captured, but no algorithm information file (the ALGINFOFOR parameter specified in the DBDEF macro) was captured. If the detail file is restored without the corresponding algorithm information, applications may not work as expected. System Action: Processing continues. User Response: If you intended to capture the associated algorithm information, do the following: 1. Modify the CRUISE parameter table to include the algorithm information file specified by the ALGINFOID parameter. 2. Run the CRUISE capture operation again. See TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE). FCRU0163I Where: fileid The ID. filever The file version. Explanation: This message indicates that the entry control block (ECB) percentage (previously entered with the ZFCRU SETUP or ZFCRU ECB command to be used in the CRUISE parameter table) is set too low and the default ECB distribution is used for the current file ID and file version. System Action: The default ECB distribution is used and processing continues. User Response: None. See TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and see TPFDF Commands for more information about the ZFCRU commands. FCRU0164I Where: crossreffiletype The type of cross-reference file (X-REF FILES or MRC X-REF FILE). Explanation: This message indicates that at the beginning of a CRUISE RESTORE function the initialization of the cross-reference files has started. System Action: None. User Response: None. See TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE). FCRU0165I Where: crossreffiletype The type of cross-reference file (X-REF FILES or MRC X-REF FILE). Explanation: This message indicates that at the beginning of a CRUISE RESTORE function the initialization of the cross-reference files has completed. INITIALIZATION OF crossreffiletype COMPLETED INITIALIZATION OF crossreffiletype STARTED SPECIFIED ECB PERCENTAGE TOO LOW USING DEFAULT DISTRIBUTION FOR ID fileid FVN filever
78
FCRU0200I FCRU0202I
System Action: None. User Response: None. See TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE). FCRU0200I Where: mod The tape module number. date The system capture date. time The system capture time. Explanation: This is the normal response when CRUISE restore processing is in running state. System Action: The message is logged to the CRUISE parameter table logging file. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0201E TAPE READ ERROR ABORT MOD mod FROM date time STARTED
Explanation: An error occurred with CRUISE restore processing in running state. System Action: The message is logged to the CRUISE parameter table logging file and CRUISE restore processing ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the capture/restore utility, information and statistics environment (CRUISE) and the ZFCRU commands. FCRU0202I Where: fileid1 The from-reference file identifier (ID). rcc1 The from-reference record code check (RCC). fileaddr1 The from-reference file address. fileid2 The referenced file ID. rcc2 The referenced RCC. fileaddr2 The referenced file address. Explanation: This is the normal response when a capture/restore utility, information and statistics environment (CRUISE) function has embedded references that were chain chased. System Action: The message is logged to the CRUISE parameter table logging file. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. fileid1 rcc1 fileaddr1 REFERENCES fileid2 rcc2 fileaddr2
Online Messages
79
FCRU0204E FCRU0208E
FCRU0204E Where: fileid The file identifier (ID) for the file to be processed. fileaddr The file address to be processed. refid The file identifier (ID) of the file that referenced the file to be processed. refaddr The file address where the file to be processed was referenced. Explanation: An error occurred while a file address was retrieved with the capture/restore utility, information and statistics environment (CRUISE) function in running state. System Action: The message is logged to the CRUISE parameter table logging file, the error counter is increased by 1, and the CRUISE function continues in running state. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0205E IRCFDF INTERNAL ERROR FIND ERROR fileid fileaddr SRCH ADR refid refaddr FROM REF
Explanation: An error occurred with a capture/restore utility, information and statistics environment (CRUISE) function in running state because of an internal database error. System Action: The message is logged to the CRUISE parameter table logging file and the CRUISE function ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0206E VARIABLE DISP SIZE ERROR
Explanation: An error occurred with a capture/restore utility, information and statistics environment (CRUISE) function in running state because the variable displacement in the user data during Count Type file processing is not valid. System Action: The message is logged to the CRUISE parameter table logging file, system error DBD005 is issued, and the specified processing entry control block (ECB) ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0207E DYNAMIC SIZE EXCEEDS BLOCKSIZE
Explanation: An error occurred with the capture/restore utility, information and statistics environment (CRUISE) function in running state because the variable displacement defined in the database definition (DBDEF) during No Item Type file processing is not valid. System Action: The message is logged to the CRUISE parameter table logging file, system error DBD005 is issued, and the CRUISE function in running state ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about CRUISE and the ZFCRU commands. FCRU0208E INVALID CBV IN DBDEF
Explanation: An error occurred with the capture/restore utility, information and statistics environment (CRUISE) function in running state because the monitor vector for the chain chaser defined in the database definition (DBDEF) is not valid. System Action: The message is logged to CRUISE parameter table logging file and the CRUISE function in running state ends. User Response: Call your database administrator to correct the problem. See TPFDF Commands and TPFDF Utilities for more information about the CRUISE and the ZFCRU commands.
80
RECP9001I RECP9007I
RECP
RECP9001I DF RECOUP PARAMETRIC PHASE STARTED
Explanation: This is the normal response to the TPF ZRECP RECALL command when TPFDF recoup is running. System Action: None. User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL command. RECP9002I DF RECOUP RCI/QUE SEARCH STARTED
Explanation: This is the normal response to the TPF ZRECP RECALL command without any other parameters specified when TPFDF recoup is running. TPFDF recoup has begun looking for files declared as RCI or QUE. System Action: None. User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL command. RECP9003I DF RECOUP QUE-ENTRIES INHIBITED
Explanation: This is the normal response to the TPF ZRECP RECALL command when the passing of file addresses between files is not allowed during TPFDF recoup. System Action: None. User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL command. RECP9004I DF RECOUP QUE-ENTRIES ALLOWED
Explanation: This is the normal response to the TPF ZRECP RECALL command when the passing of file addresses between files is allowed during TPFDF recoup. System Action: None. User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL command. RECP9005I DF RECOUP RCI CHAINCHASING STARTED
Explanation: This is the normal response to the TPF ZRECP RECALL command without any other parameters specified when TPFDF recoup is running. TPFDF recoup has begun processing files defined as RCI. System Action: None. User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL command. RECP9006I DF RECOUP RCI REFERENCE PROCESSING
Explanation: This is the normal response to the TPF ZRECP RECALL command without any other parameters specified when TPFDF recoup is running. TPFDF recoup is continuing to process files defined as RCI. System Action: None. User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL command. RECP9007I DF RECOUP STANDARD MONITOR PROCESSING
Explanation: This is the normal response to the TPF ZRECP RECALL command with the SEL parameter specified or the TPF ZRECP STATUS when TPFDF recoup is running. System Action: None.
Online Messages
81
RECP9008A RECP9012I
User Response: None. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP RECALL or TPF ZRECP STATUS commands. RECP9008A Where: errors The number of fixed file errors. Explanation: This is the normal response at the completion of TPFDF standard monitor processing. The information includes a count of the number of errors in fixed records. System Action: None. User Response: Do one of the following: v If the count is zero, continue with recoup processing. v If the count is greater than zero, correct the errors and enter the TPF ZRECP SEL command to run TPFDF recoup again on the file IDs that had problems. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP SEL command. RECP9009I RECOUP PHASE 1 ACTIVITY LOG DF RECOUP FIXED ERROR COUNT: errors
Explanation: The is the normal response to the ZRECP LOG command. This message is followed by a display of information from the current TPFDF recoup phase 1 or from the last time the TPFDF recoup utility was run. System Action: None. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility and the ZRECP LOG command. RECP9010I STATISTICS VALIDATION PARAMETERS
Explanation: This is the normal response to the ZRECP STA command with the VAL parameter and no search criteria parameters specified. This message is followed by a display of all possible search criteria parameters and conditions that can be used to select matching statistics. System Action: None. User Response: None. See TPFDF Utilities for more information about the ZRECP STA command. RECP9011I TPFDF RECOUP - ACTIVITY REPORT
Explanation: This display contains a status report for recoup activity. The status report is displayed at various times during recoup processing as well as in response to a ZRECP REPORT command during TPFDF recoup phase 1. System Action: None. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility and the ZRECP REPORT command. RECP9012I Where: ssu The subsystem user. cpuid The processor identifier (ID). fileid The file identifier (ID). ** SSU ssu SYSTEM cpuid ** ID fileid oldcount-OLD newcount-NEW ** TOTAL COUNT DISCREPANCY MORE THAN 20 PERCENT
82
RECP9013I RECP9016A
oldcount The old found count. newcount The new found count. Explanation: This message indicates that more than 20 percent of the original entries were lost during recoup processing. System Action: Processing continues. User Response: Do the following: 1. Verify that TPFDF recoup phase 1 processed correctly. 2. If necessary, run TPFDF recoup phase 1 again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. RECP9013I TPFDF RECOUP PRINTER ADDRESS SET UP
Explanation: This is a normal response to the ZRECP PRT command. System Action: None. User Response: None. See TPFDF Commands for more information about the ZRECP PRT command. RECP9014I Where: numssu The number of subsystem users. ss The subsystem name. numssu SSU DEFINITIONS IN SS ss
Explanation: During TPFDF recoup initial subsystem user (SSU) setup, the number of subsystem users in the subsystem running recoup is displayed. System Action: None. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. RECP9015I Where: dsect The DSECT name. ssu The subsystem user. Explanation: During TPFDF recoup processing, the subsystem user (SSU) that was displayed in the message attempted to access a file that is not available to (that is, excluded from) that SSU. A file can be excluded from an SSU with the EXCLUDE parameter on the DBDEF macro. System Action: TPFDF recoup processing continues. User Response: None. See TPFDF Database Administration for more information about the EXCLUDE parameter on the DBDEF macro. RECP9016A Where: errors The number of fixed file errors. Explanation: This message displays the number of errors found in fixed files when processing a TPF ZRECP SEL command during TPFDF recoup. System Action: None. Online Messages SEL RECOUP FIXED ERROR COUNT: errors RECORD STRUCTURE dsect EXCLUDED FROM SSU ssu
83
RECP9017I RECP9103E
User Response: Do one of the following: v If the number of fixed errors is zero, continue with recoup processing. v If the number of fixed errors is greater than zero, correct the errors and enter the TPF ZRECP SEL command to run selective recoup again. See TPFDF Utilities for more information about the TPFDF recoup utility. See TPF Operations and TPFDF Commands for more information about the TPF ZRECP SEL command. RECP9017I ZRECP STATISTICS DISPLAY
Explanation: This is the normal response to the ZRECP STA command. This message is followed by a display of statistical recoup information from TPFDF recoup runs. System Action: None. User Response: See TPFDF Commands for more information about the ZRECP STA command. RECP9101E BRC-INPUT FORMAT NOT VALID
Explanation: The format of the ZRECP command that you entered was not correct. System Action: The ZRECP command is rejected. User Response: Do the following: 1. Determine the correct format of the ZRECP command. 2. Enter the ZRECP command again and use the correct format. See TPFDF Commands for more information about the ZRECP commands. RECP9102E Where: fileid The file identifier (ID). filever The file version. Explanation: TPFDF recoup is ending because a TPF ZRECP ABORT command was entered. The file ID of the file being processed when the TPF ZRECP ABORT command was entered is displayed. System Action: TPFDF recoup ends. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPF Operations for more information about the TPF ZRECP ABORT command. RECP9103E Where: fileid The file identifier (ID). filever The file version. count The found record count. Explanation: A TPF ZRECP ABORT command was entered to end TPFDF recoup. The file ID of the file being processed when the TPF ZRECP ABORT command was entered is displayed. System Action: None. User Response: None. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPF Operations for more information about the TPF ZRECP ABORT command. DF RECOUP fileid filever TOTAL CHAIN CHASE POOLS FOUND BY THIS CPU: count DF RECOUP fileid filever TPFDF RECOUP ABORTED
84
RECP9104E RECP9106E
RECP9104E Where: fileid The file identifier (ID). filever The file version. Explanation: A chain chasing branch vector (CBV) value that was not valid was found during TPFDF recoup. System Action: TPFDF recoup ends. User Response: Do the following: 1. Ensure the value specified with the CBV parameter on the DBDEF macro is valid. 2. Run recoup again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPFDF Database Administration for more information about the CBV parameter on the DBDEF macro. RECP9105E Where: fileid The file identifier (ID). filever The file version. fileaddr The file address. Explanation: This error occurs when there is a loop in the forward chain field at the file address that is displayed in the message. System Action: The looping ECB exits. User Response: Do the following: 1. Enter a ZUDFM OA* command for this file ID to determine what forward chain field has the problem. 2. Enter the appropriate TPF command or ALCS command, such as ZAREC or ZAFIL, to correct the problem. 3. Run TPFDF recoup again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility and the ZUDFM commands. See TPF Operations for more information about the TPFcommands. See ALCS Operation and Maintenance for more information about the ALCS commands. RECP9106E Where: fileid The file identifier (ID). filever The file version. credcnt The outstanding entry control blocks (ECBs). Explanation: The time allowed for TPFDF recoup to process a particular file structure was exceeded. System Action: TPFDF recoup ends. User Response: Do one of the following: v Check the file chain that was being processed for loops in the forward chain fields and correct them accordingly. v Increase the maximum number of seconds allowed to process a file using the TIMEOUT parameter in the DBDEF macro. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPFDF Database Administration for more information about the TIMEOUT parameter on the DBDEF macro. DF RECOUP fileid filever MAIN MONITOR TIMEOUT NOT COMPLETE ECBS: credcnt DF RECOUP fileid filever LOOP ON FILE ADR: fileaddr DF RECOUP fileid filever INVALID BV / STP CBV
Online Messages
85
RECP9107E RECP9109E
RECP9107E Where: fileid The file identifier (ID). filever The file version. fileaddr The file address. Explanation: The time allowed for TPFDF recoup to process a particular file structure was exceeded. System Action: TPFDF recoup ends. User Response: Do one of the following: v Check the file chain that was being processed for loops in the forward chain fields and correct them accordingly. v Increase the maximum number of seconds allowed to process a file using the TIMEOUT parameter in the DBDEF. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPFDF Database Administration for more information about the TIMEOUT parameter on the DBDEF macro. RECP9108E BRC-STATISTIC FILE READ ERROR DF RECOUP fileid filever TIMEOUT FAD- fileaddr
Explanation: An error occurred when you entered a ZRECP STA command because the recoup statistics file, GR25SR (GR26SR), could not be accessed. System Action: The ZRECP STA command is rejected. User Response: Do the following: 1. Determine why the statistics file could not be accessed and correct the problem. 2. If you can recover the statistics file, enter the ZRECP STA command again. If you cannot recover the statistics file, go to step 3. 3. Determine if it is necessary to run the recoup utility again. If it is necessary, do the following: a. Enter ZUDFM OAINIT ID/FDF6, twice in succession, to reinitialize the recoup statistics index file, GR25SR. b. Run the recoup utility again. c. Enter the ZRECP STA command again. See TPFDF Commands and TPFDF Utilities for more information about the recoup utility and the ZRECP STA command. RECP9109E Where: ssu The subsystem user. type One of the following error types: v ID v RCC v SOFTWARE v HARDWARE. Explanation: When you entered a ZRECP command, an error was detected during recoup phase 1 chain chasing. This message is followed by a display that includes the following information: v The file identifier (ID) of the record that contains the file address of the referenced record, associated record code check (RCC), and file address. v The file ID of the referenced record, associated RCC, and file address. In addition, for ID-type errors, the file ID of the file for which TPFDF recoup was searching is displayed. For RCC-type errors, the RCC value of the file for which TPFDF recoup was searching is displayed. System Action: Recoup continues processing. User Response: When phase 1 ends, do the following: ssu RECOUP RETRIEVAL ERROR: type
86
RECP9110E RECP9114E
1. Correct the specified errors. 2. Enter a TPF ZRECP SEL command to process the ID with the errors again. See TPFDF Commands for more information about the TPFDF recoup utility. See TPF Operations and TPFDF Utilities for more information about the TPF ZRECP SEL command. RECP9110E PRINTER SPECIFICATION NOT VALID
Explanation: An error occurred when you entered a ZRECP PRT command because the specified printer address is not valid. System Action: The ZRECP PRT command is rejected. User Response: Enter the ZRECP PRT command again and specify a valid 6-digit printer address. See TPFDF Commands for more information about the ZRECP PRT command. RECP9111E INPUT MESSAGE NOT VALID
Explanation: An error occurred when you entered a ZRECP PRT command because the specified printer address is not valid. System Action: The ZRECP PRT command is rejected. User Response: Enter the ZRECP PRT command again and specify a valid 6-digit printer address. See TPFDF Commands for more information about the ZRECP PRT command. RECP9112E TPFDF RECOUP NOT ACTIVE - REQUEST IGNORED
Explanation: An error occurred when you entered a ZRECP REPORT command because TPFDF recoup phase 1 was not active. System Action: The ZRECP REPORT command is rejected. User Response: None. See TPFDF Commands for more information about the ZRECP REPORT command. RECP9113E Where: ssu The subsystem user. cpuid The processor identifier (ID). Explanation: An I/O error occurred while accessing the TPFDF recoup statistics file, GR25SR (GR26SR). System Action: TPFDF recoup processing ends. User Response: Do the following: 1. Enter ZUDFM OAINIT ID/FDF6, twice in succession, to reinitialize the recoup statistics index file, GR25SR. 2. Run TPFDF recoup again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility and the ZUDFM OAINIT command. RECP9114E Where: cpuid The processor identifier (ID). fileid The file identifier (ID). fileaddr The file address. item The item size. ** INVALID ITEM SIZE OR NAB - RECOUP CONTINUES - CORRECT RECORD ** SYSTEM cpuid ID fileid ADDR fileaddr ITS item NAB nab ** SSU ssu SYSTEM cpuid ** RECOUP STATISTIC FILE CORRUPTED - GR25SR/GR26SR
Online Messages
87
RECP9115E RECP9118E
nab The next available byte. Explanation: An error occurred during recoup processing because of one of the following conditions: v The item size in a logical record (LREC) is not valid. v The next available byte (NAB) field of an LREC is not valid. System Action: TPFDF recoup processing continues. User Response: Do the following: 1. Correct the item size or the NAB field for this record. 2. Run TPFDF recoup again, if necessary. RECP9115E Where: ssu The subsystem user. Explanation: An error occurred because the displayed subsystem user (SSU) was not started and is unable to receive messages. System Action: TPFDF recoup processing continues. User Response: Do the following: 1. Examine the receive-only (RO) computer room agent set (CRAS) output from the last TPF restart to determine why the SSU is dormant. 2. Correct any errors. See TPF Messages for details about the error messages and how to correct the errors. RECP9116E Where: ssu The subsystem user. Explanation: TPFDF recoup could not locate the specified subsystem user (SSU) in the subsystem user attribute table because the SSU was unavailable or not valid. System Action: TPFDF recoup processing ends. User Response: Do the following: 1. Ensure the specified SSU is valid and available. 2. If necessary, run TPFDF recoup again. RECP9117E Where: recid A 2-character alphanumeric or 4-character hexadecimal file ID. Explanation: The ZRECP STA command was entered, but a recoup subtable could not be found in the database definition (DBDEF) for the record ID specified. System Action: The ZRECP STA command is rejected. User Response: Do the following: 1. Verify that the correct record ID is specified. 2. Verify that the correct DBDEF for the record ID specified is loaded to the system. 3. Enter the ZRECP STA command again. See TPFDF Commands for more information about the ZRECP STA command. RECP9118E FILE ADDRESS NOT VALID FIXED FILE ADDRESS NO RECOUP INFORMATION FOR FILE STRUCTURE recid ssu MDBF SSU INFORMATION RETRIEVAL ERROR ssu SSU NOT PROCESSED DUE TO DORMANT STATUS
Explanation: An error occurred during TPFDF recoup when you entered a TPF ZRECP SEL command because the address specified was not a valid fixed file address. System Action: Processing for the current item is skipped.
88
RECP9119E RECP9122E
User Response: Enter the TPF ZRECP SEL command again and specify a valid fixed file address. See TPF Operations and TPFDF Commands for more information about the TPF ZRECP SEL command. RECP9119E Where: ssu The subsystem user. fileid The file identifier (ID). fvn The file version. fileaddr The file address. reg5val The contents of register 5 (R5), which is the actual next available byte (NAB) pointer. reg14val The contents of register 14 (R14), which is the item pointer. refnum The number of references for the current item. itemcnt The item count. Explanation: While processing a ZRECP command, TPFDF recoup detected a subitem count that was not valid during phase 1 chain chasing. System Action: TPFDF recoup processing steps to the next item in the table and continues processing. User Response: Do the following: 1. Correct the database definition (DBDEF) subitem count for this file ID. 2. If necessary, run TPFDF recoup again. See TPFDF Commands for more information about the ZRECP commands. RECP9122E FILE RETRIEVAL ERROR ON GR0ZSR SUBITEM ERROR. SSU: ssu,ID: fileid,FVN: fvn,FAD: fileaddr R5: reg5val,R14: reg14val,REF: refnum,CTL: itemcnt
Explanation: An error occurred when you entered a ZRECP LOG command because the command was entered incorrectly or the recoup logging file, GR0ZSR, could not be accessed. System Action: The ZRECP LOG command is rejected. User Response: Do one of the following v If the command was entered incorrectly, enter the command again using the correct parameters. Note: If you entered the PROC parameter, you may have specified a processor id that is not valid. v If the logging file could not be accessed, do the following: 1. Determine why the logging file could not be accessed and correct the problem. 2. If you can recover the logging file, enter the ZRECP LOG command again. 3. If you cannot recover the logging file, do the following: a. Enter ZUDFM OAINIT ID/FDF4, twice in succession, to reinitialize the recoup logging file. b. Run the recoup utility again, if necessary. c. Enter the ZRECP LOG command. See TPFDF Commands and TPFDF Utilities for more information about the recoup utility and the ZRECP LOG and ZUDFM OAINIT commands.
Online Messages
89
RECP9123I RECP9201E
RECP9123I RCI PROCESSING COMPLETED
Explanation: This is the normal response to the TPF ZRECP RECALL command without any other parameters specified when TPFDF recoup is running. TPFDF recoup has completed processing files defined as RCI. System Action: None. User Response: None. See TPF Operations and TPFDF Commands for more information about the TPF ZRECP RECALL command. RECP9124I RECOUP QUE-INDICATOR RESET
Explanation: This is the normal response to the ZRECP Q RESET command. System Action: None. User Response: None. See TPFDF Commands for more information about the ZRECP Q RESET command. RECP9198W Where: ssu The subsystem user. cpuid The processor identifier (ID). fileid The file identifier (ID). dsect The DSECT name. Explanation: A file ID referenced during TPFDF recoup processing is defined in the database definition (DBDEF) table but the record type defined in the DSECT for the file is not in the file address compute program (FACE) table. This display includes the subsystem user, CPU, file ID, and file DSECT name. System Action: TPFDF recoup processing continues. User Response: Do the following: 1. Ensure the record type defined in the DSECT macro for the file is included in the FACE table. 2. Run TPFDF recoup again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPF System Generation for information about how to add record types to the FACE table. RECP9201E Where: mis The maximum item size (MIS) defined in the DBDEF macro. This is the maximum size in bytes of the data area that will fit into a file block. cpuid The processor ID. id The file ID. ITEM IS LLR - SIZE MUST BE EQ MIS (mis) RECOUP CONTINUES - CORRECT RECORD SYSTEM cpuid ID id ADDR fileaddr ITS its NAB nab ssu SYSTEM cpuid ID fileid-dsect NOT IN FACE. TPFDF RECOUP CONTINUES.
fileaddr The file address of the block containing the LLR that has an error. its nab The displacement within the block of the next available byte (NAB). Explanation: An error occurred during TPFDF recoup because the item size (ITS) for the open MLL was not equal to the MIS minus the cloaked header. System Action: Processing for the current item is skipped and recoup processing continues for the next item. The item size is the actual size of the open master large logical record (MLL) data area.
90
RECP9202E UDFC0001I
User Response: Do the following: 1. Correct the problem by doing one of the following: v If the LLR is type 1, correct the size value at location (initial NAB + #LLRHDR1) to the value (MIS - #LLRHDR1). v If the LLR is type 2, correct the size value at location (initial NAB + #LLRHDR2) to the value (MIS - #LLRHDR2). The values of #LLRHDR1 and #LLRHDR2 are found in the IMLLDF DSECT. 2. Run TPFDF recoup again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPFDF Database Administration for more information about LLR block structure. RECP9202E Where: mnb The maximum next available byte (MNB). cpuid The processor ID. id The file ID. ITEM IS LLR - NAB MUST BE EQ MNB (mnb) RECOUP CONTINUES - CORRECT RECORD SYSTEM cpuid ID id ADDR fileaddr ITS its NAB nab
fileaddr The file address. its nab The displacement within the block of the next available byte (NAB). Explanation: An error occurred during TPFDF recoup when the item size (ITS) of an LLR is not equal to the MNB. System Action: Processing for the current item is skipped and TPFDF recoup processing continues for the next item. User Response: Do the following: 1. Change the NAB to the value (initial NAB + MIS). 2. Run TPFDF recoup again. See TPFDF Commands and TPFDF Utilities for more information about the TPFDF recoup utility. See TPFDF Database Administration for more information about LLR block structure. The large logical record (LLR) item size.
UDFC
UDFC0000I TPFDF DATA COLLECTION
Explanation: This is a normal message from the ZUDFC DISPLAY command. This message is followed by a display of the TPFDF data collection statistics. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC DISPLAY command. UDFC0001I Where: cpuid The processor identifier (ID). Explanation: This is a normal message from the ZUDFC START command. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC START command. DATA COLLECTION STARTED ON PROCESSOR cpuid
Online Messages
91
UDFC0002I UDFC0007I
UDFC0002I Where: cpuid The processor identifier (ID). Explanation: This is a normal message from the ZUDFC STOP command. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC STOP command. UDFC0003I DATA COLLECTION STOPPED DATA COLLECTION STOPPED ON PROCESSOR cpuid
Explanation: This is a normal message from the ZUDFC STOP command with the MODE-FORCE parameter specified. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC STOP command. UDFC0004I TPFDF DATA COLLECTION HELP
Explanation: This is the normal response to the ZUDFC HELP command. This message is followed by a display of help information for the ZUDFC commands. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC HELP command. UDFC0005I TPFDF DATA COLLECTION STATISTICS HELP
Explanation: This is the normal response to the ZUDFC HELP command with the CMD or MAC parameter specified. This message is followed by a list of all the searchable TPFDF or TPF macros. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC HELP command. UDFC0006I Where: ssu The subsystem user name. Explanation: This is the normal response to the ZUDFC STATUS command. This message indicates that data collection is active for the subsystem user (SSU) indicated. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC STATUS command. See TPFDF Utilities for more information about data collection. UDFC0007I Where: ss The subsystem name. DATA COLLECTION IS ACTIVE ON ALL SSUs for SS ss DATA COLLECTION IS ACTIVE ON SSU ssu
Explanation: This is the normal response to the ZUDFC STATUS command. This message indicates that data collection is active on all subsystem users (SSUs) for a specific subsystem. System Action: None. User Response: None.
92
UDFC0008I UDFC0013E
See TPFDF Commands for more information about the ZUDFC STATUS command. See TPFDF Utilities for more information about data collection. UDFC0008I DATA COLLECTION IS NOT ACTIVE
Explanation: This is the normal response to the ZUDFC STATUS command. This message indicates that data collection is not active on this processor in a non-loosely coupled environment, or is not active on this processor in a loosely coupled environment. If you are using the multiple database function (MDBF), this means that data collection is not active on any subsystem users (SSUs) for the current subsystem. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC STATUS command. See TPFDF Utilities for more information about data collection. UDFC0010E DATA COLLECTION ALREADY ACTIVE
Explanation: The ZUDFC START command was entered but data collection is already active. Only one data collection can run at a time. System Action: The ZUDFC START command is rejected. User Response: Do one of the following: v Wait for the current data collection to complete processing and enter the ZUDFC START command again. v Enter the ZUDFC STOP command to stop the current data collection and then enter the ZUDFC START command again. See TPFDF Commands for more information about the ZUDFC START and ZUDFC STOP commands. UDFC0011E DATA COLLECTION NOT RUNNING
Explanation: The ZUDFC STOP command was entered but data collection is not active. System Action: The ZUDFC STOP command is rejected. User Response: None. See TPFDF Commands for more information about the ZUDFC STOP command. UDFC0012E SYSTEM NOT IN NORM STATE
Explanation: A ZUDFC command was entered but the system was not in NORM state. The system must be in NORM state to enter ZUDFC commands. System Action: The ZUDFC command is rejected. User Response: Do the following: 1. Cycle the system to NORM state. 2. Enter the ZUDFC command again. See TPFDF Commands for more information about the ZUDFC commands. UDFC0013E NOT MDBF ENVIRONMENT
Explanation: A ZUDFC command was entered in a non-multiple database function (MDBF) environment or an ALCS environment with the SSU-ALL parameter specified. The SSU-ALL parameter can be used only in an MDBF environment. System Action: The ZUDFC command is rejected. User Response: Enter the ZUDFC command again without specifying the SSU-ALL parameter. See TPFDF Commands for more information about the ZUDFC commands.
Online Messages
93
UDFC0014E UDFC0017E
UDFC0014E NOT HPO ENVIRONMENT
Explanation: A ZUDFC command was entered in a non-loosely coupled environment or an ALCS environment with the PROCESSOR-ALL parameter specified. The PROCESSOR-ALL parameter can be used only in loosely coupled environments. System Action: The ZUDFC command is rejected. User Response: Enter the ZUDFC command again without specifying the PROCESSOR-ALL parameter. See TPFDF Commands for more information about the ZUDFC commands. UDFC0015E Where: cpuid The processor identifier (ID). Explanation: A ZUDFC command was entered with the PROCESSOR-ALL parameter specified, but the processor displayed in the message did not respond. System Action: The ZUDFC command is not processed on the processor displayed in the message. User Response: Determine why the processor displayed in the message did not respond. If you attempt to start data collection on all processors, you may need to stop and restart data collection on all processors to compile complete totals for the TPF loosely coupled complex. See TPFDF Commands for more information about the ZUDFC commands. UDFC0016E Where: cpuid The processor identifier (ID). Explanation: The ZUDFC START command with the PROCESSOR-ALL parameter specified was entered to start data collection on all processors, but data collection is already active on the processor displayed in the message. System Action: The ZUDFC START command is not processed on the processor displayed in the message. User Response: Do one of the following: v If data collection was already started on all processors by entering the ZUDFC START command with the PROCESSOR-ALL parameter specified, there is no more action for you to take. v If data collection was not already started on all processors by entering the ZUDFC START command with the PROCESSOR-ALL parameter specified, the TPF loosely coupled complex totals will not be complete. For complete totals: 1. Enter the ZUDFC STOP command to stop data collection on all processors. 2. Enter the ZUDFC START command with the PROCESSOR-ALL parameter specified to start data collection on all processors. See TPFDF Commands for more information about the ZUDFC START and ZUDFC STOP commands. UDFC0017E Where: cpuid The processor identifier (ID). Explanation: One of the following occurred: v For a TPF system, the ZUDFC STOP command was entered to stop data collection but data collection is already inactive on the processor displayed in the message. v For an ALCS environment, the ZUDFC STOP command was entered to stop data collection but data collection is already inactive. System Action: The ZUDFC STOP command is not processed on the processor displayed in the message. User Response: Do one of the following: v If data collection was already stopped on all processors by entering the ZUDFC STOP command with the MODE-ALL parameter specified, there is no more action for you to take. v If data collection was not already stopped on all processors by entering the ZUDFC STOP command with the MODE-ALL parameter specified, complex totals will not be built. To build these totals: DATA COLLECTION NOT ACTIVE ON PROCESSOR cpuid DATA COLLECTION ALREADY ACTIVE ON PROCESSOR cpuid NO RESPONSE FROM PROCESSOR cpuid
94
UDFC0018E UDFC0022E
1. Enter the ZUDFC START command with the PROCESSOR-ALL parameter specified to start data collection on all processors. 2. Enter the ZUDFC STOP command with the MODE-ALL parameter specified to stop data collection on all processors. See TPFDF Commands for more information about the ZUDFC START and ZUDFC STOP commands. UDFC0018E ID SPECIFIED NOT DEFINED IN SYSTEM
Explanation: An error occurred when processing a ZUDFC DISPLAY command because there is no database definition (DBDEF) information for the specified file ID. System Action: The ZUDFC DISPLAY command is rejected. User Response: Enter the ZUDFC DISPLAY command again and specify an ID that is defined in the DBDEF tables. See TPFDF Commands for more information about the ZUDFC DISPLAY command. UDFC0019E NO STATISTICS FOR GIVEN ID
Explanation: A ZUDFC DISPLAY command was entered but the statistics file does not contain any data collection information for the specified file ID. System Action: The ZUDFC DISPLAY command is rejected. User Response: Do one of the following: v If you specified the correct file ID on the ZUDFC DISPLAY command, there are no statistics and there is no more action for you to take. v If you specified an incorrect file ID on the ZUDFC DISPLAY command, enter the command again and specify the correct file ID. See TPFDF Commands for more information about the ZUDFC DISPLAY command. UDFC0020E ID SPECIFIED NOT A TPFDF FILE
Explanation: An error occurred when you entered a ZUDFC DISPLAY command because the file ID specified is a traditional (P-type) file. Data collection is available only with TPFDF files. System Action: The ZUDFC DISPLAY command is rejected. User Response: Enter the ZUDFC DISPLAY command again and specify a file ID for a TPFDF file. See TPFDF Commands for more information about the ZUDFC DISPLAY command. UDFC0021E PARAMETER NOT RECOGNIZED
Explanation: A ZUDFC command was entered with an incorrect parameter. System Action: The ZUDFC command is rejected. User Response: Do the following: 1. Determine the correct format of the ZUDFC command. 2. Enter the ZUDFC command again and use the correct format. See TPFDF Commands for more information about the ZUDFC commands. UDFC0022E INCORRECT TIME DEFINITION
Explanation: An error occurred when you entered a ZUDFC START command with the TIME parameter specified. The value specified with the TIME parameter must be a decimal number from 160. System Action: The ZUDFC START command is rejected. User Response: Enter the ZUDFC START command again and specify a valid value for the TIME parameter. See TPFDF Commands for more information about the ZUDFC START command.
Online Messages
95
UDFC0023E UDFC0030E
UDFC0023E TIMED STOP OF DATA COLLECTION CANCELLED
Explanation: A ZUDFC START command was entered with the TIME parameter specified to stop data collection at a specified time interval. However, the request to stop data collection at the specified time interval was canceled because of a sequence number mismatch in the data collection keypoint. This can occur if you enter a ZUDFC STOP command and then enter a ZUDFC START command again in the specified time interval. System Action: Data collection processing continues. User Response: Enter a ZUDFC STOP command to stop data collection manually. See TPFDF Commands for more information about the ZUDFC START and ZUDFC STOP commands. UDFC0024I DATA COLLECTION SEARCH STARTED
Explanation: This is the normal response to the ZUDFC DISPLAY command with the CMD, MAC, or CRIT parameter specified. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFC DISPLAY command. UDFC0025E NO STATISTICS MATCHING SELECTION CRITERIA
Explanation: A ZUDFC DISPLAY command was entered, but the statistics file does not contain any data collection information for the file ID or selection criteria specified. System Action: The ZUDFC DISPLAY command is rejected. User Response: Do one of the following: v If you specified the correct file ID or selection criteria on the ZUDFC DISPLAY command, there are no statistics and there is no more action for you to take. v If you specified an incorrect file ID or selection criteria on the ZUDFC DISPLAY command, enter the command again and specify the correct information. See TPFDF Commands for more information about the ZUDFC DISPLAY command. UDFC0030E FILE AND CORE INDICATORS DO NOT MATCH
Explanation: This message indicates that there is a mismatch between the core and the file indicators. System Action: None. User Response: Do the following: 1. Enter ZUDFC STOP MODE-FORCE 2. Do one of the following: v If you are running on a TPF system, enter ZADCA DBC 0 00 Note: If running in a loosely coupled environment , enter the ZUDFC STATUS command from each processor and enter the ZADCA command on each processor that generates this error. v If you are running in an ALCS environment, do the following: a. Enter ZUDFM ACCESS FDE4 b. Enter ZUDFM DISPLAY. c. Look for the processor ID where data collection is running in the fourth byte of data in each row. When the matching processor ID is found, note the logical record (LREC) number in the first column. d. Enter ZUDFM DEL lrecnum, where lrecnum is the LREC number identified in step 2c. See TPFDF Commands for more information about the ZUDFC STOP and ZUDFM commands. See TPF Operations for more information about the ZADCA command.
96
UDFC0050E UDFC0053E
UDFC0050E DATA COLLECTION AREA NOT DEFINED
Explanation: An error occurred when you entered a ZUDFC START command because a data collection area has not been defined on the system. System Action: The ZUDFC START command is rejected. User Response: Do one of the following: v If you are running in a TPF environment, do the following: 1. Ensure that segment CT24 is loaded correctly in the TPF system and has code generated to allocate a data collection area. 2. Enter the ZUDFC START command again. v If you are running in an ALCS environment, do the following: 1. Ensure that segment DXCUSR is loaded correctly in the ALCS environment and has code generated to allocate a data collection area. 2. Enter the ZUDFC START command again. See TPFDF Commands for more information about the ZUDFC START command. UDFC0051E TPFDF ERROR IN FILE IRDKDF
Explanation: One of the following occurred: v A problem was found with the data collection keypoint file, IRDKDF, when you entered a ZUDFC START or ZUDFC STOP command. v A problem was found with the data collection keypoint file, IRDKDF, while cleaning up the data collection tables after reaching NORM state. System Action: One of the following: v The ZUDFC START or ZUDFC STOP command is rejected. v The data collection tables are not initialized. User Response: Do the following: 1. Examine keypoint file IRDKDF to determine the cause of the problem. 2. If the file error cannot be corrected, do the following: a. Enter ZUDFM OAINIT ID/FDE4, twice in succession, to reinitialize the keypoint file. b. Enter a ZUDFC STOP command with the MODE-FORCE parameter specified to clean up data collection. See TPFDF Commands for more information about the ZUDFC START and ZUDFC STOP commands. UDFC0052E READ ERROR ON STATISTICS FILE
Explanation: A read error occurred on the data collection statistics file, IRDCDF (IRDIDF), when you entered a ZUDFC DISPLAY or a ZUDFC STOP command. System Action: The ZUDFC DISPLAY or ZUDFC STOP command is rejected. User Response: Do the following: 1. Examine the data collection statistics file, IRDCDF, and the data collection statistics index file, IRDIDF, to determine the cause of the problem. 2. If you cannot correct the cause of the problem, do the following: a. Enter ZUDFM OAINIT ID/FDE5, twice in succession, to reinitialize the data collection statistics index file, IRDIDF. b. Enter the ZUDFC STOP command with the MODE-FORCE parameter specified to clean up data collection. See TPFDF Commands for more information about the ZUDFC DISPLAY and ZUDFC STOP commands. UDFC0053E WRITE ERROR ON STATISTICS FILE
Explanation: A write error occurred on the data collection statistics file, IRDCDF (IRDIDF), when you entered a ZUDFC DISPLAY or a ZUDFC STOP command. System Action: The ZUDFC DISPLAY or ZUDFC STOP command is rejected. User Response: Do the following:
Online Messages
97
UDFC0054E UDFC0099E
1. Examine the data collection statistics file, IRDCDF, and the data collection statistics index file, IRDIDF, to determine the cause of the problem. 2. If you cannot correct the cause of the problem, do the following: a. Enter ZUDFM OAINIT ID/FDE5, twice in succession, to reinitialize the data collection statistics index file, IRDIDF. b. Enter the ZUDFC STOP command with the MODE-FORCE parameter specified to clean up data collection. See TPFDF Commands for more information about the ZUDFC DISPLAY and ZUDFC STOP commands. UDFC0054E TPFDF ERROR IN FILE IWDWDF
Explanation: A problem was found with the data collection display work file, IWDWDF, when you entered a ZUDFC DISPLAY or ZUDFC HELP command. System Action: The ZUDFC DISPLAY or ZUDFC HELP command is rejected. User Response: Do the following: 1. Determine the cause of the problem. 2. If you cannot correct the file error, do the following: a. Enter ZUDFM OAINIT ID/FDC0, twice in succession, to reinitialize file IWDWDF. b. Enter the ZUDFC STOP command with the MODE-FORCE parameter specified to clean up data collection. See TPFDF Commands for more information about the ZUDFC DISPLAY, ZUDFC HELP, and ZUDFC STOP commands. UDFC0059E DATA COLLECTION AREA NEEDS ENLARGING
Explanation: An error occurred when you entered a ZUDFC START because the space reserved for TPFDF data collection is full. System Action: The ZUDFC START command is rejected. User Response: Do one of the following: v If you are running in a TPF environment, do the following: 1. Ensure that CCCTIN has been assembled and loaded in the TPF system since the last time the file ID range changed. 2. Enter the ZUDFC START command again. v If you are running in an ALCS environment, do the following: 1. Ensure that DXCUSR has been assembled and loaded in the ALCS environment since the last time the file ID range changed. 2. Enter the ZUDFC START command again. See TPFDF Commands for more information about the ZUDFC START command. UDFC0098E Where: msgnum A hexadecimal value in R0 that represents the incorrect message number. Explanation: An unrecognized message number was passed to data collection message processor segment UFE2. System Action: Processing continues. User Response: Report the problem to your IBM service representative. UDFC0099E Where: casenum A hexadecimal value in R1 that represents the incorrect case number. Explanation: An unrecognized case number was passed to the data collection message processor, segment UFE2. System Action: Processing continues. User Response: Report the problem to your IBM service representative. INVALID CASE NUMBER IN R1 - R1- casenum INVALID MSG NUMBER IN R0 - R0- msgnum
98
UDFM0001I UDFM0121E
UDFM
UDFM0001I Where: fileaddr The file address. Explanation: This is the normal response to ZUDFM commands that display the contents of a subfile. This message is followed by a display of the contents of the subfile that has the file address that is shown in the display. If a large logical record (LLR) is displayed, see TPFDF Database Administration for more information about the LLR structure. System Action: None. User Response: None. See TPFDF Commands for more information about ZUDFM commands. UDFM0002I TPFDF BLOCK HEADER DISPLAY TPFDF LREC DISPLAY F.A. fileaddr
Explanation: This is the normal response to the ZUDFM OA* command with the D/HDR or H/HDR parameter specified. This message is followed by a display of the subfile block header in character or hexadecimal format. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OA* command. UDFM0119I UFB - EMPTY SUBFILE RELEASED BY AUTO DE-INDEX
Explanation: A ZUDFM command was entered to delete the last logical record (LREC) of a subfile that has AUTODEINDEX=YES specified in the database definition (DBDEF). The subfile was de-indexed and released. Further modifications with the ZUDFM command are inhibited. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM commands. See TPFDF Database Administration for more information about the DBDEF macro. UDFM0120W Where: fileid The file ID. cfaddr The current file address. pfaddr The prime file address. Explanation: ZUDFM command processing could not be completed because the record code check (RCC) of the linked pool subfile indicates that the subfile has been released by the TPFDF product. Further modifications with ZUDFM commands are inhibited. System Action: The ZUDFM command is rejected. User Response: Determine whether the pool subfile was supposed to be released. If it was not supposed to be released, determine why it was released. See TPFDF Commands for more information about the ZUDFM commands. UDFM0121E Where: fileid The file identifier (ID). UFB-FILE CORRUPTED ID-fileid RCC-rcc CFA-cfaddr PFA-pfaddr UFB - FILE RELEASED ID-fileid RCC-01 CFA-cfaddr PFA-pfaddr
Online Messages
99
UDFM0122E UDFM0125E
rcc The record code check. cfaddr The current file address. pfaddr The prime file address. Explanation: The ZUDFM command cannot be completed because of a data integrity error such as a mismatched file ID, file address, or record code check. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Determine the cause of the error and correct it. 2. Enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0122E UFB-MODIFICATION - SEQ DISCREPANCY
Explanation: A ZUDFM command could not be processed because the record sequence number in the subfile being modified may have changed since the last ZUDFM OA* command was entered. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Enter a ZUDFM OA* command to display the logical record (LREC) that you want to modify. 2. Enter the original ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0123E UFB-DISPLAY AND REENTER
Explanation: An error occurred when you entered a ZUDFM command because the file to which you are currently linked cannot be accessed. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Enter a ZUDFM OA or ZUDFM OAI command to display or link to the file again. 2. Enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0124E UFB-ENTRY NOT ALLOWED ON THIS CRT
Explanation: An error occurred when you entered a ZUDFM command because the current terminal does not have authorization for this command. System Action: The ZUDFM command is rejected. User Response: Do one of the following: v Enter the ZUDFM command again from a terminal that has authorization. v Enter the ZUDFM OAE command with the A parameter specified to add the terminal to the restricted command table and enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0125E UFB-GENERAL FILE SUPPORT NOT INSTALLED
Explanation: An error occurred when you entered a ZUDFM command for a G-type file because the TPFDF product does not have general data set support. System Action: The ZUDFM command is rejected. User Response: Report the problem to your IBM service representative.
100
UDFM0126E UDFM0130E
See TPFDF Commands for more information about the ZUDFM commands. UDFM0126E UFB-ITEM NOT IN TABLE
Explanation: An error occurred when you entered a ZUDFM command in an attempt to access a record that does not exist. This can occur if: v The file ID is not defined in the database definition (DBDEF) table. v An attempt was made to delete an entry from the restricted command table or ID restriction table but the entry does not exist. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Ensure that the file ID specified on the ZUDFM command is correct and is loaded in the system. 2. Enter the ZUDFM command again and specify a correct file ID or entry for the appropriate restricted table. See TPFDF Commands for more information about the ZUDFM commands. UDFM0127E UFB-NOT PRIME RECORD
Explanation: An error occurred when you entered a ZUDFM command for an overflow block. The command can be processed for an overflow block when the current file pointer contains the address of the prime block. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Link to the prime block. 2. Enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0128E UFB-INPUT FORMAT NOT VALID
Explanation: The format of the ZUDFM command that you entered was not correct. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Determine the correct format of the ZUDFM command. 2. Enter the ZUDFM command again and use the correct format. See TPFDF Commands for more information about the ZUDFM commands. UDFM0129E UFB-FILE RETRIEVAL ERROR
Explanation: An error occurred when you entered a ZUDFM command because the TPFDF product was unable to read from system files GR0YSR, GR25SR (GR26SR), or GR32SR. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Check the relevant files for data corruption and correct the problem. 2. Enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0130E UFB-UNABLE TO PROCESS
Explanation: An error occurred when you entered a ZUDFM command because you did not specify enough information. System Action: The ZUDFM command is rejected. User Response: Do one of the following: v If the error was caused by a ZUDFM TRACE command, do the following: 1. Trace a TPFDF application until one or more files are open. 2. Enter the ZUDFM TRACE command again. Online Messages
101
UDFM0131E UDFM0135E
v Determine the correct format of the ZUDFM command and enter the command again by using the correct format. See TPFDF Commands for more information about the ZUDFM commands. UDFM0131E UFB-FILE ADDRESS OR ID NOT VALID
Explanation: An error occurred when you entered a ZUDFM command. The file address or the file identifier (ID) specified is not valid. System Action: The ZUDFM command is rejected. User Response: Enter the ZUDFM command again and specify a valid file address or file ID. See TPFDF Commands for more information about the ZUDFM commands. UDFM0132E UFB-LINE NUMBER NOT VALID
Explanation: An error occurred when you entered a ZUDFM command with a line number that is not valid or that is from an outdated display. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Enter a ZUDFM OA or ZUDFM OAI command to display or link to the file again. 2. Enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0133E UFB-KEY SEQUENCE NOT VALID
Explanation: An error occurred when you entered a ZUDFM command with keys specified. The keys specified on a ZUDFM command must be sequential, starting with key 1, and there can be a maximum of six keys. System Action: The ZUDFM command is rejected. User Response: Enter the ZUDFM command again ensuring that no more than six keys are specified and that they are sequential. See TPFDF Commands for more information about the ZUDFM commands. UDFM0134E UFB-ERROR IN R- PARAMETER
Explanation: An error occurred when you entered a ZUDFM OA* command with the R parameter specified. This can occur if: v The value specified with the R parameter was not valid. v The file currently linked, using the ZUDFM command, could not be located in the macro label set (MLS) database. System Action: The ZUDFM OA* command is rejected. User Response: Do one of the following: v Enter the ZUDFM OA* command again and specify a valid value for the R parameter. v If the file currently linked is correct, add the file to the MLS database. v If the currently linked file is not correct, enter a ZUDFM command to link the correct file. See TPFDF Commands for more information about the ZUDFM commands and macro label set (MLS) support. UDFM0135E UFB-COMPARISON TYPE NOT VALID
Explanation: An error occurred when you entered a ZUDFM OA* command with the C parameter specified. The value that you specified with the C parameter is not correct. System Action: The ZUDFM OA* command is rejected. User Response: Enter the ZUDFM OA* command again and specify a correct value for the C parameter. See TPFDF Commands for more information about the ZUDFM OA* command.
102
UDFM0136E UDFM0140E
UDFM0136E UFB-ORGANIZATION NOT VALID
Explanation: An error occurred when you entered a ZUDFM OA* command with the O parameter specified. The organization that you specified for the O parameter is not correct. System Action: The ZUDFM OA* command is rejected. User Response: Enter the ZUDFM OA* command again and specify a correct value for the O parameter. See TPFDF Commands for more information about the ZUDFM OA* command. UDFM0137E UFB-PARAMETER COMBINATION NOT VALID
Explanation: An error occurred when you entered a ZUDFM OA* command with the KEYn parameter specified. You must specify the S or M parameter to display LRECs using keys. System Action: The ZUDFM OA* command is rejected. User Response: Enter the ZUDFM OA* command again and specify the S or M parameter. See TPFDF Commands for more information about the ZUDFM OA* command. UDFM0138E UFB-MAXIMUM LENGTH FOR S- EXCEEDED/49 BYTES
Explanation: An error occurred when you entered a ZUDFM OA* command with the KEYn and S parameters specified. The value that you specified for the S parameter is too long. System Action: The ZUDFM OA* command is rejected. User Response: Enter the ZUDFM OA* command again and specify a value for the S parameter that is no more than 49 bytes in length. See TPFDF Commands for more information about the ZUDFM OA* command. UDFM0139E UFB-NOT TPFDF TYPE RECORD
Explanation: An error occurred when you entered a ZUDFM command because the file being accessed is one of the following: v A traditional (P-type) file v Corrupted v Not recognized by the TPFDF product. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Ensure the file being accessed is a valid TPFDF file. 2. Enter the ZUDFM command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0140E Where: fileid The file identifier (ID). Explanation: An error occurred reading the header in a B+Tree index when processing a ZUDFM OA* command with the T parameter specified. System Action: The ZUDFM OA* command is rejected and the ECB exits. User Response: Do the following: 1. Correct the header problem. 2. Enter the ZUDFM OA* command with the T parameter specified again. See TPFDF Commands for more information about the ZUDFM OA* command. FILE ID fileid - ERROR READING HEADER
Online Messages
103
UDFM0141E UDFM0181E
UDFM0141E LLR REPLACE IN PROGRESS - TRY AGAIN
Explanation: An error occurred when you entered the ZUDFM OA* command with the LR parameter specified because a replace on the specified large logical record (LLR) is in progress. System Action: The ZUDFM OA* command is rejected. User Response: Enter the ZUDFM OA* command again. See TPFDF Commands for more information about the ZUDFM OA* command. See TPFDF Database Administration for more information about the LLR block structure. UDFM0142E ERROR DURING LLIB RETRIEVAL
Explanation: An error occurred when you entered the ZUDFM OA* command with the LR parameter specified because of a data integrity error of the LLIB such as a mismatched file ID, file address, or record code check. System Action: The ZUDFM OA* command is rejected. User Response: Do the following: 1. Determine the cause of the LLIB retrieval error and correct it. 2. Enter the ZUDFM OA command again. See TPFDF Commands for more information about the ZUDFM OA* command. See TPFDF Database Administration for more information about the LLR block structure. UDFM0161E UFB-ADD - NO LINES - DEFAULT KEYS
Explanation: This error occurs when you enter a ZUDFM OAA command with a sequence number specified for a file that has default keys defined. System Action: The ZUDFM OAA command is rejected. User Response: Do one of the following: v If the file currently linked is correct, enter the ZUDFM OAA command again and do not specify the sequence number. v If the currently linked file is not correct, enter a ZUDFM command to link the correct file and enter the ZUDFM OAA command again. See TPFDF Commands for more information about the ZUDFM commands. UDFM0162E UFB-OAA/ NOT ALLOWED FOR ALGORITHM #TPFDB0D
Explanation: An error occurred when you entered a ZUDFM OAA command to add a logical record (LREC) to a file that uses algorithm #TPFDB0D because the sequence number was not specified. The LREC sequence number is required to indicate the location to which the record will be added. System Action: The ZUDFM OAA command is rejected. User Response: Enter the ZUDFM OAA command again and specify the LREC sequence number. See TPFDF Commands for more information about the ZUDFM OAA command. UDFM0170E LABEL REPLACE NOT ALLOWED IF LLR
Explanation: An error occurred when you entered a ZUDFM OAR command with the LBL parameter specified for a large logical record (LLR). The LBL parameter is not allowed for an LLR. System Action: The ZUDFM OAR command is rejected. User Response: Do not use the ZUDFM OAR command with the LBL parameter specified for an LLR. See TPFDF Commands for more information about the ZUDFM OAR command. UDFM0181E UFB-INCORRECT FILE ADDRESS
Explanation: An error occurred when you entered a ZUDFM OAC command because the specified file address is incorrect. System Action: The ZUDFM OAC command is rejected. User Response: Enter the ZUDFM OAC command again and specify a valid 4-byte or 8-byte file address.
104
UDFM0182E UDFM0191I
See TPFDF Commands for more information about the ZUDFM OAC command. UDFM0182E UFB-PROTECTED AREA FOR COPY
Explanation: An error occurred when you entered a ZUDFM OAC command. Data cannot be written to the file address that you specified as the target address because the address is in protected storage. System Action: The ZUDFM OAC command is rejected. User Response: Do the following: 1. Select a different target file address. 2. Enter the ZUDFM OAC command again. See TPFDF Commands for more information about the ZUDFM OAC command. UDFM0183A ** ATTENTION ** CONTENT OF COPY-TO-ADDRESS
Explanation: This is the normal response to the ZUDFM OAC command. This message is displayed as a precaution against overwriting data. System Action: None. User Response: Enter the ZUDFM OAC command again to copy the specified file. UDFM0184I Where: fileaddr The file address. Explanation: This is the normal response to the ZUDFM OAB command. This message is followed by a display of detailed information about the block trailer for the file. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAB command. UDFM0185E UFB - NO TRAILER INFORMATION OR EMPTY TRAILER TPFDF BLOCK TRAILER INFORMATION F.A. fileaddr
Explanation: An error occurred when you entered a ZUDFM OAB command because there was no trailer information to display for this file. System Action: The ZUDFM OAB command is rejected. User Response: None. See TPFDF Commands for more information about the ZUDFM OAB command. UDFM0186E DECB CREATE ERROR
Explanation: An error occurred when you entered a ZUDFM command because a data event control block (DECB) could not be created. System Action: The ZUDFM command is rejected. User Response: Report the problem to your IBM service representative. UDFM0191I DISPLAY IN PROGRESS
Explanation: This is the response to the ZUDFM OA* command when the specified file display is in progress too long. The value specified on the #DFOATOV symbol in the ACPDBE macro determines how often this message is issued until the original ZUDFM OA* command is completed. System Action: The original ZUDFM OA* display is not affected and the results are displayed upon completion. User Response: If this behavior occurs often, code SEQUPDT=YES on the DBDEF for that file to ensure that the ZUDFM OA* commands are processed quickly.
Online Messages
105
UDFM0201I UDFM0241I
Coding SEQUPDT=YES on the DBDEF for the file may require additional input/output (I/O) each time the file is modified because the prime block will always be filed to ensure that the sequence number was updated. When SEQUPDT=NO is coded, the prime block is only filed when it is updated. You will need to determine whether it is more important to have fewer I/Os when updating the file or to have faster ZUDFM displays. If you choose to leave SEQUPDT=NO coded on the DBDEF, you can change the frequency of this message by altering the #DFOATOV symbol. See TPFDF Commands for more information about the ZUDFM OA* command and TPFDF Installation and Customization for more information about the ACPDBE macro. UDFM0201I OA - ENTRY RESTRICTION TABLE DISPLAY
Explanation: This is the normal response to the ZUDFM OAE command with the * parameter specified. This message is followed by a display of which ZUDFM entries are restricted to specific terminal addresses. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAE command. UDFM0221I Where: fileaddr The file address. fileid The file identifier (ID). rcc The record code check. Explanation: This is the normal response to the ZUDFM OAF command. This message is followed by a display of the chaining information for the specified subfile. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAF command. UDFM0230W MAXIMUM CHAIN COUNT EXCEEDED - DISPLAY HALTED AT 500 FCH F.A. fileaddr ID fileid RCC rcc
Explanation: The ZUDFM OAF command could not list all chains because the chain count exceeded 500, which is the maximum limit. System Action: The display shows the first 500 chains and stops. User Response: Enter a TPF ZDFIL command or ALCS ZDFIL command to display additional chains if necessary. See TPFDF Commands for more information about the ZUDFM OAF command. See TPF Operations for more information about the TPF ZDFIL command. See ALCS Operation and Maintenance for more information about the ALCS ZDFIL command. UDFM0231E FCH-ADDRESS EQUAL TO CURRENT BLOCK ADDRESS
Explanation: While processing a ZUDFM OAF command, a forward chain address was found that was the same as the current block address. System Action: The chaining information that was gathered before the error occurred is displayed and processing of the ZUDFM OAF command stops. User Response: Enter a TPF ZAFIL command or ALCS ZAFIL command to repair the incorrect forward chain. See TPFDF Commands for more information about the ZUDFM OAF command. See TPF Operations for more information about the TPF ZAFIL command. See ALCS Operation and Maintenance for more information about the ALCS ZAFIL command. UDFM0241I SYSTEM HELP UTILITY -- ZUDFM
Explanation: This is the normal response to the ZUDFM OAH command. This message is followed by a display of the parameters that are allowed with the ZUDFM OAH command. System Action: None.
106
UDFM0242I UDFM0251E
User Response: None. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0242I HELP UTILITY - PROGRAM REFERENCES
Explanation: This is the normal response to the ZUDFM OAH command with the REF parameter. This message is followed by a display of the parameters that are allowed with the ZUDFM OAH command. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0243I Where: command ZUDFM command description The description of the ZUDFM command. Explanation: This is the normal response to the ZUDFM OAH command. This message is followed by a display of the parameters that are allowed with the ZUDFM command displayed in the message. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0244I HLP-DATA BASE BUILT TPFDF HELP FACILITY O A - H E L P - command description
Explanation: This is the normal response to the ZUDFM OAH command with the INIT parameter specified. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0250A HLP-DATA BASE NOT SET UP
Explanation: An error occurred when you entered a ZUDFM OAH command because the TPFDF help database was not initialized. System Action: The ZUDFM OAH command is rejected. User Response: Do the following: 1. Enter ZUDFM OAHINIT to initialize the TPFDF help database. 2. Enter the ZUDFM OAH command again. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0251E HLP-INPUT FORMAT NOT VALID
Explanation: The format of the ZUDFM OAH command that you entered was not correct. System Action: The ZUDFM OAH command is rejected. User Response: Do the following: 1. Determine the correct format of the ZUDFM OAH command. 2. Enter the ZUDFM OAH command again and use the correct format. See TPFDF Commands for more information about the ZUDFM OAH command.
Online Messages
107
UDFM0252E UDFM0302I
UDFM0252E HLP-DATA BASE CORRUPT - RETR. ERR
Explanation: An error occurred when you entered a ZUDFM OAH command because the TPFDF help function index file, GR28SR, is corrupted. System Action: The ZUDFM OAH command is rejected. User Response: Do the following 1. Enter ZUDFM OAINIT ID/FDF7, twice in succession, to initialize the TPFDF help function index file. 2. Enter ZUDFM OAHINIT to initialize the ZUDFM help utility. 3. Enter the ZUDFM OAH command again. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0253E HLP-SUB-DISPLAY NUMBER NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAH command with an incorrect command number. System Action: The ZUDFM OAH command is rejected. User Response: Do the following: 1. Determine the correct number of the ZUDFM command for which you want to display help. 2. Enter the ZUDFM OAH command again and specify the correct number. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0254E HLP-SUB-DISPLAY ENTRY NOT VALID
Explanation: One of the following occurred: v The format of the ZUDFM OAH command that you entered was not correct. v The TPFDF help database is not initialized. System Action: The ZUDFM OAH command is rejected. User Response: Do one of the following: v Determine the correct format of the ZUDFM OAH command and enter the command again and use the correct format. v Enter ZUDFM OAHINIT to initialize the TPFDF help database. See TPFDF Commands for more information about the ZUDFM OAH command. UDFM0301I FILE INFORMATION DISPLAY
Explanation: This is the normal response to the ZUDFM OAI command. This message is followed by a display of detailed information about the file. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0302I CENTRAL DATA - FILE DEFINITIONS
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command. This message is followed by a display of DBDEF parameter settings for a specific file or for all files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command.
108
UDFM0303I UDFM0309I
UDFM0303I UFB-CENTRAL DESCRIPTOR INITIALIZED
Explanation: This is a normal message from the ZUDFM OAI/DBTAB command with the INIT parameter specified. This message indicates that the database definition (DBDEF) tables were successfully rebuilt using the DBDEFs. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0304I COMMON DESCRIPTION
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the COM parameter specified. This message is followed by a display of detailed information about the specified file or for all files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0305I TPFDF TABLE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the DBG parameter specified. This message is followed by a display of the contents of the database definition (DBDEF) table for the specified file or for all files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0306I KEY TABLE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the DBK parameter specified. This message is followed by a display of the default keys that are defined for the specified file or for all files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0307I DBDEF INDEX SUBTABLE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the IDX parameter specified. This message is followed by a display of the database definition (DBDEF) index table for the specified file or for all files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0308I PROGRAM REFERENCE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the PGN parameter specified. This message is followed by a display of the program that contains the database definition (DBDEF) for a specified file or for all files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0309I RECOUP TABLE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the REC parameter specified. This message is followed by a display of the recoup information for the specified files or for all files. System Action: None.
Online Messages
109
UDFM0310I UDFM0315I
User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0310I FORWARD REFERENCE OF INDEXED FILE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the REF parameter specified. This message is followed by a display of the file IDs that are referenced from a file used in an index structure. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0311I BACKREFERENCE OF INDEXED FILE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the BRF parameter specified. This message is followed by a display of the file IDs that are referenced from a file used in an index structure. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0312I DBDEF SUBTABLE COUNT DISPLAY
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the CNT parameter specified. This message is followed by a display of the number of each type of subtable. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0313I DISPLAY OF OPTIONBITS IN SW02SR
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the OPT parameter specified. This message is followed by a display of the option bit settings for the database definition (DBDEF) of the specified file. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0314I TPFDF FAST-LINK AREA DISPLAY
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the LINK parameter specified. This message is followed by a display of the TPFDF fast-link storage area. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0315I UFB-WID-RESTRICTION TABLE MODIFIED
Explanation: This is the normal response when modifying the ID restriction table by entering the ZUDFM OAI/DBTAB command with the WID parameter specified. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command.
110
UDFM0316I UDFM0321I
UDFM0316I IDENTIFIER USAGE BY APPLICATION
Explanation: This is the normal response to the ZUDFM OAI command with the WID and APL parameters specified. This message is followed by a display of all IDs that are used by the specified application. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0317I ALREADY USED ID-S
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the DID parameter specified. This message is followed by a list of the IDs that are being used in the database definition (DBDEF) tables. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0318I ID RESTRICTION TABLE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the WID and DIS parameters specified. This message is followed by a display of the IDs that each application is using in the ID restriction table. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0319I Where: appl The application. filecat The file category. Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the WID and NEW parameters. This message is followed by a list of the subsequent IDs for the specified application and type. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0320I DATA LABEL COLLECTION INDEX NEXT ID-S FOR APPLICATION appl AND TYPE filecat ARE:
Explanation: This is the normal response to the ZUDFM OAI command with the FILE parameter specified and no specified file. This message is followed by a display of the list of files that have macro label set support (MLS) entries generated. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0321I DATA MACRO LABEL COLLECTION
Explanation: This is the normal response to the ZUDFM OAI command with the FILE parameter specified and a specified file. This message is followed by a display of the data elements used in the specified file. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI command.
Online Messages
111
UDFM0322I UDFM0341E
UDFM0322I TPFDF FILE RELATION TABLE BUILD STARTED
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the REL and CREATE parameters specified. This message indicates that initialization of the ID relationship table has started. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0323I TPFDF FILE RELATION TABLE BUILD ENDED
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the REL and CREATE parameters specified. This message indicates that initialization of the ID relationship table has been completed. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0324I Where: fileid The file identifier (ID). dsect The DSECT name. Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the REL parameter specified. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0327I TPFDF FAST-LINK DIRECTORY BUILD COMPLETE RELATIONS FOR ID-fileid FILE-dsect
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the INIT parameter specified on the Airline Control System (ALCS) when the system is in idle state. System Action: The TPFDF fast-link table is built. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0328I TPFDF FAST-LINK DIRECTORY NOT BUILT - NOT IN IDLE
Explanation: This is the normal response to the ZUDFM OAI/DBTAB command with the INIT parameter specified on the Airline Control System (ALCS) when the system is in a state other than idle state. System Action: The TPFDF fast-link table is not built. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0341E UFB-ALG- STRING ALREADY INDEXED
Explanation: An error occurred when you entered a ZUDFM OAI command with the CREATE and ALG parameters specified to create a detail pool subfile. The algorithm specified for the ALG parameter was the same algorithm for a previously created detail pool subfile. System Action: The ZUDFM OAI command is rejected. User Response: Do the following: v If you specified the correct algorithm on the ZUDFM OAI command, a detail pool subfile for that algorithm already exists and there is no more action for you to take.
112
UDFM0342E UDFM0346E
v If you specified an incorrect algorithm on the ZUDFM OAI command, enter the command again and specify a different algorithm. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0342E Where: fileid The file identifier (ID). Explanation: An error occurred when you entered a ZUDFM OAI/DBTAB command with the COM, DBG, DBK, IDX, OPT, PGN, or REC parameter specified. This occurs if the specified file ID is not defined in the database definition (DBDEF) table, or if there are no entries in the specified subtable for this file ID. System Action: The ZUDFM OAI/DBTAB command is rejected. User Response: Do the following: 1. Ensure that the appropriate file ID is correctly loaded in the system. 2. Enter the ZUDFM OAI/DBTAB command again and specify the correct file ID. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0343E UFB-ID NOT FOUND IN DB DESCRIPTOR TABLE ID fileid NOT IN DBTAB OR NO SUBTABLE INFO
Explanation: An error occurred when you entered a ZUDFM OAI command with the FILE parameter specified because the specified file ID could not be located in the database definition (DBDEF) table. System Action: The ZUDFM OAI command is rejected. User Response: Do the following: 1. Ensure that the appropriate file ID is correctly loaded in the system. 2. Enter the ZUDFM OAI command again and specify the correct file ID. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0344E UFB-GIVEN ALG/ORD/PTH NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAI command because the specified algorithm, ordinal, partition, interleave, or path is not valid or is out of range. System Action: The ZUDFM OAI command is rejected. User Response: Do the following: 1. Determine the correct format for the ZUDFM OAI command. 2. Enter the ZUDFM OAI command again and use the correct format. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0345E UFB-ID RANGE NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAI/DBTAB command with the WID parameter specified because the file ID or range of file IDs is not valid. This can occur if you specify a hexadecimal file ID or if a character in the specified file ID is not valid. System Action: The ZUDFM OAI/DBTAB command is rejected. User Response: Enter the ZUDFM OAI/DBTABcommand again and specify a valid file ID. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0346E UFB-REQUEST NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAI/DBTAB command with the WID parameter specified. An unrecognized parameter was specified. System Action: The ZUDFM OAI/DBTAB command is rejected.
Online Messages
113
UDFM0347E UDFM0351E
User Response: Do the following: 1. Determine the correct format for the ZUDFM OAI/DBTAB command. 2. Enter the ZUDFM OAI/DBTAB command again and use the correct format. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0347E UFB-ITEM ALREADY IN TABLE
Explanation: An error occurred when you entered a ZUDFM OAI/DBTAB command with the WID and ADD parameters specified to add a record to the ID restriction table. The specified record already existed in the table. System Action: The ZUDFM OAI/DBTAB command is rejected. User Response: Do one of the following: v If you specified the correct record, the entry already exists in the ID restriction table and there is no more action for you to take. v If you specified an incorrect record, enter the ZUDFM OAI/DBTAB command again and specify the correct record to add to the ID restriction table. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0348E UFB-MULTIPLE OF 2 BYTES FOR HEX ORD
Explanation: An error occurred when you entered a ZUDFM OAI command with the ORDX parameter specified because the number of digits specified for the hexadecimal ordinal value was not valid. The hexadecimal ordinal on the ORDX parameter must be an even number of bytes (that is, a multiple of 2). System Action: The ZUDFM OAI command is rejected. User Response: Enter the ZUDFM OAI command again and specify an even number of hexadecimal digits for the ORDX parameter. Use leading zeros if necessary. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0349E UFB-NOT ALLOWED FOR POOL/WORK FILES
Explanation: An error occurred when you entered a ZUDFM OAI command for a pool or W-type file. System Action: The ZUDFM OAI command is rejected. User Response: Enter the ZUDFM OAI command again and specify a file ID that is not a pool file or W-type file. See TPFDF Commands for more information about the ZUDFM OAI command. UDFM0350E UNABLE TO PROCESS - RELATION TABLE REQUIRES INITIALIZATION
Explanation: An error occurred when you entered a ZUDFM OAI/DBTAB command for a file ID with the REL parameter specified. The required ID relationship files were not previously initialized. System Action: The ZUDFM OAI/DBTAB command is rejected. User Response: Do the following: 1. Enter ZUDFM OAINIT ID/FDA5, twice in succession, to reinitialize the ID relation table index. 2. Enter ZUDFM OAI/DBTAB/REL/CREATE to build the ID relation table. 3. Enter the ZUDFM OAI/DBTAB command again. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB and ZUDFM OAINIT commands. UDFM0351E TPFDF FILE RELATION TABLE BUILD ERROR
Explanation: An error occurred after entering a ZUDFM OAI/DBTAB command with the REL and CREATE parameters specified. A problem occurred when building the IRA5DF file. System Action: The ZUDFM OAI/DBTAB command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command.
114
UDFM0352E UDFM0356W
UDFM0352E Where: fileid1 The file identifier (ID) referenced from fileid2. fileid2 The file identifier (ID) entered on the ZUDFM command. Explanation: An error occurred when you entered a ZUDFM command. The error occurred because the fileid1 or fileid2 reference is not found in the DBDEF, which caused an inconsistent DBDEF file reference. System Action: The ZUDFM command is rejected. User Response: Report the problem to your database administrator. See TPFDF Commands for more information about the ZUDFM commands. UDFM0353E UNABLE TO PROCESS - FILE RETRIEVAL ERROR TPFDF FILE RELATION TABLE BUILD ERROR, INVALID REFERENCE fileid1 FROM fileid2.
Explanation: An error occurred when you entered a ZUDFM command because the ID relationship table is corrupted. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Enter ZUDFM OAI/DBTAB/REL/CREATE to rebuild the ID relationship table. 2. If the error persists, report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM commands. UDFM0354E UNABLE TO PROCESS - FILE ID NOT DEFINED
Explanation: An error occurred when you entered a ZUDFM command because the file ID specified is not in the central database definition tables. System Action: The ZUDFM command is rejected. User Response: Do the following: 1. Ensure the file is defined in the database definition and that the database definition is loaded in the system. 2. Enter the ZUDFM command again and specify the file ID correctly. See TPFDF Commands for more information about the ZUDFM commands. UDFM0355E UNABLE TO OBTAIN HEAP STORAGE
Explanation: The ZUDFM OAI/DBTAB command was entered, but an error occurred because there are limited system resources available. System Action: The command is rejected. User Response: Do the following: 1. Enter the TPF ZSYSL and ZSTAT commands to check the system resources and determine whether the system is shutting down. 2. Enter the ZUDFM OAI/DBTAB command again when resources become available. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. See TPF Operations for more information about the ZSYSL and ZSTAT commands. UDFM0356W Where: detailFile The file ID of the detail file DBDEF with the ALGINFOID parameter specified. algInfoFile The file ID of the referenced algorithm information file. Explanation: During DBDEF table initialization (either during restart or by entering a ZUDFM OAI/DBTABcommand with the INIT detailFile DBDEF SPECIFIES UNKNOWN DBDEF IN ALGINFOID=algInfoFile
Online Messages
115
UDFM0357W UDFM0359I
parameter specified), a DBDEF was found that uses the ALGINFOID parameter to specify an algorithm information file. However, a DBDEF for the algorithm information file was not found. System Action: DBDEF table initialization continues. User Response: Correct the mismatch in the DBDEFs so that the DBDEF referenced by the ALGINFOID parameter exists and contains an ALGINFOFOR parameter for the referencing DBDEF. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. See TPFDF Database Administration for more information about the DBDEF macro. UDFM0357W Where: algInfoFile The file ID of the algorithm information file whose DBDEF is missing the ALGINFOFOR parameter. detailFile The file ID of the detail file DBDEF with the ALGINFOID parameter specified. Explanation: During DBDEF table initialization (either during restart or by entering a ZUDFM OAI/DBTAB command with the INIT parameter specified), a DBDEF was found that uses the ALGINFOID parameter to specify an algorithm information file. However, the algorithm information file DBDEF did not specify the ALGINFOFOR parameter. System Action: DBDEF table initialization continues. User Response: Correct the mismatch in the DBDEFs so that the DBDEF referenced by the ALGINFOID parameter contains an ALGINFOFOR parameter for the referencing DBDEF. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. See TPFDF Database Administration for more information about the DBDEF macro. UDFM0358W Where: algInfoFile The file ID of the algorithm information file referenced by the detail file. detailFile The file ID of the detail file whose DBDEF references the algorithm information file with the ALGINFOID parameter. Explanation: During DBDEF table initialization (either during restart or by entering a ZUDFM OAI/DBTAB command with the INIT parameter specified), a DBDEF was found that uses the ALGINFOID parameter to specify an algorithm information file. However, the algorithm information file DBDEF specified the ALGINFOFOR parameter for a DBDEF other than that of the detail file. System Action: DBDEF table initialization continues. User Response: Correct the mismatch in the DBDEFs so that the DBDEF referenced by the ALGINFOID parameter contains an ALGINFOFOR parameter for the referencing DBDEF. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. See TPFDF Database Administration for more information about the DBDEF macro. UDFM0359I Where: algInfoFile The file ID of the algorithm information file that uses the ALGINFOFOR parameter to reference a detail file. detailFile The file ID of the detail file that is specified by the ALGINFOFOR parameter in the algorithm information file. Explanation: During DBDEF table initialization (either during restart or by entering a ZUDFM OAI/DBTAB command with the INIT parameter specified), a DBDEF was found for an algorithm information file that specified a corresponding detail file using the ALGINFOFOR parameter. However, a DBDEF for the detail file was not found. System Action: DBDEF table initialization continues. User Response: Correct the mismatch in the DBDEFs so that the DBDEF referenced by the ALGINFOFOR parameter contains an ALGINFOID parameter for the referencing DBDEF. ALG INFO FILE algInfoFile USES UNKNOWN DBDEF IN ALGINFOFOR=detailFile ALG INFO FILE algInfoFile DOES NOT REFERENCE detailFile ALG INFO FILE algInfoFile, REFERENCED BY detailFile, MISSING ALGINFOFOR=
116
UDFM0360I UDFM0380I
See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. See TPFDF Database Administration for more information about the DBDEF macro. UDFM0360I Where: detailFile The file ID of the detail file that is specified by the ALGINFOFOR parameter in the algorithm information file. algInfoFile The file ID of the algorithm information file that is not referenced by the detail file. Explanation: During DBDEF table initialization (either during restart or by entering a ZUDFM OAI/DBTAB command with the INIT parameter specified), a DBDEF was found for an algorithm information file. However, the DBDEF referenced by the ALGINFOFOR parameter in the algorithm information file does not use the ALGINFOID parameter to specify an algorithm information file. System Action: DBDEF table initialization continues. User Response: Correct the mismatch in the DBDEFs such that the DBDEF referenced by the ALGINFOID parameter contains an ALGINFOFOR parameter for the referencing DBDEF. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. See TPFDF Database Administration for more information about the DBDEF macro. UDFM0361I Where: algInfoFile The file ID of the algorithm information file that is not referenced by the detail file. detailFile The file ID of the detail file that is specified by the ALGINFOFOR parameter in the algorithm information file. Explanation: During DBDEF table initialization (either during restart or by entering a ZUDFM OAI/DBTAB command with the INIT parameter specified), a DBDEF was found for an algorithm information file using the ALGINFOFOR parameter. However, the detail file uses the ALGINFOID parameter to reference a different algorithm information file. System Action: DBDEF table initialization continues. User Response: Correct the mismatch in the DBDEFs such that the DBDEF referenced by the ALGINFOID parameter contains an ALGINFOFOR parameter for the referencing DBDEF. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command. UDFM0380I Where: fileid The file identifier (ID). filever The file version. begord The beginning absolute ordinal number. endord The ending absolute ordinal number. facetype The FACE type. ssu Subsystem user. Explanation: This is the normal response to the ZUDFM OAINIT command. System Action: This message is followed by message UDFM0381A. User Response: Examine the information to ensure you are initializing the correct file. See TPFDF Commands for more information about the ZUDFM OAINIT command. Online Messages YOU WILL INITIALIZE THE FOLLOWING FILE ID - fileid FVN - filever BOR - begord EOR - endord FACET facetype SSU - ssu ALG INFO FILE algInfoFile IS NOT REFERENCED BY detailFile. DETAIL FILE detailFile, REFERENCED BY algInfoFile, MISSING ALGINFOID=
117
UDFM0381A UDFM0393E
UDFM0381A DANGEROUS ENTRY / MAKE SURE: 1 - YOU KNOW WHAT YOU ARE DOING 2 - YOU HAVE A RECENT CAPTURE AT HAND 3 - THE FILE YOU ARE ABOUT TO INITIALIZE IS PROPERLY DEFINED IN DBDEF 4 - THE SYSTEM IS NOT IN TOO BAD A SHAPE IF YOU STILL WANT TO INITIALIZE YOUR FILE REPEAT YOUR ENTRY WITHIN 2 MINUTES
Explanation: This is the normal response to the ZUDFM OAINIT command. System Action: None. User Response: Enter the ZUDFM OAINIT command again to initialize the specified file. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0383I Where: fileid The file identifier (ID). filever The file version. ordnum The number of ordinals processed. Explanation: This is the normal response to the ZUDFM OAINIT command. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0391E INPUT FORMAT NOT VALID ZUDFM DATABASE INITIALIZATION COMPLETE ID - fileid FVN - filever ORDS PROC - ordnum
Explanation: The format of the ZUDFM OAINIT command that you entered was not correct. This message is followed by a display of valid formats for this command. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Determine the correct format of the ZUDFM OAINIT command. 2. Enter the ZUDFM OAINIT command again and use the correct format. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0392E FILE ID NOT VALID
Explanation: The file ID specified on the ZUDFM OAINIT command is not valid. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again and specify a valid 2-byte character or hexadecimal file ID. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0393E FVN MUST BE 2 BYTES HEX
Explanation: The file version specified on the ZUDFM OAINIT command is not valid. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again and specify a valid 2-byte file version. See TPFDF Commands for more information about the ZUDFM OAINIT command.
118
UDFM0394E UDFM0400E
UDFM0394E NUMERIC VALUE NOT VALID
Explanation: An error occurred when you entered the ZUDFM OAINIT command because the value specified for the beginning of the ordinal range is not valid. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again and specify a valid beginning ordinal number. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0395E EOR MUST BE NUMERIC OR /LAST/
Explanation: An error occurred when you entered the ZUDFM OAINIT command because the value specified for the end of the ordinal range is not valid. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again and specify a valid ending ordinal number or a value of LAST. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0397E OAINIT NOT ALLOWED WHEN RECOUP IS RUNNING
Explanation: An error occurred when you entered a ZUDFM OAINIT command because recoup is running. You cannot enter the ZUDFM OAINIT command during recoup. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Wait until TPFDF recoup ends. 2. Enter the ZUDFM OAINIT command again. See TPFDF Commands and TPFDF Utilities for more information about the ZUDFM OAINIT command and the TPFDF recoup utility. UDFM0398E REQUEST FROM OTHER TERMINAL ALREADY PENDING
Explanation: An error occurred when you entered a ZUDFM OAINIT command because another initialization request is being processed. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Wait for the outstanding initialization request to be processed. 2. Enter the ZUDFM OAINIT command again. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0399E ENTRIES MUST BE EQUAL / PLEASE START OVER
Explanation: An error occurred when you entered the ZUDFM OAINIT command because the specified file ID does not match the file ID specified on the previous ZUDFM OAINIT command. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again, twice in succession, and specify the same file ID. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0400E INIT TIME OUT / START OVER
Explanation: An error occurred when you entered a ZUDFM OAINIT command because more than 2 minutes has passed since you entered the previous ZUDFM OAINIT command. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again, twice in succession. See TPFDF Commands for more information about the ZUDFM OAINIT command.
Online Messages
119
UDFM0401E UDFM0405E
UDFM0401E OTHER REQ TIMEOUT / PLS REPEAT ENTRY TWICE
Explanation: An error occurred when you entered a ZUDFM OAINIT command because more than 2 minutes has passed since you entered the previous ZUDFM OAINIT command. This message occurs when you enter the second ZUDFM OAINIT command from a different terminal. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again, twice in succession. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0402E OTHER REQ ALREADY PEND / GO FOR COFFEE
Explanation: An error occurred when you entered a ZUDFM OAINIT command because a previous initialization request (ZUDFM OAINIT) is being processed. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Wait for the previous request to complete processing. 2. Enter the ZUDFM OAINIT command again. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0403E NOT FIXED RECORD THIS ID / FVN PLS CHECK
Explanation: An error occurred when you entered a ZUDFM OAINIT command because the specified file ID is not a fixed file. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again and specify a valid fixed file ID. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0404E ID / FVN NOT DEFINED IN DBDEF CONTACT YOUR DB SUPPORT GROUP
Explanation: An error occurred when you entered a ZUDFM OAINIT command because the specified file is not defined in any database definition (DBDEF) that is loaded in the system. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Ensure the file is defined in the database definition and that the database definition is loaded in the system. 2. Enter the ZUDFM OAINIT command again and specify the correct file ID. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0405E FACE ERROR ON ZUDFM INIT MAKE SURE THAT THE FACE TABLE FOR YOUR FILE IS CORRECTLY SET UP
Explanation: An error occurred when you entered a ZUDFM OAINIT command because the specified file ID could not be accessed. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Ensure the file address compute program (FACE) table for the file ID you specified is set up correctly. 2. Ensure the ordinal specified is in the range allowed in the FACE table for this file ID. 3. Enter the ZUDFM OAINIT command again. See TPFDF Commands for more information about the ZUDFM OAINIT command.
120
UDFM0406E UDFM0421I
UDFM0406E FIND ERROR CHECKING RECORD MAKE SURE THAT THE DISKS ARE PROPERLY FORMATTED
Explanation: An error occurred when you entered a ZUDFM OAINIT command because the specified file ID could not be accessed. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Ensure the file address compute program (FACE) table for the file ID you specified is set up correctly. 2. Enter the ZUDFM OAINIT command again. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0407E UNABLE TO PROCESS / DATA BASE CORRUPT
Explanation: An error occurred when you entered a ZUDFM OAINIT command. This can occur if the file address compute program (FACE) table is not set up correctly or if the TPFDF initialization control file, GR31SR, is corrupted. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Ensure the FACE table for the file ID you specified is set up correctly. 2. Ensure that file GR31SR is not corrupted. 3. Enter the ZUDFM OAINIT command again. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0408E ORDINAL RANGE NOT VALID
Explanation: An error occurred when you entered the ZUDFM OAINIT command because the value specified for the ordinal range is not valid. System Action: The ZUDFM OAINIT command is rejected. User Response: Enter the ZUDFM OAINIT command again, twice in succession, and specify a valid ordinal number range. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0409E UFB - INV MSG IND FOR OAINIT / CTC TPFDF-SUPPORT
Explanation: A logic error in segment UFD3 was found when processing a ZUDFM OAINIT command. System Action: None. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAINIT command. UDFM0410E ZUDFM INIT NOT ALLOWED WHEN CRUISE IS RUNNING
Explanation: An error occurred when you entered a ZUDFM OAINIT command because the capture/restore utility, information and statistics environment (CRUISE) is in running state. System Action: The ZUDFM OAINIT command is rejected. User Response: Do the following: 1. Wait until CRUISE parameter table processing ends. 2. Enter the ZUDFM OAINIT command again. See TPFDF Commands and TPFDF Utilities for more information about the ZUDFM OAINIT command and CRUISE. UDFM0421I OA MODIFICATION LOG DISPLAY
Explanation: This is the normal response to the ZUDFM OAL command with no additional parameters specified or with the *LOG parameter specified. This message is followed by a display of the ZUDFM commands contained in the log file. System Action: None.
Online Messages
121
UDFM0461E UDFM0465E
User Response: None. See TPFDF Commands for more information about the ZUDFM OAL command. UDFM0461E UFB-OAR - MLS DATABASE CORRUPTED
Explanation: An error occurred when you entered a ZUDFM OAR command because the macro label set (MLS) database is corrupted. System Action: The ZUDFM OAR command is rejected. User Response: Do the following: 1. Load the MLS tape again to rebuild the MLS database. 2. Enter the ZUDFM OAR command again. See TPFDF Commands for more information about the ZUDFM OAR command. UDFM0462E UFB-OAR - LABEL SPECIFICATION NOT VALID
Explanation: An error occurred entering a ZUDFM OAR command because the specified label is missing or not valid. System Action: The ZUDFM OAR command is rejected. User Response: Enter the ZUDFM OAR command again and specify a valid label. See TPFDF Commands for more information about the ZUDFM OAR command. UDFM0463E Where: label The DSECT field. Explanation: An error occurred when you entered a ZUDFM OAR command because the specified label is not defined in the macro label set (MLS). System Action: The ZUDFM OAR command is rejected. User Response: Do the following: 1. Enter the ZUDFM OAI command with the FILE parameter to verify that the label is correct. 2. Enter the ZUDFM OAR command again and specify the correct label. See TPFDF Commands for more information about the ZUDFM OAR and ZUDFM OAI commands. UDFM0464E UFB-OAR - NOT ALLOWED WITH DEFAULT KEYS UFB-OAR- LABEL NOT FOUND ON MACRO LABEL SET: label
Explanation: An error occurred when you entered a ZUDFM OAR command for a file that has default keys defined. The ZUDFM OAR command is not allowed with default keys. System Action: The ZUDFM OAR command is rejected. User Response: None. See TPFDF Commands for more information about the ZUDFM OAR command. UDFM0465E UFB-SIZ-FIELD NOT ALLOWED FOR OAR
Explanation: An error occurred when you entered a ZUDFM OAR command because the label specified is for the size field of the logical record (LREC). The size field cannot be changed. System Action: The ZUDFM OAR command is rejected. User Response: Do the following: 1. Verify the label of the field for which you want to change the data. 2. Enter the ZUDFM OAR command again and specify the correct label. See TPFDF Commands for more information about the ZUDFM OAR command.
122
UDFM0466E UDFM0475E
UDFM0466E UFB-LABEL/DATA-LENGTH DISCREPANCY
Explanation: An error occurred when you entered a ZUDFM OAR command because the length of the field specified does not match the length of the field as defined to the macro label set. System Action: The ZUDFM OAR command is rejected. User Response: Do the following: 1. Ensure that the number of bytes of data for the field to be replaced matches the number of bytes defined in the DSECT and the macro label set. 2. Enter the ZUDFM OAR command again and specify the correct number of bytes. See TPFDF Commands for more information about the ZUDFM OAR command. UDFM0467E UFB-LABEL-DISPLACEMENT ERROR
Explanation: An error occurred when you entered a ZUDFM OAR command because there is a discrepancy between the label displacement and the total length of the item. The total length of the item must always be greater than the label displacement. System Action: The ZUDFM OAR command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAR command. UDFM0472I SSTR - SPECIAL OPTIONS DISPLAY
Explanation: This is the normal response to the ZUDFM OAS command with the OPS parameter specified. This message is followed by a display of the SW00SR option bytes. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0473E UFB-DATA BLOCK NOT YET RETRIEVED
Explanation: An error occurred when you entered a ZUDFM OAS command because the data block could not be retrieved for display. System Action: The ZUDFM OAS command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0474E UFB-NO SW-BLOCK FOUND FOR THIS REF
Explanation: An error occurred when you entered a ZUDFM OAS command because a SW00SR block could not be obtained for the referenced file. System Action: The ZUDFM OAS command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0475E UFB-SW00SR EVM CORE ADDRESS NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAS command because the target entry control block (ECB) is not active or the ECB/EVM address is not valid. System Action: The ZUDFM OAS command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAS command.
Online Messages
123
UDFM0476E UDFM0480E
UDFM0476E UFB-STEP TRACE LINKAGE NOT AVAILABLE
Explanation: An error occurred when you entered a ZUDFM OAS command because trace support was not defined with the &ACPDBST variable in the DBLCL macro. System Action: The ZUDFM OAS command is rejected. User Response: If trace support is available, do the following: 1. Modify the &ACPDBST variable in the DBLCL macro. 2. Assemble the appropriate segments again. 3. Enter the ZUDFM OAS command again. See TPFDF Installation and Customization for more information about the &ACPDBST variable and DBLCL macro. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0477E UFB-NOT SW00SR BASE AT GIVEN LOCATION
Explanation: An error occurred when you entered a ZUDFM OAS command because the base of the SW00SR DSECT was not located at the specified address. System Action: The ZUDFM OAS command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAS commands. UDFM0478E UFB-NO LOGICAL LREC LOCATED
Explanation: An error occurred when you entered a ZUDFM OAS command because a valid logical record (LREC) was not found while attempting to display the current LREC during trace. System Action: The ZUDFM OAS command is rejected. User Response: Do the following: 1. Ensure that the current LREC is valid. 2. Enter the ZUDFM OAS command again. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0479E UFB-ITEM SIZE IN DATA BLOCK NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAS command because a variable-size logical record (LREC) was found that does not have a valid size. The size either exceeds the maximum LREC size or is less than or equal to zero. System Action: The ZUDFM OAS command is rejected. User Response: Do the following: 1. Check the integrity of the data. 2. Enter the ZUDFM OAS command again. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0480E UFB-LABEL INFORMATION OUTSIDE RANGE - DISPLAY INCOMPLETE
Explanation: An error occurred when you entered a ZUDFM OAS command with the LBL parameter specified for the following reasons: v The label information was not found in the macro label set (MLS) database. v The label does not exist in the current logical record (LREC). v Label HDR or REC was included on an extended LREC. v The label information or its data is not in the range of the data area for the current block. System Action: The ZUDFM OAS command displays the appropriate error message. User Response: Do one of the following: v Ensure that the label specified is defined in the MLS database. v Ensure that the label specified is valid for the current LREC.
124
UDFM0481I UDFM0495E
v Ensure that labels HDR and REC are not included on an extended LREC. v Ensure that the specified label and its data are within the data area of the current block. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0481I MACRO LABEL SET - TAPELOAD STATISTICS
Explanation: This is the normal response to the ZUDFM OAT command with the *LOG parameter. This message is followed by a display of the tape load statistics for macro label set support. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0482I TAPELOAD STARTED
Explanation: This is a normal response from the ZUDFM OAT command. This message indicates the beginning of the tape load. System Action: The system begins to load the tape, or prompts you to mount the tape for input. User Response: If prompted, mount the tape for input. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0483I TAPELOAD ENDED
Explanation: This is a normal response from the ZUDFM OAT command. This message indicates the end of the tape load. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0494E ERROR ACCESSING FILE GR3NSR
Explanation: An error occurred when you entered a ZUDFM OAT command because the macro label set (MLS) detail file, GR3NSR, could not be accessed. System Action: The ZUDFM OAT command is rejected. User Response: Do the following: 1. Determine why the MLS detail file could not be accessed and correct the problem. 2. If you can recover the MLS detail file, enter the ZUDFM OAT command again. If you cannot recover the MLS detail file, go to 3. 3. Do the following: a. Enter ZUDFM OAINIT ID/FDF3, twice in succession, to reinitialize the MLS index file, GR3MSR. b. Enter the ZUDFM OAT command again. See TPFDF Commands for more information about the ZUDFM OAT and ZUDFM OAINIT commands. UDFM0495E TAPELOAD WITH BAD RETURN
Explanation: An error occurred while loading to DASD when processing a ZUDFM OAT command. System Action: The ZUDFM OAT command is rejected. User Response: Report the problem to your IBM service representative. See TPFDF Commands for more information about the ZUDFM OAT command.
Online Messages
125
UDFM0496E UDFM0501I
UDFM0496E TAPEREAD WITH BAD RETURN
Explanation: An error occurred while doing a tape read when processing a ZUDFM OAT command. System Action: The ZUDFM OAT command is rejected. User Response: Do one of the following: v Verify that the correct tape is mounted and enter the ZUDFM OAT command again. v Check the tape device for a possible hardware problem. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0497E TIMEOUT OCCURRED
Explanation: When processing a ZUDFM OAT command, the tape load timed out after 2 minutes while waiting until all slave entry control block (ECB)s were finished. System Action: The ZUDFM OAT command is rejected. User Response: Do the following: 1. Determine why the ECBs did not complete processing. 2. Enter the ZUDFM OAT command again. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0498E IMG NOT CORRECT
Explanation: The format of the ZUDFM OAT command that you entered was not correct. System Action: The ZUDFM OAT command is rejected. User Response: Do the following: 1. Determine the correct format for the ZUDFM OAT command. 2. Enter the ZUDFM OAT command again and use the correct format. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0499E ERROR IN FILE
Explanation: An error occurred when you entered a ZUDFM OAT command. There was a problem accessing the macro label set (MLS) control record file, GR3OSR. System Action: The ZUDFM OAT command is rejected. User Response: Do the following: 1. Ensure file GR3OSR is not corrupted. 2. Enter the ZUDFM OAT command again. See TPFDF Commands for more information about the ZUDFM OAT command. UDFM0501I TOD CLOCK VALUE DISPLAY
Explanation: This is the normal response to the ZUDFM OAZ command. This message is followed by a display of the date and time represented by the time-of-day (TOD) clock value specified. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAZ command.
126
UDFM0511E UDFM0523E
UDFM0511E UFB-DATA IN INPUT NOT VALID
Explanation: An error occurred when you entered a ZUDFM OAZ command because the specified clock value contained a non-hexadecimal digit. System Action: The ZUDFM OAZ command is rejected. User Response: Enter the ZUDFM OAZ command again and specify a hexadecimal clock value. See TPFDF Commands for more information about the ZUDFM OAZ command. UDFM0520I Where: coreaddr The core address of SW00SR base. filename The name of file represented by SW00SR. Explanation: This is the normal response to the ZUDFM OAS command with the W parameter and a field name specified. This message is followed by a display of the contents of the field name in the SW00SR DSECT. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0521I CURRENTLY PENDING FILES SW00SR BASE coreaddr FILENAME..06-filename
Explanation: This is the normal response to the ZUDFM OAS command without any parameters specified. This message is followed by a display of all open files. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAS command. UDFM0522E FILE ADDRESS IS NOT VALID
Explanation: An error occurred when you entered a ZUDFM OA command because the specified file address is not correct. System Action: The ZUDFM OA command is rejected. User Response: Enter the ZUDFM OA command again and specify a correct file address. See TPFDF Commands for more information about the ZUDFM OA command. UDFM0523E Where: fileaddr The fixed file address. ssu The subsystem user that owns the file address. Explanation: An error occurred when you entered a ZUDFM OA command with a file address that is not valid for the SSU specified with the command. System Action: The ZUDFM OA command is rejected. User Response: Do one of the following: v Enter the ZUDFM OA command again from the SSU indicated in the error message. v Enter the ZUDFM OA command again and specify a valid file address for the SSU from which you are entering the command. See TPFDF Commands for more information about the ZUDFM OA command. FILE ADDRESS fileaddr BELONGS TO SUBSYSTEM USER ssu
Online Messages
127
UDFM0524E UDFM0529I
UDFM0524E SS OR SSU IS NOT AVAILABLE FOR THIS ENTRY
Explanation: An error occurred when you entered a ZUDFM OA command because a subsystem or subsystem user (SSU) is not available. System Action: The ZUDFM OA command is rejected. User Response: Do the following: 1. Enter a TPF ZPSMS command to determine which subsystem or SSU is not available. 2. Investigate why the subsystem or SSU is not available. See TPFDF Commands for more information about the ZUDFM OA command. See TPF Operations for more information about the ZPSMS command. UDFM0525E Where: ssu The subsystem user. Explanation: An error occurred when you entered a ZUDFM command for a TPF subsystem user (SSU) because the SSU is not available. System Action: The ZUDFM command is rejected. User Response: Do one of the following: v If the specified SSU is correct, investigate why the SSU is not available. v Enter the ZUDFM command for an SSU that is available. See TPFDF Commands for more information about the ZUDFM command. UDFM0527I Where: type The large logical record (LLR) type that is displayed, where type is 1 or 2. Explanation: This is the normal response to the ZUDFM OA* command with the LR parameter specified. This command displays information about the LLR, including its size, the file addresses of the prime block of the subfile and the master large logical record (MLL, the beginning of the LLR), data block addresses, and for type 2 LLRs, index block addresses. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OA* command and for examples of the display. See TPFDF Database Administration for more information about LLR block structure. UDFM0528E TARGET LREC IS NOT AN LLR TPFDF LLR BLOCK INFORMATION DISPLAY - TYPE type SUBSYSTEM USER ssu NOT AVAILABLE
Explanation: This is the normal response to the ZUDFM OA* or ZUDFM DIS command with the LR parameter specified when the logical record (LREC) specified by the LR parameter is not a large logical record (LLR). System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OA* or ZUDFM DIS command. UDFM0529I TRACE DATABLOCK DISPLAY
Explanation: This is the normal response to the ZUDFM OAS command with the D parameter specified. This message is followed by a display of the content of the specified data block. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAS command.
128
UFB70012I UFDT0000I
UFB7
UFB70012I CENTRAL DESCRIPTOR INITIALIZED
Explanation: This is a normal response from the ZUDFM OAI/DBTAB command with the INIT parameter specified. This message is issued when you enter the command from one processor to initialize the database definition (DBDEF) tables on another processor. System Action: None. User Response: None. See TPFDF Commands for more information about the ZUDFM OAI/DBTAB command.
UFDT
UFDT0000I TPFDF EDUCATION PACKAGE NOT INSTALLED
Explanation: The ZUDFM DF command was entered for the TPFDF education package, but the TPFDF education package is not installed. The TPFDF education package is a non-IBM product. System Action: The entry control block (ECB) exits. User Response: Install the TPFDF education package, and enter the ZUDFM DF command again.
Online Messages
129
130
Offline Messages
UFOF
UFOF0001W Where: dsect The DSECT macro name. maclbl One of the following: v MACROS v LABELS Explanation: This message indicates that one of the following conditions was detected while running the offline macro label set (MLS) program: v Too many DSECT macros are defined. v Too many labels are defined for the DSECT macro (dsect). System Action: The MLS tape or data set is created; however, it does not contain label information for the DSECT macro indicated in the message. User Response: Do one of the following: v Reduce the number of macros defined for a single run and run the offline MLS program again. v Reduce the number of labels in the macro and run the offline MLS program again. UFOF0002I Where: dsect The DSECT macro name. Explanation: This is the normal response when the offline macro label set (MLS) program ends successfully. This indicates that the MLS tape or data set is ready to load to the TPF or ALCS system. System Action: None. User Response: None. UFOF0003E ASSEMBLY LIST INPUT IS INCOMPLETE, NO LABEL DS CREATED dsect SUCCESSFULLY PROCESSED, MACRO LABEL SET CREATED dsect NOT PROCESSED, TOO MANY maclbl FOR A SINGLE RUN
Explanation: This error occurs if you run the offline macro label set (MLS) program when the assembly input list does not contain any valid DSECT macros. System Action: The MLS tape or data set is not created. User Response: Do the following: v Update the assembly input list to include the valid DSECT macro names. v Run the offline MLS program again. UFOF0004E NO PROPER DATA MACRO FOUND IN INPUT
Explanation: This error occurs if you run the offline macro label set (MLS) program and no DSECT macros in the assembly input list were processed. This can occur if: v There are no labels in a DSECT macro. v A DSECT macro contains incorrect assembler instructions. v A DSECT macro contains a coding error. System Action: The macro label set tape or data set is not created. User Response: Do the following: 1. Determine the cause of the error. Copyright IBM Corp. 2002, 2009
131
UFOF0005E UFOF0008W
2. Correct the error. 3. Run the offline MLS program again. See TPFDF Database Administration for information about coding a DSECT macro. UFOF0005E DID-TABLE OVERFLOW - PGM ENDED
Explanation: This message occurs when you run the offline macro label set (MLS) program and the number of database identifiers (DID) defined in the DSECT macro was too high. System Action: The macro label set tape or data set is not created. User Response: Do the following: 1. Reduce the number of DIDs in the DSECT macro. 2. Run the offline MLS program again. UFOF0006E SORT ERROR - PGM ENDED
Explanation: A nonzero return code was returned when the offline macro label set (MLS) program attempted to link to an MVS sort routine. System Action: The macro label set tape or data set is not created. User Response: Do the following: 1. See your MVS system programmer to determine the cause of the link error. 2. Correct the error. 3. Run the offline MLS program again. UFOF0007E THIS VERSION OF HLASM IS NOT SUPPORTED
Explanation: The offline macro label set (MLS) program attempted to assemble a DSECT using a high level assembler release that is not supported. System Action: The MLS tape or data set is not created. User Response: Report the problem to your IBM service representative. UFOF0008W ILLRDF CONTAINS LARGE LOGICAL RECORD
Explanation: When generating a macro label set, the subfile contains a large logical record (LLR). System Action: None. User Response: None.
132

Dumps

Uploaded by

Copyright:

Available Formats

Dumps

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dumps

Uploaded by

Copyright:

Available Formats

TPF Database Facility

Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

Offline Messages . . . . . . . . . . . . . . . . . . . . . . . 131 UFOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Copyright IBM Corp. 2002, 2009

TPFDF Messages (System Error, Online, Offline)

Copyright IBM Corp. 2002, 2009

TPFDF Messages (System Error, Online, Offline)

Analyze a System Error

Copyright IBM Corp. 2002, 2009

Example of System Errors

Online and Offline Messages

TPFDF Messages (System Error, Online, Offline)

Locate an Online or Offline Message

Analyze an Online or Offline Message

TPFDF Messages (System Error, Online, Offline)

Standard Message Example

Non-Standard Message Example

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

Copyright IBM Corp. 2002, 2009

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)

TPFDF Messages (System Error, Online, Offline)