| Fileshare Tutorial |
| Fileshare on Novell NetWare | |
There are three levels of messages that can be produced by the Fileshare
Server. These are of varying levels of severity; Severe, Warning or
Informational. 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 level messages indicate that a situation
was encountered that the Fileshare Server was not expecting, but was able
to continue and carry out the operation. Informational level messages
provide information about the operation that the Fileshare Server is
performing.
The format of each message is as follows:-
FSxxx-y text |
the message text giving a description of the message
the severity of the message ("S", "W" or "I")
the message number
the characters "FS" indicating that this is a Fileshare
Server message |
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 Fileshare Server
Configuration, Database Reference File Maintenance, Rollforward
Recovery Utility and Password File Maintenance in the
chapter Fileshare.
FS004-S The parameter "text " specifies a
time-out value that is invalid.
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
allowed for this parameter.
- Retry the operation ensuring that only one occurrence of the
parameter exists.
FS007-S Invalid parameter combination.
FS008-S Communications Initialization Failure.
- An error has occurred when the Fileshare Server initialised CCI or
the Fileshare Server was unable to perform the CCI call due to the
required Operating System and/or Micro Focus communication support
modules not being 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
intialized.
- 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 attempted 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 attempting the start the Fileshare Server again.
See your Programmer's Guide to Communications for
details on the Common Communications Interface.
FS011-W Communications send failure.
FS012-W Communications disconnect failure.
- The Fileshare Server attempted to drop the connection with the
Fileshare Client, but the communications system returned an error. The
Fileshare Server will attempt to disconnect from Fileshare Clients under
the following circumstances:
- If the CCITCP protocol is being used and a request is received
from an unknown Fileshare Client
- The CCI protocol indicated that the Fileshare Client application
has 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
application correctly, and not turning the workstation machines off or
using utilities to terminate the Fileshare application abnormally (for
example kill on UNIX).
FS013-W Communications receive error.
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 under normal circumstances and implies
that there is a problem with the communications system.
This error can also occur if the netbios protocol is being used but
the requester service has not been started.
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 any reply back.
Depending upon the CCI protocol being used, a timeout 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 so that a valid option is used.
FS017-S Unable to open the file : filename.
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 due to a system crash. The Recovery Utility
has 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 which implies that the log
file has become corrupt.
This error can occur 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.
FS021-S There is no log filename specified in the database
reference file.
- An attempt to erase a log file entry from the database reference file
was made but no log filename is specified in the database reference
file. The operation therefore cannot be completed successfully.
- No action is necessary as the erase operation is not required as no
log filename is specified in the database reference file.
FS022-S The log filename given cannot be found in the
database reference file.
- An attempt to erase a log file entry from the database reference file
was unsuccessful because the log filename specified is not the same as
the log filename in the database reference file. The operation therefore
cannot be completed successfully.
- Specify the correct name of the log file when attempting to erase the
entry from the database reference file.
FS024-S Failed to open log file : filename.
- The Fileshare Server encountered an error while attempting to open or
create the rollforward recovery log file. Common causes of this error
are listed below.
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 runtime 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 outside of 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 or alternatively the current database reference
file can be discarded and a new one created using the Database
Reference File Maintanance Utility.
FS028-W The log file shows the last session was not shut
down successfully.
- The last record written to the recovery log file when the Fileshare
Server is shut down successfully is a special record that marks the end
of the recovery log file. This message indicates that when the Fileshare
Server opened the log file (either to append to or read from in order to
perform a rollforward recovery) it could not find the special last
record. This indicates that the log file was not closed in a controlled
manner, probably due to a system crash.
If the Fileshare Server is starting up, the log file will be backed
up and a new log file created.
If a rollforward recovery is being performed, recovery will proceed
up to the last full record in the recovery log file (any incomplete
transactions will be rolled back).
- No action is required.
FS029-S The log filename is already specified in the
database reference file.
- An attempt has been made 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.
FS031-I Record lock timeout 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.
The record lock time-out period can be specified using the "/t"
option when configuring the Fileshare Server.
Note: 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.
On the next I-O operation, a status of 9/125 will be returned to the
Fileshare Client application that held the lock.
See the section Automatic Record Lock Timeout in the chapter
Fileshare for more information.
- No action is required, however the timeout 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 (log file 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.
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 using the
Workbench File Loader.
- 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.
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 Fileshare 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 Database Sequence Numbering
for full details on how 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 will
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 Fileshare for
more information.
FS039-S Improperly closed file - filename.
FS040-S Unable to read the file header record in the file
filename.
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 upon 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.
FS043-S The database reference file contains an invalid
entry.
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 Fileshare for more details.
FS051-W Failure to allocate a larger buffer, the I-O request
failed.
FS052-S Failure to allocate required memory. The Fileshare
Server is closing down.
- This message is displayed when the Fileshare Server is initialising
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.
- An attempt has been made to add an entry to the database reference
file which specifies a value for the data compression not within the
permitted limits. The data compression option must specify a value
within the range 0 to 255. Thus to use the routine CBLDC001 as the
compression method on records in the file, specify a compression value
of 1.
Note: 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 between 0 and 255.
See the section Database Reference File Maintenance in the
chapter Fileshare 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.
- An attempt has been made to add an entry to the database reference
file which specifies a value for the key compression not within the
permitted limits.
The key compression option must specify a value within the range 0
to 7. Note that specifying key compression only has 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 between 0 and 7.
See the section Database Reference File Maintenance in the
chapter Fileshare 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 in order for it to 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 the
Rollforward Recovery is being attempted. Then attempt 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 will attempt
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 will attempt
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 is
correct.
If they are correct then the current password file should be
discarded and a new one created using the Password File Maintenance
Utility. This will overcome any corruption that has occurred.
FS066-S The specified user name already exists in the
password file.
- This message is displayed when using the Password File Maintenance
Utility and an attempt has been made to add a user name to the password
file when the user name already exists in the password file.
- If you wish to update a user entry that already exists in the
password file, the entry should first be erased and then the new entry
added to the file. See the section Password File Maintenance in
the chapter Fileshare for more details.
FS068-I The password file is now empty and has been deleted.
- This message is displayed when the /e (erase) option has been
used 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 will automatically be
created when an entry is added 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 the /e (erase) option has been
used 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 correct (ie 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, a new password file will need to be created using the Password
File Maintenance Utility.
FS070-S Failure writing to the password file.
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 allow the operating system or runtime 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 runtime 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 allowed on database entries defining an
Alternate Program.
See the /ap option in the section Database Reference
File Maintenance in the chapter Fileshare for more
details.
- Do not specify a wild card symbol for this parameter as it is not
allowed.
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 (either when 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.
- This message is displayed 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 attempting
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 the
password entered (when prompted to do so) was incorrect.
- 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 either because it is not available or there is not
enough memory available to load the module. Alternatively there may be
an insufficient number of file handles available to allow the operating
system or runtime system to load the module.
This module is required in order 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 allow the logon to proceed in this
situation.
The Fileshare Client application program has been returned 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 allow the module to be loaded.
See the section Fileshare Security in the chapter Fileshare
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 FSSECOPN either because it is not available or there is not
enough memory available to load the module. Alternatively there may be
an insufficient number of file handles available to allow the operating
system or runtime system to load the module.
This module is required in order 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 allow the open to proceed in this
situation.
The Fileshare Client application program has been returned 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 allow the module to be loaded.
See the section Fileshare Security in the chapter Fileshare
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 upon the
network so that Fileshare Clients can connect to it. This message
indicates that the name the Fileshare Server is attempting to register
with 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 name that the Fileshare Server is configured to
register on the network is unique for this server. 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 upon the communications
protocol that is being used).
See your Programmer's Guide to Communications for
more information.
FS078-S No password file has been specified for the use of
background mode.
UNIX:
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 an attempt has been made to run the
Fileshare Server in background mode but no password file has been
specified.
- 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
Fileshare, and the chapter FSView for more
information.
FS079-S A supervisor password entry must exist for the use
of background mode.
UNIX:
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 an attempt has been made to run the
Fileshare Server in background mode but the password file 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
Fileshare, and the chapter FSView for more
information.
FS080-S No password file has been specified for the use of
the synchronous communications mode.
- An attempt has been made to start the Fileshare Server using
synchronous communications (as opposed to asynchronous communications
which is the default). To enable the use of synchronous communications,
a password file (which contains a supervisor id of FSVIEW) must be
specified. 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. For more information see the
sections Fileshare Password System and Password File
Maintenance in the chapter Fileshare for more information.
FS081-S A supervisor password must be specified in the
password file for the synchronous communications mode.
FS082-S The Netbios communications protocol is not
responding. Ensure the requester software is loaded and functional.
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 attempting 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 (i.e. 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.
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 limits that
allow logging to continue.
- The Fileshare Server process was terminated by an event outside
of the Fileshare Server's control (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 upon the communications protocol that is in use, the
Fileshare Client applications may appear to suspend if they are still
attempting 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 has been stopped, all
files have been closed, all transactions rolled back and any rollforward
recovery log file has been 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 attempt 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 Fileshare for more details.
- No action is required.
FS090-I Database Reference File installation completed
successfully.
FS091-I Rollforward Recovery Utility
FS092-I Rollforward Recovery has completed.
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 Fileshare 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)
- The ESC key sequence is being used to close down the Fileshare
Server. This is an additional prompt to ensure that the Fileshare Server
is not being closed in error and that the Fileshare Server is ok to shut
down.
Note: While prompting for this input, the Fileshare Server has
suspended accepting input from Fileshare Clients who may time out
after a period. The response to this prompt should be given as quickly
as possible.
- Responding "Y" to the above prompt will cause the Fileshare
server to enter its termination code. If there are still files open or
users logged onto this Fileshare Server then an additional prompt and
confirmation will be displayed. When the Fileshare Server shuts down all
outstanding transactions are rolled back, all open files are closed, all
users logged off and the communication support modules are closed down.
Any other response will cause the Fileshare Server to continue
operation 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. For
more details of the action code see the chapter Callable File
Handler.
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 (such as disk-full) 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 attempt the rollforward recovery again.
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 is being performed depends
upon 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 what processing should be done upon 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.
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) ?
- The Fileshare Server termination code has been invoked, however there
are still files open by Fileshare Client applications. This message is a
prompt to ensure that it is correct that the Fileshare Server should be
shut down.
The Fileshare Server termination code has been invoked using the ESC
key sequence.
This message indicates that Fileshare Clients are connected to this
Fileshare Server with files open, or alternatively, at least one
Fileshare Client application program has terminated abnormally leaving
one or more files open.
- At the prompt enter "y" or "n" depending upon if
the Fileshare Server is to be closed down.
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
deleted 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.
This message is displayed 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.
The rollforward recovery attempted is not necessary.
See the sections Rollforward Recovery Logging and Rollforward
Recovery Utility in the chapter Fileshare for more
details.
- No action is required.
FS122-I Communications too busy on CCI SEND - retrying.
- The Fileshare Server attempted to send a reply back to the Fileshare
Client performing an I/O request. The Fileshare Server was returned a
Too Busy error (error 10) from CCI.
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. See your Programmer's Guide
to Communications for more information.
- No action is required.
FS123-I Communications too busy on CCI RECEIVE - retrying.
- The Fileshare Server has attempted to receive information from the
network but was returned a Too Busy error (error 10) from CCI.
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. See your Programmer's Guide
to Communications for more information.
- No action is required.
FS124-I Checking the validity of the log file, please wait.
- This message is displayed 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 is therefore
having to scan through the log file to find the last sequence number
that was in use and 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 Fileshare for more
information.
- No action is required.
FS125-I Recovery possible to last valid recovery log file
record.
- This message is displayed when the Rollforward Recovery Utility has
been invoked. This message indicates that the recovery log file has been
searched and 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 Fileshare for more
information.
- No action is required.
FS126-I Performing recovery, please wait.
FS127-S Invalid name mapping command.
- This message is displayed 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 sections Filename Mapping and Database Reference
File Maintenance in the chapter Fileshare 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 outside of 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:
- The Fileshare Server process has been terminated outside the
control of the Fileshare Server or run-time system. Such an instance
would be a kill command on UNIX or closing the Fileshare Session on
OS/2 or 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 Runtime System to be
invoked. In this situation you should contact Micro Focus technical
support to try and ascertain the cause of this error.
The Fileshare Server will terminate 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.
FS130-I Reading database reference file, please wait.
FS131-W Invalid communications mode - parameter ignored.
FS132-I The Fileshare Server is running with the following
communcation protocol(s):
FS133-I Processing the password file, please wait.
FS134-I The password file cannot be found - creating a new
password file.
FS135-I Fileshare Server security is active.
FS136-I Fileshare Server security is not active.
- A password file has been specified, however the only user-ID 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 attempt to access the Fileshare Server do not have to
supply a valid user-ID or password.
Logon attempts are validated by the Fileshare Server by calling the
FSSECLOG module.
See the section Fileshare Security in the chapter Fileshare
for more details about the Fileshare Server security features and how
to use them.
See the section Password File Maintenance in the chapter
Fileshare 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.
- This message is displayed 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 that this message implies that the correct sequence of regulary
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
Fileshare for more details.
- No action is required.
FS139-I A matching date and time entry has been found in the
log file.
- This message is 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 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.
- This message is 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.
- This message is displayed 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 the attempt to flush the recovery log file to disk was
made. This implies that the operating system does not enable
application programs to force I-O buffers to be flushed to disk. The
Fileshare Server is thus 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 sections Database Reference File Maintenance and Logging
for Rollforward Recovery - Fileshare Server in the chapter Fileshare
for more details.
FS143-W The Operating System does not allow free disk space
information to be obtained.
FS144-W More than one communications protocol has been
specified - synchronous communications mode not active.
- An attempt has been made to start the Fileshare Server using the
synchronous communcations mode (as opposed to the asychronous
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 communication 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 Fileshare Server has been returned an error from CCI indicating
that a Fileshare Client has been disconnected. This can be due to a
network error or because the Fileshare Client application has terminated
abnormally.
The user number and user name (if one was supplied at the time that
this user logged onto the Fileshare Server) is displayed.
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 their next I-O operation.
- This message indicates that there may be a problem with the network
or that the Fileshare Client application program is no longer
functioning. 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.
FS147-I A duplicate network message was received and
discarded.
- This message only occurs when you are using the CCIIPX protocol. 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 it is not a valid I-O request.
- This message indicates that an old version of the CCIIPX modules are
being used. Ensure that the latest CCIIPX modules are installed on the
Fileshare Client and Fileshare Server machines.
FS148-I CCI return-code (function func) = code.
- This message is displayed 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 Micro Focus Technical Support 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 this message is displayed 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.
- This message is displayed 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 implies 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.
- Follow the actions for message FS014.
FS153-I The Fileshare Server name has been reregistered on
the network.
- The Fileshare Server attempted to register its name upon 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.
FS155-I Password accepted - CCI Trace is enabled. Do you
want CCI Trace active immediately? (Y/N)
- This message is 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 hence include all of the CCI
initialization requests made by the Fileshare Server).
- Entering "Y" to this prompt will cause the Fileshare Server
to start using CCI Trace immediately and will cause all CCI
intialization requests to be traced to the CCI Trace file. The CCI Trace
will remain operational until toggled off using the F3 key.
Entering any response apart from "Y" will not enable CCI
trace immediately. However, CCI trace can be toggled on at a later
time using the F3 key.
See also messages FS154 and FS156.
FS156-W Incorrect password - CCI Trace is disabled.
- This message is displayed 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.
This message is displayed 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 that 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. This message is displayed when either the CCI
Trace is not made active immediately on the Fileshare Server starting up
(see message FS155) or toggled off using the F3 key while the Fileshare
Server is operational.
- No action is required.
FS160-I Fileshare trace activated.
- This message is 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 upon 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.
FS163-I Input user opcode [filename-1]
[ filename-2].
FS170-I Input- Logon.
- This message is displayed 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.
- This message is displayed when the Fileshare Server trace option is
activated and a logoff request has been received by the Fileshare
Server. If the Fileshare Client supplied a user name when it logged onto
this Fileshare Server then the user name will be displayed here if
Fileshare Security is active. If no user name was supplied, then the
user number will be displayed.
The user number is generated when the Fileshare Client logs onto
this Fileshare Server. The first Fileshare Client will have 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.
- This message is displayed when the trace option is activated and a
Find File request has been received by the Fileshare Server. A Find File
request is automatically made by a Fileshare Client when a program
attempts to open a file, the Fileshare Server that should process the
file is not 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.
user |
If the Fileshare Client supplied a user name when
it logged onto this Fileshare Server then the user name will be
displayed here if Fileshare Server security is active. If no user
name was supplied, then the user number will be displayed. The user
number is generated when the Fileshare Client logs onto this
Fileshare Server. The first Fileshare Client will have 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.
FS176-W There is no log file backup directory specified in
the database reference file.
- An attempt to erase a recovery log file backup directory entry from
the database reference file was made but there is not a recovery log
file backup directory name specified in the database reference file.
- No action is necessary (as the erase operation is not required
because there is no recovery log file backup directory name specified in
the database reference file).
FS177-S The log file backup directory specified cannot be
found in the database reference file.
- An attempt to erase a recovery log file backup directory name from
the database reference file was unsuccessful because the log file backup
directory name specified is not the same as the log file backup
directory name in the database reference file. The operation therefore
cannot be completed successfully.
- Specify the correct name of the recovery log file backup directory
name when attempting 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 log file backup directory has been added to the
database reference file.
- The Database Reference File has been invoked to add a recovery log
file backup directory name to the database reference file and the
operation has completed successfully. The database reference file now
contains the name of the recovery log file backup directory specified.
- No action is required.
FS179-S A log file backup directory is already specified in
the database reference file.
- An attempt has been made to add the name of the recovery log file
backup directory to the database reference file, however such an entry
already exists in the database reference file. A database reference file
can only contain one recovery log file backup directory name.
- Remove the current recovery log file 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
recovery log file 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, when adding a recovery log filename to
the database reference file do not use a filename with an extension.
FS182-W Output- Access Denied
- This message is displayed when the Fileshare Server trace option is
activated and a logon request as been received by the Fileshare Server.
The logon request by the Fileshare Client has been denied, either
because an incorrect password or user-ID was supplied (and password
security is active) or the logon validation by the module FSSECLOG
failed (if password security is not active).
If using password file security, 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
specified when the Fileshare Server was started.
If the password file security option is not being used, then the
logon attempt has been denied by the FSSECLOG module. The FSSECLOG
module supplied with the Fileshare Server will allow any Fileshare
Client to log onto the Fileshare Server. This therefore implies that
the logon attempt has been denied by a user supplied FSSECLOG module
and the appropriate action should be taken.
See the section Fileshare Security in the chapter Fileshare
for more information of how the Fileshare Server validates logon
attempts by Fileshare Clients.
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 Fileshare.
FS189-W The log file backup directory does not exist.
- The Database Reference File Maintenance Utility has been invoked to
add the name of a recovery log file backup directory to the database
reference file.
This message indicates that the directory specified does not exist.
The recovery log file 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 the directory is created or made
available to the Fileshare Server so that the automatic backup on the
recovery log file can take place. If the directory does not exist, the
Fileshare Server will fail in its attempt to automatically backup the
recovery log file when required to do so.
FS190-W The log file backup directory specifies the name of
an existing file.
- The Database Reference File Maintenance Utility has been invoked to
add the name of a recovery log file 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 recovery log file 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 on the recovery log file can take place. The file of
this name should be removed.
If the directory does not exist, the Fileshare Server will fail in
its attempt to automatically backup the recovery log file when
required to do so.
FS191-W An error occurred accessing the log file backup
directory.
- The Database Reference File Maintenance Utility has been invoked to
add the name of a recovery log file backup directory to the database
reference file.
This message indicates that when verifying that the directory
exists, the Database Reference File Maintenance Utility was returned
an unexpected error.
The error did not indicate that the directory exists, the directory
does not exist or that the directory name is actually a file.
See also messages FS189-W and FS190-W.
The recovery log file 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 on the recovery log file can take place.
If the directory does not exist or cannot be accessed, the Fileshare
Server will fail in its attempt to automatically backup the recovery
log file when required to do so.
FS192-S More than one log file exists in the log file
directory.
- This message is displayed 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 the "L"
character. This message indicates that the correct procedures for
backing up data files and deleting recovery log files is 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 will
create 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 Fileshare.
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 attempted to open it.
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. This
message can also be displayed 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 attempted 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.
This error indicates that the Fileshare Server does not have the
correct permissions to access the file or that the recovery log file
is open by another process. The Fileshare Server requires read and
write access to the recovery log file and will attempt to open the
file with exclusive access.
- Ensure that the Fileshare Server has read and write access
permissions to the recovery log file and that the file is not open by
another process.
FS194-I The log file "filename-1" have
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 will be 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".
FS197-S Unable to create the log file "filename".
- The Fileshare Server attempted to create the recovery log file
indicated, but was unable to do so.
FS196-W - 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 will not close down. The Fileshare
Server will attempt 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.
FS197-S - 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 an attempt to start the Fileshare Server is made
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 open by another process.
FS198-W The attempt to backup the log file failed because
the backup file "filename" already exists.
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.
FS198-W - 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 will attempt
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.
FS199-S - The Fileshare Server was unable to backup the log file
which it cannot append to. 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 an
attempt to start the Fileshare Server is made again.
- 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
Fileshare for more details.
FS200-W The attempt to backup the log file to "filename"
failed.
FS201-S The attempt to backup the log file to "filename"
failed.
- The Fileshare Server attempted 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.
FS200-W - 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 will attempt
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.
FS201-S - 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. The problem should be rectified before an attempt to start the
Fileshare Server is made again.
- 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 attempting to start the Fileshare Server, 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 Fileshare
for more details.
FS202-I The Fileshare Server will continue logging to the
log file "filename".
- The Fileshare Server attempted to backup the recovery log file as
part of an FSView or FSMgr operation. However, the backup operation
failed. The Fileshare Server is attempting 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 that a valid recovery log file already
exists which it is able to append data to.
This message indicates that the recommended sequence of backing up
data and removing recovery log files is not being followed as a
recovery log file already exists when the Fileshare Server is started.
See the section Rollforward Recovery Logging in the chapter
Fileshare 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.
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, the attempt to delete
the old recovery log file returned an unexpected error. The Fileshare
Server will attempt 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. The old recovery log file
should be removed manually if the backup operation has succeeded. This
will free up 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.
- This message is displayed when the Rollforward Recovery Utility has
determined that there is more than one starter recovery log file. A
starter recovery log file is created when the Fileshare Server is
started and a new log file is created.
Thus, if the Fileshare Server is started and there is no recovery
log file available, one will be created. If an automatic backup of the
recovery log file is made, the starter recovery log file will be
backed up and a continuation recovery log file will be created. If
another backup is performed, the continuation recovery log file will
be backed up and another continuation recovery log file created.
A rollforward recovery can only proceed when there is one starter
recovery log file to use.
- Ensure that the correct recovery log files are in place and then
attempt the rollforward recovery process again.
This message indicates 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 Fileshare
for more details.
FS207-I There is no starter log file in the log file
directory.
FS208-S There is no starter log file in the log file backup
directory.
- The Rollforward Recovery Utility has been invoked and has scanned all
of the recovery log files in the recovery log file 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 log file
backup directory.
- The Rollforward Recovery Utility has not found a starter log file in
the recovery log file directory, but one was located in the recovery log
file backup directory. The Rollforward Recovery Utility is therefore
able to commence 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 recovery log file backup directory
and has determined that there is more than one starter recovery log
file.
A rollforward recovery can only commence when there is one starter
recovery log file to use.
See the section Rollforward Recovery Logging in the chapter
Fileshare for more information.
- Ensure that the correct recovery log files are in place and then
attempt the rollforward recovery process again.
This message indicates that the recommended sequence of backing up
data files and removing recovery log files is not being followed.
FS211-S An error occurred checking the header on the log
file "filename".
- The Rollforward Recovery Utility was able to locate 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
was unable to 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 open 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 is unable to find the
next recovery log file in the same directory as the previous recovery
log file.
The Rollforward Recovery Utility will attempt to find the next
recovery log file in the recovery log file backup directory if one has
been specified.
The Rollforward Recovery Utility will now search the recovery log
file backup directory for the required file.
- No action is required.
FS214-I Searching for a backed up log file in the log file
directory.
- The Rollforward Recovery Utility is unable to locate the required
recovery log file in the current log file directory and so 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 log file
backup directory.
- The Rollforward Recovery Utility is unable to locate the required
recovery log file in the current log file directory and so is now
searching for a backed up copy of the required recovery log file in the
backup recovery log file 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 for a backed up starter
recovery log file in the log file current directory but was unable to
find one.
- No action is required.
FS217-I No backed up starter log file can be found in the
log file backup directory.
- The Rollforward Recovery Utility has searched for a backed up starter
recovery log file in the log file backup directory but was unable to
find one.
- 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 for a backed up
continuation recovery log file in the current log file directory but was
unable to find one.
- 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 for a backed up
continuation recovery log file in the recovery log file backup directory
but was unable to find one.
- No action is required.
FS220-I A backed up starter log file has been found in the
log file directory.
FS221-I A backed up starter log file has been found in the
log file backup directory.
FS222-I A backed up continuation log file has been found in
the log file directory.
FS223-I A backed up continuation log file has been found in
the log file backup directory.
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 the recommended sequence of backing up
data files and removing unneeded recovery log files is not being
followed. See the section Rollforward Recovery Logging in the
chapter Fileshare for more information.
- Ensure that only the correct backed up starter recovery log file is
in the log file directory. Then attempt to start the rollforward
recovery process again.
FS225-S The log file backup directory contains more than one
backed up starter log file.
- The Rollforward Recovery Utility has searched the recovery log file
backup directory for a backed up starter log file. The backup recovery
log file directory contains more than one backed up starter log file and
so is unable to determine which one is the correct one to use.
It is not possible to start the rollforward recovery process.
- Ensure that only the correct backed up starter recovery log file is
in the recovery log file backup directory. Then attempt to start the
rollforward recovery process again.
Note that this message indicates that the correct sequence of
backing up data files and removing unneeded recovery log file is not
being followed. See the section Rollforward Recovery Logging
in the chapter Fileshare for more information.
FS227-W Failure to set Fileshare Server's access rights.
- This message is displayed by the Fileshare NLM only.
The Fileshare NLM attempted to set the Fileshare Server's access
rights on the NetWare operating system but encountered an error when
doing so.
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
attempt to connect with supervisor access rights to the NetWare
operating system.
- If this error persists you should contact your Micro Focus Technical
Support representative.
FS228-I CCI SEND status checked.
- A request sent back to a client application from the Fileshare server
which previously had not completed within the expected time period has
now been determined to have either failed or completed successfully.
See also message FS149.
A second message following this one indicates the outcome of the
request in question. If this indicates communications errors occurring
frequently there may be errors on the network, or client applications
may be terminating abnormally. See your Programmer's Guide to
Communications for more information about communications
errors. If no message follows then this indicates that the request
completed normally.
- No action is required.
FS229-I Unrecognized CCI session ID - could not disconnect
user.
FS230-I User : user-ID user-name
- This message is displayed when the Fileshare Server has been returned
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 attempted to contact. This message is used in conjunction with
other error messages displayed by the Fileshare Server to determine
information specific to the error which has occurred.
- 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.
- This message is displayed 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 attempt to restart 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 will therefore attempt to allocate
memory as required, with no upper limit.
- The message indicates an internal Fileshare NLM failure. Please
contact your Micro Focus Technical Support representative.
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 minumum 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 to 6 Mbytes.
- Specify a different value for the /mm option so that the
amount of dynamically allocated memory that it can use is at least 6
Mbytes.
FS235-W Failure to allocate memory for incomplete CCI SEND
processing.
- The Fileshare Server has attempted to allocate some memory in order
to simultaneously process CCI requests to multiple Fileshare Client
sessions, but there is insufficient free memory available for it to do
so. As a consequence, 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 the
particular request in question, although it may allow 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 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 filename has been removed from the database
reference file.
- This message indicates that the Database Reference File Maintenance
Utility has successfully removed the log filename 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 of the name
that the Fileshare Server is attempting to use for the next recovery log
file exists, and 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 attempted 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 attempt 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 of the name that the Fileshare
Server is attempting to use for the next recovery log file exists.
FS238-I Terminating communications with this user.
- This message is displayed, together with FS015-W, when the network
connection with an unknown Fileshare Client is terminated.
- No action is required.
FS239-I Output - user Record locked. Retry
operation.
- This message is displayed 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.
- This message is displayed 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.
- This message is displayed 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. This
message is displayed 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).
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
| Fileshare Tutorial |
| Fileshare on Novell NetWare | |