Chapter 10: Fileshare Server Messages

There are three levels of messages that can be produced by the Fileshare Server. These are of varying levels of severity:

• Severe

  Severe level messages indicate that a problem has occurred that has prevented the Fileshare Server carrying out the requested operation. The cause of the error should be rectified and then the operation tried again.

• Warning

  Warning level messages indicate that a situation was encountered that the Fileshare Server was not expecting, but was able to continue.

• Informational

  Informational level messages provide information about the operations that the Fileshare Server is performing.

The format of each message is as follows:

FSnnn-x text

where:

FS001-S The parameter "text " is not recognized as a valid parameter.

• This error status is displayed when the Fileshare Server parses the specified parameters and finds one which it does not recognize.

  The operation did not complete.

• Change the indicated parameter and retry the operation.

  The valid parameters are given in the sections:

  • Server Configuration in the chapter Configuration

  • Database Reference File Maintenance and Rollforward Recovery Utility in the chapter Database Integrity

  • Password File Maintenance in the chapter Security

FS004-S The parameter "text " specifies a time-out value that is invalid.

• The /t parameter has been specified in a configuration file, but the characters following do not conform to a valid specification of a time-out value.

  The time-out value is specified in seconds and must be in the range 0 through 99999.

  See the section Automatic Record Lock Timeout in the chapter Database Integrity for more information.

• Retry the operation using a time-out value in the correct range

FS005-S The parameter "text " is too long or invalid.

• The parameter indicated could not be processed correctly. This can be for one of the following reasons:
  • The parameter specified is too long. For example a password has been specified which is more than 20 characters in length.

  • The parameter expects a value, but none has been given. For example, the /t parameter has been specified but no time-out value has been given.

• Retry the operation using a correct value for the parameter indicated

FS006-S The parameter "text " has already been specified.

• A duplicate parameter has been specified and duplicates are not permitted for this parameter

• Retry the operation ensuring that only one occurrence of the parameter exists

FS007-S Invalid parameter combination.

• Fileshare has processed the specified parameters and is unable to process the information given.

  This can be for the following reasons:

  • Not enough parameters have been specified in order for the operation to be processed. For example, you have tried to start the Fileshare Server without giving a server name.

  • The parameters specified do not indicate a valid operation that can be carried out. For example, the combination /s and /r is invalid as the first implies that the Fileshare Server is to start with the server name indicated, whereas the second parameter indicates that a Rollforward Recovery is to be performed.

• Ensure that the parameters specified are correct and retry the operation

FS008-S Communications Initialization Failure.

• An error has occurred when the Fileshare Server initialized CCI or the Fileshare Server was unable to perform the CCI call because the required operating system and/or Micro Focus communication support modules are not available. This error can also indicate a problem with the network setup on the machine (for example, the required drivers have not been loaded).

• Ensure that the required CCI module(s) required for the protocol you are using is/are available. Use the CCI demo program supplied with the product to ensure that the CCI module required can be loaded and initialized.

• Ensure that the network software on the machine is installed, configured and operational

FS009-S The required communications module cannot be found.

• The Fileshare Server tried to load the CCI module required for the protocol specified, but was unable to do so. This implies that the CCI module (or required support modules) cannot be found or they cannot be loaded.

• Ensure that the CCI (and required network modules) are installed correctly on the machine

• Try out the CCI demo program supplied with the product with the same CCI protocols before trying the start the Fileshare Server again

FS011-W Communications send failure.

• The Fileshare Server encountered a communications error when it tried to return the result of an I-O operation to a Fileshare Client. This can imply that there is a problem with the network or that the Fileshare Client process terminated abnormally.

  See the message FS148-I for more information.

• No user action is possible. However, if the error persists, this could indicate that there is a possible problem with the network or that the network has a high volume of traffic.

FS012-W Communications disconnect failure.

• The Fileshare Server tried to drop the connection with the Fileshare Client, but the communications system returned an error. The Fileshare Server tries to disconnect from Fileshare Clients when:
  • It receives a request from an unknown Fileshare Client

  • The CCI protocol indicated that the Fileshare Client application terminated abnormally

• If the error persists, there could be a problem with the network that is being used. Also, ensure that users are closing down Fileshare Client applications correctly and not turning the workstation machines off or using utilities to terminate the Fileshare applications abnormally (for example kill on UNIX).

FS013-W Communications receive error.

• An unexpected error occurred while receiving information from the communications system. This error implies a problem with the network software or hardware because a message has been received but could not be processed correctly.

  See the message FS148-I for more information about the cause of the error.

• No direct action by the user is possible. However, if the error persists, there could be a problem with the network that is being used or there could be a high volume of network traffic.

FS014-W Communications data length not as expected.

• The information sent from the Fileshare Client to the Fileshare Server includes a check on the amount of information that is being sent. This error occurs when the amount of data received by the Fileshare Server is not the same as the amount sent by the Fileshare Client.

  This error should not occur in normal circumstances. If found, it implies that there is a problem with the communications system or that the requester service has not been started when using the NETBIOS protocol.

  The Fileshare Server has ignored the data sent from the Fileshare Client.

  See also the messages FS151-I and FS082-S for additional information.

• If using the NETBIOS protocol, ensure that it is installed correctly, configured and operational.

  It is highly likely that the Fileshare Client appears to have stopped because the Fileshare Server has not sent back any reply. Depending on the CCI protocol being used, a time-out occurs in approximately two minutes and a 9/124 status is returned to the application program.

FS015-W Request from unknown user - request rejected.

• The information received by the Fileshare Server is not recognized as being from a Fileshare Client that is currently logged onto this Fileshare Server.

  The Fileshare Server has ignored the information that it has received and has returned a 9/125 error status to the Fileshare Client that sent the request.

  With some CCI protocols, the session associated with this request is disconnected. See the message FS238-I for additional information.

• No action is required

FS016-S The parameter "text " is invalid.

• The parameter has been recognized as a valid parameter, but the option specified for that parameter is not valid. For example, the /o (omit) parameter has been specified, but the option is not t (transaction processing), l (rollforward recovery logging) or s (sequence number checking).

• Change the parameter specified to a valid option

FS017-S Unable to open the file : filename.

• The Fileshare Server is unable to create the file specified.

  The file may be open already or marked as read-only.

• Ensure that the path and filename are valid and that the Fileshare Server has read and write access to the directory

FS018-S Log file corrupt - unrecognizable record in file.

• Each record written to the recovery log file has a marker informing the Rollforward Recovery Utility of the type of data contained in the record.

  This error indicates that the marker in the record header is not recognized which implies that the log file has become corrupted in some way.

  This error can occur if the last record of the recovery log file was not written successfully because of a system crash. The Recovery Utility will have processed all of the records up to the point of failure.

• Ensure that the correct log file is available to the Fileshare Rollforward Recovery Utility

FS019-S Log file corrupt - can't read header.

• Each record written to the recovery log file has a marker indicating the type of data contained in the record. This error indicates that the required header record at the beginning of the log file was not found. This implies that the log file has become corrupt, which can happen, for example, if the system crashed while records were being written to the recovery log file.

• Ensure that the correct log file is available to the Fileshare Rollforward Recovery Utility. If the correct log file is in place, then the file is corrupt and cannot be used in a rollforward recovery process.

FS020-S The log file does not match the database sequence numbers - recovery aborted.

• Each index file (not C-ISAM) and all variable length record files have (by default) a sequence number stored in the header of the file. A corresponding sequence number is stored in the log file. Checks are made between the sequence numbers in the file headers and the log file to help ensure that the recovery process proceeds successfully.

  This error indicates one of the following:

  • The sequence number in the file headers is greater than that in the log file. This indicates that updates have been applied to the files, without the updates being logged in the log file. Because the log file does not contain all of the updates, it is not possible to perform a rollforward recovery. This also indicates that the rollforward recovery is trying to use the wrong versions of the files.

  • The first sequence number in the recovery log file is larger than the sequence number in the file headers. This indicates that updates have been written to the log file but they have not been applied to the data files. It is not possible to apply the updates from the recovery log file because the versions of the data files and the recovery log file do not match.

• Ensure that the correct versions of the data and rollforward recovery log file are being used. See the section Database Sequence Numbering in the chapter Database Integrity for more information.

FS021-S There is no log filename specified in the database reference file.

• You have tried to erase a log file entry from the database reference file but there is no log filename specified in the database reference file. The operation therefore cannot be completed successfully.

• No action is necessary

FS022-S The log filename given cannot be found in the database reference file.

• You have failed to erase a log file entry from the database reference file because the log filename specified is not the same as the log filename in the database reference file

• Specify the correct name of the log file when trying to erase the entry from the database reference file

FS024-S Failed to open log file : filename.

• The Fileshare Server encountered an error while trying to open or create the rollforward recovery log file. Common causes of this error are:
  • The Fileshare Server does not have read/write access to the log file and/or the directory where the log file resides

  • The filename specified for the log file is invalid. The filename may not be a valid filename for the operating system on which the Fileshare Server resides or the path specified in the log filename specifies a drive/directory that does not exist.

  • The log file is in use by another process, preventing the Fileshare Server from obtaining exclusive access to the log file

  • The operating system or the COBOL run-time system is unable to allocate a file handle to the log file

FS025-S Write failure to the log file, Fileshare Server is closing down.

• The Fileshare Server encountered an error while writing a record to the recovery log file. Because the integrity of the log file cannot be guaranteed, the Fileshare Server shuts down so that the updates performed up to the point of failure are not lost.

• The cause of the failure should be investigated. Possible causes include the disk is full, a disk error or, if logging to a remote drive, a network error occurred.

  We advise you to have the recovery log file local to where the Fileshare Server is running so that the chances of network errors occurring while writing to the log file are reduced. Also, the Fileshare Server cannot force the operating system to flush records to disk if the log file is not on the local machine.

FS026-W Failed to close the log file.

• The Fileshare Server encountered an error while closing the current log file.

  Possible causes are that the disk is full or, if logging to a remote drive, a network error occurred.

  We advise you to have the recovery log file local to where the Fileshare Server is running so that the chances of network errors occurring while writing to the log file are reduced.

• The cause of the failure should be investigated.

  It should be possible to use this recovery log file in a rollforward recovery operation as the Fileshare Server has written all of the required information to the file.

FS027-S A second log file parameter has been found.

• While processing the database reference file, a second log file parameter was found. There should only ever be one log file specified in the database reference file and this error indicates that the database reference file is corrupt or has been changed without using the Database Reference File Maintenance Utility.

• Ensure that the correct database reference file is used and that only one recovery log filename is specified in the database reference file.

  Only use the Database Reference File Maintenance Utility to change the contents of the database reference file. In this situation however, it may be possible to remove the duplicate entry using a normal text editor. Alternatively the current database reference file can be discarded and a new one created using the Database Reference File Maintenance Utility.

FS028-W The log file shows the last session was not shut down successfully.

• When the Fileshare Server shuts down successfully, the last record written to the recovery log file is a special record that marks the end of the recovery log file. This message indicates that the Fileshare Server could not find the special, last record when it opened the log file, suggesting that the log file was not closed in a controlled manner, probably due to a system crash. The log file could have been opened either to append to or read from in order to perform a rollforward recovery.

  If the Fileshare Server is starting up, the log file is backed up and a new log file created. If you have specified a backup directory in the database reference file, the Rollforward Recovery Utility is invoked automatically.

  If a rollforward recovery is being performed, recovery proceeds up to the last full record in the recovery log file (any incomplete transactions are rolled back).

• No action is required

FS029-S The log filename is already specified in the database reference file.

• You have tried to add the name of the recovery log file to the database reference file. However a log filename already exists in the database reference file. A database reference file can only contain one log filename.

• Remove the current log filename from the database reference file using the Database Reference File Maintenance Utility and then add the name of the new log file using the same utility

