gtpm5m1e | Messages (Online) |
FDNT0001I | GENERAL FILE DATA SET num DISMOUNTED FROM addr |
Where:
Explanation: The general file data set specified in the message was dismounted successfully.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFDNT command.
FDNT0011E | DATA SET num NOT ASSIGNED TO SYSTEM |
Where:
Explanation: The data set number specified in the message is not within the legal range defined for general file data set numbers.
System Action: The command is rejected and the ECB is exited.
User Response: Do the following:
See TPF Operations for more information about the ZFDNT command.
FDNT0021E | I/O ERROR READING GENERAL FILE CONTROL RECORD |
Explanation: An error was encountered while trying to access the general file control record.
System Action: None.
User Response: None.
FDNT0022E | DATA SET num NOT MOUNTED IN THIS PROCESSOR |
Where:
Explanation: The data set specified in the message cannot be dismounted because it is not mounted.
System Action: The request is ignored and the ECB exits.
User Response: None.
See TPF Operations for more information about the ZFDNT command.
FDNT0024E | FACE ERROR -- INVALID RECORD TYPE |
Explanation: A file address compute (FACE) program error is returned on the computation of the general file control record.
System Action: None.
User Response: None.
FDNT0025E | FACE ERROR -- ORDINAL NUMBER OUT OF RANGE |
Explanation: A file address compute (FACE) program error was returned on the computation of the general file control record.
System Action: None.
User Response: None.
FDNT0027E | GENERAL FILE RESTART HAS NOT COMPLETED. |
Segment Reference: CVTT
Explanation: A ZFMNT command was entered but the TPF system has not completed general file restart.
System Action: The ZFMNT command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFMNT command.
FECB0001E | ECB ADDRESS ENTERED WAS NOT VALID |
Explanation: The ZFECB command was entered with an entry control block (ECB) address that was not valid.
System Action: The ZFECB command was rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFECB command.
FECB0002E | ERROR RETRIEVING PROGRAM RECORD CDEP |
Explanation: The CDE0 real-time program was unable to retrieve the CDEP program record successfully.
System Action: The ZFECB command was rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFECB command.
FECB0003I | UNABLE TO FIND STATE CHANGE ECB |
Explanation: The ZFECB command was entered at a time when there was no state change entry control block (ECB) active.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFECB command.
FECB0004I | NO ACTIVE ECBS FOUND MATCHING SEARCH CRITERIA |
Explanation: The ZFECB command was entered, but no active entry control blocks (ECBS) were found that were at or above the time limit specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFECB command.
FECB0005I | INPUT SVC MACRO NAME WAS NOT FOUND |
Explanation: No active entry control blocks (ECBs) were found that had last issued the input supervisor call (SVC) macro name.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFECB command.
FECB0006I | ACTIVE ECB DISPLAY |
Explanation: This is a normal response to the ZFECB active entry control block (ECB) display command. This message is followed by a display of all the ECBs in the TPF system that meet the criteria of the parameters specified. The I-stream will be displayed as a decimal number.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFECB command and for an example of the informational display.
FECB0008I | FORMATTED ECB DISPLAY |
Explanation: This is a normal response to the ZFECB command. This message is followed by either a display of the entry control block (ECB) whose address was specified in the command or a display of the state change ECB. The I-stream will be displayed as a decimal number.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFECB command and for an example of the informational display.
FILE0001I | START OF DISPLAY FROM cmd |
Where:
Explanation: This is a normal response to a ZFILE command when the request generates normal output for the standard output (stdout) stream. This message is followed by a display of the normal output.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFILE commands and for examples of the displays.
FILE0002I | START OF ERROR DISPLAY FROM cmd |
Where:
Explanation: This is a normal response to a ZFILE command when the request generates error output for the standard error (stderr) stream. This message is followed by a display of the error output.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFILE commands and for examples of the displays.
FILE0003I | cmd COMPLETED SUCCESSFULLY. NO OUTPUT TO DISPLAY |
Where:
Explanation: This is a normal response to a ZFILE command when the request was completed successfully and did not generate any specific output for either the standard output (stdout) or standard error (stderr) stream.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFILE commands.
FILE0005W | FILE SYSTEM RUNNING LOW OF INODE AND FLOCK RECORDS |
Explanation: The file system ran low of the #INODE and #FLOCK fixed file records that were needed to create new files because a high percentage of the #INODE and #FLOCK fixed file records were in use for existing files.
System Action: The file system cannot create new files when it runs out of available #INODE and #FLOCK fixed file records. When this occurs, the TPF system C functions that normally create files fail with the value of the errno external variable set to ENOSPC.
User Response: Do the following:
See TPF Operations for more information about the ZFINT command. See TPF System Generation for more information about the FACE table.
FILE0050W | SAVED FILE SYSTEM STATE NOT REESTABLISHED |
Explanation: A ZFILE command was entered, but the environment variables for the file system may not be set correctly. For example, assume you entered a ZFILE cd command to change your current working directory and then entered a subsequent ZFILE command, expecting the second request to process in the new current directory. This message occurs if your new environment (the directory to which you just changed) cannot be established for the new ZFILE command request.
Environment variables for ZFILE commands are saved in the /.tpfZfileState hidden directory. There is a state file for each computer room agent set (CRAS) terminal that issues ZFILE commands. The name of the file is a combination of the line number, interchange address, and terminal address (LNIATA) of the terminal and the processor identifier (ID) on which the ZFILE command was processed; for example, 000100B. The files in the /.tpfZfileState directory are not hidden. ZFILE processing uses the environment variables to restore the environment for each CRAS terminal to the previous state, such as the current working directory. You can edit this file to modify or add ZFILE environment variable values.
System Action: The ZFILE command request continues. Any results based on the environment variables may not be reliable.
User Response: Do the following:
See TPF Operations for more information about the ZFILE commands.
FILE0096E | FILE SYSTEM INOPERATIVE |
Explanation: A ZFILE command was entered during a period of time when the file system was inactive. No #INODE fixed file records appear to be available. This can occur if you enter a ZFILE command before the file system is fully initialized.
System Action: The ZFILE command is rejected.
User Response: Wait for the file system to complete initialization and enter the ZFILE command again.
See TPF Operations for more information about the ZFILE commands.
FILE0097E | COMMAND NOT FOUND |
Explanation: A ZFILE command was entered that is not supported.
System Action: The ZFILE command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFILE commands.
FILE0098E | FILE SYSTEM MUST BE INITIALIZED |
Explanation: A ZFILE command was entered in a TPF subsystem where the file system is not initialized.
System Action: The ZFILE command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFILE and ZFINT commands.
FILE0099E | SYSTEM MUST BE IN CRAS STATE OR ABOVE |
Explanation: A ZFILE command was entered in a TPF subsystem below CRAS state.
System Action: The ZFILE command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILE commands.
Explanation: This is the normal response to the ZFILT command
with the DISPLAY parameter specified.
System Action: The contents of the packet filtering rules table are displayed.
User Response: None.
See TPF Operations for more information about the
ZFILT command and an example of the informational
display. See TPF Transmission Control
Protocol/Internet Protocol for more information about TCP/IP packet
filtering firewall support.
Explanation: This is the normal response to the ZFILT command
with the REFRESH parameter specified.
System Action: The packet filtering rules table is refreshed to core storage.
User Response: None.
See TPF Operations for more information about the
ZFILT command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about TCP/IP packet filtering firewall support.
Explanation: The ZFILT command was entered, but the TPF system
is in restart mode.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILT command.
Explanation: The ZFILT command was entered, but TCP/IP native
stack support is not defined.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILT command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about the SNAKEY parameters that are required for TCP/IP native stack
support. See TPF ACF/SNA Network Generation
for more information about the SNAKEY macro.
Explanation: The ZFILT command was entered with the REFRESH
parameter specified, but the /etc/iprules.txt file does not
exist.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILT command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about TCP/IP packet filtering firewall support and the
/etc/iprules.txt file.
Where:
Explanation: The ZFILT command was entered with the REFRESH
parameter specified, but an error occurred when opening the
/etc/iprules.txt file.
System Action: The command is rejected.
User Response: Look in errno.h to see a description of the error and do one
of the following:
See TPF Operations for more information about the
ZFILT, ZFILE ls, and ZFILE chmod commands. See TPF Transmission Control Protocol/Internet Protocol for
more information about TCP/IP packet filtering firewall support.
Explanation: The ZFILT command was entered with the REFRESH
parameter specified, but there are too many rules defined in the
/etc/iprules.txt file. You can have a maximum of 120
rules defined for TCP/IP packet filtering firewall support.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILT command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about TCP/IP packet filtering firewall support.
Where:
Explanation: The ZFILT command was entered with the REFRESH
parameter specified, but there was a syntax error in one of the rules in the
/etc/iprules.txt file.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILT command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about TCP/IP packet filtering firewall support.
Explanation: The ZFILT command was entered with the DISPLAY
parameter specified, but there is not enough storage in the TPF system to
display the packet filtering rules table.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZFILT command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about TCP/IP packet filtering firewall support.FILT0001I DISPLAY PACKET FILTERING RULES
FILT0002I PACKET FILTERING RULES REFRESHED
FILT0003E REJECTED, SYSTEM IS IN RESTART
FILT0004E REJECTED, TCP/IP NATIVE STACK SUPPORT NOT DEFINED
FILT0006E REJECTED, FILE /etc/iprules.txt DOES NOT EXIST
FILT0007E ERROR OPENING FILE /etc/iprules.txt, ERRNO description
FILT0008E TOO MANY RULES DEFINED IN FILE /etc/iprules.txt
FILT0009E ERROR ON LINE NUMBER num, ERROR NUMBER error
FILT0010E MALLOC ERROR, CANNOT DISPLAY IP PACKET FILTERING RULES TABLE
FINT0001I | FILE SYSTEM INITIALIZATION PENDING |
Explanation: This is the normal response for the ZFINT command with the ON parameter specified. This normal response indicates that the file system will be initialized when the TPF system reaches NORM state at the next cycle.
System Action: The file system is initialized if the TPF system cycles to NORM state without an intervening IPL or without a ZFINT command entered with the OFF parameter specified.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0002I | FILE SYSTEM INITIALIZATION NOT PENDING |
Explanation: This is the normal response to the ZFINT command with the OFF parameter specified. This normal response could be a result of one of the following:
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0005E | NOT ENOUGH INODE AND FLOCK RECORDS ARE AVAILABLE. ONLY number ARE AVAILABLE |
Where:
Explanation: The ZFINT command was entered with the ADD parameter specified to add more #INODE and #FLOCK fixed file records to the file system than were available for initialization.
System Action: The ZFINT command was rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFINT command. See TPF System Generation for information about the FACE table.
FINT0006I | INODE AND FLOCK RECORDS ADDED TO THE SYSTEM |
Explanation: This is the normal response to the ZFINT command with the ADD parameter specified.
System Action: The #INODE and #FLOCK fixed file records were added to the file system successfully.
User Response: None.
FINT0007I | NO INODES ADDED TO THE SYSTEM |
Explanation: This is the normal response to the ZFINT command with the ADD parameter specified. No #INODE or #FLOCK fixed file records will be added to the file system.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0008I | ONLY i OF THE INODE AND FLOCK RECORDS CAN BE USED BECAUSE OF TOO FEW IZERO RECORDS |
Where:
Explanation: Not all of the requested #INODE and #FLOCK fixed file records can be added because there are not enough #IZERO fixed file records.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZFINT command.
FINT0009I | NO INODE OR FLOCK RECORDS ADDED. THERE ARE NOT ENOUGH REQUESTED TO FIT INTO 1 IZERO RECORD. |
Explanation: The minimum of 1000 records must be added to the TPF system at one time.
System Action: No records were added to the TPF system.
User Response: Enter the ZFINT command again (with the ADD parameter specified) with at least the minimum of 1000 records.
See TPF Operations for more information about the ZFINT command.
FINT0010I | x INODE AND FLOCK RECORDS ADDED TO THE SYSTEM |
Where:
Explanation: A ZFINT command with the ADD parameter specified has successfully added x #INODE and #FLOCK fixed file records to the TPF system.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0011I | i OF j INODE AND FLOCK AND m OF n IZERO RECORDS ARE INITIALIZED |
Where:
Explanation: A ZFINT command with the ADD parameter specified has successfully added i #INODE and #FLOCK fixed file records to the TPF system.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0012I | FILE SYSTEM NOT INITIALIZED |
Explanation: A ZFINT command with the ADD parameter specified was entered but the file system was not initialized.
System Action: None.
User Response: Enter the ZFINT command with the ON parameter specified and then cycle the TPF system to NORM state.
See TPF Operations for more information about the ZFINT command.
FINT0014E | ERROR CREATING FILE SYSTEM name CACHE |
Where:
Explanation: This is the normal response to the ZFINT command with the DCACHE and ICACHE parameters specified when there are not enough system heap resources available.
System Action: Processing continues without the specified cache.
User Response: Make sure there are enough system heap resources available for the cache size being specified.
See TPF Operations for more information about the ZFINT command. See TPF System Generation for more information about using the CORREQ macro to verify and define system heap storage.
FINT0015I | FILE SYSTEM name CACHE CREATED |
Where:
Explanation: This is the normal response to the ZFINT command with the DCACHE or ICACHE parameter specified if the specified cache did not already exist.
System Action: The specified number of directory or i-node cache entries has been set in #IZERO fixed file record ordinal 0 of the file system and the cache has been created.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0016I | FILE SYSTEM name CACHE SIZE CHANGED |
Where:
Explanation: This is the normal response to the ZFINT command with the DCACHE or ICACHE parameter specified if the specified cache already exists.
System Action: The specified number of directory or i-node cache entries has been set in #IZERO fixed file record ordinal 0 of the file system for use on the next IPL.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0017I | FILE SYSTEM CACHE SIZE: DIRECTORY CACHE xxxxxx INODE CACHE xxxxxx |
Where:
Explanation: This is the normal response to the ZFINT command with the USAGE parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0018I | FILE SYSTEM name CACHE DELETED |
Where:
Explanation: This is the normal response to the ZFINT command with the DCACHE or ICACHE parameter specified when a size of 0 is specified and the specified cache already exists.
System Action: The number of directory or i-node cache entries has been set to zero in #IZERO fixed file record ordinal 0 of the file system and the active cache has been released.
User Response: None.
See TPF Operations for more information about the ZFINT command.
FINT0019E | ZFINT name ONLY VALID FROM THE BSS |
Where:
Explanation: The ZFINT command with the DCACHE or ICACHE parameter specified is valid only on the basic subsystem (BSS) because it is the only record the system will read for allocating the specified cache for the entire TPF system.
System Action: The request is ignored and the entry control block (ECB) exits without any action taken.
User Response: Enter the ZFINT command again and specify the DCACHE or ICACHE parameter on the BSS.
See TPF Operations for more information about the ZFINT command.
FINT0020I | OLD SIZE EQUALS NEW SIZE, NO CHANGE MADE |
Explanation: The cache size designated for the ZFINT command with the DCACHE or ICACHE parameter specified is the same as the current size.
System Action: No cache size change has been made.
User Response: Enter the ZFINT command again and specify a different cache size for the DCACHE or ICACHE parameter.
See TPF Operations for more information about the ZFINT command.
FKPA0001A | INSUFFICIENT CORE FOR WORKING STORAGE TOTAL CORE AVAILABLE = num_avail TOTAL CORE REQUIRED = num_req |
Where:
Explanation: There was insufficient working storage to carve out the number of core blocks specified in the keypoint A (CTKA).
System Action: The TPF system reduces the ECBs, input/output blocks (IOBS), frames, common blocks, and system work blocks (SWBs).
User Response: Do one of the following:
See TPF Operations for more information about the ZFKPA command.
FKPA0007A | SPECIFY OPTION -- TO CONTINUE RESTART ENTER -- ZFKPA RED TO CANCEL RESTART ENTER -- ZFKPA CAN |
Explanation: This message follows the FKPA0001A message, which indicates that there was insufficient working storage to carve out the number of core blocks was specified in the system keypoint A (CTKA).
The message is also issued when a parameter that is not valid was specified with the ZFKPA command.
System Action: Core block counts are reduced by the nucleus initialization program. The FKPA0003E message displays.
User Response: If the response is to continue, the file copy of keypoint A is updated with the reduced counts and filed back before continuing with the restart.
If the response is to cancel, state change is disabled.
See TPF Operations for more information about the ZFKPA command. Also see the FKPA0003E message.
FKPA0008A | NUMBER OF COMMON BLOCKS REDUCED TO num |
Where:
Explanation: This message is issued when there is insufficient storage below 16MB.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFKPA command.
FKPA0009A | NUMBER OF ECBS REDUCED TO num1 NUMBER OF FRAMES REDUCED TO num2 |
Where:
Explanation: This message is issued when there is insufficient storage below 16 MB.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFKPA command.
FKPA0010I | RESTART ABORTED PER OPERATOR REQUEST |
Explanation: A request was made to abort the restart.
System Action: Restart is exited and state change is disabled.
User Response: None.
See TPF Operations for more information about the ZFKPA command.
FKPA0011A | num PAGES REMOVED TO ACCOMMODATE VIRTUAL ADDRESS SPACE |
Where:
Explanation: This message is displayed when the size of the defined virtual address space overlaps with real storage.
System Action: The TPF system suspends restart processing and waits for you to accept the current configuration.
User Response: Enter one of the following:
See TPF Operations for more information about the ZFKPA and ZCTKA commands. See TPF Main Supervisor Reference for more information about the restart and state change functions.
FKPA0012I | MAXIMUM NUMBER OF THREADS REDUCED TO num |
Where:
Explanation: This message is displayed when the number of threads defined in keypoint A (CTKA) is greater than the amount of available storage.
System Action: The maximum number of threads was reduced.
User Response: None.
FKPA0013I | num PAGES REMOVED TO ACCOMMODATE VIRTUAL ADDRESS SPACE |
Where:
Explanation: This message is displayed when the size of the defined virtual address space overlaps with real storage.
System Action: The pages that are removed from the virtual address space are added to the machine check patch area and processing continues.
User Response: None.
FLBK0000I | SYSTEM PRINTER FALLEN BACK, NOW ON SUBCHANNEL aaaaa |
Where:
Explanation: The receive-only (RO) device became disabled and was replaced with the device on the subchannel specified in the message.
System Action: None.
User Response: None.
FLBK0001I | SYSTEM CONSOLE FALLEN BACK, THIS IS NOW THE SYSTEM CONSOLE SUBCHANNEL aaaaa |
Where:
Explanation: The prime computer room agent set (PRC) device became disabled and was replaced with the device on the subchannel specified in the message.
System Action: None.
User Response: None.
FLBK0010W | CONSOLE DOWN, aaaaa REPLACED BY LNIATA bbbbbb |
Where:
Explanation: The console specified in the message (prime computer room agent set (PRC), receive-only (RO), or PRC/RO) became disabled and was replaced with the device at the LNIATA specified in the message.
System Action: None.
User Response: None.
FLBK0020W | RO CRAS DOWN, NO REPLACEMENT AVAILABLE IN CRAS TABLE |
Explanation: The receive-only (RO) device became disabled and there was no valid alternate device available from the alternate (ALT) slots in the CRAS table (CRAT).
System Action: None.
User Response: Do the following:
FMNT0001I | GENERAL FILE DATA SET num MOUNTED ON addr |
Where:
Explanation: The general file data set specified in the message was mounted successfully. This message is issued when the BYPASS (BP) parameter is not specified on the ZFMNT command and it is verified that the specified general file data set exists on the specified device.
When the BP parameter is specified, this additional line is appended to the message:
DATA SET num MAY/MAY NOT BE CONTAINED ON THE GENERAL FILE MOUNTED ON addr
The volume label of the specified device is not checked to verify that the general file data set specified in this message is on the pack.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFMNT command.
FMNT0006E | MAXIMUM NUMBER OF DATA SETS ON SYSTEM |
Explanation: The data set number specified in the ZFMNT command exceeds the maximum allowable number of data sets.
System Action: The ZFMNT command is rejected and the ECB exits.
User Response: If the data set number is correct, then the general file definition program (CVZD) must be regenerated with an entry for the specified data set number. It them must be loaded to the TPF system along with a patch to CTKB to cause the general file control record to be rebuilt.
See TPF Operations for more information about the ZFMNT command.
FMNT0007E | DATA SET NOT ON THIS GENERAL FILE |
Explanation: The ZFMNT command specified a device address and a data set number. The volume label of the addressed device does not contain the data set number specified.
System Action: The request is ignored and the ECB is exited.
User Response: Do the following:
See TPF Operations for more information about the ZFMNT, ZDGFL, and ZAGFL commands.
FMNT0011E | DATA SET num NOT ASSIGNED TO SYSTEM |
Where:
Explanation: The data set number specified in the message is not within the legal range defined for general file data set numbers.
System Action: The request is ignored and the ECB is exited.
User Response: If the data set number is correct, then the general file definition program (CVZD) must be regenerated with an entry for that data set number. It then must be loaded to the TPF system along with a patch to CTKB to cause the general file control record to be rebuilt.
See TPF Operations for more information about the ZFMNT command.
FMNT0013E | DATA SET num PREVIOUSLY MOUNTED |
Where:
Explanation: The ZFMNT command request to mount general file data set specified in the message cannot be honored because it is already mounted at the time of this request.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFMNT command.
FMNT0014E | DATA SET num NOT MOUNTED. SDA addr NOT USABLE |
Where:
Explanation: In a TPF system that is not a multiple database function (MDBF) system, this message is issued when the address specified is not available for general file use. In an MDBF system, this message is issued for the same condition or when the address specified is outside the TPF subsystem from which the command originates.
This message may have been preceded by another error message with the CPAA prefix, which contains additional diagnostic information about any errors encountered while trying to mount the volume for general file use.
System Action: The request is ignored and the ECB is exited.
User Response: None.
See TPF Operations for more information about the ZFMNT command.
FMNT0015I | GFCR MIGRATION COMPLETE |
Explanation: Because a record ID (RID) or record control check (RCC) error occurred while accessing the general file control record (GFCR) in the #IBMMP4 fixed file record type, the GFCR was migrated from the existing #IBMM4 processor shared fixed file record to the new #IBMMP4 processor shared fixed file record.
System Action: TPF system restart continues.
User Response: None.
FMNT0017E | UNABLE TO MIGRATE GFCR |
Explanation: An error occurred while trying to read the general file control record (GFCR) from the #IBMMP4 fixed file record type. The attempt to migrate the GFCR from the existing #IBMM4 fixed file record to the new #IBMMP4 fixed file record failed. The GFCR is initialized in the #IBMMP4 fixed file record from premount definitions in segment CVZD.
System Action: TPF system restart continues.
User Response: Do the following:
See TPF Database Reference for information about the general file and the GFCR.
FMNT0018E | I/O ERROR READING PREMOUNT RECORD (CVZD) |
Explanation: An error occurred while trying to read the premount records from segment CVZD.
System Action: The system restart process is ended.
User Response: Do the following:
See TPF System Generation for more information about segment CVZD.
FMNT0019E | GENERAL FILE label PREVIOUSLY MOUNTED |
Where:
Explanation: After finding that the pack is not yet mounted, the program locates the pack's volume serial number (VSN) in the GFMT. This means you have two packs with different device addresses but with the same VSNs.
System Action: The request is ignored and the ECB is exited.
User Response: One of the two packs should be switched off the TPF system. Otherwise, on the next IPL, IPLB discovers the duplicate VSNs and throws both off the TPF system with an appropriate error message to the console.
See TPF Operations for more information about the ZFMNT command.
FMNT0020E | INVALID SSID FOUND ON VOLUME LABEL |
Explanation: The mount is not allowed because the TPF subsystem ID that owns the pack is not equal to the TPF subsystem ID from which the mount message originated.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZFMNT command.
FMNT0021E | I/O ERROR READING GENERAL FILE CONTROL RECORD |
Explanation: An error was encountered while trying to access the general file control record.
System Action: None.
User Response: None.
FMNT0022A | GENERAL FILE CONFIGURATION MISMATCH. MOUNT MISSING PACKS OR DISMOUNT MISSING DATA SETS, THEN HARD IPL |
Explanation: During processing for a general file restart in a loosely coupled complex, the input/output (I/O) device configuration available to the host processor is found to be different from the configuration that is available to other processors. The general file mount process is unable to continue because mountable DASD devices are not available. This check is made only if other processors are active. If this is the only active processor, the test is bypassed, the general file configuration keypointed as found, and the message is not sent.
System Action: The restart is aborted and the message is issued.
User Response: Do one of the following:
If this is the only active processor, then other processors must still be marked active in the processor status table. An IPL with the Destruct option should be done.
FMNT0024E | FACE ERROR -- INVALID RECORD TYPE |
Explanation: A file address compute program (FACE) error is returned on the computation of the general file control record.
System Action: None.
User Response: None.
FMNT0025E | FACE ERROR -- ORDINAL NUMBER OUT OF RANGE |
Explanation: A file address compute program (FACE) error was returned on the computation of the general file control record.
System Action: None.
User Response: None.
FMNT0026E | VSN label NOT FOUND. DATA SET num NOT MOUNTED |
Where:
Explanation: During general file restart, the volume specified in the message was not found. Therefore, the general file data set that resides on that volume cannot be mounted.
System Action: None.
User Response: None.
FMNT0027E | GENERAL FILE RESTART HAS NOT COMPLETED. |
Segment Reference: CVTT
Explanation: A ZFMNT command was entered but the TPF system has not completed general file restart.
System Action: The ZFMNT command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZFMNT command.