gtpm5m0l | Messages (Online) |
CFAI0002I | DISPLAY FOR FIXED RECORD BEGINS |
Explanation: This is the normal response to the ZDFAI command with the file address for a fixed file record specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDFAI command and for an example of the informational display.
CFAI0003I | DISPLAY FOR POOL RECORD BEGINS |
Explanation: This is the normal response to the ZDFAI command with the file address for a pool record specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDFAI command and for an example of the informational display.
CFAI0004I | DISPLAY FOR INACTIVE POOL SECTION RECORD BEGINS |
Explanation: This is the normal response to the ZDFAI command with the file address for a pool record specified. The pool section that contains this file address is not active, so only the pool section and ordinal number for this pool record can be displayed.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDFAI command and for an example of the informational display.
CFAI0050E | INPUT FILE ADDRESS NOT 4 OR 8 BYTES IN LENGTH |
Explanation: The ZDFAI command was entered, but the specified file address is not 4 or 8 bytes in length.
System Action: The command is rejected.
User Response: Enter the ZDFAI command again and specify either a 4- or 8-byte file address.
See TPF Operations for more information about the ZDFAI command.
CFAI0051E | FILE ADDRESS IS NOT VALID |
Explanation: The ZDFAI command was entered, but the ESFAC macro was unable to convert the specified file address.
System Action: The command is rejected.
User Response: Enter the ZDFAI command again and specify a valid file address.
See TPF Operations for more information about the ZDFAI command. See TPF System Macros for more information about the ESFAC macro.
CFAI0052E | FACS ERROR DIRECTORY RECORD |
Explanation: The ZDFAI command was entered, but an error occurred because the file address for the pool directory record (#SONRI) could not be obtained. The ZDFAI command must read the pool directory to determine if a pool address is in use.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDFAI command.
CFAI0053E | FIND ERROR DIRECTORY RECORD |
Explanation: The ZDFAI command was entered, but an error occurred because a request to find the file address for the pool directory record (#SONRI) failed. The ZDFAI command must read the pool directory to determine if a pool address is in use.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDFAI command.
CFCA0002E | CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - CONNECT RETURN CODE WAS retcode |
Where:
Explanation: While trying to create a CF cache structure, an attempt to connect to the CF specified was not successful.
System Action: The connection request is rejected.
User Response: See your IBM service representative.
See TPF System Macros for more information about the CFCONC macro.
CFCA0003E | CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - AVAILABLE VECTOR LENGTH FOR CACHE STRUCTURE IS size AND LESS THAN THE REQUESTED VECTOR LENGTH OF reqsize |
Where:
Explanation: While trying to create a CF cache structure, an attempt to connect to the CF specified was not successful because there were not enough vector entries available in the processor.
System Action: The connection request is rejected.
User Response: IPL the processor.
See TPF System Macros for more information about the CFCONC macro.
CFCA0004E | CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - SIZE AVAILABLE FOR CACHE STRUCTURES IS size LESS THAN THE REQUESTED SIZE OF reqsize |
Where:
Explanation: While trying to create a CF cache structure, an attempt to connect to the CF specified was not successful because there is not enough space available on the CF to create the CF cache structure.
System Action: The connection request is rejected.
User Response: See your IBM service representative for more information about ensuring there is enough space available on the CF for CF cache structures.
See TPF System Macros for more information about the CFCONC macro.
CFCA0006E | NEWCFCACHE ERROR - NO LOCKING CF DEFINED |
Explanation: A NEWCFCACHE function call was issued to request a new coupling facility (CF) cache structure, but no CFs have been added to the CF locking configuration by entering the ZCFLK ADD command.
System Action: The request is rejected.
User Response: Enter the ZCFLK ADD command to add a CF to the CF locking configuration, which then enables the CF for use as an external locking facility (XLF) so new locks can be stored on it.
See TPF Operations for more information about the ZCFLK ADD command.
CFCC0020E | I/O ERROR READING record FILE ADDRESS REFERENCE WORD farw SUD indicator |
Where:
Explanation: An error occurred while reading a coupling facility (CF) record at the specified file address.
System Action: The TPF system displays additional messages that describe the error.
User Response: Do the following:
See TPF General Macros for more information about the SUD.
CFCC0021E | FACS ERROR CALCULATING ADDRESS OF record RECORD TYPE rectype ORDINAL NUMBER ordnum |
Where:
Explanation: The file address compute (FACE) program for symbolic record types (FACS) returned an error while calculating the file address of a coupling facility (CF) record. Either the FACE table is damaged or the record type does not exist.
System Action: The TPF system displays additional messages.
User Response: Do the following:
See TPF Application Programming for more information about the FACS and FACE tables. See TPF Database Reference for more information about coupling facility support.
CFCC0022E | segment - UNABLE TO OBTAIN SUFFICIENT RETRY BUFFERS FOR COUPLING FACILITY cfname |
Where:
Explanation: During TPF restart processing for the CF specified in the message, the TPF system was unable to obtain sufficient retry buffers. This error is usually received after one or more TPF systems attached to the specified CF did not have an initial program load (IPL) performed again or were not deactivated after a system failure.
System Action: Processing continues. Normal CF operations are unaffected. However, the TPF system may not be able to perform the apropriate error recovery procedure in the event that certain CF errors are encountered.
User Response: Enter the ZPSMS command to properly deactivate any TPF systems that were attached to the specified CF when a system failure occurred.
See TPF Operations for more information about the ZPSMS command.
CFCC0024W | segment - COUPLING FACILITY cfname IS UNAVAILABLE |
Where:
Explanation: During CF restart, no symbolic device addresses (SDAs) were found for the CF. The CF was previously added for the processor and was expected to be attached to the processor.
System Action: The CF is disabled and restart continues.
User Response: Do one of the following:
See TPF Operations for more information about the ZMCFT DELETE and ZMCFT ENABLE commands.
CFCC0025I | segment - COUPLING FACILITY RESTART COMPLETED |
Where:
Explanation: Coupling facility (CF) restart is completed successfully.
System Action: The TPF system performs the next task in the restart schedule.
User Response: None.
CFCC0028E | segment - COUPLING FACILITY RESTART ENDS - UNABLE TO SET LOCK ON COUPLING FACILITY cfname |
Where:
Explanation: During CF restart, an attempt to set the CF lock on the CF to serialize processing was not successful.
System Action: The TPF system displays additional messages that describe the error. In addition, CF functions are disabled and system restart continues.
User Response: Do the following:
CFCC0029E | segment - COUPLING FACILITY RESTART ENDS - UNABLE TO READ COUPLING FACILITY RECORD |
Where:
Explanation: During coupling facility (CF) restart, an attempt to read the CF status table (CFST) or a CF structure block (CFSB) was not successful.
System Action: CF functions are disabled and system restart continues.
User Response: Do the following:
See TPF Operations for more information about the ZIFIL command. See TPF Database Reference for more information about initializing the record.
CFCC0031E | segment - UNABLE TO DEFINE LIST NOTIFICATION VECTOR FOR COUPLING FACILITY cfname |
Where:
Explanation: During CF restart, an attempt to define a list notification vector for the CF was not successful because there was not enough space available.
System Action: The CF is disabled and CF restart continues.
User Response: Perform an initial program load (IPL) of the processor using the load-clear key.
CFCC0034E | segment - UNABLE TO DISCONNECT FROM STRUCTURE strname ON COUPLING FACILITY cfname |
Where:
Explanation: During CF restart, an attempt to disconnect the processor from a structure to which it is connected was not successful.
System Action: CF restart continues.
User Response: See your IBM service representative.
CFCE0001E | segment - CHANNEL CONTROL CHECK CF - cfname, DEVICE - sda, PATH - chpid |
Where:
Explanation: A channel control check status was received on the channel path and device referenced in the message for the CF referenced.
System Action: The status of any CF operation in progress is not known. The CF request is posted as complete with the ICFRRCSTATUSUNKNOWN return and reason code.
User Response: See your IBM service representative.
CFCE0002E | segment - INTERFACE CONTROL CHECK CF - cfname, DEVICE - sda, PATH - chpid |
Where:
Explanation: An interface control check status was received on the channel path and device referenced in the message for the CF referenced.
System Action: The status of any CF operation in progress is not known. The CF request is posted as complete with the ICFRRCSTATUSUNKNOWN return and reason code.
User Response: See your IBM service representative.
CFCE0003E | segment - DEVICE sda HAS BEEN REMOVED FROM CF cfname |
Where:
Explanation: A condition was encountered that caused the device referenced in the message to be removed from the coupling facility status table (CFST) entry for the CF referenced. This device will no longer be used to perform CF operations.
System Action: The TPF system attempts to retry any CF operation in progress on any remaining devices for the CF referenced in the message.
User Response: Do the following:
CFCE0004E | segment - PATH chpid HAS BEEN REMOVED FROM CF cfname |
Where:
Explanation: A condition was encountered that caused the channel path referenced in the message to be removed from the coupling facility status table (CFST) entry of the referenced CF. This channel path will no longer be used to perform CF operations.
System Action: The TPF system attempts to retry any CF operation in progress on any remaining channel paths for the referenced CF.
User Response: Do the following:
CFCE0005E | segment - COUPLING FACILITY cfname HAS BEEN DISABLED |
Where:
Explanation: A condition was encountered that caused the TPF system to disable the CF referenced in the message.
System Action: The CF will no longer be used for any CF operations.
User Response: Do the following:
See TPF Operations for more information about the ZMCFT ENABLE command.
CFCE0006E | segment - RETRY BUFFER NOT AVAILABLE FOR ERROR RECOVERY ON CF cfname |
Where:
Explanation: A CF error was encountered that required a retry buffer to perform the appropriate error recovery procedure, but no retry buffer was available. This condition was prevoiusly made known by either the MCFT0040E message or the CFCC0022E message, both of which warn that insufficient retry buffers were available when the CF was added to the system configuration, enabled, or validated during TPF restart.
System Action: The CF is disabled.
User Response: Do the following:
See TPF Operations for more information about the ZMCFT ENABLE and ZPSMS commands.
CFCE0007E | segment - PATH chpid HAS RECEIVED errnum ERRORS IN secnum SECONDS |
Where:
Explanation: The number of channel path errors indicated in the message were received on the channel path referenced in the message in the time interval indicated. The number of errors does not exceed a system-defined threshold so no further action is taken.
System Action: Processing continues.
User Response: Do one of the following if the number of errors is excessive for your complex:
See TPF Operations for more information about the ZMCFT commands.
CFCH0001I | CACHE CONTROL AREA HAS NOT BEEN ALLOCATED |
Explanation: The ZCFCH command was entered with the DISPLAY and COUNTS parameters specified to display the current storage class counters for a specific coupling facility (CF) cache structure, but none are currently defined.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZCFCH command.
CFCH0002I | CF CACHE CONTROL RECORD DISPLAY |
Explanation: This is the normal response to the ZCFCH command with the DISPLAY and FILE parameters specified.
System Action: The names of the caches currently defined in the processor shared coupling facility (CF) cache control record and their assigned sizes are displayed.
User Response: None.
See TPF Operations for more information about the ZCFCH command and for an example of the informational display.
CFCH0003E | CACHE cache NOT FOUND |
Where:
Explanation: The ZCFCH command was entered, but the CF cache structure specified was not found.
System Action: The entry control block (ECB) exits.
User Response: Do the following:
See TPF Operations for more information about the ZCACH and ZCFCH commands.
CFCH0005I | CF STORAGE CLASS 1 COUNTER DISPLAY |
Explanation: This is the normal response to the ZCFCH command with the DISPLAY and COUNTS parameters specified to display the storage class counters for the coupling facility (CF) cache structure.
System Action: Processing was completed successfully with information about the current storage class counters displayed.
User Response: None.
See TPF Operations for more information about the ZCFCH command and for an example of the informational display.
CFCH0008E | ERROR RETRIEVING CF STORAGE CLASS COUNTERS |
Explanation: The ZCFCH command was entered with the DISPLAY and COUNTS parameters specified, but an error occurred while trying to retrieve the counter values.
System Action: The entry control block (ECB) exits.
User Response: Do the following:
See TPF Operations for more information about the ZCFCH command.
CFCH0009E | ERROR RETRIEVING CF CACHE CONTROL RECORD |
Explanation: The ZCFCH command was entered to modify, remove, or display information about the coupling facility (CF) cache structure, but an error occurred while trying to find the processor shared CF cache control record.
System Action: The entry control block (ECB) exits.
User Response: Do the following:
CFCH0010E | FACE ERROR ON CF CACHE CONTROL RECORD |
Explanation: The ZCFCH command was entered to modify, remove, or display information about the coupling facility (CF) cache structure, but an error occurred in the file address compute (FACE) program when the file address of the processor shared CF cache control record could not be resolved.
System Action: The entry control block (ECB) exits.
User Response: Do one of the following:
See TPF Operations for more information about the ZCFCH command. See TPF System Generation for more information about the FCTB.
CFCH0011E | CF CONTROL RECORD NOT INITIALIZED, CACHE cache NOT FOUND |
Where:
Explanation: The ZCFCH command was entered with the REMOVE parameter specified, but an error occurred because the processor shared CF cache control record was not initialized so the specified CF cache structure was not found.
System Action: The entry control block (ECB) exits.
User Response: None.
See TPF Operations for more information about the ZCFCH command.
CFCH0016I | CACHE cache SUCCESSFULLY REMOVED |
Where:
Explanation: This is the normal response to the ZCFCH command with the REMOVE parameter specified.
System Action: The cache definition for the specified CF cache structure was removed from the processor shared CF cache control record.
User Response: None.
See TPF Operations for more information about the ZCFCH command.
CFCH0017I | CACHE cache SUCCESSFULLY MODIFIED |
Where:
Explanation: This is the normal response to the ZCFCH command with the MODIFY parameter specified.
System Action: The number of entries for the CF cache structure specified in the processor shared CF cache control record is changed.
User Response: None.
See TPF Operations for more information about the ZCFCH command.
CFCH0018E | NO ENTRIES AVAILABLE IN CF CACHE CONTROL RECORD FOR MODIFICATION OF CACHE cache |
Where:
Explanation: The ZCFCH command was entered with the MODIFY parameter specified to change the number of entries for the CF cache structure in the processor shared CF cache control record, but an error occurred because the processor shared CF cache control record already contains the maximum number of entries allowed.
System Action: The entry control block (ECB) exits.
User Response: Do the following:
See TPF Operations for more information about the ZCFCH command.
CFCR0001I | UNABLE TO OBTAIN CF LOCK FOR CF cfname - CURRENT HEX LOCK VALUE IS - hexlockvalue |
Where:
Explanation: An error occurred when issuing the CFRQC macro with the REQUEST parameter set to SETLOCK, which sets the CF lock, because it was not available in a system-defined period of time.
System Action: The TPF system tries to issue the CFRQC macro again.
User Response: Do the following:
See TPF Database Reference for more information about the format of the CF lock. See TPF System Macros for more information about the CFRQC macro. See TPF Operations for more information about the ZMCFT RESETLOCK command.
CFDT0001I | PTAP -- TAPE STATUS SENT TO PRINTER |
Explanation: This is the normal response to the ZPTAP command.
System Action: None.
User Response: None.
CFDT0050E | PTAP --NO PRINTER AVAILABLE |
Explanation: All printers are currently busy.
System Action: None.
User Response: Try your print request again at a later time.
CFDT0051E | PTAP --PRINTER ERROR -- JOB TERMINATED |
Explanation: A printer error occurred.
System Action: The job is ended.
User Response: Check your printer status. If you suspect a hardware problem, see your IBM service representative.
CFD20001E | INVALID FORMAT: USE ZDMOD xxx |
Where:
Explanation: The format of the ZDMOD command is not valid. For example, you specified characters that are not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDMOD command.
CFD20002E | INVALID MODULE NUMBER |
Explanation: The symbolic module number specified in the ZDMOD command is not defined in your TPF system.
System Action: The command is rejected.
User Response: Enter the ZDMOD command again and specify a valid module number.
See TPF Operations for more information about the ZDMOD command.
CFD20004I | MODULE xxx |
Where:
Explanation: This is the normal response to the ZDMOD command. This message is followed by a display of the core addresses of the file status table, the XREF table, and the control status table.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDMOD command.
CFIN0001W | FILE SYSTEM NEEDS TO BE INITIALIZED |
Explanation: The CFIN file system restart segment determined that the file system must be initialized.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZFINT command.
CFIN0002E | NO INODE OR FLOCK RECORDS AVAILABLE |
Explanation: The CFIN file system restart segment determined that no #INODE or #FLOCK fixed file records are on the TPF system.
System Action: None.
User Response: Load a new file address compute program (FACE) table containing the new records.
See TPF System Generation for more information about #INODE and #FLOCK fixed file records.
CFIN0003I | number NEW INODE AND FLOCK RECORDS ALLOCATED BUT NOT INITIALIZED |
Where:
Explanation: The CFIN file system restart segment determined that more #INODE fixed file records have been allocated to the TPF system and are not initialized to be used by the TPF system.
System Action: None.
User Response: Enter the ZFINT command with the ADD parameter specified to add the #INODE fixed file records to the file system.
See TPF Operations for more information about the ZFINT command. See TPF System Generation for more information about #INODE and #FLOCK fixed file records.
CFIN0004I | FILE SYSTEM RESTART COMPLETED i OF j INODE AND FLOCK AND m OF n IZERO RECORDS ARE IN USE |
Explanation: The CFIN file system restart segment was completed successfully.
System Action: None.
User Response: None.
CFIN0005W | INODE 0 RESTORED FROM FLOCK 0 |
Explanation: The CFIN file system restart segment needed to restore the copy of #INODE fixed file record ordinal 0 from the backup copy kept in #FLOCK fixed file record ordinal 0.
System Action: #INODE fixed file record ordinal 0 was restored from #FLOCK fixed file record ordinal 0.
User Response: See your IBM service representative to determine the cause of the error.
See TPF System Generation for more information about #INODE and #FLOCK fixed file records.
CFIN0006E | NO SYSTEM HEAP AVAILABLE. FILE SYSTEM IS NOT USABLE |
Explanation: File system restart tried to get one system heap frame, but none were available.
System Action: The file system is not usable.
User Response: Enter the ZCTKA ALTER command to increase the number of system heap frames.
See TPF Operations for more information about the ZCTKA ALTER command.
CFIN0007E | NO IZERO RECORDS AVAILABLE |
Explanation: No #IZERO fixed file records were allocated on the TPF system.
System Action: The file system cannot be used until #IZERO fixed file records are allocated.
User Response: Load a new file address compute program (FACE) table that contains #IZERO fixed file records.
CFIN0008E | NO SYSTEM HEAP AVAILABLE. SHARED MEMORY IS NOT USABLE |
Explanation: File system restart tried to get three system heap frames, but none were available.
System Action: The shared memory cannot be used.
User Response: Enter the ZCTKA ALTER command to increase the number of system heap frames.
See TPF Operations for more information about the ZCTKA ALTER command.
CFIN0009E | UNABLE TO CREATE FILE SYSTEM DIRECTORY CACHE |
Explanation: During system restart, the file system restart program was unable to create file system directory cache.
System Action: System restart continues and file system directory caching is disabled.
User Response: Do the following:
See TPF System Generation for more information about using the CORREQ macro to verify and define system heap storage.
CFIN0010E | UNABLE TO CREATE FILE SYSTEM INODE CACHE |
Explanation: During system restart, the file system restart program was unable to create file system i-node cache.
System Action: System restart continues and file system i-node caching is disabled.
User Response: Do the following:
See TPF System Generation for more information about using the CORREQ macro to verify and define system heap storage.