FS030-S Insufficient disk space to continue logging to log file.

• The amount of space remaining on the disk where the log file is being written has less than 200K bytes of free space remaining. This is not adequate to ensure that the recovery log file can continue to be successfully written.

  The Fileshare Server will close the current recovery log file and wait for it to be backed up before continuing.

• Manually back up the current log file and then delete the file. This releases disk space and enables the Fileshare Server to continue logging with a new logfile.

FS031-I Record lock time-out failure on user : user.

• A record lock time-out has occurred on the user indicated. This is due to the user holding a lock on a record for a period of time longer than the record lock time-out period, when another user is trying to access that locked record.

  This record lock time-out has caused any transactions that this user has outstanding to be automatically rolled back and all record locks held by this user have been released. See the section Automatic Record Lock Timeout in the chapter Database Integrity for more information.

  You can specify the record lock time-out period using the /t option when you configure the Fileshare Server.

  On the next I/O operation, a status of 9/125 will be returned to the Fileshare Client application that held the lock.

• No action is required, however the time-out period can be changed or disabled if required

FS034-S A filename or log file parameter must be specified.

• The Database Reference File Maintenance Utility has been invoked using the /d option, however a valid parameter for the utility has not been given

• Ensure that when invoking the Database Reference File Maintenance Utility, the option /f (filename), /l (log filename), /fs (file string) or /backup (log file backup directory) is used to specify which action should be taken

FS035-S A database reference file must be specified.

• The Database Reference File Maintenance Utility has been invoked, however the name of the database reference file to use has not been specified using the /d parameter. For example, the parameter /f (filename), /l (log filename), /fs (file string) or /backup (backup directory) has been used to invoke the Database Reference File Maintenance Utility but a /d option has not been specified to supply the name of the database reference file.

• Include the /d option when invoking the Database Reference File Maintenance Utility to provide the name of the database reference file to use

FS037-I The file filename does not have a file header record. Sequence checking is switched off for this file.

• The Fileshare Server has determined that the file indicated does not have a Micro Focus format file header. It is not possible to have sequence numbering on files that do not contain file headers. However, the configuration of the database reference file specifies that sequence number checking should be applied to this file.

  The Fileshare Server will not apply sequence number checking to this file.

• The programs accessing the files should be changed so that they define the files as variable length record files.

  It is not possible to have sequence number checking on line sequential files.

  If sequence number checking is required, the file must contain a file header. Fixed length indexed, sequential and relative files should be converted to variable length record format.

  Alternatively, if sequence number checking is not required for this file, this message can be avoided by explicitly turning sequence number checking off using the /o s option in this file's entry in the database reference file. See the section Database Reference File Maintenance in the chapter Database Integrity for more details.

FS038-S A matching sequence number not found in filename.

• This error message is displayed when the sequence number in the header of the named file does not match the sequence number in the rollforward recovery log file. See the section Database Sequence Numbering in the chapter Database Integrity for full details of database sequence numbering works.

  The named file is listed in the database reference file and sequence number checking is active for the file. This message indicates that an incorrect version of the file is being used. The Fileshare Server does not start until this problem is rectified.

• Ensure that the correct version of the file is available to the Fileshare Server and that if sequence numbering is used, all updates performed to the file are done via the Fileshare system. See the section Database Sequence Numbering in the chapter Database Integrity for more information.

FS039-S Improperly closed file - filename.

• The Fileshare Server has found that the file indicated has been marked as corrupt because it was not closed correctly. This implies that the file was not closed in a controlled manner and that the Fileshare Server last accessing the file terminated abnormally.

• The file is corrupt and a backup should be put in place and recovery performed using the Rollforward Recovery Utility. See the section Rollforward Recovery Utility in the chapter Database Integrity for details. If you have specified a backup directory in the database reference file, the recovery will be performed automatically.

  If updates to the file have not been logged then the file should be rebuilt using the REBUILD utility.

FS040-S Unable to read the file header record in the file filename.

• The Fileshare Server was able to open the file specified, but was not able to read the file header. The file header consists of the first 128 bytes of the file.

• If sequence number checking is not required for this file then this feature should be omitted for this file using the /o s option in the database reference file.

  All files that can have sequence number checking are at least 128 bytes in length as this is the size of a file header (which is required for sequence number checking to be performed).

FS041-S Unable to update the sequence number in the file filename.

• The Fileshare Server was unable to update the sequence number in the header of the file specified. The sequence number in the header of this file cannot be relied on and hence messages relating to incorrect sequence numbers can be ignored. However, careful checks should be made to ensure that the correct version of the file are in place when starting the Fileshare Server or performing a rollforward recovery.

• This error is very rare and implies a disk I/O error (or a network error if the file is not on the local Fileshare Server machine)

FS042-S Unable to open the database reference file: filename.

• The Fileshare Server was unable to open the database reference file indicated

• Ensure that the path and filename are correct and that the Fileshare Server has full read and write access to the file specified.

  Also ensure that the Fileshare Server can gain exclusive access to the database reference file and that another process does not have the file open.

FS043-S The database reference file contains an invalid entry.

• The Fileshare Server has found data in the database reference file which is not as expected. This implies that the database reference file has been changed without using the Database Reference File Maintenance Utility or that the database reference file is corrupt in some way.

• Ensure that only the Database Reference File Maintenance Utility is used to change the contents of the database reference file.

  Alternatively, discard the current database reference file and re-create the contents of the file using the Database Reference File Maintenance Utility.

FS044-S Error reading the database reference file.

• An error was encountered when reading the database reference file. The file was successfully opened by the Fileshare Server. This message implies that the file is corrupt or that a disk I/O error occurred. Alternatively, if the database reference file is on a remote drive, a network error could have occurred.

• Try the operation again. If the problem persists, the database reference file is probably corrupt - the current file should be discarded and a new database reference file created using the Database Reference File Maintenance Utility.

FS045-W Duplicate filename specified in the database reference file.

• A duplicate filename was found when the Fileshare Server processed the database reference file. This message implies that the database reference file has been modified, but not using the Database Reference File Maintenance Utility. A given filename should appear only once in the database reference file.

• Recreate the database reference file ensuring that each filename appears in the file only once

FS050-W A log file is not specified in the database reference file.

• The Fileshare Server processed the database reference file but could not find a rollforward recovery log filename. The database reference file should have a recovery log file specified in order that recovery logging can be performed.

• If rollforward recovery logging is required, add an entry to the database reference file specifying a rollforward recovery log filename. See the section Database Reference File Maintenance in the chapter Database Integrity for more details.

FS051-W Failure to allocate a larger buffer, the I-O request failed.

• When using compression on the communication buffers, this message indicates that there was not enough memory available to the Fileshare Server to enable it to decompress the buffer. The I/O request has failed and the Fileshare Client was returned a 9/105 (out of memory) error.

• Free some memory on the machine where the Fileshare Server is running so that it is able to increase the size of its decompression buffers.

  Alternatively, reconfigure the Fileshare System so that compression on the communications buffers is not used.

FS052-S Failure to allocate required memory. The Fileshare Server is closing down.

• You see this message when the Fileshare Server is initializing and cannot allocate enough memory for the required internal tables

• Free some memory on the machine where the Fileshare Server is running so that more memory is available to the Fileshare Server

FS055-S The parameter "text " specifies a configuration file that does not exist.

• The Fileshare Server is unable to locate or open the configuration file indicated

• Ensure that the path and filename are correct and that the Fileshare Server has read access to the file. Also ensure that no other process currently has the file open as the Fileshare Server requires exclusive access to the configuration file.

FS056-S The parameter "text " specifies a data compression value that is not within the range 0-255.

• You have tried to add an entry to the database reference file. This entry specifies a value for the data compression outside of the permitted limits. The data compression option must specify a value within the range 0 through 255. To use the routine CBLDC001 as the compression method on records in the file, specify a compression value of 1.

  The specification of compression of records only takes effect when the file is created. Specifying data compression on a file that already exists and contains uncompressed records has no effect.

• Specify a data compression value of 0 through 255

  See the section Database Reference File Maintenance in the chapter Database Integrity for more information on the /k parameter and valid options.

FS057-S The parameter "text " specifies a key compression value that is not within the range 0-7.

• You have tried to add an entry to the database reference file which specifies a value for the key compression outside of the permitted limits.

  The key compression option must specify a value within the range 0 through 7.

  Specifying key compression only has an effect at the time that the file is created. Specifying key compression on a file that already exists, but does not have key compression, has no effect.

• Specify a key compression value of 0 through 7.

  See the section Database Reference File Maintenance in the chapter Database Integrity for more information on the /k parameter and valid options.

FS058-S Failure to allocate memory for the decompression of the log file.

• The Rollforward Recovery Utility has been invoked but is unable to allocate the required memory so that it can process the recovery log file. This error is displayed during the initialization of the recovery process and indicates a shortage of available memory.

• Increase the amount of available memory by reducing the number of processes and/or applications running on the same machine where you are running the Rollforward Recovery. Then try to run the Rollforward Recovery Utility again.

FS059-S Failure to allocate the memory required for processing the database reference file.

• When reading in a database reference file (either when the Fileshare Server or the Rollforward Recovery Utility is starting) this message indicates that the Fileshare Server was not able to allocate the required memory to be able to process all of the information in the database reference file

• Try to make more memory available to the Fileshare Server by reducing the number of processes or applications that are running on the same machine. If this is not possible, reduce the amount of information that is contained in the database reference file.

FS062-S Failure creating the password file filename.

• The Fileshare Server was unable to create the password file indicated

• Ensure that the path and filename are valid and that the specified file is not already open by another process. The Fileshare Server requires read and write permission to the password file and tries to create the file with exclusive access.

FS063-S Failure opening the password file filename.

• The Fileshare Server was unable to open the password file indicated

• Ensure that the path and filename are valid and that the specified file is not already open by another process. The Fileshare Server requires read and write permission to the password file and tries to open the file with exclusive access.

FS064-S Failure reading the password file filename.

• The Fileshare Server encountered an error reading the information from the password file. This implies that an I/O error occurred, the password file has become corrupted in some way or that a network error occurred if the password file is located on a remote machine.

• Retry the operation. If the message persists, the password file may be corrupt and should be discarded. A new password file should then be created using the Password File Maintenance Utility.

FS065-S The password file is not of a recognized format.

• The first record in the password file is a special record which indicates to the Fileshare Server that the file is a password file. This record also contains information regarding the version of the password file being used.

  This message indicates that the Fileshare Server has not recognized this record in the file as being that identifying a password file. Alternatively the password file has become corrupt.

• Check that the path and filename of the password file specified are correct.

  If they are correct then the current password file should be discarded and a new one created using the Password File Maintenance Utility.

FS066-S The specified user name already exists in the password file.

• You see this message when using the Password File Maintenance Utility and you have tried to add a user name to the password file when the user name already exists in the password file

• To update a user entry that already exists in the password file, first erase the entry and then add the new entry to the file. See the section Password File Maintenance in the chapter Security for more details.

FS068-I The password file is now empty and has been deleted.

• You see this message when you have used /e (erase) option with the Password File Maintenance Utility to remove the last entry from the password file. As the password file is now empty, it has been deleted. If a new password file is required it is created automatically when you add an entry using the Password File Maintenance Utility.

• No action is required

FS069-S The specified entry could not be found in the password file.

• This message indicates that you have used /e (erase) option with the Password File Maintenance Utility to remove an entry, but the entry specified does not exist in the password file.

• Ensure that the user name and password are correct (that is, exactly those which were specified for the entry to be erased when the entry was first added to the password file). If the user-ID or password are no longer known, you must create a new password file using the Password File Maintenance Utility.

FS070-S Failure writing to the password file.

