OS/2 Shareware BBS: 18 REXX/18-REXX.zip/rxneterr.zip/neterr.tab

Text File | 1997-04-21 | 117KB | 1,445 lines

CAS0002: *** was passed an unsupported parameter: ***.
CAS0003: *** was not able to access the log file ***.
CAS0004: *** could not find the directory ***.
CAS0005: *** - The required parameter *** was not specified.
CAS0006: *** cannot find a SRVIFS drive. If a SRVIFS drive is not attached, then the /REQ: parameter must be supplied on the command line.
CAS0007: *** - The *** parameter was specified more than once.
CAS0008: *** - The REXX command file *** was not found.
CAS0009: *** - The REXX command file *** was not found.The program will attempt to run ***.
CAS0010: *** - A command file name must follow ***.
CAS0013: REXX has not been initialized.
CAS0014: An error occurred while validating ***.
CAS0015: The value for the *** parameter must be alphanumeric.
CAS0016: *** - An alphanumeric client name must follow ***.
CAS0018: If /REQ:* is on the command line, then one of the /D or /D: parameters must also be on the command line.
CAS0020: The value for the *** parameter cannot contain drive or path information.
CAS0021: *** cannot open the file *** for input.
CAS0022: *** cannot process *** because it is a hidden file.
CAS0023: *** - The required DEVICE=*** statement was not found in ***.
CAS0024: *** Warning! The *** parameter was not specified.
CAS0025: *** cannot open the temporary file ***.
CAS0026: *** completed with errors.
CAS0028: Both the /D and /D: parameters may not be specified on the command line at the same time.
CAS0029: *** Warning! One or more lines in *** exceed 255 characters.
CAS0033: *** was unable to update ***.
CAS0038: *** - A valid drive indicator must follow ***.
CAS0039: *** - A fully-qualified file name must follow ***.
CAS0040: *** - A fully qualified or relative path must follow ***.
CAS0041: The value for this parameter must be no more than *** bytes long.
CAS0045: *** - A fully qualified directory name must follow ***.
CAS0060: *** encountered an error while determining the response file for ***.
CAS0061: *** encountered an error while determining the response file.
CAS0063: *** was passed a nonnumeric value for parameter number ***.
CAS0064: *** was called with an insufficient number of parameters.
CAS0073: [***] *** returned to the REXX program.
CAS0076: The procedure *** was called with an unsupported value*** for the CID type parameter. CID type is the first parameterof the procedure. The supported CID types are:* ***, Normal CID return code processing* ***, Treat return codes 0x4, 0x8, and 0x12 as bad return codes.
ETH0001: The IBM Ethernet adapter was either not found or not specified in thePROTOCOL.INI file.
ETH0003: Multiple IBM Ethernet adapter parameters were specified in the PROTOCOL.INI file.
LSI0001: The operating system must be OS/2 2.0 and above.
LSI0002: The OS/2 Peer installation/configuration program is already running.
LSI0003: There is not enough space on any hard disk.
LSI0004: *** is missing, damaged, or cannot be copied to the hard disk.
LSI0005: *** failed to load.
LSI0006: There is not enough disk space available to process locked files.
LSI0007: The installation/configuration program has detected an error in the *** parameter.
LSI0008: An access-denied error occurred while loading the installation/configuration program.
LSI0009: The installation/configuration program has detected an incorrect value for the OS/2 environment variable REMOTE_INSTALL_STATE.
LSI0010: Logging initialization failed for file ***.
LSI0100: An error occurred while writing to log file ***. Logging to that filehas been disabled.
LSI0101: *** completed unsuccessfully with a return code of ***.
LSI0102: IBMLANLK detected errors processing the following commands.
LSI0105: File specified (/B:***) does not have the proper format.
LSI0106: OS/2 error *** has occurred.
LSI0107: The LAN Server APIs cannot be used.
LSI0108: The syntax is incorrect.
LSI0109: The file or subdirectory *** could not be found.
LSI0110: OS/2 error *** has occurred while processing file ***.
LSI0111: The file or subdirectory *** could not be created.
LSI0112: There is not enough disk space on drive ***.
LT00003: IBM LANDD: A failure occurred during initialization.
LT00006: The protocol manager could not be opened. The return code is ***.
LT00007: The protocol manager would not accept a request.
LT00008: The protocol manager would not supply a configuration image.
LT00009: The protocol manager would not accept module registration.
LT00011: No MAC driver bindings were specified in PROTOCOL.INI. IBM LANDD didnot load.
LT00012: There are too many MAC drivers to bind. IBM LANDD did not load.
LT00013: There are more values specified for keyword *** than allowed. IBM LANDD did not load.
LT00014: System resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM IEEE 802 (LANDD) did not load.
LT00015: The value specified as the node address for MAC *** is not a valid hexadecimal number.
LT00016: The value specified for the node address is not valid for adapter ***. IBM LANDD did not load.
LT00017: The ETHERAND parameter configured for adapter *** is not DIX or 802.3. IBM LANDD did not load.
LT00018: The unrecognized keyword *** was found in PROTOCOL.INI.
LT00020: A value is required for keyword *** in PROTOCOL.INI.
LT00021: The value specified for parameter *** is not valid.
LT00022: The value specified for parameter *** is not valid.
LT00023: Duplicate parameter *** was found in PROTOCOL.INI.
LT00025: The IBM LANDD section was not found in PROTOCOL.INI.
LT00026: The LANMSGDD device driver could not be opened. The return code is ***.
LT00027: An unexpected error was returned from a SetTimer request.
LT00028: An unexpected error was returned from a request to allocate GDT selectors. The return code is ***.
LT00029: An unexpected error was returned from a request to map GDT selectors.The return code is ***.
LT00030: An unexpected error was returned from a PhysToVirt request. The return code is ***.
LT00031: An unexpected error was returned from a PhysToVirt request.
LT00032: An unexpected error was returned from a GetDOSVar request.
LT00033: The operating system installed is not compatible with this program.
LT00034: An unexpected error was returned when the program tried to lock a memory segment.
LT00035: An unexpected error was returned from a VirtToPhys request.
LT00036: An unexpected error was returned when the program tried to allocate memory for the group SAP receive Buffer. The return code is ***.
LT00037: An unexpected error was returned when the program tried to request a GDT for the group SAP recieve buffer.
LT00038: The system is unable to map the group SAP receive buffer to a GDT. The return code is ***.
LT00039: The *** MAC is an 802.3 protocol but is configured for DIX.
LT00040: The *** MAC is a DIX protocol but is configured for 802.3.
LT00041: The *** MAC will not accept the configured node address.
LT00042: The *** MAC was not able to bind. Return Code = ***.
LT00043: An unexpected error occurred when the program tried to set the *** MAC packet filter.
LT00044: An unexpected error occurred when the program tried to set the *** MAC lookahead size.
LT00045: An error occurred when the program tried to set the *** MAC node address.
LT00046: IBM LANDD was unable to open the *** MAC driver.
LT00047: IBM LANDD received an open adapter request before the *** MAC bind completed.
LT00049: IBM LANDD encountered an internal error when the program attempted toreference *** MAC by the logical adapter number.
LT00050: Duplicate node addresses exist on the network for *** MAC.
LT00055: An unexpected error was returned when the program tried to transmit the duplicate node address test. The *** MAC return code is ***.
LT00056: The OpenAdapter request to the *** MAC Driver did not complete withinthe required time limit.
LT00060: An error occurred while attempting to load NETBEUI.
LT00061: There is no section for NETBEUI in PROTOCOL.INI.
LT00064: A version of the redirector was detected that is not compatible with the version of NETBIOS ***.
LT00065: The configuration parameters defined in PROTOCOL.INI exceed the 64KB work area. NETBIOS *** support has ended.
LT00071: The default path is not valid. The default directory will be changedto the root directory.
LT00072: An error occurred while attempting to open or write to file ***. Check for insufficient disk space.
LT00073: FFST/2 is installed but is not started. LANTRAN.LOG is being created.
LT00081: The IBM LANDD device driver is not installed.
LT00082: An unexpected error was returned from an AllocPhys request.
LT00083: An unexpected error was returned from a DosGetInfoSeg request.
LT00084: An unexpected error was returned from a PhysToGDT request.
LT00086: IBM OS/2 LANDLLDD is not installed.
LT00087: IBM OS/2 LANDLLDD: There is not enough memory available for CCB3 areas.
LT00090: Adapter ***: NETBIOS is not operational.
LT00091: No configuration section was found in the PROTOCOL.INI file for either NETBIOS or NETBEUI.
LT00092: NETBIOS does not recognize device driver ***.
LT00093: An error occurred when the program tried to open network device driver ***.
LT00094: A syntax error was detected for ADAPTER *** in the NETBIOS section ofPROTOCOL.INI.
LT00095: No MAC driver bindings were specified in PROTOCOL.INI. IBM NETBEUI did not load.
LT00096: There are too many MAC drivers to bind. IBM NETBEUI did not load.
LT00097: System resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM NETBEUI did not load.
LT00098: An unexpected error was returned from a request to allocate GDT selectors. The return code is ***.
LT00099: The operating system installed is not compatible with this program.
LT00100: The value specified for the node address is not valid for adapter ***. IBM NETBEUI did not load.
LT00101: More values than allowed are specified for keyword ***. IBM NETBEUI did not load.
LT00102: NETBIOS name-in-conflict was received for NETBIOS local name *** (ASCII format). The name-in-conflict frame was transmitted by node address ***.
LT00104: A NETBIOS name-in-conflict has occurred. The same NETBIOS name was detected at node addresses *** and ***.
LT00105: A request to use a free NETBEUI GDT selector failed. The resource isnot available.
LT00106: A NETBIOS link was disconnected because a NETBIOS acknowledgment was not received within the response timer (T1) value.
LT00107: NETBEUI has been notified of a change in network status. A critical network status notification may cause the adapter to close.
LT00108: A request to use a free NETBEUI UI-Frame descriptor failed. The resource is not available.
LT00109: Namecaching has been disabled because insufficient datagrampackets have been configured.
LT00130: An error occurred while attempting to load TCPBEUI.
LT00131: There is no section for TCPBEUI in PROTOCOL.INI.
LT00134: No MAC driver bindings were specified in PROTOCOL.INI. IBM TCPBEUI did not load.
LT00135: There are too many MAC drivers to bind. IBM TCPBEUI did not load.
LT00136: System resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM TCPBEUI did not load.
LT00137: An unexpected error was returned from a request to allocate GDT selectors. The return code is ***.
LT00138: The operating system installed is not compatible with this program.
LT00139: The value specified for the node address is not valid for adapter ***. IBM TCPBEUI did not load.
LT00140: More values than allowed are specified for keyword ***. IBM TCPBEUI did not load.
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.--------- 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 wantto end configuration.
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 Exitif you wantto end configuration.
LT00202: An error occurred while copying from subdirectory *** to subdirectory ***. Make sure that files being copied are not in use in eitherof these subdirectories in any other OS/2 or DOS session. Return to this session and selectRetry to continue configuration. Select Exit if you want to end configuration.
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 cannotbe longer than *** characters.
LT00204: The PROTOCOL.INI file was not found at the path specified. Select OK and respecify the full path.
LT00205: The network adapter drivers were not found at the path specified. Select OK and respecify the full path.
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.
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.
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.
LT00209: A decimal number must be entered. (or) A hexadecimal number must be entered.
LT00210: An error occurred while attempting to update ***.
LT00211: An error occurred while attempting to read ***.
LT00212: An error occurred while copying from subdirectory *** to subdirectory***.
LT00300: The configuration parameters supplied to LTSVCFG are incorrect. Defaults will be used for all adapters.
LT00301: IBM LANVDD: A request for internal memory failed.
LT00302: IBM LANVDD: A failure has occured which prevents LANVDD from operating in this Virtual Dos Machine, Int5C support is terminated for this VDM.
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.
LT00305: LANPDD was unable to register with the Virtual Dos Machine Manager.
LT00307: A failure occurred which has prevented *** from being installed.
LT00308: IBM LANVDD: The system could not obtain or map a GDT Selector.
LT00309: The number of Dos Sessions which LANVDD can support has been exceeded.
LT00310: The Virtual Dos Machine Manager could not allocate a Software Hook required for LANVDD's internal operations.
LT00311: The operating system installed is not compatible with this program.
LT00312: The OS/2 802.2 device driver, LANDD.OS2, is not available. DOS 802.2support is ended for all VDMs.
LT00314: LANVDD.OS2 was unable to map a virtual address to a linear address in system memory.
LT00315: A status indication was received for an unknown application ID.
LT00316: A status indication was lost or ignored.
LT00317: LANVDD is unable to access DOS memory.
LT00318: The maximum number of OS/2 802.2 user applications was reached.
LT00319: The maximum number of OS/2 802.2 SAPs was reached.
LT00320: LANVDD was unable to allocate the requested OS/2 SAP buffers.
LT00322: LANDD did not complete a LANVDD BufferFree request successfully.
LT00323: LANVDD was unable to allocate internal memory elements.
LT00324: A LANVDD buffer allocation request was cancelled.
LT00325: LANVDD received a DLC status indication for a SAP that LANVDD did not open.
LT00326: LANVDD was unable to simulate local busy to a DOS application.
LT10001: The protocol manager could not be opened.
LT10002: The adapter was not found or is not responding.
LT10003: Conflicting adapter mode parameter values were found in the PROTOCOL.INI file.
LT10005: Resources are not available to set up the adapter as configured in PROTOCOL.INI.
LT10006: An error occurred while attempting to create a data segment for the alternate adapter.
LT10007: A failure occurred during initialization.Press any key to continue.
LT10013: An error occurred while attempting to set up a FIFO address or an IRQlevel, or during the POST for the primary IBM PC Network adapter.
LT10014: An error occurred while attempting to set up a FIFO address or an IRQlevel, or during the POST for the alternate IBM PC Network adapter.
LT30002: Device ***: A failure occurred during initialization.
LT30003: This protocol used by this adapter is not supported.
LT30004: Device ***: The value specified for a parameter in PROTOCOL.INI is not valid.
LT30005: Device ***: An unrecognized keyword was found in PROTOCOL.INI.
LT30006: Device ***: The 3270 emulation adapter was not found.
LT30007: There are too many IBMXLN devices defined in CONFIG.SYS.
LT30009: Device ***: The protocol manager could not be opened.
LT30010: Device ***: An unexpected error was returned from a DOSDevIOCtl request.
LT30011: Device ***: An error occurred when the program tried to get configuration information from the protocol manager.
LT30012: Device ***: The version of the protocol manager installed is not compatible with this device.
LT30013: Device ***: An unexpected error was returned from an AllocGDTSelectorrequest.
LT30014: Device ***: An unexpected error was returned from a PhysToGDTSelectorrequest.
LT30015: Device ***: The MAC driver is not registered or cannot be found.
LT30016: Device ***: An unexpected error was returned from a PhysToVirt request.
LT30017: Device ***: There was no entry found in PROTOCOL.INI for driver name***. Default values will be used.
LT30018: Device ***: Duplicate driver name *** parameters exist in PROTOCOL.INI.
LT30022: Device ***: The establishment controller is not responding.
LT30023: Device ***: An unexpected error was returned from a SetIRQ request.
LT30024: Device ***: A RESET command was received from the controller.
LT30025: Device ***: A *** protocol error was received from the controller.
LT30026: Device ***: A *** protocol error was sent to controller.
LT30027: Device ***: This controller does not support peer communication protocols.
LT30028: Device ***: The RDEF command from the controller is not valid.
LT30029: Device ***: An unexpected error was returned from a TickCount request.
LT40004: The microcode file *** could not be opened.
LT40005: The microcode file *** could not be read.
LT40006: The bootstrap file *** could not be opened.
LT40007: The bootstrap file *** could not be read.
LT40008: The parameter specified in PROTOCOL.INI for keyword *** is not the proper character type.
LT40009: An unrecoverable error occurred in the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A NDIS device driver program.
LT40010: All IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapters must be set to the same interrupt level.
LT40011: A data-check error occurred while attempting to load the bootstrap code onto the adapter.
LT40012: A checksum error occurred while attempting to load the bootstrap codeonto the adapter.
LT40014: The parameter values have forced the control-block size to exceed theallowable limit.
LT40015: The adapter is not responding.
LT40016: A 2KB window error occurred while attempting to load the bootstrap code onto the adapter.
LT40017: An error occurred while attempting to run the bootstrap code.
LT40018: A parameter error occurred while attempting to run the bootstrap code.
LT40019: A write error occurred while attempting to load the bootstrap code onto the adapter.
LT40020: A checksum error occurred while attempting to load the microcode ontothe adapter.
LT40021: The microcode encountered a program-status error while attempting to write to the adapter.
LT40022: A reset error occurred while attempting to initialize the adapter microcode.
LT40023: A parameter error occurred while attempting to run the microcode.
LT40024: The burned-in address could not be found on the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapter.
LT40025: Duplicate device driver statements exist in CONFIG.SYS.
LT40026: The required parameter DRIVERNAME was not found in PROTOCOL.INI.
LT40027: The protocol manager could not be opened.
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.
LT40029: No physical adapter was found in this machine.
LT40030: The unrecognized parameter *** was found in PROTOCOL.INI.
LT40031: The value specified for network address in PROTOCOL.INI is not valid.The burned-in address will be substituted.
LT40033: A duplicate network address was found while inserting onto the ring.
LT40034: Ring failure or beaconing was encountered while inserting onto the ring.
LT40035: A hardware failure occurred while attempting to open the adapter.
LT40036: A lobe media error has occurred. Ensure that the token-ring cable isconnected to the adapter.
LT40040: This version of the microcode is not supported.
LT40043: An unrecoverable error occurred during an address translation in the IBM Token-Ring 16/4 Network Busmaster Server Adapter/A NDIS device driver.
LT40044: The configuration values have forced the control-block size to exceedthe available memory.
LT80198: The attempt to add the Multiple Link Interface Driver(MLID) protocol ID failed. The ODI2NDI.OS2 cannot function.
LT80199: The attempt to allocate memory for Virtual Boards failed. ODI2NDI.OS2cannot function.
LT80204: The Link Support Layer (LSL.SYS) is not installed. ODI2NDI.OS2 cannot function.
LT80208: An error occurred when ODI2NDI.OS2 tried to set the packet filter foradapter ***. Adapter *** cannot be used by ODI2NDI.OS2.
LT80209: An error occurred when ODI2NDI.OS2 tried to set the lookahead size for adapter ***. Adapter *** cannot be used by ODI2NDI.OS2.
LT80210: An error occurred when ODI2NDI.OS2 tried to set the node address for adapter ***. Adapter *** cannot be used by ODI2NDI.OS2.
LT80211: An error occurred when ODI2NDI.OS2 tried to open adapter ***. Adapter*** cannot be used by ODI2NDI.OS2.
LT80213: ODI2NDI.OS2 was unable to bind to MAC ***. Adapter *** cannot be used by ODI2NDI.OS2.
LT80217: The OpenAdapter request to adapter *** did not complete within the required time limit. Adapter *** cannot be used by ODI2NDI.OS2.
LT80218: There is no section for ODI2NDI.OS2 in PROTOCOL.INI. ODI2NDI.OS2 cannot function.
LT80219: No MAC driver bindings were specified in PROTOCOL.INI. The ODI2NDI.OS2 cannot function.
LT80220: Too many MAC driver bindings were specified in PROTOCOL.INI. ODI2NDI.OS2 cannot function.
LT80221: ODI2NDI.OS2 could not locate the Protocol Manager. ODI2NDI.OS2 cannot function.
LT80222: ODI2NDI.OS2 could not access PROTOCOL.INI. ODI2NDI.OS2 cannot function.
LT80223: ODI2NDI.OS2 could not register with the Protocol Manager. ODI2NDI.OS2cannot function.
LT80224: Frame type *** configured for ODI2NDI.OS2 is inconsistent with other frame types configured for adapter ***. ODI2NDI.OS2 may not function as desired.
LT80225: The frame types configured for ODI2NDI.OS2 are not supported by adapter ***. Adapter *** cannot be used by ODI2NDI.OS2.
LT80226: ODI2NDI.OS2 is configured for an incorrect node address, ***. ODI2NDI.OS2 may not function as desired.
LT80227: A node address was not configured for ODI2NDI.OS2 for adapter ***. Adapter *** cannot be used by ODI2NDI.OS2.
LT80250: Too many parameters were specified.
LT80251: The correct syntax for the command is: [<path>]NWFIXUP [<filespec>]
LT80252: The filespec is not valid.
LT80254: NWFIXUP did not complete successfully. Cause: NWFIXUP encountered an error which prevented it fromcompleting all operations successfully. Usually this error occurs whenyou configure NetWare* Requester Support (ODI2NDI.OS2) prior to installingthe NetWare* Requester.Action: Make sure you have the NetWare* Requester installed. Refer tothe \OS2\INSTALL\LAPSHIST.LOG file for a more detailed description ofthe error.* NetWare is a registered trademark of Novell, Inc.--------- LT80255: An OS/2 error occurred while querying the current drive.
LT80256: An OS/2 error occurred during the attempt to query the current directory.
LT80257: An OS/2 error occurred during the attempt to query the boot drive.
LT80258: The CONFIG.SYS file could not be parsed.
LT80259: A DEVICE= statement invoking ODI2NDI.OS2 could not be deleted from the CONFIG.SYS file.
LT80260: A DEVICE= statement invoking LSL.SYS was not found.
LT80261: A DEVICE= statement invoking ODI2NDI.OS2 could not be added to the CONFIG.SYS file.
LT80262: The MLID device driver could not be disabled in the CONFIG.SYS file.
LT80263: The CONFIG.SYS file image was not written out to disk.
MAC0001: The WD8003 adapter was either not found or not specified in the PROTOCOL.INI file.
MAC0002: The parameters in the PROTOCOL.INI do not match the adapter configuration.
MAC0003: Multiple WD8003 adapter parameters were specified in the PROTOCOL.INIfile.
MAC0004: The installed WD8003 adapter is not supported.
MAC0005: A parameter value in the PROTOCOL.INI file is out of range.
NET2102: The NETWKSTA.200 requester driver is not installed.
NET2103: The server cannot be located.
NET2104: An internal error occurred. The network cannot access a shared memory segment.
NET2105: A network resource shortage occurred.
NET2106: This operation is not supported on requesters.
NET2107: The device is not connected.
NET2114: The Server service is not started.
NET2115: The queue is empty.
NET2116: The device or directory does not exist.
NET2117: The operation is not valid on a redirected resource.
NET2118: The netname has already been shared.
NET2119: The server is currently out of the requested resource.
NET2121: Addition of the requested item exceeds the maximum allowed.
NET2122: The peer server will support only two simultaneous users.
NET2123: The API return buffer is too small.
NET2127: A remote API error occurred.
NET2131: An error occurred while opening or reading IBMLAN.INI.
NET2134: An internal error occurred while calling the requester driver.
NET2136: A general network error occurred.
NET2138: The Requester service has not been started.
NET2140: An internal LAN software error occurred.
NET2141: The server is not configured for transactions.
NET2142: The requested API is not supported on the remote server.
NET2143: The event name is not valid.
NET2146: The specified component could not be found in IBMLAN.INI.
NET2147: The specified parameter could not be found in IBMLAN.INI.
NET2149: A line in IBMLAN.INI is too long.
NET2150: The printer queue does not exist.
NET2151: The print job does not exist.
NET2152: The printer destination cannot be found.
NET2153: The printer destination already exists.
NET2154: The printer queue already exists.
NET2155: No more printer queues can be added.
NET2156: No more print jobs can be added.
NET2157: No more printer destinations can be added.
NET2158: This printer destination is idle and cannot accept control operations.
NET2159: This printer destination request contains a control function that is not valid.
NET2160: The printer processor is not responding.
NET2161: The spooler is not running.
NET2162: This operation cannot be performed on the print destination in its current state.
NET2163: This operation cannot be performed on the printer queue in its current state.
NET2164: This operation cannot be performed on the print job in its current state.
NET2165: A spooler memory allocation failure occurred.
NET2166: The device driver does not exist.
NET2167: The data type is not supported by the processor.
NET2168: The print processor is not installed.
NET2180: The service does not respond to control actions.
NET2181: The service table is full.
NET2182: The requested service has already been started.
NET2183: The service does not respond to control actions.
NET2184: The service has not been started.
NET2185: The service name is not valid.
NET2186: The service is not responding to the control function.
NET2187: The service control is busy.
NET2188: IBMLAN.INI contains a service program name that is not valid.
NET2189: The service cannot be controlled in its present state.
NET2190: The service ended abnormally.
NET2191: The requested pause or stop is not valid for this service.
NET2200: This requester is already logged on to the local area network.
NET2201: The requester is not logged on to the local area network.
NET2202: The user ID or group ID parameter is not valid.
NET2203: The password parameter is not valid.
NET2204: The user ID was not added as a message name.
NET2205: The user ID was not added as a message name.
NET2206: The message name was not deleted.
NET2207: The message name was not deleted.
NET2209: Network logons are paused.
NET2210: A conflict occurred at the domain controller.
NET2212: An error occurred while loading or running the logon script.
NET2214: The domain controller was not specified. Your workstation will be logged on as STANDALONE.
NET2215: The domain controller cannot be found.
NET2217: The domain controller could not validate the logon.
NET2218: The user account cannot be deleted.
NET2219: The accounts file NET.ACC cannot be found.
NET2220: The group ID cannot be found.
NET2221: The user ID cannot be found.
NET2222: The resource name cannot be found.
NET2223: The group already exists.
NET2224: The user account already exists.
NET2225: The resource permission list already exists.
NET2226: Because the user accounts database is replicated from the domain controller, updates are not allowed locally.
NET2227: The user accounts database has not been started.
NET2228: There are too many names in the user accounts database.
NET2229: A disk I/O to access the user accounts database failed.
NET2230: The limit of 64 entries per resource was exceeded.
NET2231: Deleting a user with a session is not allowed.
NET2232: The parent directory cannot be located.
NET2233: The cache for the user accounts session could not be increased.
NET2234: This operation is not allowed on this special group.
NET2235: This user is not in the cache for the user accounts session.
NET2236: The user already belongs to this group.
NET2237: The user does not belong to this group.
NET2238: This user account is undefined.
NET2239: This user account has expired.
NET2240: The user is not allowed to log on at this requester.
NET2241: The user is not allowed to log on at this time.
NET2242: This user's password has expired.
NET2243: This user's password cannot change.
NET2244: This password cannot be used now.
NET2245: The password is shorter than required.
NET2246: This user's password is too recent to change.
NET2247: The user accounts database file is damaged.
NET2248: No updates are necessary to this user accounts database because it has been synchronized with the domain controller.
NET2249: This user accounts database is outdated because it no longer is synchronized with the domain controller. Synchronization is required.
NET2250: The connection cannot be found.
NET2251: This asg_type is not valid.
NET2252: This device is currently being shared.
NET2270: A machine ID has not been configured.
NET2271: The Messenger service is already started.
NET2272: The Messenger service failed to start.
NET2273: The message name cannot be found on the local area network, or the receiving workstation may be busy.
NET2274: This message name has already been forwarded.
NET2276: This message name already exists locally.
NET2277: The maximum number of added message names has been exceeded.
NET2278: The machine ID cannot be deleted.
NET2279: Messages cannot be forwarded back to the same requester.
NET2280: An error occurred in the domain message processor.
NET2282: The message was sent, but not received.
NET2283: The message name is currently in use. Try again later.
NET2284: The Messenger service has not been started.
NET2285: The name is not on the local workstation.
NET2286: The forwarded message name cannot be found on the network.
NET2287: The message name table on the remote workstation is full.
NET2288: Messages for this name are not currently forwarded.
NET2289: The broadcast message was truncated.
NET2294: This is not a valid device.
NET2295: A write fault occurred.
NET2297: A duplicate message name exists on the local area network.
NET2298: This message name will be deleted later.
NET2299: The message name was not successfully deleted from all networks.
NET2300: This operation is not supported on workstations with multiple networks.
NET2301: Directory limits are not enabled on the specified drive.
NET2302: Directory limits are already enabled on the specified drive.
NET2303: The directory is not on a 386 HPFS volume.
NET2304: The supplied directory limit is smaller than the current directory size. The limit was not applied.
NET2305: Support for directory limits on the specified drive cannot complete at this time. The drive is in use or locked by another process. You must shut down and restart your system in order for directory limits to become operational.
NET2306: The directory limit was not found.
NET2307: The directory limit already exists.
NET2308: The 386 HPFS file system failed to enable directory limits on the specified drive.
NET2309: The NET DASD operation failed. Support for directory limits is enabled but is not yet operational.
NET2310: This shared resource does not exist.
NET2311: This device is not shared.
NET2312: A session with that machine ID does not exist.
NET2314: There is not an open file with that ID number.
NET2315: A failure occurred while processing a remote administration command.
NET2316: A failure occurred while opening a remote temporary file.
NET2317: The data returned from a remote administration command has been truncated to 64KB.
NET2318: This device cannot be shared as both a spooled and a nonspooled resource.
NET2319: The information in the list of servers may be incorrect.
NET2320: The workstation is not active on this domain.
NET2321: The redirection of *** to *** cannot be deleted because it is not associated with application ***.
NET2322: The *** parameter specifies a local path. The specified path must exist on each machine that runs the application.
NET2323: One or more logon assignments was not made because one or more of thedevices you specified is already assigned to another resource.
NET2324: At least one of the assignments you tried to delete using the /UNASSIGN parameter does not exist.
NET2325: The user definition was added successfully. However no assignments were made for this user because of the following error: ***.
NET2326: Assignment changes could not be made for this user because the following error occurred: ***. Any other changes to the user definition werecompleted successfully.
NET2327: This is domain-specific information that is only available at servers.
NET2328: The logon assignment was not successful. The limit has been reached.
NET2331: The operation is not valid for this device.
NET2332: This device cannot be shared.
NET2333: This device was not open.
NET2334: This device list is not valid.
NET2335: The queue priority is not valid.
NET2337: There are no shared serial devices.
NET2338: The queue you specified does not exist.
NET2340: This list of devices is not valid.
NET2341: The requested device is not valid.
NET2342: This device is already in use by the spooler.
NET2343: This device is already in use as a serial device.
NET2351: This machine ID is not valid.
NET2354: The string and prefix specified are too long.
NET2356: This path component is not valid.
NET2357: The type of input cannot be determined.
NET2362: The buffer for types is not big enough.
NET2377: This log file exceeds the maximum defined size.
NET2378: This log file has changed between reads.
NET2379: This log file is damaged.
NET2380: The source path cannot be a directory.
NET2381: The source path is not valid.
NET2382: The destination path is not valid.
NET2383: The source and destination paths are on different servers.
NET2385: The run server you requested is paused.
NET2389: An error occurred while communicating with a run server.
NET2391: An error occurred while starting a background process.
NET2392: The shared resource you are connected to could not be found.
NET2400: The LAN adapter number is not valid.
NET2401: There are open files on the connection.
NET2402: Active connections still exist.
NET2403: This netname or password is not valid.
NET2404: The device is being accessed by an active process.
NET2405: The drive letter is in use locally.
NET2406: Logoff failed; a device cannot be disconnected.
NET2407: A network application has tried to write to a named pipe buffer that is full. This can cause delays in the application.
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.
NET2431: The Alerter service table is full.
NET2432: An incorrect or nonexistent alert name was raised.
NET2433: The Alerter service recipient is not valid.
NET2434: A user's session with this server has been ended because the user's logon time has expired.
NET2440: The log file does not contain the requested record number.
NET2450: The user accounts database is not configured correctly.
NET2451: This operation is not permitted when the Netlogon service is running.
NET2452: This operation is not allowed on the last account with administrator privilege.
NET2453: The domain controller for this domain cannot be found.
NET2454: Logon information for this user cannot be set.
NET2455: The Netlogon service has not been started.
NET2456: No more information can be added to the user accounts database.
NET2458: A password mismatch has been detected.
NET2460: The server ID does not specify a valid server.
NET2461: The session ID does not specify a valid session.
NET2462: The connection ID does not specify a valid connection.
NET2463: There is no space for another entry in the table of available servers.
NET2464: The server has reached the maximum number of sessions it supports.
NET2465: The server has reached the maximum number of connections it supports.
NET2466: The server cannot open more files because it has reached its maximum number.
NET2467: There are no additional servers registered on this server.
NET2480: The UPS driver could not be accessed by the UPS service.
NET2500: The specified program returned an error code:
NET2501: The specified program needs extra memory KB:
NET2502: The specified program called an unsupported 21H function:
NET2503: Remote IPL is ended.
NET2504: The specified file is damaged.
NET2505: There is no system loader specified for the remote IPL files.
NET2506: NetBIOS returned an error: The NCB and SMB are dumped above.
NET2507: A disk I/O error has occurred.
NET2508: Image parameter substitution failed.
NET2509: Too many image parameters span disk sectors.
NET2510: The image was generated from a DOS format diskette.
NET2511: Remote IPL will be started again later.
NET2512: The call to the remote IPL server failed.
NET2513: The requester is unable to connect to the image server.
NET2514: The image file on the remote IPL server cannot be opened.
NET2517: The Remote IPL service was ended; check the error log at the remote IPL server for details.
NET2518: Remote IPL startup failed; check the error log for the cause of the problem.
NET2520: The Remote IPL service detected a configuration error but is continuing. Check the error log at the remote IPL server for details.
NET2525: DISKFT.SYS is not installed. Fault Tolerance cannot be started.
NET2526: FTMONIT.EXE is not active. Fault Tolerance cannot be started.
NET2527: An unlock request has been made to a drive that is not locked.
NET2528: A request has been made to lock a drive that is already locked by another process.
NET2529: The Fault Tolerance verification function or correction function cannot be started.
NET2530: The Fault Tolerance verification function or correction function is already stopped.
NET2531: The Fault Tolerance verification function or correction function cannot be stopped. Errors have been found and are being corrected.
NET2532: A request has been made to change the lock state of a drive. The state cannot be changed.
NET2533: An error with the requested handle was not found in \IBMLAN\LOGS\FT.LOG.
NET2534: The drive is not mirrored; Fault Tolerance cannot verify the drive.
NET2600: VNETAPI.OS2 is required for VNETAPI.SYS to run in DOS.
NET2601: VNETAPI requires OS/2 2.0 or later.
NET2751: The domain controller is not available.
NET2758: The system cannot connect to the server.
NET2759: This command is only available to network administrators.
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: ***.
NET2781: The drive specified is not valid or cannot be accessed.
NET2782: The alias has already been created.
NET2783: The alias does not exist.
NET2784: The alias name does not exist.
NET2785: The resource specified is not valid.
NET2786: The domain control database is unreadable or cannot be accessed at this time.
NET2787: The alias is already used as a spooler queue name.
NET2788: The resource is already defined by another alias.
NET2789: The alias is a DOS-only external resource. An external alias cannotbe specified in a NET USE command.
NET2790: The alias is an OS/2-only external resource. An external alias cannot be specified in a NET USE command.
NET2791: The alias is both a DOS and an OS/2 external resource. An external alias cannot be specified in a NET USE command.
NET2792: An application with this name has already been created.
NET2793: The application does not exist.
NET2794: An error occurred while creating domain control database files or subdirectories for a user.
NET2795: An attempt was made to access a domain control database file on a machine that is not the domain controller.
NET2796: The application remark contains an error or is not unique.
NET2800: The Apply operation is not allowed on the specified path.
NET2801: An Apply operation ended prematurely.
NET2802: An apply error occurred with the following information in the returnbuffer: Error path: *** Error code: ***
NET2999: This is the last error in NERR range.--------- NET3000: Drive *** is nearly full. *** bytes are available. Warn users and delete unneeded files.
NET3001: *** errors were logged in the last *** minutes. Review the server error log.
NET3002: *** network errors occurred in the last *** minutes on network ***.Review the server error log. The server or network hardware may need service.
NET3003: There were *** bad password attempts in the last *** minutes. Review the server audit trail.
NET3004: *** access-denied errors occurred in the last *** minutes. Review the server audit trail.
NET3005: Your session to this server has been automatically disconnected because of inactivity.
NET3006: The error log is full. No errors will be logged until the file is cleared or the limit is raised.
NET3007: The error log is 80% full.
NET3008: The audit log is full. No audit entries will be logged until the file is cleared or the limit is raised.
NET3009: The audit log is 80% full.
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.
NET3013: A critical sector error was detected on drive ***. Back up the drive. No data was lost.
NET3014: A bad sector on drive *** cannot be fixed. Run CHKDSK /F on the drive.
NET3015: Drive *** is experiencing severe disk errors. Back up the drive immediately.
NET3016: The write operation on server *** was successful. The remaining space in the directory is *** KB.
NET3017: There was not enough space within the directory on server *** to perform a write operation.
NET3020: A power failure was detected at ***. The server has been paused.
NET3021: Power has been restored at ***. The server is no longer paused.
NET3022: The UPS service is commencing shutdown at *** due to low power on the battery.
NET3023: The write operation was successful, but the size of directory *** on server *** crossed a threshold. The remaining space in the directory is *** KB.
NET3024: There was not enough space within directory *** on server *** to perform a write operation.
NET3025: A bad sector was fixed on drive ***. No data was lost.
NET3026: An error occurred while processing a remote request. The error occurred on drive ***.
NET3030: The server cannot export directory *** to importer ***. It is exported from another server.
NET3031: The replication server could not update directory *** from the sourceon *** due to error ***.
NET3032: Exporter *** did not send an update notice for directory *** at the expected time.
NET3033: User *** has exceeded account limitation *** on server ***.
NET3034: The primary domain controller for domain *** failed.
NET3035: This server failed to authenticate with ***, the domain controller for domain ***.
NET3036: The replicator attempted to log on at *** as *** and failed.
NET3038: The replicator could not access *** on *** because of *** system error.
NET3039: The replicator limit for files in a directory has been exceeded.
NET3040: The replicator limit for tree depth has been exceeded.
NET3041: The replicator cannot update directory ***. It has tree integrity and is the current directory for an active process.
NET3042: Network error *** occurred.
NET3045: System error *** occurred.
NET3046: The replicator cannot log on, user is currently logged on and TRYUSERis set to NO.
NET3047: IMPORT path *** cannot be found.
NET3048: EXPORT path *** cannot be found.
NET3050: The replicator failed to update the signal file in directory *** because of system error ***.
NET3051: IBMLAN.INI or the command line has an incorrect value for ***.
NET3052: The required parameter *** was not provided on the command line or inIBMLAN.INI.
NET3053: *** is not recognized as a valid option.
NET3054: A request for *** resources could not be satisfied.
NET3056: A system error has occurred.
NET3057: An internal consistency error has occurred.
NET3058: IBMLAN.INI or the command line has an ambiguous option: ***.
NET3059: IBMLAN.INI or the command line has a duplicate parameter: ***.
NET3060: The service did not respond to a control signal and was stopped with the DosKillProc function.
NET3061: An error occurred while attempting to run the service.
NET3062: The sub-service *** failed to start.
NET3063: There is a conflict in the value or use of these options: ***.
NET3064: There is a problem with the file ***: ***.
NET3065: The required NetBIOS group name cannot be added to the adapter.
NET3066: The role of this machine cannot be standalone.
NET3067: NUMMAILSLOTS cannot be zero.
NET3074: A security failure has occurred.
NET3078: The server cannot access the user accounts database (NET.ACC).
NET3079: There are incompatible files installed in the IBMLAN tree.
NET3080: The IBMLAN\LOGS directory cannot be accessed.
NET3081: The domain specified could not be used.
NET3082: The machine ID is being used as a message name on another workstation.
NET3084: The user accounts system is not configured correctly.
NET3085: The server is not running with user-level security.
NET3087: The requester detected a problem with the cable connection.
NET3088: View your error log (type NET ERROR) for details.
NET3091: The 386 server cannot be started because CACHE386.EXE is not running.
NET3100: The operation failed because a network software error occurred.
NET3101: The system ran out of a resource controlled by the *** option.
NET3102: The service failed to obtain a long-term lock on the segment for NCBs. The error code is the data.
NET3103: The service failed to release the long-term lock on the segment for NCBs. The error code is the data.
NET3104: An error occurred while stopping the *** service. The error code from NetServiceControl is the data.
NET3105: Initialization failed because of an OS/2 execution failure on path ***. The OS/2 error code is the data.
NET3106: An unexpected NCB was received. The NCB is the data.
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
NET3109: System semaphore *** could not be opened or created. The error codeis the data.
NET3110: Initialization failed because file *** could not be opened or created. The OS/2 error code is the data.
NET3111: An unexpected NetBIOS error occurred. The error code is the data.
NET3112: An SMB that is not valid was received. The SMB is the data.
NET3113: Initialization failed because the requested *** service could not bestarted.
NET3114: Some entries in the error log were lost because of a buffer overflow.
NET3120: Initialization parameters controlling resource usage other than net buffers are sized so that too much memory is needed.
NET3121: The server cannot increase the size of a memory segment.
NET3122: Initialization failed because account file *** is either incorrect or not present.
NET3123: Initialization failed because network *** was not started.
NET3124: The server failed to start. All three parameters for character devices on the server must be zero or all three must be nonzero.
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:
NET3127: The server cannot create the *** mailslot needed to respond to a RELEASEMEMORY alert. The error received is:
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.
NET3130: The server encountered an error while calling NetIMakeLMFileName. The error code is the data.
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.
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.
NET3140: The service has stopped because of repeated consecutive occurrences of an NCB error. The last bad NCB follows in raw data.
NET3141: The Messenger service has stopped because of a lock on the Messengerservice shared data segment.
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.
NET3151: Messages cannot be displayed as pop-ups because of an OS/2 VIO call error. The error code is the data.
NET3152: The SMB that was received is not valid. The SMB is the data.
NET3160: The requester information segment is bigger than 64KB. The size follows, in DWORD format.
NET3161: The requester was unable to get the name-number of the machine ID.
NET3162: The requester could not initialize the asynchronous NetBIOS thread.The error code is the data.
NET3163: The requester could not open the initial shared segment. The error code is the data.
NET3164: The requester host table is full.
NET3165: A bad mailslot SMB was received. The SMB is the data.
NET3166: The requester encountered an error while trying to start the user accounts system. The error code is the data.
NET3167: The requester encountered an error while responding to an SSI revalidation request. The function code and the error codes are the data.
NET3170: The Alerter service encountered an error while creating the list of alert recipients. The error code is ***.
NET3171: An error occurred while expanding *** as a group ID.
NET3172: An error occurred while sending *** the alert message ***. The error code is ***.
NET3173: An error occurred while creating or reading the alerter mailslot. The error code is ***.
NET3174: The server could not read the AT schedule file.
NET3175: The server found an AT schedule record that is not valid.
NET3176: The server could not find an AT schedule file so one was created.
NET3177: The server could not open the *** network.
NET3178: The AT command processor could not run ***.
NET3180: Warning: The lazy write process encountered an error while writing to drive ***. The disk contains damaged data. The cache has been stopped.
NET3181: A bad sector was fixed on drive ***. No data was lost.
NET3182: A hard error occurred while processing a remote request. The error occurred while on drive ***.
NET3183: The 386 HPFS server was unable to be started because of a memory address conflict for network ***.
NET3187: A critical sector error was detected on drive ***. Back up the drive. No data was lost.
NET3188: A bad sector on drive *** cannot be fixed. Run CHKDSK /F on the drive.
NET3189: Drive *** is experiencing severe disk errors. Back up the drive immediately.
NET3190: A NetWksta internal error has occurred: ***.
NET3191: The redirector is out of a resource: ***.
NET3192: An SMB error occurred on connection to ***. The SMB header is the data.
NET3193: A virtual circuit error occurred on the session to ***. The NCB command and return code are the data.
NET3194: A stalled session to *** is being disconnected.
NET3195: An NCB error occurred: ***. The NCB is the data.
NET3196: A write operation to *** failed. Data may have been lost.
NET3197: A reset of driver *** failed to complete the NCB. The NCB is the data.
NET3198: The amount of resource *** requested was more than the maximum. Themaximum amount was allocated.
NET3199: Sideband transmissions have been disabled for the session with server ***.
NET3202: The spooler queue manager did not handshake with the initialization process.
NET3203: A spooler queue *** configuration error occurred. The *** file cannot be found.
NET3204: The server could not create a thread. The THREADS parameter in CONFIG.SYS should be increased.
NET3205: The server could not close ***. The file may be damaged.
NET3206: The replicator cannot update directory ***. It has tree integrity and is the current directory for an active process.
NET3207: The server cannot export directory *** to importer ***. It is exported from another server.
NET3208: The replication server could not update directory *** from the sourceon *** because of error ***.
NET3209: Exporter *** did not send an update notice for directory *** at the expected time.
NET3210: This server failed to authenticate with ***, the domain controller for domain ***.
NET3211: The replicator attempted to log on at *** as *** and failed.
NET3212: Network error *** occurred.
NET3213: The replicator limit for files in a directory has been exceeded.
NET3214: The replicator limit for tree depth has been exceeded.
NET3215: An unrecognized message was received in the mailslot.
NET3216: System error *** occurred.
NET3217: The replicator cannot log on. The user is currently logged on and TRYUSER is set to NO.
NET3218: IMPORT path *** cannot be found.
NET3219: EXPORT path *** cannot be found.
NET3220: The Replicator failed to update the signal file in directory *** due to system error ***.
NET3221: A Fault Tolerance error has occurred with the following characteristics: Severity: *** Error code: *** Drive: *** Block number: *** ***
NET3222: The replicator could not access *** on *** because of system error ***.
NET3223: The primary domain controller for domain *** has failed.
NET3224: An error occurred while changing the password for this workstation.
NET3225: An error occurred while updating the logon or logoff information for***.
NET3226: An error occurred while synchronizing with the primary domain controller ***.
NET3227: The REPL.INI file in subdirectory *** contained an incorrect statement. The statement was ignored.***
NET3228: The following error occurred while updating the access control profile for ***
NET3230: A power failure has been detected.
NET3231: The UPS service performed server shutdown.
NET3232: The UPS service did not complete execution of the user-specified shutdown command file.
NET3233: The UPS driver could not be opened. The error code is the data.
NET3235: RAM for 64KB work buffer.
NET3236: RAM for heap expansion.
NET3237: RAM for file handle table growth.
NET3238: Requester connections.
NET3239: Open file handles.
NET3240: DOS search handles.
NET3241: OS/2 file handles.
NET3242: 64KB work buffers
NET3243: Heap space.
NET3244: RAM for 64KB read-ahead buffer
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
NET3250: Initialization failed because of an incorrect or missing parameter in the IBMLAN.INI file: ***.
NET3251: Initialization failed because of an incorrect line in the configuration file ***. The incorrect line is the data.
NET3252: Initialization failed because of an error in the configuration file ***.
NET3253: The file *** has been changed after initialization. The boot block loading was temporarily ended.
NET3254: The files do not fit in the boot-block configuration file ***.
NET3255: Initialization failed because the dynamic link library *** returned a wrong version number.
NET3256: An unrecoverable error occurred in the dynamic link library of the service.
NET3257: The system returned an unexpected error code. The error code is thedata.
NET3258: The Fault Tolerance error log, \IBMLAN\LOGS\FT.LOG, has been extended.
NET3259: Fault Tolerance was interrupted while updating the error log. One or more log entries may have been lost.
NET3265: A checksum error occurred when accessing the domain control databasefile ***.
NET3266: An error occurred when reading from or writing to the domain controldatabase file ***.
NET3267: The domain control database file *** was not found.
NET3268: The write operation was successful, but the size of directory *** crossed a threshold. The remaining space in the directory is *** KB.
NET3269: There was not enough space within directory *** to perform a write operation.
NET3270: The server encountered an error while initializing internaldata structures. The server uses these structures to process alerts thatpertain to directory limits. The server will not post alerts. The OS/2return code is ***.
NET3271: The server encountered an error while initializing internaldata structures. The server uses these structures to process alerts thatpertain to directory limits. The server will now use its own defaultvalues. The INI file in use is ***.The return code is ***.
NET3272: An error occurred as the server attempted to send a messageconcerning a directory limit. No message was sent. The OS/2 return codeis ***.
NET3273: The 386 HPFS server failed to enable directory limits on drive*** because of insufficient heap space. The drive is still operational.
NET3274: The 386 HPFS server failed to enable directory limits ondrive *** because of a disk error. The drive is still operational.
NET3275: The server detected a parameter in the INI file *** that is notvalid. The parameter is: ***.
NET3276: The server detected a parameter in the INI file *** that doesnot have a valid syntax. The parameter is ***.
NET3277: The server detected and ignored a drive letter that is notvalid within a parameter in the INI file ***. The parameter is ***.
NET3400: There is not enough memory to start the Requester service.
NET3401: An error occurred while reading the NETWORKS entry in the IBMLAN.INI file.
NET3402: This is not a valid argument: ***.
NET3403: The *** NETWORKS entry in the IBMLAN.INI file has a syntax error and will be ignored.
NET3404: There are too many NETWORKS entries in the IBMLAN.INI file.
NET3406: An error occurred while opening network device driver *** = ***.
NET3407: Device driver *** sent a bad BiosLinkage response.
NET3408: The LAN software cannot run on this version of OS/2.
NET3411: There was an error installing NETWKSTA.***. Press ENTER to continue.
NET3412: A resolver linkage problem has occurred.
NET3501: You used an option that is not valid.
NET3502: OS/2 error *** has occurred.
NET3503: The command contains an incorrect number of arguments.
NET3504: The command completed with one or more errors.
NET3505: You used an option with a value that is not valid.
NET3506: The option *** is unknown.
NET3507: Option *** is ambiguous.
NET3508: DOS error *** has occurred.
NET3509: Too many commands were specified as netservices or wrkservices.
NET3510: A command was used with conflicting switches.
NET3511: Subprogram *** could not be found.
NET3512: The software requires a later version of the operating system.
NET3513: More data is available than can be returned.
NET3517: The required parameter, ***, was not specified.
NET3533: The service is starting or stopping. Try again later.
NET3550: File NETACC.OLD exists; NETACC.BKP may be damaged.
NET3551: File NETAUD.OLD exists; NETAUD.BKP may be damaged.
NET3552: File *** cannot be opened.
NET3553: File *** cannot be created.
NET3554: File *** cannot be removed.
NET3555: File *** cannot be renamed to ***.
NET3556: File *** cannot be copied to ***.
NET3557: The access control list backup file *** could not be opened.
NET3558: The file *** is not a valid access control list backup file.
NET3559: BACKACC could not open a temporary work file.
NET3560: There is not enough disk space available on *** for the backup file.
NET3561: The volume label of the source drive, ***, does not match the label specified in the existing access control list backup file ***.
NET3563: BACKACC encountered an unexpected OS/2 error.
NET3564: BACKACC cannot overwrite the backup file ***.
NET3565: *** is not a valid BACKACC option.
NET3566: BACKACC cannot back up NET.ACC and NET.AUD.
NET3567: BACKACC cannot back up the access control list information.
NET3568: The user accounts subsystem could not be started.
NET3569: Warning: Access control lists for drive *** could not be completelycleaned.
NET3570: Warning: The access control list for *** could not be removed.
NET3580: The access control list backup file *** does not exist.
NET3581: RESTACC cannot read the access control list backup file ***.
NET3582: The access control list backup file *** is not a valid access control list backup file.
NET3583: You do not have sufficient privileges to set permissions on ***.
NET3584: RESTACC cannot set permission on *** because it does not exist.
NET3585: User *** does not exist; the access control list entry will be discarded.
NET3586: Group *** does not exist; the access control list entry will be discarded.
NET3587: *** does not exist.
NET3588: You cannot specify newname if pathname contains wildcard characters.
NET3589: *** is not a valid RESTACC option.
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 tocontinue anyway? [***]
NET3591: RESTACC was not able to complete.
NET3592: RESTACC ran out of resources.
NET3593: The maximum number of access control lists for a resource was exceeded.
NET3594: You cannot specify wildcard characters in newname.
NET3595: The backup file *** contains no access control lists.
NET3600: FIXACC cannot run while UPM is running.
NET3601: FIXACC cannot run while the LAN Requester is started.
NET3602: An unknown process is using the User Access Subsystem (UAS).
NET3604: The file *** cannot be opened because of system error ***.
NET3605: The file *** already exists.
NET3606: Network error *** occurred while adding group ***.
NET3607: Network error *** occurred while adding user ***.
NET3608: Network error *** occurred while adding access control for ***.
NET3619: An error *** occurred when FIXACC attempted to update the groups.
NET3669: All open files must be closed before logging off.
NET3672: You are not currently logged on.
NET3687: The server is running with user-level security. The share password is ignored.
NET3692: The program you were running on a remote server ended abnormally. The exit code was ***.
NET3710: An error occurred while opening the help file.
NET3711: The help file is empty.
NET3712: The help file is damaged.
NET3713: A domain controller could not be found for domain ***.
NET3714: This operation requires administrator privilege on systems with earlier versions of LAN software.
NET3716: The device type is unknown.
NET3717: The log file has been damaged.
NET3718: Program file names must end with .EXE.
NET3719: A matching share could not be found. Nothing was deleted.
NET3720: The units-per-week field in the user record contains a value that is not correct.
NET3721: The password is not valid for ***.
NET3722: An error occurred while sending a message to ***.
NET3723: An error occurred while opening a temporary file.
where x:\path is the path to a directory where you want temporaryfiles to be created.--------- NET3724: An error occurred while writing to a temporary file.
NET3725: An error occurred while the share was deleted.
NET3726: The user ID is not valid.
NET3727: The password is not valid.
NET3728: The passwords do not match.
NET3729: The profile could not be loaded.
NET3730: This is not a valid machine ID or domain name.
NET3731: The command is not in the runpath on the remote server.
NET3732: Default permissions cannot be set for that resource.
NET3733: The NETRUN command looks for the program name on the run path. You cannot specify path characters while using NETRUN.
NET3734: A valid password was not entered.
NET3735: A valid name was not entered.
NET3736: The resource named cannot be shared.
NET3737: The permissions string contains permissions that are not valid.
NET3738: You can perform this operation only on LPT and COM devices.
NET3739: *** already has permissions for the resource.
NET3740: *** does not have permissions for the resource.
NET3741: *** is not a valid permission string.
NET3742: *** is not a valid user ID or group ID.
NET3743: The server is not configured for administration.
NET3744: An error occurred while starting CMD.EXE.
NET3745: An error occurred while processing file ***.
NET3746: *** is not a valid source file.
NET3747: *** is not a valid destination file.
NET3748: An error occurred while copying ***.
NET3749: An error occurred while deleting ***.
NET3750: An error occurred while moving ***.
NET3751: An error occurred while searching a directory.
NET3752: No users have sessions with this server.
NET3753: User *** is not a member of group ***.
NET3754: User *** is already a member of group ***.
NET3755: There is no such user: ***.
NET3757: No valid response was provided.
NET3758: The destination list provided does not match the destination list of the printer queue.
NET3759: Your password cannot be changed until ***.
NET3760: *** is not a recognized day of the week.
NET3761: The time range specified ends before it starts.
NET3762: *** is not a recognized hour.
NET3763: *** is not a valid specification for minutes.
NET3764: The time supplied is not exactly on the hour.
NET3765: 12- and 24-hour time formats cannot be mixed.
NET3766: *** is not a valid 12-hour suffix.
NET3767: An incorrect date format has been supplied.
NET3768: An incorrect day range has been supplied.
NET3769: An incorrect time range has been supplied.
NET3770: Arguments supplied with NET USER are not valid. Verify the minimum password length or the arguments supplied.
NET3771: The value for ENABLESCRIPT must be YES.
NET3773: An incorrect country code has been supplied.
NET3774: An incorrect domain controller has been supplied.
NET3787: Your password has expired.
NET3793: Your password has expired. Change it as soon as possible.
NET3794: Your password has expired. Contact your network administrator.
NET3802: This schedule date is not valid.
NET3803: The \IBMLAN root directory is unavailable.
NET3804: SCHED.LOG cannot be opened.
NET3806: The AT job ID does not exist.
NET3807: The AT schedule file is damaged.
NET3808: The delete operation failed because of a problem with the AT schedulefile.
NET3809: The command line cannot exceed 128 characters.
NET3810: The AT schedule file cannot be updated because the disk is full.
NET3812: The AT schedule file is not valid. Delete the file and create a new one.
NET3813: The AT schedule file was deleted.
NET3815: The AT command has timed out. Try again later.
NET3870: *** is not a valid machine ID.
NET3871: *** is not a valid message ID.
NET3912: A time server could not be located.
NET3913: A domain controller could not be found for domain ***.
NET3916: An error occurred while setting the clock at server ***.
NET3921: The users in group *** cannot be enumerated.
NET3924: Only one server can be specified on the command line.
NET3925: The /DOMAIN option cannot be used if a server is specified.
NET3926: You have used an option more than once.
NET3927: The /ALERTS option requires a value of YES or NO.
NET3928: You typed an unrecognized value for the /ALERTS option.
NET3929: You typed the following unrecognized value: ***.
NET3930: There is not enough memory to run the service or command you specified.
NET3932: *** is not a valid domain name.
NET3933: An error occurred while trying to access ***.
NET3934: *** is not a valid user or group.
NET3940: You must supply a value for the *** option.
NET3941: The option *** is not recognized.
NET3942: Too many arguments were given.
NET3943: The users in the domain could not be enumerated.
NET3944: User *** could not be located.
NET3945: No source file was specified.
NET3951: You specified too many values for the *** option.
NET3952: You entered a value that is not valid for the *** option.
NET3953: The syntax is incorrect.
NET3960: The file number supplied is not valid.
NET3961: The print job number supplied is not valid.
NET4902: Your local logon attempt has failed.
NET4905: The local security process has stopped.
NET4907: The 386 HPFS file system driver was not found.
NET4908: LAN Server is already in the locally secured state.
NET4909: The syntax of this command is: PRIV program [options]
NET4910: Privileged access is denied.
NET4912: Warning: LAN Server local security could not be started.The system is booting in privileged mode.
NET4913: An error occurred while starting the privileged file.
NET4914: Error *** occurred while starting the following user shell: ***Trying to start the default shell: C:\OS2\PMSHELL.EXE
NET4915: Error *** occurred while starting the default protect-mode shell: C:\OS2\PMSHELL.EXE
NET4916: PRIV.EXE could not run the program specified.
NET4918: SECURESH.EXE cannot find the privileged modeinitialization script: ***
NET5300: The NCB request completed successfully. The NCB is the data.
NET5301: An NCB buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS is not valid. The NCB is the data.
NET5302: The data descriptor array specified in the NCB is not valid. The NCB is the data.
NET5303: The command specified in the NCB is not valid. The NCB is the data.
NET5304: The message correlator specified in the NCB is not valid. The NCB is the data.
NET5305: An NCB command timed out. The session may have ended abnormally. The NCB is the data.
NET5306: An incomplete NCB message was received. The NCB is the data.
NET5307: The buffer address specified in the NCB is not valid. The NCB is the data.
NET5308: The session number specified in the NCB is not active. The NCB is the data.
NET5309: No resource was available on the network adapter. The NCB request was refused. The NCB is the data.
NET5310: The session specified in the NCB was closed. The NCB is the data.
NET5311: The NCB command was canceled. The NCB is the data.
NET5312: The message segment specified in the NCB is not valid. The NCB is the data.
NET5313: The name already exists in the local adapter name table. The NCB request was refused. The NCB is the data.
NET5314: The network adapter name table is full. The NCB request was refused. The NCB is the data.
NET5315: The network name has active sessions and is now deregistered. The NCB command completed. The NCB is the data.
NET5316: A previously issued Receive Lookahead command is active for this session. The NCB command was rejected. The NCB is the data.
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.
NET5318: An NCB session open was rejected. No LISTEN is outstanding on the remote workstation. The NCB is the data.
NET5319: The name number specified in the NCB is not valid. The NCB is the data.
NET5320: The call name specified in the NCB cannot be found or did not answer. The NCB is the data.
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.
NET5322: The name specified in the NCB is in use on a remote adapter. The NCB is the data.
NET5323: The name specified in the NCB has been deleted. The NCB is the data.
NET5324: The session specified in the NCB ended abnormally. The NCB is the data.
NET5325: The network protocol has detected two or more identical names on thenetwork. The NCB is the data.
NET5326: An unexpected protocol packet was received. There may be an incompatible remote device. The NCB is the data.
NET5333: The NetBIOS interface is busy, or NetBIOS is out of linkstations. The NCB request was refused. The NCB is the data.
NET5334: There are too many NCB commands outstanding. The NCB request was refused. The NCB is the data.
NET5335: The adapter number specified in the NCB is not valid. The NCB is the data.
NET5336: The NCB command completed while a cancellation was occurring. The NCB is the data.
NET5337: The name specified in the NCB is reserved. The NCB is the data.
NET5338: The NCB command cannot be canceled. The NCB is the data.
NET5348: The name is defined by another environment. The NCB is the data.
NET5351: There are multiple NCB requests for the same session. The NCB request was refused. The NCB is the data.
NET5352: A network adapter error has occurred. The only NetBIOS command thatmay be issued is an NCB.RESET. The NCB is the data.
NET5353: Required operating system resources are exhausted; try the operationagain later. The NCB is the data.
NET5354: The maximum number of applications was exceeded. The NCB request was refused. The NCB is the data.
NET5355: No SAPs are available for NetBIOS. The NCB is the data.
NET5356: The requested resources are not available. The NCB request was refused. The NCB is the data.
NET5357: The NCB address is not valid or the length does not fit in the segment. The NCB is the data.
NET5358: NCB.RESET may not be issued from a NetBIOS adapter appendage. The NCB is the data.
NET5359: The NCB_DD_ID value is not valid. The NCB is the data.
NET5360: NetBIOS attempted to lock user storage and the lock failed. The NCB is the data.
NET5363: A NetBIOS device driver open error has occurred. The NCB is the data.
NET5364: A system error has occurred. The NCB is the data.
NET5365: A ROM checksum failure has occurred. The NCB request was refused. The NCB is the data.
NET5366: A RAM test failure has occurred. The NCB request was refused. The NCB is the data.
NET5367: A digital loopback failure has occurred. The NCB request was refused. The NCB is the data.
NET5368: An analog loopback failure has occurred. The NCB request was refused. The NCB is the data.
NET5369: An interface failure has occurred. The NCB request was refused. The NCB is the data.
NET5370: An unrecognized NCB return code was received. The NCB is the data.
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.
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.
NET5380: A network adapter is not working correctly. The NCB request was refused. The NCB is the data.
NET5381: The NCB command is still pending. The NCB is the data.
NET5401: The server name specified is not a valid remote IPL server.
NET5402: The RPL.MAP file was not found or could not be opened on the remote IPL server.
NET5403: An error was detected while reading the RPL.MAP file on the remote IPL server.
NET5404: An error occurred while updating the RPL.MAP file on the remote IPL server.
NET5405: The machine definition does not exist on the remote IPL server.
NET5406: An error was detected while reading configuration files in the IBMLAN\RPL\FITS directory on the remote IPL server.
NET5407: An error was detected while reading configuration files in the IBMLAN\RPL\MACHINES directory tree on the remote IPL server.
NET5408: An error was detected while reading configuration files in the IBMLAN\RPL\IBMCOM directory tree on the remote IPL server.
NET5409: An error was detected while reading configuration files in the IBMLAN\RPLUSER directory tree on the remote IPL server.
NET5410: An error was detected while reading configuration files in the IBMLAN\RPL directory tree on the remote IPL server.
NET5411: Machine configuration files are locked by the remote IPL server filesystem.
NET5412: The server record identifier is not defined in an enabled server record entry in the RPL.MAP file.
NET5413: The machine definition remark was more than 48 bytes.
NET5414: The network adapter directory profile could not be found in the NDISDD.PRO file on the remote IPL server.
NET5415: Machine definition names for DOS or FAT file systems cannot exceed 8bytes.
NET5420: The machine definition could not be created because the name is not unique in the domain.
NET5421: The machine definition already exists on the remote IPL server.
NET5422: The model machine name does not exist on the remote IPL server.
NET5424: The remote IPL OS/2 boot drive identifier is not valid.
NET5425: The network adapter address is not valid.
NET5426: A machine definition already exists with the specified network adapter address.
NET5428: An error was detected while reading machine configuration files on the remote IPL server.
NET5429: An error was detected while writing machine configuration files on the remote IPL server.
NET5430: Files required for creating a machine definition could not be found on the remote IPL server.
NET5432: An error was detected while creating machine configuration directories on the remote IPL server.
NET5433: An error was detected while creating access control profiles on the remote IPL server.
NET5440: The machine definition could not be deleted.
NET5441: An error was detected while deleting machine configuration directories on the remote IPL server.
NET5450: A machine definition of the type requested does not exist on the remote IPL server.
NET5470: The remote IPL OS/2 boot drive identifier cannot be changed because the machine has a Workplace Shell desktop defined.
NET5471: The machine definition name cannot be changed.
NET5472: The machine definition OS/2 version cannot be changed.
NET5473: The machine definition parameter specified is not valid for the current machine definition type.
NET5480: The DOS image file name does not exist.
NET8002: The name of the function detecting the error is ***.
NET8007: The application could not allocate more memory.
NET8023: The fileset *** could not be shared during the LSserver service initialization. The error reported was ***.
NET8024: The printer *** could not be shared during the LSserver service initialization. The error reported was ***.
NET8025: The serial device *** could not be shared during the LSserver serviceinitialization. The error reported was ***.
NET8026: Filesets could not be shared during the LSserver service initialization. The database access error was ***.
NET8027: A printer could not be shared during the LSserver service initialization. The database access error was ***.
NET8028: Serial devices could not be shared during the LSserver service initialization. The database access error was ***.
NET8030: The \IBMLAN directory structure could not be shared.
NET8031: A system error occurred while opening a database file.
NET8036: An error occurred while creating the Network Application folder.
NET8037: LAN Server was unable to delete the Network Applications folder during logoff.
NET8038: The class 'LsProg' cannot be found.
NET8039: There is not enough memory available to create the program object ***.
NET8041: Error *** occurred while connecting *** to ***. Do you want to continue ?
NET8042: Error *** occurred while deleting connection to ***.
NET8064: An OS/2 error has occurred. Correct the problem and press Enter.
NET8073: The specified drive is not a diskette drive.
NET8074: There is not enough memory available to run this command.
NET8075: parameter is not valid.
NET8076: An error occurred while creating the image.
NET8077: An error occurred while writing the image.
NET8078: An error occurred while reading the diskette.
NET8079: An error occurred while reading source file ***.
NET8080: An error occurred while writing file *** to the diskette.
NET8081: An error occurred while opening file *** on the diskette.
NET8082: Insert the diskette and type the command again.
NET8083: File *** in the image definition file cannot be found.
NET8084: There are too many files specified for the image.
NET8085: The image is full. Request a larger image.
NET8086: The image definition file could not be found.
NET8087: The image definition file has a format that is not valid.
NET8088: The DOS system file *** could not be copied.
NET8089: The file name *** is duplicated in the image.
NET8090: The specified drive does not exist.
NET8091: The directory path *** is not valid.
NET8092: Another process is accessing the diskette drive.
NET8093: An error occurred while reading file *** on the diskette.
NET8094: A serious *** error *** was detected by ***.
NET8153: The source drive type is incorrect, or the diskette is faulty.
NET8154: The destination drive or diskette is not valid.
NET8155: There is no definition file for this image.
NET8156: The selected definition file cannot be read.
NET8157: The definition file is not valid.
NET8158: The diskette you are trying to use cannot start a DOS machine.
NET8159: The RPL.MAP file on the source server does not contain the specified server record.
NET8160: The RPL.MAP file was not found on the source server.
NET8161: An error occurred while reading a source file needed to create the image file.
NET8162: An error occurred while writing data to the diskette, indicating that the diskette might be full.
NET8163: A source file specified in the image definition file could not be opened on the target diskette.
NET8164: A file specified in the image definition file cannot be found.
NET8165: A DOS system file could not be accessed.
NET8166: The same source file name appears twice 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.
NET8168: An error was detected while trying to update the AUTOEXEC.BAT file on the diskette.
NET8169: The server record identifier is not valid.
NET8170: The machine name you gave is not in the correct format.
NET8171: The image ID is an incorrect length or contains incorrect characters.
NET8181: The logon assignment of files alias *** to *** failed.
NET8182: The logon assignment of serial device queue *** to *** failed.
NET8183: The logon assignment of printer queue *** to *** failed.
NET8188: A user is already logged on at this requester.
NET8191: Your home directory could not be set up.
NET8193: The domain controller could not be contacted. The logon was validated by a backup server. No LAN Server update activities will be allowed.
NET8194: One or more of your logon alias assignments failed.
NET8195: An error occurred while running your user profile.
NET8198: Any logon assignments, applications, or the PROFILE.CMD file could not be retrieved to be set up or run by the logon program.
NET8210: One or more device redirections are currently in use.
NET8215: OS/2 error number *** occurred while opening ***.
NET8228: The machine ID could not be added to the network adapter.
NET8229: The access profile for the remote IPL workstation could not be added.
NET8231: Logon is currently not available. Try again after the server is started.
NET8232: Logoff is currently not available. Try again after the server is started.
NET8234: Contention for server resources exceeds capacity.
NET8235: The LSserver service has encountered an unexpected OS/2 or network return code: ***
NET8250: The domain control database (DCDB) does not exist on this server.
NET8253: The LSserver service could not create the required access control list (ACL) for the resource: ***.
NET8256: \IBMLAN\DCDB\IMAGES\RPL.MAP was not found in the domain controller.
NET8257: \IBMLAN\DCDB\IMAGES\RPL.MAP in the domain controller has a bad file format or an I/O error.
NET8258: The RPL.MAP file under the netname RPLFILES was not found in the remote IPL server.
NET8259: You must be logged on with administrator privilege before running this program.
NET8260: The RPL.MAP file under the netname RPLFILES in the remote IPL server has a bad file format or an I/O error.
NET8261: An I/O error occurred while updating the RPL.MAP file under the netname RPLFILES on the remote IPL server.
NET8262: The Remote IPL service should not be started before running this program.
NET8263: The IBMLAN.INI file was not found.
NET8264: The IBMLAN.INI file has a bad format or an I/O error.
NET8265: An I/O error has occurred on the IBMLAN.BAK file you used for updating.
NET8270: The DOS system files could not be copied.
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 ***.
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.
NET8278: The temporary file *** could not be written to at the time remote IPLrequester *** attempted to make an alternate boot selection. The requester boot information was not changed.
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.
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.
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.
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 ***.
NET8283: The file *** could not be read at the time remote IPL requester *** attempted to make an alternate boot selection. The requester boot informationwas not changed.
NET8300: A DosMakeMailslot error occurred.
NET8301: A NetAlertStart error occurred.
NET8302: A DosReadMailslot error occurred.
NET8303: A LAN API error occurred.
NET8304: An error occurred while building the generic alert.
NET8305: An OS/2 system error occurred.
PRO0002: PROTOCOL.INI could not be read.
PRO0003: PROTOCOL.INI could not be opened.
PRO0004: The unrecognized parameter *** was found in PROTOCOL.INI.
PRO0005: System resources are not available to hold PROTOCOL.INI.
PRO0006: The numeric value specified for configuration parameter *** in PROTOCOL.INI is not valid.
PRO0007: The value specified in keyword *** is not a valid hexadecimal number.
PRO0008: A numeric value specified in keyword *** in PROTOCOL.INI is not a valid number.
PRO0009: The end double quotation mark is missing for keyword *** in PROTOCOL.INI.
PRO0010: The option specified is not valid.
PRO0011: An equal sign was not found following keyword ***.
PRO0012: An unrecoverable error occurred during initialization.
PRO0013: The PROTOCOL.INI file in the IBMCOM directory is either damaged or has statements in it that are not valid.
PRO0021: A general failure occurred when the program tried to bind *** to ***.
PRO0022: An unspecified failure error occurred when the program tried to bind *** to ***.
PRO0023: The protocol manager could not be found.
PRO0024: The NETBIND command has already been processed.
PRO0025: An error occurred when the program tried to bind *** to ***.
PRO0026: The media access control (MAC) driver is not registered or cannot be found. The request to bind *** to *** cannot be completed.
PRO0027: The adapter was not found when the program tried to bind *** to ***.
PRO0028: A hardware failure occurred when the program tried to bind *** to ***.
PRO0029: A configuration parameter failure occurred when the program tried to bind *** to ***.
PRO0030: Multiple adapters are trying to use the same interrupt level. The request to bind *** to *** cannot be completed.
PRO0031: The version of the media access control (MAC) driver installed is notsupported by the protocol manager. The request to bind *** to *** cannot be completed.
PRO0032: A media access control (MAC) driver initialization failure has occurred. The request to bind *** to *** cannot be completed.
PRO0033: The binding of the media access control (MAC) driver was not successful.
UBI0004: ****** initialization failed.
UBI0005: ***The driver's call to the GetDOSVar DevHlp system call failed.
UBI0006: ***No Protocol Manager driver (PROTMAN$) is installed.
UBI0007: ***There is no PROTOCOL.INI information at all.
UBI0008: ***There is no section in PROTOCOL.INI with DriverName equal to ***$,or to ***n$, n = 2, ..., 9.
UBI0009: ***There is no section in PROTOCOL.INI with DriverName equal to ***$.
UBI0010: ****** is already installed.
UBI0011: ***The *** *** drivers called for by PROTOCOL.INI are already installed.
UBI0012: ***The parameter keyword "***" in the [***] section of PROTOCOL.INI is misspelled, or not supported by ***.
UBI0013: ***Too many parameter values are specified for "***" in the [***] section of PROTOCOL.INI.
UBI0014: ***The type of value given for "***" in the [***] section of PROTOCOL.INI is wrong.
UBI0015: ***The value given for "***" in the [***] section of PROTOCOL.INI is too large for ***.
UBI0016: ***The value given for "***" in the [***] section of PROTOCOL.INI is too small for ***.
UBI0017: ***A bad parameter value is given for "***" in the [***] section of PROTOCOL.INI.
UBI0018: ***The value specified for "***" in the [***] section of PROTOCOL.INIis too long.
UBI0019: ***GDT selector allocation failed.
UBI0020: ***Conversion of the adapter's memory window address to a GDT virtualaddress failed.
UBI0021: ***Conversion of the NIU memory window address to a virtual address failed.
UBI0022: ***Slot *** does not contain an NIUps adapter.
UBI0023: ***The NIUps in slot *** is not enabled.
UBI0024: ***Either there are no enabled NIUps adapters, or they are all reserved by other *** drivers.
UBI0025: ***The NIUps is configured for an illegal window size.
UBI0026: ***The NIU failed its diagnostic tests. Please check the network connection, configuration parameters, and hardware installation.
UBI0027: ***The adapter was reset successfully, but it did not respond after that.
UBI0028: ***The adapter passed its diagnostic tests but failed to halt.
UBI0029: ***The adapter passed its diagnostic tests and was halted, loaded, and started, but it did not complete its initialization.
UBI0030: ***The adapter passed diagnostics and seemed to initialize properly, but its adapter-to-PC interrupt does not work.
UBI0031: ***Working storage GDT selector allocation failed.
UBI0032: ***The memory needed for working storage could not be allocated.
UBI0033: ***Setup of the GDT selectors for working storage failed.
UBI0034: ***The configured number of receive buffers is too large.
UBI0035: ***The memory needed for receive buffers could not be allocated.
UBI0036: ***Receive buffer GDT selector allocation failed.
UBI0037: ***Setup of the GDT selector for ReceiveChain descriptors failed.
UBI0038: ***Setup of the GDT selectors for ReceiveChain buffers failed.
UBI0039: ***The *** module was unable to register with the Protocol Manager.
UBI0040: ***Interrupt handler installation failed.
UBI0041: ***Memory window: 0x***-0x***. IO Ports: 0x***-0x***. IRQ level: ***.
UBI0042: ***Max transmits: ***. Max multicasts: ***.
UBI0043: ***Receive method: ***.
UBI0044: ***Receive buffers: ***. Receive buffer size: ***.
UBI0045: ***Permanent address: ***.
UBI0046: ***Memory used: *** bytes, in conventional memory.
UBI0047: ***Memory used: *** bytes, in upper memory.
UBI0048: ***Memory used: *** bytes in low memory; *** bytes in high memory.
UBI0049: ***Memory used: *** bytes, all in low memory.***--------- UBI0051: ***Permanent address: ***. Slot number: ***.***--------- 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 responseto a MPTS request.
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.
XI00003: An error occurred in the MPTS exception handler. Unable to process current error condition.The MPTS exception handler stack has been changed.
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.
XI00005: An error occurred while reading the file "***".MPTS encountered an error while trying to copy the specified file.
XI00006: An error occurred during configuration.An error occurred while configuring MPTS.
XI00007: An error occurred while initializing the system for configuration.An error occurred while initializing the system for MPTSconfiguration.
XI00008: An OS/2 system error occurred.This message has a number of possible causes.
XI00009: An error occurred while creating the directory "***".This error message is displayed if a call to DosMkDir fails.
XI00010: A memory allocation error occurred.A call to DosAllocSeg returned with an error.
XI00011: Source files for MPTS can not be found on entered path "***".This message is displayed if the MPTS product files could not be foundon the entered path.
XI00012: A Presentation Manager error occurred. MPTS is unable to continue.This message is displayed if any of the WinXxx function calls fails.
XI00013: There is insufficient space on drive "***" for MPTS installation.MPTS checks to ensure that sufficient free disk space is availablebefore continuing with installation.
XI00014: An error occurred while attempting to update "***".This error is returned if MPTS was unable to update the CONFIG.SYS filespecified (location of CONFIG.SYS is indicated).
XI00016: An error occurred while attempting to write to the file "***".MPTS encountered an error while writing data to the specified file.
XI00017: Unable to load the DLL "***".MPTS was either unable to load the specified dynamic link library or todetermine the address of a procedure within the DLL.
XI00018: One or more source files is missing from the MPTS installation diskette.MPTS was unable to find a file needed for installation.
XI00019: Unable to preserve the current PROTOCOL.INI file.This error indicates that MPTS was unable to copy the currentPROTOCOL.INI file to a temporary directory.
XI00020: An error occurred unpacking the file "***".This error indicates that the file unpacking program could not bestarted.
XI00021: An error occurred while attempting to process a locked file.
XI00022: The device "***" is not ready.
XI00023: Unable to copy "***" to the path specified by the L1 parameter.This error indicates that MPTS was unable to perform logging.
XI00024: Unattended configuration was unable to create the PROTOCOL.INI file.
XI00025: Initialization of CID failed.
XI00026: MPTS must be installed before configuration or installing additional drivers can be performed.
XI00030: MPTS installation is being canceled by the user.MPTS installation is being canceled.
XI00032: No network information files were found at "***".This message indicates that no NIFs were found at the specified path.
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 thisNIF.
XI00034: The installation of the driver, "***", failed.This message indicates that MPTS was unable to copy one or more files tothe temporary directory used for installation.
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 driverhas been preserved, MPTS will try to restore the previous copy.
XI00036: The previous version of the driver "***" could not be restored.MPTS attempts to preserve a copy of an existing driver before copying anew version of the driver.
XI00037: The file "***" was not found on the source for additional network drivers.
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 andcannot be replaced.
XI00040: Mult-Protocol Transport Services is currently running. Only one invocation can run at a time.
XI00041: The value provided for MPTS installation target parameter is not valid.
XI00042: Error reading response file.
XI00043: Cannot read the file "***".As part of its operation, MPTS must access many files.
XI00044: MPTS was unable to migrate the OS/2 1.3 Extended Edition configuration file ***.
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 invalidPROT_SECTION.
XI00046: Internal software error during configuration.MPTS checks the values in a response file against the parameters in theappropriate NIF and adjusts them if necessary.
XI00047: Section name "***" is invalid and cannot be used for configuration.MPTS checks the values in a response file against the parameters in theappropriate NIF and corrects them if necessary.
XI00049: Error trying to write a file.
XI00050: Unable to migrate the OS/2 Extended Edition 1.3 configuration file "***" because no LAN information was available.
XI00051: Unable to open the OS/2 Extended Edition 1.3 configuration file "***".
XI00052: Unable to read the 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.
XI00054: The version of configuration file "***" is not supported for migration.
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.
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.
XI00057: Error processing a PROT_SECTION in the response file. The NIF keyword is missing.
XI00058: No Network Information Files (.NIF) were found.
XI00059: MPTS attempted to update CONFIG.SYS and the current PROTOCOL.INI filedoes not contain any configuration information.
XI00060: Not all parameters were specified.
XI00061: Too many parameters were specified.
XI00062: The specified source is not valid.
XI00063: The source must be a valid path specification.
XI00064: The specified target is not valid.
XI00065: The target must be a valid drive specification.
XI00066: The target must be a valid path specification.
XI00068: Unable to execute ***; the return code is ***.
XI00069: *** returned an error; the exit code is ***.
XI00070: *** did not complete successfully.
XI00071: Missing dynamic link library module or entry point; object name is ***.
XI00072: Command line invocation errors. Either not all required parameters were specified or unsupported parameters/values were supplied.
XI00073: Unable to copy ***; the return code is ***.
XI00074: Unable to obtain information for ***; the return code is ***.
XI00075: Unable to open ***; the return code is ***.
XI00076: Unable to seek within ***; the return code is ***.
XI00077: Unable to read from ***; the return code is ***.
XI00078: Unable to write to ***; the return code is ***.
XI00079: Unable to close ***; the return code is ***.
XI00080: Unable to delete ***; the return code is ***.
XI00081: Error reading from ***; not all bytes were read.
XI00082: Error writing to ***; not all bytes were written.
XI00083: Unable to allocate memory; the return code is ***.
XI00084: Error while parsing ***.
XI00085: Usage: [<path>]LAPSDISK <source> <target>
XI00086: Usage: [<path>]LAPSRSP <source> <target> {/m: /n: /b: /v: /t: /i: /c:/u:}
XI00087: LAPSRSP requires a colon to separate the keyword and the value.
XI00088: A LAPSRSP switch is specified but the value is not provided.
XI00089: An invalid switch was specified on the LAPSRSP command line.
XI00090: Invalid installation value.
XI00091: Invalid target drive specification.
XI00092: Invalid upgrade level value.
XI00094: Error processing PROT_NETBIOS in the response file; the SECTION_NAME keyword is missing.
XI00095: The Network Information File (.NIF) filename must be valid and include the filename extension.
XI00096: Unable to locate any Network Information Files (.NIF) on target drive.
XI00097: Unexpected error while searching for Network Information Files (.NIF).
XI00098: Warning: Creating new CONFIG.SYS on the target drive.
XI00099: An error occurred while attempting to add LAPSDEL invocation to MAINTDEL.CMD.
XI00102: SHPIINST.DLL could not be successfully loaded.
XI00103: The MPTS installation was not successful.
XI00104: MPTS did not install due to UPGRADE_LEVEL specified in the response file.
XI00106: An error occurred trying to create the file "***".
XI00107: Error while attempting to copy the file "***".
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.
XI00109: CONFIG.SYS could not be successfully updated with the configuration information provided by MPTS. Your system may not be operational when restarted.
XI00111: The file *** was not found in the ZIP file of the MPTS product image.
XI00114: THINLAPS was unable to copy the file ***; the return code is ***.
XI00115: Error while attempting MPTS installation due to the UPGRADE_LEVEL. The installed version is the same as the version being installed. To reinstallthe same version an UPGRADE_LEVEL of "NEW" or "SAME" must be specified.
SYS0317: The system cannot find message 0118in message file XI0H.MSG.--------- XI00132: Incorrect IP ADDRESS format "***" was specified.
XI00133: Invalid *** parameter specified.
XI00134: SETENVAR usage: /V:EnvVariableName /P:"PromptString"
XI00135: EnvVariableName Name of environment variable to be createdPromptString Prompt string layout
XI00136: SETENVAR: Unknown keyword *** entered.
XI00138: Cannot specify both the IP and PIP parameters.XI00138: Cause: The IP parameter and the PIP parameter cannot be specified at thesame 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 specifiedat thesame 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.
XI00142: A CONFIG.SYS file cannot be located at the value specified for the /TU: parameter.
XI00143: NetBIOS configuration values exceed acceptable configuration requirements.
XI00144: LANDD configuration values exceed acceptable configuration requirements.
SYS0317: The system cannot find message 0147in message file XI0H.MSG.--------- SYS0317: The system cannot find message 0148in message file XI0H.MSG.--------- XI00150: The "/P:" parameter is not valid or was not followed by a valid filespec.
The "/P:" parameter is used to specify the name of a user-suppliedPROTOCOL.INI file that should be used instead of the one generated byThinLAPS.Action: Ensure that the parameter is in the correct format and that itspecifies the name of a valid PROTOCOL.INI file. Retry the operation.--------- XI00151: The syntax for this parameter is "/P:<PROTOCOL.INI filespec>".
XI00165: An error was encountered while trying to unzip file *** from ***. The return code form spawnl function was ***.
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 ***.
XI00167: The *** token was not found while searching the *** file for the devicd driver names.
XI00168: The string "***" was not found while searching the *** file for thedevice driver names.
XI00169: The section "***" was not found while searching the *** file for the device driver names.
XI00170: The syntax error was encountered while searching the "***" file forthe *** token. This error was encountered while searching for device driver names.
XI00171: The file *** was not found in *** file. The return code from the spawnl function is ***.
XI00172: An error occurred while attempting to parse the response file entry for the RFCNAMES_SECT "***".
XI00174: Error processing MPTS_SECT in the response file; the SECTION_NAME keyword is missing.
XI00175: The keyword parameter *** specified in the MPTS_SECT of the response file is invalid.
XI00176: The section name *** specified in the MPTS_SECT of the response file was not found in theMPTCONFG.INI file.
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, anincorrect number of parameters used for that section was specified.Action: Ensure the response file is correct, and that the MPTCONFG.INI is configuredproperly.--------- XI10001: Command line invocation errors. Either not all required parameters were specified or unsupported parameters/values were supplied.
XI10002: CONFIG.SYS file cannot be located as prescribed by the "/TU:" parameter.
XI10003: Unsupported value supplied for the "/D:" parameter on ThinIFS programinvocation.
XI10004: Value supplied for the "/R:" parameter is invalid.ThinSRV expects the fully qualified name of a response file to followthe "/R:" parameter. This parameter is required.
XI10005: Value supplied for the "/U:" parameter is invalid.
the "/U:" parametercorrectly references the source location of a SRVIFS authorizationfile.--------- XI10006: Unsupported value supplied for the "/SRV:" parameter on ThinIFS invocation.
XI10007: Unsupported value supplied for the "/REQ:" parameter on ThinIFS invocation.
XI10008: Unsupported value supplied for the "/NS:" parameter on ThinIFS invocation.
XI10009: Unsupported value supplied for the "/W" parameter on ThinIFS invocation.
XI10010: Unsupported value supplied for the /A: parameter.
The "/A:" parameter may be used on the ThinIFS command line to specifythe 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.
XI10012: NetBIOS not configured in CONFIG.SYS.
XI10013: Unable to read file attributes of the CONFIG.SYS file.
XI10014: Unable to set or restore file attributes of the CONFIG.SYS file.
XI10015: Drive letter *** is already being used as a drive specifier on a SRVATTCH statement in the CONFIG.SYS file.
XI10016: Error attempting to copy the file "***" to target.
XI10017: Unsupported value for "ADAPTER =" statement on line *** in response file.
XI10018: Unable to process response file.
XI10019: Syntax error on line *** in response file.
XI10020: Unsupported value for "MAXFILES =" statement on line *** in response file.
XI10021: Invalid value for "PATH =" statement or path on "ALIAS =" statement on line *** in response file.
XI10022: Invalid value for "NAME =" statement on line *** in response file.
XI10023: Invalid value for "GROUPNAME =" statement on line *** in response file.
XI10024: Unable to open AuthList file "***" for validation of users.
XI10025: Invalid value for "PERMITWRITE =" statement on line *** in response file.
XI10026: Invalid value for "CLIENTWORKERS =" statement on line *** in responsefile.
XI10027: Invalid value in "ALIAS =" statement on line *** in response file.
XI10028: Response file does not contain the required "PATH =" statement.
XI10029: Invalid entry in the AuthList file on line ***.
XI10030: Cannot open log file as specified by the "/L1:" parameter on the invocation command line.
XI10031: Invalid value for "MAXCLIENTS =" parameter on line *** in response file.
XI10032: SERVER file SERVICE.EXE already exists on the target. The file will not be overlaid.
XI10033: Error attempting to create the path "***".
XI10034: Usage: [<path>]THINSRV /s: /t: /r: {/l1: /u: /tu:}
XI10035: Usage: [<path>]THINIFS /s: /t: /req: /srv: /d: {/l1: /ns: /a: /tu:}
XI10036: The specified source is not valid.
XI10037: The source must be a valid path specification.
XI10038: The specified target is not valid.
XI10040: Unable to write to ***; the return code is ***.
XI10041: Unable to read from ***; the return code is ***.
XI10042: *** did not complete successfully.
XI10050: A syntax error caused SRVATTCH not to start.
XI10052: The drive letter was entered incorrectly.
XI10053: The SRVIFS redirector is not started on this system.
XI10054: The LAN Adapter for SRVIFS is not active.
XI10055: The SRVIFS DEVICE= statement, the IFS= statement, or both are not installed in CONFIG.SYS file.
XI10056: The server name *** cannot be found.
XI10057: The alias name *** was not found.
XI10058: SRVIFS could not start.
XI10059: The specified drive could not be detached.
XI10060: Drive *** is already assigned.
XI10061: The connection request to server *** is denied.
XI10062: The client could not be attached to server ***.
XI10063: The connection attempt was not successful.
XI10064: The client could not be started.
XI10065: The command could not be completed successfully.
XI10066: *** failed with rc = ***.
XI10069: The client name must contain only letters and numbers.
XI10070: An invalid client name was specified.
XI10071: The specified adapter could not be used.
XI10073: A NetBIOS error occurred with rc = *** (in decimal).
XI10075: Adapter 0 failed to register with the network.
XI10076: Adapter 1 failed to register with the network.
XI10077: SRVIFS was unable to create a shared memory segment.
XI10078: The configuration parameters defined in the SRVIFS Server .INI file exceeds the 64kb work area.
XI10079: SRVIFS was unable to create a system semaphore.
XI10080: The PATH= statement, in the .INI file for SRVIFS, is missing or is incorrect.
XI10081: The syntax for SERVICE is: SERVICE [ /Quit | /Force | /Status | /Authlist | /ini=name ].
XI10082: The SERVICE command was not specified correctly.
XI10083: SERVICE was unable to open the adapters for requested NetBIOS configuration.
XI10084: SERVICE was unable to establish NetBIOS Services.
XI10085: *** cannot be started.
XI10087: *** is not running.
XI10105: Insufficient session resources are available on adapter *** : Requested = *** Available = ***
XI10106: Insufficient command resources are available on adapter *** : Requested = *** Available = ***
XI10107: Insufficient names resources are available on adapter *** : Requested= *** Available = ***
XI10108: A NetBIOS reset call failed on adapter *** with rc = ***.
XI10110: NetBIOS could not add a name on adapter ***. The rc = ***.
XI10111: SERVICE could not find the NetBIOS files on the system.
XI10112: The return code for Listen was *** on adapter ***.
XI10116: *** rejected a connection from ***.
XI10117: Session initiation from the client *** timed out on adapter ***.
XI10119: Unknown case value *** was received.
XI10120: A system semaphore was interrupted with rc = ***.
XI10121: An unexpected RECEIVE return code = *** was received on Adapter ***.
XI10122: *** is terminating.
XI10124: The ADAPTER parameter could not be set.
XI10125: The MAXCLIENTS parameter must be an integer.
XI10126: The MAXCLIENTS parameter must be 1 to ***.
XI10127: The MAXCLIENTS parameter could not be set.
XI10128: The MAXFILES parameter must be 100 to ***.
XI10129: The directory *** specified for the PATH= parameter could not be found.
XI10130: The PATH= parameter *** is incorrect.
XI10131: An incorrect value was used for NAME in the .INI file for SRVIFS.
XI10132: The NAME parameter could not be set.
XI10133: The GROUPNAME parameter could not be set.
XI10134: The authorization list *** could not be found.
XI10135: An incorrect parameter was specified for AUTHLIST.
XI10136: The LOGEXEC parameter *** could not be found.
XI10137: The alias directory *** on line *** of *** could not be found.
XI10138: The alias path specified on line *** of *** could not be found.
XI10139: The read_style parameter is incorrect on line *** of ***.
XI10140: The alias access parameter is incorrect on line *** of ***.
XI10141: The alias *** on line *** of *** could not be used.
XI10142: The alias name on line *** of *** could not be used.
XI10143: An alias syntax on line *** of *** was found.
XI10144: A syntax error was found on line *** of ***.
XI10145: The .INI file *** for SRVIFS could not be opened.
XI10146: The .INI file *** for SRVIFS could not be found.
XI10147: The memory allocation used for an authorization entry failed.
XI10148: The authorization ID *** could not be used.
XI10149: The authorization address *** for *** could not be found.
XI10150: A blank entry was found on line *** of the .LST file, but SERVICE is continuing.
XI10151: SERVICE was unable to open the .LST file ***.
XI10155: The server name cannot be used.
XI10157: The MAXFILES parameter must be an integer.
XI10158: The MAXFILES parameter value could not be used.
XI10159: The PERMITWRITE parameter could not be used.
XI10160: The PERCLIENT parameter could not be used.
XI10161: The CLIENTWORKERS parameter must be an integer.
XI10162: The CLIENTWORKERS parameter must be between 2 and ***.
XI10163: The CLIENTWORKERS parameter could not be used.
XI10179: An allocation error has occurred for the worker stack.