gtpm5m0lMessages (Online)

CFAI-CFIN

CFAI0002IDISPLAY 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.

CFAI0003IDISPLAY 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.

CFAI0004IDISPLAY 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.

CFAI0050EINPUT 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.

CFAI0051EFILE 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.

CFAI0052EFACS 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:

  1. Determine why the pool directory record file address could not be resolved.
  2. Correct the problem.
  3. Enter the ZDFAI command again.

See TPF Operations for more information about the ZDFAI command.

CFAI0053EFIND 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:

  1. Determine why the find request for the pool directory record file address failed.
  2. Correct the problem.
  3. Enter the ZDFAI command again.

See TPF Operations for more information about the ZDFAI command.

CFCA0002ECONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - CONNECT RETURN CODE WAS retcode

Where:

cfname
The name of the coupling facility (CF).

retcode
The return code.

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.

CFCA0003ECONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - AVAILABLE VECTOR LENGTH FOR CACHE STRUCTURE IS size AND LESS THAN THE REQUESTED VECTOR LENGTH OF reqsize

Where:

cfname
The name of the coupling facility (CF).

size
The number of cache vector entries available.

reqsize
The number of cache vector entries requested.

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.

CFCA0004ECONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - SIZE AVAILABLE FOR CACHE STRUCTURES IS size LESS THAN THE REQUESTED SIZE OF reqsize

Where:

cfname
The name of the coupling facility (CF).

size
The space available in the CF for the CF cache structure.

reqsize
The size requested for the CF cache structure.

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.

CFCA0006ENEWCFCACHE 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.

CFCC0020EI/O ERROR READING record FILE ADDRESS REFERENCE WORD farw SUD indicator

Where:

record
The type of record in the #CFREC or #CF2LR record types, which can be one of the following:

CFSB
Coupling facility structure block.

CFST
Coupling facility status table.

CFLR
Coupling facility locking record (CFLR)

CFDL
Coupling facility distribution list (CFDL)

IPLI
Initial program load (IPL) inhibitor record.

farw
The file address reference word that is used to read the record.

indicator
The detail data level error indicator.

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:

  1. Refer to the SUD and the file address reference word information to determine the cause of the error.
  2. Correct the error.

See TPF General Macros for more information about the SUD.

CFCC0021EFACS ERROR CALCULATING ADDRESS OF record RECORD TYPE rectype ORDINAL NUMBER ordnum

Where:

record
The type of record in the #CFREC record type, which can be one of the following:

CFSB
Coupling facility structure block.

CFST
Coupling facility status table.

rectype
The record type of the record.

ordnum
The ordinal number of the record.

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:

  1. Correct the FACE table if necessary.
  2. Define the record type if CF support is needed.

See TPF Application Programming for more information about the FACS and FACE tables. See TPF Database Reference for more information about coupling facility support.

CFCC0022Esegment - UNABLE TO OBTAIN SUFFICIENT RETRY BUFFERS FOR COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

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.

CFCC0024Wsegment - COUPLING FACILITY cfname IS UNAVAILABLE

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

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.

CFCC0025Isegment - COUPLING FACILITY RESTART COMPLETED

Where:

segment
The name of the segment that completed restart.

Explanation: Coupling facility (CF) restart is completed successfully.

System Action: The TPF system performs the next task in the restart schedule.

User Response: None.

CFCC0028Esegment - COUPLING FACILITY RESTART ENDS - UNABLE TO SET LOCK ON COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

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:

  1. Review the accompanying error messages to determine the cause of the error.
  2. Correct the error.

CFCC0029Esegment - COUPLING FACILITY RESTART ENDS - UNABLE TO READ COUPLING FACILITY RECORD

Where:

segment
The name of the segment that detected the error.

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:

  1. Review the previous error messages to determine the cause of the error and the type of record being read.
  2. Correct the error. If the error shows that the contents of the record are not valid, enter the ZIFIL command to initialize the record.
  3. Perform an initial program load (IPL) of the TPF system.

See TPF Operations for more information about the ZIFIL command. See TPF Database Reference for more information about initializing the record.

CFCC0031Esegment - UNABLE TO DEFINE LIST NOTIFICATION VECTOR FOR COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

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.

CFCC0034Esegment - UNABLE TO DISCONNECT FROM STRUCTURE strname ON COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

strname
The name of the coupling facility (CF) structure.

cfname
The name of the CF.

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.

CFCE0001Esegment - CHANNEL CONTROL CHECK CF - cfname, DEVICE - sda, PATH - chpid

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

sda
The symbolic device address (SDA).

chpid
The channel path.

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.

CFCE0002Esegment - INTERFACE CONTROL CHECK CF - cfname, DEVICE - sda, PATH - chpid

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

sda
The symbolic device address (SDA).

chpid
The channel path.

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.

CFCE0003Esegment - DEVICE sda HAS BEEN REMOVED FROM CF cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

sda
The symbolic device address (SDA).

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:

  1. See any preceding messages for details about the problem.
  2. Correct the problem.

CFCE0004Esegment - PATH chpid HAS BEEN REMOVED FROM CF cfname

Where:

segment
The name of the segment that detected the error.

chpid
The channel path.

cfname
The name of the coupling facility (CF).

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:

  1. See any preceding messages for details about the problem.
  2. Correct the problem.