• The Password Maintenance Utility encountered an error when it tried to write information to the password file. This implies that an I/O error occurred (possibly a full disk) or a network error was encountered (if the password file is on a remote machine). The integrity of the password file cannot be guaranteed.

• Restore the password file from a backup and try to add the new entry again. If no backup is available, discard the current password file and create a new one using the Password File Maintenance Utility.

  Ensure that there is enough disk space available on the drive where the password file resides.

FS071-W Unable to load the module FHXSCOMP to decompress the data area.

• This message indicates that the Fileshare Server has received a compressed communications buffer. However, it is unable to load the decompression module FHXSCOMP in order to perform the necessary decompression. There may not be enough memory to load the module or the module may not be found.

  Alternatively there may be an insufficient number of file handles available to enable the operating system or run-time system to load the module.

  The request received from the Fileshare Client has been discarded.

• Ensure that the system module FHXSCOMP is available on your system. Also ensure that there is enough memory available for the module to be loaded and file handles are available to enable the run-time or operating system to load the file.

FS072-S The parameter "text " contains a wild card which is not allowed with this parameter.

• A parameter containing a wild card symbol was specified when invoking the Database Reference File Maintenance Utility but the parameter does not support wild cards.

  Wild cards are only permitted on database entries defining an alternate program.

  See the /ap option in the section Database Reference File Maintenance in the chapter Database Integrity for more details.

• Do not specify a wild card symbol for this parameter.

  A full path or filename should be given.

FS073-S Failure to allocate memory to process the password file.

• When reading in a password file (when either the Fileshare Server or the Password File Maintenance Utility is starting), this message indicates that the Fileshare Server was not able to allocate the required memory to be able to process all of the information in the password file.

• Try to make more memory available to the Fileshare Server by reducing the number of processes or applications that are running on the same machine. Alternatively, reduce the amount of information that is contained in the password file.

FS074-S The Fileshare Server (NLM) failed to log on to NetWare with the login id specified.

NLM:
This message is only applicable to the Fileshare NLM.

• You see this message when using the /nu option to force the Fileshare Server to log onto NetWare with the specified user-ID. However, the Fileshare NLM Server encountered an error when trying to connect with the user-ID specified. This implies that there is no user account with the user-ID set up on the NetWare server or that you entered an incorrect password when prompted to do so.

• Check that the user-ID is correct and that a user account for that ID is defined on the NetWare operating system. Also check that the correct password for this user-ID was entered when prompted.

FS075-W Unable to load the module FSSECLOG - LOGON has been denied.

• This message indicates that the Fileshare Server failed to call the module FSSECLOG because:
  • FSSECLOG is not available

  • There is insufficient memory available to load FSSECLOG

  • There may be an insufficient number of file handles available to enable the operating system or run-timesystem to load FSSECLOG

  FSSECLOG is required to validate logon requests to the Fileshare Server by Fileshare Clients. Because one possible cause of this error is that the FSSECLOG module has been removed on purpose, the Fileshare Server does not permit the logon to proceed in this situation.

  The Fileshare Client application program has received a 9/037 error status.

• Ensure that the module FSSECLOG is available to the Fileshare Server (this can be the FSSECLOG module supplied with the Fileshare system or a user-written one). If the module is available, try making more memory available by reducing the number of other processes or applications running on the machine and ensure that there are enough free file handles available to enable the module to be loaded.

  See the chapter Security for more information about the FSSECLOG module.

FS076-W Unable to load the module FSSECOPN - OPEN has been denied.

• This message indicates that the Fileshare Server failed to call the module FSSECLOG because:
  • FSSECOPN is not available

  • There is insufficient memory available to load FSSECOPN

  • There may be an insufficient number of file handles available to enable the operating system or run-timesystem to load FSSECOPN

  FSSECOPN is required to validate open requests to the Fileshare Server by Fileshare Clients. Because one possible cause of this error is that the FSSECOPN module has been removed on purpose, the Fileshare Server does not permit the open to proceed in this situation.

  The Fileshare Client application program has received a 9/037 error status.

• Ensure that the module FSSECOPN is available to the Fileshare Server (this can be the FSSECOPN module supplied with the Fileshare system or a user-written one). If the module is available, try making more memory available by reducing the number of other processes or applications running on the machine and ensure that there are enough free file handles available to enable the module to be loaded.

  See the chapter Security for more information about the FSSECOPN module.

FS077-S A Fileshare Server of the same name has already been defined - the Fileshare Server is closing down.

• When the Fileshare Server starts up, it registers its name on the network so that Fileshare Clients can connect to it. This message indicates that the Fileshare Server is trying to register with a name that is already in use by another Fileshare Server on the network.

  Alternatively, this message can indicate that a Fileshare Server that was using this name terminated abnormally and did not de-register its name from the network.

• Ensure that the Fileshare Server name is unique for this server. This is the name that the Fileshare Server is configured to register on the network. If a Fileshare Server that was using this name terminated abnormally, it may be necessary to re-initialize the network software on the machine where that Fileshare Server was running to ensure that its name is no longer registered (what action is required in this situation depends on the communications protocol that is being used).

UNIX:

FS078-S No password file has been specified for the use of background mode.

This message is applicable to Fileshare Servers on UNIX only.

• It is possible to configure the Fileshare Server to run as a daemon process on UNIX so that information is neither accepted from the keyboard nor displayed on the screen. When configuring the Fileshare Server to run in this mode, a password file must be used which should contain a FSVIEW (supervisor) user-ID and password. This enables the Fileshare Server to be closed down remotely using FSView, FSMgr or FSCLOSE.

  This message indicates that you have tried to run the Fileshare Server in background mode but you have not specified a password file.

• Create a password file using the Password File Maintenance Utility containing a user-ID of FSVIEW and a password. Then specify this password file (using the -pf option) in the Fileshare Server configuration file.

  See the section Password File Maintenance in the chapter Security for more information.

UNIX:

FS079-S A supervisor password entry must exist for the use of background mode.

This message is applicable to Fileshare Servers on UNIX only.

• It is possible to configure the Fileshare Server to run as a daemon process in the background on UNIX where no information is accepted from the keyboard nor displayed on the screen. When configuring the Fileshare Server to run in this mode, a password file must be used which should contain an FSVIEW (supervisor) user-ID and password. This enables the Fileshare Server to be closed down remotely using FSMgr, FSView or fsclose.

  This message indicates that you have tried to run the Fileshare Server in background mode but the password file that you specified does not contain an FSVIEW (supervisor) user-ID or password.

• Add a user-ID of FSVIEW and password to the password file specified using the Password File Maintenance Utility.

  See the section Password File Maintenance in the chapter Security for more information.

FS080-S No password file has been specified for the use of the synchronous communications mode.

• You have tried to start the Fileshare Server using synchronous communications (as opposed to asynchronous communications which is the default). To enable the use of synchronous communications, you must specify a password file which contains a supervisor-ID of FSVIEW. This enables the Fileshare Server to be closed down remotely using FSVIEW or FSMgr. This is necessary because in this communications mode, the Fileshare Server only checks for keyboard input very occasionally.

• When starting the Fileshare Server, use the /pf option in the Fileshare Server configuration file to specify the name of a password file containing a user-ID of FSVIEW. See the sections Password System and Password File Maintenance in the chapter Security for more information.

FS081-S A supervisor password must be specified in the password file for the synchronous communications mode.

• You have tried to start the Fileshare Server using synchronous communications (as opposed to asynchronous communications which is the default). To enable the use of synchronous communications, you must specify a password file which contains a user-ID of FSVIEW. This enables the Fileshare Server to be closed down remotely using FSVIEW or FSMGR. This is necessary because in this communications mode, the Fileshare Server only checks for keyboard input very occasionally.

  This message indicates that a password file has been specified, however, there is no (supervisor) user-ID of FSVIEW in the password file.

• Add a user-ID of FSVIEW and a password to the password file using the Password File Maintenance Utility and try the operation again. See the section Password File Maintenance in the chapter Security for more information.

FS082-S The Netbios communications protocol is not responding. Ensure the requester software is loaded and functional.

• You have tried to start the Fileshare Server using the Netbios protocol (CCINETB) but the required network software is not loaded or is not operational. The Fileshare Server is trying to use the NETBIOS software but is receiving invalid data.

• Ensure that the NETBIOS software has been loaded, is functioning and is configured correctly on the machine where you are trying to start the Fileshare Server. Try to start the Fileshare Server again. Alternatively, use another communications protocol.

  See the message FS014 for further information.

FS083-S Incompatible CCIIPX.NLM version.

• The Fileshare NLM Server has detected that the version of cciipx.nlm being used is not a compatible version. You are probably trying to use an old version of the CCIIPX NLM with this version of the Fileshare NLM.

• Ensure that the version of cciipx.nlm supplied with the Fileshare Server NLM is the one on the system and that this version is loaded in preference to any earlier version (meaning that this version is on the search path before any older version of the CCIIPX NLM)

FS084-I Fileshare Server is starting.

• This message indicates that the Fileshare Server is in the process of initializing. The configuration, database reference and password files (if specified) are being processed and the communications software is being loaded and initialized.

• No action is required

FS085-I Fileshare Server is active.

• This message indicates that the Fileshare Server has completed its initialization processing and is now ready to accept incoming requests from Fileshare Clients. At this stage all of the configuration, database reference and password files have been processed and the communications software has been successfully initialized and is operational.

  Fileshare Client applications can now be started and communicate with this Fileshare Server.

• No action is required

FS086-I Fileshare Server is closing down.

• This message indicates that the Fileshare Server has started the process of closing down and will shortly terminate. This can be invoked by the following:
  • The Fileshare Server encountered an error when starting up, for example an error was found in a configuration, database reference or password file. Alternatively the communications support could not be started.

  • The user has requested to shut down the Fileshare Server (either by the Esc key sequence or a remote request from FSView or FSMgr)

  • The Fileshare Server has encountered an unrecoverable error during its operation. For example, the remaining disk space where the rollforward recovery log file resides is below the acceptable limits for logging to continue.

  • The Fileshare Server process was terminated by an event external to the Fileshare Server (for example a kill command on UNIX)

  The Fileshare Server is closing all outstanding connections with Fileshare Clients, rolling back any outstanding transactions, closing all open files and shutting down the communication support.

  Depending on the communications protocol that is in use, the Fileshare Client applications may appear to suspend if they are still trying to send requests to this Fileshare Server.

• No action is required

FS087-I Fileshare Server has closed down.

• This message indicates that the Fileshare Server has completed all of its termination processing. All communications have stopped, all files closed, all transactions rolled back and any rollforward recovery log file shut. The Fileshare Server can now be restarted when necessary.

• No action is required

FS089-I Database Reference File Maintenance Utility.

• The Database Reference File Maintenance Utility has been invoked using the parameters specified on the command line or in the Fileshare Server configuration file. The Database Reference File Maintenance Utility will try to process the remaining parameters specified as options to this utility.

  If the Database Reference File Maintenance Utility should not have been invoked, check the command line to ensure that neither the /d option nor any other valid Database Reference File Maintenance option has been specified. See the section Database Reference File Maintenance in the chapter Database Integrity for more details.

• No action is required

FS090-I Database Reference File installation completed successfully.

• The Database Reference File Maintenance Utility has been invoked successfully and the required change made to the database reference file has been made.

  The database reference file specified now contains the change required.

• No action is required

FS091-I Rollforward Recovery Utility

• The Rollforward Recovery Utility has been invoked using the parameters specified on the command line or in the Fileshare Server configuration file.

  If the Rollforward Recovery Utility should not have been invoked, check the command line to ensure that neither the /r option nor any other valid Rollforward Recovery Utility option has been specified. See the section Rollforward Recovery Utility in the chapter Database Integrity for more details.

• No action is required

FS092-I Rollforward Recovery has completed.

