LAN Server 4.0 Error Messages Reference

This reference describes error messages and their cause and actions.
The error messages are grouped by category and each category is
identified by an unique, 3-letter prefix.  Messages within each
category are listed alphanumerically.  You can use the online
Search function to find a specific error message number.

You can also print the entire reference, which is an ASCII file.

The error message categories and their prefixes are listed below.
GUI errors are not documented in this reference.

 * BSH - 386 HPFS Boot Diskette

 * CAC - HPFS CACHE386

 * CHS - Change Server Name Utility

 * CAS, ETH, LT0, LT1...., MAC, PRO, UBI, XI0, XI1 - Transport

 * FTD - Fault Tolerance

 * HFS - 386 HPFS

 * LSI - Installation

 * NET - DOS LAN Services (see Note below)

 * NET - Command Line Interface (see Note below)


Note:
Some of the NET error messages are not in alphanumeric order because the
NET prefix is used for 2 categories; LAN Server CLI and DOS LAN Services.
DOS LAN Services also lists errors prefixed with ERROR.

BSH0004:  Errors occurred while making BOOTSH.EXE a privileged process.

          Booting is stopped.



Cause:   The 386 HPFS file system driver (FSD) on your boot diskette
         failed to make this BOOTSH.EXE file privileged.
         Booting is stopped.

Action:  Ensure that a current version of the 386 HPFS FSD is on your
         boot diskette.  Then start your workstation again with the
         boot diskette.


---------  

BSH0005:  A good CONFIG.SYS file cannot be found on your workstation.

          Booting is continuing.



Cause:   An error occurred while opening the CONFIG.SYS file
         on the boot drive of your workstation.

Action:  After your workstation is started from the boot diskette,
         ensure that you have a CONFIG.SYS file on the boot drive
         of your workstation.


---------  

BSH0006:  The LAN root directory cannot be determined from the
          IFS statements in your CONFIG.SYS file.

          Booting is continuing.



Cause:   The CONFIG.SYS file on the boot drive of your workstation
         does not have the proper LAN root directory specified.

Action:  After your workstation is started, do one or more of
         the following:

         - Correct any error encountered while starting your
           workstation from the boot drive.
         - Ensure that the IFS statement for the NETWKSTA.* file
           has a /I option with the proper LAN root directory specified.
         - Ensure that the IFS statement for the HPFS386.IFS file
           has a /I option with the proper LAN root directory specified.

         Note that the asterisk (*) is the file extension.


---------  

BSH0007:  An unknown process is using the user accounts database.

          Booting is stopped.



Cause:    A process that cannot be identified is presently using the
          user accounts database.

Action:   Remove any RUN= or DEVICE= statements that may access the
          user accounts database from the CONFIG.SYS file on your
          boot diskette.  Then start your workstation again with
          the boot diskette.


---------  

BSH0008:  The following user accounts database file is missing
          or damaged:

              ***

          Booting is continuing.



Cause:    The user accounts database file specified by the /I option
          in the IFS statements (for either NETWKSTA.* or HPFS386.IFS)
          in the CONFIG.SYS file on your boot drive is either
          missing or damaged.  Note that the asterisk (*) is the
          file extension.

Action:   After your workstation is started, do one or more
          of the following:

          - Correct any error encountered while starting your
            workstation from the boot drive.
          - Ensure that you have a good NET.ACC file in the
            ACCOUNTS subdirectory of the path specified by
            the /I option in the IFS statements.


---------  

BSH0009:  You did not log on as an administrator.

          Booting is stopped.



Cause:    You may have used an incorrect administrator ID or
          an incorrect password.

Action:   Start your workstation again with the diskette and log
          on as an administrator.


---------  

BSH0011:  Error *** occurred while starting the following user shell:

           ***

          Trying to start the default shell:  CMD.EXE



Cause:   A system error occurred while starting the user protect-mode
         shell.  This error may indicate an incorrect PROTSHELL= line
         in the CONFIG.SYS file on the boot diskette.

Action:  Correct the PROTSHELL= line in the CONFIG.SYS file, or
         ensure that the user shell specified by the PROTSHELL= line
         is on your boot diskette.  Then start the workstation again.


---------  

BSH0012:  Error *** occurred while starting the CMD.EXE file.



Cause:   A system error occurred while starting the CMD.EXE file.

Action:  Ensure that a good CMD.EXE file is on your boot diskette.
         Then start your workstation again with the boot diskette.


---------  

BSH0013:  The 386 HPFS is not loaded from your boot diskette.

          Booting is stopped.



Cause:   The 386 HPFS file system driver (FSD) is missing or damaged.

Action:  Ensure that the 386 HPFS FSD is loaded by doing one or more
         of the following:

         - Correct any error that the 386 HPFS FSD encountered.
         - Ensure that you have the HPFS386.IFS
           file on your boot diskette.
         - Correct the IFS statement in the CONFIG.SYS file of
           your boot diskette.


---------  

CAC1606: *** is not a valid 386 HPFS drive.



Cause:  The listed drive does not exist or is not a
formatted high performance file system (HPFS) partition.

Action:  Specify a drive that has the HPFS, and retry the
command.  To see a list of drives with the HPFS, type:

     CACHE386 /OPTIONS

---------  

CAC1607: The CACHE386 background process cannot start.



Cause:  The CACHE386 background process cannot start.
There may not be enough memory available or an
unexpected OS/2 error may have occurred.

Action:  If this message is displayed during system start,
change your CONFIG.SYS file to decrease your memory requirements.
Restart your computer.  If it fails again, the computer may not
have enough memory to start lazy writes.

If this message is displayed after system start, end sessions or
applications to free up memory.  Retry the command.  If it fails
again, the computer may not have enough memory to start lazy writes.



---------  

CAC1608: The CACHE386 configuration parameter is not valid;
parameter *** is set to *** msec for drive ***.



Cause:  The value you specified is not in the valid range for this
option.  The size of the parameter that was set incorrectly has
been set to the nearest allowable value for the listed drive.

Action:  Retry the command with a valid value for the parameter.


---------  

CAC1609: The CACHE386 configuration parameter is not valid;
parameter *** is set to *** msec for all drives.



Cause:  The value you specified is not in the valid range for this
option.  The size of the parameter that was set incorrectly has
been set to the nearest allowable value for all the HPFS drives.

Action:  Retry the command with a valid value for the parameter.


---------  

CAC1611: The local security system could not start.  The system cannot
access the user accounts database (NET.ACC).

** LOCAL logon is not permitted **




Cause:  Local security cannot be started because the user accounts
database (NET.ACC) cannot be accessed or is damaged.

Action:  Be sure that NET.ACC is present in the IBMLAN\ACCOUNTS directory.
If it is present, replace it with a backup copy, and restart the computer.


---------  

CAC1612: The local security system could not start.
The system error code is ***.

** LOCAL logon is not permitted **




Cause:  Local security cannot be started because an IBM OS/2
error occurred.

Action:  For more information about the IBM OS/2 error, type:

     HELPMSG message#

where message# is the number of the error.

Then correct the error and restart the computer.


---------  

CAC1614: The local security system could not start.  There is not enough
memory available.

** LOCAL logon is not permitted **




Cause:  Local security cannot be started because there is
not enough memory.

Action:  Change your CONFIG.SYS file to decrease your memory
requirements.  Restart your computer.  If it fails again, the
computer may not have enough memory to start local security.


---------  

CAC1618: 
Local security could not be started because the user accounts
database (NET.ACC) is missing or damaged, and no usable backup
database (NETACC.BKP) is present.

*** THE SYSTEM IS NOT SECURE. ***




Cause:  Local security cannot be started because there is no usable
copy of the user accounts database (NET.ACC) available.

Action:  Restore NET.ACC from a backup copy to the IBMLAN\ACCOUNTS
directory, and then restart the computer.


---------  

CAC1622: The action you requested could not be completed.   Administrative
authority is required.



Cause:  You tried a command that only an administrator can perform.
You are not currently logged on as an administrator.

Action:  Log on as an administrator and retry the command.


---------  

CAC1623: The high performance file system driver was not found;
processing has stopped.



Cause:  The HPFS386.IFS file has not been loaded, so the operation could
not continue.  This error indicates that the OS/2 LAN Server program
was not installed correctly.

Action:  Ensure that HPFS386.IFS is present in the
directory specified by the IFS line in the CONFIG.SYS file.
If it is not present, run the LAN Services installation/configuration
program to install and load the file.


---------  

CAS0002: *** was passed an unsupported parameter: ***.

Cause:  The program was invoked with a command line
argument that it does not recognize.

Action:  To view the syntax of the command, run the program
without parameters.  Alternatively, check the syntax of the
command in the documentation, and then run the program with
the correct command line arguments.

---------  

CAS0003: *** was not able to access the log file ***.

Cause:  The program was unable to write to the log file
specified in the message.

Action:  If the file exists, ensure that it is not read-only.
If the drive on which the file is located should be attached
through SRVIFS, ensure that the drive exists and that it is
not read-only.  Also, ensure that the directory exists on the
drive indicated.

---------  

CAS0004: *** could not find the directory ***.

Cause:  The program was unable to find the directory
specified in the message.

Action:  If the drive on which the directory is located should
be attached through SRVIFS, ensure that the drive exists.  Also,
ensure that the directory exists on the drive indicated.

---------  

CAS0005: *** - The required parameter *** was not specified.

Cause:  The program was invoked without the specified required
command line argument.

Action:  To view the syntax of the command, run the program
without parameters.  Alternatively, check the syntax of the
command in the documentation, and then run the program with
the correct command line argument.

---------  

CAS0006: *** cannot find a SRVIFS drive.  If a SRVIFS drive is not attached, 
then the /REQ: parameter must be supplied on the command line.

Cause: The program cannot determine the client name to use for
this workstation because the /REQ: parameter was not passed on
the command line and an attached SRVIFS drive was not found.

If the /REQ: parameter is not on the command line, then a valid
drive must be accessed through SRVATTCH for this program to
determine the SRVIFS requester name.

Action:  Perform one of the following actions, and then run the
program again:

*  Add the /REQ: parameter to the command line.

*  Ensure that SRVIFS is running and that there is a CALL=SRVATTCH
   statement in the CONFIG.SYS file.

---------  

CAS0007: *** - The *** parameter was specified more than once.

Cause:  The specified parameter was entered on the command
line more than once.

Action:  Run the program again without specifying the
duplicate parameter.

---------  

CAS0008: *** - The REXX command file *** was not found.

Cause:  The specified REXX command file specified could not be
found by the program, and could not be executed.

Action:  Ensure that the path indicated in the /CMD: parameter is
correct and that the indicated REXX command file exists in that
path. Also, ensure that the REXX command file name matches the
desired SRVIFS requester name.  If it does not, SRVIFS must be
restarted with the correct SRVIFS requester name.

---------  

CAS0009: *** - The REXX command file *** was not found.
The program will attempt to run ***.

Cause:  The REXX command file matching the client name could not be found
by the program and could not be run.  Since the /D or /D: parameter was
specified on the command line, the program will attempt to run the default
command file indicated.

Action:  If you meant for the default command file to run instead of a
command file matching the client name, no action is necessary.

If the program should have been able to find the client command file,
ensure that the path specified in the /CMD: parameter is correct and
that the indicated command file exists in that path.  Also, ensure that
the command file name matches the desired client name.  If it does not,
perform one of the following actions and run the program again:

* Rename the client command file to match the desired client name.

* Provide the correct client name on the command line with the /REQ:
  parameter.

---------  

CAS0010: *** - A command file name must follow ***.

Cause:  A value was not specified on the command line for the parameter
indicated.

Action:  Run the program again specifying a valid command file name for
the parameter indicated.

---------  

CAS0013: REXX has not been initialized.

Cause:  The program could not start the LAN CID Utility command
file because REXX has not been initialized on the system.

Action:  Perform one of the following actions and then run the program
again.

* Run the command 'DETACH <path>SRVREXX', where <path> is the directory
  containing the LAN CID Utility programs.

* Ensure that a CALL=<path>SRVREXX statement is in your CONFIG.SYS file
  and that the indicated path is correct.  If SRVREXX is located on a
  redirected drive, also ensure that the drive indicated is attached.  If
  changes had to be made to the CONFIG.SYS file, then restart
  (CTRL+ALT+DEL) the workstation before running the program again.

---------  

CAS0014: An error occurred while validating ***.

Cause:  The program detected an error during parameter validation.

Action:  You can get the cause and action information you need to resolve
the error from the help for the message displayed immediately
following CAS0014.  Display the help for the message number that the program
displayed immediately after the line with message number CAS0014 on it.

---------  

CAS0015: The value for the *** parameter must be alphanumeric.

Cause:  The value specified for the indicated parameter contained
nonalphanumeric characters.

Action:  Run the program again specifying a valid alphanumeric value for
the parameter specified.  For this program, a valid alphanumeric value
consists of the characters A through Z, a through z, 0 through 9, and the
underscore.

---------  

CAS0016: *** - An alphanumeric client name must follow ***.

Cause:  A value was not specified on the command line for the parameter
indicated.

Action:  Run the program again specifying a valid alphanumeric value for
the parameter specified.  For this program, a valid alphanumeric value
consists of the characters A through Z, a through z, 0 through 9, and the
underscore.

---------  

CAS0018: If /REQ:* is on the command line, then one of the /D or /D: 
parameters must also be on the command line.

Cause:  The program was instructed with the /REQ:* parameter to randomly
select a client name, but the default command file to run was not
specified with either the /D or the /D:  parameter.  The program requires
that a default command file name be supplied when the client name is to
be randomly selected.

Action:  Perform one of the following actions and then run the program
again:

* Add the /D parameter to the command line to run the default command
  file DEFAULT.CMD.

* Add the /D:<filename> parameter to the command line to run the default
  command file <filename>.

* Change the /REQ: parameter to indicate a valid client name.

---------  

CAS0020: The value for the *** parameter cannot contain drive or path 
information.

Cause:  A command file name was provided for the specified parameter that
contained drive and/or path information.  Since the command file will be
run from the directory you specified on the /CMD:  parameter, the command
file name must not contain a path or a drive indicator.

Action:  Run the program again with a valid command file name indicated
for the parameter specified in the message.

---------  

CAS0021: *** cannot open the file *** for input.

Cause:  The required file could not be opened for processing.

Action:  Verify that the file exists.  If the file exists,
determine why the file could not be opened and correct
the problem.

---------  

CAS0022: *** cannot process *** because it is a hidden file.

Cause:  The required file has the hidden attribute set.
The program will not modify hidden files.

Action:  Use a utility to unhide the file.

---------  

CAS0023: *** - The required DEVICE=*** statement was not found in ***.

Cause:  A required device driver was not found in the
CONFIG.SYS file.

Action:  Edit the CONFIG.SYS file and add the appropriate
DEVICE= statement.

---------  

CAS0024: *** Warning! The *** parameter was not specified.

Cause:  The optional parameter was not specified on the command
line.  This parameter may be needed to access code on the server.
If the parameter was omitted from the command line intentionally,
this warning message can be ignored.

Action:  If the parameter should have been specified, then add the
parameter to the command line and run the program again.

---------  

CAS0025: *** cannot open the temporary file ***.

Cause:  The program cannot open the file that it uses for
temporary file processing.

Action:  If the file exists, erase it.  Ensure that the drive
the file is on is not full or read-only.

---------  

CAS0026: *** completed with errors.

Cause:  The program was not able to complete processing the
CONFIG.SYS file, the STARTUP.CMD, or both on one or more
drives.

Action:  Look at the messages displayed prior to this one to
determine the cause of the failure.

---------  

CAS0028: Both the /D and /D: parameters may not be specified on the command 
line at the same time.

Cause:  Both the /D and /D: parameters were specified on the command
line; however, you can only specify one of them.

Action:  Perform one of the following actions and then run the program
again:

* Specify the /D parameter to run the default command file DEFAULT.CMD if
  the client command file cannot be found.

* Specify the /D:<filename> parameter to run the default command file
  <filename> if the client command file cannot be found.

---------  

CAS0029: *** Warning!  One or more lines in *** exceed 255 characters.

Cause:  The program has detected or created one or more lines in
the specified file that exceed 255 characters in length.  This
will not be a problem with the operating system processing the
file, but most editors, if used on this file, will either truncate
or wrap the long lines.  If this happens, the operating system will
no longer process the file correctly.

Action:  If this file will be edited, be sure to use an editor
that will handle lines greater than 255 characters without
truncating or wrapping.  If an editor will not be used on this
file, there is no action to take.

---------  

CAS0033: *** was unable to update ***.

Cause:  The updates could not be made to the file indicated.

Action:  If the file exists, ensure that it is not read-only
or on a read-only drive.  Also, ensure that the drive is not full.

---------  

CAS0038: *** - A valid drive indicator must follow ***.

Cause:  A valid drive indicator was not provided for the specified
parameter.  The drive indicator can have the form Z, Z:, or Z:\,
where the drive letter is any of the letters between A and Z.

Action:  Run the program again with a valid drive indicator for the
parameter specified in the message.

---------  

CAS0039: *** - A fully-qualified file name must follow ***.

Cause:  A fully-qualified file name was not provided for the
specified parameter.  A fully-qualified file name must have the
form Z:\<path>\<filename>.

Action:  Run the program again with a fully qualified file name
specified for the parameter indicated in the message.

---------  

CAS0040: *** - A fully qualified or relative path must follow ***.

Cause:  A fully qualified or relative path name was not provided
for the specified parameter.  A fully qualified path has the form
Z:\<path>.  A relative path has the form ., .., .\<path> or ..\<path>.
Multiple paths may be specified for the parameter if separated by
semicolons, for example,  Z:\DLL;.;.\DLL;X:\EXE\DLL.

Action:  Run the program again using the preceding path formats to
specify the value of the parameter indicated in the message.

---------  

CAS0041: The value for this parameter must be no more than *** bytes long.

Cause:  The value specified for the parameter indicated is more
than the maximum number of bytes allowed for this parameter.

Action:  Run the program again specifying a value for the indicated
parameter that is no more than the maximum number of characters.

---------  

CAS0045: *** - A fully qualified directory name must follow ***.

Cause:  A fully qualified directory name was not provided for the
specified parameter.  A fully qualified directory name has the
form Z:\<path>.

Action:  Run the program again using the preceding path format to
specify the value of the parameter indicated in the message.

---------  

CAS0060: *** encountered an error while determining the response file for ***.

Cause:  The procedure was unable to produce a response file name
for the indicated install program.

Action:  Check the values for the response file path and default
response file for the install program indicated in the appropriate
REXX command file.  Ensure that the drive, path, and the default
response file name exist.

---------  

CAS0061: *** encountered an error while determining the response file.

Cause:  The procedure was unable to produce a response file name
for an install program.  The program was also unable to determine
the install program name.

Action:  Check the LCU log file to determine the product that was
installing.  Then check its values for the response file path and
the default response file in the appropriate REXX command file.
Ensure that the drive, path, and default response file name exist.

---------  

CAS0063: *** was passed a nonnumeric value for parameter number ***.

Cause:  The procedure was called with a nonnumeric value for
a numeric parameter.

Action:  Ensure that the call to the procedure has a numeric
value for the parameter number indicated.

---------  

CAS0064: *** was called with an insufficient number of parameters.

Cause:  An incorrect number of parameters was passed to the
procedure.

Action:  Ensure that the syntax of the call to the procedure
has the same syntax as in the original REXX command file
shipped with this product:  CASSKEL.CMD.

---------  

CAS0073: [***] *** returned to the REXX program.

Cause:  The REXX program may have encountered a problem when
trying to execute the specified program.

Action:  If all of the installs specified in the REXX program
completed successfully, then there is no action to take.

If this message is displayed as the last message in the log
file and the REXX program did not complete all of the installs
on the workstation, then perform one of the following actions:

* If the program exists, determine why the program would not run.

* If the program does not exist, ensure that the path specified is
  the path to the executables directory on the server.  If it is,
  put the program in that directory.  If it is not, ensure that the
  exepath= statement in the REXX command file is set to the fully
  qualified path to the executables directory on the server.

---------  

CAS0076: The procedure *** was called with an unsupported value
*** for the CID type parameter.  CID type is the first parameter
of the procedure.  The supported CID types are:

* ***, Normal CID return code processing
* ***, Treat return codes 0x4, 0x8, and 0x12 as bad return codes.

Cause:  The procedure was called with an unsupported value for the CID
type parameter.  CID type is the first parameter of the procedure.

Action:  Ensure that the call to the procedure has a supported value for
the CID type parameter.

---------  

CHS0001: The Server service is not started.



Cause:    You must start the server and log on before you can
          run the CHGSRVR utility.

Action:   Start the server and log on as an administrator.


---------  

CHS0002: An administrator is not logged on at this workstation.



Cause:    An administrator must be logged on to change the server name.
          Because alias and user information must be retrieved and changed,
          only an administrator can change the server name.

Action:   Log on as an administrator.


---------  

CHS0003: An incorrect server name, ***, was specified.



Cause:    The name that you specified for a server name is not valid.
          A server name must consist of 1 to 15 nonblank characters, with
          the following restrictions:
          The name must not contain any of the following characters:
          " / \ [ ] : | < > + = ; , ? *

Action:   Verify that the specified server name contains valid characters.


---------  

CHS0005: This workstation is not the domain controller.



Cause:    You must run this program at the domain controller.

Action:   Run CHGSRVR at the domain controller.


---------  

CHS0006: The additional server whose name you are changing is not started.



Cause:    Before changing the name of an additional server, you must
          start the additional server.  This will allow replication
          of the appropriate user information to the additional server.
          Replication must occur for the additional server, or the server
          will not start with the new name.

Action:   Start the additional server.


---------  

CHS0008: An error occurred while adding the new server definition.



Cause:    The user accounts database could not be updated.

Action:   Restore NET.ACC from a backup and restart the CHGSRVR utility.
          If the problem persists, report the problem and the method
          by which it can be reproduced to your IBM support representative.


---------  

CHS0009: An error occurred while updating the user accounts database.



Cause:    The user accounts database may be damaged.

Action:   Restore NET.ACC from a backup and restart the CHGSRVR utility.
          If the problem persists, report the problem and the method
          by which it can be reproduced to your IBM support representative.


---------  

CHS0010: The server name that you specified does not exist.



Cause:    The server name that you specified to be changed does not exist
          in the domain control database.

Action:   Verify that you have specified the name correctly.


---------  

CHS0011: An error occurred while accessing the domain control database.



Cause:    The domain control database cannot be accessed.

Action:   Restore the domain control database from a backup and restart the
          CHGSRVR utility. If the problem persists, report the problem and
          the method by which it can be reproduced to your IBM support
          representative.


---------  

CHS0012: The Netlogon service is not started at server ***.



Cause:    The Netlogon service at the additional server must be started
          in order to receive the user changes.

Action:   Start the Netlogon service.


---------  

CHS0013: Replication of the server user information could not be confirmed.



Cause:    The user accounts database could not be replicated to the
          additional server.

Action:   Before stopping and restarting the server, verify that the
          new server name has been added as a USER and has been added
          to the group SERVERS.


---------  

CHS0015: An error occurred while updating the RPL.MAP file.



Cause:    The disk may be full.

Action:   Ensure that the drive where LAN Server is installed has some
          free disk space, and run the CHGSRVR utility again. If the problem
          persists, edit the RPL.MAP file and replace all occurrences
          of the old server name with the new server name.


---------  

CHS0016: An error occurred while updating the FIT file ***.



Cause:    The disk may be full.

Action:   Ensure that the drive where LAN Server is installed has some
          free disk space, and run the CHGSRVR utility again. If the problem
          persists, edit all of the FIT files referenced in the RPL.MAP
          file and replace all occurrences of the old server name with the
          new server name.


---------  

ETH0001: The IBM Ethernet adapter was either not found or not specified in the
PROTOCOL.INI file.

Cause:  There were either no entries found in the PROTOCOL.INI file for this
device driver, the adapter is not installed, or there is a hardware
problem with the adapter.

Action:  Ensure that an IBM Ethernet adapter is installed
in this system, and that a DRIVERNAME=  entry exists in the
PROTOCOL.INI file for the MACETH$ or MACETH2$ device driver.  Retry
the operation.  If the problem persists, contact your vendor service
representative.

---------  

ETH0003: Multiple IBM Ethernet adapter parameters were specified in the 
PROTOCOL.INI file.

Cause:  More than one entry was found in the PROTOCOL.INI file for
the MACETH$ or MACETH2$ device driver.

Action:  Ensure that DRIVERNAME entry appears only once in the
PROTOCOL.INI file.

---------  

FTD0001:  There is not enough memory for the Fault Tolerance driver
to build the internal structures.

Cause:  Too much memory has been requested for the requester
queues in the Fault Tolerance driver.
Action:  Decrease the MaxOS2Req or Max386Req parameter in the DISKFT line in
CONFIG.SYS.
The MaxOS2Req range is 32 to 255.  The default is 64.
The Max386Req range is 16 to 1024.  The default is 128.

---------  

FTD0002: Fault Tolerance could not attach to the disk device driver.

Cause:  The disk device driver may not be in the correct directory.
Action:  Verify that the disk driver is in the \OS2\BOOT directory and that 
the
file can be opened by the system.

---------  

FTD0003: Fault Tolerance received an incorrect response from the disk
device driver.

Cause:  The disk device driver may not support Fault Tolerance.
Action:  Verify that the disk device driver supports Fault Tolerance and
establishes communication with Fault Tolerance correctly.
Consult the support documentation for the disk driver.

---------  

FTD0004: The disk device driver does not support Fault Tolerance.

Cause: The disk driver did not establish communication with
Fault Tolerance.
Action:  The disk driver should be modified to establish
correct communication with Fault Tolerance.
Consult the support documentation for the disk driver.

---------  

FTD0005: The versions of the disk device driver and the
Fault Tolerance device driver are not compatible.

Cause: The disk device driver version is not correct.
Action:  Install compatible versions of the disk device driver and the
Fault Tolerance driver.
Consult the support documentation for the disk driver.

---------  

FTD0006: Fault Tolerance detected a disk device driver that is not valid .

Cause: The disk driver did not establish communication with
Fault Tolerance.
Action:  The disk driver should be modified to establish
correct communication with Fault Tolerance.
Consult the support documentation for the disk driver.

---------  

FTD0007: The disk partition limit of 128 entries was exceeded.

Cause:  Too many disk primary and secondary partitions have been
created.
Action:  Take the following steps when the limit of 128 partitions is 
exceeded:
1)  Determine which logical drives can be deleted.
2)  Copy files you want to save from drives to be deleted to drives that will
not be deleted.
3)  Using the LVM utility, delete the selected drives identified in step 1.
4)  Restart the system.

---------  

FTD0008: The Fault Tolerance system could not allocate global
descriptor table entries.

Cause:  Too much memory has been requested for the requester
queues in the Fault Tolerance driver.
Action:  Decrease the MaxOS2Req or Max386Req parameter in the DISKFT line in
CONFIG.SYS.

---------  

FTD0009:  Warning:  The Fault Tolerance driver failed to initialize.

Cause:  The Fault Tolerance driver was not loaded because of
a previous error that occurred.
Action:  Check the screen for an error message in the range of FTD0002E
to FTD0008E.  Perform the action specified for that error.

---------  

FTD0010: The Fault Tolerance driver encountered an error while parsing the
DEVICE=path\DISKFT.SYS command line in CONFIG.SYS.

Cause:  The DEVICE=DISKFT.SYS line in CONFIG.SYS contains a
syntax error, a misspelled word, or a number that is out of range.
Action:  The syntax of the DEVICE= line that loads the Fault Tolerance
driver is:
DEVICE=path\DISKFT.SYS /ReadPrim:d  /ReadPrimFirst:d
        /MaxOS2Req:nnn  /Max386Req:nnn

/ReadPrim:d      Forces all reads to be satisfied from the primary partition.
                 If the drive letter is omitted, all mirrored drives are
                 implied.

/ReadPrimFirst:d Forces all reads to be satisfied from the primary partition
                 first; the secondary may be attempted if any error condition
                 occurs.  If the drive letter is omitted, all drives are
                 implied.

/MaxOS2Req:nnnn  Sets the maximum number of OS/2 requests outstanding at a
                 time in the Fault Tolerance and disk drivers.  The
                 maximum allowable value is 255;  the minimum allowable value
                 is 32; the default value is 64.

/Max386Req:nnnn  Sets the maximum number of 386 HPFS requests outstanding at
                 a time in the Fault Tolerance and disk drivers.  The
                 maximum allowable value is 1024;  the minimum allowable value
                 is 16; the default value is 128.

You cannot specify /ReadPrim and /ReadPrimFirst for the same drive
(or all drives) on the same command line.  If you attempt to do so, the
last entry on the command line takes precedence.


---------  

FTD0052: The Fault Tolerance device driver could not be opened.


Cause: DISKFT.SYS is not active or is not responding correctly.
This may be caused by missing statements in CONFIG.SYS or by a
version of DISKFT.SYS that is not valid.
Action: Run FTSETUP to install the necessary statements in CONFIG.SYS.
Then shut down the workstation and restart it.  If the problem persists,
install Fault Tolerance again.

---------  

FTD0053: There is not enough memory to create \\SHARMEM\\FTMONIT.


Cause: FTMONIT cannot obtain memory for some of its data structures.
Action: Check the MEMMAN statement in CONFIG.SYS to make sure that
memory swapping has been enabled.  Then shut down the workstation
and restart it.

---------  

FTD0054: Incorrect options have been used to start FTMONIT.

Valid options for FTMONIT are:
/Alert:[Yes]|[No]
    Specifies whether alerts are to be sent to users specified by the
    alertnames parameter in the Server section of IBMLAN.INI.
    /Alert:Yes is the default.

/Compare:[Yes]|[No]
    Specifies whether to do a low-confidence comparison at startup.
    This parameter is ignored if FTMONIT has already been started.
    /Compare:Yes is the default.

/Quiet:[Yes]|[No]
    Prevents the display of messages on the screen. This option is ignored
    when starting FTMONIT from CONFIG.SYS (no message is ever displayed
    in this case).  /Quiet:No is the default.

/Clear:[Yes]|[No]
    Clears all statistics counters maintained by the Fault Tolerance driver.
    /Clear:No is the default.

/Verify:[Yes]|[No][Confirm]
    Specifies whether FTMONIT should attempt to do required drive Verifies.
    /Verify:Confirm allows verify to be run even when a drive is locked.
    This parameter is ignored if FTMONIT has already been started.
    /Verify:Yes is the default.

---------  

FTD0059: The file FT.DLL could not be found.


Cause: FT.DLL is required for Fault Tolerance support.
Action: Make sure \IBMLAN\NETLIB\FT.DLL has been installed.

---------  

FTD0101: Fault Tolerance error 001 has occurred:
A write to the primary partition failed.
A write to the alternate partition succeeded.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0102: Fault Tolerance error 002 has occurred:
A write to the primary partition succeeded.
A write to the alternate partition failed.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0103: Fault Tolerance error 003 has occurred:
A read from the primary partition failed.
A read was recovered from the secondary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0104: Fault Tolerance error 004 has occurred:
A read from the secondary partition failed.
A read was recovered from the primary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0105: Fault Tolerance error 005 has occurred:
A write to the primary partition and the secondary partition failed.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0106: Fault Tolerance error 006 has occurred:
A write to a non-mirrored drive failed.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0107: Fault Tolerance error 101 has occurred:
A read from a non-mirrored drive failed.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0108: Fault Tolerance error 102 has occurred:
A read from the primary partition and the secondary partition failed.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0109: Fault Tolerance error 103 has occurred:
An excessive failure rate was detected on the primary partition of a drive.
Read requests will be routed to the secondary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0110: Fault Tolerance error 104 has occurred:
An excessive failure rate was detected on the secondary partition of a drive.
Read requests will be routed to the primary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0111: Fault Tolerance error 105 has occurred:
The primary partition of a drive was shut down because of complete failure.
All requests will be routed to the secondary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0112: Fault Tolerance error 106 has occurred:
The secondary partition of a drive was shut down because of complete failure.
All requests will be routed to the primary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0113: Fault Tolerance error 107 has occurred:
A low-confidence comparison of mirrored partitions for a drive failed.
All read requests will be routed to the primary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0114: Fault Tolerance error 108 has occurred:
A complete comparison of mirrored partitions failed.  All read
requests will be routed to the primary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0115: Fault Tolerance error 109 has occurred:
A low-confidence comparison of mirrored partitions for a drive failed.
All read requests will be routed to the secondary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0116: Fault Tolerance critical error 201 has occurred:
An excessive error rate was detected on a non-mirrored drive.
An alternate partition is not available.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0117: Fault Tolerance critical error 202 has occurred:
A complete failure was detected on a drive. An alternate partition
is not available.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0118: Fault Tolerance critical error 209 has occurred:
The secondary partition of a mirrored drive was not found.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0119: Fault Tolerance critical error 210 has occurred:
A secondary partition with no matching primary was found.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0120: Fault Tolerance critical error 211 has occurred:
Error logging has been interrupted.  One or more errors may have been lost.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0121: Fault Tolerance critical error 212 has occurred:
Error logging was not completed.  One or more errors may not have been
logged for the following drives:


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0122: Fault Tolerance error 110 has occurred:
Configuration information cannot be saved.  The C: drive has been unmirrored.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0123: Fault Tolerance error 111 has occured:
A critical sector in the primary partition has been damaged.
Read requests will be routed to the secondary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.

---------  

FTD0124: Fault Tolerance error 112 has occured:
A critical sector in the secondary partition has been damaged.
Read requests will be routed to the primary partition.


Cause: An error has been logged by Fault Tolerance.
Action: Run FTADMIN to correct the error.


---------  

HFS0003: The /Cache syntax is not valid.



Cause:   The /Cache syntax in the 386 HPFS IFS line in the
         CONFIG.SYS file is not valid.

Action:  The format of the Cache parameter is /Cache:nnnn, where
         nnnn is a decimal number that represents kilobytes.
         Correct the Cache parameter in the 386 HPFS IFS line in
         the CONFIG.SYS file.  The specified cache size will be
         used the next time the machine is started.  Until then,
         the cache size is 20% of available memory.



---------  

HFS0004: The /Heap syntax is not valid.



Cause:   The /Heap syntax in the 386 HPFS IFS line in the
         CONFIG.SYS file is not valid.

Action:  The format of the Heap parameter is /Heap:nnnn, where
         nnnn is a decimal number that represents kilobytes.
         Correct the Heap parameter in the 386 HPFS IFS line in
         the CONFIG.SYS file.  The specified heap size will be
         used the next time the machine is started.  Until then,
         the maximum heap size is limited by available memory.



---------  

HFS0005: The /I syntax is not valid.



Cause:   The /I syntax in the 386 HPFS IFS line in the CONFIG.SYS
         file is not valid.

Action:  The format of the /I parameter is /I:{path}, where
         {path} is the path where you installed OS/2 LAN
         Server.  Correct the /I parameter in the 386 HPFS IFS
         line in the CONFIG.SYS file.  The specified path
         will be used the next time the machine is started.
         Until then, the 386 HPFS assumes your LAN root directory
         is C:\IBMLAN.



---------  

HFS0006: The /Autocheck syntax is not valid.



Cause:   The /Autocheck syntax in the 386 HPFS IFS line in the
         CONFIG.SYS file is not valid.

Action:  The format of the Autocheck parameter is
         /Autocheck:{drivelist}, where {drivelist} is a list of
         your 386 HPFS drives; for example, /Autocheck:cde.
         Correct the Autocheck parameter in the 386 HPFS IFS line
         in the CONFIG.SYS file.  The list of autocheck drives
         will be checked the next time the machine is started.
         Until then, only the 386 HPFS boot drive (if one exists)
         will be checked.



---------  

HFS0007: A drive letter on /Autocheck that is not valid has
          been ignored.



Cause:   A drive letter in /Autocheck that is not valid has been
         ignored.

Action:  The format of the Autocheck parameter is
         /Autocheck:{drivelist}, where {drivelist} is a list of
         your 386 HPFS drives; for example, /Autocheck:cde.  Valid
         characters for {drivelist} are the letters A-Z (or a-z).
         The character that is not valid has been ignored.
         Correct the Autocheck parameter in the 386 HPFS IFS line
         in the CONFIG.SYS file.  The valid drive letters have
         been autochecked.


---------  

HFS0010: The cache size specified is too small.
          The minimum size of 256KB will be used.



Cause:   The cache size specified for the 386 HPFS is too small.
         The minimum size of 256KB will be used.

Action:  Change the CACHESIZE parameter in the 386 HPFS INI file
         to be 256KB or more.  The default INI file is
         \IBM386FS\HPFS386.INI on the boot drive.  Start your
         machine again to make the new cache size go into effect.


---------  

HFS0011: The cache size specified is too large.
          50% of available memory will be used.



Cause:   The cache size specified for the 386 HPFS is too large.
         A default of 50% of available memory will be used.

Action:  Change the CACHESIZE parameter in the 386 HPFS INI file
         to a value less than what it currently is.  The default
         INI file is \IBM386FS\HPFS386.INI on the boot drive.
         Start your machine again to make the new cache size go
         into effect.


---------  

HFS0012: The cache size specified is too large.
          20% of available memory will be used.



Cause:   The cache size specified for the 386 HPFS is too large.
         A default of 20% of available memory will be used.

Action:  Change the CACHESIZE parameter in the 386 HPFS INI file
         to a value less than what it currently is.  The default
         INI file is \IBM386FS\HPFS386.INI on the boot drive.
         Start your machine again to make the new cache size go
         into effect.


---------  

HFS0013: The heap size specified is too large.
          The maximum size of 64KB will be used.



Cause:   The heap limit size specified for the 386 HPFS is too large.
         A heap limit size of 64KB will be used.

Action:  Change the MAXHEAP parameter in the 386 HPFS INI file to
         a value less than what it currently is.  The default INI
         file is \IBM386FS\HPFS386.INI on the boot drive.  Start
         your machine again to make the new heap limit size go
         into effect.


---------  

HFS0014: The heap size specified is too small.
          The minimum size of 64KB will be used.



Cause:   The heap limit size specified for the 386 HPFS is too
         small.  A heap limit size of 64KB will be used.

Action:  Change the MAXHEAP parameter in the 386 HPFS INI file to
         be 64KB or larger.  The default INI file is
         \IBM386FS\HPFS386.INI on the boot drive.  Start your
         machine again to make the new heap limit size go into
         effect.


---------  

HFS0019: There is not enough memory for the 386 HPFS cache and
          heap.



Cause:   There is not enough memory for both the 386 HPFS cache
         and the heap.

Action:  You can reduce the amount of memory being used by your
         system.  To do this:

         -  Change the amount of memory you have configured for
            your device drivers to use.

         -  Do not use device drivers that consume large amounts
            of memory.

         You can also add more memory to your machine.

         Start your machine again after you have obtained more
         memory or reduced the amount of memory being used.



---------  

HFS0022: An option that is not valid is on HPFS386.IFS line:
          ***



Cause:   An option that is not valid exists in the 386 HPFS IFS
         line in the CONFIG.SYS file.

Action:  The option displayed in the error message was found in
         the 386 HPFS IFS line in the CONFIG.SYS file, but it is
         not a valid 386 HPFS option.  It has been ignored.
         Remove the option from the 386 HPFS IFS line in the
         CONFIG.SYS file.


---------  

HFS0026: The /RUNCHKDSK syntax in the 386 HPFS IFS line in the
          CONFIG.SYS file is not valid.


Cause:    You entered information for the /RUNCHKDSK parameter
          incorrectly.  The format of the /RUNCHKDSK parameter is:

            /RUNCHKDSK=nnn

          where nnn is a decimal number that is greater than 0.  This
          is the number of times CHKDSK /F will run on those drives
          that are specified by the /AUTOCHECK parameter.  CHKDSK /F
          will be run once even if this parameter is syntactically
          incorrect or if it is not present on the 386 HPFS IFS line.

Action:   Correct the parameter and restart the workstation.


---------  

HFS0027: HPFS386 cannot AUTOCHECK drive *** because of the
          following error code: ***.  Reboot from a diskette and
          run CHKDSK /F.


Cause:   HPFS386 could not access the target drive to determine
         if it should run CHKDSK /F on it.

Action:  Boot from a diskette and run CHKDSK /F against the drive.


---------  

HFS0030: HPFS386 could not open the initialization file ***.
The return code was ***.



Cause:   HPFS386 could not open its initialization file.  The default file
         name is \IBM386FS\HPFS386.INI on the boot drive.  The
         initialization file name or path can be changed by specifying a new
         file name or path on the IFS= line which loads HPFS386 in
         CONFIG.SYS.  HPFS386 tries to open the initialization file in two
         different ways.  First it assumes it was given an entire file name
         on the IFS= line.  If this open fails, it then assumes that only a
         path was given.  It appends \HPFS386.INI to the path and tries to
         open the file.  Both of these opens failed.

Action:  Check the IFS= line which loads HPFS386 in CONFIG.SYS and see if a
         path or file name was specified.  If not, run OS/2 LAN Services
         Installation/Configuration, choose the advanced path, and
         reconfigure the HPFS386 file system.

         If a path or file name was specified, verify that the path or file
         name was spelled correctly.  If the spelling is correct, run OS/2
         LAN Services Installation/Configuration, choose the advanced path,
         and reconfigure the HPFS386 file system.


---------  

HFS0032: An option that is not valid is on HPFS386.IFS line:  ***
This option has been moved to the HPFS386 initialization file.
The option was ignored.



Cause:   A parameter that is not valid was specified on the IFS= line which
         loads HPFS386 in CONFIG.SYS.  The parameter is now specified in the
         initialization file instead of on the IFS= line.

Action:  Remove the parameter from the IFS= line in CONFIG.SYS.  If you want
         to specify a new value for this parameter, do so in the HPFS386
         initialization file.  The default name and location of the file is
         \IBM386FS\HPFS386.INI on the boot drive.  The path and/or file name
         can be changed by specifying the new path or file name on the IFS=
         line.  Check the IFS= line to see if the path or file name has been
         changed.  Make your changes to the file specified on the IFS= line.


---------  

HFS0033: The file *** contains a parameter that is not valid:  ***
The parameter was ignored.



Cause:   A parameter that is not valid was specified in the HPFS386
         initialization file.  The error message lists the name of the
         initialization file and the parameter.

Action:  Verify that the parameter is valid.  If the parameter is not valid,
         change it to a valid parameter or remove the line with the
         parameter from the initialization file.


---------  

HFS0034: The value given for the parameter *** in the file
*** is not valid.  The parameter was ignored.



Cause:   The HPFS386 initialization file contains a parameter value that is
         not valid.  The error message lists the name of the initialization
         file and the parameter that has the bad value.

Action:  Verify that the value is valid.  If the value is not valid, change
         it to a valid value or remove the line with the parameter from the
         initialization file.


---------  

HFS0035: The drive letter "***" given for the *** parameter in the file
*** is not valid and has been ignored.



Cause:   A drive letter was given for a parameter value in the HPFS386
         initialization file.  The letter is not a valid drive letter.
         Valid drive letters are 'A' through 'Z' and '*', which means the
         value applies to all drives.  The error message lists the name of
         the initialization file and the parameter that has the bad drive
         letter.

Action:  Delete the character from the list of drives in the parameter
         value.


---------  

HFS0036: The parameter *** in the file *** does not appear within a component 
group.
The parameter was ignored.



Cause:   The HPFS386 initialization file contains an improperly placed
         parameter.  The parameter appears before the first definition of
         a component group.  Component groups start with a line that has
         a name enclosed in square brackets.  For example:

         [filesystem]

         All parameters must appear within a component group definition.
         The error message lists the name of the initialization file and
         the parameter that is in error.

Action:  Verify that the parameter is valid.  If the parameter is valid,
         move the parameter statement to the correct component group.
         Then, shut down and restart your workstation.  If it is not valid,
         remove the parameter statement from the initialization file.


---------  

HFS0051: MMUTIL cannot access drive ***.



Cause:   The drive may be locked or in use by another process, or 386 HPFS
         is not installed.

Action:  Verify that 386 HPFS is installed and is active.
         Either stop all processes that are accessing this drive,
         or boot with a 386 HPFS boot diskette and run MMUTIL again
         to remove the multimedia format from the drive.


---------  

HFS0052: Critical sector *** cannot be read.



Cause:   A disk error occurred while trying to read in the critical sector
         indicated.

Action:  The HPFS format relies on sectors 16 and 17 to store drive layout
         information for the drive.  If sectors 16 and 17 cannot be accessed,
         no information is available on the drive.  Run MMUTIL again.  If
         the error still occurs, run diagnostics on the physical disk
         containing the drive.


---------  

HFS0053: Critical sector *** is not valid.



Cause:   The information read from the indicated sector was not valid.

Action:  The HPFS format relies on sectors 16 and 17 to store drive layout
         information for the drive.  Sectors 16 and 17 do not contain valid
         HPFS data.  Verify that the drive you are trying to remove the
         multimedia format from is an HPFS drive.  If the drive is formatted
         as HPFS, run CHKDSK to verify that the disk is correct.

---------  

HFS0055: Critical sector *** cannot be written.



Cause:   A disk error occurred while trying to write critical sector
         information.

Action:  The HPFS format relies on sectors 16 and 17 to store drive layout
         information for the drive.  If sectors 16 and 17 cannot be written,
         the multimedia format cannot be removed.  Run MMUTIL again.
         If the error still occurs, run diagnostics on the physical disk
         containing the drive.


---------  

HFS0056: The multimedia feature could not be removed from this drive.



Cause:   A disk error prevented the multimedia format from being removed.

Action:  You can continue to use the drive in the current multimedia format.
         No information on the disk has been updated.


---------  

HFS0057: The disk may be inconsistent.



Cause:   A disk error prevented the multimedia format from being removed.

Action:  The HPFS format relies on sectors 16 and 17 to store drive layout
         information for the drive.  Only sector 16 could be written
         successfully.  The drive may be in an inconsistent state.  Run
         CHKDSK to verify that your drive is correct.


---------  

HFS0058: A parameter *** that was specified is not valid.



Cause:  One of the parameters specified on the command line is not a valid
        parameter for MMUTIL.


Action: Verify that the parameters are specified correctly.


---------  

HFS0060: The multimedia format could not be applied.



Cause:  The write of a critical sector prevented an upgrade of the drive
        to the multimedia format.

Action: Try the operation again.  Repeated failures may indicate problems
        with the existing disk sectors.  Back up the files from the current
        drive.  Reformat the drive with the desired attributes, and restore
        the backed-up files to the drive.


---------  

HFS0061: PROFILER could not be run because of OS/2 error ***.



Cause:  MMUTIL must run PROFILER when applying the multimedia format to a 
drive.
        MMUTIL could not start the PROFILER utility because of the 
error
        specified.

Action: The error number specified is an OS/2 error number.  You can obtain
        more help on that particular error by typing HELP SYSxx, where xx
        is the error number listed in the original error.


---------  

HFS0062: Files that do not meet the multimedia format requirements remain
on the drive. The multimedia format has not been applied.



Cause:  PROFILER was run, and it detected files that did not meet the
        multimedia format requirements.  PROFILER could not correct the
        problems associated with these files.

Action: You must correct the files that PROFILER listed as not meeting the
        requirements. To correct the files, back up the current version of
        the file.  Delete the current version.  Apply the multimedia format
        to the drive.  Then restore the backed-up version. The new version
        will be created with the proper requirements.



---------  

HFS0066: File *** was not processed because of OS/2 error ***.



Cause:  The file listed could not be examined by the PROFILER utility.

Action: The error number specified is an OS/2 error number.  You can obtain
        more help on that particular error by typing HELP SYSxx, where xx
        is the error number listed in the original error.


---------  

HFS0076: An attempt to copy file *** to file *** failed with OS/2 error ***.



Cause:  The PROFILER utility attempts to create a backup file named
        PROFILER.TMP.001 in the same directory as the file it is trying
        to correct.  The PROFILER utility could not make a copy of
        the file being corrected.

Action: The error number specified is an OS/2 error number.  You can obtain
        more help on that particular error by typing HELP SYSxx, where xx
        is the error number listed in the original error.


---------  

HFS0077: An attempt to delete file *** failed with OS/2 error ***.



Cause:  The PROFILER utility could not delete the file listed in the
        original error message.  The PROFILER utility attempts to delete
        the original file after making a copy of that file.  The PROFILER
        attempts to delete the PROFILER.TMP.001 file in case errors
        occur after copying, but before deleting, the original file.

Action: The error number specified is an OS/2 error number.  You can obtain
        more help on that particular error by typing HELP SYSxx, where xx
        is the error number listed in the original error.


---------  

HFS0078: An attempt to rename file *** to file *** failed with OS/2 error ***.



Cause:  The PROFILER utility could not rename the PROFILER.TMP.001 file
        to the original file name.

Action: The error number specified is an OS/2 error number.  You can obtain
        more help on that particular error by typing HELP SYSxx, where xx
        is the error number listed in the original error.


---------  

HFS0079: An attempt to retrieve the access control information of file ***
failed with LAN Server error ***.



Cause:  The PROFILER utility attempts to maintain the access control
        present on the original file.  The NetAccessGetInfo API call used
        to obtain the access control information for the file listed
        failed because of the LAN Server error listed.

Action: The error number specified is a LAN Server error number.
        You can obtain more help on that particular error by typing
        HELP NETxx, where xx is the error number listed in the
        original error.  Failure to obtain the access control
        information prevents the file from being corrected.  You must
        manually correct the file if this is being done as part of the
        multimedia format application.


---------  

HFS0080: An attempt to set the access control information on file ***
failed with LAN Server error ***.



Cause:  The PROFILER utility attempts to maintain the access control
        present on the original file.  The NetAccessSetInfo API call used
        to set the access control information for the file listed
        failed because of the LAN Server error listed.

Action: The error number specified is a LAN Server error number.
        You can obtain more help on that particular error by typing
        HELP NETxx, where xx is the error number listed in the original
        error.  The new version of the file is no longer protected by
        the original access control.  You must reset the access control
        profile that originally existed on this file.


---------  

HFS0081: An attempt to change the attributes on file *** failed with OS/2 
error ***.



Cause:  The PROFILER utility was attempting to correct a file that had a
        read-only attribute.  PROFILER removes the attribute before
        doing the correction and replaces it afterward.  The read-only
        file attribute could not be changed by the PROFILER utility.

Action: The error number specified is an OS/2 error number.  You can obtain
        more help on that particular error by typing HELP SYSxx, where xx
        is the error number listed in the original error.

        If the error occurred before attempting to correct the file,
        the file has not been corrected and must manually be corrected.
        If the error occurred after correcting the file, the file
        no longer has the original read-only file attribute.  Run PROFILER
        again, specifying the file name that was being corrected, to check
        whether the file has been corrected or not.


---------  

HFS0101: A disk error has been found on a 386 HPFS volume
on drive ***.



Cause:   The disk driver reported an error reading or writing
         to the disk.

Action:  Shut down the system, start the computer again, and run
         CHKDSK /F on the disk.



---------  

HFS0102: A 386 HPFS volume on drive *** is dirty. You must
clean the file system with CHKDSK /F before you can use it.



Cause:   The system was not shut down properly.

Action:  Run CHKDSK /F on the disk, or add the disk-drive letter
         to the /Autocheck list in the IFS line in the CONFIG.SYS
         file and start the computer again.



---------  

HFS0103: A 386 HPFS volume on drive *** was not mounted because
of a shortage of memory.



Cause:   Either the 386 HPFS could not find space in the internal
         memory heap, or the 386 HPFS could not allocate more
         memory from the system to increase the memory heap.

Action:  You can increase the maximum amount of memory the 386 HPFS
         uses and the amount it preallocates by specifying the
         MAXHEAP parameter in the 386 HPFS INI file.  The default
         INI file is \IBM386FS\HPFS386.INI on the boot drive.
         You can also reduce the amount of memory used in other
         areas of the system (for example, reduce the cache size
         or run fewer applications), or you can add more memory
         to the computer.



---------  

HFS0104: A defective sector on drive *** has been replaced
(hotfixed). No data was lost. Run CHKDSK /F to restore
performance.



Cause:   The 386 HPFS received an error from the disk driver
         while attempting to access a disk sector.

Action:  Run CHKDSK /F soon to restore full performance and
         to replenish the spare sector pool for the volume.



---------  

HFS0105: A 386 HPFS volume on drive *** cannot be mounted
because of a shortage of memory.



Cause:   Either the 386 HPFS could not find space in its internal
         memory heap, or the 386 HPFS could not allocate more
         memory from the system to increase the memory heap.

Action:  You can increase the maximum amount of memory the 386 HPFS
         uses and the amount it preallocates by specifying the
         MAXHEAP parameter in the 386 HPFS INI file.  The default
         INI file is \IBM386FS\HPFS386.INI on the boot drive.
         You can also reduce the amount of memory used by other
         parts of the system (for example, reduce the cache size
         or run fewer applications), or you can add more memory
         to the computer.


---------  

HFS0106: The 386 HPFS volume on drive *** detected severe
media errors.  The system has taken corrective measures.
Back up the volume before you restart the machine.  Run
CHKDSK /F after the machine is restarted.



Cause:   The 386 HPFS could not access a critical sector on a 386 HPFS
         volume.  Although corrective measures were taken to maintain
         normal operation, the volume may not be accessible once you
         restart the machine.

Action:  Back up all files and access control profiles on this volume
         before turning off the machine. You can use the BACKUP, XCOPY,
         and BACKACC utilities to do this. CHKDSK and FORMAT will be
         denied access to the volume until the machine is restarted.
         Run CHKDSK /F after you restart the machine.


---------  

HFS0107: The 386 HPFS volume on drive *** is unable to
replace a defective sector because of a shortage of
hotfix sectors.  Lazy-writing is now disabled.
Run CHKDSK /F to restore performance.



Cause:   While attempting to hotfix a defective sector, the 386 HPFS
         discovered that the volume had no free hotfix sectors left.

Action:  Run CHKDSK /F to allocate new hotfix sectors and restore
         performance.


---------  

HFS0108: The 386 HPFS volume on drive *** detected severe
media errors.  Try to back up the volume immediately.
Run CHKDSK /F once the machine is restarted.



Cause:   The 386 HPFS could not access a critical sector on a 386 HPFS
         volume.  The volume may not be accessible following a restart
         of the machine.

Action:  Try to back up all files and access control profiles on this
         volume.  You can use the BACKUP, XCOPY, and BACKACC utilities
         to do this.  CHKDSK and FORMAT will be denied access to the
         volume until the machine is restarted.  Run CHKDSK /F after
         you restart the machine.


---------  

HFS0109: The disk device driver for the 386 HPFS volume on
drive *** does not support memory above 16MB.  The volume was
mounted for DASD access only.



Cause:   The disk device driver for this volume does not support
         memory above 16MB.

Action:  Set the USEALLMEM parameter in the 386 HPFS INI file to NO.
         The default INI file is \IBM386FS\HPFS386.INI on the boot
         drive.  Start your machine again to make the change go into
         effect.


---------  

HFS0110: The 386 HPFS server failed to enable directory limits on
drive *** because of insufficient heap space.  The drive is
still operational.



Cause:   The 386 HPFS server did not enable directory limits on
         the drive because it could not obtain space from its own
         memory heap, or the 386 HPFS could not allocate more
         memory from the system to increase the memory heap.  The
         volume is still operational.

Action:  You can increase the maximum amount of memory the 386
         HPFS uses and the amount it preallocates by modifying
         the MAXHEAP parameter in the HPFS 386 INI file and
         restarting the workstation.  You can also reduce the
         amount of memory used by other parts of the system (for
         example, reduce the cache size or run fewer
         applications), or you can add more memory to the
         computer.



---------  

HFS0111: The 386 HPFS server failed to enable directory limits
on drive *** because of a disk error.  The drive is still
operational.



Cause:   The 386 HPFS server did not enable directory limits on
         the drive because it encountered a disk error during a
         read operation.  The volume is still operational.

Action:  Run CHKDSK /F on the volume.  If the failure occurred while
         you were installing directory limits, then retry the
         installation command.  Otherwise, refresh the DASD
         information using the following command:

              NET DASD drive /REFRESH


---------  

HFS0112: This version of the 386 HPFS server does not
support some of the HPFS extensions contained on drive ***.
The volume was mounted for DASD access only.



Cause:   The 386 HPFS server could not mount the volume because
         the volume's format contains extensions that are not
         supported by this version of the file system.  This
         error can occur if a downlevel version of the file
         system is used.

Action:  Ensure that the proper version of the file system,
         HPFS386.IFS, is used.


---------  

HFS0113: The 386 HPFS volume on drive *** is locked by another process.
No file operation can proceed until the drive is unlocked.



Cause:  Another process has locked the drive.  Consequently, file
        operations cannot proceed.

Action: Wait until the drive is unlocked.


---------  

HFS0200: An unrecoverable error has occurred.



Cause:   The 386 HPFS received a bad-command error from the disk
         driver that was possibly caused by memory damage.
         Rather than risk further damage to the data on the disk,
         the 386 HPFS has stopped the system so that the problem can
         be corrected.

Action:  Start the computer again and run CHKDSK /F on your
         386 HPFS disks.  Ensure that your disk driver is
         compatible with other system software.  Run diagnostics
         on the system memory.


---------  

HFS0201: An unrecoverable error has occurred.



Cause:   The 386 HPFS ran out of space on the disk for directory
         structures and has used up all of the directory
         structures set aside for emergency use.

Action:  Start the computer again and run CHKDSK /F on your
         386 HPFS disks.  Archive and delete any unneeded files to
         free space on the disks.


---------  

HFS0202: An unrecoverable error has occurred.



Cause:   The 386 HPFS was unable to read a critical file-system
         structure from the disk.  The 386 HPFS cannot continue
         without this structure.

Action:  Start the computer again and run CHKDSK /F on your
         386 HPFS disks.  Run diagnostics on the disks to locate
         and mark the faulty sectors.  If the problem persists,
         you may have faulty hardware.



---------  

HFS0203: An unrecoverable error has occurred.



Cause:   The 386 HPFS was unable to read a critical file-system
         structure from the disk.  The 386 HPFS cannot continue
         without this structure.

Action:  Start the computer again and run CHKDSK /F on your
         386 HPFS disks.  Run diagnostics on the disks to locate
         and mark the faulty sectors.  If the problem persists,
         you may have faulty hardware.


---------  

HFS0204: An unrecoverable error has occurred.



Cause:   The 386 HPFS was not able to write a critical file-system
         structure to the disk.  Rather than risk further loss of
         data or disk damage, the 386 HPFS has stopped further
         attempts at using the volume.

Action:  Start the computer again and run CHKDSK /F on the
         disk.  Run diagnostics on the disk to locate and mark
         the faulty sectors.  If the problem persists, you may
         have faulty hardware.



---------  

HFS0205: An unrecoverable error has occurred.



Cause:   The 386 HPFS was not able to find space in its internal
         memory heap and was not able to allocate more memory
         from the system to increase the memory heap.

Action:  Start the computer again and run CHKDSK /F on your
         386 HPFS disks.  You can increase the maximum amount of
         heap the 386 HPFS uses and the amount it preallocates by
         specifying the MAXHEAP parameter in the 386 HPFS INI
         file.  The default INI file is \IBM386FS\HPFS386.INI on
         the boot drive.  You can also reduce the amount of
         memory used in other areas of the system (for example,
         reduce the cache size or run fewer applications), or you
         can add more memory to the computer.



---------  

HFS0207: An unrecoverable error has occurred.



Cause:   The 386 HPFS received an error from the disk driver while
         writing to the swapper file after the file system was
         already flushed.

Action:  No action is necessary.  The volume was already flushed,
         so no data should have been lost.



---------  

HFS0208: An unrecoverable error has occurred.



Cause:   The 386 HPFS was unable to reopen a file opened by the
         minifile system driver at boot time.  You may have
         system software that is mismatched.

Action:  Ensure that the version of the HPFS you have is compatible
         with the version of the operating system you are
         running.



---------  

HFS0209: An unrecoverable error has occurred.



Cause:   The 386 HPFS ran out of reserved hotfix sectors on the
         disk.  Rather than risk further loss of data or disk
         damage, the 386 HPFS has stopped further attempts at
         using the volume.

Action:  Start the computer again and run CHKDSK /F on your
         386 HPFS disks.  Run diagnostics on the disks to locate
         and mark faulty sectors.  If the problem persists, you
         may have faulty hardware.

---------  

HFS0302: The following file is missing:
             ***



Cause:   The listed file is not in the specified path.

Action:  In order to make a 386 HPFS boot diskette with the
         MAKEDISK utility, you must have the listed file in the
         specified path.  Ensure that the listed file is in the
         specified directory and that you have the proper access
         to the listed file.  Then run the utility again.


---------  

HFS0319: OS/2 error *** occurred while deleting the following file:
             ***



Cause:   The listed OS/2 error occurred while deleting the listed
         file from the diskette.

Action:  To get more information about the OS/2 error, type:

         HELP message#

         where message# is the error code.

         Be sure that you have a backup copy of the original OS/2
         2.0 Diskette 1 diskette, and then run the utility again.


---------  

HFS0320: OS/2 error *** occurred while copying the following file
         to drive ***:
             ***



Cause:   The listed OS/2 error occurred while copying the listed
         file from the boot drive of your workstation to the diskette.

Action:  To get more information about the OS/2 error, type:

         HELP message#

         where message# is the error code.

         Be sure that you have a backup copy of the original OS/2
         2.0 Diskette 1 diskette, and then run the utility again.


---------  

HFS0321: Errors occurred while making the boot diskette.



Cause:   The MAKEDISK utility did not work correctly because
         of the errors indicated by previous error messages.

Action:  Fix the problems indicated by the previous error messages.
         Be sure that you have a backup copy of the original OS/2
         2.0 Diskette 1 diskette, and then run the utility again.


---------  

HFS0322: An error occurred while creating the following file:
             ***



Cause:   The MAKEDISK utility encountered an error while
         creating the listed file.

Action:  Do one or more of the following:

         - Fix any problem indicated by previous error messages.
             - Ensure that you have the original MAKEDISK.CFG file on
           the hard disk.
             - Ensure that the listed file is not write-protected.
             - Ensure that you have access to the hard disk.

         Ensure that you have a backup copy of the original OS/2
         2.0 Diskette 1 diskette, and then run the utility again.


---------  

HFS0323: The command line contains a parameter that is not valid.



Cause:   You have specified an incorrect parameter for the
         MAKEDISK utility.

Action:  Check the spelling of the parameter.  The valid
         parameters for MAKEDISK are as follows:

             /BOOTDRIVE:d      d is the boot drive for the
                               OS/2 program.  /BOOTDRIVE can change
                               the drive letter from which files
                               are copied to the bootable diskette.

             /FT               Updates the Fault Tolerance
                               configuration file on an already
                               created bootable diskette

         The parameters can be abbreviated by using the first
         letter.  Only one parameter can be used at a time.


---------  

HFS0324:  The Fault Tolerance configuration for this machine has
been copied to your bootable 386 HPFS diskettes.  These diskettes
should be used only on this machine.




Cause:  The Fault Tolerance configuration for this machine is
        specific to this machine.  This configuration has been copied to
        your 386 HPFS bootable diskettes.

Action: When any changes are made to the disk configuration of
        this machine, either by adding new partitions, changing partition
        sizes, or changing the mirroring state of any drives, then the
        Fault Tolerance configuration for the 386 HPFS bootable diskettes
        for this machine needs to be updated.  Use MAKEDISK /FT to update
        the bootable diskettes.


---------  

HFS0325:  The Fault Tolerance configuration file (C:\FTCFG.SYS) for
this machine cannot be located.



Cause:  Either Fault Tolerance is not activated or the file may be
        inaccessible.

Action: If Fault Tolerance is not activated, the bootable diskettes
        do not need updating with the Fault Tolerance configuration file.
        If Fault Tolerance is activated, verify that the Fault Tolerance
        configuration file (C:\FTCFG.SYS) can be located, and run
        MAKEDISK /FT again.  C:\FTCFG.SYS is a file with hidden and system
        attributes.  Use attrib -h -s C:\FTCFG.SYS to unhide the file.


---------  

LSI0001: The operating system must be OS/2 2.1 or above.

Cause:   The version of the base operating system currently
         installed is not compatible with the version of LAN Services being
         installed.

Action:  Install OS/2 2.1 or above and then reinstall LAN Services.

---------  

LSI0002: The Lan Services installation/configuration program is already 
running.

Cause:   The LAN Services installation/configuration program is
         already running.  You cannot start the installation/configuration
         program again at this time.

Action:  Run only one copy of the LAN Services installation/configuration
         program at a time.

---------  

LSI0003: There is not enough space on any hard disk.

Cause:   The LAN Services installation/configuration program is
         unable to continue because there is not enough hard-disk space on
         this workstation.

Action:  Make hard-disk space available on this workstation by moving or
         deleting files, and then try the installation again.

---------  

LSI0004: *** is missing, damaged, or cannot be copied to the hard disk.

Cause:   The LAN Services installation/configuration program is
         unable to open or read this required file, or you have not logged
         on with sufficient privilege to allow this required file to be
         copied.

Action:  Make a new copy of the product diskettes and try the installation
         again, or log on with sufficient privilege and then try the
         installation again.

---------  

LSI0005: *** failed to load.

Cause:   The LAN Services installation/configuration program is
         unable to load this dynamic link library (DLL).

Action:  Make a new copy of the product diskettes and try the installation
         again.

---------  

LSI0006: There is not enough disk space available to process locked files.

Cause:   The LAN Services locked-file device driver is unable to
         continue because there is not enough hard-disk space on this
         workstation.

Action:  Make hard-disk space available on this workstation by moving or
         deleting files, and then start the workstation again.

---------  

LSI0007: The installation/configuration program has detected an error in the 
*** parameter.

Cause:   This error code indicates that LAN Services has detected
         a parameter that is not correct.
         The installation command syntax is:

         [d:\path\]LANINSTR {/SRV | /REQ} [/R:d:\path\filename
          /G:d:\path /L1:d:\path\filename /L2:d:\path\filename]

         where:

         /SRV  Specifies you are remotely installing server code.
         /REQ  Specifies you are remotely installing requester code.
         /R    Specifies the fully qualified file name of a response file.
         /G    Specifies the fully qualified path of a directory containing
               files that are included by the response file.
         /L1   Specifies the fully qualified file name of an error log file.
         /L2   Specifies the fully qualified file name of a history log file.

Action:  Try the command again using the correct parameters.

---------  

LSI0008: An access-denied error occurred while loading the 
installation/configuration program.

Cause:   You have not logged on with sufficient privilege
         to allow the files to be copied to the hard disk on this
         workstation.

Action:  Log on with sufficient privilege and then try the installation
         again.

---------  

LSI0009: The installation/configuration program has detected an incorrect 
value for the OS/2 environment variable REMOTE_INSTALL_STATE.

Cause:   The value you specified for REMOTE_INSTALL_STATE is not
         valid.

Action:  SET REMOTE_INSTALL_STATE=.  Then try the installation again.

---------  

LSI0010: Logging initialization failed for file ***.

Cause:   The LAN Services installation/configuration program
         could not initialize history and error logging because it could
         not access the specified file.

Action:  Ensure that the file name specified is correct and that you have
         access privileges for the file.  Then try the installation again.

---------  

LSI0100: An error occurred while writing to log file ***. Logging to that file
has been disabled.

Cause:   An error occurred while writing to the log file.
         Logging to that file was disabled, but the
         installation/configuration program was allowed to continue.
         The error may have been caused by the loss of LAN connectivity,
         lack of hard-disk space, or lack of access to the log file.

Action:  Verify that a LAN connection exists and that enough hard-disk
         space is available.  Also make sure the user has the proper
         access permissions to the log file and that no other programs
         are trying to write to the log file at the same time.


---------  

LSI0101: *** completed unsuccessfully with a return code of ***.

Cause:   The module specified completed unsuccessfully with
         a return code.  The return code may be module-specific.

Action:  Contact your network administrator for assistance.


---------  

LSI0102: IBMLANLK detected errors processing the following commands.

Cause:   IBMLANLK detected errors while processing the
         following commands.  The commands did not complete
         successfully.

Action:  Verify that there is enough hard-disk space available
         and that the user has the proper access permissions to
         perform the commands listed; then try the installation again.


---------  

LSI0105: File specified (/B:***) does not have the proper format.

Cause:   The file specified on the /B parameter does not have the
         format required to restore ACLs.

Action:  Specify the correct file name on the /B parameter or correct the
         format of the specified file.


---------  

LSI0106: OS/2 error *** has occurred.

Cause:   An error occurred because of a request made to the operating
         system.

Action:  Type Help followed by the error number to determine the cause of
         the error.


---------  

LSI0107: The LAN Server APIs cannot be used.

Cause:   The APIs are not on this workstation or their path is not
         in LIBPATH in CONFIG.SYS.

Action:  Verify that the LIBPATH statement in CONFIG.SYS contains a pointer
         to the APIs.  If you are using the 386 boot diskette, make sure that
         the APIs have been copied to the hard disk.


---------  

LSI0108: The syntax is incorrect.

Cause:   There is an error in the command syntax.

Action:  Type the command followed by a ? to display the proper syntax.


---------  

LSI0109: The file or subdirectory *** could not be found.

Cause:   The file or subdirectory specified on one of the command
         parameters could not be found.

Action:  Reissue the command with the proper file or subdirectory name.


---------  

LSI0110: OS/2 error *** has occurred while processing file ***.

Cause:   The operating system returned an error on a file request
         for the specified file.

Action:  Type Help followed by the error number to determine the cause of
         the error.


---------  

LSI0111: The file or subdirectory *** could not be created.

Cause:   A request to create the specified file or subdirectory
         failed.

Action:  Ensure that the proper file or subdirectory was specified and that
         you have the proper authority to create the file or subdirectory.


---------  

LSI0112: There is not enough disk space on drive ***.


Cause:   The required amount of disk space is not available on the
         specified drive.

Action:  Move or erase files to increase the available disk space
         or specify a different drive.


---------  

LT00003: IBM LANDD:  A failure occurred during initialization.

Cause:  An initialization error has been reported, which has
caused the device driver to not install.

Action:  Check the FFST/2 message log if you are using FFST/2 or the
LANTRAN.LOG to identify the specific condition that caused the failure.
A message detailing that condition will be logged prior to this message.

---------  

LT00006: The protocol manager could not be opened.  The return code is ***.

Cause:  This message will be displayed when the system service DosOpen
request to the PROTMAN.OS2 device driver fails for any reason.  This can
also happen when another device driver has opened PROTMAN with exclusive
rights and has failed to close it.

Action:  Check your CONFIG.SYS file and ensure that the PROTMAN.OS2
device driver is active.  For additional information about the return code
displayed with the message for a specific cause, type HELP nnnn from
the OS/2 command prompt.

---------  

LT00007: The protocol manager would not accept a request.

Cause:  The protocol manager failed to honor a request from this protocol 
stack.

Action:  Check the FFST/2 message log if you are using FFST/2 or the
LANTRAN.LOG for additional messages from the protocol manager that
will indicate the cause for failure.  Correct the error and try
the operation again.

---------  

LT00008: The protocol manager would not supply a configuration image.

Cause:  The protocol manager did not honor the request for the
configuration image.

Action:  Verify that the PROTOCOL.INI file exists and that it
is valid; then retry the operation.

---------  

LT00009: The protocol manager would not accept module registration.

Cause:  An attempt to register the device name with the protocol
manager was unsuccessful.

Action:  Ensure that the bracketed names in PROTOCOL.INI are unique
and try the operation again.

---------  

LT00011: No MAC driver bindings were specified in PROTOCOL.INI.  IBM LANDD did
not load.

Cause:  There were no media access control (MAC) names specified
on the BINDINGS= statement in the IBM LANDD section of PROTOCOL.INI.

Action:  Correct the PROTOCOL.INI file to ensure that a valid MAC
driver name is specified on the BINDINGS= statement.

---------  

LT00012: There are too many MAC drivers to bind.  IBM LANDD did not load.

Cause:  The number of media acess control (MAC) drivers specified
on the BINDINGS= statement in PROTOCOL.INI exceeds the maximum
number of devices to bind (MAXBIND).

Action:  Correct the PROTOCOL.INI file to ensure that the number
of MAC names specified in the BINDINGS= statement does not exceed
16.

---------  

LT00013: There are more values specified for keyword *** than allowed. IBM 
LANDD did not load.

Cause:  Each value for a keyword in the PROTOCOL.INI file represents
a configuration parameter for a media access control (MAC) device
driver.  The maximum number of MAC drivers allowed is determined by
the value specified for the MAXBIND parameter or defaults to 16.

Action:  Correct the PROTOCOL.INI file to ensure that the number of values
for the keyword is less than or equal to the maximum number of MAC drivers
allowed.  Check your release information for the number of adapters
supported by this system.

---------  

LT00014: System resources are not available to hold the current parameter 
configuration in PROTOCOL.INI.  IBM IEEE 802 (LANDD) did not load.

Cause:  Either the sum of the configuration parameters require more than
64KB, or there is not enough memory to allocate the necessary storage
for the device driver.  If this is a 286 processor system, the sum of all
of the configuration parameters must fit in 64KB.  If this is a 386
or higher processor system, all parameters except the links and timer
control blocks must fit in 64KB.

Action:  Refer to your network planning and administration guides
for additional information about suggested values.
Reduce the resources required by changing PROTOCOL.INI,
or add more memory, and try the operation again.

---------  

LT00015: The value specified as the node address for MAC *** is not a valid 
hexadecimal number.

Cause:  The node address specified must be a hexadecimal number.
An incorrect hexadecimal character was specified in the node
address value.

Action:  Change the NETADDRESS parameter in PROTOCOL.INI to ensure
that the value is correct.  Hexadecimal numbers can consist of
the digits 0 through 9 only and the letters A through F (uppercase
or lowercase).

---------  

LT00016: The value specified for the node address is not valid for adapter 
***.  IBM LANDD did not load.

Cause:  The value specified for the node address (NETADDRESS) must
be 12 hexadecimal numbers in length.  Hexadecimal numbers can
consist of the digits 0 through 9 only and the letters A through F
(uppercase or lowercase).

Action:  Correct the node address and try the operation again.

---------  

LT00017: The ETHERAND parameter configured for adapter *** is not DIX or 
802.3.  IBM LANDD did not load.

Cause:  The parameter that identifies ETHERAND type in PROTOCOL.INI
must be configured for DIX or 802.3.  This parameter is not
configured correctly.

Action:  Either remove the ETHERAND type parameter from PROTOCOL.INI
to allow the value to default to 802.3, or change the parameter to
reflect the appropriate value.  If the ETHERAND type is DIX, a D
must be specified.  If the ETHERAND type is 802.3, an I (IEEE
format) must be specified.

---------  

LT00018: The unrecognized keyword *** was found in PROTOCOL.INI.

Cause:  A keyword was found in PROTOCOL.INI that is not
recognized as a valid parameter.

Action:  Review the PROTOCOL.INI file to locate the incorrect
parameter.  Correct or delete the unrecognized keyword and try
the operation again.

---------  

LT00020: A value is required for keyword *** in PROTOCOL.INI.

Cause:  The keyword specified has required parameters.  No parameter
values were found for this keyword.

Action:  Add the proper value to the keyword and try the operation again.

---------  

LT00021: The value specified for parameter *** is not valid.

Cause:  The value provided for the parameter is not the correct
type or is not a valid value.

Action:  Change the value for the parameter in PROTOCOL.INI.

---------  

LT00022: The value specified for parameter *** is not valid.

Cause:  The value specified for the parameter is either larger
than the maximum allowed or smaller than the minimum allowed for
that parameter.

Action:  Correct the value specified and try the operation again.

---------  

LT00023: Duplicate parameter *** was found in PROTOCOL.INI.

Cause:  The parameter occurred more than once in PROTOCOL.INI.
Only one occurrence of the parameter is allowed.

Action:  Change PROTOCOL.INI so that it contains only one reference to the
parameter and try the operation again.

---------  

LT00025: The IBM LANDD section was not found in PROTOCOL.INI.

Cause:  No section was found defining the parameters for the IBM LANDD device
driver in PROTOCOL.INI.

Action:  Insert a section in PROTOCOL.INI with the appropriate values for
the IBM LANDD device driver.  Minimum entries are the module name, driver
name, and bindings statements.

---------  

LT00026: The LANMSGDD device driver could not be opened.  The return code is 
***.

Cause:  The message handling device driver is not installed
or cannot be accessed.

Action:  Check the FFST/2 message log if you are using FFST/2 or the
LANTRAN.LOG for a failure message.  Check the CONFIG.SYS file to
ensure that a DEVICE= statement exists for LANMSGDD.OS2.  For
additional information about the return code displayed with
the message, type HELP nnnn from the OS/2 command prompt.
Correct the problem and try the operation again.

---------  

LT00027: An unexpected error was returned from a SetTimer request.

Cause:  The system service SetTimer returned an unsuccessful
error code.

Action:  Try the operation again.  If the error persists, contact
your vendor sales representative.

---------  

LT00028: An unexpected error was returned from a request to allocate GDT 
selectors.  The return code is ***.

Cause:  The device driver tried to allocate one or more
GDT selectors and the system service returned an unsuccessful
error code.

Action:  Reduce the number of GDTs used by device drivers that
install before LANDD.OS2.  It may be possible to do this by changing
the configuration options in PROTOCOL.INI for the drivers that
install before LANDD.OS2, or it may be necessary to change CONFIG.SYS
to have LANDD.OS2 load earlier.  For additional information about the
return code displayed with the message, type HELP nnnn from the OS/2
command prompt.

---------  

LT00029: An unexpected error was returned from a request to map GDT selectors.
The return code is ***.

Cause:  The operating system could not map a physical address to a GDT 
selector.

Action:  Try the operation again.  For additional information about the
return code displayed with the message, type HELP nnnn from the OS/2 command
prompt.  If the problem persists, note the message number and return code
value and contact your vendor sales representative.

---------  

LT00030: An unexpected error was returned from a PhysToVirt request.  The 
return code is ***.

Cause:  The operating system could not convert a physical address to
a virtual LDT ring three selector.

Action:  Try the operation again.  For additional information about the
return code displayed with the message, type HELP nnnn from the OS/2
command prompt.  If the problem persists, note the message number and
return code value and contact your vendor sales representative.

---------  

LT00031: An unexpected error was returned from a PhysToVirt request.

Cause:  The offset returned from the system service PhysToVirt
request was not 0.

Action:  Try the operation again.  If the problem persists, note the
message number and contact your vendor sales representative.

---------  

LT00032: An unexpected error was returned from a GetDOSVar request.

Cause:  The address to the system global information segment is not
valid.

Action:  Try the operation again.  If the problem persists, note the
message number and contact your vendor sales representative.

---------  

LT00033: The operating system installed is not compatible with this program.

Cause:  This program requires that a compatible version of OS/2
be loaded in order to run.

Action:  Refer to your documentation to determine the compatible OS/2
version and install that version, or delete the IBM LANDD section
from CONFIG.SYS.

---------  

LT00034: An unexpected error was returned when the program tried to lock a 
memory segment.

Cause:  The request to lock a memory segment failed because the
segment was unavailable or the lock handle was not valid.

Action:  Change the number of links or adapters being used to reduce
memory usage and try the operation again.  If the problem persists,
contact your vendor sales representative.

---------  

LT00035: An unexpected error was returned from a VirtToPhys request.

Cause:  The system service VirtToPhys returned an unsuccessful
error code.

Action:  Try the operation again.  If the problem persists, note the
message number and contact your vendor sales representative.

---------  

LT00036: An unexpected error was returned when the program tried to allocate 
memory for the group SAP receive Buffer.  The return code is ***.

Cause:  A system service request to allocate memory for the
group SAP receive buffer failed because the memory was not available.

Action:  Change the number of links or adapters being used to
reduce memory usage and try the operation again.
For additional information about the return code displayed with
the message, type HELP nnnn from the OS/2 command prompt.
If the problem persists, contact your vendor sales representative.

---------  

LT00037: An unexpected error was returned when the program tried to request a 
GDT for the group SAP recieve buffer.

Cause:  The sytem has run out of GDT selectors.

Action:  Increase the available number of GDT selectors by
changing the SELECTORS= parameter in PROTOCOL.INI to a larger number.
Try the operation again.

---------  

LT00038: The system is unable to map the group SAP receive buffer to a GDT.  
The return code is ***.

Cause:  The system could not map a physical address to a GDT selector
because either the physical address or the GDT is not valid.

Action:  Try the operation again.  For additional information about the
return code displayed with the message, type HELP nnnn from the OS/2 command
prompt.  If the problem persists, note the message number and return
code and contact your vendor sales representative.

---------  

LT00039: The *** MAC is an 802.3 protocol but is configured for DIX.

Cause:  The ETHERAND type specified for this adapter in PROTOCOL.INI
is DIX, but the MAC driver requires 802.3 frame formats.

Action:  Either remove the ETHERAND type parameter from PROTOCOL.INI
to allow the value to default to 802.3 or change the parameter to allow 802.3
frame formats for this MAC.

---------  

LT00040: The *** MAC is a DIX protocol but is configured for 802.3.

Cause:  The ETHERAND type specified for this adapter in PROTOCOL.INI
is 802.3, but the MAC driver requires DIX frame formats.

Action:  Change the ETHERAND type keyword to allow DIX frame
formats for this MAC.  If the parameter does not exist in PROTOCOL.INI,
it must be created; the default value for this parameter is 802.3.

---------  

LT00041: The *** MAC will not accept the configured node address.

Cause:  A node address (NETADDRESS) has been configured for
a MAC driver that does not support the SetStationAddress function.

Action:  Remove the node address statement from PROTOCOL.INI.
Check the MAC parameters to see if the node address can be configured
directly through the MAC driver.

---------  

LT00042: The *** MAC was not able to bind.  Return Code = ***.

Cause:  An unexpected error occurred when the protocol manager
tried to bind to the MAC driver.

Action:  Check for additional messages from the MAC driver
indicating an error, and check the bindings list in PROTOCOL.INI
for an incorrect name.  Correct the error and try the operation
again.  If the condition persists, contact your MAC vendor
sales representative.

---------  

LT00043: An unexpected error occurred when the program tried to set the *** 
MAC packet filter.

Cause:  IBM LANDD and NETBEUI require that the packet filter function be
supported by the MAC device driver.  The MAC driver installed on this
system does not support the receiving of packets of the type requested.

Action:  Install a version of the MAC device driver that supports the
required level of function.

---------  

LT00044: An unexpected error occurred when the program tried to set the *** 
MAC lookahead size.

Cause:  NDIS requires that MAC device drivers support a 256 byte lookahead
buffer.  An error code was returned when the program tried to set
this buffer size.

Action:  Install a version of the MAC device driver that supports the
required level of function.

---------  

LT00045: An error occurred when the program tried to set the *** MAC node 
address.

Cause:  The MAC device driver indicates that it will accept
a user-defined node address but is unable to process the request.

Action:  To use the burned-in address from the adapter, change
PROTOCOL.INI to remove the configured node address.

---------  

LT00046: IBM LANDD was unable to open the *** MAC driver.

Cause:  The unexpected error occurred when the program attempted
to open the adapter for the MAC device driver.

Action:  Check for additional messages from the MAC driver indicating
an error.  Try the operation again.  If the problem persists, contact
your MAC vendor sales representative.

---------  

LT00047: IBM LANDD received an open adapter request before the *** MAC bind 
completed.

Cause:  An open adapter request was issued before the bind
to the MAC driver was successfully completed.

Action:  Change CONFIG.SYS to ensure that the RUN= statement
exists for NETBIND.EXE.  This will ensure that the bind process
completes as quickly as possible.

---------  

LT00049: IBM LANDD encountered an internal error when the program attempted to
reference *** MAC by the logical adapter number.

Cause:  The high-memory GDT selector for this MAC could not be
found in the logical MAC cross-reference array.  Binding to this
MAC will fail.

Action:  Try the operation again.  If the problem persists,
contact your vendor sales representative.

---------  

LT00050: Duplicate node addresses exist on the network for *** MAC.

Cause:  The node address specified in the PROTOCOL.INI file already
exists on the network.  Each node address must be unique for the
network.

Action:  Either change the node address for this MAC device driver to be
a unique or locate the other system with the same node address specified
in the PROTOCOL.INI file and change that node address.  Try the operation
again.

---------  

LT00055: An unexpected error was returned when the program tried to transmit 
the duplicate node address test. The *** MAC return code is ***.

Cause:  LANDD received an unexpected return code when trying to transmit
the duplicate node address test.

Action:  Correct the error and try the operation again.  If the condition
persists, contact your MAC vendor sales representative.

---------  

LT00056: The OpenAdapter request to the *** MAC Driver did not complete within
the required time limit.

Cause:  The OpenAdapter request made to the MAC Driver did not complete
within the specified time limit.

Action:  Check the adapters for possible hardware conflicts and try the
operation again.  If the condition persists, contact your MAC vendor sales
representative.

---------  

LT00060: An error occurred while attempting to load NETBEUI.

Cause:  An error occurred during device driver initialization.  This
error is preventing the device driver from installing properly.

Action:  Check for additional messages indicating a specific
problem.  Correct that problem and try the operation again.

---------  

LT00061: There is no section for NETBEUI in PROTOCOL.INI.

Cause:  There are no configuration parameters defined for
NETBEUI in PROTOCOL.INI.

Action:  Change PROTOCOL.INI to add a section of configuration
information for NETBEUI.  The minimum statements required for this
section are MODULENAME=, DRIVERNAME=, and BINDINGS=.  Try the
operation again.

---------  

LT00064: A version of the redirector was detected that is not compatible with 
the version of NETBIOS ***.

Cause:  An incompatible version of the redirector is installed
on this system.  NETBIOS will not run with this version.

Action:  Install the proper version of the redirector and try the operation
again.

---------  

LT00065: The configuration parameters defined in PROTOCOL.INI exceed the 64KB 
work area.  NETBIOS *** support has ended.

Cause:  This error usually occurs when an additional adapter is
installed in the machine, but none of the Netbios Command resources have
been reserved by the Requester configuration.  This causes the Netbios
commands for all adapters to be absorbed by the NETBIOS.OS2 file, which
reaches an overflow condition for its 64K resource area.

Action:  If LAN Server or Requester is installed, configure resources to
support the new adapter.  The LS configuration utility will add a new NET
statement to the IBMLAN.INI file reducing the number of Commands passed
to NETBIOS.OS2.  If LAN Server or Requester is NOT installed, reduce the
number of Netbios Commands per adapter using the MPTS configuration utility.
This will reduce the Netbeui NCBs parameter in the PROTOCOL.INI file.

---------  

LT00071: The default path is not valid.  The default directory will be changed
to the root directory.

Cause:  The path \IBMCOM or the default override path specified on
the DEVICE= statement in CONFIG.SYS for the message device driver
is not valid.

Action:  Change the DEVICE= statement in CONFIG.SYS to an
existing path or create the directory specified as the path.
Re-IPL the system and try the operation again.

---------  

LT00072: An error occurred while attempting to open or write to file ***.  
Check for insufficient disk space.

Cause:  An error occurred when the program tried to open
or write from the message device driver.

Action:  Check the root directory and ensure that adequate
space exists for operation.  Try the operation again.

---------  

LT00073: FFST/2 is installed but is not started.  LANTRAN.LOG is being 
created.

Cause:  A program was unable to use FFST/2 to handle messages
because it is not started.  An ASCII file named LANTRAN.LOG
is being created to hold messages.  This file may be
viewed or printed using OS/2 commands.

Action:  No action is required.  If logging to FFST/2 is desired,
include a RUN=d:\OS2\EPW statement in CONFIG.SYS.

---------  

LT00081: The IBM LANDD device driver is not installed.

Cause:  The IBM LANDLLDD was not able to open or attach to the IBM
LANDD device driver.

Action:  Change the CONFIG.SYS file to ensure that the DEVICE= statements
exist for both LANDLLDD and LANDD and that the LANDD statement is
specified first.  Retry the operation.  If the problem persists,
reinstall the device drivers.

---------  

LT00082: An unexpected error was returned from an AllocPhys request.

Cause:  The system service AllocPhys returned an unsuccessful
error code to the program.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT00083: An unexpected error was returned from a DosGetInfoSeg request.

Cause:  The system service DosGetInfoSeg returned an unsuccessful
error code.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT00084: An unexpected error was returned from a PhysToGDT request.

Cause:  The system service PhysToGDT returned an unsuccessful
error code.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT00086: IBM OS/2 LANDLLDD is not installed.

Cause:  The program was unable to open the IBM LANDLLDD device driver.

Action:  Check the CONFIG.SYS file to ensure that the DEVICE= statement
exist for LANDLLDD.  Retry the operation.  If the problem persists,
reinstall the device driver.

---------  

LT00087: IBM OS/2 LANDLLDD:  There is not enough memory available for CCB3 
areas.

Cause:  There is not adequate memory for LANDLLDD to run properly.

Action:  There are several things that might fix this error:

- Add additional memory to this system.

- Reduce the number of active applications and devices.

- Reconfigure the MAC parameters to reduce resource requirements.

---------  

LT00090: Adapter ***:  NETBIOS is not operational.

Cause:  There are not enough system resources for NETBIOS
to continue running.  Refer to the message log for total
resources currently allocated for all NETBIOS applications.

Action:  To resolve the problem, increase the resource requirements
(SESSIONS=, NAMES=, and COMMANDS=) in PROTOCOL.INI.  Try the
operation again.

---------  

LT00091: No configuration section was found in the PROTOCOL.INI file for 
either NETBIOS or NETBEUI.

Cause:  NETBIOS requires the presence of either a NETBEUI or NETBIOS
section in the PROTOCOL.INI file.

Action:  Ensure that the configuration parameters are present in
the PROTOCOL.INI file for either NETBIOS or NETBEUI or both; then
retry the operation.  If the NETBIOS API is not needed, remove
the DEVICE= statement for NETBIOS.OS2 from the CONFIG.SYS file.

---------  

LT00092: NETBIOS does not recognize device driver ***.

Cause:  The device driver specified is not valid.  The specified device
driver may not be compatible with the network adapter or the version
may not be supported.

Action:  Install a supported version of the device driver and retry
the operation.

---------  

LT00093: An error occurred when the program tried to open network device 
driver ***.

Cause:  NETBIOS could not open the device driver.

Action:  Change the CONFIG.SYS file to ensure that the DEVICE= statement
exists and contains the correct path and name for the device driver.
Ensure that the device driver entry is before the NETBIOS.OS2
entry.  Retry the operation.

---------  

LT00094: A syntax error was detected for ADAPTER *** in the NETBIOS section of
PROTOCOL.INI.

Cause:  The NETBIOS section of the PROTOCOL.INI file contains an error
on the line specified by the adapter number.

Action:  Specify a valid adapter line and try the operation again.

The following is the syntax of the adapter line in the NETBIOS section:

ADAPTER# = Driver,Adp,Sess,NCBs,Names

Where:
# - Digit to be used as the NETBIOS API NCB adapter number.
Driver - String specifing driver name that NETBIOS will bind to.
Adp - Digit adapter number that NETBIOS uses to bind to the Driver.
Sess - Digit specifing Sessions requested for the NETBIOS API.
NCBs - Digit specifing NCBs requested for the NETBIOS API.
Names - Digit specifing Names requested for the NETBIOS API.

---------  

LT00095: No MAC driver bindings were specified in PROTOCOL.INI.  IBM NETBEUI 
did not load.

Cause:  There were no media access control (MAC) names specified
on the BINDINGS= statment in the IBM NETBEUI section of PROTOCOL.INI.

Action:  Correct the PROTOCOL.INI file to ensure that a valid MAC
driver name is specified on the BINDINGS= statement.

---------  

LT00096: There are too many MAC drivers to bind.  IBM NETBEUI did not load.

Cause:  The number of media acess control (MAC) drivers specified
on the BINDINGS= statement in PROTOCOL.INI exceeds the maximum
number of devices to bind (MAXBIND).

Action:  Correct the PROTOCOL.INI file to ensure that the number
of MAC names specified in the BINDINGS= statement does not exceed
12.

---------  

LT00097: System resources are not available to hold the current parameter 
configuration in PROTOCOL.INI.  IBM NETBEUI did not load.

Cause:  Either the sum of the configuration parameters require more than
64KB, or there is not enough memory to allocate the necessary storage
for the device driver.  If this is a 286 processor system, the sum of all
of the configuration parameters must fit in 64KB.  If this is a 386
or higher processor system, all parameters except the link and session
control blocks must fit in 64KB.

Action:  Refer to your network planning and administration guides
for additional information about suggested values.  Reduce the resources
required by changing PROTOCOL.INI, or add more memory, and try the
operation again.

---------  

LT00098: An unexpected error was returned from a request to allocate GDT 
selectors.  The return code is ***.

Cause:  The device driver tried to allocate one or more
GDT selectors and the system service returned an unsuccessful
error code.

Action:  Reduce the number of GDTs used by device drivers that
install before NETBEUI.OS2.  It may be possible to do this by changing
the configuration options in PROTOCOL.INI for the drivers that
install before NETBEUI.OS2, or it may be necessary to change CONFIG.SYS
to have NETBEUI.OS2 load earlier.  For additional information about
the return code displayed with the message, type HELP nnnn from the
OS/2 command prompt.  If the problem persists, reduce the number of GDT
selectors specified in the NETBEUI section of the PROTOCOL.INI file.

---------  

LT00099: The operating system installed is not compatible with this program.

Cause:  This program requires a compatible version of OS/2 in order to
run.

Action:  Check your documentation and install the proper version
of OS/2 and try the operation again, or delete the IBM NETBEUI section
from CONFIG.SYS.

---------  

LT00100: The value specified for the node address is not valid for adapter 
***.  IBM NETBEUI did not load.

Cause:  The value specified for the node address (NETADDRESS) must
contain 12 hexadecimal numbers.  Hexadecimal numbers can
consist of the digits 0 through 9 and the letters A through F
(uppercase or lowercase).

Action:  Correct the node address and try the operation again.

---------  

LT00101: More values than allowed are specified for keyword ***. IBM NETBEUI 
did not load.

Cause:  The value for the keyword in the PROTOCOL.INI file represents
a configuration parameter for a media access control (MAC) device
driver.  The maximum number of MAC drivers allowed is 12.

Action:  Correct the PROTOCOL.INI file to ensure that the number
of values for the keyword is less than or equal to the maximum
number of MAC drivers allowed.

---------  

LT00102: NETBIOS name-in-conflict was received for NETBIOS local name *** 
(ASCII format). The name-in-conflict frame was transmitted by node address 
***.

Cause:  A remote node received responses to a Netbios Call from more
than one address.

Action:  If the remote node sending the NIC frame is across a bridged link,
the NETBIOSTIMEOUT and T1 timers may need to be increased on the remote
node.  Make sure if the server has multiple adapters, that the topology of
the LAN was not changed to connect two separate LAN segments together during
server operation.  Be sure that there is not a duplicate address on the 
network
matching the address of the remote node sending the NIC frame.  Be 
sure there
is not a genuine duplicate name on the network.

---------  

LT00104: A NETBIOS name-in-conflict has occurred.  The same NETBIOS name was 
detected at node addresses *** and ***.

Cause:  The workstation received a name-recognized frame from
more than one node address which has the same NETBIOS unique name
registered, or a NETBIOS name is registered as both a group name and a
unique name in the network.  For example, two workstations may have
specified the same COMPUTERNAME in the IBMLAN.INI file.

Action:  Check the workstations at the node addresses for duplicate
NETBIOS names and change them to be unique.

---------  

LT00105: A request to use a free NETBEUI GDT selector failed.  The resource is
not available.

Cause:  NETBEUI attempted to use one or more NETBEUI GDT
selectors, and the resource was not available.

Action:  Increase the available number of GDT selectors specified in the
NETBEUI section of the PROTOCOL.INI file by changing the SELECTORS
parameter.  Then, restart the workstation and try the operation again.

---------  

LT00106: A NETBIOS link was disconnected because a NETBIOS acknowledgment was 
not received within the response timer (T1) value.

Cause:  A NETBIOS acknowledgment was not received within the
response timer (T1) value set in the NETBEUI section of the PROTOCOL.INI
file.  The local link station disconnected the link with the remote link
station.  The lack of receiving an acknowledgment may be because of heavy
network traffic.

Action:  Increase the response timer value specified in the NETBEUI
section of the PROTOCOL.INI by changing the T1 parameter.  This parameter
has the following relationship with the T2 and Ti parameters:

  T2 < T1 < Ti

Then, restart the workstation and try the operation again.

---------  

LT00107: NETBEUI has been notified of a change in network status.  A critical 
network status notification may cause the adapter to close.

Cause:  A change in the network status has occurred, and
NETBEUI has been notified of the change.  If the change indicates a
critical network status, the adapter may close.

Action:  Ensure the cable is securely connected to the network adapter
card.  Otherwise, ensure that the network is functioning correctly.

---------  

LT00108: A request to use a free NETBEUI UI-Frame descriptor failed.  The 
resource is not available.

Cause:  NETBEUI attempted to use one or more NETBEUI UI-Frame
descriptors, and the resource was not available.

Action:  Increase the available number of UI-Frame descriptors specified in
the NETBEUI section of the PROTOCOL.INI file by changing the DATAGRAMPACKETS
parameter.  Then, restart the workstation and try the operation again.

---------  

LT00109: Namecaching has been disabled because insufficient datagrampackets 
have been configured.

Cause: The configuration of the namecaching function was enabled,
however, an insufficient number of datagram packets were configured to
support the namecaching function. The namecaching function was disabled.

Action:  Increase to at least 10, the number of DATAGRAMPACKETS configured in
NETBEUI section of the PROTOCOL.INI file.  Then, restart the workstation and
try the operation again.

---------  

LT00130: An error occurred while attempting to load TCPBEUI.

Cause:  An error occurred during device driver initialization.  This
error is preventing the device driver from installing properly.

Action:  Check for additional messages indicating a specific
problem.  Correct that problem and try the operation again.

---------  

LT00131: There is no section for TCPBEUI in PROTOCOL.INI.

Cause:  There are no configuration parameters defined for
TCPBEUI in PROTOCOL.INI.

Action:  Change PROTOCOL.INI to add a section of configuration
information for TCPBEUI.  The minimum statements required for this
section are MODULENAME=, DRIVERNAME=, and BINDINGS=.  Try the
operation again.

---------  

LT00134: No MAC driver bindings were specified in PROTOCOL.INI.  IBM TCPBEUI 
did not load.

Cause:  There were no media access control (MAC) names specified
on the BINDINGS= statment in the IBM TCPBEUI section of PROTOCOL.INI.

Action:  Correct the PROTOCOL.INI file to ensure that a valid MAC
driver name is specified on the BINDINGS= statement.

---------  

LT00135: There are too many MAC drivers to bind.  IBM TCPBEUI did not load.

Cause:  The number of media acess control (MAC) drivers specified
on the BINDINGS= statement in PROTOCOL.INI exceeds the maximum
number of devices to bind (MAXBIND).

Action:  Correct the PROTOCOL.INI file to ensure that the number
of MAC names specified in the BINDINGS= statement does not exceed
12.

---------  

LT00136: System resources are not available to hold the current parameter 
configuration in PROTOCOL.INI.  IBM TCPBEUI did not load.

Cause:  Either the sum of the configuration parameters require more than
64KB, or there is not enough memory to allocate the necessary storage
for the device driver.  If this is a 286 processor system, the sum of all
of the configuration parameters must fit in 64KB.  If this is a 386
or higher processor system, all parameters except the link and session
control blocks must fit in 64KB.

Action:  Refer to your network planning and administration guides
for additional information about suggested values.  Reduce the resources
required by changing PROTOCOL.INI, or add more memory, and try the
operation again.

---------  

LT00137: An unexpected error was returned from a request to allocate GDT 
selectors.  The return code is ***.

Cause:  The device driver tried to allocate one or more
GDT selectors and the system service returned an unsuccessful
error code.

Action:  Reduce the number of GDTs used by device drivers that
install before TCPBEUI.OS2.  It may be possible to do this by changing
the configuration options in PROTOCOL.INI for the drivers that
install before TCPBEUI.OS2, or it may be necessary to change CONFIG.SYS
to have TCPBEUI.OS2 load earlier.  For additional information about
the return code displayed with the message, type HELP nnnn from the
OS/2 command prompt.  If the problem persists, reduce the number of GDT
selectors specified in the TCPBEUI section of the PROTOCOL.INI file.

---------  

LT00138: The operating system installed is not compatible with this program.

Cause:  This program requires a compatible version of OS/2 in order to
run.

Action:  Check your documentation and install the proper version
of OS/2 and try the operation again, or delete the IBM TCPBEUI section
from CONFIG.SYS.

---------  

LT00139: The value specified for the node address is not valid for adapter 
***.  IBM TCPBEUI did not load.

Cause:  The value specified for the node address (NETADDRESS) must
contain 12 hexadecimal numbers.  Hexadecimal numbers can
consist of the digits 0 through 9 and the letters A through F
(uppercase or lowercase).

Action:  Correct the node address and try the operation again.

---------  

LT00140: More values than allowed are specified for keyword ***. IBM TCPBEUI 
did not load.

Cause:  The value for the keyword in the PROTOCOL.INI file represents
a configuration parameter for a media access control (MAC) device
driver.  The maximum number of MAC drivers allowed is 12.

Action:  Correct the PROTOCOL.INI file to ensure that the number
of values for the keyword is less than or equal to the maximum
number of MAC drivers allowed.

---------  

LT00141: Errors occurred while attempting to initialize TCPBEUI.

LT00141: Cause:  Errors occurred when TCPBEUI made TCP/IP calls to open and 
bind sockets to a TCP/IP network interface.

Action:  Make certain that TCP/IP is properly installed and configured.  
Correct the TCP/IP configuration so that at least one network interface is 
configured.

---------  

LT00143: TCPBEUI: Domain Name Server not found but DOMAINSCOPE was specified 
in PROTOCOL.INI.

LT00143: Cause: TCPBEUI tried to resolve a NETBIOS name into a TCP/IP name by
asking the TCP/IP Domain Name Server(DNS) but the gethostbyname call returned
an error indicating that the DNS did not answer.

Action: Make certain that TCP/IP is properly installed and configured.  
Correct the configuration so that the Domain Name Server is properly 
identified.  Do not use DOMAINSCOPE in your protocol.ini if a DNS is 
unavailable.

---------  

LT00200: An error occurred while updating the following file:      ***   Make 
sure that this file is not in use in any other OS/2 or DOS session.   Return 
to this session and select Retry to continue configuration.   Select Exit if 
you want
to end configuration.

Cause:  An OS/2 error occurred while updating the specified
file.  The file was not updated.

Action:  Switch to another OS/2 session and make sure the
file is not in use by another session.  Select Retry to
perform the operation again.

For additional information, see the FFST/2 message log if you are
using FFST/2 or the LANTRAN.LOG.

Select Cancel to return to the window displayed before the
update error occurred.

If you cannot correct the error, select Exit to return to the
installation/configuration program.

---------  

LT00201: An error occurred while reading the following file:         ***   
Make sure that this file is not in use in any other OS/2 or DOS session.   
Return to this session and select Retry to continue configuration. Select Exit
if you want
to end configuration.

Cause:  An OS/2 error occurred while attempting to read the
specified file.  The file could not be read.

Action:  Switch to another OS/2 session and make sure
the file is not in use by another session.  Select
Retry to perform the operation again.

For additional information, see the FFST/2 message log if you are
using FFST/2 or the LANTRAN.LOG.

Select Cancel to return to the previous window.  (Cancel is not
available for some configurations.)

If you cannot correct the error, select Exit to return to the
installation/configuration program.

---------  

LT00202: An error occurred while copying from subdirectory ***    to 
subdirectory ***.   Make sure that files being copied are not in use in either
of these subdirectories in any other OS/2 or DOS session.   Return to this 
session and select
Retry to continue configuration.   Select Exit if you want to end 
configuration.

Cause:  An OS/2 error occurred while copying the specified
file to the specified subdirectory.

Action:  Switch to another OS/2 session and verify that the
file is not in use by another session.  Select Retry to perform
the operation again.

For additional information, see the FFST/2 message log if you are
using FFST/2 or the LANTRAN.LOG.

Select Ignore to continue.

Select Cancel to return to the previous window.

If you cannot correct the error, select Exit to return to the
installation/configuration program.

---------  

LT00203: The value for the *** field must be between *** and ***. (or) The 
value for the *** field must be one of the following: (or) The value for the 
*** field must be between *** and *** in steps of ***. (or) The length of the 
*** field cannot
be longer than *** characters.

Cause:  The value in an entry field is out of range.

Action: Select OK to close this message and return to the field
indicated by the cursor.  Type the correct information as indicated
by the message.  For more information, press F1 on that field to display
help information for the field.

---------  

LT00204: The PROTOCOL.INI file was not found at the path specified.   Select 
OK and respecify the full path.

Cause:  An incorrect or incomplete path was typed in the
Path field in the Select Default PROTOCOL.INI File window.

Action:  Select OK to return to the previous window.  Type the
path to the PROTOCOL.INI file in the Path field.

---------  

LT00205: The network adapter drivers were not found at the path specified.   
Select OK and respecify the full path.

Cause:  An incorrect or an incomplete path was specified in the
Copy Additional Network Adapter Drivers window.  Ensure that
the drivers, initialization (.NIF) files, and supplementary
files are all at the specified path.

Action:  If the path is incorrect or incomplete, select
OK to return to the previous window.  Type the path in the
Path field.

If some of the files are not at the path, switch to another
session and copy the files to the specified path.  Return to
this window and select OK.  Specify the path again, if
necessary.

---------  

LT00206: All LAN Adapter and Protocol Support combinations in the Current 
Configuration list must contain at least one protocol driver.   Select OK and 
make sure all combinations are complete.

Cause:  One of the network adapter and protocol driver
combinations in the Current Configuration list is not complete.
One of the network adapters does not have a protocol driver.

Action:  Select OK to close this message.  Complete the
configuration by assigning a protocol driver to the
network adapter driver indicated by the cursor or by removing
the network adapter driver from the Current Configuration list.

---------  

LT00207: You have selected to change a network adapter that has a protocol 
driver associated with it.   You must remove all associated protocol drivers 
before removing this network adapter.

Cause:  You tried to remove a network adapter before removing
the associated protocol drivers.

Action:  Select OK to close the message.  If you want to remove
a network adapter, you must first remove the protocol drivers
associated with the network adapter.

---------  

LT00208: You cannot have duplicate logical adapter numbers for a protocol 
driver using multiple network adapters.   Select OK and then change one or 
more of the adapter numbers.

Cause:  You tried to update the PROTOCOL.INI file,
but there are duplicate logical adapter numbers for a specific
protocol driver.

Action:  Select OK and change one of the logical adapter
numbers.

---------  

LT00209: A decimal number must be entered. (or) A hexadecimal number must be 
entered.

Cause:  The value in an entry field is out of range.  The range of
correct values is indicated in the message.

Action: Select OK to close this message and return to the field
indicated by the cursor.  Type the correct information.  If you
do not know the correct data, press F1 on that field to display
help information for the field.

---------  

LT00210: An error occurred while attempting to update ***.

Cause:  An OS/2 error occurred during the attempt to update the
specified file.

Action:  Switch to another OS/2 session and ensure that the
file is not in use by another session.  Select Retry to
perform the operation again.

For additional information, see the FFST/2 message log if you are
using FFST/2, or see LANTRAN.LOG or LAPSHIST.LOG.

Select Cancel to return to the window displayed before the
update error occurred.

If you cannot correct the error, select Exit to return to the
installation/configuration program.

---------  

LT00211: An error occurred while attempting to read ***.

Cause:  An OS/2 error occurred during the attempt to read the
specified file.

Action:  Switch to another OS/2 session and ensure that
the file is not in use by another session.  Select
Retry to perform the operation again.

For additional information, see the FFST/2 message log if you are
using FFST/2, or see LANTRAN.LOG or LAPSHIST.LOG.

Select Cancel to return to the previous window.  (Cancel is not
available in some installation paths.)

If you cannot correct the error, select Exit to return to the
installation/configuration program.

---------  

LT00212: An error occurred while copying from subdirectory *** to subdirectory
***.

Cause:  An OS/2 error occurred during the attempt to copy
the specified file to the specified subdirectory.

Action:  Switch to another OS/2 session and ensure that the
file is not in use by another session.  Select Retry to perform
the operation again.

For additional information, see the FFST/2 message log if you are
using FFST/2, or see LANTRAN.LOG or LAPSHIST.LOG.

Select Ignore to continue.  However, the files may not be copied.

Select Cancel to return to the previous window.

Select Exit to return to the installation/configuration program.

---------  

LT00300: The configuration parameters supplied to LTSVCFG are incorrect. 
Defaults will be used for all adapters.

Cause:  A syntax error occurred in the configuration parameters supplied
to the LTSVCFG configuration tool.

Action:  Refer to your documentation for additional information about
parameter syntax. Correct the syntax and retry the operation.

---------  

LT00301: IBM LANVDD:  A request for internal memory failed.

Cause:  There is insufficient resources to accommodate a request for
fixed contiguous system memory.

Action:  There are several things that might fix this problem:
- Add additional memory to this system.
- Reduce the number of active applications and devices loaded on the
system.

---------  

LT00302: IBM LANVDD:  A failure has occured which prevents LANVDD from 
operating in this Virtual Dos Machine, Int5C support is terminated for this 
VDM.

Cause:  An unexpected error has been reported which prevents LANVDD
from operating in this Virtual Dos Machine.

Action:  Check LANTRAN.LOG to identify the specific condition that
caused the failure.  A message detailing that condition will be logged
prior to this message.

---------  

LT00303: The 802.2 protocol stack and the NetBIOS device drivers are not 
available. Virtual NetBIOS and Virtual 802.2 support are not available to 
VDMs.

Cause:  The protocol stack and device drivers were not loaded.

Action:  Ensure that the CONFIG.SYS file contains a DEVICE= statement
for LANDD.OS2 or NETBIOS.OS2.  If the CONFIG.SYS file contains these
statements, check the LANTRAN.LOG file for additional information.
If you do not need Virtual 802.2 and Virtual NetBIOS support, delete
the DEVICE= statments for LANVDD.OS2 and LANPDD.OS2 from the CONFIG.SYS
file.

---------  

LT00305: LANPDD was unable to register with the Virtual Dos Machine Manager.

Cause:  LANPDD could not register with the Virtual Dos Machine Manager.
Registration is required for LANVDD/LANPDD coexistence.

Action:  Insure that Virtual Dos support was selected at installation.
If Virtual Dos Support is not required then remove LANVDD and LANPDD
from the Config.sys file.


---------  

LT00307: A failure occurred which has prevented *** from being installed.

Cause:  An unexpected error has been reported which has
caused the device driver to not install.

Action:  Check LANTRAN.LOG to identify the specific condition that
caused the failure.  A message detailing that condition will be logged
prior to this message.

---------  

LT00308: IBM LANVDD:  The system could not obtain or map a GDT Selector.

Cause:  The system can not map a linear address to a 16:16 format or
is out of GDT Selectors.  If this happens at Device Driver initialization
the LANVDD will fail to install.

Action:  Reduce the number of GDTs used by device drivers that
install before LanVDD.OS2.  It may be possible to do this by changing
the configuration options in PROTOCOL.INI for the drivers that
install before LanVDD.OS2.

---------  

LT00309: The number of Dos Sessions which LANVDD can support has been 
exceeded.

Cause:  Netbios is supported in a maximum of 16 VDM sessions.  One has
surpassed this limit.

Action:  If Netbios is required, reduce the number of Dos sessions in
use or run your Netbios application in an already existing dos session.

---------  

LT00310: The Virtual Dos Machine Manager could not allocate a Software Hook 
required for LANVDD's internal operations.

Cause:  A failure occurred when trying to allocate either a Context,
Return, or WaitVIRR hook with the VDM Manager.

Action:  Insure that there are adequate disk and memory resources on
your machine before starting an VDM session or run with fewer VDM
Sessions.

---------  

LT00311: The operating system installed is not compatible with this program.

Cause:  The version of the operating system required for this program to
run is OS/2 2.0 or greater.

Action:  Install a version of OS/2 which is 2.0 or greater,
or delete the IBM LANPDD and LANVDD sections from CONFIG.SYS.

---------  

LT00312:  The OS/2 802.2 device driver, LANDD.OS2, is not available. DOS 802.2
support is ended for all VDMs.

Cause:  The IBM OS/2 802.2 protocol stack (LANDD.OS2) is not
installed or is not operational.  LANVDD cannot support the DOS 802.2
API if the OS/2 802.2 protocol stack is not present.

Action:  Ensure that the CONFIG.SYS file contains a DEVICE= statement
for LANDD.OS2.  If the CONFIG.SYS file contains the statement, check
the LANTRAN.LOG file for additional information.

---------  

LT00314:  LANVDD.OS2 was unable to map a virtual address to a linear address 
in system memory.

Cause:  The operating system may be damaged.

Action: Restart OS/2 and retry the request.  If this message persists,
report this problem and the contents of LANTRAN.LOG to an IBM service
representative.

---------  

LT00315:  A status indication was received for an unknown application ID.

Cause:  The IBM OS/2 802.2 protocol stack (LANDD.OS2) notified
LANVDD of a status event for an application unknown to LANVDD.

Action:  Restart OS/2 and retry the request.  If this message persists,
report this problem and the contents of LANTRAN.LOG to an IBM service
representative.

---------  

LT00316:     A status indication was lost or ignored.

Cause:  The IBM OS/2 802.2 protocol stack (LANDD.OS2) notified LANVDD
of a status event for a SAP LANVDD does not own.

Action:  Restart OS/2 and retry the operation. If this message persists,
report this problem and the contents of LANTRAN.LOG to an IBM service
representative.

---------  

LT00317:  LANVDD is unable to access DOS memory.

Cause: LANVMEM.SYS was not loaded as part of the DOS device settings in
this DOS environment.

Action:  Ensure that the DOS device driver, LANVMEM.SYS, is being loaded
as part of the DOS device settings for the specific DOS environment.

---------  

LT00318:  The maximum number of OS/2 802.2 user applications was reached.

Cause: The number of active 802.2 applications is the configured
maximum.

Action: Run the LAPS (Lan and Protocol Support) install program and
choose Configure.  Increase the value for the OS/2 802.2 resource,
Maximum Number of Users.

---------  

LT00319:  The maximum number of OS/2 802.2 SAPs was reached.

Cause:  The number of open 802.2 SAPs is the configured maximum.

Action: Run the LAPS (Lan And Protocol Support) install program and
choose Configure.  Increase the value for the OS/2 802.2 resource,
Maximum SAPs.

---------  

LT00320:  LANVDD was unable to allocate the requested OS/2 SAP buffers.

Cause:  The operating system could not provide system memory for a
LANVDD request.

Action: Stop any unnecessary applications and retry the request. If this
message persists, add more memory to your system.

---------  

LT00322:  LANDD did not complete a LANVDD BufferFree request successfully.

Cause:  The operating system may be damaged.

Action: Restart OS/2 and retry the request.  If this message persists,
report this problem and the contents of LANTRAN.LOG to an IBM service
representative.

---------  

LT00323:  LANVDD was unable to allocate internal memory elements.

Cause:  The operating system could not provide system memory for a
LANVDD request.

Action: Stop any unnecessary applications and retry the request. If this
message persists, add more memory to your system.

---------  

LT00324:  A LANVDD buffer allocation request was cancelled.

Cause: LANVDD could not allocate system memory for status elements.

Action: Stop any unnecessary applications and retry the request. If this
message persists, add more memory to your system.

---------  

LT00325:  LANVDD received a DLC status indication for a SAP that LANVDD did 
not open.

Cause:  The IBM OS/2 802.2 protocol stack (LANDD.OS2) notified
LANVDD of a status event for a SAP that LANVDD does not own.

Action:  Restart OS/2 and retry request.  If this message persists,
report this problem and the contents of LANTRAN.LOG to an IBM service
representative.

---------  

LT00326:  LANVDD was unable to simulate local busy to a DOS application.

Cause: LANVDD does not have enough internal resources to complete the
request.  LANVDD received an expected return code from LANDD on a
DLC.FLOW.CONTROL.

Action: Restart the application and retry the request. If this message
persists, report this problem and the contents of LANTRAN.LOG to an
IBM service representative.

---------  

LT30002: Device ***: A failure occurred during initialization.

Cause:  This is a generic initialization failure message.  If any
error is encountered by the device driver during IPL, the
specific message related to the error will be followed by
this generic message.

Action:  Resolve the specific error message that displayed prior
to this message, if present.  Otherwise, ensure that the protocol
manager is located in the proper directory and that the protocol
manager statement exists in CONFIG.SYS.

---------  

LT30003: This protocol used by this adapter is not supported.

Cause:  This adapter uses a protocol that is not supported by this
product.

Action:  Consult the ES/LS user documentation for a list of supported
adapters.

---------  

LT30004: Device ***: The value specified for a parameter in PROTOCOL.INI is 
not valid.

Cause:  The value provided for the parameter is not valid.

Action:  Review PROTOCOL.INI to determine the parameter that
contains the incorrect value.  Change the value and try the
operation again.

---------  

LT30005: Device ***: An unrecognized keyword was found in PROTOCOL.INI.

Cause:  A configuration parameter is defined in PROTOCOL.INI that
is not recognized as a valid keyword.

Action:  Review the PROTOCOL.INI file and determine the keyword
that caused the error.  Correct  the keyword and try the
operation again.

---------  

LT30006: Device ***:  The 3270 emulation adapter was not found.

Cause:  Probable causes are:

- The 3270 emulation adapter is not installed or is installed
improperly.

- The number of IBMXLN.OS2 drivers specified in CONFIG.SYS exceed
the number of 3270 emulation adapters installed.

Action:  Ensure that the 3270 emulation adapter is properly
installed and that CONFIG.SYS does not contain more
DEVICE= statements for IBMXLN.OS2 than there are 3270 emulation
adapters present in this system.

---------  

LT30007: There are too many IBMXLN devices defined in CONFIG.SYS.

Cause:  CONFIG.SYS contains too many DEVICE= statements for
IBMXLN.OS2. The maximum supported number for a Micro Channel PS/2 system is 4.
The maximum number for a non-Micro Channel PC system is 1.

Action:  Remove the excess DEVICE= statements from CONFIG.SYS
and try the operation again.

---------  

LT30009: Device ***: The protocol manager could not be opened.

Cause:  An unexpected error occurred when the program attempted to
open the protocol manager.


Action:  Check the drive and directory to ensure that the protocol
manager is located in the specified path.  Check CONFIG.SYS
to ensure that a DEVICE= statement for PROTMAN.OS2 is listed before
the DEVICE= statement for IBMXLN.OS2, and try the operation again.

---------  

LT30010: Device ***: An unexpected error was returned from a DOSDevIOCtl 
request.

Cause:  The system service DOSDevIOCtl returned an unsuccessful
error code.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT30011: Device ***: An error occurred when the program tried to get 
configuration information from the protocol manager.

Cause:  An attempt to obtain configuration information from
the protocol manager was unsuccessful.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT30012: Device ***: The version of the protocol manager installed is not 
compatible with this device.

Cause:  The version of the protocol manager installed will not run
with this device.

Action:  Install a compatible version of the protocol manager and
try the operation again.

---------  

LT30013: Device ***: An unexpected error was returned from an AllocGDTSelector
request.

Cause:  The system service AllocGDTSelector returned an
unsuccessful error code.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT30014: Device ***: An unexpected error was returned from a PhysToGDTSelector
request.

Cause:  The system service PhysToGDTSelector returned an
unsuccessful error code.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT30015: Device ***: The MAC driver is not registered or cannot be found.

Cause:  An attempt to register the device name with the
protocol manager was unsuccessful.

Action:  Review PROTOCOL.INI to ensure that the bracketed
names are unique and try the operation again.

---------  

LT30016: Device ***:  An unexpected error was returned from a PhysToVirt 
request.

Cause:  The system service PhysToVirt returned an unsuccessful
error code.

Action:  Try the operation again.  If the problem persists,
contact your vendor sales representative.

---------  

LT30017: Device ***:  There was no entry found in PROTOCOL.INI for driver name
***.  Default values will be used.

Cause:  No entry was found for the driver name in PROTOCOL.INI.

Action:  If default values are acceptable, no action is
required; otherwise, build a PROTOCOL.INI entry for the device and
try the operation again.

---------  

LT30018: Device ***:  Duplicate driver name *** parameters exist in 
PROTOCOL.INI.

Cause:  PROTOCOL.INI contains more than 1 entry with the
same driver name parameter.

Action:  Correct or remove the duplicate driver name parameter
and try the operation again.

---------  

LT30022: Device ***: The establishment controller is not responding.

Cause:  The establishment controller is not responding to a request issued
by the device.  The adapter has been closed.

Action:  Ensure the device is attached by coax to the controller
and that the controller is turned on; reopen the adapter to reactivate
peer communication protocols.  If the problem persists, restart your
system.

---------  

LT30023: Device ***:  An unexpected error was returned from a SetIRQ request.

Cause:  The system service SetIRQ returned an unsuccessful
error code.

Action:  Try the operation again. If the problem persists,
contact your vendor sales representative.

---------  

LT30024: Device ***: A RESET command was received from the controller.

Cause:  The controller has stopped peer communication
protocols by issuing a RESET  command to the device.

Action:  Reopen the adapter to activate the peer communication
protocols to the controller.

---------  

LT30025: Device ***: A *** protocol error was received from the controller.

Cause:  The controller has detected a protocol error from
the device or has been requested to remove the device from
the network.

Action:  If the protocol error returned is INVALID ENABLE INFO,
ensure that the address defined for the adapter in PROTOCOL.INI
is unique.  Reopen the adapter to reactivate peer communication
protocols to the controller.  If the problem persists, contact
your vendor sales representative.

---------  

LT30026: Device ***: A *** protocol error was sent to controller.

Cause:  The device has detected a protocol error from the controller and has
closed the adapter.

Action:  Reopen the adapter to reactivate peer communication protocols.   If
the error persists, contact your vendor sales representative.

---------  

LT30027: Device ***: This controller does not support peer communication 
protocols.

Cause:  The controller that is attached by coax to the device
does not support the 3174 Peer Communication protocol.

Action:  Ensure the the controller attached to the device
contains 3174 Peer Communication support.  If support is
available, try the operation again.  If the problem persists,
contact your vendor sales representative.

---------  

LT30028: Device ***: The RDEF command from the controller is not valid.

Cause:  The RDEF command from the controller was not acceptable to
the device.

Action:  Try the operation again.  If the problem persists, contact
your vendor sales representative.

---------  

LT30029: Device ***: An unexpected error was returned from a TickCount 
request.

Cause:  The system service TickCount returned an unsuccessful
error code.

Action:  Try the operation again. If the problem persists, contact
your vendor sales representative.

---------  

LT40004: The microcode file *** could not be opened.

Cause:  An unexpected error occurred when the program attempted to open
the microcode file.

Action:  Ensure that the microcode file MONT400.BIN is installed in
the drive and directory identified in the message.  If the file does
not exist or if the problem persists, reinstall the device driver.

---------  

LT40005: The microcode file *** could not be read.

Cause:  An unexpected error occurred when the program attempted to read
the microcode file.

Action:  Reinstall the device driver.

---------  

LT40006: The bootstrap file *** could not be opened.

Cause:  An unexpected error occurred when the program attempted to open
the bootstrap file.

Action:  Ensure that the bootstrap file WRTRAM.BIN is installed
in the drive and directory identified in the message.  If the file does
not exist or if the problem persists, reinstall the device driver.

---------  

LT40007: The bootstrap file *** could not be read.

Cause:  An unexpected error occurred when the program attempted to read
the bootstrap file.

Action:  Reinstall the device driver.

---------  

LT40008: The parameter specified in PROTOCOL.INI for keyword *** is not the 
proper character type.

Cause:  The value provided for the keyword in the
IBMTRBM module in PROTOCOL.INI is not the correct type.

Action:  Change the value in PROTOCOL.INI to
the correct type for the parameter.

---------  

LT40009: An unrecoverable error occurred in the IBM Token-Ring Network 16/4 
Busmaster Server Adapter/A NDIS device driver program.

Cause:  An internal software error occurred.

Action:  Contact your vendor sales representative.

---------  

LT40010: All IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapters 
must be set to the same interrupt level.

Cause:  One or more IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapters are set to a different interrupt level.
To function properly, these adapters must all be set to the
same interrupt level.

Action:  Use the reference diskette that came with your
computer to ensure that all IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapters are set to the same interrupt level.

---------  

LT40011: A data-check error occurred while attempting to load the bootstrap 
code onto the adapter.

Cause:  The bootstrap code was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.

Action:  Contact your vendor sales representative.

---------  

LT40012: A checksum error occurred while attempting to load the bootstrap code
onto the adapter.

Cause:  The bootstrap code was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.

Action:  Contact your vendor sales representative.

---------  

LT40014: The parameter values have forced the control-block size to exceed the
allowable limit.

Cause:  The parameters specified require more space for processing
than can be handled.  The maximum allowable control-block size
is 64KB.

Action:  Reduce the value specified for the MAXTRANSMITS
or MINRCVBUFFS parameter to change the amount of storage
required for the control-blocks.

The control-block area can be computed using the following formula:
334 + (142 * MAXTRANSMITS) + (20 * MINRCVBUFFS)

The control-block work area must be less than 64KB.

---------  

LT40015: The adapter is not responding.

Cause:  The adapter is not responding to a request to load
the bootstrap code.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40016: A 2KB window error occurred while attempting to load the bootstrap 
code onto the adapter.

Cause:  The adapter is not responding to a request to load
the bootstrap code.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40017: An error occurred while attempting to run the bootstrap code.

Cause:  The adapter is not responding to a request to run
the bootstrap code.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40018: A parameter error occurred while attempting to run the bootstrap 
code.

Cause:  The adapter is not responding to a request to run
the bootstrap code.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40019: A write error occurred while attempting to load the bootstrap code 
onto the adapter.

Cause:  The bootstrap code was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40020: A checksum error occurred while attempting to load the microcode onto
the adapter.

Cause:  The microcode was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.

Action:  Contact your vendor sales representative.

---------  

LT40021: The microcode encountered a program-status error while attempting to 
write to the adapter.

Cause:  The microcode was unable to write properly
to the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.

Action:  Contact your vendor sales representative.

---------  

LT40022: A reset error occurred while attempting to initialize the adapter 
microcode.

Cause:  The adapter is not responding to a request to initialize
the microcode.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40023: A parameter error occurred while attempting to run the microcode.

Cause:  The adapter is not responding to a request to run
the microcode.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40024: The burned-in address could not be found on the IBM Token-Ring 
Network 16/4 Busmaster Server Adapter/A adapter.

Cause:  The burned-in address on the adapter could not be located.

Action:  Either use the set network address (NETADDRESS)
parameter in PROTOCOL.INI to override the burned-in address or
run the hardware diagnostics for the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A adapter and contact your
vendor sales representative.

---------  

LT40025: Duplicate device driver statements exist in CONFIG.SYS.

Cause:  Only one occurrence of the device driver statement
for the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS MAC device driver is required to support multiple adapters.
Additional instances of the device driver statement in CONFIG.SYS
will be ignored.

Action:  Remove the duplicate device driver statements from
CONFIG.SYS.

---------  

LT40026: The required parameter DRIVERNAME was not found in PROTOCOL.INI.

Cause:  The parameter specifying the driver name (DRIVERNAME) was not
found in PROTOCOL.INI.  This parameter is required.

Action:  Change PROTOCOL.INI to specify the proper information.

---------  

LT40027: The protocol manager could not be opened.

Cause:  An unexpected error occurred when the
program attempted to open the protocol manager.
The IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS MAC device driver has been removed.

Action:  Check the drive and directory to ensure that
the protocol manager is located in the specified path.

---------  

LT40028: An unrecoverable error occurred while attempting to register the IBM 
Token-Ring Network 16/4 Busmaster Server Adapter/A NDIS device driver program 
with the protocol manager.

Cause:  The device driver was unable to register with
the protocol manager.

Action:  Reinstall the protocol manager and
try the operation again.

---------  

LT40029: No physical adapter was found in this machine.

Cause:  There was no adapter found in this machine.
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapters
are required to run the MAC device driver.

Action:  Install an IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter in this machine, or remove the device
driver statement from CONFIG.SYS.

---------  

LT40030: The unrecognized parameter *** was found in PROTOCOL.INI.

Cause:  An unrecognized parameter was found
while processing the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A section of PROTOCOL.INI.

Action:  Correct the parameter or remove it from
PROTOCOL.INI.

---------  

LT40031: The value specified for network address in PROTOCOL.INI is not valid.
The burned-in address will be substituted.

Cause:  The value specified for the network address parameter in
PROTOCOL.INI is not valid for one of the following reasons:

- Invalid local station address
- Too long
- Too short
- Contains non-hexadecimal characters
- Not enclosed in double quotes

Action:  Remove or correct the network address parameter
(NETADDRESS). A valid value for this parameter is 12 characters
long, is enclosed in double quotes, and contains only valid
hexadecimal characters within the range of 400000000000 through
40007FFFFFFF.

---------  

LT40033: A duplicate network address was found while inserting onto the ring.

Cause:  The network address that the adapter wants to use on the
token-ring is being used by another node.

Action:  Either modify PROTOCOL.INI to provide a different
value for the network address (NETADDRESS) parameter, use the
default burned-in address, or remove the other node that is
using this network address from the ring.

---------  

LT40034: Ring failure or beaconing was encountered while inserting onto the 
ring.

Cause:  The ring speed is different from the speed of the
node attempting to insert onto the ring.

Action:  Use the reference diskette that came with your
computer to ensure that the adapter is configured at the same
speed as the token-ring.

---------  

LT40035: A hardware failure occurred while attempting to open the adapter.

Cause:  When the adapter tried to insert onto the token-ring, a
hardware error occurred on the adapter.

Action:  Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter.  Contact
your vendor sales representative.

---------  

LT40036: A lobe media error has occurred.  Ensure that the token-ring cable is
connected to the adapter.

Cause:  While attempting to open the adapter, an indication
was received that the adapter is not properly connected to
the token-ring.

Action:  Ensure that the token-ring cable is connected to
the adapter and to the token-ring multistation access unit (MAU).

If the error persists, use a different token-ring cable
and check to ensure that the connection to the MAU is
functioning properly.  Then run the hardware diagnostics
for the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
adapter.

---------  

LT40040: This version of the microcode is not supported.

Cause:  The version of the microcode contained in MONT400.BIN
is down level.

Action:  Reinstall the microcode from the installation diskette.

---------  

LT40043: An unrecoverable error occurred during an address translation in the 
IBM Token-Ring 16/4 Network Busmaster Server Adapter/A NDIS device driver.

Cause:  This message will be displayed only when there is
an AOX adapter installed in this system.  The AOX adapter acts
as a replacement processor or a dual processor, which requires
that busmaster adapters perform extra translation of physical
addresses.  This error message can be caused by one of the
following situations:

- At initialization, when the device driver is being installed,
a block of physical memory is obtained.  If the physical
address crosses a "memory seam", this error is displayed.

- While running, the upper protocol layer provides the
device driver with a physical address.  If the physical address
crosses a "memory seam", this error is displayed.  The
device driver cannot continue to run.  The adapter is
stopped and the request from the protocol is rejected.


Action:  Restart your system and try the operation again.  If
the problem persists, reinstall the system and run diagnostics
on the AOX adapter.  If the problem continues to persist,
contact your vendor sales representative.

---------  

LT40044: The configuration values have forced the control-block size to exceed
the available memory.

Cause:  The configuration parameters specified require more space for
processing than can be handled with the available system memory.

Action:  Reduce the value specified for the MAXTRANSMITS
or MINRCVBUFFS parameter to change the amount of storage required.

Use the following formula to compute the maximum value:

H(i) = RCVAREA(i) + ALLOCSIZECB(i)

A H(i) value should be computed for each IBM Token-Ring Network 16/4
Busmaster Adapter, and the sum of all H(i) values must be less than 1 MB.

Use the following formula to compute the receive area for each adapter:
RCVAREA = MINRCVBUFFS x SIZWORKBUFF

Use the following formula to compute the control block area for each adapter.
The control block area must be less than 64KB.
ALLOCSIZECB = 334 + (142 x MAXTRANSMITS) + (20 x MINRCVBUFFS)

---------  

LT80198: The attempt to add the Multiple Link Interface Driver(MLID) protocol 
ID failed.  The ODI2NDI.OS2 cannot function.

Cause:  The attempt to add this MLID protocol ID has failed.  The IBM
NetWare* Requester Support (ODI2NDI.OS2) will not work.

Action:  You may have too many protocol IDs defined.  Delete those
protocol IDs that are not required.

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80199: The attempt to allocate memory for Virtual Boards failed. ODI2NDI.OS2
cannot function.

Cause:  The attempts by IBM NetWare* Requester Support (ODI2NDI.OS2) to
obtain memory from OS/2 failed.

Action:  Contact an IBM service representative.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80204: The Link Support Layer (LSL.SYS) is not installed.  ODI2NDI.OS2 
cannot function.

Cause:  The IBM NetWare* Requester Support (ODI2NDI.OS2) driver was unable
to locate the LSL support module.  This error usually indicates that the
NetWare* Requester is not installed.

Action:  Ensure that the NetWare* Requester is installed.  Also, verify
that the LSY.SYS driver statement is in the CONFIG.SYS file and that it
precedes the ODI2NDI.OS2 driver statement.  An example follows:

:
DEVICE=<path>\LSL.SYS
DEVICE=<path>\DDAEMON.EXE
:
DEVICE=C:\IBMCOM\ODI2NDI.OS2
:
DEVICE=<path>\IPX.SYS
:

Also ensure that the LSL.SYS driver loaded without errors.

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80208: An error occurred when ODI2NDI.OS2 tried to set the packet filter for
adapter ***.  Adapter *** cannot be used by ODI2NDI.OS2.

Cause:  IBM NetWare* Requester Support (ODI2NDI.OS2) was unable to specify
which frames to receive.

Action:  Some NDIS MAC drivers do not support setting the MAC packet
filter.  This may be the case for the NDIS MAC driver that you are using.
Also, ensure that the MAC driver has loaded and initialized properly and
that the hardware associated with the MAC driver is operational.  Check
for any messages that the MAC driver may have displayed or logged.

See the FFST/2 message log, if you are using FFST/2, or see the
LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80209: An error occurred when ODI2NDI.OS2 tried to set the lookahead size 
for adapter ***.  Adapter *** cannot be used by ODI2NDI.OS2.

Cause:  The IBM NetWare* Requester Support (ODI2NDI.OS2) has tried to specify
the amount of data in the frame that ODI2NDI.OS2 requires to be available
for interrogation of the frame.  This action will ensure that the frame
is owned ODI2NDI.OS2.

Action:  Some NDIS MAC drivers do not support the setting of this size.
This may be the case for the NDIS MAC driver that you are using.  Also,
ensure that the MAC driver has loaded and initialized properly and that
the hardware associated with the MAC driver is operational.  Check for
any messages that the MAC driver may have displayed or logged.

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80210: An error occurred when ODI2NDI.OS2 tried to set the node address for 
adapter ***.  Adapter *** cannot be used by ODI2NDI.OS2.

Cause:  The attempt by IBM NetWare* Requester Support (ODI2NDI.OS2) to set
the node address for the specified adapter was unsuccessful.  This error
might occur if another protocol, for example IBM 802.2, has set the node
address to a value different from the node address configured for
ODI2NDI.OS2.

Action:  Use the LAPS installation program to ensure that all protocols
configured to use the adapter are configured for the same node address.
If the IBM IEEE 802.2 protocol is configured to use the adapter, but only
ODI2NDI.OS2 has the node address configured, ODI2NDI.OS2 should be
configured to use the adapter's universal address.

Also, some NDIS MAC drivers do not support the setting of a local address.
This may be the case for the NDIS MAC driver that you are using.

Finally, ensure that the MAC driver has loaded and initialized properly
and that the hardware associated with the MAC driver is operational.
Check for any messages that the MAC driver may have displayed or logged.

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80211: An error occurred when ODI2NDI.OS2 tried to open adapter ***. Adapter
*** cannot be used by ODI2NDI.OS2.

Cause:  The attempt by IBM NetWare* Requester Support (ODI2NDI.OS2) to open
the specified adapter was unsuccessful.

Action:  Use the LAPS installation program to ensure that the MAC driver
has loaded and initialized properly.  Also verify that the hardware
associated with the MAC driver is operational.  Check for any messages
that the MAC driver may have displayed or logged.

See the FFST/2 message log, if you are using FFST/2, or see the
LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80213: ODI2NDI.OS2 was unable to bind to MAC ***.  Adapter *** cannot be 
used by ODI2NDI.OS2.

Cause:  IBM NetWare* Requester Support (ODI2NDI.OS2) has tried bind to the
NDIS MAC driver as specified in the current LAPS configuration but was
unsuccessful.

Action:  Use the LAPS installation program to ensure that the MAC driver
has loaded and initialized properly.  Also verify that the hardware
associated with the MAC driver is operational.  Check for any messages
that the MAC driver may have displayed or logged.

See the FFST/2 message log, if you are using FFST/2, or see the
LANTRAN.LOG file.

* NetWare* is a registered trademark of Novell, Inc.

---------  

LT80217: The OpenAdapter request to adapter *** did not complete within the 
required time limit.  Adapter *** cannot be used by ODI2NDI.OS2.

Cause:  IBM NetWare* Requester Support (ODI2NDI.OS2) tried to open the
specified adapter, but the open has not yet completed.

Action:  Ensure that the MAC driver has loaded and initialized properly and
that the hardware associated with the MAC driver is operational.  Check for
any messages that the MAC driver may have displayed or logged.

See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG

* NetWare is a registered trademark of Novell, Inc.
file.

---------  

LT80218: There is no section for ODI2NDI.OS2 in PROTOCOL.INI.  ODI2NDI.OS2 
cannot function.

Cause:  IBM NetWare* Requester Support (ODI2NDI.OS2) has not been configured
in the current LAPS configuration.

Action:  Use the LAPS installation program to configure IBM NetWare*
Requester Support or remove the ODI2NDI.OS2 device driver statement from
the CONFIG.SYS file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80219: No MAC driver bindings were specified in PROTOCOL.INI.  The 
ODI2NDI.OS2 cannot function.

Cause:  IBM NetWare* Requester Support (ODI2NDI.OS2) has not been configured
in the current LAPS configuration.

Action:  Use the LAPS installation program to configure IBM NetWare*
Requester Support.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80220: Too many MAC driver bindings were specified in PROTOCOL.INI. 
ODI2NDI.OS2 cannot function.

Cause:  The IBM NetWare* Requester Support (ODI2NDI.OS2) was configured
for too many adapters.  ODI2NDI.OS2 can be configured for a maximum of
4 adapters.

Action:  Use the LAPS installation program to decrease the number of
network adapters for which IBM NetWare* Requester Support is configured.

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80221: ODI2NDI.OS2 could not locate the Protocol Manager.  ODI2NDI.OS2 
cannot function.

Cause:  The IBM NetWare* Requester Support (ODI2NDI.OS2) could not find the
Protocol Manager (PROTMAN.OS2).

Action:  Ensure that the following statement is in your CONFIG.SYS file:

DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80222: ODI2NDI.OS2 could not access PROTOCOL.INI.  ODI2NDI.OS2 cannot 
function.

Cause:  The IBM NetWare* Requester Support (ODI2NDI.OS2) either could no find
the PROTOCOL.INI file or encountered an error while trying to open or read
this file.

Action:  Use the LAPS installation program to ensure that you have configured
at least one adapter for IBM NetWare* Requester Support.

For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80223: ODI2NDI.OS2 could not register with the Protocol Manager. ODI2NDI.OS2
cannot function.

Cause:  An error occurred when the IBM NetWare* Requester Support 
(ODI2NDI.OS2)
tried to register with the Protocol Manager.

Action:  Contact an IBM service representative.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80224: Frame type *** configured for ODI2NDI.OS2 is inconsistent with other 
frame types configured for adapter ***.  ODI2NDI.OS2 may not function as 
desired.

Cause:  The adapter is configured to use both Token-Ring and Ethernet
frame types, which is not allowed.

Action:  Use the LAPS installation program to ensure that IBM NetWare*
Requester Support for the specified adapter is configured to use
either Token Ring frame types or Ethernet frame types, but not both.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80225: The frame types configured for ODI2NDI.OS2 are not supported by 
adapter ***.  Adapter *** cannot be used by ODI2NDI.OS2.

Cause:  The frame types configured for IBM NetWare* Requester Support
(ODI2NDI.OS2) are not compatible with the MAC driver of the specified
adapter.  For example, Ethernet frame types have been configured for a
Token Ring adapter.

Action:  Use the LAPS installation program to ensure that IBM NetWare*
Requester Support for the specified adapter is configured to use
frame types that are supported by the adapter.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80226: ODI2NDI.OS2 is configured for an incorrect node address, ***. 
ODI2NDI.OS2 may not function as desired.

Cause:  The node address configured for IBM NetWare* Requester Support
(ODI2NDI.OS2) is not correct.

Action:  Use the LAPS installation program to ensure that IBM NetWare*
Requester Support is configured to use a valid node address. A valid
node address consists of 12 hexadecimal digits and may be preceded by
an I to indicate IEEE node address format or a T
to indicate 802.5 node address format.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80227: A node address was not configured for ODI2NDI.OS2 for adapter ***. 
Adapter *** cannot be used by ODI2NDI.OS2.

Cause: The node address was not configured for IBM NetWare*
Requester Support (ODI2NDI.OS2) and ODI2NDI.OS2 was unable to obtain the
node address automatically from the network adapter at boot time.

Action:  Use the LAPS installation program to configure the NETADDRESS
parameter for IBM NetWare* Requester Support.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80250: Too many parameters were specified.

Cause:  More than one parameter was specified on the NWFIXUP command
line.

Action:  Specify no more than one parameter for NWFIXUP.

---------  

LT80251: The correct syntax for the command is: [<path>]NWFIXUP [<filespec>]

Cause: More than one parameter was specified on the NWFIXUP command
line.

Action: Specify no more than one parameter for NWFIXUP.

---------  

LT80252: The filespec is not valid.

Cause: The filespec supplied as a command-line parameter is not valid.
The drive or path specification was incorrect, or the file
could not be found.

Action: Provide a valid filespec as an argument for the command.

---------  

LT80254: NWFIXUP did not complete successfully.

 Cause:  NWFIXUP encountered an error which prevented it from
completing all operations successfully.  Usually this error occurs when
you configure NetWare* Requester Support (ODI2NDI.OS2) prior to installing
the NetWare* Requester.

Action: Make sure you have the NetWare* Requester installed.  Refer to
the \OS2\INSTALL\LAPSHIST.LOG file for a more detailed description of
the error.

* NetWare is a registered trademark of Novell, Inc.

---------  

LT80255: An OS/2 error occurred while querying the current drive.

Cause:  A call to the OS/2 DosQCurDisk function returned with an error.

Action:  Contact an IBM service representative.

---------  

LT80256: An OS/2 error occurred during the attempt to query the current 
directory.

Cause: A call to the OS/2 DosQCurDir function returned with an error.

Action: Contact an IBM service representative.

---------  

LT80257: An OS/2 error occurred during the attempt to query the boot drive.

Cause: A call to the OS/2 DosGetInfoSeg function returned with an error.

Action: Contact an IBM service representative.

---------  

LT80258: The CONFIG.SYS file could not be parsed.

Cause: An error occurred during the attempt to open the CONFIG.SYS file
and read it into memory.

Action: Ensure that the CONFIG.SYS file being used is not marked as read
only and is not currently in use by any other process.  Ensure that
enough free memory (about 128KB) is available to perform the parsing
operation.

---------  

LT80259: A DEVICE= statement invoking ODI2NDI.OS2 could not be deleted from 
the CONFIG.SYS file.

Cause: A line could not be deleted from the parsed CONFIG.SYS file
image.  The line contains DEVICE = <path>ODI2NDI.OS2.

Action: Contact an IBM service representative.

---------  

LT80260: A DEVICE= statement invoking LSL.SYS was not found.

Cause: A line containing DEVICE = <path>LSL.SYS could not be located
within the parsed CONFIG.SYS file image.

Action: Ensure that the correct CONFIG.SYS file is being used.  Also,
ensure that the NetWare requester has been installed.  If the correct
file is being used, and if it contains the LSL.SYS invocation, contact
an IBM service representative.

---------  

LT80261: A DEVICE= statement invoking ODI2NDI.OS2 could not be added to the 
CONFIG.SYS file.

Cause: An error occurred during the attempt to add a line to the parsed
CONFIG.SYS file image.  The line contains DEVICE = <path>ODI2NDI.OS2.

Action: Contact an IBM service representative.

---------  

LT80262: The MLID device driver could not be disabled in the CONFIG.SYS file.

Cause: An error occurred during the attempt to disable a line in the
parsed CONFIG.SYS file image.  The REM command could not be prefixed
to the line containing DEVICE = <MLID driver>.

Action: Contact an IBM service representative.

---------  

LT80263: The CONFIG.SYS file image was not written out to disk.

Cause:  An error occurred during the attempt to replace the CONFIG.SYS
file with the revised version.

Action:  Run CHKDSK to determine whether the problem lies with the file
system.  If no disk problems are found, contact an IBM service
representative.

---------  

MAC0001: The WD8003 adapter was either not found or not specified in the 
PROTOCOL.INI file.

Cause:  There were either no entries found in the PROTOCOL.INI file for this
device driver, the adapter is not installed, or there is a hardware
problem with the adapter.

Action:  Ensure that a Standard Microsystems Ethernet adapter is
installed in this system.  Also ensure that a DRIVERNAME=  entry exists
in the PROTOCOL.INI file for the MACWD$ or MACWD2$ device driver.  Retry
the operation.  If the problem persists, contact your vendor service
representative.

---------  

MAC0002: The parameters in the PROTOCOL.INI do not match the adapter 
configuration.

Cause:  POS data or AT bus software configured adapter data does not
match the PROTOCOL.INI entry.

Action:  Correct the PROTOCOL.INI file to ensure that the configuration values
specified correspond to the adapter configuration.

---------  

MAC0003: Multiple WD8003 adapter parameters were specified in the PROTOCOL.INI
file.

Cause:  More than one entry was found in the PROTOCOL.INI file for
the MACWD$ or MACWD2$ device driver.

Action:  Ensure that DRIVERNAME entry appears only once in the
PROTOCOL.INI file.

---------  

MAC0004: The installed WD8003 adapter is not supported.

Cause:  The adapter installed in this system is not supported by
the MAC device driver.

Action:  Install a supported version of the adapter.

---------  

MAC0005: A parameter value in the PROTOCOL.INI file is out of range.

Cause:  One of the parameters in the MACWD$ or MACWD2$ section of the
PROTOCOL.INI file is out of range.

Action:  Ensure the parameter values are valid in the PROTOCOL.INI file.

---------  

NET2102: The NETWKSTA.200 requester driver is not installed.



Cause:  The required LAN software (the NETWKSTA.200 requester driver)
is not installed, or your IBMLAN.INI file or CONFIG.SYS file is incorrect.

Action:  If you installed the OS/2 operating system again, install the
LAN software again.  If you have not installed the OS/2 operating
system, verify that your IBMLAN.INI and CONFIG.SYS files are correct.


---------  

NET2103: The server cannot be located.



Cause:  The server you specified does not exist.

Action:  Verify your spelling.  You may have typed the server
machine ID incorrectly.  To see a list of available
servers in your domain, type:

        NET VIEW

Also, remember to precede machine IDs with two backslashes,
as in \\machineid.


---------  

NET2104: An internal error occurred.  The network cannot access a shared 
memory segment.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2105: A network resource shortage occurred.



Cause:  The network hardware could not access the resources it
needed.

Action:  Try the operation again later.


---------  

NET2106: This operation is not supported on requesters.



Cause:  This operation can be performed only on a LAN server.

Action:  Refer to the "OS/2 LAN Commands and Utilities" for information
regarding valid LAN Requester commands.


---------  

NET2107: The device is not connected.



Cause:  This device is not assigned to a shared resource.

Action:  First verify the spelling of the device name.

To see the local devices assigned to shared resources, type:

        NET USE



---------  

NET2114: The Server service is not started.



Cause:  The server is not started.  The server must be
started before you can run this command.

Action:  Try the command again after the server has been started.


---------  

NET2115: The queue is empty.



Cause:  You have no requests in the specified queue.


Action:  No action is needed.


---------  

NET2116: The device or directory does not exist.



Cause:  The device or directory specified is unknown.

Action:  Verify your spelling.


---------  

NET2117: The operation is not valid on a redirected resource.



Cause:  The device you specified is assigned to a shared resource.

Action:  To perform this operation on this device, you first must
end its connection to the shared resource.  To end a connection,
type:

        NET USE device /DELETE


---------  

NET2118: The netname has already been shared.



Cause:  This netname is already in use on this server.

Action:  Choose a netname that is not currently used at this server.
To see a list of resources currently shared on this server, type:

        NET SHARE


---------  

NET2119: The server is currently out of the requested resource.



Cause:  The server could not access enough of a resource, such as
memory, to complete this operation.

Action:  Try again later.  If the problem persists, stop some
unneeded processes or applications and try the operation again.
If you still have problems, you may need to reconfigure your system.


---------  

NET2121: Addition of the requested item exceeds the maximum allowed.



Cause:  You tried to create a share and no more shares are allowed,
or the list of items in the command is too long.

Action:  If you are trying to create a share, stop sharing a resource
not currently used or increase the value of MAXSHARES in IBMLAN.INI.
If IBMLAN.INI is changed, the server must be stopped and started
again for the changes to take effect.  Then try the command again.

If your command included a list of items, split the list into two
smaller lists.  Type the command using the first list and then again
using the second list.


---------  

NET2122: The peer server will support only two simultaneous users.



Cause:  This server is configured to allow a maximum of two users to
have connections to a shared resource at once.

Action:  Retype the command again, specifying two as the maximum
number of users for the resource.


---------  

NET2123: The API return buffer is too small.



Cause:  The program you are running created a buffer that is too
small for the data being used.

Action:  The program should correct this problem.  If it does not,
contact the vendor who supplied the program.


---------  

NET2127: A remote API error occurred.



Cause:  The program or command you were running on a server failed.
There may be communication problems on the network, or the
remote server may be short of resources.

Action:   Ensure that the server is configured with enough resources.
Specifically, the NUMBIGBUFS entry in the IBMLAN.INI file on the server
may need to be increased.


---------  

NET2131: An error occurred while opening or reading IBMLAN.INI.



Cause:  The IBMLAN.INI file is missing or contains information that
is not valid.

Action:  Review the contents of the IBMLAN.INI file.


---------  

NET2134: An internal error occurred while calling the requester driver.



Cause:  An internal error occurred in the NETWKSTA.200 driver.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2136: A general network error occurred.



Cause:  A general failure occurred in the network hardware.

Action:  Investigate possible problems with the network hardware.
If the problems persist, use diagnostics to verify that the network
hardware is installed and working properly.  For further assistance,
contact your hardware dealer.


---------  

NET2138: The Requester service has not been started.



Cause:  You tried to use the network before starting the
Requester service.

Action:  To start the Requester service, type:

        NET START REQUESTER


---------  

NET2140: An internal LAN software error occurred.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2141: The server is not configured for transactions.



Cause:  The specified server is not configured to accept the
command you typed.  This could be caused by a busy server or
defective network hardware.

Action:  Verify that the server is configured properly.  You may
need to share the IPC$ resource to correct this problem.


---------  

NET2142: The requested API is not supported on the remote server.



Cause:  The server does not support the API sent to it.  This error
can occur if two or more machines are not running the same version
of the LAN software.

Action:  Contact the vendor of the program that was running when the
error occurred.


---------  

NET2143: The event name is not valid.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2146: The specified component could not be found in IBMLAN.INI.



Cause:  The required information could not be located in your IBMLAN.INI file.

Action:  Verify that your IBMLAN.INI file is correct.  Ensure
that the file contains all information required to run the
LAN software and any associated applications.


---------  

NET2147: The specified parameter could not be found in IBMLAN.INI.



Cause:  A particular entry could not be located in your IBMLAN.INI file.

Action:  Verify that your IBMLAN.INI file is correct.  Ensure
that the file contains all information required to run the
LAN software and any associated applications.


---------  

NET2149: A line in IBMLAN.INI is too long.



Cause:  A line in the IBMLAN.INI file is too long.

Action:  Edit the IBMLAN.INI file.


---------  

NET2150: The printer queue does not exist.



Cause:  The queue you specified is not valid.

Action:  Verify the spelling of the queue name.

To see the list of printer queues shared on this server, type:

     NET PRINT \\serverid


---------  

NET2151: The print job does not exist.



Cause:  There is no print job matching the print job
identification number you typed.

Action:  Ensure that you typed the correct print job identification
number.  To see a list of current print jobs, type:

        NET PRINT \\serverid


---------  

NET2152: The printer destination cannot be found.



Cause:  This printer is not used by a printer queue.

Action:  Verify your spelling.


---------  

NET2153: The printer destination already exists.



Cause:  This printer has already been installed.

Action:  Ensure that you typed the correct device name.


---------  

NET2154: The printer queue already exists.



Cause:  You tried to create a printer queue with a name
already in use on this server.

Action:  Give the new queue a different name.  To see a
list of printer queues already existing on the server, type:

        NET SHARE


---------  

NET2155: No more printer queues can be added.



Cause:  The system does not have enough memory available to add
another printer queue.

Action:  To free memory, delete an existing printer queue.
Then create and share the new queue.


---------  

NET2156: No more print jobs can be added.



Cause:  The system does not have enough memory available to add
another print job.

Action:  Wait awhile, and then send the print job again.


---------  

NET2157: No more printer destinations can be added.



Cause:  The system does not have enough memory available to add
another printer.

Action:  To free memory, delete an existing printer.  Then, create
the new printer.


---------  

NET2158: This printer destination is idle and cannot accept control 
operations.



Cause:  The specified printer is not in use.


Action:  Ensure that you are referring to the correct printer.


---------  

NET2159: This printer destination request contains a control function that is 
not valid.



Cause:  An internal control function is not valid.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2160: The printer processor is not responding.



Cause:  The spooler is failing to communicate with a queue driver.


Action:  Contact your network administrator.  There may be software
problems with the queue driver or hardware problems with
the associated printer.


---------  

NET2161: The spooler is not running.



Cause:  The spooler has not been started.


Action:  Start the OS/2 print spooler.


---------  

NET2162: This operation cannot be performed on the print destination in its 
current state.



Cause:  The requested change cannot be made because a software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2163: This operation cannot be performed on the printer queue in its 
current state.



Cause:  The requested change cannot be made because a software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2164: This operation cannot be performed on the print job in its current 
state.



Cause:  The requested change cannot be made because a software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2165: A spooler memory allocation failure occurred.



Cause:  The spooler ran out of memory.


Action:  To free memory for the spooler, delete one or more printer queues
or print jobs, or remove one or more printers from all print queues on the
server.


---------  

NET2166: The device driver does not exist.



Cause:  The device driver you specified has not been installed
for the print queue.


Action:  Verify your spelling.

To use a new device driver with this print queue, you must
first install the device driver.  Refer to your base operating system
documentation for information on installing the device driver.


---------  

NET2167: The data type is not supported by the processor.



Cause:  The data type of the print job is not supported by the queue
driver for the queue.


Action:  Use a different queue driver for jobs that have this
data type, or rewrite the application so that it uses a data type
the queue driver can recognize.


---------  

NET2168: The print processor is not installed.



Cause:  The queue driver you specified has not been installed.


Action:  Install a queue driver.  Refer to your base operating
system documentation for information on installing the queue driver.


---------  

NET2180: The service does not respond to control actions.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2181: The service table is full.



Cause:  You cannot start another service, because you have reached
the maximum number of services specified in your IBMLAN.INI file.


Action:  To start another service, first stop an unneeded one.  To display
the list of services that are running, type:

        NET START

You can also change the maximum number of services allowed to run
simultaneously on the workstation by changing the value of the
NUMSERVICES entry in your IBMLAN.INI file.


---------  

NET2182: The requested service has already been started.



Cause:  You attempted to start a service that is already running.


Action:  To display a list of active services, type:

        NET START


---------  

NET2183: The service does not respond to control actions.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2184: The service has not been started.



Cause:  You tried to use a service that is not running.


Action:  To display a list of active services, type:

        NET START

To start a service, type:

        NET START service


---------  

NET2185: The service name is not valid.



Cause:  You tried to start a service with a name that is not valid.


Action:  Verify the spelling of the service name and ensure that the
specified service is appropriate to the type of workstation in use.

Valid OS/2 LAN Server services are listed in the [services] section of
the IBMLAN.INI file.


---------  

NET2186: The service is not responding to the control function.



Cause:  The service cannot run your command at this time.


Action:  Try the command again later.

If the service does not respond to commands such as NET PAUSE
and NET CONTINUE, stop and start the service again.

If the problem persists, report the problem, including the name of
the service and the command that was refused, to your IBM support
representative.


---------  

NET2187: The service control is busy.



Cause:  The service is not responding to requests now.  Another program
may be controlling the service or there may be a software problem.


Action:  Try to stop the service by typing:

     NET STOP service

If this action fails, stop all programs running on the workstation
and type the NET STOP command again.

If the problem persists, contact your IBM support representative.
Be prepared to give the name of the service and other information about
the system, such as the services and applications that were running on
the workstation, and the amount and type of network activity when the
problem occurred.


---------  

NET2188: IBMLAN.INI contains a service program name that is not valid.



Cause:  Your IBMLAN.INI file has associated a service with a
nonexistent program file.


Action:  Ensure that each entry shown in the [services]
section of your IBMLAN.INI file lists a valid path name
for the executable file for the service.


---------  

NET2189: The service cannot be controlled in its present state.



Cause:  The service is not currently accepting requests.  If the
service is starting, it cannot process requests until it is fully
started.


Action:  Try the operation again in a minute or two.

If this problem persists, the service may be stuck in a partially
running state.  Contact your IBM support representative.
Be prepared to give the name of the service and other information
about the system, such as the services and applications that were
running, and the type and amount of network activity at the time
of the problem.


---------  

NET2190: The service ended abnormally.



Cause:  The service was not running properly and would not respond to a 
command.  The service was ended.


Action:  Stop the service by typing:

     NET STOP service

Then start the service again by typing:

     NET START service

If the problem still persists, report the problem and the
method by which it can be reproduced to your IBM support
representative.


---------  

NET2191: The requested pause or stop is not valid for this service.



Cause:  This command is not valid for this service, or the service cannot 
accept the command right now.


Action:  If the service normally accepts this command, try the command again 
later.

To display a list of valid commands, type:

        NET HELP


---------  

NET2200: This requester is already logged on to the local area network.



Cause:  A user is already logged on at this requester.


Action:  To see the user ID currently logged on at the requester, type:

        NET CONFIG REQUESTER

To log that user off, type:

        LOGOFF

You can then log on.


---------  

NET2201: The requester is not logged on to the local area network.



Cause:  You must log on to the network before performing this operation.


Action:  To log on, type:

     LOGON


---------  

NET2202: The user ID or group ID parameter is not valid.



Cause:  You specified a user ID or group ID that is not valid.


Action:  Use a different user ID or group ID.


---------  

NET2203: The password parameter is not valid.



Cause:  You specified a password that is not valid.


Action:  Use a different password.


---------  

NET2204: The user ID was not added as a message name.



Cause:  Your user ID was not added as a new message name for one of the 
following reasons:

- The Messenger service is not started on your requester.

- Your user ID and your requester machine ID are the
  same, and your requester machine ID is already a
  message name.

- Your user ID is in use as a message name on another
  workstation on the network.  In this case, you cannot
  receive messages at the local requester using this name.


Action:  Start the Messenger service on your requester if it is
not already started.  Then use the NET NAME command to add your user
ID as a message name.

If your user ID is being used as a message name on another workstation,
delete the message name on that workstation.  Then use the NET NAME
command to add your user ID as a message name on this workstation.


---------  

NET2205: The user ID was not added as a message name.



Cause:  Your user ID is already established as a message name.  Either your
user ID and machine ID are the same, or your user ID is in use as a
message name on another workstation on the network.  If your user ID is
being used as a message name on another workstation, you cannot receive
messages at the local requester using this name.


Action:  If your user ID is being used as a message name on another
workstation, delete the name on that workstation.  Then log on again
at this requester.


---------  

NET2206: The message name was not deleted.



Cause:  The message name corresponding to your user ID was not
deleted.  Either your user ID is the same as the machine ID, or your
user ID is being used as a message name on some other workstation on
the network.


Action:  No action is needed.


---------  

NET2207: The message name was not deleted.



Cause:  The message name corresponding to your user ID was not
deleted because your user ID is the same as the machine ID.


Action:  No action is needed.


---------  

NET2209: Network logons are paused.



Cause:  The Netlogon service has been paused.  No one can log on until the 
Netlogon service is continued.


Action:  Continue the Netlogon service by typing:

     NET CONTINUE Netlogon


---------  

NET2210: A conflict occurred at the domain controller.



Cause:  You cannot start the Netlogon service on this server, because
a server in the domain with an earlier version of LAN Server is
running the Netlogon service.


Action:  Before you can start the Netlogon service on this server, you
must stop the Netlogon service on all servers in the domain
that are running earlier versions of LAN Server.


---------  

NET2212: An error occurred while loading or running the logon script.



Cause:  The logon script for your account may contain unrecognized commands or
commands that could not be run.


Action:  Ask your network administrator to review your logon script.


---------  

NET2214: The domain controller was not specified.  Your workstation will be 
logged on as STANDALONE.



Cause:  The logon was not validated.


Action:  No action is needed.


---------  

NET2215: The domain controller cannot be found.



Cause:  No domain controller is responding to your command.


Action:  Try the command again later.  If the problem persists, verify that 
the domain controller for your domain is running.


---------  

NET2217: The domain controller could not validate the logon.



Cause:  Your domain controller is running an earlier version of LAN Server.


Action:  No action is needed.


---------  

NET2218: The user account cannot be deleted.



Cause:  You tried to delete a user account that has been marked undeletable.


Action:  Enable the account for deletion and try the operation again.



---------  

NET2219: The accounts file NET.ACC cannot be found.



Cause:  The user accounts database, NET.ACC, could not be found.
NET.ACC is normally located in the ACCOUNTS subdirectory of
the \IBMLAN directory.


Action:  Copy a backup version of the file, NETACC.BKP, to NET.ACC.
If NETACC.BKP does not exist, restore NET.ACC from a backup
copy or from the installation diskettes.


---------  

NET2220: The group ID cannot be found.



Cause:  You specified an unknown group ID.


Action:  Verify the spelling of the group ID.  To display a list of group IDs 
established locally, type:

        NET GROUP

If you are not working at the domain controller, you must run
the NET GROUP command remotely on the domain controller to see the groups
that exist on the domain by typing:

        NET ADMIN \\domaincontrollerid /C NET GROUP


---------  

NET2221: The user ID cannot be found.



Cause:  You specified an unknown user ID.


Action:  Verify the spelling of the user ID.  To display a list of the user 
IDs established locally, type:

        NET USER

If you are not working at the domain controller, you must run
the NET USER command remotely on the domain controller to see the users
that exist on the domain by typing:

        NET ADMIN \\domaincontrollerid /C NET USER


---------  

NET2222: The resource name cannot be found.



Cause:  You tried to access the permissions for a resource that is not in the 
user accounts database.


Action:  Verify the spelling of the resource.

Before you can assign user permissions for a particular resource,
you must create an access control profile for that resource by typing:

     NET ACCESS resource /ADD


---------  

NET2223: The group already exists.



Cause:  You tried to create a group with a group ID that already exists.


Action:  Use a different group ID for the new group.  To display a list of 
group IDs established locally, type:

        NET GROUP

If you are not working at the domain controller, you must run
the NET GROUP command remotely on the domain controller to see the
groups that exist on the domain by typing:

        NET ADMIN \\domaincontrollerid /C NET GROUP


---------  

NET2224: The user account already exists.



Cause:  You tried to create a user account with a user ID that already exists.


Action:  Use a different user ID for the new user.  To display a list of user 
IDs established locally, type:

        NET USER

If you are not working at the domain controller, you must run
the NET USER command remotely on the domain controller to see the
users that exist on the domain by typing:

        NET ADMIN \\domaincontrollerid /C NET USER


---------  

NET2225: The resource permission list already exists.



Cause:  You tried to create an access control profile for a resource that 
already has one.


Action:  To display the list of resources on this server that have access 
control profiles, type:

        NET ACCESS


---------  

NET2226: Because the user accounts database is replicated from the domain 
controller, updates are not allowed locally.



Cause:  The specified server is not the domain controller, so you cannot 
update its user accounts database.


Action:  Run your command on the domain controller.  You can determine the 
workstation that is the domain controller by typing:

     NET ACCOUNTS

The domain controller will have its role set to PRIMARY.


---------  

NET2227: The user accounts database has not been started.



Cause:  The user accounts database is not active.  This database must be 
active for the command to run.


Action:  The user accounts database should have started when the
Requester service started.  Look at the error log to determine why it was
not started.


---------  

NET2228: There are too many names in the user accounts database.



Cause:  The user accounts database is full.  The limit for groups that
the administrator can create is 251.  The limit for access control lists
(ACLs) the administrator can create is 8192.  Each ACL is limited to 64
permissions (a permission consists of the user/group name and the list
of their access rights).  The total cache size for all the ACLs is 1MB
because resource names and permissions are cached in memory.


Action:  Free space in the database by deleting users, groups, and
resource permissions.

To delete a user, type:

     NET USER userid /DELETE

To delete a group, type:

     NET GROUP groupid /DELETE

To delete permissions for a resource, type:

     NET ACCESS resource /DELETE


---------  

NET2229: A disk I/O to access the user accounts database failed.



Cause:  A software error occurred when an attempt was made to access the user 
accounts database, (NET.ACC).


Action:  Type the command again.  If the problem persists, you may have a 
faulty disk drive or a corrupted NET.ACC file.  A corrupted NET.ACC file 
should be restored from a backup NET.ACC file.


---------  

NET2230: The limit of 64 entries per resource was exceeded.



Cause:  Each resource can have no more than 64 access control profile records 
defined.


Action:  Put the users into groups and specify permissions for the groups 
rather than for each user.


---------  

NET2231: Deleting a user with a session is not allowed.



Cause:  The user currently has a session with the server.


Action:  The session must be ended before you can perform this task.


---------  

NET2232: The parent directory cannot be located.



Cause:  The parent directory has no access control profile in the user 
accounts database.


Action:  Create an access control profile assigning permissions for this 
resource.


---------  

NET2233: The cache for the user accounts session could not be increased.



Cause:  The user accounts database has reached its size limit.  Nothing can be
added to it.


Action:  No action is needed.


---------  

NET2234: This operation is not allowed on this special group.



Cause:  You cannot perform this task on special groups such as USERS, ADMINS, 
and GUESTS.


Action:  No action is needed.


---------  

NET2235: This user is not in the cache for the user accounts session.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2236: The user already belongs to this group.



Cause:  The user you are trying to add to this group is already
a member.


Action:  No action is needed.


---------  

NET2237: The user does not belong to this group.



Cause:  This user is not a member of this group.


Action:  To see a list of users in this group, type:

     NET GROUP groupid


---------  

NET2238: This user account is undefined.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2239: This user account has expired.



Cause:  Only a network administrator can access an expired account.


Action:  The network administrator must reinstate this account
before the action you specified can be taken.


---------  

NET2240: The user is not allowed to log on at this requester.



Cause:  You are not allowed to log on at this requester.


Action:  If you need to log on at this requester, have your
network administrator change the logon requesters listed in
your account.


---------  

NET2241: The user is not allowed to log on at this time.



Cause:  You are not allowed to log on at this time of day.


Action:  If you need to log on at this time of day, have
your network administrator change the logon hours listed
in your account.


---------  

NET2242: This user's password has expired.



Cause:  Your password has expired.  You will not be able to perform any 
network tasks until you change your password.


Action:  To change your password in the requester domain, type:

 NET PASSWORD userid oldpassword newpassword

To change your password on another domain, type:

 NET PASSWORD /DOMAIN:name userid oldpassword newpassword


---------  

NET2243: This user's password cannot change.



Cause:  You cannot change your password.


Action:  See your network administrator if you want your password changed.


---------  

NET2244: This password cannot be used now.



Cause:  You cannot use a password that has just expired.  Your network
administrator may also have configured your account so that you cannot
use any of your previous passwords.


Action:  Use a password that you have not used before.


---------  

NET2245: The password is shorter than required.



Cause:  The password you specified is not long enough.


Action:  Use a longer password.  See your network administrator for the 
required length for passwords on your system.


---------  

NET2246: This user's password is too recent to change.



Cause:  You cannot change your password again for a certain length of time.


Action:  No action is needed.  See your network administrator to find out the 
length of time that you must use your current password.


---------  

NET2247: The user accounts database file is damaged.



Cause:  The user accounts database file, NET.ACC, is damaged.


Action:  Copy a backup version of the file, NETACC.BKP, to NET.ACC.
If NETACC.BKP does not exist, restore NET.ACC from a backup copy
or from the installation diskettes.


---------  

NET2248: No updates are necessary to this user accounts database because it 
has been synchronized with the domain controller.



Cause:  A server requested an update of the user accounts database, even 
though no update was required.


Action:  No action is needed.


---------  

NET2249: This user accounts database is outdated because it no longer is 
synchronized with the domain controller.  Synchronization is required.



Cause:  The user accounts database for the additional server is
completely out of synchronization with that of the domain controller.
A complete synchronization is needed.


Action:  Stop the Netlogon service on this workstation by typing:

     NET STOP NETLOGON

Then start it again with the UPDATE option set to YES by typing:

     NET START NETLOGON /UPDATE:YES


---------  

NET2250: The connection cannot be found.



Cause:  Either this network connection does not exist or it is paused.


Action:  To display a list of shared resources that your workstation
is connected to, type:

        NET USE

If the connection is paused, continue the connection by typing:

        NET CONTINUE REQUESTER


---------  

NET2251: This asg_type is not valid.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2252: This device is currently being shared.



Cause:  The device you tried to assign to a shared resource represents a local
device that is being shared.


Action:  Select another device or stop sharing the device that is represented 
by the device you specified.

To display a list of resources shared by this server, type:

        NET SHARE

To stop sharing a device, type:

        NET SHARE device /DELETE


---------  

NET2270: A machine ID has not been configured.



Cause:  A network service cannot determine the name of the workstation.

Action:  Verify that the COMPUTERNAME parameter in the IBMLAN.INI file
contains a valid workstation name.  If this error persists, contact your IBM
support representative.


---------  

NET2271: The Messenger service is already started.



Cause:  You tried to start the Messenger service, but it is already
running.

Action:  No action is needed.


---------  

NET2272: The Messenger service failed to start.



Cause:  The initialization sequence of the Messenger service failed,
so the service could not start.

Action:  Check the error log for error messages related to the
Messenger service failing to start.  This problem may be related to
the way your requester or server is configured, or to hardware or
software errors.


---------  

NET2273: The message name cannot be found on the local area network, or the 
receiving workstation may be busy.



Cause:  This message name cannot be located.

Action:  Verify the spelling of the message name.  If it is correct,
the workstation that is to receive your message may be busy or the
Messenger service is not started.  Try sending the message again later.


---------  

NET2274: This message name has already been forwarded.



Cause:  A message name can only be forwarded once, and messages for
this name have already been forwarded.

Action:  To stop forwarding messages for a message name, type:

 NET FORWARD name /DELETE


---------  

NET2276: This message name already exists locally.



Cause:  You tried to add a message name that already exists on this
workstation.

Action:  Use a different name if you want to add a new message name.

To display the list of names on this workstation, type:

     NET NAME


---------  

NET2277: The maximum number of added message names has been exceeded.



Cause:  The maximum number of message names on each workstation is
limited by the LAN configuration parameters and the system hardware.
You have reached the limit of one of these.

Action:  Try increasing the number of messaging names of the NET1
statement in the IBMLAN.INI file.  It may also be necessary to increase
the NAMES parameter in the [netbeui] section of the PROTOCOL.INI file.
If the hardware limit is reached, no additional action is possible.



---------  

NET2278: The machine ID cannot be deleted.



Cause:  You cannot delete a message name that is also a machine ID.

Action:  No action is needed.


---------  

NET2279: Messages cannot be forwarded back to the same requester.



Cause:  You cannot forward a message to yourself at your own
requester.

Action:  No action is needed.


---------  

NET2280: An error occurred in the domain message processor.



Cause:  An error occurred while the requester was receiving or processing
a domain-wide message.

Action:  Investigate the requester error log.  Stop and start the
Messenger service again.  If the problem persists, contact your network
administrator.


---------  

NET2282: The message was sent, but not received.



Cause:  The remote workstation was unable to receive your message.  The
Requester or Messenger service may not be running on that workstation, it
may have been receiving another message as yours arrived, or its
message buffer may be too small.

Action:  Send your message again later.

If the error persists, do the following:

  1. Verify that the Requester and Messenger services are started
     on the remote workstation.

  2. Consult with your network administrator about increasing the
     SIZMESSBUF parameter in your IBMLAN.INI file.



---------  

NET2283: The message name is currently in use.  Try again later.



Cause:  The workstation to which you tried to send a message was receiving
another message.  A workstation can receive only one message at a time.

Action:  Send the message again later.


---------  

NET2284: The Messenger service has not been started.



Cause:  The Messenger service must be running for you to use this command.

Action:  To start the Messenger service, type:

 NET START MESSENGER


---------  

NET2285: The name is not on the local workstation.



Cause:  You tried to delete a message name that is not on
your workstation.

Action:  To display a list of message names on your workstation, type:

 NET NAME


---------  

NET2286: The forwarded message name cannot be found on the network.



Cause:  This name no longer exists on the requester that was receiving its
forwarded messages.  The name may have been deleted at that requester, or
the requester may have been started again.

Action:  To continue forwarding messages to this name, type:

 NET FORWARD name1 name2

where name1 is the messaging name originally intended to receive incoming
            messages and
      name2 is the message name to receive and forward messages.



---------  

NET2287: The message name table on the remote workstation is full.



Cause:  The requester to which you are trying to forward the
message name has no room for new names.

Action:  Consult the user on that requester to see if an existing name can
be deleted so that yours can be added, or forward your name to a different
requester.


---------  

NET2288: Messages for this name are not currently forwarded.



Cause:  Messages for this name are not being forwarded.

Action:  No action is needed.


---------  

NET2289: The broadcast message was truncated.



Cause:  The broadcast message was too long.  Only the first
128 bytes of the message were sent.

Action:  Keep broadcast messages to 128 bytes or less.


---------  

NET2294: This is not a valid device.



Cause:  You typed a command or ran a program that specified a
device that is not valid.

Action:  If you specified the device, ensure that it is valid
and that you have typed it correctly.  If a program specified
the device, consult the program documentation.


---------  

NET2295: A write fault occurred.



Cause:  The Messenger service found an error while writing to
the message log file.  The error may have been caused by a full
disk, a disk error, the file being locked by another process, or
by any other situation that would cause an error while writing
to a file.

Action:  If the disk is full, free space on it by deleting unnecessary
files and directories.

Then verify that the message log file is accessible and turn on message
logging by typing:

       NET LOG /ON


---------  

NET2297: A duplicate message name exists on the local area network.



Cause:  The message name you tried to add is already in use on
the network.

Action:  Use a different message name.


---------  

NET2298: This message name will be deleted later.



Cause:  Some hardware configurations have a delay between the typing of a
command and the deletion of a name.

Action:  No action is needed.  The deletion will occur soon.


---------  

NET2299: The message name was not successfully deleted from all networks.



Cause:  The message name could not be deleted from all networks
of which this workstation is a member.

Action:  If this error occurs frequently, it probably indicates
that another user is also deleting this message name from the
network.  Try to determine who the other user is and resolve the
conflict.


---------  

NET2300: This operation is not supported on workstations with multiple 
networks.



Cause:  You cannot run this command on a workstation that is on multiple
networks.

Action:  No action is needed.


---------  

NET2301: Directory limits are not enabled on the specified volume.



Cause:  The action you attempted requires that support for directory
limits be enabled on the specified volume.

Action:  Enable support for directory limits on the volume and try the
operation again.  This is an administrative function.  Use the following
command to perform the operation:

   NET DASD volume /ENABLE

For more information on NET DASD commands, type:

   NET HELP DASD


---------  

NET2302: Directory limits are already enabled on the specified volume.



Cause:  You attempted to enable support for directory limits on a
volume that already supports them.

Action:  No action is needed.


---------  

NET2303: The directory is not on a volume that supports directory limits.



Cause:  You have attempted an operation that is only valid for resources
on volumes that are managed by 386 HPFS or by JFS.

Action:  Try the operation again, specifying a directory that resides on
a volume that is managed by 386 HPFS or by JFS.


---------  

NET2304: The supplied directory limit is smaller than the current directory 
size.  The limit was not applied.



Cause:  The directory size exceeds the value specified as the directory
limit.

Action:  Perform one of the following:

- Specify a limit that is larger than the current directory size.
- Use the following parameter to apply a directory limit that is smaller
  than the directory's current size:

    /VALIDATE:NO

  No write operations are allowed until the directory size is less than
  the limit.


---------  

NET2305: The command has completed.  Because some files are locked, you must 
shut down and restart your workstation.  You can set directory limits on this 
volume after you restart the workstation.



Cause:  The server cannot complete the command because the volume
is currently locked or in use by another process.

Action:  When the workstation is shut down and then restarted, the
process will complete.  It is not necessary for the workstation to be
shut down and restart immediately; however, the requested operation will
not take effect until after the worktation has been shutdown and
restarted.


---------  

NET2306: The directory limit was not found.



Cause:  You attempted to change, delete, or obtain information about a
directory that has no limit associated with it.

Action:  Use the following command to add a limit for the resource:

     NET DASD /ADD


---------  

NET2307: The directory limit already exists.



Cause:  You attempted to add a limit to a directory that already has one.

Action:  Use the following command to change the existing limit for the
resource:
     NET DASD <directory> /MAX

Use the following command to delete the limit:

     NET DASD <directory> /DELETE

For more information on the NET DASD commands, type:

     NET HELP DASD


---------  

NET2308: The file system failed to enable directory limits on the specified 
volume.



Cause:  The NET DASD operation failed because of a disk or memory error.
The volume cannot support directory limits.

Action:  Use the NET ERROR command to examine the error log on the server
to determine the cause of the error.


---------  

NET2309: The directory limits command failed.  You have enabled your 
workstation to set directory limits.  You must shutdown and restart your 
workstation before attempting the directory limits command.



Cause:  The NET DASD operation failed because support for directory limits
has been enabled but is not yet operational.  Directory limits operations
on this volume cannot be performed until support for directory limits is
operational.

Action:  Shut down and restart the workstation.  It is not necessary for the
workstation to be shut down and restarted immediately; however, directory
limit support will not become operational until after the workstation has
been shut down and restarted.


---------  

NET2310: This shared resource does not exist.



Cause:  The netname you specified does not exist.


Action:  Verify the spelling of the netname.

To display a list of resources shared on the server, type:

     NET SHARE


---------  

NET2311: This device is not shared.



Cause:  The device you specified is not shared.


Action:  Verify the spelling.

To share the device, type:

        NET SHARE netname=device


---------  

NET2312: A session with that machine ID does not exist.



Cause:  The specified workstation does not have a session with the server.


Action:  Verify the spelling of the machine ID.

To display a list of requesters and users that have sessions with
the server, type:

        NET SESSION


---------  

NET2314: There is not an open file with that ID number.



Cause:  There is no open file on the server corresponding to the
number you specified.


Action:  Verify the ID number of the open file.  To display a list
of open files and their ID numbers, type:

        NET FILE


---------  

NET2315: A failure occurred while processing a remote administration command.



Cause:  The command cannot run on the remote server.  The
DosExecPgm API failed.  There is either a problem with the
configuration of the operating system on the server or there
is not enough memory.


Action:  Verify that the configuration of the operating system
is correct.  Close open sessions to free memory.


---------  

NET2316: A failure occurred while opening a remote temporary file.



Cause:  The command failed because it could not open a temporary file
on the server.  The most likely cause is a shortage of disk space for
the IBMLAN tree on the remote server.


Action:  Verify that the IBMLAN tree has sufficient free disk space.
If the problem persists, investigate other resources that might
affect the server ability to open files, such as MAXOPENS and
MAXSESSOPENS, in IBMLAN.INI.


---------  

NET2317: The data returned from a remote administration command has been 
truncated to 64KB.



Cause:  The maximum amount of data that can be returned by a
remote command is 64KB.  The data from the last command exceeded
that limit.


Action:  Run the command locally on the server by either going to
the server or using the NET RUN command.


---------  

NET2318: This device cannot be shared as both a spooled and a nonspooled 
resource.



Cause:  You cannot route requests from both a printer queue and a
serial device queue to the same device.


Action:  To assign this device to a printer queue, you must first
remove it from all serial device queues.

To assign the device to a serial device queue, you must remove it
from all printer queues.


---------  

NET2319: The information in the list of servers may be incorrect.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2320: The workstation is not active on this domain.



Cause:  Your workstation is not active on the domain you specified.


Action:  To perform this task on this domain, you must add the
domain to the list of domains of which your requester is a
member by typing:

     NET CONFIG REQUESTER /OTHDOMAINS:domain


---------  

NET2321: The redirection of *** to *** cannot be deleted because it is not 
associated with application ***.



Cause:  An attempt was made to delete an assignment of an alias or a
        device that is not associated with the application definition.

Action: Verify that the alias name is valid.  Verify that the device
        that was typed is paired with the alias name that was specified.


---------  

NET2322: The *** parameter specifies a local path.  The specified path must 
exist on each machine that runs the application.



Cause:  A directory that resides on the local machine was specified as
           the location of an application or as its working directory.

Action: Ensure that the directory exists on every machine that will run
        the application.  Alternatively, change the directory to indicate
        a remote directory on a server by specifying an alias followed by
        a remaining path (if any).


---------  

NET2323: One or more logon assignments was not made because one or more of the
devices you specified is already assigned to another resource.



Cause:  One or more logon assignments specified with the /ASSIGN
        parameter contained an error.  The assignments specified
        devices that are already assigned to an alias other than the
        ones specified.  Erroneous assignments were not assigned to
        the user.  Assignments without errors were assigned to the
        user.

Action: Ensure that all command line specifications are typed correctly.
        To ensure that subsequent logon assignments do not use devices
        that are already assigned, use the following command to view
        the user's current assignments:

            NET USER userid


---------  

NET2324: At least one of the assignments you tried to delete using the 
/UNASSIGN parameter does not exist.



Cause:  At least one assignment specified with the /UNASSIGN parameter
        does not exist.  The deletion of these assignments failed.
        Unassignments of existing assignments were completed successfully.

Action: Ensure that all command line specifications are typed correctly.
        The user's current assignments may be displayed with the
        command:

            NET USER userid


---------  

NET2325: The user definition was added successfully.  However no assignments 
were made for this user because of the following error:  ***.



Cause:   The new user definition was created successfully, but
         assignments for the user could not be made because an error
         occurred.  The error code is displayed.  Some possible causes
         for the error include:

         - A non-existant alias was specified as a logon assignment.
         - A non-existant application was specified as an application
           assignment.
         - A logon assignment was specified where the device is
           inappropriate for the alias type.  For example, LPT3 cannot
           be specified as the device for a files alias.
         - Errors may have occurred when the user's domain control
           database files were created.  One or more files may be
           missing or damaged.

Action:  Ensure that all command line specifications are typed correctly.
         For logon assignments, ensure that alias definitions exist for
         all specified aliases and that the device associated with the alias
         is an appropriate type.  For application assignments, ensure that
         application definitions exist for the specified applications and
         that the application type is correct.  To get more
         information about the error, type

           HELP message#

         where message# is the error code.


---------  

NET2326: Assignment changes could not be made for this user because the 
following error occurred:  ***.  Any other changes to the user definition were
completed successfully.



Cause:  An error occurred when adding or changing an assignment for a
        user.  The error code is displayed.  Some possible causes for the
        error include:

         - A non-existant alias was specified as a logon assignment.
         - A non-existant application was specified as an application
           assignment.
         - A logon assignment was specified where the device is
           inappropriate for the alias type.  For example, LPT3 cannot be
           specified as the device for a files alias.
         - The user's domain control database files may be missing or
           damaged.

Action: Ensure that all command line specifications are typed correctly.
         For logon assignments, ensure that alias definitions exist for
         all specified aliases and that the device associated with the alias
         is an appropriate type.  For application assignments, ensure that
         application definitions exist for the specified applications and
         that the application type is correct.  To get more
         information about the error, type

           HELP message#

         where message# is the error code.


---------  

NET2327: This is domain-specific information that is only available at 
servers.



Cause:  When the NET USER <userid> command is issued at a requester,
        user information is obtained from the NET.ACC file at the local
        workstation, which only contains locally defined users.  Logon
        assignment and application assignment information is
        domain-specific; it can only be obtained when this command is
        issued at a server.

Action: No action is needed if local user information was desired.  If
        logon assignment or application assignment information about
        this user is desired, do one of the following:

        - Issue the following command at a server:

            NET USER userid

        - Issue the following command from a requester:

            NET ADMIN \\servername /C NET USER userid

          where \\servername specifies the domain controller of a domain
          where userid is defined.


---------  

NET2328: The logon assignment was not successful.  The limit has been reached.



Cause:  One or more of the following occurred:

        - More than 23 files assignments were specified.
        - More than 9 printer assignments were specified.
        - More than 9 serial device assignments were specified.

Action: Specify no more than 23 files assignments, 9 printer
        assignments, and 9 serial device assignments.


---------  

NET2329: Critical OS/2 files may not exist to set LAN Server directory limits.

Before you can set directory limits, you must apply the appropriate IBM OS/2 
FIXPAK.  Contact your IBM dealer representative or your service and support 
group for these OS/2 FIXPAKs.

Select Help for further information.

Cause:  If you have OS/2 2.1 or 2.11 installed on your workstation,
you may not have the versions of two critical OS/2 files, OS2BOOT and
UHPFS.DLL, that allow you to set LAN Server directory limits.  Setting
directory limits within OS/2 2.0 is not supported.

Action:  Before you can set LAN Server directory limits, do the following:

1. Identify which version of OS/2 you are using by typing the following
   command at the OS/2 command prompt:  VER

2. If you have not already installed a FIXPAK with more recent OS2BOOT and
   UHPFS.DLL fixes, contact your IBM dealer representative or your service and
   support group for these IBM OS/2 FIXPAKs.
      If you have OS/2 2.10 request:  IBM OS/2 2.10 FIXPAK - PJ10428.
      If you have OS/2 2.11 request:  IBM OS/2 2.11 FIXPAK - PJ13619.
   Follow the instructions in the README.1ST file on the FIXPAK diskette.

WARNING:
   Do not type the following command unless you have successfully installed
   this IBM OS/2 FIXPAK or unless you have a more recent FIXPAK.  If you type
   the command DLIMFIX and attempt to set LAN Server directory limits without
   the proper OS/2 FIXPAK, YOU WILL COMPLETELY DISABLE YOUR OS/2 OPERATING
   SYSTEM, no programs will work, and no files can be accessed.

3. After installing the correct IBM OS/2 FIXPAK, at the OS/2 command prompt,
   type the following command:  DLIMFIX

4. Stop all running applications, shut down your workstation, and restart your
   workstation for the changes to take effect.  You are now ready to set the
   LAN Server directory limits.

---------  

NET2331: The operation is not valid for this device.



Cause:  The command cannot be used on a serial device queue.


Action:  Refer to the "OS/2 LAN Commands and Utilities" for information
on the command you used.


---------  

NET2332: This device cannot be shared.



Cause:  The device you typed does not represent a valid local
device that can be shared.


Action:  Select a valid device.


---------  

NET2333: This device was not open.



Cause:  You tried to purge an empty serial device queue.


Action:  No action is needed.


---------  

NET2334: This device list is not valid.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2335: The queue priority is not valid.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2337: There are no shared serial devices.



Cause:  The server is not sharing any serial device queues,
so the command you typed is not valid.


Action:  No action is needed.


---------  

NET2338: The queue you specified does not exist.



Cause:  The netname you typed does not exist.


Action:  Verify your spelling.

To see a list of valid serial device queues for the server, type:

        NET COMM machineid


---------  

NET2340: This list of devices is not valid.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2341: The requested device is not valid.



Cause:  The device is not valid because it does not represent
a physical device or because the device hardware is faulty.


Action:  Verify your spelling, and then try the command again.

If the problem persists, use diagnostics to verify that the
device hardware is properly installed and working.  For more
assistance, contact your hardware dealer.


---------  

NET2342: This device is already in use by the spooler.



Cause:  This device is used with a printer queue.  You cannot
use a device with both printer queues and serial device queues.


Action:  To use this device with a serial device queue, you
must first disconnect all printer queues from it.


---------  

NET2343: This device is already in use as a serial device.



Cause:  This device is used with a serial device queue.
You cannot use a device with both serial device queues and
printer queues.


Action:  To use this device with a printer queue, you must
disconnect all serial device queues from it.


---------  

NET2351: This machine ID is not valid.



Cause:  An internal record of a machine ID was not valid.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2354: The string and prefix specified are too long.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2356: This path component is not valid.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2357: The type of input cannot be determined.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2362: The buffer for types is not big enough.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2377: This log file exceeds the maximum defined size.



Cause:  The log file is too large.

Action:  Clear the log file or increase the MAXERRORLOG entry
in the IBMLAN.INI file on your workstation.



---------  

NET2378: This log file has changed between reads.



Cause:  You cannot begin reading the log file from the previously
established position because the log file has changed since the
last time you read it.


Action:  You can read the log file again from the beginning.


---------  

NET2379: This log file is damaged.



Cause:  The log file is damaged.


Action:  Copy the file to another file name if you will need it
later.  Then start a new log file.  To start a new audit trail file,
type:

     NET AUDIT /DELETE

To start a new error log, type:

     NET ERROR /DELETE


---------  

NET2380: The source path cannot be a directory.



Cause:  The source path you typed is a directory name, which is not
allowed.


Action:  You must include a file name or wildcard character (? or *)
in the path name.

To copy all files in a directory, type:

        COPY [source-path]\*.* destination-path


---------  

NET2381: The source path is not valid.



Cause:  You referred to a nonexistent drive, directory, or
file name, or you typed the command incorrectly.


Action:  Verify the spelling of the source or path name you typed.
Remember to precede machine IDs with two backslashes, as in \\machineid.


---------  

NET2382: The destination path is not valid.



Cause:  The destination path name does not exist.


Action:  Verify your spelling.


---------  

NET2383: The source and destination paths are on different servers.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2385: The run server you requested is paused.



Cause:  You tried to run a program or command on a server that
is paused.


Action:  The server must be continued using the command
NET CONTINUE SERVER for your command to run.


---------  

NET2389: An error occurred while communicating with a run server.



Cause:  A problem was detected while trying to complete the operation.


Action:  Type the command again in a few minutes.  If you continue
to receive this message, investigate possible problems at the
server or on the network.


---------  

NET2391: An error occurred while starting a background process.



Cause:  A problem was detected while trying to complete the operation.


Action:  Type the command again in a few minutes.  If you continue to
receive this message, investigate possible operating system problems.


---------  

NET2392: The shared resource you are connected to could not be found.



Cause:  A problem was detected while trying to complete the operation.


Action:  Type the command again in a few minutes.  If you
continue to receive this message, investigate possible
problems at the server or on the network.


---------  

NET2400: The LAN adapter number is not valid.



Cause:  The LAN adapter number in the IBMLAN.INI file is incorrect.


Action:  Correct the appropriate NETn entry in the [networks]
section of the IBMLAN.INI file.


---------  

NET2401: There are open files on the connection.



Cause:  You tried to delete an active connection.  There
are open files or requests pending on this connection.


Action:  Close all files and end all programs related to the
connection before you try to delete it.


---------  

NET2402: Active connections still exist.



Cause:  You tried to delete a network connection that has an
active process, or you tried to log off while you have an active
process.


Action:  Ensure that the processes running on a server are
completed before you break the connection to that server.  Ensure
that processes on all remote servers are completed before you log off.


---------  

NET2403: This netname or password is not valid.



Cause:   You typed an incorrect password or netname.


Action:  Verify your spelling.  Verify that the password or the
netname is valid on the server you are trying to contact and that
you have access to the resource.

Contact the administrator of the server to which you want to connect.
Ensure that your user ID and password are correct and that you have
access to the netname for the resource you want to connect to.


---------  

NET2404: The device is being accessed by an active process.



Cause:  The drive letter you specified is the current drive of
a screen session.


Action:  Ensure that the drive you are trying to delete is not the
current drive in any of your screen sessions.


---------  

NET2405: The drive letter is in use locally.



Cause:  You tried to assign a local drive letter to a shared resource.


Action:  Use a drive letter that does not correspond to a local drive.

---------  

NET2406: Logoff failed; a device cannot be disconnected.



Cause:  The printer and serial device redirection has been paused by the
NET PAUSE REQUESTER command.  Paused devices cannot be disconnected until
the Requester service is continued.

Action:  Continue the Requester service by typing:

        NET CONTINUE REQUESTER

---------  

NET2407: A network application has tried to write to a named pipe buffer that 
is full.  This can cause delays in the application.



Cause:   A network application has tried to write to a named pipe
buffer that is full.  This can cause delays in the application.

Action:  The developer of the named pipe application may want to increase
the size of the buffers specified when the named pipe is created.

---------  

NET2412: The redirector could not establish a bandwidth-managed session.



---------  

NET2413: The bandwidth-managed session was disconnected.



---------  

NET2414: There is insufficient network bandwidth to perform this operation.



---------  

NET2415: Frames have been dropped.



---------  

NET2430: The specified importer is already registered for the specified event.



Cause:  A program requested to be notified by the alerter of
an event for which it is already receiving notifications.

Action:  Contact your network administrator.


---------  

NET2431: The Alerter service table is full.



Cause:  The number of alert notifications requested exceeded the
number specified by the NUMALERTS entry in the IBMLAN.INI file.

Action:  Increase the value of the NUMALERTS entry.  Then stop
and start the Requester service again.


---------  

NET2432: An incorrect or nonexistent alert name was raised.



Cause:  An attempt to generate an alert notification failed
because the Alerter service is not started or it is no longer
accepting one or more alert events.

Action:  Stop and start the Alerter service again.  If this
problem persists, report the problem and the method by which
it can be reproduced to your IBM support representative.


---------  

NET2433: The Alerter service recipient is not valid.



Cause:  A program has attempted to register an alert event using an
undefined mailslot ID.

Action:  Verify that the Alerter service is started.  If this error
occurs while the Alerter service is started, stop and start the
Alerter service again.  If the error persists, report the problem
and the method by which it can be reproduced to your IBM support
representative.


---------  

NET2434: A user's session with this server has been ended because the user's 
logon time has expired.



Cause:  A user's session with this server was ended because the user's logon 
time expired.

Action:  No action is needed.  To define the times during which a user
can use the server, type:

     NET USER userid /TIMES:times


---------  

NET2440: The log file does not contain the requested record number.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2450: The user accounts database is not configured correctly.



Cause:  The user accounts database is not configured properly. There
may be a conflict between the /ROLE option, which defines how this
server participates in logon security, and the server record of
the name of the primary domain controller.

For example, the role of this workstation may be set to PRIMARY while
the primary domain controller entry names a different server.


Action:  Stop the Netlogon service by typing:

     NET STOP NETLOGON

Set the server role by typing:

     NET ACCOUNTS /ROLE:role

Start the Netlogon service again by typing:

     NET START NETLOGON


---------  

NET2451: This operation is not permitted when the Netlogon service is running.



Cause:  You cannot perform this task while the Netlogon service is
running.


Action:  To perform this task, stop the Netlogon service on the server.
Type the command again and then start the Netlogon service again.


---------  

NET2452: This operation is not allowed on the last account with administrator 
privilege.



Cause:  This is the only account with administrator privilege.
You cannot delete it.


Action:  You must add another account with administrator privilege
before deleting this one.


---------  

NET2453: The domain controller for this domain cannot be found.



Cause:  The domain name is not valid, or the domain controller is not
running in this domain.


Action:  Verify that you have spelled the domain name correctly.  Verify
that the domain controller is running in this domain.  Verify that the
Netlogon service is running on the domain controller in this domain.


---------  

NET2454: Logon information for this user cannot be set.



Cause:  The domain controller could not update the logon or logoff
information.


Action:  Stop and start the Netlogon service again at the domain
controller.


---------  

NET2455: The Netlogon service has not been started.



Cause:  The Netlogon service is not running.


Action:  Start the Netlogon service at the server, and then type the
command again.


---------  

NET2456: No more information can be added to the user accounts database.



Cause:  The user accounts database cannot be enlarged because the
server hard disk is full.


Action:  Remove unnecessary and outdated files from the server disk.


---------  

NET2458: A password mismatch has been detected.



Cause:  Your local password no longer matches your password on the server
you tried to contact.  You may have changed your password since your last
logon or you may have logged on with a password when no password was
required.

Action:  Log off and log on again with the correct password.


---------  

NET2459: The maximum number of bad password retries has been exceeded.



Cause:  Your user account is no longer active. The maximum number of
bad passwords allowed has been exceeded.

Action:  Contact your network administrator.


---------  

NET2460: The server ID does not specify a valid server.



Cause:  The server name does not specify a valid server.  There
is no server with that server name in the additional server
table.

Action:  Ensure that you are using the correct server name.


---------  

NET2461: The session ID does not specify a valid session.



Cause:  The session is not valid.  There was no session with that
identification in the session table for the specified server.

Action:  Ensure that you are using the correct server.  The
session is the software link between the requester and the server
that shares the resources.  Verify the link by ensuring you have
permission for the requested resource.  Verify the physical
connection between your workstation and the server where the resource
is located.  If the problem persists, contact your IBM support
representative.


---------  

NET2462: The connection ID does not specify a valid connection.



Cause:  The connection is not valid.  A connection is a software
link between a requester and a shared resource on a server, and
that link has not been made.

Action:  Associate a local device on the requester with a
resource on the server.  A connection can be made by using a
network path name with a command line command or from an
application.  If the problem persists, contact your IBM support
representative.


---------  

NET2463: There is no space for another entry in the table of available 
servers.



Cause:  The table of available servers is full.  You will not be
able to see a complete list of network servers when you type the
NET VIEW command.

Action:  Stop other processes or services on the requester to
free enough memory to complete the task.


---------  

NET2464: The server has reached the maximum number of sessions it supports.



Cause:  The server is supporting the maximum number of sessions.

Action:  Try the command later. You will not be able to start a
session with this server until another user's session has ended.
You may need to increase the value of the MAXUSERS entry of the
server IBMLAN.INI file.


---------  

NET2465: The server has reached the maximum number of connections it supports.



Cause:  The server is supporting the maximum number of connections.

Action:  To make another connection to the server, first end a
current connection.  If you have no connections that you can end,
try your command again later.  You will be able to make your
connection once another connection has ended.  You may need to
increase the value of the MAXCONNECTIONS entry in the server IBMLAN.INI file.


---------  

NET2466: The server cannot open more files because it has reached its maximum 
number.



Cause:  No more files can be opened on the server.

Action:  To open another file, you will first have to close a file that is
currently open or stop a network application that has open files.
You may need to increase the value of the MAXOPENS entry in the
server IBMLAN.INI file.


---------  

NET2467: There are no additional servers registered on this server.



Cause:  This server has no additional servers registered.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET2468: The maximum number of server names has been reached.



Cause:  The server is supporting the maximum number of server names.

Action:  To add another server name to the server, first delete a
current server name.  If there are no server names that you can delete,
try your command again later.  You will be able to add a new
server name once another name has been deleted.


---------  

NET2469: The deletion of the server's primary name is not allowed.



Cause:  This is the primary server name. You cannot delete it.

Action:  You are only allowed to delete secondary server names. The
primary name is the server name specified with the COMPUTERNAME parameter
in the server IBMLAN.INI file.


---------  

NET2480: The UPS driver could not be accessed by the UPS service.



---------  

NET2500: The specified program returned an error code:



Cause:  A DOS error occurred.

Action:  Start the requester again.  If the problem persists,
ensure that the remote IPL server is sharing the resources
necessary for the REMOTEBOOT service.


---------  

NET2501: The specified program needs extra memory KB:



Cause:  The program listed needs more memory.


Action:  Allocate extra memory to this program by editing the server
boot-block definition file.


---------  

NET2502: The specified program called an unsupported 21H function:



Cause:  The program on the requester called a DOS function that the
Remote IPL service does not support.


Action:  In the boot-block definition files, use device drivers that call
only functions that the Remote IPL service supports.


---------  

NET2503: Remote IPL is ended.



Cause:  The requester failed to start.


Action:  Start the requester again.  If that fails, stop and start the
REMOTEBOOT service on the server again.


---------  

NET2504: The specified file is damaged.



Cause:  While starting the requester, the server found that the
listed file is damaged.


Action:  Verify the listed file.


---------  

NET2505: There is no system loader specified for the remote IPL files.



Cause:  No loader is specified in the boot-block definition file.


Action:  Specify a loader in the boot-block definition file.


---------  

NET2506: NetBIOS returned an error: The NCB and SMB are dumped above.



Cause:  A NETBIOS error occurred.


Action:  Start the requester again.  If that fails,
stop and start the REMOTEBOOT service on the server again.


---------  

NET2507: A disk I/O error has occurred.



Cause:  An error was detected while reading the image file on the server.


Action:  Verify the access permissions on the server image file.


---------  

NET2508: Image parameter substitution failed.



Cause:  There was an error in the image parameter substitution.


Action:  Verify the RPL.MAP file and the image file.


---------  

NET2509: Too many image parameters span disk sectors.



Cause:  Too many image parameters span disk sectors.

Action:  Regenerate the source disk from which the image was made.  Then
start the requester again.



---------  

NET2510: The image was generated from a DOS format diskette.



Cause:  This warning was generated by the loader.


Action:  No action is needed.


---------  

NET2511: Remote IPL will be started again later.



Cause:  An error caused a temporary pause in the starting of this
requester.  The starting of this requester will continue soon.


Action:  No action is needed.


---------  

NET2512: The call to the remote IPL server failed.



Cause:  An attempt to access a server running the REMOTEBOOT service
failed.


Action:  Ensure that the REMOTEBOOT service is running on a server
that can start this requester.


---------  

NET2513: The requester is unable to connect to the image server.



Cause:  An attempt to connect your requester to the remote IPL server
failed.


Action:  Ensure that the REMOTEBOOT service is running on a server
that can start this requester.


---------  

NET2514: The image file on the remote IPL server cannot be opened.



Cause:  The image file on the remote IPL server could not be opened.


Action:  Ensure that the REMOTEBOOT service is running on a server
that can start this requester.


---------  

NET2517: The Remote IPL service was ended; check the error log at the remote 
IPL server for details.



Cause:  The Remote IPL service stopped.  To find the cause, check the
error log at the remote IPL server by typing:

     NET ERROR

Action:  To start the Remote IPL service again, type:

     NET START REMOTEBOOT

at the remote IPL server.


---------  

NET2518: Remote IPL startup failed; check the error log for the cause of the 
problem.




Cause:  The Remote IPL service could not be started.

To find the cause, check the error log by typing:

     NET ERROR

Action:  After checking the error log, start the Remote IPL
service again by typing:

     NET START REMOTEBOOT


---------  

NET2520: The Remote IPL service detected a configuration error but is 
continuing.  Check the error log at the remote IPL server for details.



Cause:  A configuration error was detected by the Remote IPL
service.

Action:  To find the cause, check the error log at the remote IPL
server by typing:

     NET ERROR

Then edit the RPL.MAP file to correct the error.  The Remote IPL
service does not need to be started again.


---------  

NET2525: DISKFT.SYS is not installed.  Fault Tolerance cannot be started.



Cause:  DISKFT.SYS must be installed to use Fault Tolerance.
A DEVICE statement is needed in the CONFIG.SYS file.

Action:  Refer to the "LAN Server Network Administrator Reference
Volume 3:  Network Administrator Tasks" for more information.



---------  

NET2526: FTMONIT.EXE is not active.  Fault Tolerance cannot be started.



Cause:  FTMONIT.EXE must be active to use Fault Tolerance.  A RUN
statement is needed in the CONFIG.SYS file.


Action:  Refer to the "LAN Server Network Administrator Reference
Volume 3:  Network Administrator Tasks" for more information.


---------  

NET2527: An unlock request has been made to a drive that is not locked.



Cause:  A program has requested Fault Tolerance to unlock a logical drive,
but the drive is not locked.

Action:  No action is needed.



---------  

NET2528: A request has been made to lock a drive that is already locked by 
another process.



Cause:  A program has requested Fault Tolerance to lock a logical
drive, but the drive is already locked by another process.

Action:  Try the operation again later.



---------  

NET2529: The Fault Tolerance verification function or correction function 
cannot be started.



Cause:  A program has requested Fault Tolerance to verify a logical
drive or to correct an error on a drive.  The function cannot be started.

Action:  Try again later.  If the problem persists, start the server
that contains the logical drive again.  If the problem still persists,
back up and restore the logical drive.



---------  

NET2530: The Fault Tolerance verification function or correction function is 
already stopped.



Cause:  A program has requested Fault Tolerance to stop verification or
correction.  The requested function has already been stopped.

Action:  No action is needed.



---------  

NET2531: The Fault Tolerance verification function or correction function 
cannot be stopped.  Errors have been found and are being corrected.



Cause:  A program has requested Fault Tolerance to stop verification or
correction.  Errors have been found and corrective action is taking
place.  The function cannot be stopped.

Action:  Wait until the function has completed.



---------  

NET2532: A request has been made to change the lock state of a drive.  The 
state cannot be changed.



Cause:  A program has requested to lock a locked drive or unlock an unlocked
drive.

Action:  Try the operation again.  If the problem persists, contact your
network administrator.



---------  

NET2533: An error with the requested handle was not found in 
\IBMLAN\LOGS\FT.LOG.



Cause:  A program has requested information about a specific entry
in the Fault Tolerance error log.  The entry was not found in the log.
The error may have been corrected or the requested error handle is
not correct.

Action:  No action is needed.



---------  

NET2534: The drive is not mirrored; Fault Tolerance cannot verify the drive.



Cause:  A program has requested to verify a drive that is not mirrored.
Only mirrored drives can be verified.

Action:  No action is needed.



---------  

NET2535: The application parameter definition does not exist.



Cause: You have referred to an application parameter that has not
been defined.

Action: Do one or more of the following:
  - Verify that the application name was typed correctly.
  - Verify that the application parameter name was typed correctly.

  If the application parameter is an environment variable, verify that
  the /PLACEMENT switch has been specified.

  If /USERID:<user> was specified, verify that:
    - The user ID for <user> exists and was typed correctly.
    - The application parameter can be overridden on a per-user basis.

      The command
         NET APPPARM appname
      shows all defined application parameters for application 'appname'
      and lists the parameters that can be overridden for the specified user.

    - The application parameter has been overridden for the specified user.

      To display the parameters for application 'appname' that have been
      overridden for user 'userID', type the following command:

         NET APPPARM appname /USER:userID



---------  

NET2536: The application parameter you defined has been previously created.



Cause: The application parameter name is a duplication.

Action: Use a different application parameter name.  To view the list
of existing parameters for an application called 'appname', type the
following command:

    NET APPPARM appname

Note that duplicate application parameter names are allowed when the
parameter is an environment variable.  The combination of the parameter
name and the /PLACEMENT value make the application parameter unique.
For example, an application parameter called LIBPATH with /PLACEMENT:B
is unique from a second LIBPATH application parameter with /PLACEMENT:E.



---------  

NET2537: Individual users are not allowed to override the value of the 
specified application parameter.



Cause: You tried to change the value of an application parameter.  This
application parameter cannot be overridden on a per-user basis, because
it was not so specified at its creation.

Action: Verify that the correct application parameter name was entered.
If the correct application parameter name was entered, the parameter cannot
be overridden on a per-user basis unless the following steps are taken by
a system administrator:
  - The application parameter is deleted.
  - The application parameter is re-created with the /UO option specified.



---------  

NET2538: The data type specified for the application parameter conflicts with 
the specified field type.



Cause: The specified field is an environment variable.  This requires a
string data type.

Action: If the specified field is an environment variable, enter a data
type of string.  If the data type is not string, specify a different field
type.



---------  

NET2539: The file containing information about the specified application 
parameter is not readable or cannot be accessed at this time.



Cause: The file containing data about the specified application parameter
is in use or is not available for the requested operation.  Either another
user is accessing the file or the server where the file is located is
not available at this time.

Action: Wait and try the operation again.



---------  

NET2540: You tried to access an application parameter definition file on a 
machine that is not the domain controller.



Cause: The server you specified is not the domain controller.  Access to
the files containing application parameter definition data can only be
completed through the domain controller.

Action: Run the command on the domain controller.  To determine the machine
that is the domain controller, type:

              NET ACCOUNTS

The domain controller has its role set to PRIMARY.



---------  

NET2541: The file containing information about the specified application 
parameter is missing or damaged.



Cause: The file containing application parameter definition data either
is not present or is damaged.

Action: Do one or more of the following:
  - Verify that the application name was typed correctly.
  - Verify that the application parameter name was typed correctly.

  If /USERID:<user> was specified, verify that:
    - The user ID <user> exists and was typed correctly.
    - The application parameter has been overridden for <user>.
      This can be verified by viewing the list that is displayed
      after typing the following command:

         NET APPPARM appname /USERID:<user>

      If the parameter has not been overridden for a particular user,
      the application parameter definition data file does not exist
      for that user.

  - Restore the missing file from a backup copy.



---------  

NET2542: This command can only be used with DOS Public applications and 
WorkSpace On-Demand applications.



Cause: The application specified with the NET APPPARM command is
neither a DOS Public application nor a WorkSpace On-Demand application.

Action: Specify the name of an application that is a DOS Public application
or a WorkSpace On-Demand application.  To view a list of applications and
their types, type:

      NET APP


---------  

NET2600: VNETAPI.OS2 is required for VNETAPI.SYS to run in DOS.



Cause:  Before you can load the VNETAPI.SYS device driver in a specific
DOS session, you must first install the OS/2 VNETAPI.OS2 device driver.

Action:  Check the OS/2 CONFIG.SYS file for a DEVICE= statement that loads
the VNETAPI.OS2 device driver.  If the statement is not found, run the OS/2
LAN Services Installation/Configuration program, and select Virtual DOS LAN
API Support for installation.


---------  

NET2601: VNETAPI requires OS/2 2.0 or later.



Cause:  The OS/2 VNETAPI.OS2 device driver does not provide services for
any versions of the OS/2 program prior to OS/2 2.0.

Action:  Install the correct version of the OS/2 program.


---------  

NET2604: You did not specify a valid drive and path target for the 
installation.

Example: VNETDLS C:\NET 



Cause:  You did not specify a valid installation path for the DOS LAN
Services Windows network drivers when you ran VNETDLS.CMD.

Action:  Run VNETDLS.CMD again, and specify a target installation path
for the network drivers, for example, VNETDLS C:\NET.


---------  

NET2606: WIN-OS/2 is not installed.


Cause:  Before you can load the DOS LAN Services Windows network drivers,
you must first install WIN-OS/2.

Action: Refer to your base operating system documentation for
information about installing WIN-OS/2.  After you have installed
WIN-OS/2, run VNETDLS.CMD again.


---------  

NET2607: Virtual DOS LAN API support is not installed.


Cause:  Before you can load the DOS LAN Services Windows network drivers,
you must first install the OS/2 VNETAPI.OS2 device driver.

Action:  Check the OS/2 CONFIG.SYS file for a DEVICE= statement that loads
the VNETAPI.OS2 device driver.  If the statement is not found, run the OS/2
LAN Services Installation/Configuration program, and select Virtual DOS LAN
API Support for installation.  Run VNETDLS.CMD again.


---------  

NET2751:  The domain controller is not available.



Cause:  The domain controller either is not running the Server service
or is too busy to respond.

Action:  Wait awhile and then try the operation again.  If the error
persists, print the error log.  Examine the error log for network or
system errors.  Ensure that the Server service is running on the domain
controller.  If the service is running, wait until system activity
slows, and then try the operation again.  If the problem persists,
stop and start the domain controller again, and then stop and start
the user's workstation again.


---------  

NET2758:  The system cannot connect to the server.



Cause:  The user ID and password you are currently logged on with
do not match the access privilege required to complete this action.

Action:  Log on with an ID and password that provide the required
access or provide the matching password with the ID.


---------  

NET2759:  This command is only available to network administrators.



Cause: While logged on with user privileges, you attempted an
operation that requires administrator privileges.

Action:  Limit your network activity to that permissible for a
nonadministrative user, or log off and try the operation again
after logging on with an administrator ID.


---------  

NET2761:  This command requires that you have administrator privilege or
 that you are a user who has been granted one of the following operator
 rights:  ***.



Cause:  You issued a command for which you do not have sufficient
authority.  This command can only be performed by users with
administrator privilege or users who have been granted one or more
of the operator rights listed in the error message.  If you are an
administrator or a user with the operator rights listed, then this
command cannot be performed from your workstation because it is a
requester or because the Peer service is not started.

Action:  Limit your activities to those for which you have sufficient
authority or log off and try the operation again after you have
logged on with sufficient authority for the commands you want to issue.
If you are logged on as an administrator, you may need to start the Peer
service or use the NET ADMIN command.


---------  

NET2781:  The drive specified is not valid or cannot be accessed.



Cause:  An attempt was made to define an alias for a directory on a removable
drive, such as a diskette, or a drive that is not valid.  Internal diskette
drives, redirected drives, virtual disk drives, or nonexistent drives are not
valid.

Action:  Ensure that you specify a valid hard-disk drive for
that server, and try the operation again.


---------  

NET2782:  The alias has already been created.



Cause: The alias is a duplicate of one that has already been defined.

Action:  If the definition for the existing alias is correct, stop
the operation.  Choose a unique alias name and try adding with this
name.  If the problem persists, delete the existing alias, and try
adding the alias name again.


---------  

NET2783:  The alias does not exist.



Cause: You have attempted an operation such as a NET USE with an
alias that has not been created.

Action:  Verify that you are using a valid alias.  If you are
trying to NET USE a netname, ensure that you have preceded the netname
with the server name on which it was defined.  Create a new alias if
necessary.


---------  

NET2784:  The alias name does not exist.



Cause:  You have attempted an operation such as a NET USE with
an alias name that has not been created.

Action:  Verify that you are using a valid alias name.  If you are
trying to NET USE a netname, ensure that you have preceded the netname
with the server name on which it was defined.  Create a new alias
if necessary.


---------  

NET2785:  The resource specified is not valid.



Cause:  If the resource is a files alias, the name must be of the
format drive:\path.  If the resource is a serial device alias, use
a valid list of LPTn or COMn devices.  The resource for a printer
alias must specify a valid spooler queue.

Action:  Try the operation again using a valid resource name.


---------  

NET2786:  The domain control database is unreadable or cannot be accessed at 
this time.



Cause:  The domain control database (DCDB) either is being updated
by another user and cannot be read or is damaged.

Action:  Wait and try the operation again.  If the problem persists,
restore the DCDB from a backup copy.




---------  

NET2787:  The alias is already used as a spooler queue name.



Cause:  The name that you specified is already the name of a spooler queue.
An alias cannot be created with the same name as a spooler queue.

Action:  Select another name if the resource is a file or a serial device.
The alias must be different from the spooler queue name if the resource is
a printer.




---------  

NET2788:  The resource is already defined by another alias.



Cause:  You have attempted to define an alias for a resource for which an
alias has already been defined.  An example of a resource already defined
may be a spooler queue.

Action:  Abandon the operation, and use the existing alias.
Choose a different resource (for example, a new spooler queue)
and try the operation again. If the problem persists, delete
the existing alias and try adding the alias again.




---------  

NET2789:  The alias is a DOS-only external resource.  An external alias cannot
be specified in a NET USE command.



Cause:  You cannot specify an external alias with NET USE.

Action:  Contact the administrator of the external alias and determine
the server name and netname of the resource you want to connect to.
Use the server and netname combination to connect to the resource.



---------  

NET2790:  The alias is an OS/2-only external resource.  An external alias 
cannot be specified in a NET USE command.



Cause:  You cannot specify an external alias with NET USE.

Action:  Contact the administrator of the external alias and determine
the server name and netname of the resource you want to connect to.
Use the server and netname combination to connect to the resource.


---------  

NET2791:  The alias is both a DOS and an OS/2 external resource.  An external 
alias cannot be specified in a NET USE command.



Cause:  You cannot specify an external alias with NET USE.

Action:  Contact the administrator of the external alias and determine
the server name and netname of the resource you want to connect to.
Use the server and netname combination to connect to the resource.


---------  

NET2792:  An application with this name has already been created.



Cause:  The application name is a duplicate of one that has already been
defined.

Action:  Use a different application name.


---------  

NET2793:  The application does not exist.



Cause:  You have attempted an operation that refers to an application
that is not defined in the domain control database.

Action:  Verify that you are using a valid application name.  If the
application name refers to a user's private application, the user's
domain control database files and subdirectories need to have been
initialized.  Verify that:

         - The user exists.
         - The subdirectory \IBMLAN\DCDB\USERS\<user> exists, where
           <user> is the user ID for this user.
         - The files USER.A and USER.S exist in this subdirectory.


---------  

NET2794:  An error occurred while creating domain control database files or 
subdirectories for a user.



Cause:  One of the following occurred:

         - The subdirectory \IBMLAN\DCDB\USERS\<user> could not be created.
         - The subdirectory \IBMLAN\DCDB\USERS\<user>\BATCH could not be
           created.
         - An access control profile could not be created for one of the
           previous subdirectories.
         - LIST.A, LIST.S, LIST.U, USER.A, USER.L, or USER.S could not
           be opened or written to.

Action:  Verify that the user exists.  Verify that the caller has authority
to create the subdirectories and their access control profiles.


---------  

NET2795:  An attempt was made to access a domain control database file on a 
machine that is not the domain controller.



Cause:  The specified server is not the domain controller.  Accesses to
the domain control database files can be done only at the domain controller.

Action:  Run the command on the domain controller.  To determine the machine
that is the domain controller, type:

              NET ACCOUNTS

The domain controller will have its role set to PRIMARY.


---------  

NET2796: The application remark contains an error or is not unique.



Cause:  The application remark:

* Contains no text or is more than 40 bytes long.
* Contains this character:  \
* Is not unique.  OS/2 public applications must have unique remarks
  among themselves.  Each user's OS/2 private applications must have
  unique remarks among themselves.

Action:  Ensure that the remark:

* Is from 1 to 40 bytes
* Does not contain the following character:  \
* Is unique.  To view all public applications and their remarks, type:

     NET APPS

  To view all of a particular user's private applications and their
  remarks, type:

     NET APPS /PRIVATE:<userid>


---------  

NET2797: This application cannot be modified to become a WorkSpace On-Demand 
application.



Cause: Only OS/2 Public applications can be modified to become
WorkSpace On-Demand applications.  The /MIGRATE switch was used
with an application that has a type that is not OS/2 Public.

Action: Use the /MIGRATE switch with an OS/2 Public application.
To view a list of public applications and their types, type:

     NET APP


---------  

NET2800:  The Apply operation is not allowed on the specified path.



Cause: File names, printer queues, serial device queues, pipes, and
certain subdirectories under \IBMLAN are not valid for the Apply
operation. For example, if C:\IBMLAN is the LAN Services base
directory (specified in /I:<directory> for NETWKSTA.200 in CONFIG.SYS),
then the apply operation is not permitted on:

   - C:\IBMLAN
   - C:\IBMLAN\DCDB and its subdirectories
   - C:\IBMLAN\NETPROG and its subdirectories
   - C:\IBMLAN\DOSLAN and its subdirectories.

Action:  Specify a valid path for the Apply operation.


---------  

NET2801:  An Apply operation ended prematurely.



Cause:  The Apply action was not able to complete because of an
unrecoverable error encountered on the target server.  The path
that contributed to the failure and the error code is returned
in the return buffer.

Action:  Examine the return buffer to determine the directory,
file, or profile on which the Apply failed.  Correct the problem
and try the Apply action again.


---------  

NET2802:  An apply error occurred with the following information in the return
buffer:

  Error path:   ***
  Error code:   ***



Cause:  The Apply action was not able to complete because of an unrecoverable
error encountered on the target server. The path that contributed to the
failure and the error code is displayed with the error message.

Action:  Examine the error path and the error code to determine the directory,
file, or profile on which the Apply failed.  Correct the problem and try the
Apply action again.


---------  

NET2999: This is the last error in NERR range.



---------  

NET3000:   Drive *** is nearly full. *** bytes are available.  Warn users and 
delete unneeded files.



Cause:  The amount of free space on the specified drive has fallen
        below the minimum size specified in the DISKALERT parameter
        in the IBMLAN.INI file.

Action:  Warn all users that the drive is nearly full and ask the users
         to delete unneeded files.  If sufficient space cannot be freed
         by the users, additional disk drives should be added to the
         system and some of the existing users should be moved to the
         new disk drives.


---------  

NET3001:   *** errors were logged in the last *** minutes.  Review the server 
error log.



Cause: The number of errors logged in the server error log during the
       specified time interval exceeds the limits defined by the ERRORALERT
       and ALERTSCHED parameters in the IBMLAN.INI file.

Action: The network administrator should review the server error log and
        determine if the logged errors need additional action.


---------  

NET3002:   *** network errors occurred in the last *** minutes on network ***.
Review the server error log.  The server or network hardware may need service.



Cause:  The number of network errors logged in the server error log during the
        specified time interval exceeds the limits defined by the ERRORALERT
        and ALERTSCHED parameters in the IBMLAN.INI file.

Action:  The network administrator should review the server error log to
         determine the type of network errors that are occurring.  If a
         problem with the network hardware in the server is indicated,
         run hardware diagnostics for the network adapter.  If a hardware
         problem is indicated somewhere else on the network, have the
         appropriate network technician investigate the problem.


---------  

NET3003:   There were *** bad password attempts in the last *** minutes.  
Review the server audit trail.



Cause:  The number of logon attempts with bad passwords during the
        specified time interval exceeds the limits defined by the
        LOGONALERT and ALERTSCHED parameters in the IBMLAN.INI file.

Action:  The network administrator should review the server audit
         trail log to determine if an attempt is being made to gain
         unauthorized access to the server.

         If the server audit trail log is not enabled, the network
         administrator should enable the audit trail log until the
         reason for the excessive number of failed logon attempts
         is determined.


---------  

NET3004:   *** access-denied errors occurred in the last *** minutes.  Review 
the server audit trail.



Cause:  The number of access-denied errors during the specified time
        interval exceeds the limits defined by the ACCESSALERT and
        ALERTSCHED parameters in the IBMLAN.INI file.

Action:  The network administrator should review the server audit
         trail log to determine if an attempt is being made to gain
         unauthorized access to a network resource.

         If the server audit trail log is not enabled, the network
         administrator should enable the audit trail log until the
         reason for the excessive number of access-denied errors
         is determined.


---------  

NET3005:  Your session to this server has been automatically disconnected 
because of inactivity.



Cause:  No user activity has occurred with the indicated session for
        the time interval specified by the AUTODISCONNECT parameter
        in the IBMLAN.INI file.

Action:  No action is necessary.  The session will reconnect automatically
         when the user starts using the session again.


---------  

NET3006:   The error log is full.  No errors will be logged until the file is 
cleared or the limit is raised.



Cause:  The error log has exceeded the maximum error log size.

Action:  Do one or more of the following:

         -  Clear the error log from the Error Log menu.
         -  Increase the size of the error log from the Error Log menu.
         -  Delete the error log using the NET ERROR /D command.
         -  Increase the maximum error log size by increasing the value
            of the MAXERRORLOG parameter in the IBMLAN.INI file.  The
            Requester must be stopped and started again to make this
            change effective.


---------  

NET3007:   The error log is 80% full.



Cause:  The error log has reached 80% of the maximum error log size.

Action:  Do one or more of the following to prevent the error log from
         becoming full:

         -  Clear the error log from the Error Log menu.
         -  Increase the size of the error log from the Error Log menu.
         -  Delete the error log using the NET ERROR /D command.
         -  Increase the maximum error log size by increasing the value
            of the MAXERRORLOG parameter in the IBMLAN.INI file.  The
            Requester must be stopped and started again to make this
            change effective.


---------  

NET3008:   The audit log is full.  No audit entries will be logged until the 
file is cleared or the limit is raised.



Cause:  The audit log has exceeded the maximum audit log size.

Action:  Do one or more of the following:

         -  Clear the audit log from the Audit Trail menu.
         -  Increase the size of the audit log from the Audit Trail menu.
         -  Delete the error log using the NET AUDIT /D command.
         -  Increase the maximum error log size by increasing the value
            of the MAXAUDITLOG parameter in the IBMLAN.INI file.  The
            server must be stopped and started again to make this
            change effective.


---------  

NET3009:   The audit log is 80% full.



Cause:  The audit log has reached 80% of the maximum audit log size.

Action:  Do one or more of the following to prevent the audit log from
         becoming full:

         -  Clear the audit log from the Audit Trail menu.
         -  Increase the size of the audit log from the Audit Trail menu.
         -  Delete the error log using the NET AUDIT /D command.
         -  Increase the maximum error log size by increasing the value
            of the MAXAUDITLOG parameter in the IBMLAN.INI file.  The
            server must be stopped and started again to make this
            change effective.



---------  

NET3010:   An error occurred while closing file ***.  Examine the file to 
ensure that it is not damaged.



---------  

NET3011:  The administrator has closed ***.



---------  

NET3012:  *** access-denied errors occurred in the last *** minutes.



Cause:  The number of access-denied errors during the specified time
        interval exceeds the limits defined by the ACCESSALERT and
        ALERTSCHED parameters in the IBMLAN.INI file.

Action:  The network administrator should review the server audit trail log
         to determine if someone is trying to gain unauthorized access to
         a network resource.

         If the server audit trail log is not enabled, the network
         administrator should enable the audit trail log until the
         reason for the excessive number of access-denied errors
         is determined.



---------  

NET3013:  A critical sector error was detected on drive ***.  Back up the 
drive.  No data was lost.



Cause:   The 386 HPFS could not access a critical sector on a 386 HPFS
         volume.  Although corrective measures were taken to maintain
         normal operation, the volume may not be accessible once you
         restart the machine.

Action:  Back up all files and access control profiles on this volume
         before turning off the machine. You can use the BACKUP, XCOPY,
         and BACKACC utilities to do this. CHKDSK and FORMAT will be
         denied access to the volume until the machine is restarted.
         Run CHKDSK /F after you restart the machine.


---------  

NET3014:  A bad sector on drive *** cannot be fixed.  Run CHKDSK /F on the 
drive.



Cause:   While attempting to hotfix a defective sector, the 386 HPFS
         discovered that the volume had no free hotfix sectors left.

Action:  Run CHKDSK /F to allocate new hotfix sectors and restore
         performance.


---------  

NET3015:  Drive *** is experiencing severe disk errors.  Back up the drive 
immediately.



Cause:   The 386 HPFS could not access a critical sector on a 386 HPFS
         volume.  The volume may not be accessible following a restart
         of the machine.

Action:  Try to back up all files and access control profiles on this
         volume.  You can use the BACKUP, XCOPY, and BACKACC utilities
         to do this.  CHKDSK and FORMAT will be denied access to the
         volume until the machine is restarted.  Run CHKDSK /F after
         you restart the machine.



---------  

NET3016: The write operation on server *** was successful.  The remaining 
space in the directory is *** KB.



Cause:  A request for disk space within the directory tree increased the
size beyond a specified threshold value.  Thresholds are set by the LAN
administrator or privileged users.

Action: No action is needed unless you need more space.


---------  

NET3017: There was not enough space within the directory on server *** to 
perform a write operation.



Cause: There was not enough disk space within the directory tree to
satisfy the request.  Directory limits are set by the LAN administrator
or privileged users.

Action:  Perform one or more of the following:

- Contact the LAN administrator to increase the directory limit.
- Erase files that are no longer needed.


---------  

NET3020: A power failure was detected on *** at ***.  The server has been 
paused.



Cause:  The UPS service has detected a power failure.  The server
has been paused until power is restored.

Action:  Restore power to the server system.


---------  

NET3021: Power has been restored at ***.  The server is no longer paused.



Cause:  Power has been restored to the server.  The server will
resume normal operation.

Action: No action is necessary.


---------  

NET3022: The UPS service is performing shutdown at *** due to low power on the
battery.



Cause:  The UPS battery supply has dropped below the minimum
power level.  The UPS service is starting an ordered shutdown
of the system.

Action:  Restore power to the server system.


---------  

NET3023: The write operation was successful, but the size of directory *** on 
server *** crossed a threshold.  The remaining space in the directory is *** 
KB.



Cause:  A request for disk space within the directory tree increased the
size beyond a specified threshold value.  Thresholds are set by the LAN
administrator or privileged users.

Action: No action is needed unless you need more space.


---------  

NET3024: There was not enough space within directory *** on server *** to 
perform a write operation.



Cause: There was not enough disk space within the directory tree to
satisfy the request.  Directory limits are set by the LAN administrator
or privileged users.

Action:  Perform one or more of the following:

- Contact the LAN administrator to increase the directory limit.
- Erase files that are no longer needed.


---------  

NET3025: A bad sector was fixed on drive ***.  No data was lost.



Cause:  The 386 HPFS found a bad disk sector and rerouted the data to
a good sector (this process is called hotfixing).  No data was lost.

Action:  Run CHKDSK soon to ensure that enough good disk sectors are
available for error recovery.


---------  

NET3026: An error occurred while processing a remote request.  The error 
occurred on drive ***.



Cause:  An error occurred during an operation on the listed disk
because of problems with the disk.  The operation probably did
not succeed.

Action:  Try the operation again.  If the problem persists and you
are unable to recover data from the disk, use backups of the
affected files, if available.


---------  

NET3030: The server cannot export directory *** to importer ***.  It is 
exported from another server.



Cause:  This server found that another server is exporting the
listed directory to the listed import server.

Action:  Ensure that only one workstation is configured as the
export server for this directory for the listed import workstation.
Verify the EXPORTLIST and EXPORTPATH entries in the IBMLAN.INI
files of the export servers and the IMPORTLIST and IMPORTPATH
entries in the IBMLAN.INI file of the import server.


---------  

NET3031: The replication server could not update directory *** from the source
on *** due to error ***.



Cause:  An error prevented this server from updating the listed
directory from the export server.  The directory cannot be updated
until the problem is corrected.

Action:  Copy the directory manually if necessary and investigate
the cause of the listed error.


---------  

NET3032: Exporter *** did not send an update notice for directory *** at the 
expected time.



Cause:  The Replicator service for this server lost contact with
the export server for the listed directory.


Action:  Ensure the Server and Replicator services are running on
the export server.


---------  

NET3033: User *** has exceeded account limitation *** on server ***.



Cause:  A user's session with this server was ended because the user's logon 
time expired.

Action:  No action is needed.  To define the times during which a user
can use the server, type:

     NET USER userID /TIMES:times


---------  

NET3034: The primary domain controller for domain *** failed.



Cause:  The primary domain controller for this domain has stopped.


Action:  Start the primary domain controller again.  If this is not
possible, specify another server with user-level security to be the
primary domain controller.


---------  

NET3035: This server failed to authenticate with ***, the domain controller 
for domain ***.



Cause:  This server was denied access to the user accounts database
at the domain controller.  Until this problem is corrected, the server
cannot synchronize the user accounts database with the domain controller.

Action:  Stop and start the Netlogon service at this server again.


---------  

NET3036: The replicator attempted to log on at *** as *** and failed.



Cause:  The Replicator service was denied access to the listed export
server.  Until this problem is corrected, the replicator cannot update
the local copies of files exported by that server.

Action:  Ensure that the local workstation has an account on the export
server.  The user ID and password of this account are specified by the
LOGON and PASSWORD entries in the IBMLAN.INI file on the local workstation.
If there is no LOGON entry, then the local workstation name is used as the
user ID and a null password is used.


---------  

NET3038: The replicator could not access *** on *** because of *** system 
error.



Cause:  Because of the listed OS/2 error, the Replicator service
could not access a file on the listed export server.

Action:  Ensure that the local workstation account on the export
server has permission to read the directories being replicated.
The name of this account is specified in the LOGON entry of the
IBMLAN.INI file for the local workstation.  If there is no LOGON entry,
then the name of the account is the machine ID of the local workstation.


---------  

NET3039: The replicator limit for files in a directory has been exceeded.



Cause:  A directory that is being replicated can have no more than 1000 files.

Action:  Remove files from the directory until 1000 or fewer remain.


---------  

NET3040: The replicator limit for tree depth has been exceeded.



Cause:  The replication tree can be no more than 32 levels deep.

Action:  Reorganize the replicated directories so that no path
is more than 32 levels deep.


---------  

NET3041: The replicator cannot update directory ***.  It has tree integrity 
and is the current directory for an active process.



Cause:  A directory cannot be replicated if it is the current
directory of an active process and the INTEGRITY parameter in
the REPL.INI file for the directory has been set to TREE.

Action:  Ensure that the directory to be replicated is not the
current directory of any active process.


---------  

NET3042: Network error *** occurred.



Cause:  The Replicator service stopped because the listed
error occurred.


Action:  To get more information about the error, type:

     HELP message#

where message# is the error code.



---------  

NET3045: System error *** occurred.



Cause:  The Replicator service stopped because the listed
OS/2 error occurred.

Action:  Investigate the cause of the OS/2 error.


---------  

NET3046: The replicator cannot log on, user is currently logged on and TRYUSER
is set to NO.



Cause:  The workstation cannot update its copies of the replicated
files while a user is logged on and the TRYUSER option is set to NO.


Action:  No action is needed.  The workstation will update the files
when no user is logged on.

To have the local workstation update files while users are logged on,
change the value of the TRYUSER entry in the IBMLAN.INI file to YES.


---------  

NET3047: IMPORT path *** cannot be found.



Cause:  The path specified to be the import path, either from the
command line or in IBMLAN.INI, does not exist.


Action:  Verify the spelling of the IMPORTPATH entry in IBMLAN.INI.
This entry must specify a directory that exists.


---------  

NET3048: EXPORT path *** cannot be found.



Cause:  The path specified to be the export path does not exist.


Action:  Verify the spelling of the EXPORTPATH entry in IBMLAN.INI.
This entry must specify a directory that exists.


---------  

NET3050: The replicator failed to update the signal file in directory *** 
because of system error ***.



Cause:  The listed OS/2 error caused the Replicator service to fail
to update its status.


Action:  Investigate the cause of the OS/2 error.


---------  

NET3051: IBMLAN.INI or the command line has an incorrect value for ***.



Cause:  One or more of the values you specified for options
for the service are not valid.


Action:  Type the command again with correct values, or
change the values for the listed options in the IBMLAN.INI file.


---------  

NET3052: The required parameter *** was not provided on the command line or in
IBMLAN.INI.



Cause:  You must specify a value for the listed option.


Action:  You must define a value for the option, either
from the command line or in the IBMLAN.INI file.


---------  

NET3053: *** is not recognized as a valid option.



Cause:  This option is not valid for this service.


Action:  Verify that the spelling of this option is correct.
If you did not specify the option from the command line,
look in the IBMLAN.INI file.


---------  

NET3054: A request for *** resources could not be satisfied.



Cause:  The service required more of the listed resource than was
available.


Action:  Increase the amount of this resource.  Stopping other
services or applications may free some resources, such as memory.

Decrease the value of MAXCONNECTIONS in the IBMLAN.INI file, if it
is set too high.

Also, verify the swap disk, specified by the SWAPPATH entry in
the CONFIG.SYS file.  If this disk is full, delete unnecessary
files and directories from it to clear space.


---------  

NET3056: A system error has occurred.



Cause:  An error was returned from a LAN software component or OS/2 function.

Action:  The system error may be an OS/2 LAN Server error or an OS/2 error.

An error code beginning with NET is a LAN software error;
An error code beginning with SYS is an OS/2 error.
To get help for the error, type:

         HELP message#

where message# is either NET#### or SYS####.

If the problem persists, start the workstation again.  If the
problem still persists, report the problem and the method by
which it can be reproduced to your IBM support representative.


---------  

NET3057: An internal consistency error has occurred.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3058: IBMLAN.INI or the command line has an ambiguous option: ***.



Cause:  This option can be confused with other options that
start with the same letter.


Action:  Spell out enough of the option so that it cannot
be confused with other command options.


---------  

NET3059: IBMLAN.INI or the command line has a duplicate parameter: ***.



Cause:  An option was used more than once in your command
or in the IBMLAN.INI file.  An option can be used only once
in a command and once in the IBMLAN.INI file.  If an option
is typed from the command line, it overrides the value in
IBMLAN.INI.


Action:  Do not type the same option twice in a command.
Be careful not to use different abbreviations that can
specify the same option, such as WRKSERV and WRKSERVICES.

If the error was not caused by a command, look in the
IBMLAN.INI file for duplicate options.


---------  

NET3060: The service did not respond to a control signal and was stopped with 
the DosKillProc function.



Cause:  The service may not be responding to a request to
stop or start.  An unrecoverable error might have occurred.
The service was stopped.

Action:  If this error occurred while starting the requester,
ensure that the product of the PROTOCOL.INI file parameters
NETBIOSTIMEOUT and NETBIOSRETRIES does not exceed 20000 (20
seconds).  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3061: An error occurred while attempting to run the service.



Cause:  The service you specified could not start.


Action:  In the [services] section of the IBMLAN.INI file,
find the name of the program file for this service.  Ensure
that this file exists and is an executable file with a
file-name extension of .EXE or .COM.

If the program file exists, it may be damaged.  If possible,
restore the file from a backup version or from the installation
diskettes.  If the problem persists, contact your IBM support
representative.


---------  

NET3062:  The sub-service *** failed to start.



Cause:  The specified service could not be started automatically
when another service was started.


Action:  Start the service individually by typing:

   NET START service

for the service that could not be started automatically.  This
action may return a more specific error message.

More specific information about the error may also have been logged
in the error log.  To view the error log, type:

   NET ERROR

---------  

NET3063:  There is a conflict in the value or use of these options: ***.



Cause:  Two command-line options or IBMLAN.INI entries have
conflicting values.


Action:  Verify that the command you typed or the IBMLAN.INI
file does not contain conflicting options.


---------  

NET3064:  There is a problem with the file ***:  ***.



Cause:  A problem with the listed configuration file prevented
the service from starting.


Action:  Verify that the listed file is correct.


---------  

NET3065:  The required NetBIOS group name cannot be added to the adapter.


Cause:  This error can be caused by any of the following:
  -  A duplicate NETBIOS group name exists on the network. Adding a bridge
     to join two previously distinct networks can also cause this error if
     an identical COMPUTERNAME exists on each network.
  -  Network adapter hardware errors have occurred.
  -  Insufficient names are specified in the NETx line of the IBMLAN.INI file.
  -  Insufficient NCBs (commands) are specified in the NETx line of the
     IBMLAN.INI file.

Action:  Stop and start the machine again.

If the error occurs again, try one of the following:
  -  Examine your machine and others on the network for other NETBIOS
     applications running on the system to determine if duplicate names
     exist.  For example, the IBMLAN.INI parameter DOMAIN on one machine on
     the network may be identical to the IBMLAN.INI parameter COMPUTERNAME
     on your local machine.  COMPUTERNAMES must be unique and cannot be the
     same as the names of any of the domains on the network.
  -  Check your cable connections and network adapter.
  -  Increase the names in the NETx line of the IBMLAN.INI file.
  -  Increase the NCBs (commands) in the NETx line of the IBMLAN.INI file.


---------  

NET3066:  The role of this machine cannot be standalone.



Cause:  This machine is serving as a standalone machine.

Action:  Change the role of the machine:
              NET ACCOUNTS /ROLE:[PRIMARY|MEMBER|BACKUP]


---------  

NET3067:  NUMMAILSLOTS cannot be zero.


Cause:  The NUMMAILSLOTS is set to zero in the IBMLAN.INI file.

Action:  Change NUMMAILSLOTS to a nonzero positive value.


---------  

NET3074: A security failure has occurred.


Cause:  A software error occurred when an attempt was made to access
the user accounts database, (NET.ACC).

Action:  Type the command again.  If the problem persists, you may have a
faulty disk drive.


---------  

NET3078: The server cannot access the user accounts database (NET.ACC).


Cause:  The user accounts database file (NET.ACC) is missing, is damaged,
or is locked by another process.

Action:  Stop any processes that may have NET.ACC locked.  Verify that;
        - NET.ACC is in the IBMLAN\ACCOUNTS subdirectory
        - NET.ACC is not damaged
        - The /I: parameter on the IFS=NETWKSTA line in the CONFIG.SYS file
          points to the rest of the IBMLAN tree (/I:x:\IBMLAN where 'x' is the
          drive where the IBMLAN tree is installed).

The FIXACC utility can be used to verify that NET.ACC is not damaged or is
not locked by another process.


---------  

NET3079: There are incompatible files installed in the IBMLAN tree.


Cause:  Files from an incompatible version of the OS/2 LAN Server software
are installed.

Action:  Install OS/2 LAN Server again.


---------  

NET3080: The IBMLAN\LOGS directory cannot be accessed.


Cause:  The directory x:\IBMLAN\LOGS (where x: is the drive where the IBMLAN
tree is installed) could not be created.  The drive may be full, there may
already be a file named LOGS in the x:\IBMLAN directory, or there may be
insufficient memory to complete this task.

Action:  Try to create the directory manually by typing:
        MD x:\IBMLAN\LOGS

Ensure that there is sufficient space on the disk.  Verify that the IBMLAN
directory does not contain a file named LOGS.


---------  

NET3081: The domain specified could not be used.


Cause:  There is another domain controller already running the domain.

Action:  Either change the name of the domain or change the role of one of
the domain controllers to Member or Backup.


---------  

NET3082: The machine ID is being used as a message name on another workstation.


Cause:  There is another workstation on the network using the COMPUTERNAME
specified in the IBMLAN.INI file.

Action:  Change COMPUTERNAME in the IBMLAN.INI file to a name not being
used on the network.


---------  

NET3084: The user accounts system is not configured correctly.


Cause:  The server machine name is not defined as a user or it is not a member
of the SERVERS group, or both.

Action:  Ensure that the server machine is defined correctly in the local
user accounts database (NET.ACC).


---------  

NET3085: The server is not running with user-level security.


Cause:  The system is not configured to use user-level security.

Action:  Change SECURITY=SHARE to SECURITY=USER in the [server] section
of the IBMLAN.INI file.


---------  

NET3087: The requester detected a problem with the cable connection.


Cause:  You tried to log on or to start the system.

Action:  Verify that all cables are connected.


---------  

NET3088: View your error log (type NET ERROR) for details.


Cause:  The required requester control segments or server control segments are
too large.  Either too many LAN services are configured or too many alerts
are specified.

Action:  Reduce the number of services specified in the WRKSERVICES or
SRVSERVICES line in your IBMLAN.INI file.

If the error occurs again, reduce the NUMALERTS parameter in the IBMLAN.INI
file.


---------  

NET3091:  The 386 server cannot be started because CACHE386.EXE is not running.


Cause:  The CACHE386.EXE program must be running before the LAN
Server 386 server can be started.


Action:  Run CACHE386.EXE by typing:

    CACHE386

You can also add a RUN line to the CONFIG.SYS file to have
CACHE386.EXE start automatically when the workstation starts.


---------  

NET3100:  The operation failed because a network software error occurred.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3101:  The system ran out of a resource controlled by the *** option.



Cause:  The system required more of a resource than was available.


Action:  Change the value of the listed resource in the
IBMLAN.INI file to allow the system to access more of
the resource.


---------  

NET3102:  The service failed to obtain a long-term lock on the segment for 
NCBs.  The error code is the data.



Cause:  A software error occurred.  A short-term lock
may have been obtained instead on the segment for
network control blocks (NCBs).

Action:  If the problem persists, contact your IBM
support representative.


---------  

NET3103:  The service failed to release the long-term lock on the segment for 
NCBs.  The error code is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3104:  An error occurred while stopping the *** service. The error code 
from NetServiceControl is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3105:  Initialization failed because of an OS/2 execution failure on path 
***.  The OS/2 error code is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3106:  An unexpected NCB was received.  The NCB is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3108:  The DosDevIoctl or DosFsCtl API function call to
 NETWKSTA.*** failed.  The data shown is in this format:
     DWORD  approximate CS:IP of call to ioctl or fsctl
     WORD   error code
     WORD   ioctl or fsctl number



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3109:  System semaphore *** could not be opened or created.  The error code
is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3110:  Initialization failed because file *** could not be opened or 
created.  The OS/2 error code is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3111:  An unexpected NetBIOS error occurred.  The error code is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3112:  An SMB that is not valid was received.  The SMB is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3113:  Initialization failed because the requested *** service could not be
started.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3114:  Some entries in the error log were lost because of a buffer 
overflow.



Cause:  The error log is full, and one or more error
log entries have been lost.


Action:  If you want to save the current error log file, copy
it to another file name.  Then clear the error log by typing:

     NET ERROR /DELETE


---------  

NET3120:  Initialization parameters controlling resource usage other than net 
buffers are sized so that too much memory is needed.



Cause:  The main information segment for the server is larger
than the largest segment that can be allocated.


Action:  Decrease the values for one or more of the following
entries in the IBMLAN.INI file on the server:

      MAXCHDEVJOB     MAXCONNECTIONS    MAXOPENS
      MAXCHDEVQ       MAXLOCKS          MAXSHARES
      MAXCHDEVS

Then start the Server service again.


---------  

NET3121:  The server cannot increase the size of a memory segment.



Cause:  The server cannot increase the size of a memory segment.


Action:  Ensure that the MEMMAN entry in the server CONFIG.SYS
file allows swapping and that there is at least 1 megabyte of free
memory on the swap disk.  The swap disk is specified by the
SWAPPATH entry in CONFIG.SYS.

You could also decrease the value of the NUMBIGBUF entry
in the server IBMLAN.INI file.


---------  

NET3122:  Initialization failed because account file *** is either incorrect 
or not present.



Cause:  The user accounts database, NET.ACC, is missing, damaged,
or in a format that is incompatible with this version of the
LAN software.


Action:  If NET.ACC is damaged, copy the backup version of
the file, NETACC.BKP, to NET.ACC.  If NETACC.BKP does not
exist, restore NET.ACC from a backup copy or from the
installation diskettes.

If you have installed a new version of LAN Server, you may
need to migrate the user accounts database to a new format.
Refer to the "LAN Server Network Administrator Reference
Volume 3:  Network Administrator Tasks" for more information.


---------  

NET3123:  Initialization failed because network *** was not started.



Cause:  All networks named in the SRVNETS entry of the
server IBMLAN.INI file must use the LAN Requester software.


Action:  Ensure that all networks named in the SRVNETS
entry of the server IBMLAN.INI file are also named in
the WRKNETS entry of that file.


---------  

NET3124:  The server failed to start.  All three parameters for character 
devices on the server must be zero or all three must be nonzero.



Cause:  The IBMLAN.INI entries MAXCHDEVJOB, MAXCHDEVQ, and
MAXCHDEVS must all be zero or must all have nonzero values.


Action:  Correct the entries and start the Server service again.


---------  

NET3125:  A remote API request was stopped because of the following 
description string that is not valid: ***.



---------  

NET3126:  The network *** ran out of NCBs.  You may need to increase NCBs for 
this network in the IBMLAN.INI file.  The following information includes the 
number of NCBs submitted by the server when this error occurred:



Cause:  The server found a resource shortage in a network driver
when it tried to issue a network control block (NCB).


Action:  Ensure that the NETn entries in the IBMLAN.INI
file specify valid NETBIOS device drivers and that these
device drivers are in the correct directory.
Also ensure that the CONFIG.SYS file contains a DEVICE line
specifying the absolute path names of the device drivers.

You may be able to increase the NCBs for the listed network
by changing an option in the network NETn entry in the
IBMLAN.INI file and the NCBS entry in the PROTOCOL.INI file.
See the "LAN Server Network Administrator Reference
Volume 2:  Performance Tuning" for more information on the
NETn option and the "Multi-Protocol Transport Services - AnyNet
for OS/2:  Configuration Guide" for more information on the
NCBS option.



---------  

NET3127:  The server cannot create the *** mailslot needed to respond to a 
RELEASEMEMORY alert.  The error received is:



Cause:  The server cannot respond to a Releasememory alert.
Otherwise, the server is functioning normally.


Action:  No action is needed.


---------  

NET3128:  The server failed to register for the RELEASEMEMORY alert with 
recipient ***.  The error code from NetAlertStart is the data.



---------  

NET3129:  The server cannot update the AT schedule file.  The file is damaged.



Cause:  The schedule file, SCHED.LOG in the LOGS directory, is damaged.


Action:  Restore the schedule file from a backup copy, or delete
the file and create a new one using the AT utility.


---------  

NET3130:  The server encountered an error while calling NetIMakeLMFileName.  
The error code is the data.



Cause:  The server could not find the NET.MSG file.


Action:  The NET.MSG file should be in the IBMLAN\NETPROG directory.
If it is not there, copy it from the installation diskettes.


---------  

NET3131:  Initialization failed because of an OS/2 execution failure on path 
***.  There is not enough memory to start the process.
 The OS/2 error code is the data.



Cause:  There is not enough memory available to run the Server service.


Action:  Stop other applications and services
(except the Requester service) running on the workstation
and try again.  If the problem continues, you may have
to add memory to the workstation.


---------  

NET3132:  Long-term locking of the server buffers failed.  Check for free 
space on the swap disk, and then reboot the system to start the server.



Cause:  The server was unable to access required memory.


Action:  Ensure there is at least 1 megabyte of free space on
the swap disk.  The swap disk is specified by the SWAPPATH entry in
CONFIG.SYS.  Then start the workstation again and start the
Server service again.


---------  

NET3140:  The service has stopped because of repeated consecutive occurrences 
of an NCB error.  The last bad NCB follows in raw data.



Cause:  The Messenger service has stopped because of unexpected network 
errors.

Action:  Start the service again.  If the error persists, verify that the
error message displays network control block (NCB) data.  Save this
information and contact your IBM support representative.


---------  

NET3141:  The Messenger service has stopped because of a lock on the Messenger
service shared data segment.



Cause:  A software error occurred that resulted in the Messenger service
shared data segment being left in a locked state.  The Messenger service
cannot continue until the shared data segment is unlocked.

Action:  Start the Messenger service again.  If the problem persists,
stop and start the requester again and then start the Messenger service.
If the problem still persists, report the problem and the method by
which it can be reproduced to your IBM support representative.


---------  

NET3150:  A file system error occurred while opening or writing to the system 
message log file, ***.  Message logging has been turned off because of the 
error. The error code is the data.



Cause:  An error occurred when the Messenger service tried to access
the message log, so message logging has stopped.  The error may have
been caused by a full disk, a disk error, the file being locked by
another process, or by any other situation that would cause an error
while writing to a file.

Action:  If the disk is full, free space on it by deleting unnecessary
files and directories.  Then verify that the message log file is
accessible, and turn on message logging by typing:

     NET LOG /ON




---------  

NET3151:  Messages cannot be displayed as pop-ups because of an OS/2 VIO call 
error.  The error code is the data.



Cause:  The Messenger service could not display a message because an error
occurred while the message panel was being created.

Action:  If message logging was on, the message was still logged to
the file and can be viewed by displaying or printing the message log file.


---------  

NET3152:  The SMB that was received is not valid.  The SMB is the data.



Cause:  A software error occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3160:  The requester information segment is bigger than 64KB.  The size 
follows, in DWORD format.



Cause:  The main information segment of the requester is bigger than
the largest segment that can be allocated.

Action:  Decrease the values for one or more of the following entries in the
[requester] section of the IBMLAN.INI file.

     MAXCMDS       NUMCHARBUF     NUMWORKBUF
     MAXTHREADS    NUMDGRAMBUF    SIZCHARBUF
     NUMALERTS     NUMSERVICES    SIZERROR

After you change the IBMLAN.INI file, start the Requester service again.
If you change the MAXCMDS or MAXTHREADS entry, you must start the
workstation again.


---------  

NET3161:  The requester was unable to get the name-number of the machine ID.


Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3162:  The requester could not initialize the asynchronous NetBIOS thread.
The error code is the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3163:  The requester could not open the initial shared segment.  The error 
code is the data.



Cause:  The Requester service may not have been started correctly.
Always use the NET START command to start the requester;  do not
run WKSTA.EXE directly.

Action:  To start the requester service, type:

        NET START REQUESTER

If the problem persists, start the workstation again.  If the
problem still persists, report the problem and the method by
which it can be reproduced to your IBM support representative.


---------  

NET3164:  The requester host table is full.



Cause:  The internal table that maintains information about network
servers is full.  You can access all network servers normally, but
you may not be able to see all servers when you type the NET VIEW
command.

This error occurs only on very large networks.

Action:  You may want to divide the network into domains, using
the DOMAIN entry in the IBMLAN.INI file of each workstation.


---------  

NET3165:  A bad mailslot SMB was received.  The SMB is the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3166:  The requester encountered an error while trying to start the user 
accounts system.  The error code is the data.



Cause:  The Requester service failed to start the user accounts database.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3167:  The requester encountered an error while responding to an SSI 
revalidation request.  The function code and the error codes are the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3170:  The Alerter service encountered an error while creating the list of 
alert recipients.  The error code is ***.



Cause:  A software error occurred.

Action:  Contact your network administrator.


---------  

NET3171: An error occurred while expanding *** as a group ID.



Cause:  An error occurred while attempting to identify the
members of the specified group.  The group is probably too large.


Action:  Split the group into two or more smaller groups.


---------  

NET3172:  An error occurred while sending *** the alert message  ***.  The 
error code is ***.



Cause:  An error occurred when an alert message was sent.  The name
designated to receive the alert may no longer exist on the network
or may be logged off.

Action:  Ensure that all names listed in the ALERTNAMES parameter
in the IBMLAN.INI file are correct and do exist.  Update the ALERTNAMES
entry in the server IBMLAN.INI file.  Remove user IDs that no longer exist.


---------  

NET3173:  An error occurred while creating or reading the alerter mailslot.   
The error code is ***.



Cause:  A software error occurred.

Action:  Contact your network administrator.


---------  

NET3174:  The server could not read the AT schedule file.



Cause:  The server cannot read the schedule file because the file is damaged.


Action:  Restore the schedule file from a backup copy,
if you have one.  If not, delete the file and create a
new one, using the AT utility.


---------  

NET3175:  The server found an AT schedule record that is not valid.



Cause:  The schedule file contains a record with a format
that is not valid.


Action:  Restore the schedule file from a backup copy,
if you have one.  If not, delete the file and create a
new one using the AT utility.


---------  

NET3176:  The server could not find an AT schedule file so one was created.



Cause:  The server created a schedule file.


Action:  No action is needed.


---------  

NET3177:  The server could not open the *** network.



Cause:  The server could not start one of its networks.

Action:  Ensure that each network listed in the SRVNETS entry in the
server IBMLAN.INI file has a corresponding entry in the [networks]
section of IBMLAN.INI.


---------  

NET3178:  The AT command processor could not run ***.



Cause:  You used the AT utility to specify a program that
could not run.


Action:  Check the file name of the program you tried to
schedule.  If it is not in the \IBMLAN\NETPROG directory,
ensure that its full path name is specified.


---------  

NET3180:  Warning:  The lazy write process encountered an error while writing 
to drive ***. The disk contains damaged data. The cache has been stopped.



Cause:  An error occurred when the lazy-write process tried to write to
the specified hard disk.

Action:  Run CHKDSK on the specified drive to look for problems with the
disk or the files affected by the lazy-write process.


---------  

NET3181:  A bad sector was fixed on drive ***.  No data was lost.



Cause:  The 386 HPFS found a bad disk sector and rerouted the
data to a good sector (this process is called hotfixing).
No data was lost.


Action:  Run CHKDSK soon to ensure that enough good disk sectors are
available for error recovery.


---------  

NET3182:  A hard error occurred while processing a remote request.  The error 
occurred while on drive ***.



Cause:  An error occurred during an operation on the listed disk because of
problems with the disk.  The operation probably did not succeed.

Action:  Try the operation again.  If the problem persists and you are
unable to recover data from the disk, use backups of the affected files,
if available.


---------  

NET3183:  The 386 HPFS server was unable to be started because of a memory 
address conflict for network ***.



Cause:  The USEALLMEM parameter was set to YES in the 386 HPFS
initialization file, but the device driver for the network was unable
to use memory above 16MB.

Action:  Either set the USEALLMEM parameter to NO in the 386 HPFS
initialization file or remove the network from the [networks] section of
the IBMLAN.INI file.  Start your machine again to make the change go
into effect.



---------  

NET3187:  A critical sector error was detected on drive ***.  Back up the 
drive.  No data was lost.



Cause:   The 386 HPFS could not access a critical sector on a 386 HPFS
         volume.  Although corrective measures were taken to maintain
         normal operation, the volume may not be accessible once you
         restart the machine.

Action:  Back up all files and access control profiles on this volume
         before turning off the machine. You can use the BACKUP, XCOPY,
         and BACKACC utilities to do this. CHKDSK and FORMAT will be
         denied access to the volume until the machine is restarted.
         Run CHKDSK /F after you restart the machine.


---------  

NET3188:  A bad sector on drive *** cannot be fixed.  Run CHKDSK /F on the 
drive.



Cause:   While attempting to hotfix a defective sector, the 386 HPFS
         discovered that the volume had no free hotfix sectors left.

Action:  Run CHKDSK /F to allocate new hotfix sectors and restore
         performance.


---------  

NET3189:  Drive *** is experiencing severe disk errors.  Back up the drive 
immediately.



Cause:   The 386 HPFS could not access a critical sector on a 386 HPFS
         volume.  The volume may not be accessible following a restart
         of the machine.

Action:  Try to back up all files and access control profiles on this
         volume.  You can use the BACKUP, XCOPY, and BACKACC utilities
         to do this.  CHKDSK and FORMAT will be denied access to the
         volume until the machine is restarted.  Run CHKDSK /F after
         you restart the machine.



---------  

NET3190:  A NetWksta internal error has occurred:
  ***.



Cause:  An internal requester error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3191:  The redirector is out of a resource:  ***.



Cause:  The requester is out of the specified resource.

Action:  Adjust the IBMLAN.INI file on the requester to increase
the amount of this resource.  Refer to "Network Administrator
Reference Volume 2:  Performance Tuning" for information on
setting parameters in the IBMLAN.INI file.


---------  

NET3192:  An SMB error occurred on connection to ***.  The SMB header is the 
data.



Cause:  An error occurred on a request sent to the specified
server.  The resource to which the requester was connected may
no longer be shared.

Action:  Ask your network administrator to reshare the resource
so that you can use it.  Try the operation again.  If the problem
persists, start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3193:  A virtual circuit error occurred on the session to ***.  The NCB 
command and return code are the data.



Cause:  The connection between your requester and the specified
server was unexpectedly disconnected.  The server may have been
started again, or a network problem may have occurred.

Action:  If the server was started again, try the operation again
to re-establish the connection.

Note that this message displays a network control block (NCB)
value and the NCB error that was returned.

If the problem persists, start the workstation again.  If the problem
still persists, report the problem and the method by which it can be
reproduced to your IBM support representative.


---------  

NET3194:  A stalled session to *** is being disconnected.



Cause:  The session to the specified server was ended because the
server was not responding.

Action:  Contact your network administrator to ensure that the
server is running, and then reconnect to the server.  The amount
of time a requester waits for a server to respond to a request is
determined by the SESSTIMEOUT entry in the IBMLAN.INI file on the
requester.  If your sessions to servers are frequently ended by
this error, you may want to increase the value of SESSTIMEOUT.


---------  

NET3195:  An NCB error occurred:  ***.  The NCB is the data.



Cause:  An unexpected network control block (NCB) error occurred
on the session to the specified server.  The server may have been
started again, or a network problem may have occurred.

Action:  Contact your network administrator to see if the server
was recently restarted.

Note that this message displays an NCB value and the NCB error that
was returned.

For more information on NCBs and NCB return codes, refer to the
"IBM Local Area Network Technical Reference."

If the problem persists, start the workstation again.  If the
problem still persists, report the problem and the method by
which it can be reproduced to your IBM support representative.


---------  

NET3196:  A write operation to *** failed.  Data may have been lost.



Cause:  An attempt to write data to a file failed.

Action:  See if the specified disk is full.  Also ensure that you
have write permission for the target file.


---------  

NET3197:  A reset of driver *** failed to complete the NCB.  The NCB is the 
data.



Cause:  The specified NETBIOS driver found a problem that
required the network adapter card to be reset.  When the
card was reset, the problem was not corrected.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3198:  The amount of resource *** requested was more than the maximum.  The
maximum amount was allocated.



Cause:  The amount of the listed resource requested was more than
the maximum.  The maximum amount was allocated.

Action:  Verify your configuration.  Note the resource listed in
the original message and verify that its value in the IBMLAN.INI
file does not exceed the maximum.


---------  

NET3199:  Sideband transmissions have been disabled for the session with 
server ***.



Cause:  An excessive number of frames have been lost on the connection
with the indicated server.  This could be caused by a busy server or
defective network hardware.

Action:  In order to re-enable Sideband transmissions for this session,
the session must be deleted and then re-established.  In the
case of Sideband transmissions being disabled repeatedly, contact
your network administrator regarding the instability of the network
configuration.


---------  

NET3202:  The spooler queue manager did not handshake with the initialization 
process.



Cause:  A software error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3203:  A spooler queue *** configuration error occurred.  The *** file 
cannot be found.



Cause:  A software error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3204:  The server could not create a thread.  The THREADS parameter in 
CONFIG.SYS should be increased.



Cause:  The server was unable to create a thread.

Action:  Increase the value of the THREADS entry in the server
CONFIG.SYS file.  The valid range for this value is 64 to 4095.


---------  

NET3205:  The server could not close ***.  The file may be damaged.



Cause:  The server found an error while closing the listed file.

Action:  See if the file is damaged.  If it is, restore it from a backup
copy.


---------  

NET3206:  The replicator cannot update directory ***.  It has tree integrity 
and is the current directory for an active process.



Cause:  A directory cannot be replicated if it is the current
directory of an active process and the INTEGRITY parameter in
the REPL.INI file for the directory has been set to TREE.

Action:  Ensure that the directory to be replicated is not the
current directory of any active process.


---------  

NET3207: The server cannot export directory *** to importer ***.  It is 
exported from another server.



Cause:  This server found that another server is exporting the
listed directory to the listed import server.


Action:  Ensure that only one workstation is configured as the export
server for this directory for the listed import workstation.  Verify
the EXPORTLIST and EXPORTPATH entries in the IBMLAN.INI files of
the export servers and the IMPORTLIST and IMPORTPATH entries in
the IBMLAN.INI file of the import server.


---------  

NET3208: The replication server could not update directory *** from the source
on *** because of error ***.



Cause:  An error prevented this server from updating the listed
directory from the export server.  The directory cannot be updated
until the problem is corrected.

Action:  Copy the directory manually if necessary and investigate
the cause of the listed error.


---------  

NET3209: Exporter *** did not send an update notice for directory *** at the 
expected time.



Cause:  The Replicator service for this server lost contact with
the export server for the listed directory.


Action:  Ensure that the Server and Replicator services are running
on the export server.


---------  

NET3210: This server failed to authenticate with ***, the domain controller 
for domain ***.



Cause:  This server was denied access to the user accounts database
at the domain controller.  Until this problem is corrected, the server
cannot synchronize user account information with the domain controller.


Action:  Stop and start the Netlogon service at this server again.


---------  

NET3211: The replicator attempted to log on at *** as *** and failed.



Cause:  The Replicator service was denied access to the listed export
server.  Until this problem is corrected, the replicator cannot update
the local copies of files exported by that server.


Action:  Ensure that the local workstation has an account on the export
server. The user ID and password of this account are specified by the
LOGON and PASSWORD entries in the IBMLAN.INI file on the local workstation.
If there is no LOGON entry, then the local workstation name is used as the
user ID and a null password is used.


---------  

NET3212: Network error *** occurred.



Cause:  The Replicator service stopped because the listed
error occurred.


Action:  To get more information about the error, type:

     HELP message#

where message# is the error code.



---------  

NET3213: The replicator limit for files in a directory has been exceeded.



Cause:  A directory that is being replicated can have no more
than 1000 files.

Action:  Remove files from the directory until 1000 or fewer remain.


---------  

NET3214: The replicator limit for tree depth has been exceeded.



Cause:  The replication tree can be no more than 32 levels deep.

Action:  Reorganize the replicated directories so that no path
is more than 32 levels deep.


---------  

NET3215: An unrecognized message was received in the mailslot.



Cause:  The replicator received a message from the network that
it did not recognize.

Action:  No action is necessary, the message will be ignored.
If this error occurs regularly, contact your IBM support
representative.


---------  

NET3216: System error *** occurred.



Cause:  The Replicator service stopped because the listed
OS/2 error occurred.

Action:  Investigate the cause of the OS/2 error.


---------  

NET3217: The replicator cannot log on.  The user is currently logged on and 
TRYUSER is set to NO.



Cause:  The workstation cannot update its copies of the replicated
files while a user is logged on and the TRYUSER option is set to NO.


Action:  No action is needed.  The workstation will update the files
when no user is logged on.

To have the local workstation update files while users are logged on,
change the value of the TRYUSER entry in the IBMLAN.INI file to YES.


---------  

NET3218: IMPORT path *** cannot be found.



Cause:  The path specified to be the import path, either from the
command line or in IBMLAN.INI, does not exist.


Action:  Verify the spelling of the IMPORTPATH entry in IBMLAN.INI.
This entry must specify a directory that exists.


---------  

NET3219: EXPORT path *** cannot be found.



Cause:  The path specified to be the export path does not exist.


Action:  Verify the spelling of the EXPORTPATH entry in IBMLAN.INI.
This entry must specify a directory that exists.


---------  

NET3220: The Replicator failed to update the signal file in directory *** due 
to system error ***.



Cause:  The listed OS/2 error caused the Replicator service to
fail to update its status.


Action:  Investigate the cause of the OS/2 error.


---------  

NET3221: A Fault Tolerance error has occurred with the following 
characteristics:
  Severity:      ***                Error code:    ***
  Drive:         ***                    Block number:  ***
  ***




Cause:  An error was recorded by Fault Tolerance.
The error is explained in the original error message.

Action:  Read the original error message text.


---------  

NET3222: The replicator could not access *** on *** because of system error 
***.



Cause:  Because of the listed OS/2 error, the Replicator
service could not access a file on the listed export server.

Action:  Ensure that the local workstation account on the export
server has permission to read the directories being replicated.
The name of this account is specified in the LOGON entry of
the IBMLAN.INI file for the local workstation.  If there is no
LOGON entry, the name of the account is the machine ID
of the local workstation.


---------  

NET3223: The primary domain controller for domain *** has failed.



Cause:  The primary domain controller for this domain has stopped.


Action:  Start the primary domain controller again.  If this is not
possible, specify another server with user-level security to be the
primary domain controller.


---------  

NET3224: An error occurred while changing the password for this workstation.



Cause:  This server found an error while changing the password at the
primary domain controller.

Action:  You must change the password for this workstation manually, both
at this server and at the primary domain controller.

To change the password at this server, first stop the Netlogon service
by typing:

     NET STOP NETLOGON

Temporarily change the server role to standalone by typing:

     NET ACCOUNTS /ROLE:STANDALONE

Then change the password of this server account, both at this server and
at the primary domain controller, by typing:

     NET USER computername newpassword

where computername is the name of this server.

Once the password is changed, return the server to its original role.


---------  

NET3225: An error occurred while updating the logon or logoff information for
***.



Cause:  The current logon statistics may not be accurate because an
error occurred while logon and logoff information was being updated.


Action:  No action is needed.


---------  

NET3226: An error occurred while synchronizing with the primary domain 
controller ***.



Cause:  The local copy of the user accounts database may be out of
synchronization with the copy on the domain controller, because an
error occurred while the database was being updated.


Action:  Stop the Netlogon service by typing:

     NET STOP NETLOGON

Then start the Netlogon service again, with the UPDATE option set
to YES, by typing:

     NET START NETLOGON /UPDATE:YES


---------  

NET3227: The REPL.INI file in subdirectory *** contained an incorrect 
statement.  The statement was ignored.
***



Cause:  The specified line in REPL.INI is not valid.  The line was
ignored, and a default value may have been assumed.

Action:  Correct the statement.  Then stop and restart the service.


---------  

NET3228: The following error occurred while updating the access control 
profile for ***



Cause: The Replicator service could not set the access control profile
for the specified resource.  The error code is the data.

Action: Correct the error, then stop and restart the service.


---------  

NET3229: The NET.ACC file located on the primary domain controller for domain 
*** cannot be used for synchronization.



Cause:  The additional server has detected a new user accounts database
located on the domain controller that cannot be used for synchronization
with the Netlogon service /SYNCSERIALS option set to YES.


Action:  Apply the original NET.ACC file on the domain controller. Or, stop 
the
additional server and run PREPACL to remove all 386 HPFS ACLs, run FIXACC
and then restart the server services on the additional server. When the
synchronization status on the NET STATUS command indicates OK, restore
the previously removed ACLs.


---------  

NET3232: The UPS service did not complete execution of the user-specified 
shutdown command file.



Cause:  The UPS service could not finish running the command file
specified by the CMDFILE entry in the [ups] section of the server
IBMLAN.INI file.

Action:  Check files that could be damaged by the failure of the
command file.  For example, check the files used by applications
that the command file stops.



---------  

NET3233: The UPS driver could not be opened.  The error code is the data.



Cause:  The UPS service could not access the UPS driver (UPSDRV.OS2).
The UPS driver may not be configured properly.

Action:  Ensure that your CONFIG.SYS file has a DEVICE line specifying
the location of the UPS device driver and that the /PORT option of that
line specifies the serial port that the battery is connected to.

If you make changes to the CONFIG.SYS file, you must start your system
again in order for the changes to take effect.


---------  

NET3235: RAM for 64KB work buffer.



Cause: The 386 HPFS server could not obtain RAM for a 64KB work buffer.
Possible reasons are:

- The operating system has already allocated as much physical RAM as
  possible.
- The memory is too fragmented for the request to be satisfied.
- The operating system is unable to swap memory blocks to the swapper
  file.

Action: Do one or more of the following:

- Add additional physical RAM.
- Ensure that the 386 HPFS server parameters in IBMLAN.INI are
  appropriately configured.  For example, if all of your volumes
  are HPFS, then lower the value of the parameters that apply
  exclusively to the Entry server -- NUMBIGBUFF can be set to 0 (if
  you have no shared FAT drives); lower MAXSHARES, MAXLOCKS, and
  MAXCONNECTIONS parameters.  Refer to the "LAN Server Network
  Administrator Reference Volume 2:  Performance Tuning."
- Tune other applications so that they do not use more memory than
  needed.
- Lower the 386 HPFS CACHESIZE and MAXHEAP parameters in the 386 HPFS
  initialization file to free physical RAM.
- Reduce the load on the server in order to give the operating system
  time to consolidate the physical RAM.
- Ensure that there is enough disk space to expand the swapper file.


---------  

NET3236: RAM for heap expansion.



Cause: The 386 HPFS server could not obtain RAM to expand its heap.
Possible reasons are:

- The operating system has already allocated as much physical RAM as
  possible.
- The memory is too fragmented for the request to be satisfied.
- The operating system is unable to swap memory blocks to the swapper
  file.

Action: Do one or more of the following:

- Add additional physical RAM.
- Ensure that the 386 HPFS server parameters in IBMLAN.INI are
  appropriately configured.  For example, if all of your volumes
  are HPFS, then lower the value of the parameters that apply
  exclusively to the Entry server -- NUMBIGBUFF can be set to 0 (if
  you have no shared FAT drives); lower MAXSHARES, MAXLOCKS, and
  MAXCONNECTIONS parameters.  Refer to the "LAN Server Network
  Administrator Reference Volume 2:  Performance Tuning."
- Tune other applications so that they do not use more memory than
  needed.
- Lower the 386 HPFS CACHESIZE and MAXHEAP parameters in the 386 HPFS
  initialization file to free physical RAM.
- Reduce the load on the server in order to give the operating system
  time to consolidate the physical RAM.
- Ensure that there is enough disk space to expand the swapper file.


---------  

NET3237: RAM for file handle table growth.



Cause: The 386 HPFS server could not obtain RAM to expand its file
handle table.
Possible reasons are:

- The operating system has already allocated as much physical RAM as
  possible.
- The memory is too fragmented for the request to be satisfied.
- The operating system is unable to swap memory blocks to the swapper
  file.

Action: Do one or more of the following:

- Add additional physical RAM.
- Ensure that the 386 HPFS server parameters in IBMLAN.INI are
  appropriately configured.  For example, if all of your volumes
  are HPFS, then lower the value of the parameters that apply
  exclusively to the Entry server -- NUMBIGBUFF can be set to 0 (if
  you have no shared FAT drives); lower MAXSHARES, MAXLOCKS, and
  MAXCONNECTIONS parameters.  Refer to the "LAN Server Network
  Administrator Reference Volume 2:  Performance Tuning."
- Tune other applications so that they do not use more memory than
  needed.
- Lower the 386 HPFS CACHESIZE and MAXHEAP parameters in the 386 HPFS
  initialization file to free physical RAM.
- Reduce the load on the server in order to give the operating system
  time to consolidate the physical RAM.
- Ensure that there is enough disk space to expand the swapper file.


---------  

NET3238: Requester connections.



Cause: The maximum number of connections that the 386 HPFS server can
satisfy has been reached.  This maximum is not a configuration option.

Action: Do one or more of the following:

- Reduce the number of connections to the 386 HPFS server.
- Identify users with unneeded connections to the server and have them
  delete those connections.


---------  

NET3239: Open file handles.



Cause: The maximum number of concurrently open files that the 386 HPFS
server can satisfy has been reached.  This maximum is not a configuration
option.

Action:  Do one or more of the following:

- Identify users with excessive or unneeded open files on the server.
  Have them close the files.  The NET SESSION command can be used to
  identify the number of open files per session.  The NET FILE command
  enumerates all of the currently open files.
- Distribute the most commonly used files among other servers in the
  domain.


---------  

NET3240: DOS search handles.



Cause: The maximum number of concurrent searches from DOS workstations
(or DOS applications on OS/2 workstations) that the 386 HPFS server can
satisfy has been reached.  DOS applications request handles but do not
close them.  This maximum is not a configuration option.

Action:  Do one or more of the following:

- Identify users of DOS applications with unneeded sessions to the server
  and delete those sessions.
- Distribute the most commonly used files among other servers in the
  domain.


---------  

NET3241: OS/2 file handles.



Cause: The 386 HPFS server could not satisfy a request for a find
handle from an OS/2 workstation.
Possible causes are:

- Concurrent DOS searches, which can limit the number of find handles
  available for OS/2 workstations.
- The internal limit for find handles has been reached.  This limit is
  not a configuration option.

Action:  Do one or more of the following:

- Identify users of DOS applications with unneeded sessions to the server
  and delete those sessions.
- Distribute the most commonly used files among other servers in the
  domain.


---------  

NET3242: 64KB work buffers



Cause: The maximum number of 64KB work buffers that the 386 HPFS
server uses has been reached.  This maximum is not a configuration option.

Action: Do one or more of the following:

- Distribute the workload among other servers in the domain.
- Have users retry their failed requests when the server is not as busy.



---------  

NET3243: Heap space.



Cause: The 386 HPFS server has reached its preallocated heap limit.

Action: Do one or more of the following:

- Remove the MAXHEAP parameter from the 386 HPFS initialization file.
- Increase the value of the MAXHEAP parameter in the 386 HPFS
  initialization file.


---------  

NET3244: RAM for 64KB read-ahead buffer



Cause: The 386 HPFS server could not obtain RAM for a 64KB read-ahead buffer.
Possible reasons are:

- The operating system has already allocated as much physical RAM as
  possible.
- The memory is too fragmented for the request to be satisfied.
- The operating system is unable to swap memory blocks to the swapper
  file.

Action: Do one or more of the following:

- Add additional physical RAM.
- Ensure that the 386 HPFS server parameters in IBMLAN.INI are
  appropriately configured.  For example, if all of your volumes
  are HPFS, then lower the value of the parameters that apply
  exclusively to the Entry server.  Refer to the "LAN Server Network
  Administrator Reference Volume 2:  Performance Tuning."
- Tune other applications so that they do not use more memory than
  needed.
- Lower the 386 HPFS CACHESIZE and MAXHEAP parameters in the 386 HPFS
  initialization file to free physical RAM.
- Reduce the load on the server in order to give the operating system
  time to consolidate the physical RAM.
- Ensure that there is enough disk space to expand the swapper file.


---------  

NET3245:  A bandwidth management error occurred. The error is the data ***.



---------  

NET3246:  A bandwidth management error occurred on the session to ***. The 
error is the data ***.



---------  

NET3247: 64KB read-ahead buffers



Cause: The maximum number of 64KB read-ahead buffers configured for the
386 HPFS server has been reached.

Action: Do one or more of the following:

- Remove the NUMBUFFERS parameter in the [ultimedia] section of the
  386 HPFS initialization file.
- Increase the maximum number of read-ahead buffers available by
  increasing the NUMBUFFERS parameter in the [ultimedia] section of
  the 386 HPFS initialization file.


---------  

NET3250:  Initialization failed because of an incorrect or missing parameter 
in the IBMLAN.INI file: ***.



Cause:  The Remote IPL service could not start because the listed
entry was missing from IBMLAN.INI.


Action:  Add the listed entry to the server IBMLAN.INI file.


---------  

NET3251:  Initialization failed because of an incorrect line in the 
configuration file ***.  The incorrect line is the data.



Cause:  The Remote IPL service could not start because a line in the
listed configuration file is not valid.


Action:  Correct the listed line.


---------  

NET3252:  Initialization failed because of an error in the configuration file 
***.



Cause:  The Remote IPL service failed to start because of an error in
the listed configuration file.


Action:  Correct the listed file.


---------  

NET3253:  The file *** has been changed after initialization.  The boot block 
loading was temporarily ended.



Cause:  The listed file was changed after the Remote IPL service was
started.  Loading of the boot block was temporarily stopped.


Action:  Stop and start the Remote IPL service again.


---------  

NET3254:  The files do not fit in the boot-block configuration file ***.



Cause:  The files in the listed boot-block definition file do not fit in
the boot block.


Action:  Change the order of the files or the value of BASE or ORG.


---------  

NET3255:  Initialization failed because the dynamic link library *** returned 
a wrong version number.



Cause:  The Remote IPL service could not start because the listed
dynamic link library returned the incorrect version number.


Action:  Verify that you are using the correct versions of the dynamic
link libraries.


---------  

NET3256:  An unrecoverable error occurred in the dynamic link library of the 
service.



Cause:  An unrecoverable error occurred because of a problem with the
dynamic link library of the Remote IPL service.


Action:  Verify that you are using the correct versions of the dynamic link
libraries.


---------  

NET3257:  The system returned an unexpected error code.  The error code is the
data.



Cause:  The system returned an unexpected error code.  The error code
is in the data.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3258:  The Fault Tolerance error log, \IBMLAN\LOGS\FT.LOG, has been 
extended.



Cause:  The Fault Tolerance error log has been extended past 64KB.

Action:  Use the FTADMIN utility to view the log and take corrective
action on the logged errors.



---------  

NET3259:  Fault Tolerance was interrupted while updating the error log.  One 
or more log entries may have been lost.



Cause:  Fault Tolerance was interrupted while updating \IBMLAN\LOGS\FT.LOG.
One or more log entries may have been lost.

Action:  Use the FTADMIN utility to take corrective action on all
logged errors and then verify all mirrored drives.

---------  

NET3265:  A checksum error occurred when accessing the domain control database
file ***.



Cause:  The contents of the domain control database file have been damaged.

Action:  Replace the damaged file with a backup copy.


---------  

NET3266:  An error occurred when reading from or writing to the domain control
database file ***.



Cause:  The file may be damaged or missing.  You may not have the proper
authority to access the file.

Action:  Verify that the file exists and that you are allowed access to it.
The file may need to be replaced with a backup copy.


---------  

NET3267:  The domain control database file *** was not found.



Cause:  The domain control database file does not exist, or the directory
it should reside in does not exist.

Action:  Verify that the user's domain control database files and
subdirectories have been initialized.  If possible, replace the missing
file with a backup copy.


---------  

NET3268: The write operation was successful, but the size of directory *** 
crossed a threshold.  The remaining space in the directory is *** KB.




Cause:  A request for disk space within the directory tree increased the
size beyond a specified threshold value.  Thresholds are set by the LAN
administrator or privileged users.

Action: No action is needed unless you need more space.


---------  

NET3269: There was not enough space within directory *** to perform a write 
operation.




Cause: There was not enough disk space within the directory tree to
satisfy the request.  Directory limits are set by the LAN administrator
or privileged users.

Action:  Perform one or more of the following:

- Contact the LAN administrator to increase the directory limit.
- Erase files that are no longer needed.


---------  

NET3270: The server encountered an error while initializing internal data 
structures.  The server uses these structures to process alerts that pertain 
to directory limits on 386 HPFS volumes.  The server will not post alerts for 
386 HPFS volumes.
The OS/2 return code is ***.



Cause:  The server was initializing internal structures when it
encountered an error.  Consequently, the server cannot send alerts to
users whenever a directory threshold is crossed or whenever a directory
is full.  386 HPFS will still enforce the directory limits.

Action:  Check the OS/2 return code included in the error message.
Restart the server after the appropriate action has been taken.
Some of the possible error codes and causes are:

- For return codes 87 and 1, the server could not communicate with the
  386 HPFS file system.  You might have incompatible versions of the
  file system and server.

- For return code 8, the server could not allocate memory for storing
  its internal structures.  Reduce the number of applications that are
  currently running and try starting the server again.


---------  

NET3271: The server encountered an error while initializing internal data 
structures.  The server uses these structures to process alerts that pertain 
to directory limits.  The server will now use its own default values.
The .INI file in use is ***. The return code is ***.



Cause:  The server encountered an error while processing the .INI file
containing directory limits information.  This is a recoverable error,
but the server will use its own internal default values.

Action:  Refer to the return code recorded in the error message.  Restart
the server after the appropriate action has been taken.  Some possible
return codes are:

- 110, 2, 3:  The server could not find or could not open the .INI file
  to read it.  Ensure that the file exists and is not in use.

- 111:  There was too much information pertaining to directory limits for
  the server to read all of it.  Consolidate the volume information where
  possible.

- 2146:  The server could not find the directory limits parameters in
  the .INI file.  Refer to the "LAN Server Network Administrator
  Reference, Volume 3:  Network Administrator Tasks" for more
  information about adding directory limits parameters to the .INI file.

- 2149:  A line in the specified .INI file is too long.  Edit the line and
  restart the server.


---------  

NET3272: An error occurred as the server attempted to send a message 
concerning a directory limit.  No message was sent.  The OS/2 return code is 
***.



Cause:  The server encountered an error while trying to set up the
message for delivery to the specified users.

Action:  Check the OS/2 return code included in the error message.
Some of the possible return codes are:

- 8:  The server tried to allocate a buffer as a work area, but could
  not.  Reduce the number of applications that are currently running and
  try the operation again.  If this fails, add more memory to your
  system or reduce the number of device drivers that are installed.

- 2:  The server failed to retrieve the message text because it could not
  find the message file, NET.MSG.  Ensure that the file exists and is
  located in a directory that is specified in the DPATH environment
  variable.


---------  

NET3273: The 386 HPFS server failed to enable directory limits on volume *** 
because of insufficient heap space.  The volume is still operational.



Cause:  The 386 HPFS server failed to calibrate the volume for directory
limits because of insufficient heap space.

Action:  Do one or more of the following and then restart the
workstation.

- Increase the heap space for the 386 HPFS space if it is not the
  default.  The heap parameter is found in the 386 HPFS .INI file.
  The default .INI file is HPFS386.INI.

- Add more memory to the workstation.

- Reduce the cache size in use by 386 HPFS.  This parameter is found
  in the 386 HPFS .INI file.  The default .INI file is HPFS386.INI.

- Reduce the number of applications that lock memory, such as device
  drivers.


---------  

NET3274: The 386 HPFS server failed to enable directory limits on volume *** 
because of a disk error.  The volume is still operational.



Cause:  The 386 HPFS server failed to calibrate the volume for directory
limits because of a disk error.

Action: Run CHKDSK /F on the specified volume and then recalibrate the
volume by performing the following command:

    NET DASD <volume> /REFRESH


---------  

NET3275: The server detected a parameter in the .INI file *** that is not 
valid.  The parameter is:  ***.



Cause:  While parsing the .INI file, the server detected and ignored a
parameter that is not valid.

Action:  Correct the parameter in the specified .INI file.  Stop and
restart the server for the change to take effect.


---------  

NET3276: The server detected a parameter in the .INI file *** that does not 
have a valid syntax.  The parameter is ***.



Cause:  While parsing the .INI file, the server detected incorrect syntax.
The parameter was ignored.

Action:  Correct the syntax in the specified .INI file.  Stop and restart
the server for the change to take effect.


---------  

NET3277: The server detected and ignored a drive letter that is not valid 
within a parameter in the .INI file ***.  The parameter is ***.



Cause:  While parsing the .INI file, the server detected a drive letter
that is not valid or a volume that does not exist.  The drive letter was
ignored.

Action:  Correct the error in the specified .INI file.  Stop and restart
the server for the change to take effect.


---------  

NET3278: The server encountered an error while initializing support for 
directory limits on JFS volumes.  Directory limits will not be enforced on JFS
volumes.  The OS/2 return code is ***.



Cause:  The server was initializing internal structures when it
encountered an error.  Consequently, the server cannot enable directory
limits on JFS volumes.  JFS will not enforce the directory limits.

Action:  Check the OS/2 return code included in the error message.
Restart the server after the appropriate action has been taken.
Some of the possible error codes and causes are:

- For return codes 87 and 1, the server could not communicate
  with the JFS file system.  You might have incompatible versions of
  the file system and server.

- For return code 8, the server could not allocate memory for
  storing its internal structures.  Reduce the number of applications
  that are currently running and try starting the server again.


---------  

NET3279: The server encountered an error while initializing internal data 
structures.  The server uses these structures to process alerts that pertain 
to directory limits on JFS volumes.  The server will not post alerts for JFS 
volumes.
The OS/2 return code is ***.



Cause:  The server was initializing internal structures when it
encountered an error.  Consequently, the server cannot send alerts to
users whenever a directory threshold is crossed on a JFS volume or
whenever a directory is full on a JFS volume.  JFS will still enforce
the directory limits.

Action:  Check the OS/2 return code included in the error message.
Restart the server after the appropriate action has been taken.
Some of the possible error codes and causes are:

- For return codes 87 and 1, the server could not communicate
  with the JFS file system.  You might have incompatible versions of
  the file system and server.

- For return code 8, the server could not allocate memory for
  storing its internal structures.  Reduce the number of applications
  that are currently running and try starting the server again.


---------  

NET3400: There is not enough memory to start the Requester service.



Cause:  The workstation does not have enough memory available
to start the Requester service.

Action:  Stop other applications running on the workstation,
then start the Requester service again.  To run a LAN Server
requester on a workstation with IBM OS/2, 3 megabytes of RAM
are required.



---------  

NET3401: An error occurred while reading the NETWORKS entry in the IBMLAN.INI 
file.



Cause:  LAN Server could not read the entries in the [networks]
section of the IBMLAN.INI file.

Action:  Ensure that the IBMLAN.INI file exists (in the \IBMLAN
directory).  Check the format of the entries in the [networks] section.



---------  

NET3402: This is not a valid argument: ***.








Cause:  The listed variable or option (from an entry in the [networks] section
of the IBMLAN.INI file) is not valid.

Action:  Check the format of the entries in the [networks] section of the 
IBMLAN.INI file.



---------  

NET3403: The *** NETWORKS entry in the IBMLAN.INI file has a
 syntax error and will be ignored.



Cause:  The listed entry in the [networks] section of the
IBMLAN.INI file has a syntax error.

Action:  Check the format of the listed entry.



---------  

NET3404: There are too many NETWORKS entries in the IBMLAN.INI file.



Cause:  The IBMLAN.INI file cannot have more than 12 entries in
the [networks] section.

Action:  Remove entries from the [networks] section until 12 or
fewer remain.



---------  

NET3406: An error occurred while opening network device driver *** = ***.



Cause:  The device driver listed in the error message could not be
installed.

Action:  Verify that the listed entry in the [networks] section of
the IBMLAN.INI file is valid.  In the CONFIG.SYS file, verify that
the DEVICE entry that loads this device driver has correct entry
parameters.  Also verify that the DEVICE entry specifies the correct
path name of the device driver.



---------  

NET3407: Device driver *** sent a bad BiosLinkage response.



Cause:  The device driver specified is incorrect.  It may not be
compatible with the network adapter card, or it may be out of date.

Action:  Use a different device driver.



---------  

NET3408: The LAN software cannot run on this version of OS/2.



Cause:  LAN Server cannot be run on the IBM OS/2 version you have installed.

Action:  Install the correct version of the IBM OS/2 program on this
workstation.  Refer to the read-me file on the product diskettes for
the required version of the OS/2 program.


---------  

NET3411: There was an error installing NETWKSTA.***.

 Press ENTER to continue.



Cause:  The LAN Server device driver NETWKSTA.200 could not be installed.

Action:  Another error message, containing a more detailed explanation of the 
error, should have been displayed prior to this message.  See that message for
the cause of the problem.



---------  

NET3412: A resolver linkage problem has occurred.






Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3501: You used an option that is not valid.



Cause:  You typed a command option that is not valid.


Action:  To find the correct options for this command, type:

        NET HELP command

When typing commands, remember that most options must be
preceded with a slash, as in /DELETE.


---------  

NET3502: OS/2 error *** has occurred.



Cause:  The specified OS/2 error occurred.


Action:  Correct the problem and type the command again.

For details on the original error, type HELP SYS####
where #### is the error number from the original message.


---------  

NET3503: The command contains an incorrect number of arguments.



Cause:  The number of options or variables in the command
is not valid.


Action:  To see the syntax of this command, type:

        NET HELP command


---------  

NET3504: The command completed with one or more errors.



Cause:  The command tried to perform multiple tasks, and
some of them failed.


Action:  No action is needed.


---------  

NET3505: You used an option with a value that is not valid.



Cause:  You typed an incorrect value for a command option.


Action:  To see the syntax of this command, type:

     NET HELP command


---------  

NET3506: The option *** is unknown.



Cause:  The specified option is not valid.


Action:  Verify that your spelling is correct.

To see a list of options for this command, type:

     NET HELP command



---------  

NET3507: Option *** is ambiguous.



Cause:  The specified option can be confused with other options.


Action:  Type enough letters of the option so that it is
not ambiguous.

To see a list of options for this command, type:

        NET HELP command


---------  

NET3508: DOS error *** has occurred.



Cause:  The specified DOS error occurred.


Action:  Correct the problem and type the command again.


---------  

NET3509: Too many commands were specified as netservices or wrkservices.



Cause:  Too many programs or services were specified as
WRKSERVICES or NETSERVICES, either from the command line
or in the IBMLAN.INI file on the workstation.


Action:  Specify fewer programs and services as WRKSERVICES
or NETSERVICES.


---------  

NET3510: A command was used with conflicting switches.



Cause:  You typed a command with options that conflict, such
as /YES and /NO.


Action:  Type the command again without conflicting switches.


---------  

NET3511: Subprogram *** could not be found.



Cause:  The specified program file was not found.


Action:  Verify that the program is in the same directory as
NET.EXE, which is usually in \IBMLAN\NETPROG.  This directory should
also be in your search path (specified by the PATH command).


---------  

NET3512: The software requires a later version of the operating system.



Cause:  LAN Server cannot run on the IBM OS/2 version you have installed.

Action:  Install the correct version of the IBM OS/2 program on this
workstation.  Refer to the read-me file on the product diskettes for
the required version of the OS/2 program.


---------  

NET3513: More data is available than can be returned.



Cause:  LAN Server was unable to display all available data.


Action:  The action required depends on the command that
returned the error.  See your network administrator.


---------  

NET3517: The required parameter, ***, was not specified.



Cause:  The command could not complete because a required parameter was
not specified.

Action:  Try the command again, specifying the required parameter.  To
see the syntax for this command, type:

   NET HELP command

To see detailed information about the options, type:

   NET HELP command /O


---------  

NET3533: The service is starting or stopping.  Try again later.



Cause:  This task cannot be performed while the service
is starting or stopping.


Action:  Try the operation again later.


---------  

NET3550:  File NETACC.OLD exists; NETACC.BKP may be damaged.



Cause:  NETACC.OLD is a temporary file created during the update of
NETACC.BKP.  Its presence means that the system failed during the backup.
The file NETACC.BKP may only be a partial copy of the user accounts
database.

Action:  Delete NETACC.BKP and NETACC.OLD, and then rerun BACKACC.


---------  

NET3551:  File NETAUD.OLD exists; NETAUD.BKP may be damaged.



Cause:  NETAUD.OLD is a temporary file created during the update of
NETAUD.BKP.  Its presence means that the system failed during the backup.
The file NETAUD.BKP may only be a partial copy of the audit file.


Action:  Stop the Server service.  Copy NET.AUD to NETAUD.BKP and
delete NETAUD.OLD.  Then start the server again.


---------  

NET3552:  File *** cannot be opened.



Cause:  The listed file could not be opened.


Action:  Ensure that the file exists and that you have permission to
read the file.


---------  

NET3553:  File *** cannot be created.



Cause:  The listed file could not be created.


Action:  Ensure that the file is not read-only and that you have
permission to create the file.


---------  

NET3554:  File *** cannot be removed.



Cause:  The listed file could not be deleted.


Action:  Ensure that the file is not read-only and that you have
permission to delete the file.


---------  

NET3555:  File *** cannot be renamed to ***.



Cause:  The listed file could not be renamed.


Action:  Ensure that the file is not read-only and that you have
permission to delete the old file name and create and write to the new
file name.


---------  

NET3556:  File *** cannot be copied to ***.



Cause:  The copy command could not run.


Action:  Ensure that you have permission to read the source file and
write to the destination file.


---------  

NET3557:  The access control list backup file *** could not be opened.



Cause:  BACKACC could not open the backup file.


Action:  Run BACKACC again, using the /F option to specify a different
backup file.  For example, to back up the permission records of the
directory C:\DB into the backup file DBACC.BAK in the current
directory, type:

     BACKACC C:\DB /F:DBACC.BAK


---------  

NET3558:  The file *** is not a valid access control list backup file.



Cause:  BACKACC stopped because the listed file is not a valid backup
file.

This error can occur even when the /A option is not specified, because
BACKACC checks the target backup file before overwriting it.


Action:  Delete or rename the listed file, or run BACKACC again using
the /F option to specify a different backup file.


---------  

NET3559:  BACKACC could not open a temporary work file.



Cause:  BACKACC creates temporary files in the directory specified by
the TEMP environment variable.  BACKACC stopped because the disk
containing the TEMP directory is full or because you do not have
sufficient permissions to create the work file.


Action:  Ensure that the disk containing the directory specified by
TEMP is not full, and also check the permissions for this directory.


---------  

NET3560:  There is not enough disk space available on *** for the backup file.



Cause:  The disk designated to store the backup file is full.


Action:  Free some space on the disk by deleting unnecessary files and
directories.  Then try the command again.


---------  

NET3561:  The volume label of the source drive, ***, does not match the label 
specified in the existing access control list backup file ***.



Cause:  The specified file already contains a backup access control
profile for directories kept in another disk or volume.  You cannot
store profile backups from more than one disk or volume in a single
backup file.


Action:  Specify a different backup file.


---------  

NET3563:  BACKACC encountered an unexpected OS/2 error.




Cause:  BACKACC stopped because of an unexpected OS/2 error.


Action:  Type the command again.



---------  

NET3564:  BACKACC cannot overwrite the backup file ***.



Cause:  BACKACC could not replace the existing backup permissions
file with the new backup file.


Action:  Ensure that the existing file is not read-only and that you have
permission to write to it, or specify a different backup file name.


---------  

NET3565:  *** is not a valid BACKACC option.


Cause:  You used an option that is not valid.

Action:  The syntax for this command is:

        BACKACC [d:]pathname
        [/F:[d:]target] /L1:[drive:][path][filename] [/A] [/S]
where

d:
   Is an optional drive letter.

pathname
   Is the directory or file where permissions are to be backed up.

/F:target
   Specifies a target file to store permissions.

/L1:filename
   Is the target file where the errors will be logged.  If /L1:filename
   is not specified, then the errors will be written to the screen.
   (The L1: parameter is only valid in a remote install environment.)

/A
   Update the target file instead of overwriting it.

/S
   Backs up all descendant subdirectories.

---------  

NET3566:  BACKACC cannot back up NET.ACC and NET.AUD.



Cause:  BACKACC could not back up NET.ACC or NET.AUD.


Action:  If the server does not have auditing enabled and does not
have a NET.AUD file, then this message may not represent an actual
error.

Otherwise, ensure that the files exist and that you have sufficient
permissions to read these files.


---------  

NET3567:  BACKACC cannot back up the access control list information.



Cause:  BACKACC could not back up the resource permissions.

Another error message should be displayed with this one.


Action:  To get more information about the error, type:

   HELP message#

where message# is the error code.


---------  

NET3568:  The user accounts subsystem could not be started.



Cause:  BACKACC could not access the user accounts database.


Action:  Ensure that you have a valid NET.ACC file in the
\IBMLAN\ACCOUNTS directory and that the server is properly
installed.



---------  

NET3569:  Warning:  Access control lists for drive *** could not be completely
cleaned.



Cause:  BACKACC could not completely clean the NET.ACC file of
obsolete permissions.


Action:  No action is needed.


---------  

NET3570:  Warning: The access control list for *** could not be removed.



Cause:  BACKACC could not remove the obsolete permissions for the
specified resource.


Action:  Use the NET ACCESS /DELETE command to delete these
permissions.


---------  

NET3580:  The access control list backup file *** does not exist.



Cause:  The specified backup file could not be found.


Action:  Verify that you typed the file name correctly and ensure
that the backup file exists.


---------  

NET3581:  RESTACC cannot read the access control list backup file ***.



Cause:  RESTACC cannot read the specified backup file.


Action:  Check your privilege level and permissions for the backup
file.


---------  

NET3582:  The access control list backup file *** is not a valid access 
control list backup file.



Cause:  RESTACC did not recognize the listed file name as a valid
backup permissions file.


Action:  Run RESTACC again, specifying the name of a valid backup
file.


---------  

NET3583:  You do not have sufficient privileges to set permissions on ***.



Cause:  You do not have a sufficient privilege level to set
permissions for the listed resource. RESTACC will continue setting
permissions for other resources.

Action:  No action is needed.


---------  

NET3584:  RESTACC cannot set permission on *** because it does not exist.



Cause:  The listed resource does not exist, so no permissions can be
set for it. RESTACC will continue setting permissions for other
resources.


Action:  No action is needed.



---------  

NET3585:  User *** does not exist; the access control list entry will be 
discarded.



Cause:  A user ID specified in the access control profile does not
exist.  The permissions for this user will be ignored and the rest of
the profile permissions will be set.


Action:  No action is needed.


---------  

NET3586:  Group *** does not exist; the access control list entry will be 
discarded.



Cause:  A group ID specified in the access control profile does not
exist.  The permissions for this group will be ignored and the rest of
the profile permissions will be set.


Action:  No action is needed.


---------  

NET3587:  *** does not exist.



Cause:  The listed resource does not exist, so RESTACC cannot set
permissions for it.  RESTACC will continue setting permissions for
other resources.


Action:  No action is needed.


---------  

NET3588:  You cannot specify newname if pathname contains wildcard characters.



Cause:  You specified a path name with wildcard characters (? or *),
indicating that permissions for multiple files were to be restored,
but you specified only a single file to receive the permissions.

Action:  Type the command again, either specifying a single file for
which to restore permissions or specifying multiple new files to
receive the permissions.


---------  

NET3589:  *** is not a valid RESTACC option.



Cause:  You typed an option that is not valid.

Action:  Verify that you typed the command correctly.  The syntax
of this command is:

     RESTACC [d:]pathname
             [[d:]newname]
             [/F:[d:]source]
             [/L1:[drive:][path][filename]]
             [/S]
where

d:
   Is an optional drive letter.

pathname
   Specifies the directory or file whose access control profiles
   will be restored.

newname
   Specifies a new file or directory which is to receive the permissions
   for the file or directory associated with pathname.

/F:source
   Uses source as the source of backed up access control profiles.

/L1:filename
   Is the target file where the errors will be logged.  If /L1:filename
   is not specified, then the errors will be written to the screen.
   (The L1: parameter is only valid in a remote install environment.)

/S
   Restores subdirectories.


---------  

NET3590:  Warning: The volume label of the destination *** does not match the 
volume label specified in the access control list backup file.  Do you want to
continue anyway? [***] 


Cause:  The volume label of the destination does not match the volume
label stored in the backup file for the access control profile.


Action:  No action is needed.


---------  

NET3591:  RESTACC was not able to complete.



Cause:  RESTACC stopped because of an error.


Action:  To get more information about the error, type:

   HELP message#

where message# is the error code.


---------  

NET3592:  RESTACC ran out of resources.



Cause:  RESTACC could not access enough memory.


Action:  Stop unnecessary applications and services and run RESTACC
again. If disk swapping (specified by the MEMMAN entry in the CONFIG.SYS
file) is turned off, you may need to add more physical memory.


---------  

NET3593:  The maximum number of access control lists for a resource was 
exceeded.



Cause:  The access control profile for a resource was too long.  It
has been truncated.


Action:  No action is needed.


---------  

NET3594:  You cannot specify wildcard characters in newname.



Cause:  You cannot use wildcard characters (? or *) to specify the
new file (new-name) to receive access permissions.


Action:  Type the command again without using wildcard characters in
newname.


---------  

NET3595:  The backup file *** contains no access control lists.



Cause:  The user accounts database that was restored contains no
resource permissions; it still may contain user accounts and user
groups.

Action:  No action is needed.


---------  

NET3600:  FIXACC cannot run while UPM is running.



Cause:  UPMACCTS is running.

Action:  Stop UPMACCTS and try the command again.


---------  

NET3601:  FIXACC cannot run while the LAN Requester is started.



Cause:  The LAN Requester is running.

Action:  Stop the LAN Requester and try the command again.


---------  

NET3602:  An unknown process is using the User Access Subsystem (UAS).



Cause:  A process that cannot be identified is presently using the
User Access Subsystem.

Action:  Try stopping either Database Manager or Communication
Manager, or both, and issue the command again.  If the problem
persists, stop and start your system.


---------  

NET3604:  The file *** cannot be opened because of system error ***.



Cause:  An OS/2 error occurred while trying to open a file.

Action:  See the help for the specified error for more information.


---------  

NET3605:  The file *** already exists.



Cause:  The specified file already exists.

Action:  Delete or rename the file.


---------  

NET3606:  Network error *** occurred while adding group ***.



Cause:  A network error occurred while trying to add a group.

Action:  See the help for the specified error for more information.


---------  

NET3607:  Network error *** occurred while adding user ***.



Cause:  A network error occurred while trying to add a user.

Action:  See the help for the specified error for more information.


---------  

NET3608:  Network error *** occurred while adding access control for ***.



Cause:  A network error occurred while trying to add an access control 
profile.

Action:  See the help for the specified error for more information.


---------  

NET3619:  An error *** occurred when FIXACC attempted to update the
           groups.



Cause:  An OS/2 error occurred.

Action:  To get more information about the error, type:

    HELP message#

where message# is the error code.

Correct the error and run FIXACC again.

---------  

NET3669: All open files must be closed before logging off.



Cause:  Before you log off, you must close all files you
have open on servers.


Action:  Ensure that none of your applications or OS/2
sessions have open files on servers.


---------  

NET3672: You are not currently logged on.



Cause:  You must be logged on to perform this task.


Action:  Log on, and then try the operation again.


---------  

NET3687: The server is running with user-level security.  The share password 
is ignored.



Cause:  The password you typed is not necessary and will be ignored.


Action:  No action is needed.


---------  

NET3692: The program you were running on a remote server ended abnormally.  
The exit code was ***.



Cause:  The program run by NET RUN reported an error.
Depending on the program, this may or may not represent
an actual error.


Action:  See the program documentation for information
about the error code.


---------  

NET3710: An error occurred while opening the help file.



Cause:  A file of help information could not be found.


Action:  Ensure that NET.HLP is in the same directory as NET.EXE,
which is usually in \IBMLAN\NETPROG.  This directory should
also be on your search path (specified by the PATH command).

If you cannot find the help files on your workstation,
copy the original versions of the help files from the LAN
Server installation diskettes to your workstation.


---------  

NET3711: The help file is empty.



Cause:  The file NET.HLP is damaged.  This file is in the
\IBMLAN\NETPROG directory.


Action:  Copy the original versions of the help files from
the LAN Server installation diskettes to your workstation.

Try the operation again.  If the problem persists, start the
workstation again.  If the problem still persists, report the
problem and the method by which it can be reproduced to your
IBM support representative.


---------  

NET3712: The help file is damaged.



Cause:  An error occurred while reading the help file, NET.HLP.

Action:  Copy the original versions of the help files from
the LAN Server installation diskettes to your workstation.

Try the operation again.  If the problem persists, start the
workstation again.  If the problem still persists, report the
problem and the method by which it can be reproduced to your
IBM support representative.


---------  

NET3713: A domain controller could not be found for domain ***.



Cause:  The domain controller is not running or is busy.


Action:  Try the operation again.  If the problem persists,
verify that the domain controller is running.  If the problem
still persists, you may need to move some of the domain
controller work to other servers.


---------  

NET3714: This operation requires administrator privilege on systems with 
earlier versions of LAN software.



Cause:  You must have administrator privilege on the remote
workstation to perform this task, because that workstation is
running a previous version of LAN Server.


Action:  To complete this task, you must have administrator
privilege on the remote workstation, or have that workstation
upgraded to the current version of LAN Server.


---------  

NET3716: The device type is unknown.



Cause:  The device you specified is not valid.


Action:  Verify that your spelling is correct.  Valid devices
are LPT1 to LPT9 and COM1 to COM9 for printers and serial
devices, and A to Z for disk devices.


---------  

NET3717: The log file has been damaged.



Cause:  The log file you are using is damaged.


Action:  If you may need to refer to this log file in the
future, copy it to another file name.  Then clear the log
file so that you can start another one.

If you were using the audit trail, clear it by typing:

      NET AUDIT /DELETE

If you were using the error log, clear it by typing:

      NET ERROR /DELETE


---------  

NET3718: Program file names must end with .EXE.



Cause:  The Netrun service runs only programs with the
file-name extension .EXE.


Action:  To use a program with a .COM extension, a user
with administrative privilege must rename it to an .EXE file.


---------  

NET3719: A matching share could not be found.  Nothing was deleted.



Cause:  LAN Server could not find the resource you wanted to
stop sharing.


Action:  Verify the spelling of the netname.

To see a list of resources the server is sharing, type:

     NET SHARE


---------  

NET3720: The units-per-week field in the user record contains a value that is 
not correct.



Cause:  The internal record of this user is not valid.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET3721: The password is not valid for ***.



Cause:  You typed an incorrect password.


Action:  Verify that you have the correct password, and
then type it again.

If you cannot remember your correct password, see your
network administrator to have your password changed.


---------  

NET3722: An error occurred while sending a message to ***.



Cause:  An error occurred while a message was being sent.
More information about the error should have followed the original
message.


Action:  The additional information should provide details of the error.


---------  

NET3723: An error occurred while opening a temporary file.



Cause:  An error occurred while a temporary file was being opened.


Action:  Verify that you have permission to create files in the root
of the drive containing the IBMLAN tree.  Also verify that the disk
containing the IBMLAN tree is not full.  You can also define an
environment variable to indicate a drive and directory where you have
access and sufficient space to create temporary files by using the
following command:

    SET TMP=x:\path

where x:\path is the path to a directory where you want temporary
files to be created.


---------  

NET3724: An error occurred while writing to a temporary file.



Cause:  An error occurred while LAN Server was writing to a
temporary file.


Action:  Verify with your network administrator that you
have permission to create files in this directory.  The
network administrator should also verify that the server
disk is not full.


---------  

NET3725: An error occurred while the share was deleted.



Cause:  An error occurred when LAN Server tried to stop
sharing the resource.


Action:  Try again to stop sharing the resource.

If no more information about this error is displayed,
read the error log by typing:

     NET ERROR

If there is no more information in the error log, try the
operation again.  If the problem persists, start the workstation
again.  If the problem still persists, report the problem and the
method by which it can be reproduced to your IBM support representative.


---------  

NET3726: The user ID is not valid.



Cause:  You typed a user ID that is not valid.


Action:  If this message displays while logging on during initialization,
enter a valid user ID when prompted.  If this message did not display
while logging on during initialization, type the command again using a
valid user ID.


---------  

NET3727: The password is not valid.



Cause:  You typed a password that is not valid.

Action:  If this message displays while logging on during initialization,
enter a valid password when prompted.  If this message did not display
while logging on during initialization, type the command again using a
valid password.



---------  

NET3728: The passwords do not match.



Cause:  The two passwords you typed did not match.


Action:  Ensure that you have typed identical passwords.


---------  

NET3729: The profile could not be loaded.



Cause:  Loading of the profile stopped after an error occurred.


Action:  No action is needed.


---------  

NET3730: This is not a valid machine ID or domain name.



Cause:  The machine ID or domain name that you typed is not valid.


Action:  Type the command again with a valid machine ID or domain name.


---------  

NET3731: The command is not in the runpath on the remote server.



Cause:  You cannot run this program on this server.


Action:  Verify that you typed the program name correctly.
Verify that the runpath is configured correctly on the server.


---------  

NET3732: Default permissions cannot be set for that resource.



Cause:  This resource does not have default permissions.


Action:  Specify explicit permissions for the resource.


---------  

NET3733: The NETRUN command looks for the program name on the run path.  You 
cannot specify path characters while using NETRUN.



Cause:  You cannot specify a path when you run a program
with the Netrun service.


Action:  Do not specify a path.  Use only the name of the program.


---------  

NET3734: A valid password was not entered.



Cause:  You typed a password that is not valid.


Action:  If this message displays while logging on during initialization,
try to log on again through User Profile Management (UPM).  If your
workstation did not start correctly, start your workstation again
and try to log on.

If this message did not display while logging on during initialization,
type a valid password.


---------  

NET3735: A valid name was not entered.



Cause:  You typed a name that is not valid.


Action:  If this message displays while you are logging on during
initialization, try to log on again through User Profile Management
(UPM).  If your workstation did not start correctly, start your
workstation again and try to log on.

If this message did not display while you were logging on during
initialization, type a valid name.


---------  

NET3736: The resource named cannot be shared.



Cause:  You cannot share this resource.


Action:  No action is needed.


---------  

NET3737: The permissions string contains permissions that are not valid.



Cause:  You specified one or more permissions that are not valid.


Action:  Use only valid permissions: R, X, W, C, D, A, P, Y, and N.


---------  

NET3738: You can perform this operation only on LPT and COM devices.



Cause:  This command is valid only for printers and serial devices.


Action:  No action is needed.


---------  

NET3739: *** already has permissions for the resource.



Cause:  The listed user or group already has permissions for this resource.


Action:  To give a new set of permissions to this user or group, type:

     NET ACCESS resource /CHANGE userid:permissions



---------  

NET3740: *** does not have permissions for the resource.



Cause:  The listed user or group does not have permissions for this resource.


Action:  To give this user or group permissions for the resource, type:

     NET ACCESS resource /GRANT name:permissions


---------  

NET3741: *** is not a valid permission string.



Cause:  You specified one or more permissions that are not valid.


Action:  Use only valid permissions: R, X, W, C, D, A, P, Y, and N.


---------  

NET3742: *** is not a valid user ID or group ID.



Cause:  You typed a user ID or group ID that is not valid.


Action:  Verify that your spelling is correct.
To see a list of existing users, type:

     NET USER

To see a list of existing groups, type:

     NET GROUP


---------  

NET3743: The server is not configured for administration.



Cause:  The server is not set up to be administered remotely.


Action:  For the server to be administered remotely, you must
share the server ADMIN$ and IPC$ resources. Note that these
shares will not appear under NET SHARE, but they can be explicitly
managed with the syntax:

     NET SHARE resource


---------  

NET3744: An error occurred while starting CMD.EXE.



Cause:  CMD.EXE could not start.


Action:  Ensure that there is a SET COMSPEC line in your
CONFIG.SYS file specifying the path name of the CMD.EXE
file.  For example:

     SET COMSPEC=c:\os2\cmd.exe


---------  

NET3745: An error occurred while processing file ***.



Cause:  Your command could not be run on the listed file.
It is being run on the other files you specified.


Action:  No action is needed.


---------  

NET3746: *** is not a valid source file.



Cause:  The source file name you typed is not valid.


Action:  Type a valid file name.


---------  

NET3747: *** is not a valid destination file.



Cause:  The destination file name you typed is not valid.


Action:  Type a valid file name.


---------  

NET3748: An error occurred while copying ***.



Cause:  An error occurred while the specified file was being copied.


Action:  Correct the error and type the command again.


---------  

NET3749: An error occurred while deleting ***.



Cause:  An error occurred while the specified file was being deleted.


Action:  Correct the error and type the command again.


---------  

NET3750: An error occurred while moving ***.



Cause:  An error occurred while the specified file was being moved.


Action:  Correct the error and type the command again.


---------  

NET3751: An error occurred while searching a directory.



Cause:  An error occurred while a directory was being searched.


Action:  Correct the error and type the command again.


---------  

NET3752: No users have sessions with this server.



Cause:  No users have sessions with this server.


Action:  No action is needed.


---------  

NET3753: User *** is not a member of group ***.



Cause:  This user is not a member of the group.


Action:  No action is needed.


---------  

NET3754: User *** is already a member of group ***.



Cause:  This user is already a member of the group.


Action:  No action is needed.


---------  

NET3755: There is no such user: ***.



Cause:  You typed an unknown user ID.


Action:  Verify that your spelling is correct and type the command again.


---------  

NET3757: No valid response was provided.



Cause:  You did not provide a valid response to a prompt.


Action:  No action is needed.


---------  

NET3758: The destination list provided does not match the destination list of 
the printer queue.



Cause:  When you share an existing printer queue, you cannot
specify a list of printers different from those already assigned
for the queue.


Action:  To share the printer queue, type:

     NET SHARE queuename /PRINT

To change the list of printers the queue uses, type:

     NET PRINT netname /ROUTE:devices



---------  

NET3759: Your password cannot be changed until ***.



Cause:  You cannot change your password until the listed date
because of LAN Server security restrictions.


Action:  See your network administrator if your password needs
to be changed now.  Otherwise, wait until the listed date to
change your password.


---------  

NET3760: *** is not a recognized day of the week.



Cause:  The day you specified is not valid.  Valid days are:

Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday

Valid abbreviations are:

M, T, W, Th, F, Sa, Su


Action:  Type the command again, using a valid name or abbreviation.


---------  

NET3761: The time range specified ends before it starts.



Cause:  You specified a time range that starts later than it ends.
Time ranges must start and end on the same day.


Action:  Type the command again, using a valid time range.

You can use either the 12-hour or the 24-hour time format.
When you use the 12-hour format, you must specify either AM
or PM for each time.

When you use the 24-hour format, do not specify AM or PM.


---------  

NET3762: *** is not a recognized hour.



Cause:  You specified an hour in a format that could not be
recognized.  The hour can be a number from 0 to 12 in 12-hour
format or 0 to 24 in 24-hour format.  If you use the 12-hour
format, you must specify either AM or PM for each time.


Action:  Type the command again, using a valid hour format.


---------  

NET3763: *** is not a valid specification for minutes.



Cause:  You specified minutes in a format that could not be recognized.

You can specify times only to the hour.  Typing minutes is optional,
but if included, the format must be :00 (a colon and two zeros).


Action:  Type the command again, either omitting the minutes or
using :00.



---------  

NET3764: The time supplied is not exactly on the hour.



Cause:  Logon times can be specified only on the hour.

Specifying minutes in your command is optional, but if included,
the format must be :00 (a colon and two zeros).


Action:  Type the command again, either omitting the minutes or
using :00.


---------  

NET3765: 12- and 24-hour time formats cannot be mixed.



Cause:  You mixed 12- and 24-hour formats in your time specification.

If you use the 12-hour format (with AM and PM), the hours must
be from 0 to 12.  If you use the 24-hour format, the hours must
be from 0 to 24.


Action:  Type the command again, using either the 12- or 24-hour format.


---------  

NET3766: *** is not a valid 12-hour suffix.



Cause:  You tried to use the 12-hour format, but the time was
followed by text that was neither AM nor PM.

If you use the 12-hour format, you must follow each time with
either AM, A.M., PM, or P.M.


Action:  Type the command again, using the correct forms of AM and PM.


---------  

NET3767: An incorrect date format has been supplied.



Cause:  You used a date format that is not valid.


Action:  Type the command again, using a correct date format.

Dates should be typed in the form mm/dd/yy or dd/mm/yy, depending
on the country code for the workstation.  Months can be represented
by a number, spelled out, or abbreviated to exactly 3 letters.
Use commas or slashes to separate the parts of the date.  Do not use
spaces as separators.  If you do not specify a year, then it is
assumed to be the next occurrence of the date.


---------  

NET3768: An incorrect day range has been supplied.



Cause:  You specified a range of days that is not valid.

Action: When specifying days, use only the complete names of
the days or valid abbreviations.  Valid abbreviations are:

     M, T, W, Th, F, Sa, Su

Ensure that you use a hyphen to separate the beginning
and end of each range of days, as in M-F.  Refer to the
"OS/2 LAN Commands and Utilities" for more details.


---------  

NET3769: An incorrect time range has been supplied.



Cause:  You typed a time range that is not valid.


Action:  Type the command again, using a valid time range.
Use either the 12-hour format, with the numbers 0-12 and
AM and PM, or the 24-hour format with the numbers 0-24.

Use a hyphen to separate the beginning and end of a time
range, as in 9AM-4PM.


---------  

NET3770: Arguments supplied with NET USER are not valid.  Verify the minimum 
password length or the arguments supplied.



Cause:  You typed options or variables that are not valid with the command.


Action:  Type the command again, using valid options and variables.

When you add a user account, the password you set for the user
must conform to your system guidelines for password length.


---------  

NET3771: The value for ENABLESCRIPT must be YES.



Cause:  The /ENABLESCRIPT option of the NET USER command accepts
only YES as a value.


Action:  Type the command again, either specifying
/ENABLESCRIPT:YES or not specifying /ENABLESCRIPT.


---------  

NET3773: An incorrect country code has been supplied.



Cause:  You typed a country code that is not valid.


Action:  Specify a valid country code.


---------  

NET3774: An incorrect domain controller has been supplied.



Cause:  The name you typed for the domain controller is not valid.


Action:  Type the command again with the machine ID of the
domain controller.


---------  

NET3787: Your password has expired.



Cause:  Your password has expired.  You must change it to a new one.

Action:  When this error is displayed, you will be prompted for an
action to take.  No action is required at this time.


---------  

NET3793: Your password has expired.  Change it as soon as possible.



Cause:  Your password has expired.

Action:  If your workstation is a domain controller, type the following:
    NET START NETLOGON
    NET PASSWORD userid oldpw newpw
where oldpw and newpw are your old and new passwords.

If your workstation is an additional server, type the following:
    NET START NETLOGON
    LOGON userid /p:oldpw
where oldpw is your old password.  Then, follow the instructions
to change your password.


---------  

NET3794: Your password has expired.  Contact your network administrator.



Cause:  Your password has expired and the attempt to change it locally
has failed.

Action:  This workstation is an additional server.  Passwords can only be
changed locally at a domain controller.

Start the Server and Netlogon services on this workstation.  Log on to the
domain to which this server belongs, at which time you will be able to
change your password in the domain.  After the domain controller has
replicated your new password to this server, reattempt your local logon
by typing:
     LOGON /l
at the OS/2 command prompt.

If the Server and Netlogon services fail to start because your initial
local logon failed, have your network administrator log on locally and
start those services.

---------  

NET3802: This schedule date is not valid.



Cause:  You typed a schedule date that is not valid.


Action:  Specify either a day of the month represented by
a number between 1 and 31, or a day of the week represented
by one of the following abbreviations: M, T, W, Th, F, S, Su.


---------  

NET3803: The \IBMLAN root directory is unavailable.



Cause:  The \IBMLAN root directory is not available.


Action:  Ensure that the requester is running and the directory
containing the LAN Server software is accessible.


---------  

NET3804: SCHED.LOG cannot be opened.



Cause:  The SCHED.LOG file has been opened by another process
or the disk is full.


Action:  Ensure that the disk is not full.

If another process has opened the file, you will have to wait
for it to close the file before you can open it.


---------  

NET3806: The AT job ID does not exist.



Cause:  You specified a job identification number that does not exist.


Action:  To see the list of jobs and identification numbers in
the schedule file, type:

     AT


---------  

NET3807: The AT schedule file is damaged.



Cause:  The schedule file is damaged.


Action:  Restore the schedule file, SCHED.LOG, from a backup copy,
or delete the file and create a new one, using the AT utility.
SCHED.LOG is in the \IBMLAN\LOGS directory.


---------  

NET3808: The delete operation failed because of a problem with the AT schedule
file.



Cause:  LAN Server cannot find the job you are trying to delete.


Action:  Verify the job identification number by typing:

     AT

Try again to delete the job, using the correct job identification number.

If the error persists, the schedule file, SCHED.LOG, may be damaged.
Restore SCHED.LOG from a backup copy, or delete it and create
a new one, using the AT utility.  SCHED.LOG is in the \IBMLAN\LOGS
directory.


---------  

NET3809: The command line cannot exceed 128 characters.



Cause:  Commands used with the AT utility cannot exceed 128 characters.


Action:  Type a command with 128 or fewer characters.


---------  

NET3810: The AT schedule file cannot be updated because the disk is full.



Cause:  You cannot update the schedule file because the disk is
full.


Action:  Make room on the disk by deleting unnecessary files.


---------  

NET3812: The AT schedule file is not valid.  Delete the file and create a new 
one.



Cause:  The schedule file has been damaged, possibly by system errors.


Action:  Restore the schedule file, SCHED.LOG, from a backup copy,
or delete the file and create a new one, using the AT utility.
SCHED.LOG is in the \IBMLAN\LOGS directory.


---------  

NET3813: The AT schedule file was deleted.



Cause:  The schedule file was cleared.


Action:  No action is needed.


---------  

NET3815: The AT command has timed out.  Try again later.



Cause:  The command failed because another scheduled command is
currently running.


Action:  Type the command again later.


---------  

NET3851: The target path: *** is not valid on the backup operation.



Cause:  The target path does not exist.

Action:  Specify a valid path.


---------  

NET3857: A *** error occurred while restoring the DASD limit for ***.



Cause:  The specified network error occurred while restoring the DASD Limit.

Action:  Correct the error and try the operation again.


---------  

NET3858: A *** error occurred getting the DASD limit for ***.



Cause:  The specified network error occurred while reading a DASD Limit.

Action:  Correct the error and try the operation again.


---------  

NET3859: The file *** is not a valid DASD limit backup file.



Cause:  The input file specified is not a BackDASD data file.

Action:  Try the command again with a different file name.


---------  

NET3860: An error occurred when allocating memory.



Cause:  BackDASD could not allocate enough memory.

Action:  Free system memory and try the command again.


---------  

NET3870: *** is not a valid machine ID.



Cause:  You specified a machine ID that is not valid.


Action:  Verify that the spelling is correct.


---------  

NET3871: *** is not a valid message ID.



Cause:  The message number does not represent a LAN software message.


Action:  Verify that you typed the correct message number.

To get more information about messages, type:

     HELP message#

where message# is the message number, including the 3-letter prefix.


---------  

NET3912: A time server could not be located.



Cause:  The Timesource service is not running on any server in
the network.

Action:  Contact your network administrator and request that
the Timesource service be started on the server that is to be
the Timesource server.



---------  

NET3913: A domain controller could not be found for domain ***.



Cause:  The domain controller is not running or is busy.


Action:  Try the command again.  If the problem persists,
verify that the domain controller is running.  If the problem
still persists, contact your network administrator.


---------  

NET3916: An error occurred while setting the clock at server ***.



Cause:  One of the following occurred:

   - The specified server cannot be contacted.
   - An incorrect date or time range has been supplied.
   - An internal LAN Server error has occurred.

Action:

  - Ensure that the specified server is running and retry the command.
  - Type the command again, using a valid date or time range.
  - Stop and start the workstation.  Try the command again.  If the
    problem still persists, report the problem and the method by
    which it can be reproduced to your IBM support representative.


---------  

NET3921: The users in group *** cannot be enumerated.



Cause:  LAN Server could not identify the members of the listed group.


Action:  Verify that the group exists, and then type the command again.


---------  

NET3924: Only one server can be specified on the command line.



Cause:  You cannot specify more than one server.


Action:  Type the command again specifying only one server or domain.
To see the syntax of this command, type:

     NET HELP CHKSTOR


---------  

NET3925: The /DOMAIN option cannot be used if a server is specified.



Cause:  You cannot specify both a domain and a server.


Action:  Type the command again specifying either a domain or a server.
To see the syntax of this command, type:

     NET HELP CHKSTOR


---------  

NET3926: You have used an option more than once.



Cause:  You typed the same option more than once.


Action:  Type the command again specifying each option only once.


---------  

NET3927: The /ALERTS option requires a value of YES or NO.



Cause:  You did not specify a value for the ALERTS option.


Action:  Type the command again specifying either YES or NO for the
ALERTS option.  To see the syntax of this command, type:

     NET HELP CHKSTOR


---------  

NET3928: You typed an unrecognized value for the /ALERTS option.



Cause:  You typed an incorrect value for the ALERTS option.


Action:  Type the command again specifying either YES or NO for the
ALERTS option.  To see the syntax of this command, type:

     NET HELP CHKSTOR


---------  

NET3929: You typed the following unrecognized value: ***.



Cause:  The listed value is not valid.


Action:  Type the command again using valid options and values.
To see the syntax of the command, type:

     NET HELP CHKSTOR


---------  

NET3930: There is not enough memory to run the service or command you 
specified.



Cause:  LAN Server could not access enough memory to run the command.


Action:  Stop other applications or processes running on the server
and type the command again.  If the problem persists, try the
command again when there is less activity on the network.


---------  

NET3932: *** is not a valid domain name.



Cause:  The name you specified is not a valid domain name.


Action:  Verify that your spelling is correct.  Type the command again
with a valid domain name.  If you type the DOMAIN option with no value,
the requester domain will be used.


---------  

NET3933: An error occurred while trying to access ***.



Cause:  CHKSTOR could not access the listed directory.  This error
can occur if a directory you are checking contains a file with the
"Hidden" flag turned on.

Action:  Ensure that you logged on with a user ID that has permission
to read the home directories you are checking and to read all
directories on the tree below those home directories.



---------  

NET3934: *** is not a valid user or group.



Cause:  The listed user ID or group ID is not valid.


Action:  Verify that your spelling is correct and ensure that
there is an account for the user ID or group ID.


---------  

NET3940: You must supply a value for the *** option.



Cause:  When you type the listed option, you must also type a
value for the option.


Action:  Type the command again, either omitting the option or
specifying a value for it.  To see the syntax of this command,
type:

     NET HELP COPY


---------  

NET3941: The option *** is not recognized.



Cause:  You typed an option that is not valid.


Action:  Verify that your spelling is correct and type the
command again.  To see the syntax of this command, type:

     NET HELP COPY


---------  

NET3942: Too many arguments were given.



Cause:  You typed too many options or variables.


Action:  To see the syntax of this command, type:

     NET HELP COPY


---------  

NET3943: The users in the domain could not be enumerated.



Cause:  LAN Server could not determine which users are logged on to the 
domain.


Action:  Verify that the domain controller NET.ACC file is not damaged.


---------  

NET3944: User *** could not be located.



Cause:  The user you specified is not logged on.


Action:  No action is needed.


---------  

NET3945: No source file was specified.



Cause:  You did not specify a file to copy.


Action:  Type the command again using a file name to copy.


---------  

NET3951:  You specified too many values for the *** option.



Cause:  You specified too many values for the listed option.


Action:  Type the command again using the correct number of
values.  To see the syntax of this command, type:

     NET HELP command


---------  

NET3952:  You entered a value that is not valid for the *** option.



Cause:  You typed a value that is not valid for the listed option.


Action:  Type the command again using valid values.  To see
the syntax of this command, type:

     NET HELP command


---------  

NET3953: The syntax is incorrect.



Cause:  You did not use the correct syntax of this command.


Action:  To see the syntax of this command, type:

     NET HELP command

or refer to the "OS/2 LAN Commands and Utilities."


---------  

NET3960:  The file number supplied is not valid.



Cause:  The file identification number you specified either is
outside the valid range or is not numeric.


Action:  Type the command again using a valid file
identification number.  To see a list of the open files
and their identification numbers, type:

     NET FILE


---------  

NET3961:  The print job number supplied is not valid.



Cause: The print job identification number you specified
either is outside the valid range or is not numeric.


Action:  Type the command again using a valid print job
identification number.  To see a list of print jobs for
a server, type:

     NET PRINT \\machineid


---------  

NET4902: Your local logon attempt has failed.



Cause:  Possible causes include an incorrect user ID or
an incorrect password.

Action:  Log on again.  If your workstation did not start
correctly, start your workstation and log on again.


---------  

NET4905: The local security process has stopped.



Cause:  An unexpected system error occurred.

Action:  Start your workstation again.


---------  

NET4907: The 386 HPFS file system driver was not found.



Cause:  The system cannot enter the secure mode because the
386 HPFS file system driver (FSD) was not running.  The privileged
file will still be run and the user shell will be started,
but the system will be in an unsecured state.

Action:  Ensure that the 386 HPFS FSD is loaded by doing
one or more of the following:
- Correct any error that the 386 HPFS FSD encountered.
- Install the OS/2 LAN Server again if the file HPFS200.386
  or HPFS386.IFS is not found.
- Correct the IFS statement (for the 386 HPFS FSD) in the CONFIG.SYS file.


---------  

NET4908: LAN Server is already in the locally secured state.



Cause:  SECURESH.EXE has already been run and has
already started local security.

Action:  No action is required.  The system is already in the
locally secured state.


---------  

NET4909: The syntax of this command is:
          PRIV program [options]



Cause:  The PRIV command was not issued correctly.

Action:  Issue the PRIV command again with the correct syntax.


---------  

NET4910: Privileged access is denied.



Cause:  The PRIV command can only be used by a user
who has logged on with administrator authority.

Action:  Log on with a user ID that has administrator authority
and issue the command again.


---------  

NET4912: Warning:  LAN Server local security could not be started.

The system is booting in privileged mode.



Cause:  The IOCTL request sent to the 386 HPFS file system driver
to secure the local system failed.  The system is not locally
secured, and all processes are run in privileged mode.

Action:  Start the workstation again.


---------  

NET4913: An error occurred while starting the privileged file.



Cause:  An error occurred while starting the PRIVINIT.CMD file
(or the privileged file specified by the PROTSHELL= line in the
CONFIG.SYS file).

Action:  Change your CONFIG.SYS file or the privileged file to
decrease your memory requirements.  Start your workstation again.
If the problem persists, the workstation may not have enough memory
to start privileged system processes.


---------  

NET4914: Error *** occurred while starting the following user shell:
          ***
Trying to start the default shell:  C:\OS2\PMSHELL.EXE




Cause:  A system error occurred while starting the user protect-mode
shell.  This may indicate an incorrect PROTSHELL= line in the
CONFIG.SYS file.  The system is still secured, and the SECURESH.EXE
file will attempt to start C:\OS2\PMSHELL.EXE so that the user can
correct the error.

Action:  Correct the PROTSHELL= line in the CONFIG.SYS file.  This may
require administrator authority.  Then start the workstation again.
If this does not correct the error, you may not have the proper access
permissions to use this workstation; ask your network administrator to
give you the proper permissions.


---------  

NET4915: Error *** occurred while starting the default protect-mode shell:
          C:\OS2\PMSHELL.EXE



Cause:  A system error occurred while starting C:\OS2\PMSHELL.EXE.
The system is still secured, and the SECURESH.EXE file will attempt
to start CMD.EXE (or the command interpreter specified by the COMSPEC
environment variable) so that you can correct the error.

Action:  If the command interpreter is started, correct the specified
error, and start your workstation again.  If the command interpreter is
not started, start your workstation again and log on locally with a user
ID that has administrator authority.  Then correct the specified error
and start your workstation again.  If this does not correct the error,
you may not have the proper access permissions to use this workstation;
ask your network administrator to give you the proper permissions.


---------  

NET4916: PRIV.EXE could not run the program specified.



Cause:  The program specified could not be run by PRIV.EXE.

Action:  Ensure that the program is in the current path or in the
correct path.  Also, ensure that there is sufficient memory to run
the program.


---------  

NET4918: SECURESH.EXE cannot find the privileged mode
initialization script: ***



Cause:  The PRIVINIT.CMD file or the file specified by the PROTSHELL=
line in the CONFIG.SYS file was not found.

Action:  Ensure that the parameter specified by the /F (or /f) option
of the PROTSHELL= line in the CONFIG.SYS file matches the path and the
file name for the privileged command file.  Correct the error and start
your workstation again.


---------  

NET5300:  The NCB request completed successfully.  The NCB is the data.



Cause:  The operation completed successfully.

Action:  No action is necessary.


---------  

NET5301:  An NCB buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER 
STATUS, or SESSION STATUS is not valid.  The NCB is the data.



Cause:  The requested buffer length (or the buffer selector
if using NETBIOS 3.0) is not valid for the NCB.SEND.DATAGRAM,
NCB.SEND.BROADCAST, NCB.STATUS, or NCB.SESSION.STATUS command.

Action:  Specify the correct buffer size and try again.



---------  

NET5302:  The data descriptor array specified in the NCB is not valid.  The 
NCB is the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5303:  The command specified in the NCB is not valid.  The NCB is the data.



Cause:  The command is not valid.

Action:  Issue the correct command.



---------  

NET5304:  The message correlator specified in the NCB is not valid.  The NCB 
is the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5305:  An NCB command timed out.  The session may have ended abnormally.  
The NCB is the data.



Cause:  A network control block (NCB) command to a remote
workstation failed because the remote workstation did not
respond in time.  The remote workstation is not listening.
The session to the remote workstation may have been dropped.

Action:  No action is necessary.



---------  

NET5306:  An incomplete NCB message was received.  The NCB is the data.



Cause:  The application program received only part of a message
because the specified buffer length was not large enough
to receive the full message.

Action:

NCB.RECEIVE and NCB.RECEIVE.ANY:  Issue another RECEIVE to obtain the
rest of the message before the remote side times out.

NCB.STATUS, NCB.SESSION.STATUS, NCB.RECEIVE.DATAGRAM, and
NCB.RECEIVE.BROADCAST.DATAGRAM:  The remaining data is lost.

Note:  If the command was NCB.STATUS, this error code may occur because the
remote side could not transmit the entire status update if the data was of
greater length than the maximum length UI-frame that may be transmitted.


---------  

NET5307:  The buffer address specified in the NCB is not valid.  The NCB is 
the data.



Cause:  Data sent by a previous NCB.SEND.NO.ACK or
NCB.CHAIN.SEND.NO.ACK command was either not received
at all or only partially received by the remote
application program.

Action:  The application program must initiate any data
recovery that is needed.


---------  

NET5308:  The session number specified in the NCB is not active.  The NCB is 
the data.



Cause:  The session number that was specified is not one of the active 
sessions.

Action:  Issue the command again with the correct active session number.



---------  

NET5309:  No resource was available on the network adapter.  The NCB request 
was refused.  The NCB is the data.



Cause:  A network control block (NCB) request was refused.  There is
no space on the network adapter card for another session.

Action:  No action is needed.


---------  

NET5310:  The session specified in the NCB was closed.  The NCB is the data.



Cause:  The name from the transmitting side closed the session.
The session has ended normally.

Action:  No action is needed.



---------  

NET5311:  The NCB command was canceled.  The NCB is the data.



Cause:  The command was canceled.

Action:  No action is needed.



---------  

NET5312:  The message segment specified in the NCB is not valid.  The NCB is 
the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5313:  The name already exists in the local adapter name table.  The NCB 
request was refused.  The NCB is the data.



Cause:  A network control block (NCB) command attempted to specify a
name that is currently in the name table.

Action:  Issue the command again and specify another name.



---------  

NET5314:  The network adapter name table is full.  The NCB request was 
refused.  The NCB is the data.



Cause:  The number of defined names has exceeded the number of names
that were defined at initialization (the default is 17).

Action:  Wait until a delete name command is issued so that an entry
will become available.


---------  

NET5315:  The network name has active sessions and is now deregistered.  The 
NCB command completed.  The NCB is the data.



Cause:  The name to be deleted is presently active in a session, but is
deregistered.  When the name is marked as deregistered and has active
sessions, this name still occupies a slot in the table.  This name
cannot be used for any new sessions.

Action:  Close all the sessions that use this name.



---------  

NET5316:  A previously issued Receive Lookahead command is active for this 
session.  The NCB command was rejected.  The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5317:  The local session table is full.  You may want to reconfigure the 
NetBIOS stack to allow more sessions.  The NCB request was refused.  The NCB 
is the data.



Cause:  The network control block (NCB) request was refused because
the session table on the network adapter card was full.

Action:  To allow more sessions, reconfigure the NETBIOS stack by
changing the SESS value of the NETn entry in the IBMLAN.INI file.



---------  

NET5318:  An NCB session open was rejected.  No LISTEN is outstanding on the 
remote workstation.  The NCB is the data.



Cause:  No LISTEN command is outstanding on the remote NETBIOS.

Action:  Wait until a LISTEN command is issued on the remote NETBIOS.



---------  

NET5319:  The name number specified in the NCB is not valid.  The NCB is the 
data.



Cause:  The name number has been changed or was never specified.

Action:  Use the most recent number assigned to the name.



---------  

NET5320:  The call name specified in the NCB cannot be found or did not 
answer.  The NCB is the data.



Cause:  No response to the NCB.CALL command was received.

Action:  Try the operation again at a later time.



---------  

NET5321:  The name specified in the NCB was not found.  An asterisk (*) or 
X'0000' cannot be put in the NCB name.  The NCB is the data.



Cause:  The specified name is not in the table, or the first character
of the name is either an ASCII asterisk or X'0000'.

Action:  Try the operation again using a name that has been verified
as correct.



---------  

NET5322:  The name specified in the NCB is in use on a remote adapter.  The 
NCB is the data.



Cause:  The name was found in another table.  Names used in the network
are unique and can only be used in one place.  The name is already
defined on another node.

Action:  Specify another name or have the name changed at the remote end.



---------  

NET5323:  The name specified in the NCB has been deleted.  The NCB is the 
data.



Cause:  The name was deleted.

Action: Add the name to the table and issue the command again.



---------  

NET5324:  The session specified in the NCB ended abnormally.  The NCB is the 
data.



Cause:  The probable cause is that a send NCB timed out
because no receive command was available in the remote node.

Action:  If a send timed out, establish the session again and
ensure that the remote node has issued a receive.

If the session cannot be established again, initiate maintenance
procedures for the node in question.



---------  

NET5325:  The network protocol has detected two or more identical names on the
network.  The NCB is the data.



Cause:  The network protocol has detected two or more identical names on the
network.

Action:  Remove identical names from the network.



---------  

NET5326:  An unexpected protocol packet was received.  There may be an 
incompatible remote device.  The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5333:  The NetBIOS interface is busy, or NetBIOS is out of linkstations.  
The NCB request was refused.  The NCB is the data.



Cause:  Either NETBIOS is experiencing a busy condition or all
available linkstations are in use.  This condition can also be
caused by any of the network status bits 12, 14, or 15 being on.


Action:  Either try the action again, or free up some linkstations by
disconnecting all device redirections to a server.  You may also ask
your network administrator to verify your NETBIOS configuration and
to ensure that enough linkstation resources are specified.



---------  

NET5334:  There are too many NCB commands outstanding.  The NCB request was 
refused.  The NCB is the data.



Cause:  The maximum number of network control block (NCB) commands
is outstanding.  The command will be tried again later.

Action:  No action is needed.



---------  

NET5335:  The adapter number specified in the NCB is not valid.  The NCB is 
the data.



Cause:  A network control block (NCB) command attempted to specify
a value other than 00 or 01, or the adapter is not present.

Action:  Verify that the adapter is present, or correct the value
and try the command again.  Use 00 for the primary adapter and 01
for the alternate adapter.



---------  

NET5336:  The NCB command completed while a cancellation was occurring.  The 
NCB is the data.



Cause:  A network control block (NCB) command tried to cancel a
command that had already been completed.

Action: No action is needed.



---------  

NET5337:  The name specified in the NCB is reserved.  The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5338:  The NCB command cannot be canceled.  The NCB is the data.



Cause:  A network control block (NCB) command tried to cancel a
command that cannot be canceled.

Action:  Verify that the cancel command is correct.



---------  

NET5348:  The name is defined by another environment.  The NCB is the data.



Cause:  Another environment has already defined the name.

Action:  Choose another name.



---------  

NET5351:  There are multiple NCB requests for the same session.  The NCB 
request was refused.  The NCB is the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5352:  A network adapter error has occurred.  The only NetBIOS command that
may be issued is an NCB.RESET. The NCB is the data.



Cause:  The environment is not defined.

Action:  Issue the NCB.RESET command.



---------  

NET5353:  Required operating system resources are exhausted; try the operation
again later.  The NCB is the data.



Cause:  Required operating system resources are exhausted.

Action:  Try the operation again at a later time.



---------  

NET5354:  The maximum number of applications was exceeded.  The NCB request 
was refused.  The NCB is the data.



Cause:  The maximum number of applications defined at NETBIOS 3.0
load time are running.

Action:  Wait until another application completes.



---------  

NET5355:  No SAPs are available for NetBIOS.  The NCB is the data.



Cause:  The adapter has no service access points (SAPs) available for NETBIOS.

Action:  Wait until an application using SAPs reliquishes
the use of a SAP.



---------  

NET5356:  The requested resources are not available.  The NCB request was 
refused.  The NCB is the data.



Cause:  Requested resources are not available.

Action:  Operate with the resources available or end the session.



---------  

NET5357:  The NCB address is not valid or the length does not fit in the 
segment.  The NCB is the data.



Cause:  An application error has occurred.

Action:  Correct the network control block (NCB) address and selector length.

Note: In the case of this return code, since the NCB is in doubt,
the value is returned only in register AL.  No attempt is made
to place the return code into the NCB.



---------  

NET5358:  NCB.RESET may not be issued from a NetBIOS adapter appendage.  The 
NCB is the data.



Cause:  The NCB.RESET command was issued when the NETBIOS 3.0 adapter was
processing a hardware interrupt.

Action:  This is an application error.  Do not issue NCB.RESET in this 
situation.

Note: This return code applies only to the device driver (DD)
interface.



---------  

NET5359:  The NCB_DD_ID value is not valid.  The NCB is the data.



Cause:  NCB_DD_ID is the identification number of the device driver.
This field is supplied to the device driver application program by NETBIOS
when the first NCB.RESET completes.  The application program must then
provide this value in all subsequent commands.

The value in NCB_DD_ID is not identical to the value returned by
NETBIOS 3.0 in the first NCB.RESET issued by the device driver application
program.  Note that NCB_DD_ID must be X'0000' in the first NCB.RESET issued
for a given device driver application program.

Action:  This is an application error.  Correct the NCB_DD_ID value.
Attempt the command again at a later time.


---------  

NET5360:  NetBIOS attempted to lock user storage and the lock failed. The NCB 
is the data.



Cause:  User storage may already be locked.

Action:  Try the command at a later time.

---------  

NET5363:  A NetBIOS device driver open error has occurred.  The NCB is the 
data.



Cause:  Either the device driver had a problem in its open process
or the NETBIOS device driver was not loaded.

Action:  Load the appropriate code before running NETBIOS applications.



---------  

NET5364:  A system error has occurred.  The NCB is the data.



Cause:  During processing, an unexpected error was indicated by
the OS/2 program.

Action:  Issue NET.RESET and try the operation again.
If the problem persists, start the workstation again.  If the problem
still persists, report the problem and the method by which it can be
reproduced to your IBM support representative.



---------  

NET5365:  A ROM checksum failure has occurred.  The NCB request was refused.  
The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5366:  A RAM test failure has occurred.  The NCB request was refused.  The 
NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5367:  A digital loopback failure has occurred.  The NCB request was 
refused.  The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5368:  An analog loopback failure has occurred.  The NCB request was 
refused.  The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5369:  An interface failure has occurred.  The NCB request was refused.  
The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5370:  An unrecognized NCB return code was received.  The NCB is the data.



Cause:  A problem exists with the transport drivers or hardware.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5378:  An unrecoverable network adapter hardware error has occurred.  The 
adapter was closed because one or more of bits 12, 14, or 15 were on for more 
than 60 seconds.



Cause:  This return code is reported to the application program
only if the status bits 12, 14, or 15 remain on longer than 60 seconds.

Action:  Check the hardware or cable connections.  Since the only
NETBIOS command that can be issued is NCB.RESET, it may be necessary to
start your workstation again and also start your network software again.


---------  

NET5379:  An unrecoverable network adapter hardware error has occurred.  The 
adapter was closed because one of the network status bits (8-11) was set to 
On.



Cause:  This return code is reported to the application program
only if one of the network status bits was set to On.

Action:  Check the hardware or cable connections.  Since the only
NETBIOS command that can be issued is NCB.RESET, it may be necessary to
start your workstation again and also start your network software again.


---------  

NET5380:  A network adapter is not working correctly.  The NCB request was 
refused.  The NCB is the data.



Cause:  A hardware error has occurred.

Action:  Check the extended status last network status code.  The only
NETBIOS command that may be issued is NCB.RESET.



---------  

NET5381:  The NCB command is still pending.  The NCB is the data.



Cause:  An internal LAN Server error has occurred.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET5401:  The server name specified is not a valid remote IPL server.



Cause:  The REMOTEBOOT service is not installed on the specified server.

Action:  Either install the REMOTEBOOT service on the server or specify a
different server name and try the operation again.


---------  

NET5402:  The RPL.MAP file was not found or could not be opened on the remote 
IPL server.



Cause:  The RPL.MAP file could not be opened or may be locked by another
process.

Action:  Verify that the REMOTEBOOT service is installed on the server or
wait for the other process to complete.


---------  

NET5403:  An error was detected while reading the RPL.MAP file on the remote 
IPL server.



Cause:  An error occurred while reading the RPL.MAP file on the remote
IPL server because the file is too large (more than 64KB) or may be
damaged.

Action:  Verify that the RPL.MAP file on the remote IPL server is valid.
If the RPL.MAP file is damaged, you may need to re-install the remote
IPL service.


---------  

NET5404:  An error occurred while updating the RPL.MAP file on the remote IPL 
server.



Cause:  The remote IPL server does not have enough disk space to
update the RPL.MAP file, or the RPL.MAP file on the remote IPL server
is damaged.

Action:  Perform one of the following:

* Verify that the remote IPL server has enough disk space.
* Verify that the RPL.MAP file on the remote IPL server is not damaged.
  If the RPL.MAP file is damaged, you may need to re-install the remote
  IPL service.


---------  

NET5405:  The machine definition does not exist on the remote IPL server.



Cause:  The machine name specified is not defined on the remote IPL
server.  Either the machine definition does not exist or may be defined
on a different remote IPL server.

Action:  Perform one of the following:

* Define the machine name on the remote IPL server and retry the
  operation.
* Try the operation on another remote IPL server.


---------  

NET5406:  An error was detected while reading configuration files in the 
IBMLAN\RPL\FITS directory on the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5407:  An error was detected while reading configuration files in the 
IBMLAN\RPL\MACHINES directory tree on the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5408:  An error was detected while reading configuration files in the 
IBMLAN\RPL\IBMCOM directory tree on the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5409:  An error was detected while reading configuration files in the 
IBMLAN\RPLUSER directory tree on the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5410:  An error was detected while reading configuration files in the 
IBMLAN\RPL directory tree on the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5411:  Machine configuration files are locked by the remote IPL server file
system.



Cause:   One of the following may have occurred:

* A new machine definition cannot be created from a model machine
  definition while the model machine is active.
* A machine definition cannot be changed while the machine is active.

Action:  Shut down the model machine or the machine to be changed and
try the operation again.


---------  

NET5412:  The server record identifier is not defined in an enabled server 
record entry in the RPL.MAP file.



Cause:  The server record identifier specified is disabled or not defined.

Action:  Verify that the server record identifier exists in an enabled
server record in the RPL.MAP file on the remote IPL server.


---------  

NET5413:  The machine definition remark was more than 48 bytes.



Cause:  The machine definition remark was longer than 48 bytes.

Action:  Specify a remark with a valid length (0-48 bytes).


---------  

NET5414:  The network adapter directory profile could not be found in the 
NDISDD.PRO file on the remote IPL server.



Cause:  The NDISDD.PRO file may be missing or does not contain a network
adapter directory profile that corresponds to the specifed server record
identifier.

Action:  Perform one or more of the following:

* Verify that the NDISDD.PRO file on the remote IPL server is valid.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5415:  Machine definition names for DOS or FAT file systems cannot exceed 8
bytes.


Cause:  The name you specified for the machine definition is too long
for one or more of the following reasons:

* DOS machine definition names cannot exceed 8 bytes.
* Machine definition names cannot exceed 8 bytes on a server installed
  with a FAT file system.

Action:  Specify a different machine name and try the operation again.


---------  

NET5416:  The response file is not formatted correctly.



Cause:  The data in the response file that is used by the NET RIPLMACH and
NET RIPLMCLASS commands is not formatted correctly.

Action:  Perform one or more of the following:

* Verify that an entry for each item to be created or modified is
  included in the response file.
* For the NET RIPLMACH command, verify that each requester name is
  valid and is enclosed within square brackets.  For the NET RIPLMCLASS
  command, verify that each machine class name is valid and is enclosed
  within square brackets.
* Verify that only one command line parameter is specified per line.
* Verify that all parameter values that contain spaces are
   enclosed within double-quotation marks.
* For the NET RIPLMACH command, verify that neither /OS nor /CLASS
  is specified in a response file that is used to modify existing
  requester definitions.


---------  

NET5420:  The machine definition could not be created because the name is not 
unique in the domain.



Cause:  The name you specified for the machine definition is not unique
in the domain.

Action:  Specify a different machine name and try the operation again.


---------  

NET5421:  The machine definition already exists on the remote IPL server.



Cause:  A machine definition with this name already exists on the remote
IPL server.  Machine names must be unique in the domain.

Action:  Specify a different machine name and try the operation again.


---------  

NET5422:  The model machine name does not exist on the remote IPL server.



Cause:  The model machine definition could not be found on the remote IPL
server.

Action:  Specify a model machine name that exists on the remote IPL
server.


---------  

NET5424:  The remote IPL OS/2 boot drive identifier is not valid.



Cause:  The specified OS/2 boot drive letter is not valid.

Action:  The OS/2 boot drive letter must be a single ASCII character in
the range of C through Z.  The default OS/2 boot drive letter is Z.


---------  

NET5425:  The network adapter address is not valid.



Cause:  The specified network adapter address is not valid.

Action:  The network adapter number must be 12 bytes.  Only the
characters 0 through 9 and A through F are valid.  Refer to the
documentation for your network adapter for a method of determining the
adapter address.


---------  

NET5426:  A machine definition already exists with the specified network 
adapter address.



Cause:  Another machine definition is using the specified network adapter
address.  Network adapter addresses are unique for every adapter card.

Action:  Refer to the documentation for your network adapter for a method of
determining the adapter address.


---------  

NET5427:  The OS version specified does not match any OS version installed in 
the remote IPL directory.



Cause:  The directory tree for the WorkSpace On-Demand OS version specified
could not be located in the IBMLAN\RPL directory.

Action:  Run the WorkSpace On-Demand OS client installation procedure to
install the OS version on the Remote IPL server.


---------  

NET5428:  An error was detected while reading machine configuration files on 
the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5429:  An error was detected while writing machine configuration files on 
the remote IPL server.



Cause:  Files required for machine configuration could not be created.

Action:  Verify that there is enough disk space and that the disk is
usable on the remote IPL server.


---------  

NET5430:  Files required for creating a machine definition could not be found 
on the remote IPL server.



Cause:  Files required for machine configuration may be damaged or
missing.

Action:  Perform one or more of the following:

* Verify that the REMOTEBOOT service has been properly installed
  on the remote IPL server.
* Verify that any configuration files that were created by the
  administrator are valid and exist in the proper directories.


---------  

NET5431:  The adapter type specified does not match a Title string in any of 
the NIF files for adapters supported for remote IPL.



Cause:  The network adapter type specified does not match a Title
string in any of the NIF files for the network adapters supported
for remote IPL.

Action:  The network adapter type must exactly match the Title record
description in the NIF file for the adapter used by the remote IPL
workstation. NIF files are found in the \IBMLAN\RPL\BBxx.NN\IBMCOM\MACS
directory, where xx indicates the operating system version and NN is a
two-letter language identifier.  View the appropriate
\IBMLAN\RPL\BBxx.NN\IBMCOM\MACS\xxxxxxxx.NIF file and verify
that the Title record description matches the adapter type. From the
NET command, the Title description must be enclosed in double-quotation
marks.  From the GUI, do not enter the double-quotation marks in the
adapter type field.


---------  

NET5432:  An error was detected while creating machine configuration 
directories on the remote IPL server.



Cause:  Directories required for machine configuration could not be
created.

Action:  Verify that there is enough disk space and that the disk is
usable on the remote IPL server and try the operation again.


---------  

NET5433:  An error was detected while creating access control profiles on the 
remote IPL server.



Cause:  Access control profiles could not be created for machine
configuration directories or the NET.ACC file on the remote IPL server
may be damaged.

Action:  Verify that the SERVER service is started on the remote IPL
server.  If the problem persists, restore the NET.ACC file from backup.


---------  

NET5434:  One or more of the IP addresses specified do not conform to the 
expected IP address format.



Cause:  One or more of the specified IP addresses do not conform to the
expected IP address format.

Action:  Verify that all of the IP address fields use the nnn.nnn.nnn.nnn
format for IP address information.


---------  

NET5435:  DHCP must be selected before DDNS can be selected.



Cause:  DHCP must be configured before DDNS can be selected.

Action:  Select DHCP support before selecting DDNS support.


---------  

NET5436:  When DHCP is not selected, IP address, subnet mask, router, 
nameserver, and IP domain name must all be specified.



Cause:  When DHCP is not enabled, IP address, subnet mask, router,
nameserver, and IP domain name must all be specified.

Action:  Specify all the required IP information using the xxx.xxx.xxx.xxx
format.


---------  

NET5437:  Network adapter type is required when it is not defined in the 
machine class.



Cause:  The network adapter type is not defined in the machine class so
it must be specified in the create machine request.

Action:  Specify the network adapter type for the remote IPL workstation
create machine request.


---------  

NET5438:  Monitor type is required when it is not defined in the machine 
class.



Cause:  The monitor type is not defined in the machine class so it must be
specified in the create machine request.

Action:  Specify the monitor type for the remote IPL workstation create
machine request.


---------  

NET5439:  An error was detected while querying or defining printers.



Cause:  One or more printers could not be queried or defined.

Action:  Perform one or more of the following:
* Verify that all printer related values are valid.
* Verify that the printer drivers are installed on the system.



---------  

NET5440:  The machine definition could not be deleted.



Cause:  The machine to be deleted may be active or the attribute of
machine configuration files is set to read-only.

Action:  Perform one or more of the following:

* Verify that the machine to be deleted is not active.
* Verify that the attribute of the machine configuration directories
  and files is not set to read-only.


---------  

NET5441:  An error was detected while deleting machine configuration 
directories on the remote IPL server.



Cause:  The attribute of machine configuration files is set to read-only
or may be locked by the file system.

Action:  Perform one or more of the following:

* Verify that the machine to be deleted is not active.
* Verify that the attribute of the machine configuration directories
  and files is not set to read-only.


---------  

NET5450:  A machine definition of the type requested does not exist on the 
remote IPL server.



Cause:  A machine definition of the type requested could not be found on
the remote IPL server.

Action:  Verify that the machine definition exists on the remote IPL
server or specify a different type.


---------  

NET5460:  An error was detected while reading the machinename.INI file.



Cause: A error occurred while trying to read the
\IBMLAN\RPL\MACHINES\machinename\machinename.INI file.  The file does not
exist or has been corrupted.

Action:  The remote IPL workstation definition must be deleted and recreated
to rebuild the machinename.INI file.


---------  

NET5470:  The remote IPL OS/2 boot drive identifier cannot be changed because 
the machine has a Workplace Shell desktop defined.



Cause:  The remote IPL OS/2 boot drive identifier cannot be
changed because the machine being used as a model or the machine
being updated has an existing Workplace Shell desktop defined.

Action:  No action is possible.


---------  

NET5471:  The machine definition name cannot be changed.



Cause:  The machine definition name cannot be changed after the machine
definition has been created.

Action:  No action is possible.


---------  

NET5472:  The machine definition OS/2 version cannot be changed.



Cause:  The machine definition OS/2 version cannot be changed after the
machine definition has been created.

Action:  No action is possible.


---------  

NET5473:  The machine definition parameter specified is not valid for the 
current machine definition type.


Cause:  Either a DOS image parameter was specified for an OS/2 machine
definition, or an OS/2 boot drive parameter was specified for a DOS
machine definition.

Action:  Correct the parameter and try the operation again.


---------  

NET5474:  An error was detected while updating the machinename.INI file.



Cause:  The \IBMLAN\RPL\MACHINES\machname\machname.INI file cannot be
created or it has been corrupted and cannot be updated.

Action:  The Remote IPL workstation definition must be deleted and recreated
to rebuild the machinename.INI file.


---------  

NET5480:  The DOS image file name does not exist.



Cause:  The DOS image file name could not be found on the remote
IPL server.

Action:  Specify a valid DOS image file name.


---------  

NET5490: The machine class definition does not exist.



Cause: You referred to a machine class that is not defined on the
specified RIPL server.

Action: Verify that the machine class name was typed correctly.  To display
a list of existing machine classes, type the following command:

    NET RIPLMCLAS /OS:OSVersion

where /OS:OSVersion specifies the name of the operating system that
will be used by the client.  A valid 'OSVersion' value is no more
than 12 bytes in length, using 8.3 format. /OS is required.



---------  

NET5491:  An error was detected while reading the machineclass.INI file.



Cause:  The IBMLAN\RPL\MACHINES\os_version\machineclass\machineclass.INI
file cannot be read.  The file does not exist or has been corrupted.

Action:  The WorkSpace On-Demand OS client code must be reinstalled.


---------  

NET5492: The machine class definition already exists.



Cause:  A machine class definition with this name already exists on the
remote IPL server.  Machine class names must be unique for a given operating
system version on the specified server.

Action: Specify a different machine class name and try the operation again.


---------  

NET5493: An error occurred while creating the machine class.



Cause:  Directories required for machine class configuration could not be
created.

Action: Verify that there is enough disk space and that the disk is usable
on the remote IPL server, and try the operation again.


---------  

NET5494: An error was detected while deleting the machine class directory on 
the remote IPL server.



Cause:  An error was detected while deleting the
\IBMLAN\RPL\MACHINES\osversion\machineclass directory.
A file may be in use.

Action: Correct the problem and try again.


---------  

NET5495: An error was detected while reading MCLASS.RSP, the machine class 
configuration file.



Cause:  An error was detected while reading the
\IBMLAN\RPL\MACHINES\osversion\MCLASS.RSP file.
The file does not exist or has been damaged.

Action:  Do one or more of the following:
         * Restore the file from a backup copy.
         * Verify that the format of the file is valid, as described in
           the "WorkSpace On-Demand 2.0 Administrator's Guide."
         * Examine the WPINSTAL.LOG file in the \OS2\INSTALL directory
           for other possible actions.


---------  

NET5496: An error was detected while reading machine class video configuration
files.



Cause:  An error was detected while reading one of the files in the
\IBMLAN\RPL\MACHINES\osversion\VIDEO directory.  The file does not exist
or has been damaged.

Action:  Do one of the following:
         * Restore the file from a backup copy.
         * Verify the format of the file is valid, as described in the
           "WorkSpace On-Demand 2.0 Administrator's Guide."


---------  

NET5497: The machine class name is not valid.



Cause:  The format of the machine class name entered violates the specified
naming convention.  Machine class names can be up to 8 bytes in length and
you can use any characters except imbedded blanks and the following:

                   " / \ [ ] ; : . |  < > + = , ? *

Action: Type a valid machine class name.


---------  

NET5498: The machine class remark is too long.



Cause: The machine class remark specified is too long.  Machine Class
remarks can be a maximum of 255 bytes.

Action: Type a valid machine class remark.


---------  

NET5499: The existing machine class definition contains an item not found in 
the MCLASS.RSP response file.



Cause:  A parameter value was specified that is not in the MCLASS.RSP
response file.

Action: To modify the parameter value, you must either specify a value that
is found in the MCLASS.RSP response file or you must install an MCLASS.RSP
response file that contains the specified value.


---------  

NET5626: The data in the CONFIG.SYS file for the machine class is not valid.



Cause:  One of the following occurred:

        * /UCONFIGSYS was specified more than 15 times with the
          NET RIPLMCLAS command.
        * The value associated with a /UCONFIGSYS switch was more
          than 1024 bytes in length.
        * The total amount of text for the machine class CONFIG.SYS
          file is more than 4028 bytes in length.

 Action: Try the command again, and verify the following:

         * There are no more than 15 /UCONFIGSYS switches specified
           per NET RIPLMCLAS command.
         * There are no values associated with a /UCONFIGSYS switch that
           is more than 1024 bytes long.
         * The total amount of user-added data currently in the machine
           class CONFIG.SYS file and the data specified with the /UCONFIGSYS
           switches does not exceed 4028 bytes.


---------  

NET5627: The target server does not support DHCP boot clients.



Cause:  Information specific to DHCP boot clients was specified while
        adding or modifying a RIPL requester definition on a remote server.
        The remote server does not support DHCP boot clients.

Action: Try the operation again, doing one of the following:
        * Specify the name of a server that supports the PXE DHCP protocol.
        * Do not specify any DHCP boot information.  DHCP boot information
          is specified with the following command line options:

          /BOOT:DHCP, /NBDD, /NBNS, /NODETYPE, /SCOPE, and /PROTOCOLx:TCPBeui.


---------  

NET5628: The target server does not support the specified operating system 
version.



Cause:  You specified an operating system version that is not installed or
supported on the target server.

Action: Try the operation again, doing one of the following:
        * Specify the name of a server that supports the requested
          operating system version.
        * Specify an operating system version that is supported on the
          target server.


---------  

NET5629: A SCSI hard disk requires a SCSI adapter.



Cause:  A hard disk of type "SCSI" was specified for this machine class,
but the machine class does not include a SCSI adapter.

Action: Specify a SCSI adapter or specify a different hard disk type.  Valid
hard disk types are NONE, IDE, SCSI, and BOTH.  A list of SCSI adapters can
be found in MCLASS.RSP.


---------  

NET5630: The target server does not support the creation, modification, or 
deletion of machine classes.



Cause:  An attempt was made to create, modify, or delete a machine class
on a server that does not support these actions.

Action: Try the operation again, specifying the name of a server that
supports these actions.


---------  

NET5631: Machine classes that were not created with the Administration 
Graphical User Interface (GUI) or the command line interface (CLI) cannot be 
modified or deleted.



Cause:  The specified machine class was selected for modification or deletion.

Action:  Specify a different machine class name.  The specified machine class
cannot be modified or deleted.



---------  

NET5632: The specified network adapter does not support the selected boot 
method.



Cause:  One of the following occurred:

        * The specified network adapter supports only the 802.2 boot method.
          Neither 802.2 or RIPL was specified as the boot method.
        * The specified network adapter supports only DHCP Boot
          and DHCP Boot is not specified as the boot method.

Action: Try the command again, specifying a different network adapter or boot
method, and make sure the network adapter supports the boot method specified.


---------  

NET5633: When NetBIOS scope, node type, NetBIOS datagram distributor, or 
NetBIOS name server are specified, TCP/IP must be configured.



Cause:  One or more of the following machine definition options were
        specified for a machine that does not have TCP/IP configured:
        /NBDD, /NBNS, /NODETYPE, /SCOPE.

        TCP/IP is configured when either:

        - /DHCP and /DDNS are both set to No, and all of
          the following are specified:

         /IP, /NIP, /RIP, /SUBM, and /TCPDN.

        OR

        - /DHCP and /DDNS are both set to Yes, and both /TCPNAME
          and /TCPDN are specified.

        OR

        - /DHCP is set to Yes and /DDNS is set to No.

Action: Configure TCP/IP or do not specify values for /NBDD, /NBNS,
        /NODETYPE or /SCOPE.


---------  

NET5634: The *** option is not supported by the specified operating system 
version.



Cause:  An option was specified that is not supported by the operating
system version.

Action: Specify a different operating system version that does support
the option, or do not specify the option that is not supported.


---------  

NET5635: This action is not supported by the level of software installed on 
the client machine.



Cause:  This action is not supported.

Action:  If you require the function supported by the action, your software
must be upgraded.


---------  

NET5636: An error occurred while reading IBMLAN\SYSLEVEL.NCU.



Cause:  The IBMLAN\SYSLEVEL.NCU file is missing or damaged.

Action: Replace the file with a backup copy.


---------  

NET5637: An error was detected while querying or defining the monitor or 
resolution values.



Cause:  The monitor or resolution values could not be queried or defined
for the specified video type.

Action: Perform one or more of the following:
        * Verify that the monitor and resolution values are valid for the
          specified video type.
        * Verify that the monitor is defined on the system.


---------  

NET5638: TCPBEUI is not configured correctly for the specified node type.



Cause:  When TCPBEUI node type is specified as either P or H, the NetBIOS
datagram distributor and NetBIOS name server must be specified.  When the
node type is B, the NetBIOS datagram distributor, NetBIOS name server, and
NetBIOS scope cannot be specified.

Action: Specify the required parameters.


---------  

NET5639: The Server does not have TCP/IP configured.  TCP/IP is required when 
DHCP is the boot method or TCPBEUI is the network protocol.



Cause:  The server must be configured for TCP/IP when DHCP boot is the
boot method or TCPBEUI is the network protocol.


Action: Do one of the following:
        * Configure the server for TCP/IP.
        * Specify the 802.2 boot method.
        * Specify NETBEUI as the network protocol.


---------  

NET5640: The Server LAN Services is not configured for TCPBEUI.   TCPBEUI 
configuration is required when TCPBEUI is the selected network protocol.



Cause:  The Server LAN Services must be configured for TCPBEUI when TCPBEUI
is the selected network protocol.

Action:  Use the OS/2 LAN Services Installation and Configuration tool to
configure the LAN Server machine for TCPBEUI.


---------  

NET5641: The class or operating system version parameters cannot be modified 
for an existing RIPL requester definition.



Cause:  You attempted to modify the class or operating system version
parameter of a RIPL requester.

Action: Do not specify values for the class or operating system version
parameters when modifying an existing RIPL requester definition.


---------  

NET5642: An error occurred while copying user application files and 
directories.  However, the application was assigned successfully.



Cause:  An error occurred while copying files and directories from
\IBMLAN\DCDB\APPS\<appname> into \IBMLAN\DCDB\USERS\<user>\<appname>.

Some of the possible reasons are:
 - The subdirectory \IBMLAN\DCDB\USERS\<user> could not be created.
 - The subdirectory \IBMLAN\DCDB\USERS\<user>\<appname> could not be created.
 - The \IBMLAN\DCDB\APPS\<appname>\<subdir>\...\<subdir> path length exceeded
   the maximum length allowed.
 - The \IBMLAN\DCDB\USERS\<user>\<appname>\<subdir>\...\<subdir> path length
   exceeded the maximum length allowed.
 - The disk drive where the \IBMLAN directory is located is full.

Action:
 - Verify that the user has authority to create the subdirectories and access
   control profiles.
 - Verify that the application path length is less than 255 bytes.
 - Verify that there is enough disk space.


---------  

NET5643: The value entered for the locally administered address is not valid.



Cause:  The locally administered address value is not in the valid specified
        format.

Action: Try the operation again, specifying a valid locally administered
        address.  Locally administered addresses must be 13 bytes in length.
        The first byte must be either 'T' for token-ring network format, or
        'I' for IEEE standard notation Ethernet address format.  The remaining
        12 bytes must be a hexadecimal number.


---------  

NET5644: When a locally administered address is specified, NETBEUI must be 
selected as either the boot protocol or the additional protocol.



Cause:  A locally administered address value was specified, but the boot
        protocol or the additional protocol is not specified as NETBEUI.

Action: Do one of the following:
        * Do not specify a locally administered address.
        * Specify NETBEUI as the boot protocol or the additional protocol.


---------  

NET5684: The temporary environment name is not valid.



Cause:  The temporary environment name is more than 8 characters or
starts with "BB" or "OS2".

Action:  Specify a valid temporary environment name.


---------  

NET5685: A temporary environment already exists for this machine.



Cause:  Only one temporary environment name is allowed for each machine.
It already exists for this machine.

Action:  Delete the temporary environment for this machine before creating
another one.


---------  

NET5686: The temporary environment directory name already exists.



Cause:  The temporary environment directory cannot be created because this
directory already exists.

Action: Specify a different temporary environment name.


---------  

NET5687: There is no temporary environment for this machine to delete.



Cause:  The temporary environment does not exist for this machine and
cannot be deleted.

Action:  Specify a different machine name.


---------  

NET5690: The temporary environment has not been deleted.



Cause:  The temporary environment delete action for this machine failed
due to internal file damage.

Action:  Delete this machine configuration and create a new one.


---------  

NET5692: Invalid Directory: %s



Cause: The directory name is not correct.

Action: Specify complete path name of the directory.


---------  

NET5702: The temporary environment has not been created.



Cause:  The temporary environment create action for this machine failed
due to internal file damage.

Action:  Delete this machine configuration and create a new one.


---------  

NET8002: The name of the function detecting the error is ***.



Cause:  An internal software error has occurred.  The
function name given detected the error.

Action:  Try the operation again.  If the problem persists,
start the workstation again.  If the problem still persists,
report the problem and the method by which it can be reproduced
to your IBM support representative.


---------  

NET8007: The application could not allocate more memory.



Cause:  The application tried to allocate memory, but
there was not enough available.

Action:  Try the following:
  -  End sessions or applications to free up more memory.
  -  Free up more hard-disk storage to allow more
     virtual memory space.
  -  Reduce buffers or disk cache allocations.
  -  Add physical memory.
  -  Use temporary files to hold portions of the list that
     are not currently on the display.



---------  

NET8023: The fileset *** could not be shared during the LSserver service 
initialization.  The error reported was ***.



Cause:  The share may have failed for any of a number
of reasons:
  -  The directory to be shared does not exist.
  -  An error was encountered while getting the details of
     the alias from the domain control database; either
     the alias no longer exists or the domain control database
     has been damaged.
  -  There was not enough memory to create the buffer for
     the shared resource.

Action:  Try one of the following:
  -  Define the alias to the correct path name again.
  -  Create the directory again.
  -  Refer to the error log for system or network error
     causes; examine the error log to see the message
     that displayed previously.
  -  End sessions or applications to free up memory.
  -  Restore the domain control database from backup.
  -  Add memory to the workstation.



---------  

NET8024: The printer *** could not be shared during the LSserver service 
initialization.  The error reported was ***.



Cause:  The share may have failed for any of a number
of reasons:
  -  An error was encountered while getting the details of
     the alias from the domain control database; either the
     alias no longer exists or the domain control
     database has been damaged.
  -  There was not enough memory to create the buffer for
     the shared resource.

Action:  Try one of the following:
  -  Define the alias to the correct queue name again.
  -  Create the print queue or eliminate the share again.
  -  Refer to the error log for system or network error
     causes; examine the error log to see the message
     that displayed previously.
  -  End sessions or applications to free up memory.
  -  Restore the domain control database from backup.
  -  Add memory to the workstation.



---------  

NET8025: The serial device *** could not be shared during the LSserver service
initialization.  The error reported was ***.



Cause:  The share may have failed for a number of reasons:
  -  The device to be shared does not exist.
  -  An error was encountered while getting the details of
     the alias from the domain control database; either
     the alias does not exist any more or the domain control
     database has been damaged.
  -  There was not enough memory to create the buffer for
     the shared resource.
  -  The limit for serial device resources has been reached.
  -  An internal error occurred during the attempt to con-
     figure the serial device queue data in memory.

Action:  Try one of the following:
  -  Define the alias to the correct port name again.
  -  End sessions or applications to free up memory.
  -  Refer to the error log for system or network error
     causes; examine the error log to see the message
     that displayed previously.
  -  Restore the domain control database from backup.
  -  Add memory to the workstation.



---------  

NET8026: Filesets could not be shared during the LSserver service 
initialization.  The database access error was ***.



Cause:   An error occurred while attempting to list all
the files aliases defined in the domain control database.
There may not have been enough memory to allocate space for
the list of files aliases, or the domain control database
could not be read, possibly because the file has been
damaged.

Action:  Try one of the following:
  -  Try the operation again.
  -  End sessions or applications to free up memory.
  -  Copy a backup version of the domain control database
     onto the domain controller hard disk in
     d:\IBMLAN\DCDB\DATA, where d: is the drive on
     which the network program was installed.



---------  

NET8027: A printer could not be shared during the LSserver service 
initialization.  The database access error was ***.



Cause:  An error occurred while attempting to enumerate
all the printer aliases defined in the domain control
database.  There may not have been enough memory to
allocate space for the list of files aliases, or the
domain control database could not be read.

Action:  Try one of the following:
  -  Try the operation again.
  -  End sessions or applications to free up memory.
  -  Copy a backup version of the domain control database onto
     the domain controller hard disk in d:\IBMLAN\DCDB\DATA,
     where d: is the drive on which the network program was
     installed.  Start the workstation and the network again.



---------  

NET8028: Serial devices could not be shared during the LSserver service 
initialization.  The database access error was ***.



Cause:  An error occurred while attempting to enumerate all
the serial device aliases defined in the domain control database.
There may not have been enough memory to allocate space for
the list of serial device aliases, or the domain control database could
not be read.


Action:  Try one of the following:
  -  End sessions or applications to free up memory.
  -  Restore the domain control database from a backup copy to
     d:\IBMLAN\DCDB\DATA, where d: is the drive on which the
     network program has been installed.  Start the workstation again
     and start the server again.



---------  

NET8030: The \IBMLAN directory structure could not be shared.



Cause:  The directory name may already be shared.  This
may be a hard-disk error.

Action:  Run hardware diagnostics.  Install the LAN Server
code again and choose to save your domain control database.


---------  

NET8031: A system error occurred while opening a database file.



Cause:  An error occurred when the DCDB was opened in order
to read the additional server description.  Either the DCDB
is damaged or the internal buffer where the alias details
are kept was too small.  Another cause may be that creation
of an external resource batch file for a newly defined external
resource failed.  There are several reasons this can occur:
 - The template could not be opened, read from, or closed successfully.
 - The new batch file (ALIAS.CMD or ALIAS.BAT) could not be created,
   written to, or closed successfully.
   The .BAT and .CMD files are created in the directories
   \IBMLAN\DCDB\FILES, \IBMLAN\DCDB\PRINTERS, and \IBMLAN\DCDB\DEVICES.

Action:  Try the operation again.  If the problem persists, copy
a backup version of DCDB to d:\IBMLAN\DCDB\DATA, where d: is the
drive on which the network program was installed.  Start the
workstation again and start the network program.  If the external
resource batch-file failure occurred, ensure that the ETEMPLAT.BAT
and ETEMPLAT.CMD files exist on the domain controller in the
\IBMLAN\DCDB directory.  Also ensure that the files are not
read-protected.  Then verify that the correct directories still exist:
\IBMLAN\DCDB\FILES, \IBMLAN\DCDB\PRINTERS, and \IBMLAN\DCDB\DEVICES.
Your hard disk must have enough space left to create a new external
resource file, which will be similar in size to the template files.



---------  

NET8036: An error occurred while creating the Network Application folder.



Cause:   The class 'LsApps' did not register successfully
         because the file LSAPPS.DLL is not installed in one of
         the LIBPATH directories.

Action:  Locate LSAPPS.DLL and update your LIBPATH in your
         CONFIG.SYS file.  If LSAPPS.DLL cannot be found, reinstall
         LAN Server.  Shut down and restart your machine.


---------  

NET8037: LAN Server was unable to delete the Network Applications folder 
during logoff.



Cause:   The logoff process failed to delete the Network Applications
         folder and its contents from the desktop.

Action:  Delete the folder from the desktop.


---------  

NET8038: The class 'LsProg' cannot be found.



Cause:   The file LSPROG.DLL does not exist in one of the LIBPATH
         directories.

Action:  Locate LSPROG.DLL and update your LIBPATH in your
         CONFIG.SYS file.  If LSPROG.DLL cannot be found, reinstall
         LAN Server.  Shut down and restart your machine.


---------  

NET8039: There is not enough memory available to create the program object 
***.



Cause: The possible reasons are:
       - The operating system has already allocated as much physical
         RAM as possible.
       - The memory is too fragmented for the request to be satisfied.
       - The operating system is unable to swap memory blocks to the
         swapper file.

Action: Do one or more of the following:

       - Add additional physical RAM.
       - Tune other applications so that they do not use more memory
         than needed.
       - Ensure that there is enough disk space to expand the swapper file.


---------  

NET8041: Error *** occurred while connecting *** to ***.
          Do you want to continue ?



Cause:   One of the following occurred:
         - Your workstation cannot establish a session with the server.
         - The device is already assigned to another resource.

Action:
         - Ensure that you have access to the resource.
         - If the specified device is assigned to another resource,
           delete the existing connection.  Stop the current operation
           and start the application again.


---------  

NET8042: Error *** occurred while deleting connection to ***.



Cause:   The connections that were established for this application
         could not be deleted because there may be other processes
         using the application.

Action:  Type NET USE <device name> /D to delete the connection.


---------  

NET8064: An OS/2 error has occurred. Correct the problem and press Enter.



Cause:  The function was trying to open a file
to perform a read or write task but could not
do so because of an OS/2 error.

Action:  Verify that the drive selected is valid
and functioning properly.  Run diagnostics using
the reference diskette that came with your
workstation to test the disk.  You must be logged
on with administrator privilege.


---------  

NET8073: The specified drive is not a diskette drive.



Cause:  An incorrect drive was specified.

Action:  Change the drive specified to a local
physical diskette drive.


---------  

NET8074: There is not enough memory available to run this command.



Cause:  There is not enough memory available for
the requirements placed on the system.

Action:  Reduce the memory requirements, or
increase the memory in the workstation.  End
sessions or applications to free up memory.
Verify the memory by running diagnostics using
the reference diskette that came with the
workstation.


---------  

NET8075: parameter is not valid.



Cause:  The parameter specified is not valid.

Action:  Change the parameter or verify that you
typed the parameter correctly.


---------  

NET8076: An error occurred while creating the image.



Cause:  The image file could not be created on
the server.

Action:  Examine the image definition and required
files.  Verify that the image name is valid.  Verify
that network services are started.


---------  

NET8077: An error occurred while writing the image.



Cause:  The image file could not be created on the
server.

Action:  Examine the image definition and verify
that the required files exist.  Verify that the
target disk contains sufficient available storage.
You must be logged on with administrator privilege.


---------  

NET8078: An error occurred while reading the diskette.



Cause:  The source diskette specified for creating
the image file is incorrect.

Action:  Verify that the source diskette is a
bootable DOS diskette.



---------  

NET8079: An error occurred while reading source file ***.



Cause:  The image definition file specified for
creating the image file is incorrect.

Action:  Verify that the file exists and then try
the operation again.



---------  

NET8080: An error occurred while writing file *** to the diskette.



Cause:  The image diskette is full.

Action:  Use another diskette to finish creating
the image definition file.



---------  

NET8081: An error occurred while opening file *** on the diskette.



Cause:  The image diskette is incorrect.

Action:  Create the image definition diskette again.



---------  

NET8082: Insert the diskette and type the command again.



Cause:  There is no diskette in the drive.

Action:  Insert the image diskette and type the
command again.


---------  

NET8083: File *** in the image definition file cannot be found.



Cause:  The file in the image file does not exist on
the remote IPL server.

Action:  Ensure that the file is present as specified
or correct the image definition file.


---------  

NET8084: There are too many files specified for the image.



Cause:  There are too many files specified in the
image definition file.

Action:  Examine the image for files that can be
eliminated.  Try the operation with fewer files
specified in the image.


---------  

NET8085: The image is full.  Request a larger image.



Cause:  The image file is full.

Action:  Examine the image for files that can be
eliminated.  Try the operation with fewer files
specified in the image or request a larger image.


---------  

NET8086: The image definition file could not be found.



Cause:  The image definition file does not exist on
the domain controller disk.

Action:  The image definition file must exist on the
domain controller disk.  Verify that the image file
does not exist on the server disk.  If it does not,
create the image file again and copy it to the
server disk.  You must be logged on with administrator
privilege.



---------  

NET8087: The image definition file has a format that is not valid.



Cause:  The format of the image definition file is
not valid.

Action:  Examine the syntax of the image definition
file.  You can use one of the image definition files
shipped with LAN Server, or you can use them as
models to create your own.  You must be logged on
with administrator privilege.


---------  

NET8088: The DOS system file *** could not be copied.



Cause:  DOS system files cannot be found or access
to those files is denied.

Action:  Verify that the DOS system files exist.
Verify that you have access to the files.


---------  

NET8089: The file name *** is duplicated in the image.



Cause:  The file name in the image definition file
is not unique.

Action:  Change the duplicate file name to a unique
file name in the image definition file.


---------  

NET8090: The specified drive does not exist.



Cause:  The specified diskette drive is not valid.

Action:  Specify a valid drive.


---------  

NET8091: The directory path *** is not valid.



Cause:  The DOS path contained in the message cannot be resolved.

Action:  Specify a valid path name.



---------  

NET8092: Another process is accessing the diskette drive.



Cause:  The diskette drive has already been opened by
another process.

Action:  End sessions or applications accessing the
diskette drive or wait for the diskette drive to
become available.


---------  

NET8093: An error occurred while reading file *** on the diskette.



Cause:  The diskette file contained in the message is not correct
nor consistent.

Action:  Try the operation again or try another workstation.
If the problem persists, obtain another copy of the file.


---------  

NET8094: A serious *** error *** was detected by ***.



Cause:  An internal software error was detected.

Action:  Try the operation again or try another workstation.
Verify that your OS/2 files are not damaged.
You must be logged on with administrator privilege.
If the problem persists, start the workstation again.
If the problem still persists, report the problem and
the method by which it can be reproduced to your IBM
support representative.


---------  

NET8153: The source drive type is incorrect, or the diskette is faulty.



Cause:  Either the drive you are trying to use is the wrong type, or the
diskette is faulty.

Action:  You must specify a diskette drive that can read the diskette
from which the image will be built.  Specify a valid drive or use a
different diskette.


---------  

NET8154: The destination drive or diskette is not valid.



Cause:  One of the following has occurred:

* The drive you are using is of a different type or capacity from the
  one specified in your definition file.
* The diskette you are using is formatted for a capacity other than the
  one specified in your definition file.
* The diskette is unusable.

Action:  Specify a valid drive or use a different diskette.  To make an
image on diskette, you must use a drive and diskette that are compatible
with the type specified by the definition file in both physical size and
capacity.  You can make an image on a diskette that is larger than that
specified by the definition file.


---------  

NET8155: There is no definition file for this image.



Cause:  There must be a definition file to make an image on a diskette.

Action:  Create a definition file for the selected image.  Try the
operation again.


---------  

NET8156: The selected definition file cannot be read.



Cause:  This error indicates a fault on the disk that contains the
definition file.

Action:  Verify that the disk storing the definition file is usable and
try the operation again.


---------  

NET8157: The definition file is not valid.



Cause:  The definition file specifies that the diskette image is to be
built from a diskette.  However, you cannot make an image from a diskette
to a diskette.  You can only make an image to diskette from a set of file
names in the definition file.

Action:  Select an image with a compatible definition file and try again.
If you want to make an image of a diskette on another diskette, use
DISKCOPY.


---------  

NET8158: The diskette you are trying to use cannot start a DOS machine.



Cause:  You must use a valid DOS system diskette in order to do the
following:
  -  Create an image to a target diskette from a definition file on
     the source server.
  -  Create an image file on the target server from a source diskette.

Action:  Format a diskette with DOS 3.3 or higher, using the /S option,
or obtain a valid DOS system diskette.


---------  

NET8159: The RPL.MAP file on the source server does not contain the
          specified server record.



Cause:  The server record identifier either is not defined in an enabled
server entry or is not a DOS type in the RPL.MAP file indicated in the
error message.

Action:  Ensure that an enabled server entry with the server record
identifier (12th field) is present and is a DOS type.  Try the operation
again.


---------  

NET8160: The RPL.MAP file was not found on the source server.



Cause:  In order to make an image to a diskette from an image definition
file, the RPL.MAP file must be present on the source server.

Action:  Ensure that RPL.MAP exists on the source server in the
\IBMLAN\RPL directory.


---------  

NET8161: An error occurred while reading a source file needed to create
          the image file.



Cause:  The source file is not valid.

Action:  Copy a valid source file from a remote IPL server and then try
the operation again.


---------  

NET8162: An error occurred while writing data to the diskette,
          indicating that the diskette might be full.



Cause:  The image diskette might be full.

Action:  Retry the operation using a higher density diskette.


---------  

NET8163: A source file specified in the image definition file could not
          be opened on the target diskette.



Cause:  A file on the diskette image could not be opened.  A necessary
source file might not have been specified in the image definition file.

Action:  Correct the image definition file and retry the operation.


---------  

NET8164: A file specified in the image definition file cannot be found.



Cause:  The image definition file might be incorrect, or the target
remote IPL server might not have the correct software installed to
support this operation.

Action:  Ensure that the file is present as specified or correct the
image definition file.


---------  

NET8165: A DOS system file could not be accessed.



Cause:  DOS system files cannot be found, or access to those files is
denied.

Action:  Verify that the DOS system files exist.  Verify that you have
access to the files.


---------  

NET8166: The same source file name appears twice in the image
          definition file.



Cause:  A file name in the image definition file is not unique.

Action:  Change the duplicate file name to a unique file name in the
image definition file.


---------  

NET8167: An error occurred while reading a file during the process of
          adding the LAN device drivers to the diskette image.



Cause:  The adapter .CNF file may be incorrect, or the image definition
file may be incorrect.  These files are located on the source server.

Action:  Perform one or both of the following:

1. Verify that the adapter .CNF file is correct.  If it is incorrect,
   from a remote IPL server, copy the valid .CNF file for the adapter for
   which you are building the image and then try the operation again.

2. Verify that the image definition file is correct.  If it is incorrect,
   edit the file, make corrections, and try the operation again.


---------  

NET8168: An error was detected while trying to update the AUTOEXEC.BAT
          file on the diskette.



Cause:  In particular, this error might have been caused because of
problems manipulating the AUTOEXEC.BAK file.

Action:  Verify that the diskette is correctly inserted into the drive.
Also verify that there is enough space on the diskette and enough file
handles on the server.  Try the operation again.


---------  

NET8169: The server record identifier is not valid.



Cause:  The server record identifier must be from 1 to 40 characters.
You can use any characters except imbedded blanks and the following:

  . " / \ [ ] ; : | < > + = , ? * ~

The server record identifier must identify a DOS server record and
its first 3 characters must be R_D.

Action:  Type a valid server record identifier using the correct format.


---------  

NET8170: The machine name you gave is not in the correct format.



Cause:  The format of the machine name you entered violates the specified
naming convention.  Machines names can be up to 15 bytes, and you can use
any characters except imbedded blanks and the following:

  " / \ [ ] ; : | < > + = , ? *

Action:  Type a valid machine name.


---------  

NET8171: The image ID is an incorrect length or contains incorrect
          characters.



Cause:  An image ID contains 1 to 8 characters.  You can use any
character except imbedded blanks and the following:

  . " / \ [ ] ; : | < > + = , ? *

The first character must not be numeric, and the last must not be $.

Action:  Type a valid image ID.


---------  

NET8181: The logon assignment of files alias *** to *** failed.



Cause:  Before logon, a list of files may have been
designated to be assigned at logon.  One or more assignments
failed for one of the following reasons:
  -  The server on which the resource exists is not
     started.
  -  The drive may already be in use.
  -  The path does not exist.

Action:  Verify that the server providing the resource
is started.  Try the assignment again while you are
logged on.  If the problem persists, verify that the
resource is on that server.  Ensure that you have
access rights to the server.  Try again later when there
is no network activity with the files resource.  Print
the error log for analysis.


---------  

NET8182: The logon assignment of serial device queue *** to *** failed.



Cause:  Before logon, a list of resources including
serial device queues may have been designated to be
assigned at logon.  One or more assignments failed for
one of the following reasons:
  -  The server on which the resource exists is not
     started.
  -  The device to which you are trying to assign a
     resource is already in use.
  -  The device is not shared.
  -  The serial device does not exist.

Action:  Verify that the server providing the resource
is started.  Try the assignment again while you are
logged on.  If this also fails, verify that the resource is
on that server.  Ensure that you have access rights to the
server.  Try again later when there is no network activity
with the device.  Print the error log for analysis.


---------  

NET8183: The logon assignment of printer queue *** to *** failed.



Cause:  Before logon, a list of resources including
printer queues may have been designated to be assigned
at logon.  One or more assignments failed for one of the
following reasons:
  -  The server on which the resource exists is not started.
  -  The printer is already in use.
  -  The device is not shared.
  -  The printer does not exist.

Action:  Verify that the server providing the resource
is started.  Try the assignment again while you are
logged on.  If this also fails, verify that the resource
is on that server.  Ensure that you have access rights to
the server.  Try again later when there is no network
activity with the files resource.  Print the error log for
analysis.


---------  

NET8188: A user is already logged on at this requester.



Cause:  A requester can have only one user logged on at a time.

Action:  Log the user off, or go to a different workstation.


---------  

NET8191: Your home directory could not be set up.



Cause:  The server on which the home directory resides may
not be running or the logon program could not find your
home directory.  You may not have access to the home
directory.

Action:  Verify that the server is started.  Confirm that
the home directory exists on the server.  Report the problem
to your network administrator.


---------  

NET8193: The domain controller could not be contacted.  The logon was 
validated by a backup server.  No LAN Server update activities will be 
allowed.



Cause:  The domain controller on this domain could not be identified.

Action:  Ensure that the Server service is started on the domain controller.


---------  

NET8194: One or more of your logon alias assignments failed.



Cause:  The assignment was made to a server that is not
running, the level of access may not be correct, or the
access control profile may be denying access.

Action:  Check the error log to see which assignments
failed.  Verify that the alias exists on the server and that
the server is started.  Verify that each alias assignment
has an access control profile with the appropriate
permissions.


---------  

NET8195: An error occurred while running your user profile.



Cause:  The command file that is run automatically at logon
returned an error.

Action:  Examine the logon profile to determine what might
be causing the error.  The profile is called PROFILE.CMD if
you are on an OS/2 requester or PROFILE.BAT if you are on a
DOS requester.  The profile is located on the domain
controller in the \IBMLAN\DCDB\USERS\user directory, where
user is the ID of the user whose logon profile returned an
error.


---------  

NET8198: Any logon assignments, applications, or the PROFILE.CMD file could 
not be retrieved to be set up or run by the logon program.



Cause:  The logon program could not connect to a required share.

Action:  Start the LSserver service on the domain controller again.

---------  

NET8210: One or more device redirections are currently in use.



Cause:  Logoff is the disconnection from external and internal
resources.  An attempt at one or more resources has failed.
You may be prevented from logging off because resources
(like redirected drives) are still in use.  The problem may
be the result of a faulty connection to a server, or you may
still have access to the resource.

Action:  Try the operation again.  Print the error log.
Verify your access to the resource.  Start the workstation
again.  If the problem persists, go to the session where
the redirected drive is the current drive, and make a local
drive the current drive.  Analyze the error log for system
or network errors.  If the problem persists, restore the
domain control database from a backup copy.


---------  

NET8215: OS/2 error number *** occurred while opening ***.



Cause:  The operation was trying to open a new file for
a read or write process but was unsuccessful because of
an OS/2 error.

Action:  Try the operation again.  If the problem
persists, run diagnostics or the reference
diskette to test the disk.  The error code specified
is an OS/2 error code.  To get more information about
the error, type:

  HELP message#

where message# is the error code.


---------  

NET8228: The machine ID could not be added to the network adapter.



Cause:  Either someone in the network already has that
particular machine ID, or the network adapter is not working
properly.

Action:  Verify that the machine ID is unique.  If the machine
ID is unique, then the adapter is not working.  Replace the adapter.


---------  

NET8229: The access profile for the remote IPL workstation could not be added.



Cause:  The most likely cause of this error is that the resource does not
exist.  There may also be an internal software error.

Action:  Create the resource and ensure it exists.  If the problem
persists, contact your IBM support representative.


---------  

NET8231: Logon is currently not available.  Try again after the server is 
started.



Cause:  Logon is disabled while an additional server is starting.

Action:  Wait until the additional server startup is
complete before trying to log on.


---------  

NET8232: Logoff is currently not available.  Try again after the server is 
started.



Cause:  Logoff is disabled while an additional server is starting.

Action:  Wait until the additional server startup is
complete before trying to log off.


---------  

NET8234: Contention for server resources exceeds capacity.



Cause:  A request for server resources could not be
completed because of activity on the server.

Action:  Increase the value for SRVPIPES in the
IBMLAN.INI file and start the server again.


---------  

NET8235: The LSserver service has encountered an unexpected OS/2 or network 
return code:  ***



Cause:  An OS/2 or network function call failed with the indicated
return code.

Action:  If this error occurs during service initialization, stop
and start all services again.  If the error persists or occurs after
initialization, contact your network administrator.


---------  

NET8250: The domain control database (DCDB) does not exist on this server.



Cause:  The domain control database (DCDB) could not be located.  It must
reside on all primary servers (domain controllers).

Action:  Verify that the directory ibmlan\dcdb\data exists, and that the files
DCDB.A, DCDB.D, DCDB.F, DCDB.I, DCDB.M, and DCDB.P are present.  If any of
these are missing, restore them from a backup copy.  If all of these are
missing, use the installation/configuration program to initialize the DCDB.


---------  

NET8253: The LSserver service could not create the required access control 
list (ACL) for the resource:  ***.



Cause:  An ACL for the resource indicated could not be created at LSserver
service initialization.  The resource may not exist.

Action:  Create the resource.


---------  

NET8256: \IBMLAN\DCDB\IMAGES\RPL.MAP was not found in the domain controller.



Cause:  The RPL.MAP file is not present in the domain controller.

Action:  Ensure that the RPL.MAP file is installed in the
subdirectory \IBMLAN\DCDB\IMAGES in the domain controller.  If
the file cannot be found, install a new RPL.MAP file from
RPLTOK.MAP or RPLPCN.MAP.


---------  

NET8257: \IBMLAN\DCDB\IMAGES\RPL.MAP in the domain controller has a bad file 
format or an I/O error.



Cause:  The RPL.MAP file in the domain controller is damaged
and cannot be read.

Action:  Install a new RPL.MAP file in the subdirectory
\IBMLAN\DCDB\IMAGES in the domain controller.

Try the operation again.  If the problem persists, start the
workstation again.  If the problem still persists, report the
problem and the method by which it can be reproduced to your
IBM support representative.


---------  

NET8258: The RPL.MAP file under the netname RPLFILES was not found in the 
remote IPL server.



Cause:  The RPL.MAP file is not present in the destination remote
IPL server.

Action:  Install a new RPL.MAP file in the subdirectory
\RPLDIR (defined in IBMLAN.INI) in the remote IPL server.


---------  

NET8259: You must be logged on with administrator privilege before running 
this program.



Cause:  Your tried to perform a task that requires administrator
privilege.

Action:  Log on using a user ID that has administrator privilege.


---------  

NET8260: The RPL.MAP file under the netname RPLFILES in the remote IPL server 
has a bad file format or an I/O error.



Cause:  The RPL.MAP file under the netname RPLFILES in the remote IPL
server is damaged and cannot be read.

Action:  Install a new RPL.MAP file in the subdirectory \RPLDIR
(defined in the IBMLAN.INI file) in the remote IPL server.  If the
problem persists, contact your network administrator.


---------  

NET8261: An I/O error occurred while updating the RPL.MAP file under the 
netname RPLFILES on the remote IPL server.



Cause:  The RPL.MAP file under the netname RPLFILES in the remote IPL
server cannot be updated.

Action:  Ensure that there is enough disk space in the
remote IPL server.  If the problem persists, verify that there
are more file handles left in the remote IPL server.  If the
problem still persists, report it to your network administrator.


---------  

NET8262: The Remote IPL service should not be started before running this 
program.



Cause:  The Remote IPL service has been started.

Action:  Stop the Remote IPL service in the remote IPL server.


---------  

NET8263: The IBMLAN.INI file was not found.



Cause:  The \IBMLAN\IBMLAN.INI file is not present on
the remote IPL server.

Action:  Install a new IBMLAN.INI file in the \IBMLAN
subdirectory on the remote IPL server.


---------  

NET8264: The IBMLAN.INI file has a bad format or an I/O error.



Cause:  The \IBMLAN\IBMLAN.INI file on the remote IPL
server is damaged and cannot be read.

Action:  Install a new IBMLAN.INI file in the \IBMLAN
subdirectory on the remote IPL server.  If the problem
persists, contact your network administrator.


---------  

NET8265: An I/O error has occurred on the IBMLAN.BAK file you used for 
updating.



Cause:  Updating the \IBMLAN\IBMLAN.INI file on the remote
IPL server creates a copy, called IBMLAN.BAK.  The IBMLAN.BAK
file is damaged and cannot be updated at this time.

Action:  Ensure that there is enough disk space on the remote
IPL server.  If the problem persists, verify that there are file
handles on the remote IPL server.  If the problem still persists,
report it to your network administrator.


---------  

NET8270: The DOS system files could not be copied.



Cause:  DOS system files cannot be found or access
to those files is denied.

Action:  Verify that the DOS system files exist
on the target server or domain controller.  Verify
that you have access to the files.


---------  

NET8276: Memory could not be allocated by the server during the processing of 
a change boot request from remote IPL requester ***.  The function reporting 
the error is ***.



Cause:  Not enough memory was available at the time the specified remote
IPL requester made the request.

Action:  No action is necessary unless this error is repeated consistently
in the server error log.  If the message does repeat, it may indicate
a shortage of memory on the remote IPL server.  Either end unneeded
applications using memory at the server or add memory to the server.



---------  

NET8277: The file *** could not be opened at the time remote IPL requester ***
made a change boot request.  The requester boot information was not changed.



Cause:  The specified file could not be opened.  Either the file was in use
by LAN Server or by another user.

Action:  No action is necessary unless this error is repeated consistently
in the server error log.  If the message does repeat, it may indicate
that an application other than LAN Server is using the file specified.
If this is correct, the application should be ended.  The message may
also indicate that many remote IPL requesters were attempting to change
their boot records simultaneously.  Those that did not succeed may try
again.




---------  

NET8278: The temporary file *** could not be written to at the time remote IPL
requester *** attempted to make an alternate boot selection.  The requester 
boot information was not changed.



Cause:  The specified file could not be written to.  Either the file was in
use by LAN Server or by another user.

Action:  No action is necessary unless this error is repeated
consistently in the server error log.  If the message does repeat,
it may indicate that an application other than LAN Server is using the file
specified.  If this is correct, the application should be ended.  Only
LAN Server should use this file.  The message may also indicate that
many remote IPL requesters were attempting to change their boot records
simultaneously.  Those that did not succeed may try again.


---------  

NET8279: The file *** could not be opened to reset the alternate boot record 
for remote IPL requester ***.  The alternate boot record is still enabled for 
the requester.



Cause:  The specified file could not be opened.  Either the file was in
use by LAN Server or by another user.

Action:  No action is necessary unless this error is repeated
consistently in the server error log.  If the message does repeat,
it may indicate that an application other than LAN Server is using the file
specified.  If this is correct, the application should be ended.  The
message may also indicate that many remote IPL requesters were starting again
simultaneously with alternate boot records.  Some of these requesters
will successfully revert to their original boot records.  Those that
do not will revert to their original boot records the next time they
are started.


---------  

NET8280: The RPL.MAP file was inconsistent when remote IPL requester *** 
attempted to make an alternate boot selection.  No change was made to RPL.MAP.



Cause:  The selection made by the specified requester was not found in
the RPL.MAP file.  This can happen if a record is deleted, changed, or
commented out after a remote IPL requester has started the CHGBOOT
program.  If the user then selects the record that has been
altered, this error is logged and the remote IPL requester displays an
error message.

Action:  No action is required.  The user at the remote IPL requester
should select a different alternate boot record.


---------  

NET8281: The temporary file *** could not be copied over the file *** at the 
time remote IPL requester *** made a change boot request.  The requester boot 
information was not changed.



Cause:  The specified file could not be overwritten.  Either the file
was in use by LAN Server or by another user.

Action:  No action is necessary unless this error is repeated
consistently in the server error log.  If the message does repeat,
it may indicate an application other than LAN Server is using the file
that is to be overwritten.  If this is correct, the application should
be ended.  The message may also indicate that many remote IPL requesters
were attempting to change their boot records simultaneously.  Those
that did not succeed may try again.


---------  

NET8282: The LAN root path could not be found because a call to 
NetWkstaGetInfo failed during a change boot request from remote IPL requester 
***.  The function reporting the error is ***.



Cause:  An internal LAN Server error occurred.

Action:  No action is necessary unless this error repeats
consistently in the server error log.  If the error repeats, try
the operation again that you were attempting when the error occurred.
If the error persists, report the problem and the method by which it
can be reproduced to your IBM support representative.


---------  

NET8283: The file *** could not be read at the time remote IPL requester *** 
attempted to make an alternate boot selection.  The requester boot information
was not changed.



Cause:  The specified file could not be read.  Either the file was in
use by LAN Server or by the user.

Action:  No action is necessary unless this error is repeated
consistently in the server error log.  If the message does repeat,
it may indicate that an application other than LAN Server is using
the file that is to be read.  If this is correct, the application
should be ended.  The message may also indicate that many remote
IPL requesters were attempting to change their boot records
simultaneously.  Those that did not succeed can try again.


---------  

NET8300: A DosMakeMailslot error occurred.



Cause:  A DosMakeMailslot call can fail if the redirector
NETWKSTA.200 has not been started, if the Requester service has not
been started, or if there is insufficient memory available.

Action:  Ensure that the Requester service and redirector have been
started.  Free memory by closing unused sessions and then starting
the Generic Alerter service again.  The return code from the
DosMakeMailslot call can be found in the system error log.


---------  

NET8301: A NetAlertStart error occurred.



Cause:  A NetAlertStart call can fail if the Requester service
or the redirector NETWKSTA.200 has not been started, if there is
insufficient memory available, or if the Alerter service table is full.

Action:  Ensure that the Requester service and the Redirector have been
started.  Free memory by closing unused sessions and then starting
the Generic Alerter service again.  The return code from the NetAlertStart
call can be found in the system error log.


---------  

NET8302: A DosReadMailslot error occurred.



Cause:  A DosReadMailslot call can fail if the redirector
NETWKSTA.200 has not been started.

Action:  Ensure that the redirector NETWKSTA.200 has been
started and then start the Generic Alerter service again.


---------  

NET8303: A LAN API error occurred.



Cause:  A LAN API error can fail if the redirector NETWKSTA.200
has not been started, if there is insufficient memory available,
if the IBMLAN.INI file is missing or damaged, or if the path to the
IBMLAN.INI file has not been specified.

Action:  Ensure that the redirector NETWKSTA.200 has been started.
Free memory by closing unused sessions.  Ensure that the IBMLAN.INI
file exists and that it is not damaged.  Verify that the path to
the IBMLAN.INI file has been specified in the CONFIG.SYS file.
The name of the function that failed and its return code can be
found in the system error log.


---------  

NET8304: An error occurred while building the generic alert.



Cause:  One of the support files required for the Generic
Alerter service has not been installed or started.

Action:  Ensure that the Generic Alerter service has been installed
properly and then try starting the Generic Alerter service again.


---------  

NET8305: An OS/2 system error occurred.



Cause:  One common cause for an OS/2 system call failure in the
Generic Alerter service is that insufficient memory is available.

Action:  Free memory by closing unused sessions and then
starting the Generic Alerter service again.  The OS/2 system
call that failed and its return code can be found in the system
error log.

---------  

PRO0002: PROTOCOL.INI could not be read.

Cause:  A drive or data error occurred when the program attempted to read
PROTOCOL.INI.

Action:  If PROTOCOL.INI is being read from a diskette, make
sure the diskette is properly inserted into the drive and the
drive door is closed.  If PROTOCOL.INI is being read from
a fixed disk, recreate the PROTOCOL.INI file.

---------  

PRO0003: PROTOCOL.INI could not be opened.

Cause:  One of the following conditions caused an error
to occur when the program attempted to open PROTOCOL.INI.

- The file could not be found in the default directory \IBMCOM
or in the directory specified on the DEVICE= command following the
/I: option switch.

- The file is damaged.

Action:  Reinstall the network drivers and protocol manager.

If PROTOCOL.INI is being read from a diskette drive, make sure the
diskette is inserted properly and the drive door is closed.

---------  

PRO0004: The unrecognized parameter *** was found in PROTOCOL.INI.

Cause:  A configuration parameter is defined in PROTOCOL.INI
that is not associated with a logical module.  The parameter
may be out of order.

Action:  Review the PROTOCOL.INI file and make sure that all
configuration parameters appear under the appropriate logical
module name and are enclosed in brackets.

---------  

PRO0005: System resources are not available to hold PROTOCOL.INI.

Cause:  The system does not have enough memory to hold the
PROTOCOL.INI image.

Action:  Reduce the size of the PROTOCOL.INI file or
add more memory and retry the operation.

---------  

PRO0006: The numeric value specified for configuration parameter *** in 
PROTOCOL.INI is not valid.

Cause:  The numeric value of the configuration parameter
exceeds 2**32 or the network address value is not valid.

Action:  Review the PROTOCOL.INI file and make sure that all
numeric values for configuration parameters are less than 2**32
(4,294,967,296 decimal or 100,000,000 hexadecimal).

---------  

PRO0007: The value specified in keyword *** is not a valid hexadecimal number.

Cause:  An incorrect character was specified in a hexadecimal number.

Action:  Review PROTOCOL.INI to determine the parameter that
contains the incorrect hexadecimal number.  Hexadecimal numbers
can consist of the digits 0 through 9 only and the letters
A through F (uppercase or lowercase).

Hexadecimal values always begin with the prefix 0x or 0X.

---------  

PRO0008: A numeric value specified in keyword *** in PROTOCOL.INI is not a 
valid number.

Cause:  An incorrect character was specified in a numeric field.

Action:  Review PROTOCOL.INI to determine the parameter that
contains the incorrect number.  Numeric values can consist of digits
0 through 9 only.

---------  

PRO0009: The end double quotation mark is missing for keyword *** in 
PROTOCOL.INI.

Cause:  A character string that begins with a double quotation mark
is not ended with one on the same line.

Action:  Find the character string in the PROTOCOL.INI file and end
it with a double quotation mark.

---------  

PRO0010: The option specified is not valid.

Cause:  The only valid option on the DEVICE=path\PROTMAN.OS2 line
must begin with /I: or /i:.  If a device and path name are specified,
that value will override the default path \IBMCOM in locating the
PROTOCOL.INI file.

Action:  Correct the option and try the operation again.

---------  

PRO0011: An equal sign was not found following keyword ***.

Cause:  A configuration keyword that requires a value
must be followed by an equal sign and value in PROTOCOL.INI.

Action:  Correct the parameter and retry the operation.

---------  

PRO0012: An unrecoverable error occurred during initialization.

Cause:  An internal software error occurred during
OS/2 Protocol Manager initialization.

Action:  Contact your vendor sales representative.

---------  

PRO0013: The PROTOCOL.INI file in the IBMCOM directory is either damaged or 
has statements in it that are not valid.

Cause:  The PROTOCOL.INI file is not valid.

Action:  Correct the errors in the PROTOCOL.INI file and restart the
workstation.

---------  

PRO0021: A general failure occurred when the program tried to bind *** to ***.

Cause:  A general failure error code (0xFF) was returned
during the binding process.

Action: Reinstall the OS/2 Protocol Manager and try the operation
again.

---------  

PRO0022: An unspecified failure error occurred when the program tried to bind 
*** to ***.

Cause:  A unspecified failure error code was returned
during the binding process.

Action: Reinstall the OS/2 Protocol Manager and try the operation
again.

---------  

PRO0023: The protocol manager could not be found.

Cause:  The protocol manager could not be found for one
of the following reasons:

- The protocol manager failed to properly install.

- The NETBIND command was issued from the compatibility mode of OS/2.

Action:
Reinstall the protocol manager and retry the operation, or run the NETBIND
command from the OS/2 protect mode.

---------  

PRO0024: The NETBIND command has already been processed.

Cause:  The NETBIND command was requested after the network
was active.

Action:  No action is necessary; the command will be discarded.

---------  

PRO0025: An error occurred when the program tried to bind *** to ***.

Cause:  An error condition was returned from a request to
bind.  The possible causes are :

- The protocol/mac driver statements are not correctly specified in
the CONFIG.SYS file, or the protocol/mac drivers fail during the
system startup.

- The protocol/mac drivers have incorrect binding information in the
PROTOCOL.INI file.

Action:  Review PROTOCOL.INI to determine whether the module names
specified in the binding list match the module names enclosed in
brackets.  Check that the required protocol/mac driver statements are
included in the CONFIG.SYS file.


---------  

PRO0026: The media access control (MAC) driver is not registered or cannot be 
found.  The request to bind *** to *** cannot be completed.

Cause:  The MAC driver is not registered or cannot be found.  The request
to bind the protocol driver to the MAC was not successful.

Action:  Check for additional messages from the MAC driver indicating an 
error,
and check the bindings list in PROTOCOL.INI for an incorrect name.  
Correct the
error and try the operation again.

---------  

PRO0027: The adapter was not found when the program tried to bind *** to ***.

Cause: There was no adapter found in this machine to satisfy the
bind request.

Action:  Install an adapter in this machine or remove the device
driver statement.

---------  

PRO0028: A hardware failure occurred when the program tried to bind *** to 
***.

Cause:  An unexpected hardware failure occurred when the
protocol manager tried to bind the media access control (MAC)
driver.

Action:  Run the hardware diagnostics for the indicated adapter.
Contact your vendor sales representative.

---------  

PRO0029: A configuration parameter failure occurred when the program tried to 
bind *** to ***.

Cause:  Certain configuration parameters are unacceptable to either
the media access control (MAC) driver or the protocol manager.

Action:  Check for additional messages from the MAC driver and
correct the syntax problem in PROTOCOL.INI.

---------  

PRO0030: Multiple adapters are trying to use the same interrupt level.  The 
request to bind *** to *** cannot be completed.

Cause:  Multiple adapters have been set to use the same
interrupt level when 1 or more adapters do not share interrupts,
causing an unrecoverable conflict.

Action:  Run the hardware diagnostics for the adapters and
correct the interrupt conflict.

---------  

PRO0031: The version of the media access control (MAC) driver installed is not
supported by the protocol manager.  The request to bind *** to *** cannot be 
completed.

Cause:  A down-level or unsupported version of the MAC driver is
installed on this machine.

Action:  Install the supported version of the MAC driver.

---------  

PRO0032: A media access control (MAC) driver initialization failure has 
occurred.  The request to bind *** to *** cannot be completed.

Cause:  A parameter configured in PROTOCOL.INI is not valid.

Action:  Check for additional messages from the MAC driver
indicating an error and check the bindings list in PROTOCOL.INI
for an incorrect name.  Correct the error and try the
operation again.

---------  

PRO0033: The binding of the media access control (MAC) driver was not 
successful.

Cause:  The possible causes are:

- A protocol/MAC driver failed during system startup.

- A protocol/MAC driver has incorrect binding information.

- The protocol and/or MAC drivers are not configured, no binding has
taken place.

Action:  If the error was caused by a failed driver, correct
the problem and try the operation again.

---------  

XI00001: An error occurred while accessing the file "***".

The specified file may be in use by another process.
Alternatively, the operating system may have returned a
"no more files" or "path not found" error in response
to a MPTS request.
Cause:  The file is locked, there are no more files in the path, or
the path was not found.

Action:  Remove MPTS if it is already installed, and then reinstall MPTS.

---------  

XI00002: An error occurred in the MPTS exception handler.  Unable to process 
current error condition.

This message indicates an internal error in MPTS error handling.
Cause:  The exception number was not found in the exception stack.

Action:  Record the circumstances, and report the error to IBM.

---------  

XI00003: An error occurred in the MPTS exception handler.  Unable to process 
current error condition.

The MPTS exception handler stack has been changed.
Cause:  An internal error in MPTS has occurred.

Action:  Record the circumstances, and report the error to IBM.

---------  

XI00004: An error occurred in the OS/2 Help Facility.  MPTS is unable to 
provide help information at this time.

MPTS was unable to access its help message file.
Cause:  The file may have been locked or erased by another process.

Action:  Remove MPTS, and reinstall MPTS if help information is needed.

---------  

XI00005: An error occurred while reading the file "***".

MPTS encountered an error while trying to copy the specified file.
Cause:  Anything that results in a file not being successfully
copied can cause this error.

Action:  Record the circumstances and contact IBM.

---------  

XI00006: An error occurred during configuration.

An error occurred while configuring MPTS.
Cause:  The specific cause should have been given in a preceding error
message.

Action:  Correct the error condition and then try to configure MPTS
again.

---------  

XI00007: An error occurred while initializing the system for configuration.

An error occurred while initializing the system for MPTS
configuration.
Cause:  The specific cause should have been given by a preceding error
message.

Action:  Correct the error condition, and restart configuration.

---------  

XI00008: An OS/2 system error occurred.

This message has a number of possible causes.
Cause:  This message may be received in the following situations:
1>  MPTS was not able to insert text into a string.
2>  MPTS was not able to start a "CopyParams" thread.
3>  MPTS encountered a null current record in the exception handler.

Action:  Record the circumstances, and contact IBM.

---------  

XI00009: An error occurred while creating the directory "***".

This error message is displayed if a call to DosMkDir fails.
Cause:  MPTS was unable to create a subdirectory needed for
installation.

Action:  If the target subdirectory already exists, remove it, and then
try to install MPTS again.  Otherwise, contact IBM.

---------  

XI00010: A memory allocation error occurred.

A call to DosAllocSeg returned with an error.
Cause:  MPTS was unable to allocate memory.

Action:  Terminate any unnecessary applications and retry the operation.

---------  

XI00011: Source files for MPTS can not be found on entered path "***".

This message is displayed if the MPTS product files could not be found
on the entered path.
Cause:  You have entered an incorrect path for the MPTS files.

Action:  Enter the path where the MPTS files can be found and try
again.

---------  

XI00012: A Presentation Manager error occurred.  MPTS is unable to continue.

This message is displayed if any of the WinXxx function calls fails.
Cause:  A error occurred within the OS/2 Presentation Manager
interface.

Action:  Shut down the system, reboot, and perform the operation again.

---------  

XI00013: There is insufficient space on drive "***" for MPTS installation.

MPTS checks to ensure that sufficient free disk space is available
before continuing with installation.
Cause:  The target drive has insufficient space to install MPTS.

Action:  Delete any unnecessary files on the target drive, and try
to install MPTS again.

---------  

XI00014: An error occurred while attempting to update "***".

This error is returned if MPTS was unable to update the CONFIG.SYS file
specified (location of CONFIG.SYS is indicated).
Cause:  The CONFIG.SYS file may have been opened by another process
after MPTS was invoked.

Action:  If another process has opened the CONFIG.SYS file, terminate
that process.  Exit MPTS and try again.

---------  

XI00016: An error occurred while attempting to write to the file "***".

MPTS encountered an error while writing data to the specified file.
Cause:  The target drive may be full.

Action:  Delete any unnecessary files on the target drive, and retry
the operation.

---------  

XI00017: Unable to load the DLL "***".

MPTS was either unable to load the specified dynamic link library or to
determine the address of a procedure within the DLL.
Cause:  The MPTS DLL may be missing or damaged.

Action:  Check the IBMCOM\DLL directory for files with an extension of
DLL.  If fewer than five files are present, or if any appear to have
been altered, contact IBM.

---------  

XI00018: One or more source files is missing from the MPTS installation 
diskette.

MPTS was unable to find a file needed for installation.
Cause:  The MPTS diskette may have been damaged.

Action:  Contact IBM for replacement MPTS diskettes.

---------  

XI00019: Unable to preserve the current PROTOCOL.INI file.

This error indicates that MPTS was unable to copy the current
PROTOCOL.INI file to a temporary directory.
Cause:  Either the TMPCOM directory was removed after MPTS was invoked
or a copy of the PROTOCOL.INI file that cannot
be overwritten was created after invocation.

Action:  Remove MPTS and start the installation again.

---------  

XI00020: An error occurred unpacking the file "***".

This error indicates that the file unpacking program could not be
started.
Cause:  Either the unpacking program could not be executed or an
error occurred while unpacking files.

Action:  Record the circumstances, and contact IBM.

---------  

XI00021: An error occurred while attempting to process a locked file.

Cause:  A file that needed to be replaced was locked and could not be
replaced.

Action:  Record circumstances and contact IBM.

---------  

XI00022: The device "***" is not ready.

Cause:  When MPTS attempted to access a device, the operating system
returned a "device not ready" error code.

Action:  If the device is a diskette drive, ensure that the diskette is
fully inserted and that the drive door is closed.  If the device is a
network drive, ensure that drive is on-line.  If the problem,
persists, then
have the drive serviced.

---------  

XI00023: Unable to copy "***" to the path specified by the L1 parameter.

This error indicates that MPTS was unable to perform logging.
Cause:  MPTS was unable to copy the specified file to the place specified
by the L1 parameter.

Action:  Contact your LAN administrator.

---------  

XI00024: Unattended configuration was unable to create the PROTOCOL.INI file.

Cause:  This error can be returned if MPTS encounters a problem during
any of the following actions: creating a PROTOCOL.INI based on a response
file, updating target CONFIG.SYS based on contents of a PROTOCOL.INI
file, including VDD/PDD support, or checking for locked files.

Action:  Verify the response file used to create the PROTOCOL.INI file
is correct.  Ensure the product is properly installed.   If the
problem persists, contact IBM.

---------  

XI00025: Initialization of CID failed.

Cause:  MPTS CID functions were unable to initialize.
Possible reasons include invalid MPTS program invocation, invalid
response file or missing response file, or unable to locate imbedded
response files.

Action:  Ensure MPTS invocation is correct and response file referenced
is valid.  If problem persists,
record circumstances and contact IBM.

---------  

XI00026: MPTS must be installed before configuration or installing additional 
drivers can be performed.

Cause:  The response file has requested an action that cannot be
performed when MPTS is not installed.  MPTS is currently not
installed and the response file does not specify that installation
should be performed.  Note: if the response file being used is
attempting to install additional network drivers, verify that the
target parameter is specified and is the location where MPTS is
installed.

Action:  Install MPTS or change the response file.

---------  

XI00030: MPTS installation is being canceled by the user.

MPTS installation is being canceled.
Cause:  MPTS installation is being canceled by the user.

Action: MPTS will remove all MPTS files that it has started to install.

---------  

XI00032: No network information files were found at "***".

This message indicates that no NIFs were found at the specified path.
Cause:  The NIFs may have been deleted by another process.

Action:  Exit MPTS, and then install MPTS again.

---------  

XI00033: The network information file, "***", is not valid.  This network 
driver support will not be installed.

MPTS was unable to copy one or more of the files associated with this
NIF.
Cause:  Either the NIF is damaged or the associated files have been
deleted by another process.

Action:  Reinstall MPTS.

---------  

XI00034: The installation of the driver, "***", failed.

This message indicates that MPTS was unable to copy one or more files to
the temporary directory used for installation.
Cause:  MPTS was not able to preserve an existing driver file before
copying a new one.

Action:  Remove MPTS and reinstall.

---------  

XI00035: The driver *** could not be installed and the previous version could 
not be restored.

If the installation of a driver fails, and a previous copy of the driver
has been preserved, MPTS will try to restore the previous copy.
Cause:  The previously-saved copy of a driver file could not be restored
after installation of the new driver failed.

Action:  Remove MPTS and reinstall.

---------  

XI00036: The previous version of the driver "***" could not be restored.

MPTS attempts to preserve a copy of an existing driver before copying a
new version of the driver.
Cause:  MPTS could not restore the previous copy of a driver after the
attempt to preserve the existing copy failed.

Action:  Remove MPTS and reinstall.

---------  

XI00037: The file "***" was not found on the source for additional network 
drivers.

Cause:  The specified path does not exist.
This error indicates that the specified path for the network information
files was not valid.

Action:  If you are using MPTS in attended mode,
enter the correct path and try
again.  If you are using MPTS in an unattended environment,
ensure the value for the target parameter is correct and try again.

---------  

XI00039: Some files were locked by the operating system during the 
installation of additional network drivers.  For this reason, Install will no 
longer be selectable during this invocation of MPTS.

Files that are locked are currently in use by the operating system and
cannot be replaced.
Cause:  A file that MPTS is trying to replace is already in use.

Action:  The CURRENTLY BOOTED DRIVE must be rebooted after installation is 
complete to
allow the MPTS locked files device driver to replace the locked files. If this
is a multi-boot system, if the currently booted drive is not rebooted before
MPTS is used, system integrity cannot be guaranteed.

---------  

XI00040: Mult-Protocol Transport Services is currently running. Only one 
invocation can run at a time.

Cause:  MPTS is already running.

Action:  Switch to the session where MPTS is executing.

---------  

XI00041: The value provided for MPTS installation target parameter is not 
valid.

Cause:  The value supplied for the /T: parameter on the MPTS invocation
command line or within the MPTS response file is not valid.  The target
must reference a valid location that is not a removable media.

Action:  Ensure target provided for MPTS installation is valid
and references "fixed" media.

---------  

XI00042: Error reading response file.

Cause:  MPTS encountered an error while reading the response file
specified with the MPTS invocation by the /r: parameter.

Action:  Ensure the reference to the response file on the MPTS
invocation is valid and all imbed files are also accessible.  If
problem persists, contact IBM.

---------  

XI00043: Cannot read the file "***".

As part of its operation, MPTS must access many files.
Cause:  MPTS encountered an error while trying to read a file.

Action:  Record the circumstances and contact IBM.

---------  

XI00044: MPTS was unable to migrate the OS/2 1.3 Extended Edition 
configuration file ***.

Cause:  The specified OS/2 Extended Edition 1.3 configuration file
could not be successfully migrated to a PROTOCOL.INI file.

Action:  Retry the operation.

---------  

XI00045: Error processing PROT_SECTION in the response file; the SECTION_NAME 
keyword is missing.

The response file provided on the MPTS invocation contains a invalid
PROT_SECTION.
Cause:  A PROT_SECTION in the response file specified on MPTS invocation
is not valid.

Action:  Ensure the response file is correct and retry the operation.
If the problem persists, contact IBM.

---------  

XI00046: Internal software error during configuration.

MPTS checks the values in a response file against the parameters in the
appropriate NIF and adjusts them if necessary.
Cause:  MPTS detected an internal error while validating the contents
of a response file against the corresponding NIF.

Action:  Record circumstances and contact IBM to obtain a new copy of
MPTS.

---------  

XI00047: Section name "***" is invalid and cannot be used for configuration.

MPTS checks the values in a response file against the parameters in the
appropriate NIF and corrects them if necessary.
Cause:  The response file is not valid.

Action:  Record the circumstances and contact IBM.

---------  

XI00049: Error trying to write a file.

Cause:  An error occurred when MPTS tried to write to the CONFIG.SYS
file.
After all necessary changes have been made, MPTS attempts to write a
revised version of the CONFIG.SYS file.

Action:  Ensure the CONFIG.SYS file exists and is not in use by another
program.  Retry the operation.  If the problem persists, contact IBM.

---------  

XI00050: Unable to migrate the OS/2 Extended Edition 1.3 configuration file 
"***" because no LAN information was available.

Cause:  No LAN configuration is supported in the specified OS/2
Extended Edition 1.3 configuration file.

Action:  Ensure that the OS/2 Extended Edition 1.3 configuration file
specified in the response file is correct and contains necessary
configuration information.  Retry operation.  If problem persists,
contact your IBM Service representative.

---------  

XI00051: Unable to open the OS/2 Extended Edition 1.3 configuration file 
"***".

Cause:  MPTS was unable to open the specified OS/2 Extended Edition 1.3
configuration file.

Action:  Ensure the filename provided in the response file or the MPTS
window is correct
and references an existing OS/2 Extended Edition 1.3 configuration file.
Retry the operation.  If the problem persists, contact your IBM Service
representative.

---------  

XI00052: Unable to read the OS/2 Extended Edition 1.3 configuration file 
"***".

Cause:  MPTS encountered an error while trying to read the configuration
file specified.

Action:  Ensure the filename provided for migration is correct and
references an existing OS/2 Extended Edition 1.3 configuration file.

---------  

XI00053: MPTS was unable to migrate the OS/2 Extended Edition 1.3 
configuration file "***" because it is not a verified configuration file.

Cause:  The configuration file specified has not been verified.
OS/2 Extended Edition 1.3 configuration is verified by using the
Communications Manager verification function.  The specified
configuration file cannot be accepted because it has not been
verified by this function.

Action:  Execute the verify function from the Communications Manager
Advanced Configuration function.  Restart MPTS and retry the operation.

---------  

XI00054: The version of configuration file "***" is not supported for 
migration.

Cause:  The migration of the specified configuration is not supported
because it is not a supported version.  MPTS supports migration of OS/2
Extended Edition 1.3 configuration files only.

Action:  Ensure the configuration file supplied is the correct version
and retry the operation.

---------  

XI00055: MPTS was unable to migrate the SYSLEVEL.OS2 file from OS/2 Extended 
Edition to OS/2 Standard Edition 1.3.  The SYSLEVEL.OS2 file is damaged.

Cause:  MPTS was unable to modify the SYSLEVEL.OS2 file to reflect that
the current system is OS/2 1.3 Standard Edition.  The current system
level is not correct.

Action:  The current system may not support appropriate CSD updates
and MPTS reinstall requests will not be processed correctly.  Correct
the system by reinstalling OS/2 Extended Edition Version 1.3 and then
reinstalling MPTS.

---------  

XI00056: There is no value specified in the response file for the keyword *** 
and the associated Network Information File (.NIF) does not provide a default.

Cause:  The specified parameter is a required parameter, however, was
not provided in the response file and there is not a default value
included in the corresponding NIF file.

Action:  Ensure the parameter is included in the response file.

---------  

XI00057: Error processing a PROT_SECTION in the response file.  The NIF 
keyword is missing.

Cause:  Response file contained a PROT_SECTION keyword, however,
the required NIF keyword that identifies the corresponding NIF
file was missing.

Action:  Ensure the response file is correct and retry the operation.

---------  

XI00058: No Network Information Files (.NIF) were found.

Cause:  MPTS was unable to configure drivers because no Network
Information Files (.NIF)  could be located on the system.

Action:  Reinstall MPTS and retry the operation.

---------  

XI00059: MPTS attempted to update CONFIG.SYS and the current PROTOCOL.INI file
does not contain any configuration information.

Cause:   You have requested to complete the configuration however,
MPTS configuration has not been performed.

Action:  Select Configure on the MPTS main window to perform the
necessary configuration.
Continue if no configuration is necessary.

---------  

XI00060: Not all parameters were specified.

Cause:  The number of parameters supplied on a command line is below
that required by the program.

Action: See additional message for an example of the correct parameter
usage.

---------  

XI00061: Too many parameters were specified.

Cause:  The number of parameters supplied on a command line differs from
that required by the program.

Action: See additional message for an example of the correct parameter
usage.

---------  

XI00062: The specified source is not valid.

Cause:  The source parameter provided on the program invocation
is not valid.

Action: Ensure that the value for the source parameter is correct
and refers to a valid OS/2 location.

---------  

XI00063: The source must be a valid path specification.

Cause:  The source parameter provided on the program invocation line
does not refer to a valid OS/2 path.

Action: Ensure that the value for the source parameter is correct
and refers to a valid OS/2 location.

---------  

XI00064: The specified target is not valid.

Cause:  The target parameter provided on the program invocation line
does not refer to a valid OS/2 path.

Action: Ensure that the value for the target parameter is correct
and refers to a valid OS/2 location.

---------  

XI00065: The target must be a valid drive specification.

Cause:  The target parameter provided on the program invocation line
does not refer to a valid OS/2 drive.

Action: Ensure that the value for the target parameter is correct
and refers to a valid OS/2 drive.  Ensure that the media is properly
inserted in the specified drive.

---------  

XI00066: The target must be a valid path specification.

Cause:  The target parameter provided on the program invocation line
does not refer to a valid OS/2 path.

Action: Ensure that the value for the target parameter is correct
and refers to a valid OS/2 path.

---------  

XI00068: Unable to execute ***; the return code is ***.

Cause:  The identified program could not be executed.  The program
could not be located or is not installed correctly.

Action:  Obtain a new copy of the MPTS program diskettes and retry
the operation.  Ensure the target system supports the XCOPY command.
If the problem persists, contact your IBM Service representative.

---------  

XI00069: *** returned an error; the exit code is ***.

Cause:  The identified program encountered a failure during execution.
The exit code provided is the return code from the program with
the exception.

Action:  See related messages for more information.
Refer to specific program documentation for more information on the
exit code specified.

---------  

XI00070: *** did not complete successfully.

Cause:  The specified program did not complete successfully.

Action: Refer to associated messages for more information.

---------  

XI00071: Missing dynamic link library module or entry point; object name is 
***.

Cause:  The specified file is missing or could not be located.
The MPTS program diskettes may be damaged; it does not contain
the necessary files.

Action: Create a new copy of the MPTS program diskettes and retry the
operation.  If the problem persists, contact your IBM Service
representative.

---------  

XI00072: Command line invocation errors.  Either not all required parameters 
were specified or unsupported parameters/values were supplied.

Cause:  Invalid parameters, arguments, or both were supplied.
ThinLAPs obtains a number of required and optional
parameters and values from the command line invocation.

Action:  Supply valid parameters and arguments.  See associated
messages for more information.

---------  

XI00073: Unable to copy ***; the return code is ***.

Cause:  An error occurred while trying to copy the specified file.

Action: Refer to the appropriate OS/2 documentation for more information
using the specified return code.  Retry the operation.  If the problem
persists, contact your IBM Service representative.

---------  

XI00074: Unable to obtain information for ***; the return code is ***.

Cause:  The specified return code was returned from the operating system
in an attempt to obtain file system information on the specified file.

Action: Retry the operation.  If the problem persists, contact your
IBM Service representative.

---------  

XI00075: Unable to open ***; the return code is ***.

Cause:  The specified return code was returned from the operating
system attempting to open the specified file.

Action: Ensure that the file is not marked read-only.  Ensure that
no other program is using the file.  Retry the operation.  If the
problem persists, contact your IBM Service representative.

---------  

XI00076: Unable to seek within ***; the return code is ***.

Cause:  The specified return code was returned in response to a system
request to access the specified file.

Action: Ensure that no other process is using the file.
Retry the operation.  Contact your IBM Service representative if
the problem persists.

---------  

XI00077: Unable to read from ***; the return code is ***.

Cause:  The OS/2 program returned an error in response to a DosRead
request.

Action: Run the CHKDSK program against the affected drive.  This error
can be caused by "soft" media defects.

---------  

XI00078: Unable to write to ***; the return code is ***.

Cause:  OS/2 returned the specified error attempting to write the
specified file.

Action: Retry the operation.  If the problem persists, contact your
IBM Service representative.

---------  

XI00079: Unable to close ***; the return code is ***.

Cause:  An attempt to close the specified file resulted in a program
error.  The return code specified reflects the OS/2 error.

Action: Retry the operation.  If the problem persists, contact
your IBM Service representative.

---------  

XI00080: Unable to delete ***; the return code is ***.

Cause:  Attempt to remove the specified file was denied by the
operating system with the specified return code.

Action: Ensure that no other process is using the file.  Ensure that
the file is not marked read-only.  Retry the operation.  If the problem
persists, contact IBM.

---------  

XI00081: Error reading from ***; not all bytes were read.

Cause:  Fewer than the requested number of bytes were read from a file.

Action: Ensure that no other process is trying to use the file.
Retry the operation.  If the problem persists, contact IBM.

---------  

XI00082: Error writing to ***; not all bytes were written.

Cause:  Fewer than the specified number of bytes were written to a file.
The most likely cause is a disk that became full.

Action: Delete unnecessary files on the affected disk to free space.
Retry the operation.  If the problem persists, contact IBM.

---------  

XI00083: Unable to allocate memory; the return code is ***.

Cause:  Attempt to allocate memory necessary for processing failed
with the specified OS/2 program return code.

Action: Stop any  unnecessary executing programs and retry the operation.
If unsuccessful, perform a system shutdown and retry the operation.

---------  

XI00084: Error while parsing ***.

Cause:  An error occurred while parsing the identified file.

Action: Ensure that the file specified is a valid Network Information
File (.NIF).  Retry the operation.  If the problem persists, contact IBM.

---------  

XI00085: Usage: [<path>]LAPSDISK <source> <target>

Cause:  Incorrect LAPSDISK program invocation.

Action: See associated messages.

---------  

XI00086: Usage: [<path>]LAPSRSP <source> <target> {/m: /n: /b: /v: /t: /i: /c:
/u:}

Cause:  Incorrect LAPSRSP program invocation.

Action: LAPSRSP requires the specified syntax.  See associated messages
to correct the problem.

---------  

XI00087: LAPSRSP requires a colon to separate the keyword and the value.

Cause:  The LAPSRSP program expects a colon between a keyword and the
value for a command-line switch.

Action: Ensure the LAPSRSP command line contains a colon between all the
keywords and their values.     .

---------  

XI00088: A LAPSRSP switch is specified but the value is not provided.

Cause:  A valid switch was specified on the LAPSRSP command line, but
a value was not supplied.

Action: Ensure all the LAPSRSP switches contain valid values and retry
the operation.

---------  

XI00089: An invalid switch was specified on the LAPSRSP command line.

Cause: The switch provided on the LAPSRSP program invocation was invalid.

Action: Verify the LAPSRSP command line and retry the operation.

---------  

XI00090: Invalid installation value.

Cause:  The value supplied for the installation type was not valid.
The installation value is supplied in the following format:
/i: <installation level>
(where <installation level> is either PRODUCT or ADDITIONAL).

Action: Ensure that a valid installation level is
specified and retry the operation.

---------  

XI00091: Invalid target drive specification.

Cause:  The value supplied for the "/t:" parameter was not valid.
The value supplied in the following format: /t:<d:> where <d> is a
valid OS/2 drive letter.

Action:  Ensure the value supplied for the "/t:" option for LAPSRSP
is valid and retry the operation (the drive letter must be followed by
a colon).

---------  

XI00092: Invalid upgrade level value.

Cause:  A value supplied from the "/u:" option was not valid.  The
value is supplied in the following format:  /u:<value>  where value is
OLD, SAME or NEW.

Action: Ensure the value supplied for the "/u:" parameter is valid
and retry the operation.

---------  

XI00094: Error processing PROT_NETBIOS in the response file; the SECTION_NAME 
keyword is missing.

Cause:  The section name keyword NETBIOS was missing from the response file.

Action:  Add the section name keyword NETBIOS to the PROT_NETBIOS section and
restart the MPTS CID installation process.

---------  

XI00095: The Network Information File (.NIF) filename must be valid and 
include the filename extension.

Cause:  The NIF file name provided on program invocation is not valid.

Action:  Ensure the network information filename specified is valid
(including the filename extension).  Retry the operation.

---------  

XI00096: Unable to locate any Network Information Files (.NIF) on target 
drive.

Cause:  THINLAPS was unable to locate any NIF files on the target drive.

Action: Retry the operation.  If the problem persists, contact IBM.

---------  

XI00097: Unexpected error while searching for Network Information Files 
(.NIF).

Cause:  THINLAPS was unable to find the necessary .NIF files on the
target drive.

Action: Obtain a new copy of the MPTS diskettes and retry the operation.
If the problem persists, contact IBM.

---------  

XI00098: Warning: Creating new CONFIG.SYS on the target drive.

Cause:  THINLAPS expects a CONFIG.SYS file on the target drive that it
will append the necessary device statements for the LAN Transport.
The CONFIG.SYS file on the target drive was not found and one was created
that contains the necessary device statements for the requested
transport files to load.

Action: Append the CONFIG.SYS file created by THINLAPS to the
CONFIG.SYS file to be used to IPL the machine.

---------  

XI00099: An error occurred while attempting to add LAPSDEL invocation to 
MAINTDEL.CMD.

Cause:  An invocation string for the LAPSDEL utility program could not
be added to the MAINTDEL.CMD file.
MPTS builds a MAINTDEL.CMD file as part of its processing for C/I/D.

Action:  Retry the operation.  If the problem persists, contact IBM.

---------  

XI00102: SHPIINST.DLL could not be successfully loaded.

Cause:  MPTS was not able to load the SHPIINST.DLL file.
MPTS must be able to load the file SHPIINST.DLL when performing an
installation on an OS/2 maintenance system because Presentation Manager
support is not available.

Action:  Ensure that the SEMAINT program was successful.  Retry the
operation.  If the problem persists, contact IBM.

---------  

XI00103: The MPTS installation was not successful.

Cause:  An error occurred while processing the file IBMLVL.INI.
This file is used to indicate to MPTS if the LAN transports are already
installed and what the version of the installed product is.  If this file
is missing or is not correct, future reinstalls or updates will not
be successful.  This error may also occur if the OS/2 services to
update this file are currently installed.

Action:  Remove the LAN transports and retry the operation.  If MPTS does
not support the Remove function, MPTS must be manually removed and then
reinstalled.

---------  

XI00104: MPTS did not install due to UPGRADE_LEVEL specified in the response 
file.

Cause:  MPTS has detected the presence of an already-installed version
of MPTS that should not be replaced, based on the value of the
UPGRADE_LEVEL keyword in the response file.

Action:  No action is necessary if this is the desired behavior.
Otherwise, change the UPGRADE_LEVEL parameter in the response file.

---------  

XI00106: An error occurred trying to create the file "***".

Cause:  MPTS could not create a backup for the CONFIG.SYS file.
MPTS attempts to make a backup of the CONFIG.SYS file before making
any changes to the original file.

Action:  Ensure the file specified does not already exist.  Retry
the operation.  If the problem persists, contact IBM.

---------  

XI00107: Error while attempting to copy the file "***".

Cause:  MPTS encountered an error while trying to copy a file.
MPTS must copy a number of files as part of its operations.
MPTS may fail to copy a file because the source file doesn't exist
or because the replacement file is currently in use by the system
and cannot be replaced.

Action:  Ensure the source file exists.  If the source file is part
of the MPTS "packed" diskette image, obtain a new copy of the MPTS
diskettes and retry the operation.  If the target file already exists
on the system, verify that the operation is a reinstall and the
file IBMLVL.INI exists in the root of the drive where MPTS is
already installed.  If the file does not exist, then MPTS must be
manually removed from the system and then reinstalled.

---------  

XI00108: MPTS was unable to read or update the IBMLVL.INI file correctly.  
Since the install status of MPTS is undefined, MPTS will be removed from the 
system.

Cause:  MPTS encountered an error while accessing the IBMLVL.INI file.
MPTS needs to read and update the IBMLVL.INI file (found in the root
directory of the boot drive) as part of its operations.

Action:  If the IBMLVL.INI file exists, erase the file and restart
MPTS.  If the problem persists, contact IBM.

---------  

XI00109: CONFIG.SYS could not be successfully updated with the configuration 
information provided by MPTS.  Your system may not be operational when 
restarted.

Cause:  An error occurred when MPTS tried to update the CONFIG.SYS file.
MPTS may need to update the CONFIG.SYS file after configuration has been
completed.

Action:  Retry the operation.  If the problem persists, restore the
backup configuration file CONFIG.LAP to CONFIG.SYS and retry the
operation.  If the problem still persists, contact your IBM Service
representative.

---------  

XI00111: The file *** was not found in the ZIP file of the MPTS product image.

Cause: THINLAPS attempted to extract one or more files from a
ZIP file of the MPTS product image.  The file was not found in the ZIP file.

Action: No Action is required.  THINLAPS will attempt to copy the file
directly from the appropriate subdirectory.  If the copy fails, another
message will be displayed; refer to the help for that message.

---------  

XI00114: THINLAPS was unable to copy the file ***; the return code is ***.

Cause:  An error occurred while THINLAPS attempted to copy the
specified file from the appropriate subdirectory. Make sure that the MAC NIF
file and it's support files are located in the proper subdirectories.  The
MAC NIF file and it's support files (except .MSG files) should be located
in the \IBMCOM\MACS subdirectory off the target path of the LAPSDISK utility.
Message files (.MSG) should be located in the \IBMCOM subdirectory off the
target path of the LAPSDISK utility.

---------  

XI00115: Error while attempting MPTS installation due to the UPGRADE_LEVEL. 
The installed version is the same as the version being installed. To reinstall
the same version an UPGRADE_LEVEL of "NEW" or "SAME" must be specified.

Cause:  MPTS detected an existing version of MPTS that is the same
or newer than the version being installed.  Since the UPGRADE_LEVEL parameter
is set to OLD, this version will not be replaced.

Action:  No action is necessary if this is the desired behavior.
Otherwise, change the UPGRADE_LEVEL parameter in the response file.
If no UPGRADE_LEVEL parameter is specified, the default is OLD.

---------  
SYS0317: The system cannot find message  0118
in message file XI0H.MSG.
---------  

XI00132: Incorrect IP ADDRESS format "***" was specified.

Cause:  The format for IP address is nnn.nnn.nnn.nnn
where nnn cannot be greater than 255.

Action:  Enter a correct IP address format and retry the operation again.

---------  

XI00133: Invalid *** parameter specified.

Cause:  A THINLAPS parameter was incorrectly entered.

Action:  Check the specified parameter and correct the format of the 
parameter.
Retry the operation again.

---------  

XI00134: SETENVAR usage: /V:EnvVariableName /P:"PromptString"

Cause: The SETENVAR program has a set of parameters that are required.
They are Environment name and Prompt String.  The set and be added multiple 
times.

Action: Specify the correct set of parameters for SETENVAR program and
retry the operation again.

---------  

XI00135: EnvVariableName  Name of environment variable to be created
PromptString     Prompt string layout

Cause: The SETENVAR program has a set of parameters that are required.
They are Environment name and Prompt String.  The set and be added multiple 
times.

Action: Specify the correct set of parameters for SETENVAR program and
retry the operation again.

---------  

XI00136: SETENVAR: Unknown keyword *** entered.

Cause: An unknown parameter was entered for the SETENVAR program.

Action: Correct the parameter and retry the operation again.

---------  

XI00138: Cannot specify both the IP and PIP parameters.

XI00138: Cause: The IP parameter and the PIP parameter cannot be specified at 
the
same time.

Action: Remove one of the parameters (IP or PIP) and retry the operation 
again.

---------  

XI00139: Cannot specify both the HOST and PHOST parameters.

XI00139: Cause: The HOST parameter and the PHOST parameter cannot be specified
at the
same time.

Action: Remove one of the parameters (HOST or PHOST) and retry the operation 
again.

---------  

XI00141: MPTS was unable to create the PROTOCOL.INI file for NDIS support.

Cause:  MPTS, running in attended mode with the /N parameter
specified on the command line encountered an error while
attempting to create the PROTOCOL.INI file for NDIS support.

Action:  Retry the operation.  If the problem persists, contact IBM.

---------  

XI00142: A CONFIG.SYS file cannot be located at the value specified for the 
/TU: parameter.

Cause:  The /TU parameter on the MPTS program invocation identifies the
location (drive and path) where the CONFIG.SYS file is located that will
be updated with MPTS configuration information.

Action:  Re-invoke MPTS with a valid config.sys file.

---------  

XI00143: NetBIOS configuration values exceed acceptable configuration 
requirements.

Cause:  Unable to tune the configuration values that were migrated.
NetBIOS parameters were migrated however the memory requirements
for this configuration exceeds the value supported for the NetBIOS
protocol stack.
NetBIOS memory usage limitations is computed using the current
system processor as a limitation.  If you are using a 286 based
machine to prepare a protocol.ini for a 386/486 based machine,
memory usage limitations will be greater.

Action:  Reconfigure the resultant PROTOCOL.INI file to  lower the
necessary NetBIOS capacity parameters in order to ensure the NetBIOS
protocol stack will successfully load.  Refer to the LAPS
product documentation for NetBIOS parameter tuning guidelines.

---------  

XI00144: LANDD configuration values exceed acceptable configuration 
requirements.

Cause:  Unable to tune the configuration values that were migrated.
IEEE 802.2 parameters were migrated however the memory requirements
for this configuration exceeds the value supported for the IEEE
802.2 protocol stack. IEEE 802.2
memory usage limitations is computed using the current
system processor as a limitation.  If you are using a 286 based
machine to prepare a PROTOCOL.INI file  for a 386/486 based machine,
memory usage limitations will be greater.

Action:  Reconfigure the resultant protocol.ini file to  lower the
necessary IEEE 802.2 capacity parameters in order to ensure the
protocol stack will successfully load.  Refer to the LAPS
product documentation for specific parameter tuning guidelines.

---------  
SYS0317: The system cannot find message  0147
in message file XI0H.MSG.
---------  
SYS0317: The system cannot find message  0148
in message file XI0H.MSG.
---------  

XI00150: The "/P:" parameter is not valid or was not followed by a valid 
filespec.

Cause:  The fourth parameter supplied on the ThinLAPS command line was
not in the format: "/P:<PROTOCOL.INI filespec>".
The "/P:" parameter is used to specify the name of a user-supplied
PROTOCOL.INI file that should be used instead of the one generated by
ThinLAPS.

Action: Ensure that the parameter is in the correct format and that it
specifies the name of a valid PROTOCOL.INI file.  Retry the operation.

---------  

XI00151: The syntax for this parameter is "/P:<PROTOCOL.INI filespec>".

Cause:  The fourth parameter supplied on the ThinLAPS command line was
not in the format: "/P:<PROTOCOL.INI filespec>".
The /P: parameter is used to specify the name of a user-supplied
PROTOCOL.INI file that should be used instead of one generated by
ThinLAPS.

Action: Ensure that the parameter is in the correct format and that it
specifies the name of a valid PROTOCOL.INI file.  Retry the operation.

---------  

XI00165:   An error was encountered while trying to unzip file *** from ***.
  The return code form spawnl function was ***.

Cause:  During a CID install of MPTS the installation program attempted
to unzip the specified NIF file from the indicated source zip file when an 
error
occurred.

Action:  Check that the source IBMC\MACS and IBMCOM\PROTOCOL directories have 
the
the MACS.ZIP and PROTOCOL.ZIP files respectively.

Action:  Verify that PKUNZIP2.EXE is present in the source root directory.

Action:  Contact your administrator.

---------  

XI00166:   The file *** was not found in either the ***\IBMCOM\MACS OR 
***\IBMCOM\PROTOCOL
  directories on the source drive. The return code from 
the spawnl function is ***.

Cause:  During a CID install of MPTS the installation program attempted
to unzip the specified NIF file from the indicated  source zip files and the 
file
was not found. The NIF file was identified from the response file

Action:  Remove the NIF file statement from the response file.

---------  

XI00167:   The *** token was not found while searching the *** file for the 
devicd driver names.

Cause:  During a CID install of MPTS, the installation program attempted
to determine the list of driver names associate with indicated NIF file. The
indicated TOKEN was not located where it was expected to be.

Action:  Verify that the syntax of the indicated NIF file is correct, or 
contact
your administrator.

---------  

XI00168:   The string "***" was not found while searching the *** file for the
device driver names.

Cause:  During a CID install of MPTS, the installation program attempted
to determine the list of driver names associate with indicated NIF file. The
indicated STRING was not located where it was expected to be.

Action:  Verify that the syntax of the indicated NIF file is correct, or 
contact
your administrator.

---------  

XI00169:   The section "***" was not found while searching the *** file for 
the device driver names.

Cause:  During a CID install of MPTS, the installation program attempted
to determine the list of driver names associate with indicated NIF file. The
indicated SECTION was not located where it was expected to be.

Action:  Verify that the syntax of the indicated NIF file is correct, or 
contact
your administrator.

---------  

XI00170:   The syntax error was encountered while searching the "***" file for
the *** token.
  This error was encountered while searching for device driver names.

Cause:  During a CID install of MPTS, the installation program attempted
to determine the list of driver names associate with indicated NIF file. The
indicated TOKEN was not located where it was expected to be.

Action:  Verify that the syntax of the indicated NIF file is correct, or 
contact
your administrator.

---------  

XI00171:   The file *** was not found in *** file. The return code from the 
spawnl function is ***.

Cause:  During a CID install of MPTS the installation program attempted
to unzip the specified driver file from the two source zip files and the file
not found. The driver file was identified from the NIF files specified in the
response file.

Action:  Remove the NIF file statement containing the driver file name 
indicated
from the response file.

---------  

XI00172: An error occurred while attempting to parse the response file entry 
for the RFCNAMES_SECT "***".

Cause:  During a CID install of MPTS the installation program attempted
to pasre a line in the RFCNAMES_SECT and encountered a problem.

Action:  Check all of the RFCNAMES_SECT entries in the response file to see if
they are formatted properly (example: NAME = "Marc"      marc.austin.ibm).

---------  

XI00174: Error processing MPTS_SECT in the response file; the SECTION_NAME 
keyword is missing.

Cause:  The SECTION_NAME keyword is missing from MPTS_SECT section in
in the response file.

Action:  Ensure the response file is correct and retry the operation.
If the problem persists, contact IBM.

---------  

XI00175: The keyword parameter *** specified in the MPTS_SECT of the response 
file is invalid.

Cause:  The keyword specified in the MPTS_SECT section of the response
file is invalid.

Action:  Ensure the response file is correct.
If the problem persists, contact IBM.

---------  

XI00176: The section name *** specified in the MPTS_SECT of the response file 
was not found in the
MPTCONFG.INI file.

Cause:  The section name specified in the MPTS_SECT section of the response
file was not found in the MPTCONFG.INI file. The MPTCONFG.INI file may not 
have been
configured for TCP/IP support.

Action:  Ensure the response file is correct, and that the MPTCONFG.INI is 
configured
properly.
If the problem persists, contact IBM.

---------  

XI00178:   While adding the new section "***" to the MPTCONFG.INI file an 
invalid number of parameters (***) was specified in the MPTS_SECT section of 
the response file.

XI00178: Cause:  While mpts was adding a new section to the MPTCONFIG.INI 
file, an
incorrect number of parameters used for that section was specified.

Action:  Ensure the response file is correct, and that the MPTCONFG.INI is 
configured
properly.

---------  

XI00190: Usage: MAKEDISK <source> <target> {/d:#}

Cause:  Invalid parameters, arguments, or both were supplied.
MAKEDISK obtains a number of required and optional
parameters and values from the command line invocation.

Action:  Supply valid parameters and arguments.  See associated
messages for more information.

---------  

XI00191:   The SSL Protocol installation program *** failed with a return code
***.

XI00191: Cause:  Check the MPTS Configuration Guide to check the SSL 
Installation
return codes.

Action:  Check the return code for more information.

---------  

XI10001: Command line invocation errors.  Either not all required parameters 
were specified or unsupported parameters/values were supplied.

Cause:  Invalid parameters, arguments, or both were supplied.
ThinIFS and ThinSRV both obtain a number of required and optional
parameters and values from the command line invocation.

Action:  Supply valid parameters and arguments.  See associated
messages for more information.

---------  

XI10002: CONFIG.SYS file cannot be located as prescribed by the "/TU:" 
parameter.

Cause:  ThinSRV could not locate a CONFIG.SYS file in the path specified
by the "/TU:" parameter.
ThinSRV will update the CONFIG.SYS file located by the argument
supplied for the "/TU:" parameter.  The "/TU:" parameter is optional
and if it is omitted, then the value used to locate the CONFIG.SYS
file will be the value supplied for the "/T:" parameter.

Action:  Change the argument of the "/TU:" parameter to reflect the
location of the CONFIG.SYS file to be changed.

---------  

XI10003: Unsupported value supplied for the "/D:" parameter on ThinIFS program
invocation.

Cause:  The value for the "/D:" parameter is not a supported drive
letter.
The /D: parameter specifies the drive letter to be
used for the SRVATTCH program.

Action:  Specify a valid drive letter as argument for "/D:".  Supported
value for the /D: parameter is a single alphabetic character.  An
optional colon is supported, i.e. Q or Q: are supported input values.

---------  

XI10004: Value supplied for the "/R:" parameter is invalid.

ThinSRV expects the fully qualified name of a response file to follow
the "/R:" parameter.  This parameter is required.

Cause:  The argument for the "/R:" parameter is invalid.

Action:  Supply the fully qualified name of a response file as
the argument to the "/R:" parameter.  Verify the command line invocation
for ThinIFS contains a "/R:" parameter and the argument supplied
refers to a valid ThinSRV response file.

---------  

XI10005: Value supplied for the "/U:" parameter is invalid.

Cause:
The argument supplied for the "/U:" parameter is not valid.  The "/U:"
parameter is an optional parameter.  When specified on the ThinSRV
invocation, it identifies the source location of a SRVIFS authorization
file.

Action:  Verify ThinSRV invocation. Ensure the argument supplied for
the "/U:" parameter
correctly references the source location of a SRVIFS authorization
file.

---------  

XI10006: Unsupported value supplied for the "/SRV:" parameter on ThinIFS 
invocation.

Cause:  An invalid argument was specified for the "/SRV:" parameter.
The "/SRV:" parameter is used to specify the name of the server or a
server alias that this client will connect to.  The parameter is
required.

Action:  Specify a valid server name as the argument for "/SRV:".
Value arguments are 1-15 Netbios name of the server, single asterisk
followed by a P (*P), or a server alias name in the form of
\\servername\alias where servername is the 1-15 Netbios name of the server
and alias is an advertised alias on that server.

---------  

XI10007: Unsupported value supplied for the "/REQ:" parameter on ThinIFS 
invocation.

Cause:  An invalid argument was specified for the "/REQ:" parameter.
The "/REQ:" parameter is used to specify the name of the requester to
ThinIFS.  This is a required parameter.  Possible values for the
argument are alphanumeric strings of 1-15 characters, a single asterisk,
a single asterisk followed by the letter P (*P), or a single asterisk
followed by an I (*I).

Action:  Specify a valid requester name or other argument for the
"/REQ:" parameter.

---------  

XI10008: Unsupported value supplied for the "/NS:" parameter on ThinIFS 
invocation.

Cause:  An invalid argument was supplied for the "/NS:" parameter.
ThinIFS allows the number of NETBIOS sessions to be specified via the
"/NS:" command-line parameter.

Action:  Specify a single digit from 2 to 9 for the number of
NETBIOS sessions to be supported.

---------  

XI10009: Unsupported value supplied for the "/W" parameter on ThinIFS 
invocation.

Cause:  The "/W" parameter was specified with an argument.
The "/W" parameter is used to indicate that an extended time-out is
necessary for the requester.  This parameter is optional.

Action:  Specify the "/W" parameter without an argument.
A colon following the 'W' is accepted but is not necessary.

---------  

XI10010: Unsupported value supplied for the /A: parameter.

Cause:  An invalid argument was specified for the "/A:" parameter.
The "/A:" parameter may be used on the ThinIFS command line to specify
the adapter number.  Supported values are 0 and 1.

Action:  Specify either 0 or 1 as the argument for the "/A:"
parameter on the THINIFS invocation line.

---------  

XI10011: Error attempting to create the target path specified by the /T: 
parameter.

Cause:  The target path specified by the "/T:" parameter did not exist
and the directory (if any) could not be created.
ThinIFS and ThinSRV use the "/T:" parameter to specify a target path for
the installation.

Action:  Verify the value set for the "/T:" parameter.
Supply a valid target path (directories will be created if
necessary) as the argument for "/T:".

---------  

XI10012: NetBIOS not configured in CONFIG.SYS.

Cause:  Either a "device = NETBDD.SYS" statement (for an OS/2
Extended Edition 1.3
system) or the combination of "device = NETBEUI.OS2" and "device =
NETBIOS.OS2" statements (for LAN Transport) was not found in the
CONFIG.SYS.
ThinIFS and ThinSRV both require that NetBIOS be configured in the
CONFIG.SYS file.

Action:  Perform the necessary steps to add NETBIOS configuration to the
CONFIG.SYS file.

---------  

XI10013: Unable to read file attributes of the CONFIG.SYS file.

Cause:  An error occurred while attempting to get the attributes for
the CONFIG.SYS file.
ThinIFS and ThinSRV need to be able to read and write the contents of the
target CONFIG.SYS file.  If the file is currently marked "read-only",
then the "read-only" attribute is temporarily reset until processing
of the file has been completed.

Action:  Determine if any other programs are using the target CONFIG.SYS
file.  Perform a system shutdown if necessary and retry the operation
after system restart.

---------  

XI10014: Unable to set or restore file attributes of the CONFIG.SYS file.

Cause:  An error occurred while attempting to change the attributes of
the CONFIG.SYS file.
If the target CONFIG.SYS file is marked "read-only", this program
will temporarily reset that attribute to allow the file to be altered.
The "read-only" attribute will be restored when processing completes.

Action:  Ensure the CONFIG.SYS file is valid and is not in use by
another program.  If necessary, perform a system shutdown and retry
the operation after system restart.

---------  

XI10015: Drive letter *** is already being used as a drive specifier on a 
SRVATTCH statement in the CONFIG.SYS file.

Cause:  The specified drive letter is already being used by SRVATTCH.
Using a drive letter in multiple SRVATTCH statements will not result
in a success network connections.  Unique drive letters must be used
for each SRVATTCH statement.

Action:  Specify a different drive letter with the /D: parameter on
THINIFS invocation.

---------  

XI10016: Error attempting to copy the file "***" to target.

Cause:   An error occurred while attempting to copy the specified file.

Action:  Ensure the file specified exists and can be copied.
Ensure that there is sufficient disk space available for the file to
be copied.
Check if the file specified already exists on the target.  If it does,
then verify the file is not currently "in use" (can be replaced).
If the file cannot be replaced, perform a system shutdown to release
the file and retry the operation after system restart.

---------  

XI10017: Unsupported value for "ADAPTER =" statement on line *** in response 
file.

Cause:  The "ADAPTER =" statement was supplied with an argument
other than 0, 1, or BOTH.
The "ADAPTER =" statement is which adapter will be used to support
the SERVER.  Supported values are 0, 1 or BOTH.
used to designate either or both of up to two possible adapters.

Action:  Modify the argument for "ADAPTER =" in the response file to an
acceptable value.

---------  

XI10018: Unable to process response file.

Cause:  The response file specified on THINSRV invocation could not be
opened.

Action:  Ensure that the response file exists and is not in use by
another process.

---------  

XI10019: Syntax error on line *** in response file.

Cause:  The response file contained an invalid line.  Each line in the
response file must be in the format "<keyword> = <value>".

Action:  Correct the statement in the response file.

---------  

XI10020: Unsupported value for "MAXFILES =" statement on line *** in response 
file.

Cause:  An argument outside the range 100 - 9999, inclusive, was supplied
for the MAXFILES keyword in the response file.

Action:  Change the MAXFILES argument to a supported value.
The value for the MAXFILES keyword must be between 100 and 9999.

---------  

XI10021: Invalid value for "PATH =" statement or path on "ALIAS =" statement 
on line *** in response file.

Cause:  An invalid path was specified as the argument for either the
PATH keyword or the ALIAS keyword in the response.  The specified path
must exist to be considered valid.

Action:  Change the argument to a valid path specification.

---------  

XI10022: Invalid value for "NAME =" statement on line *** in response file.

Cause:  An invalid argument was specified for the NAME keyword.

Action:  Specify a valid NetBIOS name of 1-15 characters for the NAME
parameter in the response file.

---------  

XI10023: Invalid value for "GROUPNAME =" statement on line *** in response 
file.

Cause:  An invalid argument was specified for the GROUPNAME keyword.

Action:  Specify either Yes or No as the value for the GROUPNAME
parameter in the response file.

---------  

XI10024: Unable to open AuthList file "***" for validation of users.

Cause:  The AuthList file specified as the argument of the AUTHLIST
keyword in the response file could not be opened.

Action:  Ensure the response file or the command line invocation
identifies the correct source authorization file.  If the /U: parameter
was not specified on the ThinSRV invocation, ensure the file that the
AUTHLIST parameter refers to in the response file is valid.

---------  

XI10025: Invalid value for "PERMITWRITE =" statement on line *** in response 
file.

Cause:  An invalid argument was specified for the PERMITWRITE keyword in
the response file.

Action:  Specify either Yes or No as the value for the PERMITWRITE
statement in the response file.

---------  

XI10026: Invalid value for "CLIENTWORKERS =" statement on line *** in response
file.

Cause:  An invalid argument was specified for the CLIENTWORKERS keyword
in the response file.

Action:  Specify a number between 2 and 12, inclusive, as the value
for CLIENTWORKERS in the response file.

---------  

XI10027: Invalid value in "ALIAS =" statement on line *** in response file.

Cause:  An invalid argument was supplied for one or more of the values
for the ALIAS keyword.

Action:  Specify either ALIAS statement in the response file in the
following syntax:  ALIAS = READTYPE, ACCESSTYPE, ALIASNAME, ALIASPATH.
READTYPE will be either ReadOnly or ReadWrite,  ACCESSTYPE will be
set to either Single or PerClient, ALIASNAME is 1-8 character name
identifying the alias and ALIASPATH must be a currently valid drive:\
pathname.

---------  

XI10028: Response file does not contain the required "PATH =" statement.

Cause:  The response file does not contain a PATH keyword.

Action:  Add a valid PATH = statement to the response file.

---------  

XI10029: Invalid entry in the AuthList file on line ***.

Cause:  An incorrect entry was supplied in the AuthList file.

Action:  Correct the entry.  A valid AuthList entry consists
of a name (between 1 and 15 characters, inclusive), which may be
followed by a period (.) and a string of 12 hexadecimal characters.

---------  

XI10030: Cannot open log file as specified by the "/L1:" parameter on the 
invocation command line.

Cause:  Either the filespec supplied is invalid or the file could not be
opened.

Action:  Verify that the drive specified in the value provided with
the "/L1:" parameter is valid.  If the filespec does not exist, verify
that one can be created.
Verify that the log file is not already in use by another process.  If
it is that, perform the necessary actions to allow the log file to
be released or select another log file name.
Verify that there is sufficient disk space on the target specified.

---------  

XI10031: Invalid value for "MAXCLIENTS =" parameter on line *** in response 
file.

Cause:  The argument for the MAXCLIENTS keyword in the response file is
invalid.

Action:  Change the value specified for the MAXCLIENTS in the response
file so that it is between 1 and 99.

---------  

XI10032: SERVER file SERVICE.EXE already exists on the target.  The file will 
not be overlaid.

Cause:  SRVIFS server file SERVICE.EXE already existed and was not
re-installed.

Action:  Erase SERVICE.EXE and rerun THINSRV if necessary.

---------  

XI10033: Error attempting to create the path "***".

Cause:  The path specified did not exist and could not be created.
ThinIFS and ThinSRV support "/T:" and "/L1:" parameter values
that require subdirectories to be created.  This error is as a result
of an unsuccessful attempt to create the specified path.

Action:  Supply a valid  drive/path (directories will be created if
necessary) as argument for the "/T:" or "/L1:" parameters.

---------  

XI10034: Usage: [<path>]THINSRV /s: /t: /r: {/l1: /u: /tu:}

Cause:  Incorrect THINSRV program invocation.

Action: See program invocation documentation

---------  

XI10035: Usage: [<path>]THINIFS /s: /t: /req: /srv: /d: {/l1: /ns: /a: /tu:}

Cause:  Incorrect THINIFS invocation.

Action: Reference invocation documentation.

---------  

XI10036: The specified source is not valid.

Cause:  The source parameter provided on the program invocation
is not valid.

Action: Ensure that the value for the source parameter is correct
and refers to a valid OS/2 location.

---------  

XI10037: The source must be a valid path specification.

Cause:  The source parameter provided on the program invocation line
does not refer to a valid OS/2 path.

Action: Ensure that the value for the source parameter is correct
and refers to a valid OS/2 location.

---------  

XI10038: The specified target is not valid.

Cause:  The target parameter provided on the program invocation line
does not refer to a valid OS/2 path.

Action: Ensure that the value for the target parameter is correct
and refers to a valid OS/2 location.

---------  

XI10040: Unable to write to ***; the return code is ***.

Cause:  An attempt to write the specified file to disk was not successful.
The return code from the OS/2 request is provided.

Action: Verify that there was sufficient disk space to perform the
write.  Determine more information from an OS/2 programmers reference
based on the return code provided.

---------  

XI10041: Unable to read from ***; the return code is ***.

Cause:  An attempt to read the file specified was not successful.  The
OS/2 return code is returned.

Action: Verify the file specified exists.  Determine more information
from the OS/2 Programmers Reference regarding the return code.

---------  

XI10042: *** did not complete successfully.

Cause:  The specified program did not complete successfully.

Action: See associated error messages.

---------  

XI10050: A syntax error caused SRVATTCH not to start.

Cause:  The number of parameters entered was incorrect.
Action: Change the syntax for SRVATTCH to:
SRVATTCH { DRIVE: | * }  {{ SERVERNAME | *P  { /W }  }  |  /Detach }

---------  

XI10052: The drive letter was entered incorrectly.
Cause:  The drive letter is not valid for one of the following reasons:
An A or B was entered.
The colon was missing.
More than a single character and colon were used.

Action:  Specify the drive by entering a letter other than A or B
followed by a colon.

---------  

XI10053: The SRVIFS redirector is not started on this system.

Cause:  The SRVATTCH command did not complete because the SRVIFS redirector
is not started.

Action:  Ensure that the system has been set up properly.  NetBIOS must be
loaded, and THINIFS must have completed successfully.

---------  

XI10054: The LAN Adapter for SRVIFS is not active.

Cause:  SRVIFS cannot be run because its LAN Adapter has been closed.

Action:  Shut down the system from the OS/2 desktop to reset the adapter.
Then restart the command.

---------  

XI10055: The SRVIFS DEVICE= statement, the IFS= statement, or both are not 
installed in CONFIG.SYS file.

Cause:  THINIFS has not been installed properly, or the system was not
rebooted after CONFIG.SYS was updated.

Action:  Ensure that the DEVICE= and IFS= statements for SRVIFS are in
CONFIG.SYS.  Shut down the system from the OS/2 desktop.  Then restart
the command.

---------  

XI10056: The server name *** cannot be found.

Cause:  Either the SRVATTCH command was issued with an incorrect
server name, or the server is not running.

Action:  Verify the server name and ensure that it is running.

---------  

XI10057: The alias name *** was not found.

Cause:  The specified alias does not exist.

Action:  Specify an alias that is defined at the server.

---------  

XI10058: SRVIFS could not start.

Cause:  The adapter specified in the IFS= statement for SRVIFS in the
CONFIG.SYS file is not configured for NetBIOS.

Action:  Ensure that the /A: parameter of the IFS= statement in CONFIG.SYS
specifies the number of an adapter that is configured for NetBIOS.  If no
adapter is currently configured for NetBIOS, use the MPTS installation program
to perform the necessary configuration.

---------  

XI10059: The specified drive could not be detached.

Cause:  The drive letter specified is not currently attached.

Action:  If desired, retry the command using a drive that is currently
redirected.

---------  

XI10060: Drive *** is already assigned.

Cause:  The drive specified is already redirected by a previous SRVATTCH
command.

Action:  Specify a drive letter that is not being used.

---------  

XI10061: The connection request to server *** is denied.

Cause:  The attach failed because the current client name is not
authorized.

Action:  Check the .LST file on the server machine to ensure that the client
name is authorized.  If no use of authorizations is intended, the .LST
file should be NULL, containing only comments with no blank lines.

---------  

XI10062: The client could not be attached to server ***.

Cause:  The server already has the maximum number of clients attached.

Action:  Detach from the server one or more clients that are no longer active,
and retry the command.

---------  

XI10063: The connection attempt was not successful.

Cause: The maximum number of connections is already active.

Action: Close any inactive LAN sessions so that an entry will become 
available.
Retry the SRVATTCH command.

---------  

XI10064: The client could not be started.

Cause:  The client name specified in the IFS= statement in CONFIG.SYS file
is a duplicate of another system already started on the network.

Action:  Ensure that the name specified is unique. An asterisk (*) may be used
instead of a name, which causes SRVIFS to assign a unique name.

---------  

XI10065: The command could not be completed successfully.

Cause:  There are not enough system resources available.

Action:  Stop any applications that are no longer in use, and retry the 
command.

---------  

XI10066: *** failed with rc = ***.

Cause:  ATTACH or DETACH failed for an undetermined reason.

Action:  Contact your IBM service representative.

---------  

XI10069: The client name must contain only letters and numbers.
Cause:  An incorrect client name was used.

Action:  If SRVIFS prompts for a requester name, enter a name that is
alphanumeric.  Otherwise, specify an alphanumeric name in the IFS= statement
in the CONFIG.SYS file.

---------  

XI10070: An invalid client name was specified.
Cause:  An invalid client name was specified.

Action:  If SRVIFS prompts for a client name, enter a name that is
1-15 alphnumeric characters in length.  Otherwise specify a name 1-15 
alphanumeric
characters long in the IFS= statement in the CONFIG.SYS file.

---------  

XI10071: The specified adapter could not be used.
Cause:  The adapter number specified in the IFS= statement, for SRVIFS,
in the CONFIG.SYS file has an adapter number other than 0 or 1.

Action:  Ensure that the adapter number (A:x) is 0 or 1 in the IFS=
statement in CONFIG.SYS.

---------  

XI10073: A NetBIOS error occurred with rc = *** (in decimal).

Cause:  A NetBIOS error has occurred during an IFS call. A possible problem
is that a disconnect occurred.

Action:  Shut down the system from the OS/2 desktop. Try to restart the
command. If the problem persists contact your IBM service representative.

---------  

XI10075: Adapter 0 failed to register with the network.

Cause:  A NetBIOS error occurred during InitListen.  SRVIFS cannot function.

Action:  Try to restart SERVICE.

---------  

XI10076: Adapter 1 failed to register with the network.

Cause:  A NetBIOS error occurred during InitListen.  SRVIFS cannot function.

Action:  Try to restart SERVICE.

---------  

XI10077: SRVIFS was unable to create a shared memory segment.

Cause:  The DosCall DosAllocShrSeg  failed.

Action:  Contact your IBM service representative.

---------  

XI10078: The configuration parameters defined in the SRVIFS Server .INI file 
exceeds the 64kb work area.

Cause:  The area needed to hold the configuration defined in the SRVIFS
.INI is larger than the maximum allowable size.  The sum of the config-
uration parameters exceeded 64kb.

Action:  Reduce the Maxclients, Adapters, or number of Alias in the
.INI file for SRVIFS, or use the default values; then retry the
operation.

---------  

XI10079: SRVIFS was unable to create a system semaphore.

Cause:  An OS/2 error occurred during DosCreateSem.

Action:  Contact your IBM service representative.

---------  

XI10080: The PATH= statement, in the .INI file for SRVIFS, is missing or is 
incorrect.

Cause:  The PATH= statement, in the .INI file for SRVIFS, is missing or is 
incorrect.

Action:  Add the PATH= statement to the .INI file.  The path should specify
a directory to use if the client does not specify an alias.

---------  

XI10081: The syntax for SERVICE is: SERVICE [ /Quit | /Force | /Status | 
/Authlist | /ini=name ].

Cause:  A "?" was entered as an argument.

Action:  Enter a valid command statement.

---------  

XI10082: The SERVICE command was not specified correctly.

Cause:  One of the arguments passed on the SERVICE command was not correct,
too long, or not alphanumeric.

Action:  The syntax for SERVICE is: SERVICE [ /Quit | /Force | /Status | 
/Authlist | /ini=name ].
Where name must be 1-8 characters long and alphanumeric.

---------  

XI10083: SERVICE was unable to open the adapters for requested NetBIOS 
configuration.

Cause:  NetBIOS resources are not currently available.

Action:  Stop any inactive LAN sessions.  Try to restart SERVICE.

---------  

XI10084: SERVICE was unable to establish NetBIOS Services.

Cause:  An error occurred during the attempt to start communications.

Action:  Contact your IBM service representative.

---------  

XI10085: *** cannot be started.

Cause:  The server name specified in the .INI file for SRVIFS is already in 
use.

Action:  Change the server name in the current .INI file to a name that is not
in use , or use an .INI file that specifies a server name that is not in use.

---------  

XI10087: *** is not running.

Cause:  The specified server is not active.

Action:  Specify an active server for the request.

---------  

XI10105: Insufficient session resources are available on adapter *** : 
Requested = ***  Available = ***

Cause:  A NetBIOS reset failed because not enough sessions were available
at the time of the call.

Action:  Stop any inactive LAN sessions.  Try to restart SERVICE.

---------  

XI10106: Insufficient command resources are available on adapter *** : 
Requested = ***  Available = ***

Cause:  A NetBIOS reset failed because not enough commands were available
at the time of the call.

Action:  Stop any inactive LAN sessions.  Try to restart SERVICE.

---------  

XI10107: Insufficient names resources are available on adapter *** : Requested
= ***  Available = ***

Cause:  A NetBIOS reset failed because not enough names were available
at the time of the call.

Action:  Stop any inactive LAN sessions.  Try to restart SERVICE.

---------  

XI10108: A NetBIOS reset call failed on adapter *** with rc = ***.

Cause:  NetBIOS failed to reset the adapter.

Action:  Contact your IBM service representative.

---------  

XI10110: NetBIOS could not add a name on adapter ***.  The rc = ***.

Cause:  NetBIOS failed to add a name to the specified adapter for an
undetermined reason.

Action:  Contact your IBM service representative.

---------  

XI10111: SERVICE could not find the NetBIOS files on the system.

Cause:  NetBIOS is not correctly installed on the system.

Action:  Use the MPTS installation program to specify NetBIOS for the
adapter(s) to be used by SRVIFS.

---------  

XI10112: The return code for Listen was  *** on adapter  ***.

Cause:  The server failed to register with the network.  The reason for the
failure is undetermined.

Action:  Contact your IBM service representative.

---------  

XI10116: *** rejected a connection from ***.

Cause:  The client name is not authorized.

Action:  Check the .LST file on the server to ensure that the client
name is authorized.  If no use of authorizations is intended, the .LST
file should be NULL, containing only comments with no blank lines.

---------  

XI10117: Session initiation from the client *** timed out on adapter ***.

Cause:  The session ended abnormally for the specified adapter.  The
cause cannot be determined.

Action:  Try to restart SERVICE.  If the problem persists, contact your
IBM service representative.

---------  

XI10119: Unknown case value *** was received.

Cause:  An unexpected software error occurred.  The cause cannot be
determined.

Action:  Call your IBM service representative.

---------  

XI10120: A system semaphore was interrupted with rc = ***.

Cause:  An external factor interrupted the semaphore.  Its cause cannot be
determined.

Action:  Contact your IBM service representative.

---------  

XI10121: An unexpected RECEIVE return code = *** was received on Adapter ***.

Cause:  An error occurred during the RECEIVE command on the specified adapter.
Its cause cannot be determined.

Action:  Contact your IBM service representative.

---------  

XI10122: *** is terminating.

Cause:  An undetermined and unrecoverable error occurred in NetBIOS.

Action:  Contact your IBM service representative.

---------  

XI10124: The ADAPTER parameter could not be set.

Cause:  An incorrect value was specified for ADAPTER.

Action:  Change the value for ADAPTER in the .INI file for SRVIFS
to 0, 1, or BOTH.

---------  

XI10125: The MAXCLIENTS parameter must be an integer.

Cause:  An incorrect value was specified for the MAXCLIENTS parameter.

Action:  Change the MAXCLIENTS value in the .INI file for SRVIFS to
an integer between 1 and 100.

---------  

XI10126: The MAXCLIENTS parameter must be 1 to ***.

Cause:  The value for MAXCLIENTS exceeded the maximum.

Action:  Change the MAXCLIENTS value in the .INI file for SRVIFS to a number
within the range specified in the message.

---------  

XI10127: The MAXCLIENTS parameter could not be set.

Cause:  The value for MAXCLIENTS exceeded the maximum.

Action:  Change the MAXCLIENTS value in the .INI file for SRVIFS
to be an integer between 1 and 100.

---------  

XI10128: The MAXFILES parameter must be 100 to ***.

Cause:  The value for MAXFILES exceeded the maximum.

Action:  Change the MAXFILES value in the .INI file for SRVIFS
to a number within the range specified in the message.

---------  

XI10129: The directory *** specified for the PATH= parameter could not be 
found.

Cause:  The specified directory does not exist.

Action:  Specify a directory that exists for the PATH= statement in the
.INI file for SRVIFS.

---------  

XI10130: The PATH= parameter *** is incorrect.

Cause:  The syntax was incorrect for the PATH= parameter.

Action:  Specify an existing value for PATH= in the .INI file for SRVIFS.

---------  

XI10131: An incorrect value was used for NAME in the .INI file for SRVIFS.

Cause:  An incorrect value was used for NAME.

Action:  Change the value for NAME in the .INI file for SRVIFS to be
alphanumeric.

---------  

XI10132: The NAME parameter could not be set.

Cause:  The string value for NAME exceeded the maximum.

Action:  Change NAME in the .INI file for SRVIFS to a value no longer
than 15 characters.

---------  

XI10133: The GROUPNAME parameter could not be set.

Cause:  An incorrect value was specified for GROUPNAME.

Action:  Change the value for GROUPNAME in the .INI file for SRVIFS
to either Yes or No.

---------  

XI10134: The authorization list *** could not be found.

Cause:  The authorization list was specified incorrectly.

Action:  Change the AUTHLIST parameter in the .INI file for SRVIFS
to a name that exists.

---------  

XI10135: An incorrect parameter was specified for AUTHLIST.

Cause:  AUTHLIST contained an incorrect parameter.

Action:  Change the AUTHLIST statement in the .INI file for SRVIFS to contain
only valid parameters.

---------  

XI10136: The LOGEXEC parameter *** could not be found.

Cause:  LOGEXEC contained a non-existent parameter.

Action:  Change LOGEXEC in the .INI file for SRVIFS so that it contains an
existing parameter.

---------  

XI10137: The alias directory *** on line *** of *** could not be found.

Cause:  A nonexistent directory name was specified.

Action:  Change the directory name in the .INI file for SRVIFS to one
that exists.

---------  

XI10138: The alias path specified on line *** of *** could not be found.

Cause:  An incorrect value was specified for the alias path.

Action:  Specify a valid path, at least 3 characters in length, for the alias
in the .INI file for SRVIFS.

---------  

XI10139: The read_style parameter is incorrect on line *** of ***.

Cause:  An incorrect value was specified for alias style.

Action:  Change the read_style parameter in the .INI file for SRVIFS
to either perclient or single.

---------  

XI10140: The alias access parameter is incorrect on line *** of ***.

Cause:  An incorrect value was specified for alias access.

Action:  Change the alias access parameter in the .INI file for SRVIFS
to either readonly or readwrite.

---------  

XI10141: The alias *** on line *** of *** could not be used.

Cause:  A duplicate value was specified for the alias name.

Action:  Change the alias name in the .INI file for SRVIFS to a unique name.

---------  

XI10142: The alias name on line *** of *** could not be used.

Cause:  A value that exceeded the maximum length was specified for alias name.

Action:  Change the Alias name in the .INI file for SRVIFS to a name
less than or equal to 8 characters.

---------  

XI10143: An alias syntax on line *** of *** was found.

Cause:  An alias syntax error occurred.

Action:  Change the syntax of the specified line in the .INI file for SRVIFS.

---------  

XI10144: A syntax error was found on line *** of ***.

Cause:  A syntax error occurred.

Action:  Change the syntax of the line specified in the .INI file for SRVIFS.

---------  

XI10145: The .INI file *** for SRVIFS could not be opened.

Cause:  Either the .INI file for SRVIFS was specified with a non-existent
name, or the file is damaged.

Action:  Try to restart SERVICE with an .INI file for SRVIFS that exists.
If the file does exist, ensure that it is not damaged.

---------  

XI10146: The .INI file *** for SRVIFS could not be found.

Cause:  The directory search failed because the file does not exist or the
path is incorrect.

Action:  Ensure that the .INI file name exists.  If the file exists,
ensure the PATH= statement in the CONFIG.SYS file is correct.

---------  

XI10147: The memory allocation used for an authorization entry failed.

Cause:  Insufficient memory is available for the authorization entry.

Action:  Stop any applications that are no longer active, and retry the 
command.

---------  

XI10148: The authorization ID *** could not be used.

Cause:  The value specified for the authorization ID was too long.

Action:  Change the authorization ID in the .INI file for SRVIFS
to a value less than or equal to 15 characters.

---------  

XI10149: The authorization address *** for *** could not be found.

Cause:  An incorrect value was specified for the authorization address.

Action:  Change the authorization address in the .INI file for SRVIFS
to a value less than or equal to 12 characters.

---------  

XI10150: A blank entry was found on line *** of the .LST file, but SERVICE is 
continuing.

Cause:  An blank line was incorrectly specified in the .LST file for SRVIFS.

Action:  Remove the blank line from the .LST file for SRVIFS before you
use SERVICE again.

---------  

XI10151: SERVICE was unable to open the .LST file ***.

Cause:  Either the .LST file for SRVIFS does not exist, or it is damaged.

Action:  Ensure that the .LST file for SRVIFS exists.  If the file exists,
ensure that it is not damaged.

---------  

XI10155: The server name cannot be used.

Cause:  The operation failed because the server name already exists, and
AdapterCard = BOTH, and GroupName = NO in the .INI file for SRVIFS.

Action:  Change the GROUPNAME parameter in the .INI file for SRVIFS to Yes,
because both adapters are in the same network.

---------  

XI10157: The MAXFILES parameter must be an integer.

Cause:  An incorrect value was specified for MAXFILES.

Action:  Change the MAXFILES parameter in the .INI file for SRVIFS
to an integer between 100 and 9999.

---------  

XI10158: The MAXFILES parameter value could not be used.

Cause:  The string value for MAXFILES exceeded the maximum.

Action:  Change the MAXFILES parameter in the .INI file for SRVIFS
to an integer between 100 and 9999.

---------  

XI10159: The PERMITWRITE parameter could not be used.

Cause:  An incorrect value was specified for PERMITWRITE.

Action:  Change the PERMITWRITE parameter in the .INI file for SRVIFS
to either Yes or No.

---------  

XI10160: The PERCLIENT parameter could not be used.

Cause:  An incorrect value was specified for PERCLIENT.

Action:  Change the PERCLIENT parameter in the .INI file for SRVIFS
to either Yes or No.

---------  

XI10161: The CLIENTWORKERS parameter must be an integer.

Cause:  An incorrect value was specified for CLIENTWORKERS.

Action:  Change the CLIENTWORKERS parameter in the .INI file for SRVIFS
to an integer between 2 and 12.  The default is 6.

---------  

XI10162: The CLIENTWORKERS parameter must be between 2 and ***.

Cause:  An incorrect value was specified for CLIENTWORKERS.

Action:  Change the CLIENTWORKERS parameter in the .INI file for SRVIFS
to a number within the range specified. The default is 6.

---------  

XI10163: The CLIENTWORKERS parameter could not be used.

Cause:  The string value specified for CLIENTWORKERS exceeded the
maximum.

Action:  Change the CLIENTWORKERS parameter in the .INI file for SRVIFS
to an integer between 1 and 12.

---------  

XI10179: An allocation error has occurred for the worker stack.

Cause:  The system's resources are exhausted.

Action:  Stop any applications that are no longer in use, and retry the
command.

---------  