CFCE0005Esegment - COUPLING FACILITY cfname HAS BEEN DISABLED

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

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:

  1. See any preceding messages for details about the problem.
  2. Correct the problem.
  3. If you want to resume using the CF for CF operations, enter the ZMCFT ENABLE command to resume normal operations of the CF.

See TPF Operations for more information about the ZMCFT ENABLE command.

CFCE0006Esegment - RETRY BUFFER NOT AVAILABLE FOR ERROR RECOVERY ON CF cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

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:

  1. Enter the ZPSMS command to properly deactivate any TPF systems that were attached to the specified CF when a system failure occurred.
  2. Enter the ZMCFT ENABLE command to enable the CF.

See TPF Operations for more information about the ZMCFT ENABLE and ZPSMS commands.

CFCE0007Esegment - PATH chpid HAS RECEIVED errnum ERRORS IN secnum SECONDS

Where:

segment
The name of the segment that detected the error.

chpid
The channel path identifier (ID) of the channel path receiving errors.

errnum
The number of errors being reported.

secnum
The number of seconds in the interval during which the errors were received.

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.

CFCH0001ICACHE 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.

CFCH0002ICF 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.

CFCH0003ECACHE cache NOT FOUND

Where:

cache
The name of the coupling facility (CF) cache structure.

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:

  1. Enter the ZCACH command with the DISPLAY and CTL parameters specified to view information about all the active CF cache structures.
  2. Enter the ZCFCH command again and specify the name of an active CF cache structure.

See TPF Operations for more information about the ZCACH and ZCFCH commands.

CFCH0005ICF 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.

CFCH0008EERROR 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:

  1. Enter the ZCFCH command again with the DISPLAY and COUNTS parameters specified.
  2. If the error continues, see your system programmer to determine the cause of the problem and to correct it.

See TPF Operations for more information about the ZCFCH command.

CFCH0009EERROR 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:

  1. Enter the ZCFCH command again.
  2. If the error continues, see your system programmer to determine the cause of the problem and to correct it
See TPF Operations for more information about the ZCFCH command.

CFCH0010EFACE 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.

CFCH0011ECF CONTROL RECORD NOT INITIALIZED, CACHE cache NOT FOUND

Where:

cache
The name of the coupling facility (CF) cache structure.

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.

CFCH0016ICACHE cache SUCCESSFULLY REMOVED

Where:

cache
The name of the coupling facility (CF) cache structure.

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.

CFCH0017ICACHE cache SUCCESSFULLY MODIFIED

Where:

cache
The name of the coupling facility (CF) cache structure.

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.

CFCH0018ENO ENTRIES AVAILABLE IN CF CACHE CONTROL RECORD FOR MODIFICATION OF CACHE cache

Where:

cache
The name of the coupling facility (CF) cache structure.

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:

  1. Enter the ZCFCH command with the DISPLAY and FILE parameters specified to view all the CF cache structures currently defined in the processor shared CF cache control record.
  2. Determine if the definition for a CF cache structure can be removed from the processor shared CF cache control record. If a definition can be removed, go to step 3. If a definition cannot be removed, there is no more action for you to take.
  3. Enter the ZCFCH command with the REMOVE parameter specified to delete the definition for a CF cache structure.
  4. Enter the ZCFCH command again with the MODIFY parameter specified to define the original CF cache structure.

See TPF Operations for more information about the ZCFCH command.

CFCR0001IUNABLE TO OBTAIN CF LOCK FOR CF cfname - CURRENT HEX LOCK VALUE IS - hexlockvalue

Where:

cfname
The name of the coupling facility (CF).

hexlockvalue
The current CF lock in the CF.

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:

  1. Examine the format of the CF lock to determine why it is being held.
  2. Do one of 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.

CFDT0001IPTAP -- TAPE STATUS SENT TO PRINTER

Explanation: This is the normal response to the ZPTAP command.

System Action: None.

User Response: None.

CFDT0050EPTAP --NO PRINTER AVAILABLE

Explanation: All printers are currently busy.

System Action: None.

User Response: Try your print request again at a later time.

CFDT0051EPTAP --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.

CFD20001EINVALID FORMAT: USE ZDMOD xxx

Where:

xxx
Characters that are not valid.

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:

  1. Determine the correct format for the command.
  2. Enter the ZDMOD command again.

See TPF Operations for more information about the ZDMOD command.

CFD20002EINVALID 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.

CFD20004IMODULE xxx

Where:

xxx
The module number whose information is displayed.

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.

CFIN0001WFILE 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:

  1. Enter ZFINT ON BP to schedule file system initialization.
  2. Cycle the TPF system to NORM state.

See TPF Operations for more information about the ZFINT command.

CFIN0002ENO 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.

CFIN0003Inumber NEW INODE AND FLOCK RECORDS ALLOCATED BUT NOT INITIALIZED

Where:

number
The number of #INODE fixed file records.

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.

CFIN0004IFILE 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.

CFIN0005WINODE 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.

CFIN0006ENO 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.

CFIN0007ENO 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.

CFIN0008ENO 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.

CFIN0009EUNABLE 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:

  1. Verify the amount of system heap storage allocated.
  2. Increase the amount of system heap storage if there is not enough defined for all users.

See TPF System Generation for more information about using the CORREQ macro to verify and define system heap storage.

CFIN0010EUNABLE 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:

  1. Verify the amount of system heap storage allocated.
  2. Increase the amount of system heap storage if there is not enough defined for all users.

See TPF System Generation for more information about using the CORREQ macro to verify and define system heap storage.