• The recovery process is now complete: the files contain the updates recorded in the log file when the Fileshare Server was in use.

  If the updates have been applied successfully, you should back up the recovered files and use a new log file when you restart the Fileshare Server. This ensures that the new recovery log file is in step with the current data files.

• No action is required

FS094-I Password File Maintenance Utility.

• The Password File Maintenance Utility has been invoked using the parameters specified on the command line or in the Fileshare Server configuration file.

  If the Password File Maintenance Utility should not have been invoked, check the command line to ensure that the /pf option has been used correctly and that no other option specific to the Password File Maintenance Utility has been used. See the section Password File Maintenance in the chapter Security for more details.

• No action is required

FS096-I Password File installation has completed.

• The Password File Maintenance Utility has successfully updated the password file using the options specified when the Password File Maintenance Utility was invoked.

• No action is required

FS097-I Are you sure that you wish to close down the Fileshare Server ? (Y/N)

• You have used the Esc key sequence to close down the Fileshare Server. This message is an additional prompt to avoid closing down the Fileshare Server in error.

  The Fileshare Server does not accept input from Fileshare Clients whilst waiting for the response to this prompt. Consequently, you should respond quickly to this prompt.

• Responding Y to this prompt causes the Fileshare Server to start its termination processing. If there are any files open or users logged onto this Fileshare Server, an additional prompt and confirmation are displayed. When the Fileshare Server shuts down, it rolls back all outstanding transactions, closes all open files, logs off all users and closes down the communication support modules.

  If you give any reponse other than Y, the Fileshare Server continues operating as normal.

FS099-W File I/O status was not as expected. Returned status: status Expected status: status Action code: text File: filename.

• This error occurs when a file is being recovered using the Rollforward Recovery Utility. When the log file is written during the normal operation of the Fileshare Server, a record is made in the log file of the status of each I/O operation performed. At the time of recovery, the status returned during the recovery process is compared with that stored in the recovery log file.

  This message indicates that the status returned during the recovery process was not the same as that when the operation was performed during the normal Fileshare Server processing when the log file was written.

  The Returned status is the status that the Rollforward Recovery Utility encountered when trying to apply the updates from the recovery log file to the data files.

  The Expected Status is the status that was returned when this operation was originally performed by the Fileshare Server (and when the log file was being written).

  The Action code is the operation code that is being performed.

  The name of the file is included in the message.

  This error indicates one of the following:

  • The files to which the recovery log file is being applied are not the ones that were in use at the time that the Fileshare Server was started and the log file was created

  • The recovery log file or the files being rolled forward are corrupt

  • A situation has arisen which did not occur when the rollforward recovery file was created during normal Fileshare Server operation

• Note the expected and returned error codes and take appropriate action. Also ensure that the correct version of the data files are in place and try to re-run the rollforward recovery.

FS101-I text -- parameter has been accepted.

• The indicated parameter (and value if required) has been accepted by the Fileshare Server

• No action is required

FS103-I The log filename has been added to the database reference file.

• The Database Reference File Maintenance Utility has been invoked to add a recovery log filename to the database reference file and the operation has completed successfully. The database reference file now contains the name of the recovery log file specified.

• No action is required

FS104-I The log file cannot be found, creating a new recovery log file.

• The Fileshare Server on starting up has processed the database reference file and determined the name of the rollforward recovery log file to use. The recovery log file does not exist and so the Fileshare Server has created a new one.

• No action is required

FS105-W The disk free space for the log file is below acceptable limits.

• The Fileshare Server has detected that the amount of disk space remaining on the drive where the recovery log file is being written is below a certain level.

  The amount of disk space remaining is calculated as a percentage of the total size of the disk where the log file is being written. The default is for this warning to be displayed when less than 5 percent of the total disk space remains free. This percentage can be changed using the /p option when entering the log filename into the database reference file using the Database Reference File Maintenance Utility.

Note: If disk space is not cleared, the drive where the recovery log file is located will become so full as to make rollforward recovery logging impossible.

• Clear disk space on the drive where the recovery log file is being written so that the Fileshare Server can continue logging the updates being performed.

  Alternatively, if the amount of free disk space is becoming very low, the Fileshare Server should be shut down and the recovery log file backed up and deleted before starting the Fileshare Server again.

FS106-I filename - added to database reference file.

• This message indicates that the Database Reference File Maintenance Utility has successfully added the filename indicated to the database reference file.

• No action is required

FS107-I filename - removed from the database reference file.

• This message indicates that the Database Reference File Maintenance Utility has successfully removed the filename indicated from the database reference file.

• No action is required

FS108-I Processing the files specified in the database reference file.

• This message indicates that the Fileshare Server has opened the database reference file and is now scanning through it, processing each filename listed. The type of processing that it performs depends on the utility being used:
  • The Database Reference File Maintenance Utility searches through the list of files to check the integrity of each one and also determine the current sequence numbers that are in use (if any)

  • The Fileshare Server scans the names in the database reference file in order to determine the processing to be done on each file

  • The Rollforward Recovery Utility searches through the list of files to check the integrity of each file and the sequence number in the header of each one

• No action is required

FS109-W The file filename does not exist.

• You see this message when the filenames listed in the database reference file are being processed and indicates that the file indicated cannot be located physically on disk.

• If the file should exist, ensure that the filename and the path specified are correct and that the Fileshare Server is able to open the file with read-write access. Also ensure that the file is not open by another process as the Fileshare system requires exclusive access to the file.

  If the file should not exist (for example, it is expected that it will be created by an application program), then this warning can be ignored.

FS110-I filename - OK.

• The Fileshare system has successfully processed the entry indicated in the database reference file and the file has been physically located on disk.

• No action is required as this message is informational.

FS111-W Files are still open. Continue to close down the Fileshare Server (Y/N) ?

• You have selected to close down the Fileshare Server using the Esc key sequence. This message indicates that Fileshare Clients are still connected to this Fileshare Server with files open, or at least one Fileshare Client application program has terminated abnormally leaving one or more files open. You are asked to confirm that you do want to shut down the Fileshare Server even though there are files open.

• At the prompt enter Y or N depending on whether the Fileshare Server is to be closed down or not

FS114-W Waiting for the old log file to be removed.

• The drive where the rollforward recovery log file is being written has become full and the Fileshare Server is no longer able to continue writing to the rollforward recovery log file. The Fileshare Server is waiting for the old log file to be backed up and then deleted so that it can continue writing to the directory where the log file resides.

• The current log file should be backed up. The log file should then be moved so that the Fileshare Server can continue writing to the directory. If a rollforward recovery is necessary, the log files should be provided in the order that they were created to the Rollforward Recovery Utility. The Rollforward Recovery Utility will prompt for the continuation log files as they are required, if they cannot be located automatically.

FS118-I The database sequence number matches the sequence number in the log file, no recovery is needed.

• For files formats with file headers (all index files and variable length record relative and sequential files), the Fileshare Server stores a sequence number in the header. This sequence number is also placed in the recovery log file. The sequence numbers can be checked by the Fileshare Server in certain situations to ensure that the correct files are in use.

  You see this message when the Rollforward Recovery Utility has been invoked to perform a rollforward recovery. The Rollforward Recovery Utility has read the sequence numbers from the header of the files and also the last one that was written to the recovery log file. The sequence number in the headers and in the log file are the same indicating that the last updates written to the recovery log file have been applied to the files. It is therefore not necessary to perform a rollforward recovery as there are no updates in the recovery log file that have not already been applied to the files.

  It is not necessary to perform the rollforward recovery.

  See the sections Rollforward Recovery Logging and Rollforward Recovery Utility in the chapter Database Integrity for more details.

• No action is required

FS122-I Communications too busy on CCI SEND - retrying.

• The Fileshare Server tried to send a reply back to the Fileshare Client performing an I/O request. CCI returned a Too Busy error (error 10) to the Fileshare Server.

• The Fileshare Server will retry the operation until the CCI protocol has been able to complete the operation

• This message could indicate that the network or network software is reaching a limit or is very busy

• No action is required

FS123-I Communications too busy on CCI RECEIVE - retrying.

• The Fileshare Server tried to receive information from the network but CCI returned a Too Busy error (error 10) to the Fileshare Server

• The Fileshare Server will retry the request until valid data is returned from CCI

• This message could indicate that the network or network software is reaching a limit or is very busy

• No action is required

FS124-I Checking the validity of the log file, please wait.

• You see this message when the Rollforward Recovery Utility has been invoked and it has not found a valid record as the last record in the recovery log file. The Rollforward Recovery Utility scans through the log file to find the last sequence number that was in use to validate the integrity of the recovery log file.

  The fact that the log file does not contain a valid last record indicates that the recovery log file was not closed in a controlled manner and that the Fileshare Server which was writing to the recovery log file terminated abnormally.

  See the sections Rollforward Recovery Logging and Rollforward Recovery Utility in the chapter Database Integrity for more information.

• No action is required

FS125-I Recovery possible to last valid recovery log file record.

• You see this message when the Rollforward Recovery Utility has been invoked. This message indicates that the recovery log file has been validated up to the point of the last complete record in the recovery log file. It is therefore possible to apply the updates stored in the recovery log file up to this point.

  The Rollforward Recovery Utility will apply the updates up to the point of the last valid record stored in the recovery log file.

  See the sections Rollforward Recovery Logging and Rollforward Recovery Utility in the chapter Database Integrity for more information.

• No action is required

FS126-I Performing recovery, please wait.

• The Rollforward Recovery Utility has been invoked and has initialized successfully, processed the database reference file, checked the sequence numbers in the file listed in the database reference file and validated the recovery log file.

  The Rollforward Recovery Utility will now start the recovery process. The time required to perform the recovery depends on the number of updates that are logged in the recovery log file.

• No action is required

FS127-S Invalid name mapping command.

• You see this message when the Fileshare Server or Rollforward Recovery Utility is processing the command line or entries in the database reference file. An /fs (file string replacement) option has been specified without a corresponding /af option specifying the new string value. The /fs option must be used in conjunction with the /af option.

  See the section Filename Mapping in the chapter Advanced Operation and the section Database Reference File Maintenance in the chapter Database Integrity for more information on the /fs option.

• If the option has been specified on the command line, include the /af option to specify the name of the replacement string value and retry the operation.

  If the option is specified in a database reference file, this error indicates that the database reference file has become corrupt or has been changed without using the Database Reference File Maintenance Utility.

  In this situation, it may be possible to remove the invalid entry using a normal text editor. If this is unsuccessful, discard the current database reference file and create a new one using the Database Reference File Maintenance Utility.

FS128-W Fileshare Server closedown invoked by Stop Run processing.

• This message indicates that the Fileshare Server has entered its termination routine not under the control of an administrator (that is, the Esc key sequence or FSView or FSMgr are not being used to shut down the Fileshare Server).

  This message should not be displayed under normal circumstances. Possible causes for this error are:

  • A kill command on UNIX or closing the Fileshare Session on Windows. Such methods of closing the Fileshare Server should not be used as it can lead to files being corrupted and the recovery log file not being written to disk correctly.

  • The Fileshare Server has encountered an internal processing error which has caused the closedown code in the run-time system to be invoked. In this situation you should contact our technical support department to try and ascertain the cause of this error.

  The Fileshare Server terminates by closing all files, rolling back any outstanding transactions, clearing all communication links with Fileshare Clients and closing the recovery log file (if in use).

• You should try to ascertain why the Fileshare Server closed in this manner

FS129-I The Fileshare Server is still active.

• The response to the prompt as to whether the Fileshare Server should be closed down (see messages FS097 and FS111) indicated that the Fileshare Server should not be shut down.

  This message indicates that the Fileshare Server is continuing to function as normal.

• No action isrequired

FS130-I Reading database reference file, please wait.

• The Fileshare Server, Database File Maintenance Utility or the Rollforward Recovery Utility is reading the information stored in the database reference file. The utility will try to open the database reference file and process the information held in it.

  The amount of time required to process the database reference file depends on the amount of information contained in the file.

• No action is necessary

FS131-W Invalid communications mode - parameter ignored.

• You see this message when the Fileshare Server is processing a /cm (communications) option. The value specified for this parameter is not valid and the parameter has been ignored. See the chapters Communications and Configuration for details of valid communications modes.

• Ensure that the value specified for the communications parameter is valid.

  If you do not wish to specify a communications protocol you should not use the /cm option. The Fileshare Server uses the default communications protocol for the operating system on which it is running.

FS132-I The Fileshare Server is running with the following communication protocol(s):

• This message gives a list of the communication protocols that the Fileshare Server is using, after it has performed all of its initialization processing.

  The Fileshare Client application programs can use any of the protocols listed to contact this Fileshare Server.

• No action is required

FS133-I Processing the password file, please wait.

• You see this message displayed by the Fileshare Server when it is starting or by the Password File Maintenance Utility when the password file is being updated.

  The password file has been successfully located and opened and is now being processed.

  The time required for this operation depends on the amount of information that is stored in the password file.

• No action is required

FS134-I The password file cannot be found - creating a new password file.

• The Password File Maintenance Utility displays this message when it cannot locate the password file specified with the /pf option.

  The Password File Maintenance Utility will therefore try to create a new password file of the name specified.

• No action is required

FS135-I Fileshare Server security is active.

• Fileshare Server security is active and all Fileshare Client applications that try to access this Fileshare Server should supply a valid user-ID and password that are in the password file. If you do not provide a valid user-ID or password, access will be denied and a 9/037 error returned to the application.

  See the chapter Security for more details about the Fileshare Server security features and how to use them.

• No action is required

FS136-I Fileshare Server security is not active.

• A password file has been specified, however the only user-ID specified in the file is the FSVIEW (supervisor) id. Because this is the only ID, Fileshare Server security is not active and Fileshare Client applications that try to access the Fileshare Server do not have to supply a valid user-ID or password.

  Logons are validated by the Fileshare Server by calling the FSSECLOG module.

  See the chapter Security for more details about the Fileshare Server security features and how to use them.

  See the section Password File Maintenance in the chapter Security for more information about supervisor passwords.

• No action is required

FS138-W The log file has been backed up and a new one has been created.

• You see this message when the Fileshare Server is starting up and a recovery log file already exists. The Fileshare Server has determined that it is unable to append to the recovery log file because the last record in the log file indicates that it was not shut in a controlled manner.

  This implies that the Fileshare Server which was previously writing to this log file terminated abnormally.

  Because the Fileshare Server is unable to append to the existing log file, it has been renamed and a new recovery log file has been created. This new recovery log file will be used.

Note : This message implies that the correct sequence of regularly backing up data files and deleting recovery log files is not being performed as the Fileshare Server is being started when a recovery log file already exists.

See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

• No action is required

FS139-I A matching date and time entry has been found in the log file.

• The Rollforward Recovery Utility displays this message when the /dt option has been used to recover updates to a certain point in time. The Rollforward Recovery Utility has performed the recovery using the recovery log file and has applied the updates up to the date and time specified. This message implies that there were additional records stored in the recovery log file which were not processed as they were written after the time specified.

• No action is required

FS140-I No matching date and time entry has been found in the log file.

• You see this message displayed by the Rollforward Recovery Utility when the /dt option has been used to recover updates to a certain point in time. The Rollforward Recovery Utility has performed the recovery using the recovery log file and reached the end of the log file before a record could be found that was written at the date and time specified. This implies that the date and time specified when performing the recovery is later than the date and time that the last record was written to the recovery log file. All the updates stored in the recovery log file have been applied to the data files.

• No action is required

FS142-W The Operating System does not permit the log file to be flushed to disk.

• You see this message when the Fileshare Server is using a recovery log file to store updates made to files. At certain points during its operation the Fileshare Server makes a call to the operating system to force it to flush the contents of the recovery log file to disk. This ensures that any data that has been written to the recovery log file is physically stored on disk and can be read in again after a system failure. The Fileshare Server performs this flush operation after every COMMIT operation is performed and at regular intervals (the default being after every 100 records have been written to the recovery log file, which can be changed using a /lc entry in the database reference file).

  This message indicates that an error was returned from the operating system when it tried to flush the recovery log file to disk. This implies that the operating system does not enable application programs to force I/O buffers to be flushed to disk. Consequently, the Fileshare Server is unable to force the operating system to write the contents of the recovery log file to disk and in the event of a system failure, it is possible that not all of the contents of the recovery log file will be available when the recovery process is performed.

• See the section Database Reference File Maintenance in the chapter Database Integrity and Rollforward Recovery for more details

FS143-W The Operating System does not allow free disk space information to be obtained.

• When writing a recovery log file, it is important that there is enough disk space available. Consequently, the Fileshare Server makes periodic checks to see whether sufficient disk space remains.

  This message indicates that the call to the operating system to determine how much disk space is available has returned an error. This implies that the operating system does not enable applications to determine how much disk space is available.

• It is the system administrator's responsibility to ensure that sufficient disk space is available, as the Fileshare Server is unable to determine the amount of free space available on the drive. If the Fileshare Server is unable to write a recovery log file because there is insufficient disk space, the Fileshare Server automatically closes down.

FS144-W More than one communications protocol has been specified - synchronous communications mode not active.

• You have tried to start the Fileshare Server using the synchronous communications mode (as opposed to the asynchronous communications mode which is the default) using the /sc option.

  With this mode of communication it is only possible to start the Fileshare Server with one communications protocol.

  This message indicates that the Fileshare Server is configured to use more than one communications protocol and so the synchronous communications option has been ignored.

  The Fileshare Server has started, but it is not using the synchronous communications mode.

• If the synchronous communications mode is required, make sure that the Fileshare Server is configured to use only one communications protocol

FS145-W Fileshare Client disconnected, cannot contact user: text.

• The CCI has returned an error to the Fileshare Server indicating that a Fileshare Client has been disconnected. This message indicates that there may be a problem with the network or that the Fileshare Client application program is no longer functioning.

  You see the user number and user name, if one was supplied at the time that this user logged onto the Fileshare Server.

  The Fileshare Server has closed all files that this user had open and rolled back any outstanding transactions pending for this user.

  The Fileshare Client application, if still active, will be returned a 9/124 error on its next I/O operation.

• Check that the Fileshare Client application is still running. Also check for any adverse network conditions that could have forced the connection to have been dropped.

FS146-W Unexpected action code, action-code - discarded.

• You see this message when performing a rollforward recovery. The Rollforward Recovery Utility has read a record from the recovery log file which contains information not relating to any file currently being recovered. The information in the record cannot be processed and the Rollforward Recovery Utility has moved onto the next record in the recovery log file.

  This message can indicate that the recovery log file has become corrupted in some way or that the recovery file contains invalid information.

• As the rollforward recovery log file contains an invalid record, it is possible that not all of the record updates have been recovered from the file. After the recovery has completed the data in the files should be checked. If the problem recurs contact our technical support department.

FS147-I A duplicate network message was received and discarded.

• This message only occurs when you are using the CCIIPX protocol and indicates that you are using an old version of the CCIIPX modules. The buffer sent between the Fileshare Client and Fileshare Server for each I/O request contains additional information which enables the Fileshare Server to check on the validity of the request. This message indicates that the Fileshare Server has received (in error) a duplicate of the previous buffer received from the communications system. This duplicate buffer has been discarded as it is not a valid I/O request.

• Ensure that the latest CCIIPX modules are installed on the Fileshare Client and Fileshare Server machines

FS148-I CCI return-code (function func) = code.

• You see this message when the Fileshare Server receives an unexpected error status from a CCI module. It is normally displayed in conjunction with a Fileshare Server message indicating the circumstances in which the error occurred.

  The message consists of a function code which indicates which CCI verb was being used at the time of the error and the return-code received from the CCI module.

  The Fileshare Server calls CCI to determine details of the error that has occurred. This information is also displayed on the screen.

• No action is required. However, the above information should indicate the cause of an error or unexpected occurrence during the Fileshare Server operation. This information should be used with any additional information contained in other messages to determine the cause of any errors.

  When contacting our technical support department the above information is important and must be included with any problem report.

FS149-I CCI SEND not complete, status will be checked later.

• A request sent back to a client application from the Fileshare Server has not completed within the expected time period. This message indicates that the Fileshare Server will continue processing requests from other client applications normally and will check the status of this request at a later time.

  Message FS228 is displayed when it is determined that the request eventually either completed or failed.

  If you see this message frequently, it may be due to large record sizes taking longer to process than expected on slower network connections.

• No action is required

FS151-I CCI message size received = text. Indicated send message size = text.

• You see this message in conjunction with message FS014.

  The information sent from the Fileshare Client to the Fileshare Server includes a check on the amount of information that is being sent. This error states that the amount of data received by the Fileshare Server is not the same as the amount sent by the Fileshare Client.

  This message shows the amount of data that has been received by the Fileshare Server and also the amount of data that was sent by the Fileshare Client.

  The Fileshare Server has ignored the data sent from the Fileshare Client.

• If using the NETBIOS protocol, ensure that it is installed correctly, configured and operational.

  It is highly likely that the Fileshare Client appears to have stopped because the Fileshare Server has not sent any reply back. Depending on the CCI protocol being used, a time-out occurs in approximately two minutes and a 9/124 status is returned to the application program.

FS153-I The Fileshare Server name has been reregistered on the network.

• The Fileshare Server tried to register its name on the network so that Fileshare Clients can contact it. An error status was returned indicating that the Fileshare Server name was already registered on the network by a Fileshare Server which terminated abnormally. As this name is not being used by an active Fileshare Server, the name has been reregistered on the network by the Fileshare Server being started.

• No action is required

FS154-I Please enter the FSVIEW supervisor password to enable the use of CCI Trace.

• The Fileshare Server is being started and is configured to use the CCI Trace option. This option can only be used by a supervisor because it can cause a large amount of disk space to be used for storing the CCI Trace file. When starting the Fileshare Server a password file should be specified that contains a user-ID of FSVIEW.

  See the section Password File Maintenance in the chapter Security for more information.

  See also the messages FS155 and FS156.

• At this prompt enter the supervisor password that corresponds to the entry in the password file for the user-ID of FSVIEW

FS155-I Password accepted - CCI Trace is enabled. Do you want CCI Trace active immediately? (Y/N)

• You see this message displayed after the supervisor has entered the supervisor password to enable the use of CCI Trace. The Fileshare Server has confirmed that the password entered is correct and it is now possible to use CCI Trace.

  This prompt is to determine if the Fileshare Server is to trace communication requests immediately and include all of the CCI initialization requests made by the Fileshare Server.

• Responding Y enables the Fileshare Server to start using CCI Trace immediately and causes all CCI initialization requests to be traced to the CCI Trace file. The CCI Trace remains operational until toggled off using the F3 key.

  Entering any other response apart from Y does not enable CCI trace immediately. However, CCI trace can be toggled on at a later time using the F3 key.

  See also the messages FS154 and FS156.

FS156-W Incorrect password - CCI Trace is disabled.

• You see this message after the FSVIEW supervisor has entered the supervisor password to enable the use of CCI Trace.

  The Fileshare Server has determined that the password entered is incorrect and has consequently disabled the use of the CCI Trace feature.

• If CCI Trace is required then the Fileshare Server should be brought down using the Esc key sequence. Ensure that when starting the Fileshare Server the /pf option is used to specify a password file that contains a password for the user-ID FSVIEW. When prompted to enter the supervisor password the password for the FSVIEW user-ID should be entered.

  If CCI Trace is not required then no action is required as the Fileshare Server has started and the CCI Trace feature is not enabled. However, to prevent this message in future, the Fileshare Server should be reconfigured not to use CCI Trace.

FS158-I CCI Trace activated.

• This message indicates that the Fileshare Server has enabled the CCI Trace option and all requests made to CCI are being logged in the CCI Trace file.

  You see this message when either CCI Trace is made active on start-up, or is toggled on using the F3 key while the Fileshare Server is operational.

Note :The CCI Trace file can become very large. If no disk space remains to enable the CCI Trace file to be written, no errors are reported and the tracing of CCI requests is suspended.

• No action is required

FS159-I CCI Trace switched off.

• This message indicates that the Fileshare Server has turned off the CCI Trace option and all requests made to CCI are no longer being logged in the CCI Trace file. You see this message when the CCI Trace is either:
  • Not made active immediately on the Fileshare Server starting up (see the message FS155)

    or

  • Toggled off using the F3 key while the Fileshare Server is operational

• No action is required

FS160-I Fileshare trace activated.

• You see this message displayed by the Fileshare Server when the trace option has been activated using the F2 key. All requests received by the Fileshare Server will be shown, with the operation code being requested, the name of the user performing the request and some additional information depending on the operation being performed. The result of the operation (including the file status) that is returned to the Fileshare Client is also shown.

  If the trace to a file option was specified when the Fileshare Server was started then the information displayed on the screen is also written to a file called fsscreen.lst.

  The trace option can be toggled off using the F2 key.

  See also message FS161.

• No action is required

FS161-I Fileshare trace switched off.

• You see this message displayed by the Fileshare Server when the trace option has been toggled off using the F2 key. The Fileshare Server no longer displays requests received or information about the data being returned to the Fileshare Clients. The Fileshare Server also is no longer writing to the trace file fsscreen.lst if the trace file option was specified when the Fileshare Server was started.

  The trace option can be toggled on using the F2 key.

  See also message FS160.

• No action is required

FS163-I Input user opcode [filename-1] [ filename-2].

• You see this message when the Fileshare Server trace option is activated and a request has been received by the Fileshare Server. The information displayed is as follows:

  user	If the Fileshare Client supplied a user name when it logged onto this Fileshare Server then the user name is displayed here if Fileshare Security is active. If no user name was supplied, the user number is displayed. The user number is generated when the Fileshare Client logs onto this Fileshare Server. The first Fileshare Client has user-ID 1, the second user-ID 2, etc.
  opcode	This is an indication of the type of action requested by the Fileshare Client. Most normal operations appear as an action-code. If a byte stream operation is being performed, the name of the operation is displayed. For COMMIT operations, an indication is given if the COMMIT is part of a prepare, confirm or abort stage of the transaction processing (if the transaction spans more than one Fileshare Server).
  filename-1	If the operation being performed is specific to a file then the name of the file is displayed here
  filename-2	If the operation being performed is specific to a file and requests to the file are being mapped to a different file using the alternate filename mapping option, the actual name of the file being processed is displayed here

  The information displayed will also be written to a file called fsscreen.lst if the trace file option was specified when the Fileshare Server was started.

• No action is required

FS170-I Input- Logon.

• You see this message when the Fileshare Server trace option is activated and a logon request has been received by the Fileshare Server. The Fileshare Server will process the logon request and the result of the request will also be displayed. A logon request is always the first operation performed by a new Fileshare Client connecting to this Fileshare Server.

• No action is required

FS171-I Input- Logoff user.

• You see this message when the Fileshare Server trace option is activated and a log off request has been received by the Fileshare Server. If the Fileshare Client supplied a user name when it logged onto this Fileshare Server, the user name is displayed here if Fileshare Security is active. If no user name was supplied, then the user number is displayed.

  The user number is generated when the Fileshare Client logs onto this Fileshare Server. The first Fileshare Client has user-ID 1, the second user-ID 2.

  A logoff request is the last operation performed by a Fileshare Client when the Fileshare Client application program terminates.

• No action is required

FS172-I Input- Find File user filename.

• You see this message when the trace option is activated and a Find File request has been received by the Fileshare Server from a Fileshare Client when a program tries to open a file. The Fileshare Server that should process the file has not been explicitly defined and more than one default Fileshare Server is configured.

• The Fileshare Client is in the process of polling each default Fileshare Server to determine if that Fileshare Server should process requests for this file.

  The information displayed is as follows:

  user	If the Fileshare Client supplied a user name when it logged onto this Fileshare Server, the user name is displayed here if Fileshare Server security is active. If no user name was supplied, then the user number is displayed. The user number is generated when the Fileshare Client logs on to this Fileshare Server. The first Fileshare Client has user-ID 1, the second user-ID 2.
  filename	The name of the file that the Fileshare Client is trying to open

• No action is required

FS173-I Output- user status.

• You see this message when the Fileshare Server trace option is activated and a request has been processed by the Fileshare Server and the result sent back to the Fileshare Client

• The information displayed is as follows:

  user

  If the Fileshare Client supplied a user name when it logged onto this Fileshare Server then the user name is displayed here. If no user name was supplied, the user number is displayed. The user number is generated when the Fileshare Client logs onto this Fileshare Server. The first Fileshare Client has user-ID 1, the second user-ID 2.

  status

  The error status generated from the result of the requested operation. For normal file I/O operations this is the same format as standard file I/O statuses. Note that this status may not be the status that is returned to the application program. The Fileshare Client uses the status displayed here to do any status conversion necessary (for example, to an RM COBOL status) before returning the status to the application program.

For byte-stream I/O calls and other functions, the code returned to the Fileshare Client is displayed.

• No action is required

FS176-W There is no backup directory specified in the database reference file.

• You tried to erase a backup directory entry from the database reference file but the database reference file does not contain a backup directory entry

• No action is necessary (as the erase operation is not required because there is no backup directory name specified in the database reference file)

FS177-S The backup directory specified cannot be found in the database reference file.

• You tried unsuccessfully to erase a backup directory-name from the database reference file. This is because the backup directory-name specified is not the same as the backup directory-name in the database reference file.

• Specify the correct backup directory-name when trying to erase the entry from the database reference file. If the name specified in the database reference file is not known then the current database reference file should be discarded and a new one created using the Database Reference File Maintenance Utility.

FS178-I The backup directory has been added to the database reference file.

• The Database Reference File Maintenance Utility has been invoked to add a backup directory-name to the database reference file and the operation has completed successfully. The database reference file now contains the name of the backup directory specified.

• No action is required

FS179-S A backup directory is already specified in the database reference file.

• You tried to add the name of the backup directory to the database reference file. However such an entry already exists in the database reference file which can only contain one recovery log file backup directory-name.

• Remove the current backup directory-name from the database reference file using the Database Reference File Maintenance Utility (/e erase option) and then add the name of the new backup directory using the same utility

FS180-W The log filename specified has an extension. The name of the log file has been changed to "filename".

• The Database Reference File Maintenance Utility has been invoked to add the name of the recovery log file to the database reference file. The name of the log file specified contained an extension and this has been removed. The extension is removed to enable the Fileshare Server to automatically backup the recovery log file when necessary. The name of the log file added to the database reference file is shown.

• No action is required (as the Fileshare Server has removed the extension and added the altered name to the database reference file). To avoid this message in the future, do not use a filename with an extension when adding a recovery log filename to the database reference file.

FS182-W Output- Access Denied

• You see this message when the Fileshare Server trace option is activated and a logon request was received by the Fileshare Server from the Fileshare Client. This logon request has been denied, either because:
  • Password security is active and an incorrect password or user-ID was supplied

    or

  • Password security is not active and the logon validation by the module FSSECLOG failed

• If the password file security option is:
  • Active, ensure that the application program has supplied a valid user-ID and password to the Fileshare Client. Also ensure that the user-ID and password are in the password file that was specified when the Fileshare Server was started.

  • Inactive, the logon has been denied by the FSSECLOG module. This module supplied with the Fileshare Server enables any Fileshare Client to log on to the Fileshare Server. This therefore suggests that the logon has been denied by a user-supplied FSSECLOG module and the appropriate action should be taken.

  See the chapter Security for more information.

FS188-W Fileshare Server database reference file installation completed with errors.

• The Database Reference File Maintenance Utility has been used to update the contents of the database reference file. However, an error was found when parsing the command line passed to the utility or when processing the information stored in the database reference file.

  The database reference file has been left unaltered as the operation was unsuccessful.

• Ensure that the command line specified for the Database Reference File Maintenance Utility is correct. Other messages displayed by the Database Reference File Maintenance Utility indicate which error has occurred.

  For information on valid parameters, see the section Database Reference File Maintenance in the chapter Database Integrity .

FS189-W The backup directory does not exist.

• The Database Reference File Maintenance Utility has been invoked to add the name of a backup directory to the database reference file.

  This message indicates that the directory specified does not exist.

  The backup directory-name has been added to the database reference file.

• Check that the directory-name and path specified are correct. If they are not correct, the entry should be removed from the database reference file (using the /e (erase) option and the Database Reference File Maintenance Utility) and the correct entry added to the database reference file using the same utility.

  If the path and directory-name are correct, ensure that the directory is created or made available to the Fileshare Server before starting the Fileshare Server, so that the automatic backup can take place. If the directory does not exist, the Fileshare Server fails when trying to back up the recovery log file or the data files automatically when required to do so.

FS190-W The backup directory specifies the name of an existing file.

• The Database Reference File Maintenance Utility has been invoked to add the name of a backup directory to the database reference file.

  This message indicates that the directory specified is the name of a file and not the name of a directory.

  The backup directory-name has been added to the database reference file.

• Check that the directory-name and path specified are correct. If they are not correct, the entry should be removed from the database reference file (using the /e (erase) option and the Database Reference File Maintenance Utility) and the correct entry added to the database reference file using the same utility.

  If the path and directory-name are correct then before starting the Fileshare Server, ensure that a directory of the name specified is created or made available to the Fileshare Server so that the automatic backup can take place. The file of this name should be removed.

  If the directory does not exist, the Fileshare Server fails when trying to back up the data files or the recovery log file automatically when required to do so.

FS191-W An error occurred accessing the backup directory.

• The Database Reference File Maintenance Utility has been invoked to add the name of a backup directory to the database reference file.

  This message indicates that the Database Reference File Maintenance Utility received an unexpected error when verifying that the directory exists.

  See also messages FS189-W and FS190-W.

  The backup directory-name has been added to the database reference file.

• Check that the directory-name and path specified are correct. If they are not correct, the entry should be removed from the database reference file (using the /e (erase) option and the Database Reference File Maintenance Utility) and the correct entry added to the database reference file using the same utility.

  If the path and directory-name are correct, ensure that a directory of the name specified is created or made available to the Fileshare Server before starting the Fileshare Server, so that the automatic backup can take place.

  If the directory does not exist or cannot be accessed, the Fileshare Server fails when trying to back up the data files or the recovery log file automatically when required to do so.

FS192-S More than one log file exists in the log file directory.

• You see this message when the Fileshare Server is starting up. The Fileshare Server has searched the directory where the recovery log file is to be written and has determined that more than one recovery log file exists in the directory. The Fileshare Server is unable to determine which of these recovery log files is a valid one and hence which one it can append data to.

  Recovery log files have an extension which start with L. This message indicates that the correct procedures for backing up data files and deleting recovery log files are not being followed.

  The Fileshare Server will not start up until this problem is resolved.

• Ensure that the correct recovery log file is in the directory where the log file is to be written. Alternatively ensure that the directory does not contain any recovery log file so that the Fileshare Server creates a new one when it starts up.

  Make sure that the correct procedures for using rollforward recovery logging are used. See the sections Rollforward Recovery Logging and Rollforward Recovery Utility in the chapter Database Integrity.

FS193-S Unable to open the log file.

• The Fileshare Server has determined that a recovery log file exists in the directory where the recovery log file is specified but an error was returned when the Fileshare Server tried to open it.

  This error indicates that the Fileshare Server does not have the correct permissions to access the file or that the recovery log file is in use by another process. The Fileshare Server requires read and write access to the recovery log file and will try to open the file with exclusive access.

  This message can occur:

  • When the Fileshare Server is starting up, in which case the Fileshare Server will not start and the problem should be corrected before the Fileshare Server is started again

  • When the Fileshare Server is in the process of backing up the recovery log file. The backup of the log file failed and the Fileshare Server has tried to use the original recovery log file. However, the opening of the recovery log file failed. In this situation, the logging of updates is suspended.

• Ensure that the Fileshare Server has read and write access permissions to the recovery log file and that the file is not in use by another process

FS194-I The log file "filename-1" has been backed up successfully to "filename-2".

• This message indicates that the Fileshare Server has successfully backed up the recovery log file. The backup operation was performed either as a request from FSVIEW or FSMGR or because the current recovery log file cannot be appended to and has been automatically backed up when the Fileshare Server has started. filename-1 is the name of the log file that has been backed up. filename-2 is the name of the file that the log file has been backed up to.

  If a recovery log file backup directory has been specified, then the backed-up recovery log file is in the backup directory.

  If the log file was backed up when the Fileshare Server started, this indicates that the old recovery log file was not closed in a controlled manner. Not all of the updates in the old log file can be applied to the data files if a rollforward recovery becomes necessary. You are advised to close down the Fileshare Server and perform a rollforward recovery with the old recovery log file to restore the data files to a consistent state. The recovery log file should then be discarded and a new one will be created when the Fileshare Server is restarted.

• No action is required

FS195-I The Fileshare Server is using the log file "filename".

• The Fileshare Server has successfully opened (and created if necessary) the recovery log file indicated and is writing recovery records to this log file.

• No action is required

FS196-W Unable to create the log file "filename".

• The Fileshare Server tried to create the recovery log file indicated, but was unable to do so.

  The Fileshare Server was unable to create the new recovery log file after backing up the one that was in use. As the Fileshare Server is already operational, it does not close down. The Fileshare Server tries to re-open the old recovery log file and tries to continue writing recovery records to it. This message indicates that overall, the backing up of the recovery log file failed. The Fileshare Server is still operational.

• Ensure that the log filename contains a valid directory and filename. The Fileshare Server requires read-write access to the log file and permissions to create the file if necessary. Ensure that, if the file of this name already exists, it is not being used by another process.

FS197-S Unable to create the log file "filename".

• The Fileshare Server tried to create the recovery log file indicated, but was unable to do so.

  The Fileshare Server was unable to create the recovery log file when it was starting up and so will not start. The problem should be rectified before trying to start the Fileshare Server again.

• Ensure that the log filename contains a valid directory and filename. The Fileshare Server requires read-write access to the log file and permissions to create the file if necessary. Ensure that, if the file of this name already exists, it is not being used by another process.

FS198-W The attempt to backup the log file failed because the backup file "filename" already exists.

• The Fileshare Server was unable to backup the recovery log file to the directory and name specified because a file of that name already exists.

  The Fileshare Server was unable to backup the log file that is currently in use. As the Fileshare Server is already operational, it cannot close down. The Fileshare Server tries to re-open the old recovery log file and tries to continue writing recovery records to it. This message indicates that overall, the backing up of the recovery log file failed. The Fileshare Server is still operational.

• Remove the filename indicated so that the recovery log file can be automatically backed up.

  This message can indicate that the correct sequence of backing up data files and removing recovery log files is not being followed.

  See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

FS199-S The attempt to backup the log file failed because the backup file "filename" already exists.

• The Fileshare Server was unable to backup the recovery log file to the directory and name specified because a file of that name already exists.

  The Fileshare Server was unable to back up the log file to which it cannot append. The Fileshare Server is unable to append to the current recovery log file and is also unable to back it up and will therefore not start. The problem should be rectified before trying to start the Fileshare Server again.

• Remove the filename indicated so that the recovery log file can be automatically backed up.

  This message can indicate that you are not following the correct sequence of backing up data files and removing recovery log files.

  See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

FS200-W The attempt to backup the log file to "filename" failed.

• The Fileshare Server tried to copy the recovery log file to the directory and name specified but encountered an error when doing so. Possible causes are that the directory is full or that a disk I/O error occurred during the copying process.

  The Fileshare Server was unable to back up the log file that is currently in use. As the Fileshare Server is already operational, it cannot close down. The Fileshare Server will try to re-open the old recovery log file and continue to write recovery records to that. This message indicates that overall, the backing up of the recovery log file failed. The Fileshare Server is still operational.

• Ensure that the filename and directory of the backup file are correct. Also ensure that there is enough disk space in the backup directory for the recovery log file to be copied.

  If you are trying to start the Fileshare Server, this message can indicate that you are not following the correct sequence of backing up data files and removing recovery log files. See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

FS201-S The attempt to backup the log file to "filename" failed.

• The Fileshare Server failed to copy the recovery log file to the directory and name specified. Possible causes are that the directory is full or that a disk I/O error occurred during the copying process.

  The Fileshare Server is unable to append to the current recovery log file and is also unable to back it up and so will not start. You should rectify the problem before trying to re-start the Fileshare Server.

• Ensure that the filename and directory of the backup file are correct. Also ensure that there is enough disk space in the backup directory for the recovery log file to be copied.

  If you are trying to start the Fileshare Server, this message can indicate that you are not following the correct sequence of backing up data files and removing recovery log files. See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

FS202-I The Fileshare Server will continue logging to the log file "filename".

• The Fileshare Server failed to backup the recovery log file as part of an FSView or FSMgr operation and is trying to continue logging to the old recovery log file specified

• No action is required

FS203-I The Fileshare Server is appending to the log file "filename".

• The Fileshare Server has found a valid recovery log file to which it is able to append data.

  This message indicates that you are not following the recommended sequence of backing up data and removing recovery log files. A recovery log file already existed when the Fileshare Server started.

  See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

• No action is required

FS204-W The Fileshare Server is unable to log to the log file "filename". Rollforward recovery logging is disabled.

• The Fileshare Server has failed to back up the recovery log file as part of an FSView or FSMgr operation. Consequently, the Fileshare Server does not have a valid recovery log file into which it can write records.

  Rollforward recovery logging has been suspended.

• Terminate the Fileshare Client applications and shut down the Fileshare Server. Then back up the data files, remove the recovery log file and restart the Fileshare Server to create a new recovery log file.

FS205-W Unable to remove the old recovery log file "filename".

• The Fileshare Server has successfully backed-up the recovery log file as part of an FSView or FSMgr operation. However, deleting the old recovery log file returned an unexpected error. The Fileshare Server tries to create the new recovery log file.

• Ensure that the Fileshare Server has the correct permissions to enable it to delete the old recovery log file. Remove the old recovery log file manually if the backup operation has succeeded. This releases more disk space for recovery logging to take place.

FS206-S There is more than one starter log file. The Recovery Utility is unable to determine which one to use.

• You see this message when the Rollforward Recovery Utility has determined that there is more than one starter recovery log file. When the Fileshare Server starts, it creates a starter recovery log file and a new log file.

  Thus, if the Fileshare Server:

  • Starts and there is no recovery log file available, it creates one

  • Automatically backs up the recovery log file, it backs up the starter recovery log file and creates a continuation recovery log file

  • Performs another back up, it backs up the continuation recovery log file and creates another continuation recovery log file

  A rollforward recovery can only proceed when there is only one starter recovery log file to use.

• Ensure that the correct recovery log files are in place and then try to re-run the rollforward recovery process.

  This message indicates that you are not following the correct sequence of backing up data files and removing recovery log files. See the section Rollforward Recovery Logging in the chapter Database Integrity for more details.

FS207-I There is no starter log file in the log file directory.

• The Rollforward Recovery Utility has been invoked and has scanned all of the recovery log files in the current directory. It has not found a starter log file, so the recovery cannot start using a log file in the recovery log file directory.

  The Fileshare Server now searches for a starter recovery log file that has been backed up to the recovery log file backup directory.

• If no starter recovery log file is found in the recovery log file backup directory, it is not possible for the rollforward recovery to be performed. Place the correct starter recovery log file in the recovery log file directory and try to re-run the rollforward recovery.

FS208-S There is no starter log file in the backup directory.

• The Rollforward Recovery Utility has been invoked and has scanned all of the recovery log files in the backup directory. No starter log file was found and so the recovery cannot commence.

• Place the correct starter recovery log file in the recovery log file directory and invoke the Rollforward Recovery Utility again to perform rollforward recovery

FS209-I A starter log file has been located in the backup directory.

• The Rollforward Recovery Utility has not found a starter log file in the recovery log file folder, but one was located in the backup folder. The Rollforward Recovery Utility can start the rollforward recovery.

• No action is required

FS210-S There is more than one starter log file in the backup directory.

• The Rollforward Recovery Utility has scanned through all of the recovery log files that are in the backup directory and has determined that there is more than one starter recovery log file.

  A rollforward recovery can only start when there is only one starter recovery log file to use.

  See the section Rollforward Recovery Logging in the chapter Database Integrity for more information.

• Ensure that the correct recovery log files are in place and then re-try the rollforward recovery process.

  This message indicates that you are not following the recommended sequence of backing up data files and removing recovery log files.

FS211-S An error occurred checking the header on the log file "filename".

• The Rollforward Recovery Utility found the log file indicated but was unable to open it. This message can also indicate that the file was opened successfully but the Rollforward Recovery Utility could not read the first record in the file.

• Ensure that the Rollforward Recovery Utility has read and write access to the file indicated. Also ensure that the utility is able to open the file exclusively and that it is not currently in use by another process.

FS212-I The Rollforward Recovery Utility is processing the log file "filename".

• The Rollforward Recovery Utility has successfully opened the starter or continuation recovery log file indicated and is processing the update information contained in it

• No action is required

FS213-W Unable to locate the continuation log file "filename" in the log file directory.

• The Rollforward Recovery Utility has processed the first recovery log file.

  The marker at the end of the recovery log file indicates that there is an additional recovery log file to be processed. This message indicates that the Rollforward Recovery Utility cannot find the next recovery log file in the same directory as the previous recovery log file.

  The Rollforward Recovery Utility tries to find the next recovery log file in the backup directory if one has been specified.

• No action is required

FS214-I Searching for a backed up log file in the log file directory.

• The Rollforward Recovery Utility cannot find the required recovery log file in the current log file directory. It is now searching for a backed-up copy of the required recovery log file in the log file directory.

• No action is required

FS215-I Searching for a backed up log file in the backup directory.

• The Rollforward Recovery Utility cannot find the required recovery log file in the current log file directory. It is now searching for a backed-up copy of the required recovery log file in the backup directory

• No action is required

FS216-I No backed up starter log file can be found in the log file directory.

• The Rollforward Recovery Utility has searched unsuccessfully for a backed-up starter recovery log file in the log file current directory

• No action is required

FS217-I No backed up starter log file can be found in the backup directory.

• The Rollforward Recovery Utility has searched unsuccessfully for a backed-up starter recovery log file in the backup directory

• No action is required

FS218-I No backed up continuation log file can be found in the log file directory.

• The Rollforward Recovery Utility has searched unsuccessfully for a backed-up continuation recovery log file in the current log file directory

• No action is required

FS219-I No backed up continuation log file can be found in the backup directory.

• The Rollforward Recovery Utility has searched unsuccessfully for a backed-up continuation recovery log file in the backup folder

• No action is required

FS220-I A backed up starter log file has been found in the log file directory.

• The Rollforward Recovery Utility has found a backed-up starter log file in the current log file recovery directory.

  The Rollforward Recovery Utility will open and try to process the recovery log file that it has located.

• No action is required

FS221-I A backed up starter log file has been found in the backup directory.

• The Rollforward Recovery Utility has found a backed-up starter log file in the backup directory.

  The Rollforward Recovery Utility will open and try to process the recovery log file which it has located

• No action is required

FS222-I A backed up continuation log file has been found in the log file directory.

• The Rollforward Recovery Utility has found a backed-up continuation log file in the current recovery log file directory.

  The Rollforward Recovery Utility will open and try to process the recovery log file which it has located.

• No action is required

FS223-I A backed up continuation log file has been found in the backup directory.

• The Rollforward Recovery Utility has found a backed-up continuation log file in the backup directory.

  The Rollforward Recovery Utility will open and try to process the recovery log file which it has located.

• No action is required

FS224-S The log file directory contains more than one backed up starter log file.

• The current log file directory contains more than one backed-up starter log file and so the Rollforward Recovery Utility is unable to determine which one is the correct one to use.

  It is not possible to start the rollforward recovery process.

  This message indicates that you have not followed the recommended sequence of backing up data files and removing unneeded recovery log files. See the section Rollforward Recovery Logging in the chapter Database Integrity for more information.

• Ensure that only the correct backed-up starter recovery log file is in the log file directory. Then re-start the rollforward recovery process.

FS225-S The backup directory contains more than one backed up starter log file.

• The Rollforward Recovery Utility has searched the backup directory for a backed-up starter log file. The backup directory contains more than one backed-up starter log file and so cannot determine which one is the correct one to use.

  It is not possible to start the rollforward recovery process.

  This message indicates that you are not following the correct sequence of backing up data files and removing unneeded recovery log file. See the section Rollforward Recovery Logging in the chapter Database Integrity for more information.

• Ensure that only the correct backed-up starter recovery log file is in the backup directory. Then re-start the rollforward recovery process.

FS227-W Failure to set Fileshare Server's access rights.

• You only see this message displayed by the Fileshare NLM.

  The Fileshare NLM encountered an error when trying to set the Fileshare Server's access rights on the NetWare operating system.

  This operation is performed after an I/O operation has been carried out for a Fileshare Client. Because this operation has failed, the Fileshare Server has assumed the access rights of that Fileshare Client.

  This message indicates that the Fileshare Server's connection to the NetWare operating system is no longer valid. The Fileshare Server will try to connect with supervisor access rights to the NetWare operating system.

• If this error persists you should contact our technical support department

FS228-I CCI SEND status checked.

• A request sent back from the Fileshare Server to a client application, which previously had not completed within the expected time period, has now either failed or completed successfully.

  See also the message FS149.

  A second message following this one indicates the outcome of the request in question. If this suggests frequent communications errors, there may be errors on the network or client applications may be terminating abnormally. The request completed normally if no message follows.

• No action is required

FS229-I Unrecognized CCI session ID - could not disconnect user.

• The Fileshare Server tried to disconnect a Fileshare Client. However, the CCI session ID is invalid which means that the Fileshare Server cannot find details of this Fileshare Client.

  A possible cause of this error is that CCI indicated that a Fileshare Client application program terminated abnormally, but the Fileshare Server is unable to locate details about the Fileshare Client which has terminated.

• No action is required

FS230-I User : user-ID user-name

• You see this message when the Fileshare Server has received an error from a CCI module following a communications request. The error message indicates a problem has occurred in contacting a specific Fileshare Client.

  This message provides information regarding the user-ID and the user-name (if available) of the Fileshare Client that the Fileshare Server tried to contact.

• No action is required.

  Use details contained in other messages displayed by the Fileshare Server to determine the cause of the error.

FS231-S The parameter "nnn" is not numeric.

• You see this message when the Fileshare Server is parsing the information supplied on the command line or in the Fileshare Server configuration file. The option specified requires a value which is numeric, however the value specified is not numeric and so that parameter cannot be processed.

• Correct the Fileshare Server command line option or the Fileshare Server configuration file entry so that the value for the parameter indicated is numeric. Then try to re-start the Fileshare Server with the new command line or configuration file.

FS232-I Date : date.

• This information is written to a Fileshare Server trace file (if one is in use) when the Fileshare Server starts up. It is also written to the Fileshare Server trace file when the date of the previous message written to the trace file is different to the current date and a new message is being written to the trace file.

• No action is required

FS233-W Unable to set the maximum amount of dynamic memory to the limit specified.

• This message is only displayed by the Fileshare NLM.

  This message indicates that the Fileshare NLM is configured to use a maximum amount of dynamically-allocated memory (using the /mm option).

  The Fileshare Server was unable to set the limit of the amount of dynamically-allocated memory and therefore tries to allocate memory as required, with no upper limit.

• The message indicates an internal Fileshare NLM failure. Please contact our technical support department.

FS234-W The parameter "text " specifies a memory limit below the minimum of 6 Mbytes allowed.

• This message is only displayed by the Fileshare NLM.

  This message indicates that the Fileshare NLM is configured to use a maximum amount of dynamically-allocated memory (using the /mm option).

  However, the amount of memory that it is configured to use is below the minimum of 6 Mbytes in which the Fileshare NLM can successfully operate. The Fileshare NLM has set the amount of dynamically-allocated memory it can use up to six megabytes.

• Specify a different value for the /mm option so that the amount of dynamically-allocated memory that it can use is at least six megabytes

FS235-W Failure to allocate memory for incomplete CCI SEND processing.

• The Fileshare Server has tried to allocate some memory in order to process CCI requests to multiple Fileshare Client sessions simultaneously, but there is insufficient free memory available. Consequently, the Fileshare Server may not be able to process communications requests correctly.

  Making more memory available to the Fileshare Server session after this message has been displayed will not rectify the problem with this particular request, although it might enable the Fileshare Server to allocate memory if it needs to in the future. However, the Fileshare Server process is near the limit of memory available to it which could adversely affect its operation.

  See also the message FS149.

• Make more memory available by closing other active applications on the machine where the Fileshare Server is running in order to avoid Fileshare Server memory problems in general

FS236-I The log file name has been removed from the database reference file.

• This message indicates that the Database Reference File Maintenance Utility has successfully removed the log file name from the database reference file

• No action is required

FS237-S The next log file to use filename already exists, unable to back up current log file.

• The Fileshare Server was unable to create the recovery log file because a file of the same name already exists

• The Fileshare Server has not started. Ensure that no file already exists with the same name as that which the Fileshare Server is trying to use for the next recovery log file. Then re-start the Fileshare Server.

FS237-W The next log file to use filename already exists, unable to back up current log file.

• The Fileshare Server has tried to back up the current log file but was unable to create a new recovery log file because a file of that name already exists. The Fileshare Server will try to re-open the old log file and continue to write records to it.

• The Fileshare Server continues to run but the back up of the recovery log file has failed. Ensure that no file already exists with the same name as that which the Fileshare Server is trying to use for the next recovery log file

FS238-I Terminating communications with this user.

• You see this message, together with FS015-W, when the network connection with an unknown Fileshare Client terminates

• No action is required

FS239-I Output - user Record locked. Retry operation.

• You see this message when tracing is enabled and an I/O operation returns a status of record locked. The user application making the request is compiled with the RETRYLOCK directive which specifies that the request is automatically retried when a status of record locked is returned. The Fileshare Server sends this message to the Fileshare Client requesting that it retries the operation.

• No action is required

FS240-I Output - user File locked. Retry operation.

• You see this message when tracing is enabled and an I/O operation returns a status of file locked. The user application making the request has the Callable File Handler RETRYOPEN option set which specifies that the open request is automatically retried when a status of file locked is returned. The Fileshare Server sends this message to the Fileshare Client requesting that it retries the operation.

• No action is required

FS241-I Output - user Insufficient log file disk space. Retry operation.

• You see this message when tracing is enabled and the amount of free disk space available to the Fileshare Server to log updates in the log file is below 200 Kbytes. See the messages FS030-S and FS114-W for further information.

• Because the Fileshare Server can no longer guarantee that it can store updates in the log file, it has suspended operations and is waiting for the log file to be removed in order to create more disk space. While operations are suspended any requests from Fileshare Clients are rejected. Refer to messages FS030-S and FS114-W

FS242-W Error reading message from message file.

• All of the text for messages displayed by the Fileshare Server is stored in an external file. By default, this file is included in the mflangxx.lbr libraries in the cobdir directory. You see this message when the Fileshare Server has tried to output a message but cannot access these libraries. The Fileshare Server is unable to display any warnings or serious errors.

• Ensure that the COBDIR environment variable is set and that the mflangxx.lbr files are present in the indicated directory (or a sub-directory)

FS243-S Failure backing up the file filename1 to filename2.

• During an automatic backup of the data files, an error has occurred while copying the file specified by filename1 to the destination specified by filename2

• Ensure that no other process is currently accessing either filename1 or filename2 and that the Fileshare Server has sufficient access permissions to carry out this operation

FS244-S Failure restoring the backed up file filename1 to filename2.

• An error has occurred while copying the file specified by filename1 to the destination specified by filename2 during an automatic restoration of the data files before running the Recovery Utility

• Ensure that no other process is currently accessing either filename1 or filename2 and that the Fileshare Server has sufficient access permissions to carry out this operation. Then re-start the Recovery Utility. If this was invoked automatically during the Fileshare Server start-up, you also need to re-start the server manually once the recovery has completed successfully.

FS245-S Failure deleting the log file filename.

• A failure occurred when Fileshare tried to delete the redundant log file, filename

• Ensure that no other process is accessing the file and that the Fileshare Server has sufficient permissions to delete the log file. Fileshare cannot start up and log updates to the correct log file until the redundant log file is deleted. Once the problem is rectified you need to restart the Fileshare Server.

FS246-I Backing up database files to directory backup directory. Please wait.

• The data files listed in the database reference file are being copied to the directory specified by the /backup option

• No action is required

FS247-I Restoring database files from directory backup directory. Please wait.

• The data files listed in the database reference file are being copied from the directory specified by the /backup option to their correct locations in preparation for a Fileshare Recovery

• No action is required

FS248-I Commencing automatic Fileshare Recovery.

• This message indicates that the Fileshare Recovery Utility has been automatically invoked because the Fileshare Server has detected that the previous server session did not close down successfully

• No action is required

FS249-I Restarting Fileshare Server.

• This message indicates that the automatic Fileshare Recovery has completed successfully and that the Fileshare Server is restarting

• No action is required

FS250-I Deleting all unwanted log files.

• This message indicates that Fileshare is deleting redundant log files before re-starting the Fileshare Server when a new log file is created

• No action is required

FS251-S Logging must be activated for all files when specifying a backup directory.

• You have specified that update logging is to be switched off for one of the files named in the database reference file but have also specified a backup directory-name. You cannot do this because Fileshare automatically backs up (and restores where necessary) all the files listed in the database reference file, in order to keep them synchronized with the log file, when a backup directory is specified. If logging is not active for all files, Fileshare cannot guarantee that it can restore and recover the correct versions of these files.

• If you are adding the name of a data file to the database reference file, you must add it without specifying the /o l option

• If you are adding a backup directory-name using the /backup option, you should first remove any database reference file entries for files which have logging switched off

FS252-S Failure deleting the file filename.

• An error occurred while deleting the file filename during an automatic backup or restoration of the data files

• Ensure that no other process is accessing the file and that the Fileshare Server has sufficient permissions to delete it. You will then need to re-start the Fileshare Server or the Fileshare Recovery Utility (depending on which you were trying when the error occured).

Copyright © 2001 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.