home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
mptsref.zip
/
MPTSEMSG.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1996-04-04
|
176KB
|
6,888 lines
ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ
First Edition (August 1994)
The following paragraph does not apply to the United Kingdom or any country
where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS
MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states
do not allow disclaimer of express or implied warranties in certain
transactions; therefore, this statement may not apply to you.
This publication could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services that are
not announced in your country. Such references or information must not be
construed to mean that IBM intends to announce such IBM products, programming,
or services in your country.
Requests for copies of this publication and for technical information about IBM
products should be made to your IBM Authorized Dealer or your IBM Marketing
Representative.
ΓòÉΓòÉΓòÉ 2. Notices ΓòÉΓòÉΓòÉ
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used.
Any functionally equivalent product, program, or service that does not infringe
any of IBM's intellectual property rights or other legally protectible rights
may be used instead of the IBM product, program, or service. Evaluation and
verification of operation in conjunction with other products, programs, or
services, except those expressly designated by IBM, are the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any rights to
these patents. You can inquire, in writing, to the IBM Director of Commercial
Relations, IBM Corporation, Purchase, NY 10577.
The following terms, denoted by an asterisk (*) in this publication, are
trademarks of the IBM Corporation in the United States and/or other countries:
IBM Micro Channel
Operating System/2 OS/2
PC Network Presentation Manager
PS/2
The following terms, denoted by a double asterisk (**) in this publication, are
trademarks of other companies as follows:
EtherCard PLUS Standard Microsystems Corporation
EtherLink 3Com Corporation.
Microsoft Microsoft Corporation
NetWare Novell, Inc.
NIU Ungermann-Bass, Inc.
Standard Microsystems Standard Microsystems Corporation
Ungermann-Bass Ungermann-Bass, Inc.
3Com 3Com Corporation.
ΓòÉΓòÉΓòÉ 3. Introduction ΓòÉΓòÉΓòÉ
IBM* AnyNet/2 Multi-Protocol Transport Services (MPTS) provides a transport
that enables Operating System/2* (OS/2*) products to operate on a network. MPTS
consists of the following publications and diskettes:
o Multi-Protocol Transport Services - AnyNet for OS/2: Configuration Guide
o Multi-Protocol Transport Services - AnyNet for OS/2: Programmer's Reference
o Multi-Protocol Transport Services - AnyNet for OS/2: Error Messages and
Problem Determination Guide
o MPTS - Disk 1
o MPTS - Disk 2
o MPTS - Disk 3
ΓòÉΓòÉΓòÉ 3.1. About This Book ΓòÉΓòÉΓòÉ
The Multi-Protocol Transport Services - AnyNet for OS/2: Error Messages and
Problem Determination Guide contains:
o Information to help you to understand and resolve LAN Adapter and Protocol
Support (LAPS) and Socket/MPTS problems that can occur
o Problem determination methods
o Message and error logging information
o Information about how to perform a system trace
o Messages and error recovery information
o Information about when and how to contact IBM
This information will assist you in determining what caused an error to occur
and how to recover from the error.
It is assumed that you are using the appropriate version of IBM Operating
System/2 as your operating system. The term "OS/2", as it is used in the
product documentation and during the running of MPTS refers to IBM Operating
System/2. If you are using an operating system that is functionally equivalent
to OS/2, the product documentation still applies. The functionally equivalent
operating system should provide you with components that correspond to those in
IBM OS/2 but may be identified differently. If there are differences in
component identification, you should contact the supplier of your operating
system for assistance.
ΓòÉΓòÉΓòÉ 3.2. Who Should Use This Book ΓòÉΓòÉΓòÉ
This book is designed for use by the person who will be performing problem
determination and error recovery tasks. This person should be familiar with:
o Local area network (LAN) concepts
o Hardware and software requirements
o The LAPS and Socket/MPTS configurations of the systems they support
o Application programs and other special operations being run on the systems
they support
o The information and special diagnostic tools described in this guide
ΓòÉΓòÉΓòÉ 3.3. How This Book Is Structured ΓòÉΓòÉΓòÉ
This book is organized as follows:
o Using Diagnostic Tools, provides diagnostic information.
o Tools for Advanced Problem Determination for MPTS, provides advanced problem
determination information.
o Error Messages, provides error messages and recovery information.
This book also contains an index.
ΓòÉΓòÉΓòÉ 3.4. Related Books ΓòÉΓòÉΓòÉ
You can find additional information in the following publications:
o IBM Local Area Network Technical Reference
o IBM Token-Ring Network Information and Planning Guide
o IBM 3174 Establishment Controller Peer Communication User's Guide, RPQ8Q0718
o IBM 3174 Workstation Peer Communication Support User's Guide
o IBM NETBIOS Application Development Guide
o IEEE 802.2 Local Area Networks Standard, 802.2 Logical Link Control,
ANSI/IEEE Standard, October, 1985
o IEEE 802.3 Local Area Networks Standard 802.3 Carrier Sense Multiple Access,
ANSI/IEEE Standard, October, 1985
o IEEE 802.5 Local Area Networks Standard, 802.5 Token Ring Access Method,
ANSI/IEEE Standard, June 1989
o Microsoft/3Com LAN Manager Network Driver Interface Specification, Version
2.01, Microsoft** Corporation, 3Com** Corporation
o IBM Automated Installation for CID Enabled Extended Services, LAN Server
V3.0, and IBM MPTS - AnyNet for OS/2
o Multi-Protocol Transport Services - AnyNet for OS/2: Programmer's Reference
o Multi-Protocol Transport Services - AnyNet for OS/2: Configuration Guide
Contact your IBM authorized dealer or your IBM marketing representative for
information about ordering the preceding publications.
The IBM OS/2 NDIS Driver Implementation Package contains information about the
following items:
o Network Driver Interface Specification (NDIS) Version 2.01
o Extended network information file (NIF) format
o NDIS extensions
o IBM Local Area Network Technical Reference extensions
o Message processes and national language support
Contact IBM Corporation, Dept. 483, Austin, TX, 78758, to request copies.
ΓòÉΓòÉΓòÉ 3.5. Information Available Online ΓòÉΓòÉΓòÉ
The OS/2 program contains an online help facility that you can use to access
Help for most messages issued by components of MPTS. In addition, you can
access Help for LAPS installation and configuration messages from the message
panel that is displayed.
ΓòÉΓòÉΓòÉ 3.5.1. OS/2 Command Line Message Help ΓòÉΓòÉΓòÉ
You can view MPTS message Help for most messages by typing HELP XXXxxxx | MORE
(where XXX is the message prefix and xxxx is the message number) at the OS/2
command line and then pressing Enter. This Help describes the cause of the
message and any action you should take to resolve related problems. When text
fills the screen, the system pauses the message on the screen to allow you to
read the text. You can then press any key to continue.
ΓòÉΓòÉΓòÉ 3.5.2. LAPS Installation and Configuration Message Panel Help ΓòÉΓòÉΓòÉ
You can access help for LAPS installation and configuration messages by
selecting the Help push button or pressing F1 in the message panel. This Help
describes the cause of the message and any action you should take to resolve
related problems.
ΓòÉΓòÉΓòÉ 4. Using Diagnostic Tools ΓòÉΓòÉΓòÉ
Use the diagnostic tools described in this chapter to gather and process data
that can help identify the cause of a problem.
After it is collected, the data can be examined by you or by someone who is
familiar with the problem, or provided to IBM for analysis.
ΓòÉΓòÉΓòÉ 4.1. When to Use a Diagnostic Tool and Why ΓòÉΓòÉΓòÉ
These tools are designed to be used as part of the overall problem
determination process and should be used only upon direction provided by one of
the following:
o The messages section of this publication
o An authorized IBM service representative
Only procedural information is provided in this chapter; you should not attempt
to determine when it is appropriate to use one or more diagnostic tools based
solely upon this information.
Brief descriptions of each diagnostic tool follow. Directions for using each
tool are provided later in this chapter.
Note:
1. Information should be sent to IBM for analysis only upon direction from the
IBM Support Center.
2. Do not send IBM information that is considered to be confidential or
proprietary by you or the end user.
ΓòÉΓòÉΓòÉ 4.2. Types of Diagnostic Tools ΓòÉΓòÉΓòÉ
Identifying the source of most software problems begins with examining messages
displayed on the user's screen or saved by one of the message-logging utilities
described in the following topics.
However, there are exceptions. For this reason, you should rely on the
information provided in the messages section of this book or upon direction
provided by an IBM Support Center representative on how to proceed for a given
problem.
ΓòÉΓòÉΓòÉ 4.2.1. MPTS Problems ΓòÉΓòÉΓòÉ
If an error related to MPTS occurs during system initial program load (IPL),
you receive a message and it is also logged in LANTRAN.LOG. Following IPL,
messages are logged in LANTRAN.LOG, LAPSHIST.LOG, and in the First Failure
Support Technology/2 (FFST/2) message log, if present. See Using LANTRAN.LOG,
Using LAPSHIST.LOG, and the FFST/2 message log for additional information.
ΓòÉΓòÉΓòÉ 4.2.1.1. Additional Utilities to Assist You with MPTS Problems ΓòÉΓòÉΓòÉ
In addition to the procedures and tools discussed in this guide to help you
determine MPTS problems, the following utility programs are provided in the
APPLETS subdirectory on MPTS Diskette 3.
o The NBJDSTAT utility program uses NetBIOS to display NCB.STATUS information.
NCB.STATUS information can be useful when you are doing system configuration
and application debug. It includes such information as the adapter encoded
address, the NetBIOS release number, and the local name table. For more
information on the status command, see the IBM LAN Technical Reference,
Chapter 4. NetBIOS must be loaded before this utility can produce meaningful
results.
o The DTF2 utility program formats SYSTRACE output information for major code
164. The DTF3 utility program formats SYSTRACE output information for major
code 164 and major code 110. This information can be useful where you are
debugging LAN applications. The following statements must be in the
CONFIG.SYS file before you can use the system trace utility:
- TRACEBUF=63
- TRACE=ON 164, 110
You can then use TRACEFMT to produce a file containing the trace information.
After you have successfully saved the system trace information into a file,
you can use DTF2 or DTF3 to format the LAN trace data into a readable format.
For more information on TRACEFMT, type TRACEFMT on the command line. Then
select HELP from the action bar.
Note: When using OS/2 TRACEFMT, you must save the output as formatted.
o The MCL utility program displays current microcode level information for IBM
Token-Ring Network adapters. MCL outputs the microcode level and adapter
address of up to four token ring adapters. This utility provides a quick way
to determine the microcode level, as well as the universal and encoded
adapter addresses for IBM Token Ring adapters. 802.2 support (LANDD.OS2) is
required for this program.
o SNIFFLE is a standalone utility that is intended to aid in the development of
network information files (NIFs). Invoked against one or more NIFs, SNIFFLE
ensures that the NIF sections, keywords, and values are consistent both with
the extended NIF format definition and with each other. For more information
on the extended NIF format definition, see the IBM OS/2 NDIS Driver
Implementation Package. If an error is detected, SNIFFLE indicates the
location of the error and provides a description of the error condition.
An example of its use for the IBMTOK.NIF would be to type the following at an
OS/2 command prompt:
SNIFFLE IBMTOK.NIF
These utilities are not a formal part of the Multi-Protocol Transport Services
- AnyNet for OS/2 product and are not supported by IBM. They are provided on an
"AS-IS" BASIS WITHOUT WARRANTY OF ANY KIND, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE WHICH ARE EXPRESSLY
DISCLAIMED.
See the README.UTL file in the APPLETS subdirectory on the MPTS Utilities
diskette for additional information about these utilities.
ΓòÉΓòÉΓòÉ 4.3. Logging Utilities ΓòÉΓòÉΓòÉ
Logging utilities include:
o LANTRAN.LOG
Information about the initialization of a LAN workstation is logged in
LANTRAN.LOG each time the workstation is started. Procedures for using this
tool are provided in Using LANTRAN.LOG.
Note: When FFST/2 is enabled, the same information is also logged to the
FFST/2 message log.
o LAPSHIST.LOG
Historical information about installation and configuration events are
recorded in LAPSHIST.LOG. Procedures for using this tool are provided in
Using LAPSHIST.LOG.
o FFST/2 message log
The FFST/2 message log offers a Presentation Manager* interface to messages
logged by LAPS. Procedures for using this tool are provided in the
documentation of the product that installed FFST/2.
ΓòÉΓòÉΓòÉ 4.3.1. Using LANTRAN.LOG ΓòÉΓòÉΓòÉ
Information about the initialization of a LAN workstation is logged in a text
file, called LANTRAN.LOG, each time the workstation is started. Whenever an
event occurs, the appropriate message is placed in the LANTRAN.LOG file as a
record of that event.
ΓòÉΓòÉΓòÉ 4.3.1.1. Preliminary Considerations ΓòÉΓòÉΓòÉ
Read the following information before attempting to use LANTRAN.LOG:
o Each time a system is restarted, the LAN network adapter drivers write over
the old LANTRAN.LOG file, thereby creating a new file. The information in
the new file pertains only to the time period since the system was restarted.
Most messages are logged during initialization; however, messages can be
appended to the LANTRAN.LOG at any time until the system is shut down or
restarted.
o LANTRAN.LOG is written to the subdirectory that is specified by the /I
parameter of the DEVICE= statement for LANMSGDD.OS2 in the CONFIG.SYS file.
Normally this will be the C:\IBMCOM directory. The following example:
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
would cause LANTRAN.LOG to be written to C:\IBMCOM. Normally, the /I
parameter, which is mainly to specify the location of LANTRAN.LOG, is added
to the DEVICE= statement during LAPS installation. If no /I parameter is
specified in the CONFIG.SYS file, LANTRAN.LOG is written to the root
directory of the boot drive.
o The /I parameter is also used to identify where the message files are found.
Note: If the /I parameter is omitted, the default is assumed.
o Other parameters that may be specified on the DEVICE= statement for
LANMSGDD.OS2 include:
/P Disables the pause-on-error function during initialization. The user
is not prompted with Press any key to continue following an error
message.
/S Turns off the message display option. Messages are not displayed on
the screen, but they are still logged.
o Most of the messages logged in the LANTRAN.LOG file are status messages
indicating, for example, that the drivers:
- Are attempting to install your workstation on a LAN. The following is an
example of such a message:
Accessing IBM Token-Ring Local Area Network. Please wait.
or
- Have initialized a particular adapter. The following is an example of
such a message:
Adapter 0 is initialized and opened successfully.
However, if your workstation is unable to use LAN communications, error
messages can be logged in the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 4.3.1.2. Accessing or Printing LANTRAN.LOG ΓòÉΓòÉΓòÉ
LANTRAN.LOG is an ASCII text file that can be displayed using the OS/2 TYPE
command. For systems attached to a printer, this file can be printed using the
OS/2 PRINT command.
ΓòÉΓòÉΓòÉ 4.3.2. Using LAPSHIST.LOG ΓòÉΓòÉΓòÉ
LAPSHIST.LOG contains a historical record of installation and configuration
events as they occur.
ΓòÉΓòÉΓòÉ 4.3.2.1. Accessing or Printing LAPSHIST.LOG ΓòÉΓòÉΓòÉ
LAPSHIST.LOG is an ASCII text file that can be displayed using the OS/2 TYPE
command. For systems attached to a printer, this file can be printed using the
OS/2 PRINT command.
ΓòÉΓòÉΓòÉ 5. Tools for Advanced Problem Determination for MPTS ΓòÉΓòÉΓòÉ
MPTS uses the OS/2 system trace utility to record events.
This chapter contains the following information about using the OS/2 system
trace utility:
o Describing the system trace utility and explaining related options and other
preliminary considerations and preparations
o Providing a recommended procedure for collecting and formatting system trace
information
ΓòÉΓòÉΓòÉ 5.1. Using the OS/2 System Trace Utility ΓòÉΓòÉΓòÉ
Use the OS/2 system trace utility to record system events.
Read the information that follows before attempting to use the system trace
utility:
o The system trace utility should be used only as directed in this guide or by
an IBM Support Center representative.
o Only procedural information is presented in this chapter. For information on
diagnosing specific problems, see Error Messages.
o This utility does not analyze information; it collects data into a trace
buffer in memory. The data can be retrieved later for analysis using the
TRACEFMT command. After you format this data, copy it to a diskette.
o Minimum system activity is recommended when using this utility.
o Do not send IBM information that is considered to be confidential or
proprietary by you or the end user.
ΓòÉΓòÉΓòÉ 5.1.1. Using System Trace Commands ΓòÉΓòÉΓòÉ
To enable tracing for MPTS, you must specify a value for the protocol driver
parameters listed in LAPS Trace Parameters. See the Multi-Protocol Transport
Services - AnyNet for OS/2: Configuration Guidefor additional information
about the MPTS protocol driver parameters, and see the IBM Local Area Network
Technical Reference for additional information about tracing network
activities.
┤БББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЖ
В Table 1. LAPS Trace Parameters В
╙БББББББББББББББББББББББББББББББББББББББББББББСБББББББББББББББББББББББББББББББББББББЙ
В PROTOCOL DRIVER В PROTOCOL DRIVER PARAMETER В
╙БББББББББББББББББББББББББББББББББББББББББББББТБББББББББББББББББББББББББББББББББББББЙ
В IBM IEEE 802.2 В 802 trace level В
╙БББББББББББББББББББББББББББББББББББББББББББББТБББББББББББББББББББББББББББББББББББББЙ
В IBM NetWare** Requester Support В Trace support В
╙БББББББББББББББББББББББББББББББББББББББББББББТБББББББББББББББББББББББББББББББББББББЙ
В IBM OS/2 NETBIOS В NETBIOS trace level В
БББББББББББББББББББББББББББББББББББББББББББББ╔БББББББББББББББББББББББББББББББББББББД
The system trace utility requires the presence of one or both of the following
statements in the CONFIG.SYS file:
o TRACE=
o TRACEBUF=
After the TRACE= or TRACEBUF= statement is active in the CONFIG.SYS file, the
system trace utility is controlled from the command line by the following
commands:
o TRACE ON
o TRACE OFF
o TRACEFMT
ΓòÉΓòÉΓòÉ 5.1.1.1. Modifying the CONFIG.SYS File for Trace ΓòÉΓòÉΓòÉ
Check your operating system documentation for directions about editing the
CONFIG.SYS file and for details about its contents. Considerations for using
system trace commands follow.
Note:
1. Whenever you change the CONFIG.SYS file, you must restart your system to
make the changes become effective.
2. When used in the CONFIG.SYS file, the equal sign (=) cannot be immediately
preceded or followed by a blank space.
To enable system tracing, either the TRACE= or TRACEBUF= statement must be in
the CONFIG.SYS file. If neither a TRACEBUF= nor a TRACE= statement is included
in the CONFIG.SYS file, an error message is received when an attempt to start
TRACE is made.
o The TRACE= statement
TRACE= can be set to ON or OFF. For normal operating circumstances, a
TRACE=OFF statement is recommended; the presence of this statement in the
CONFIG.SYS file without a TRACEBUF= statement allows the trace buffer a
default size of 4KB. Syntax for the TRACE= statement is shown in the
following figure.
Parameters
OFF Prevents system tracing of specified events.
ON Permits system tracing of specified events.
x A number from 0 through 255, indicating the major event code to
be traced or not to be traced. The numbers for these codes are
supplied by the IBM Support Center. More than one major event
code may be specified by separating event code numbers using a
comma.
Events are traced in both IBM PC-DOS and OS/2 modes. If no events are listed
after the ON or OFF parameter, ON indicates that all events are traced and
OFF indicates that no events are traced.
TRACE statements are processed in the order in which they are listed in the
TRACE= command. Their effects are cumulative. If any part of a statement is
incorrect, the statement is ignored.
Note: Including the TRACE=ON statement in the CONFIG.SYS file can slow
system performance. To avoid this type of problem, add the TRACE=ON x
statement only when you need to gather information on problems that
occur during system initialization.
o The TRACEBUF= statement
Use the TRACEBUF= statement to specify the system trace buffer size. The
TRACEBUF=x statement allocates the size of the trace buffer, where x is the
size in 1KB increments up to 63KB. Syntax for the TRACEBUF= statement is
shown in the following figure.
The TRACEBUF= statement sets the size of the circular trace buffer.
Parameter
x A number from 1 through 63, representing a multiple of 1024
bytes (1KB).
For example, to increase the size of the trace buffer to 10KB, include this
statement in your CONFIG.SYS file:
TRACEBUF=10
Note:
1. THE TRACEBUF= statement allocates buffer space. It does not enable the
tracing of events. For normal operations, a 4KB trace buffer is usually
adequate. To specify this size, include a TRACE=OFF statement in the
CONFIG.SYS file, but omit the TRACEBUF= statement.
2. The system trace utility employs a buffer-wrap algorithm when writing
data to the trace buffer. The buffer wraps when full, storing new data
at the start of the buffer; old data is overwritten.
ΓòÉΓòÉΓòÉ 5.1.1.2. System Trace Command-Line Statements ΓòÉΓòÉΓòÉ
After enabling the system trace utility within the CONFIG.SYS file and
specifying the appropriate LAPS trace parameter, use the following commands to
control tracing:
o Activating a trace and specifying major event codes
- If you specified TRACE=ON in the CONFIG.SYS file, the system trace utility
is already operating. To have the LAPS major event code (164), and
Multi-Protocol Transport Services major code (110) traced, type the
following statement at the command line:
TRACE ON 164, 110
Note: The equal sign is not used in the TRACE command-line statements.
- If you specified TRACE=OFF or TRACEBUF= in the CONFIG.SYS file, you must
activate the system trace utility using the TRACE ON x command.
o Stopping a trace
- To stop all traces, type the following statement at the command line:
TRACE OFF
- To selectively stop the LAPS trace without affecting other active traces,
type the following statement at the command line:
TRACE OFF 164, 110
- Clearing a trace buffer
To clear a trace buffer, type the following command at the command prompt:
TRACE /C
- Formatting trace records
Use the TRACEFMT command to format the contents of the trace buffer. This
external command takes a snapshot of the contents of the system trace
buffer at the time TRACEFMT is requested, formats each trace record, and
sends the formatted data to standard output. TRACEFMT can be used:
o While a system trace is active
o As many times as required to diagnose a problem, without having to
restart the system or respecify the major event codes
Output can be redirected to a file or a printer. Specify the command:
TRACEFMT
and a full-screen interface prompts you for the file name or printer to
direct the output to.
If you specify to save the formatted records to a file, you can use the
file as input to the DTF2 utility program. See Additional Utilities to
Assist You with MPTS Problems for additional information.
Note: The TRACEFMT command does not turn off the trace. You can invoke this
command as many times as required to diagnose the problem.
ΓòÉΓòÉΓòÉ 5.1.2. Recommended Procedure for Collecting and Formatting System Trace Information ΓòÉΓòÉΓòÉ
This procedure applies to most cases when you should use the system trace
utility. Exceptions can be specified by an IBM Support Center representative.
If you want to change the trace or trace buffer defaults or make changes to the
CONFIG.SYS file, stop and restart your system.
Note: Starting your system erases all previously saved trace information.
The recommended place to start a system trace is from the OS/2 command line.
To start a system trace:
1. Start an OS/2 session and begin the trace; at the OS/2 command line, type:
TRACE ON 164, 110
and press Enter.
2. Switch to the application that is experiencing the problem and attempt to
re-create the problem.
3. After the problem occurs, switch back to the OS/2 command line where the
trace was activated and stop the trace by typing:
TRACE OFF
and pressing Enter.
4. To capture the contents of the trace buffer, at the OS/2 command prompt,
type:
TRACEFMT
and press Enter.
The contents of the trace buffer are displayed. You can redirect it to a file
or a printer. Specify the command:
TRACEFMT
and a full-screen interface prompts you for the file name or printer to direct
the output to.
If you specify to save the formatted records to a file, you can use the file as
input to the DTF2 utility program. See Additional Utilities to Assist You with
MPTS Problems for additional information.
Note: The TRACEFMT command does not turn off the trace. You can invoke this
command as many times as required to diagnose the problem.
ΓòÉΓòÉΓòÉ 5.1.2.1. Samples of Formatted Trace Events ΓòÉΓòÉΓòÉ
The following code is a sample of formatted trace events for 32-bit operating
systems.
For 32-bit operating systems:
EVENT# Н0004┘ PID Н0000┘MAJOR НA4┘ MINOR Н0049┘ LENGTH Н0020┘
TIME: 41.52
18 40 FF FF FF FF FF FF 90 00 5A A8 84 5D 8C 30 E5 81 CE E1 BB 21 CE F1
EF 40 E0 E0 03 FF FF 00
EVENT# Н0005┘ PID Н0000┘MAJOR НA4┘ MINOR Н0049┘ LENGTH Н0020┘
TIME: 41.55
18 40 FF FF FF FF FF FF 90 00 5A A8 84 5D 8C 30 E5 81 CE 51 BB 11 CE 61
EF 40 E0 E0 03 FF FF 00
ΓòÉΓòÉΓòÉ 5.1.2.2. When You Complete This Procedure ΓòÉΓòÉΓòÉ
If you have been directed to complete other problem determination procedures,
refer to the directions to complete those procedures.
When you have completed all appropriate procedures, complete the Problem Report
Form describing the problem.
Note: Information should be sent to IBM for analysis only upon direction from
the IBM Support Center. Also, do not send IBM information that is
considered to be confidential or proprietary by you or the end user.
ΓòÉΓòÉΓòÉ 6. Error Messages ΓòÉΓòÉΓòÉ
This chapter contains messages generated by LAPS and Socket/MPTS. The messages
are listed in alphabetical order. The alphabetic-character prefix indicates the
component that issued the message. Components That Issue Messages lists the
components that issue messages.
┤ББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЖ
В Table 2. Components That Issue Messages В
╙ББББББББББББББББСБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В MESSAGE PREFIX В COMPONENT В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В ETH В IBM PS/2* Adapter for Ethernet Networks driver В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В LT В LAPS В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В В 3Com 3C503 EtherLink** II Adapter driver or В
В В 3Com 3C523 EtherLink/MC Adapter driver В
В ╙БББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В MAC В Standard Microsystems** EtherCard PLUS** Micro Channel* В
В В Adapter driver or В
В В Standard Microsystems EtherCard PLUS Software-Configured В
В В Adapter driver В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В MPT В Multi-Protocol Transport Services В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В PRO В Protocol Manager В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В UBI В Ungermann-Bass** NIU**pc Adapter driver or В
В В Ungermann-Bass NIUps Adapter driver В
╙ББББББББББББББББТБББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В XI0 В LAPS В
╙ББББББББББББББББ╔БББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЙ
В NOTES: Online message help is not available for the 3Com network adapter В
В drivers. В
В В
В Where Western Digital Corporation was mentioned in previous releases of LAPS В
В documentation, Standard Microsystems Corporation now provides that support. В
ББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББД
For the following messages, variable data such as file names or drive letters
are represented with one or more Xs.
ΓòÉΓòÉΓòÉ 6.1. ETH0001 ΓòÉΓòÉΓòÉ
The IBM Ethernet adapter was either not found or not specified in the
PROTOCOL.INI file.
There were either no entries found in the PROTOCOL.INI file for this device
driver, the adapter is not installed, or there is a hardware problem with the
adapter.
Ensure that an IBM Ethernet adapter is installed in this system, and that a
DRIVERNAME= entry exists in the PROTOCOL.INI file for the MACETH$ or MACETH2$
device driver. Retry the operation. If the problem persists, contact your
vendor service representative.
ΓòÉΓòÉΓòÉ 6.2. ETH0003 ΓòÉΓòÉΓòÉ
Multiple IBM Ethernet adapter parameters were specified in the PROTOCOL.INI
file.
More than one entry was found in the PROTOCOL.INI file for the MACETH$ or
MACETH2$ device driver.
Ensure that DRIVERNAME entry appears only once in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.3. LT00003 ΓòÉΓòÉΓòÉ
IBM LANDD: A failure occurred during initialization.
An initialization error has been reported, which has caused the device driver
not to install.
Check the FFST/2 message log if you are using FFST/2 or the LANTRAN.LOG file to
identify the specific condition that caused the failure. A message detailing
the condition that caused initialization failure displays on the screen before
this message.
ΓòÉΓòÉΓòÉ 6.4. LT00006 ΓòÉΓòÉΓòÉ
The protocol manager could not be opened. The return code is X.
This message will be displayed when the system service DosOpen request to the
PROTMAN.OS2 device driver fails for any reason. This can also happen when
another device driver has opened PROTMAN with exclusive rights and has failed
to close it.
Check your CONFIG.SYS file and ensure that the PROTMAN.OS2 device driver is
active. For additional information about the return code displayed with the
message for a specific cause, type HELP nnnn from the OS/2 command prompt.
ΓòÉΓòÉΓòÉ 6.5. LT00007 ΓòÉΓòÉΓòÉ
The protocol manager would not accept a request.
The protocol manager failed to honor a request from this protocol stack.
Check the FFST/2 message log if you are using FFST/2 or the LANTRAN.LOG file
for additional messages from the protocol manager that will indicate the cause
for failure. Correct the error and try the operation again.
ΓòÉΓòÉΓòÉ 6.6. LT00008 ΓòÉΓòÉΓòÉ
The protocol manager would not supply a configuration image.
The protocol manager did not honor the request for the configuration image.
Verify that the PROTOCOL.INI file exists and that it is valid; then retry the
operation.
ΓòÉΓòÉΓòÉ 6.7. LT00009 ΓòÉΓòÉΓòÉ
The protocol manager would not accept module registration.
An attempt to register the device name with the protocol manager was
unsuccessful.
Ensure that the bracketed names in the PROTOCOL.INI are unique and try the
operation again.
ΓòÉΓòÉΓòÉ 6.8. LT00011 ΓòÉΓòÉΓòÉ
No MAC driver bindings were specified in the PROTOCOL.INI file. IBM LANDD did
not load.
There were no media access control (MAC) names specified on the BINDINGS=
statement in the IBM LANDD section of the PROTOCOL.INI file.
Correct the PROTOCOL.INI file to ensure that a valid MAC driver name is
specified on the BINDINGS= statement.
ΓòÉΓòÉΓòÉ 6.9. LT00012 ΓòÉΓòÉΓòÉ
There are too many MAC drivers to bind. IBM LANDD did not load.
The number of media access control (MAC) drivers specified on the BINDINGS=
statement in the PROTOCOL.INI file exceeds the maximum number of devices to
bind (MAXBIND).
Correct the PROTOCOL.INI file to ensure that the number of MAC names specified
in the BINDINGS= statement does not exceed 16.
ΓòÉΓòÉΓòÉ 6.10. LT00013 ΓòÉΓòÉΓòÉ
There are more values specified for keyword X than allowed. IBM LANDD did not
load.
Each value for a keyword in the PROTOCOL.INI file represents a configuration
parameter for a media access control (MAC) device driver. The maximum number
of MAC drivers allowed is determined by the value specified for the MAXBIND
parameter or defaults to 16.
Correct the PROTOCOL.INI file to ensure that the number of values for the
keyword is less than or equal to the maximum number of MAC drivers allowed.
Check your release information for the number of adapters supported by this
system.
ΓòÉΓòÉΓòÉ 6.11. LT00014 ΓòÉΓòÉΓòÉ
System resources are not available to hold the current parameter configuration
in PROTOCOL.INI. IBM IEEE 802 (LANDD) did not load.
Either the sum of the configuration parameters require more than 64KB, or there
is not enough memory to allocate the necessary storage for the device driver.
If this is a 286 processor system, the sum of all of the configuration
parameters must fit in 64KB. If this is a 386 or higher processor system, all
parameters except the links and timer control blocks must fit in 64KB.
Refer to your network planning and administration guides for additional
information about suggested values. Reduce the resources required by changing
the PROTOCOL.INI file, or add more memory, and try the operation again.
ΓòÉΓòÉΓòÉ 6.12. LT00015 ΓòÉΓòÉΓòÉ
The value specified as the node address for MAC X is not a valid hexadecimal
number.
The node address specified must be a hexadecimal number. An incorrect
hexadecimal character was specified in the node address value.
Change the NETADDRESS parameter in the PROTOCOL.INI file to ensure that the
value is correct. Hexadecimal numbers can consist of the digits 0 through 9
only and the letters A through F (uppercase or lowercase).
ΓòÉΓòÉΓòÉ 6.13. LT00016 ΓòÉΓòÉΓòÉ
The value specified for the node address is not valid for adapter X. IBM LANDD
did not load.
The value specified for the node address (NETADDRESS) must be 12 hexadecimal
numbers in length. Hexadecimal numbers can consist of the digits 0 through 9
only and the letters A through F (uppercase or lowercase).
Correct the node address and try the operation again.
ΓòÉΓòÉΓòÉ 6.14. LT00017 ΓòÉΓòÉΓòÉ
The ETHERAND parameter configured for adapter X is not DIX or 802.3. IBM LANDD
did not load.
The parameter that identifies ETHERAND type in the PROTOCOL.INI file must be
configured for DIX or 802.3. This parameter is not configured correctly.
Either remove the ETHERAND type parameter from the PROTOCOL.INI file to allow
the value to default to 802.3, or change the parameter to reflect the
appropriate value. If the ETHERAND type is DIX, a D must be specified. If the
ETHERAND type is 802.3, an I (IEEE format) must be specified.
ΓòÉΓòÉΓòÉ 6.15. LT00018 ΓòÉΓòÉΓòÉ
The unrecognized keyword X was found in PROTOCOL.INI.
A keyword was found in the PROTOCOL.INI file that is not recognized as a valid
parameter.
Review the PROTOCOL.INI file to locate the incorrect parameter. Correct or
delete the unrecognized keyword and try the operation again.
ΓòÉΓòÉΓòÉ 6.16. LT00020 ΓòÉΓòÉΓòÉ
A value is required for keyword X in the PROTOCOL.INI.
The keyword specified has required parameters. No parameter values were found
for this keyword.
Add the proper value to the keyword and try the operation again.
ΓòÉΓòÉΓòÉ 6.17. LT00021 ΓòÉΓòÉΓòÉ
The value specified for parameter X is not valid.
The value provided for the parameter is not the correct type or is not a valid
value.
Change the value for the parameter in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.18. LT00022 ΓòÉΓòÉΓòÉ
The value specified for parameter X is not valid.
The value specified for the parameter is either larger than the maximum allowed
or smaller than the minimum allowed for that parameter.
Correct the value specified and try the operation again.
ΓòÉΓòÉΓòÉ 6.19. LT00023 ΓòÉΓòÉΓòÉ
Duplicate parameter X was found in the PROTOCOL.INI.
The parameter occurred more than once in the PROTOCOL.INI file. Only one
occurrence of the parameter is allowed.
Change the PROTOCOL.INI file so that it contains only one reference to the
parameter and try the operation again.
ΓòÉΓòÉΓòÉ 6.20. LT00025 ΓòÉΓòÉΓòÉ
The IBM LANDD section was not found in PROTOCOL.INI.
No section was found defining the parameters for the IBM LANDD device driver in
the PROTOCOL.INI file.
Insert a section in the PROTOCOL.INI file with the appropriate values for the
IBM LANDD device driver. Minimum entries are the module name, driver name, and
bindings statements.
ΓòÉΓòÉΓòÉ 6.21. LT00026 ΓòÉΓòÉΓòÉ
The LANMSGDD device driver could not be opened. The return code is X.
The message handling device driver is not installed or cannot be accessed.
Check the FFST/2 message log if you are using FFST/2 or the LANTRAN.LOG file
for a failure message. Check the CONFIG.SYS file to ensure that a DEVICE=
statement exists for LANMSGDD.OS2. For additional information about the return
code displayed with the message, type HELP nnnn from the OS/2 command prompt.
Correct the problem and try the operation again.
ΓòÉΓòÉΓòÉ 6.22. LT00027 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a SetTimer request.
The system service SetTimer returned an unsuccessful error code.
Try the operation again. If the error persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.23. LT00028 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a request to allocate GDT selectors. The
return code is X.
The device driver tried to allocate one or more GDT selectors and the system
service returned an unsuccessful error code.
Reduce the number of GDTs used by device drivers that install before LANDD.OS2.
It may be possible to do this by changing the configuration options in the
PROTOCOL.INI file for the drivers that install before LANDD.OS2, or it may be
necessary to change the CONFIG.SYS file so that LANDD.OS2 loads earlier. For
additional information about the return code displayed with the message, type
HELP nnnn from the OS/2 command prompt.
ΓòÉΓòÉΓòÉ 6.24. LT00029 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a request to map GDT selectors. The
return code is X.
The operating system could not map a physical address to a GDT
Try the operation again. For additional information about the return code
displayed with the message, type HELP nnnn from the OS/2 command prompt. If
the problem persists, note the message number and return code value and contact
your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.25. LT00030 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a PhysToVirt request. The return code is
X.
The operating system could not convert a physical address to a virtual LDT ring
three selector.
Try the operation again. For additional information about the return code
displayed with the message, type HELP nnnn from the OS/2 command prompt. If
the problem persists, note the message number and return code value and contact
your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.26. LT00031 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a PhysToVirt request.
The offset returned from the system service PhysToVirt request was not 0.
Try the operation again. If the problem persists, note the message number and
contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.27. LT00032 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a GetDOSVar request.
The address to the system global information segment is not valid.
Try the operation again. If the problem persists, note the message number and
contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.28. LT00033 ΓòÉΓòÉΓòÉ
The operating system installed is not compatible with this program.
This program requires that a compatible version of OS/2 be loaded in order to
run.
Refer to your documentation to determine the compatible OS/2 version and
install that version, or delete the IBM LANDD section from CONFIG.SYS.
ΓòÉΓòÉΓòÉ 6.29. LT00034 ΓòÉΓòÉΓòÉ
An unexpected error was returned when the program tried to lock a memory
segment.
The request to lock a memory segment failed because the segment was unavailable
or the lock handle was not valid.
Change the number of links or adapters being used to reduce memory usage and
try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.30. LT00035 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a VirtToPhys request.
The system service VirtToPhys returned an unsuccessful error code.
Try the operation again. If the problem persists, note the message number and
contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.31. LT00036 ΓòÉΓòÉΓòÉ
An unexpected error was returned when the program tried to allocate memory for
the group SAP receive buffer. The return code is X.
A system service request to allocate memory for the group SAP receive buffer
failed because the memory was not available.
Change the number of links or adapters being used to reduce memory usage and
try the operation again. For additional information about the return code
displayed with the message, type HELP nnnn from the OS/2 command prompt. If the
problem persists, contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.32. LT00037 ΓòÉΓòÉΓòÉ
An unexpected error was returned when the program tried to request a GDT for
the group SAP receive buffer.
The system has run out of GDT selectors.
Increase the available number of GDT selectors by changing the SELECTORS=
parameter in the PROTOCOL.INI file to a larger number. Try the operation
again.
ΓòÉΓòÉΓòÉ 6.33. LT00038 ΓòÉΓòÉΓòÉ
The system is unable to map the group SAP receive buffer to a GDT. The return
code is X.
The system could not map a physical address to a GDT selector because either
the physical address or the GDT is not valid.
Try the operation again. For additional information about the return code
displayed with the message, type HELP nnnn from the OS/2 command prompt. If
the problem persists, note the message number and the return code and contact
your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.34. LT00039 ΓòÉΓòÉΓòÉ
The X MAC is an 802.3 protocol but is configured for DIX.
The ETHERAND type specified for this adapter in the PROTOCOL.INI file is DIX,
but the MAC driver requires 802.3 frame formats.
Either remove the ETHERAND type parameter from the PROTOCOL.INI file to allow
the value to default to 802.3 or change the parameter to allow 802.3 frame
formats for this MAC.
ΓòÉΓòÉΓòÉ 6.35. LT00040 ΓòÉΓòÉΓòÉ
The X MAC is a DIX protocol but is configured for 802.3.
The ETHERAND type specified for this adapter in the PROTOCOL.INI file is 802.3,
but the MAC driver requires DIX frame formats.
Change the ETHERAND type keyword to allow DIX frame formats for this MAC. If
the parameter does not exist in the PROTOCOL.INI file, it must be created; the
default value for this parameter is 802.3.
ΓòÉΓòÉΓòÉ 6.36. LT00041 ΓòÉΓòÉΓòÉ
The X MAC will not accept the configured node address.
A node address (NETADDRESS) has been configured for a MAC driver that does not
support the SetStationAddress function.
Remove the node address statement from the PROTOCOL.INI file. Check the MAC
parameters to see if the node address can be configured directly through the
MAC driver.
ΓòÉΓòÉΓòÉ 6.37. LT00042 ΓòÉΓòÉΓòÉ
The X MAC was not able to bind. Return Code = X.
An unexpected error occurred when the protocol manager tried to bind to the MAC
driver.
Check for additional messages from the MAC driver indicating an error, and
check the bindings list in the PROTOCOL.INI file for an incorrect name.
Correct the error and try the operation again. If the condition persists,
contact your MAC vendor sales representative.
ΓòÉΓòÉΓòÉ 6.38. LT00043 ΓòÉΓòÉΓòÉ
An unexpected error occurred when the program tried to set the X MAC packet
filter.
IBM LANDD and NETBEUI require that the packet filter function be supported by
the MAC device driver. The MAC driver installed on this system does not
support the receiving of packets of the type requested.
Install a version of the MAC device driver that supports the required level of
function.
ΓòÉΓòÉΓòÉ 6.39. LT00044 ΓòÉΓòÉΓòÉ
An unexpected error occurred when the program tried to set the X MAC lookahead
size.
NDIS requires that MAC device drivers support a 256 byte lookahead buffer. An
error code was returned when the program tried to set this buffer size.
Install a version of the MAC device driver that supports the required level of
function.
ΓòÉΓòÉΓòÉ 6.40. LT00045 ΓòÉΓòÉΓòÉ
An error occurred when the program tried to set the X MAC node address.
The MAC device driver indicates that it will accept a user-defined node address
but is unable to process the request.
To use the burned-in address from the adapter, change the PROTOCOL.INI file to
remove the configured node address.
ΓòÉΓòÉΓòÉ 6.41. LT00046 ΓòÉΓòÉΓòÉ
IBM LANDD was unable to open the X MAC driver.
The unexpected error occurred when the program attempted to open the adapter
for the MAC device driver.
Check for additional messages from the MAC driver indicating an error. Try the
operation again. If the problem persists, contact your MAC vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.42. LT00047 ΓòÉΓòÉΓòÉ
IBM LANDD received an open adapter request before the X MAC bind completed.
An open adapter request was issued before the bind to the MAC driver was
successfully completed.
Change the CONFIG.SYS file to ensure that the RUN= statement exists for
NETBIND.EXE. This ensures that the bind process completes as quickly as
possible.
ΓòÉΓòÉΓòÉ 6.43. LT00049 ΓòÉΓòÉΓòÉ
Try the operation again. If the problem persists, contact your vendor sales
representative.
IBM LANDD encountered an internal error when the program attempted to reference
X MAC by the logical adapter number.
The high-memory GDT selector for this MAC could not be found in the logical MAC
cross-reference array. Binding to this MAC will fail.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.44. LT00050 ΓòÉΓòÉΓòÉ
Duplicate node addresses exist on the network for X MAC.
The node address specified in the PROTOCOL.INI file already exists on the
network. Each node address must be unique for the network.
Either change the node address for this MAC device driver to be a unique
address or locate the other system with the same node address specified in the
PROTOCOL.INI file and change that node address. Try the operation again.
ΓòÉΓòÉΓòÉ 6.45. LT00055 ΓòÉΓòÉΓòÉ
An unexpected error was returned when the program tried to transmit the
duplicate node address test. The X MAC return code is X.
LANDD received an unexpected return code when trying to transmit the duplicate
node address test.
Correct the error and try the operation again. If the condition persists,
contact your MAC vendor sales representative.
ΓòÉΓòÉΓòÉ 6.46. LT00056 ΓòÉΓòÉΓòÉ
The OpenAdapter request to the X MAC driver did not complete within the
required time limit.
The OpenAdapter request made to the MAC driver did not complete within the
specified time limit.
Check the adapters for possible hardware conflicts and try the operation again.
If the condition persists, contact your MAC vendor sales representative.
ΓòÉΓòÉΓòÉ 6.47. LT00060 ΓòÉΓòÉΓòÉ
An error occurred while attempting to load NETBEUI.
An error occurred during device driver initialization. This error is
preventing the device driver from installing properly.
Check for additional messages indicating a specific problem. Correct that
problem and try the operation again.
ΓòÉΓòÉΓòÉ 6.48. LT00061 ΓòÉΓòÉΓòÉ
There is no section for NETBEUI in PROTOCOL.INI.
There are no configuration parameters defined for NETBEUI in the PROTOCOL.INI
file.
Change the PROTOCOL.INI file to add a section of configuration information for
NETBEUI. The minimum statements required for this section are MODULENAME=,
DRIVERNAME=, and BINDINGS=. Try the operation again.
ΓòÉΓòÉΓòÉ 6.49. LT00064 ΓòÉΓòÉΓòÉ
A version of the redirector was detected that is not compatible with the
version of NETBIOS X.
An incompatible version of the redirector is installed on this system. NetBIOS
will not run with this version.
Install the proper version of the redirector and try the operation again.
ΓòÉΓòÉΓòÉ 6.50. LT00065 ΓòÉΓòÉΓòÉ
The configuration parameters defined in PROTOCOL.INI exceed the 64KB work area.
NETBIOS X support has ended.
The area needed to hold the configuration defined in the PROTOCOL.INI file is
larger than the maximum allowable size. The sum of the configuration
parameters exceeds 64KB.
Refer to your network planning and administration guides for additional
information about suggested values. Reduce the SESSIONS, NAMES, and COMMANDS
statements in the PROTOCOL.INI file or use the default values; then retry the
operation.
ΓòÉΓòÉΓòÉ 6.51. LT00071 ΓòÉΓòÉΓòÉ
The default path is not valid. The default directory will be changed to the
root directory.
The path \IBMCOM or the default override path specified on the DEVICE=
statement in CONFIG.SYS for the message device driver is not valid.
Change the DEVICE= statement in the CONFIG.SYS file to an existing path or
create the directory specified as the path. Re-IPL the system and try the
operation again.
ΓòÉΓòÉΓòÉ 6.52. LT00072 ΓòÉΓòÉΓòÉ
An error occurred while attempting to open or write to file X. Check for
insufficient disk space.
An error occurred when the program tried to open or write from the message
device driver.
Check the root directory and ensure that adequate space exists for the
operation. Try the operation again.
ΓòÉΓòÉΓòÉ 6.53. LT00073 ΓòÉΓòÉΓòÉ
FFST/2 is installed but is not initialized. LANTRAN.LOG is being created.
FFST/2 was unable to initialize properly and cannot be used to handle messages.
An ASCII file named LANTRAN.LOG is being created to hold messages. This file
may be viewed or printed using OS/2 commands.
No action is required. If logging to FFST/2 is desired, include a
RUN=d:\OS2\EPW statement in the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.54. LT00081 ΓòÉΓòÉΓòÉ
The IBM LANDD device driver is not installed.
The IBM LANDLLDD was not able to open or attach to the IBM LANDD device driver.
Change the CONFIG.SYS file to ensure that the DEVICE= statements exist for both
LANDLLDD and LANDD and that the LANDD statement is specified first. Retry the
operation. If the problem persists, re-install the device drivers.
ΓòÉΓòÉΓòÉ 6.55. LT00082 ΓòÉΓòÉΓòÉ
An unexpected error was returned from an AllocPhys request.
The system service AllocPhys returned an unsuccessful error code to the
program.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.56. LT00083 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a DosGetInfoSeg request.
The system service DosGetInfoSeg returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.57. LT00084 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a PhysToGDT request.
The system service PhysToGDT returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.58. LT00086 ΓòÉΓòÉΓòÉ
IBM OS/2 LANDLLDD is not installed.
The program was unable to open the IBM LANDLLDD device driver.
Check the CONFIG.SYS file to ensure that the DEVICE= statement exists for
LANDLLDD. Retry the operation. If the problem persists, reinstall the device
driver.
ΓòÉΓòÉΓòÉ 6.59. LT00087 ΓòÉΓòÉΓòÉ
IBM OS/2 LANDLLDD: There is not enough memory available for CCB3 areas.
There is not adequate memory for LANDLLDD to run properly.
There are three actions that might fix this error:
o Add additional memory to this system.
o Reduce the number of active applications and devices.
o Reconfigure the MAC parameters to reduce resource requirements.
ΓòÉΓòÉΓòÉ 6.60. LT00090 ΓòÉΓòÉΓòÉ
Adapter X: NETBIOS is not operational.
There are not enough system resources for NetBIOS to continue running. Refer
to the message log for total resources currently allocated for all NetBIOS
applications.
To resolve the problem, increase the resource requirements (SESSIONS=, NAMES=,
and COMMANDS=) in the PROTOCOL.INI file. Try the operation again.
ΓòÉΓòÉΓòÉ 6.61. LT00091 ΓòÉΓòÉΓòÉ
No configuration section was found in the PROTOCOL.INI file for either NETBIOS
or NETBEUI.
NetBIOS requires the presence of either a NETBEUI or NETBIOS section in the
PROTOCOL.INI file.
Ensure that the configuration parameters are present in the PROTOCOL.INI file
for either NetBIOS or NETBEUI or both; then retry the operation. If the
NetBIOS API is not needed, remove the DEVICE= statement for NETBIOS.OS2 from
the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.62. LT00092 ΓòÉΓòÉΓòÉ
NETBIOS does not recognize device driver X.
The device driver specified is not valid. The specified device driver may not
be compatible with the network adapter or the version may not be supported.
Install a supported version of the device driver and retry the operation.
ΓòÉΓòÉΓòÉ 6.63. LT00093 ΓòÉΓòÉΓòÉ
An error occurred when the program tried to open network device driver X.
NetBIOS could not open the device driver.
Change the CONFIG.SYS file to ensure that the DEVICE= statement exists and
contains the correct path and name for the device driver. Ensure that the
device driver entry is before the NETBIOS.OS2 entry. Retry the operation.
ΓòÉΓòÉΓòÉ 6.64. LT00094 ΓòÉΓòÉΓòÉ
A syntax error was detected for ADAPTER X in the NETBIOS section of
PROTOCOL.INI.
The NetBIOS section of the PROTOCOL.INI file contains an error on the line
specified by the adapter number.
Specify a valid adapter line and try the operation again.
The following is the syntax of the adapter line in the NETBIOS section:
ADAPTER# = Driver,Adp,Sess,NCBs,Names
Where:
# - Digit to be used as the NETBIOS API NCB adapter number.
Driver - String specifying the driver name that NETBIOS will bind to.
Adp - Digit adapter number that NETBIOS uses to bind to the Driver.
Sess - Digit specifying Sessions requested for the NETBIOS API.
NCBs - Digit specifying NCBs requested for the NETBIOS API.
Names - Digit specifying Names requested for the NETBIOS API.
ΓòÉΓòÉΓòÉ 6.65. LT00095 ΓòÉΓòÉΓòÉ
No MAC driver bindings were specified in PROTOCOL.INI. IBM NETBEUI did not
load.
There were no media access control (MAC) names specified on the BINDINGS=
statement in the IBM NETBEUI section of the PROTOCOL.INI file.
Correct the PROTOCOL.INI file to ensure that a valid MAC driver name is
specified on the BINDINGS= statement.
ΓòÉΓòÉΓòÉ 6.66. LT00096 ΓòÉΓòÉΓòÉ
There are too many MAC drivers to bind. IBM NETBEUI did not load.
The number of media access control (MAC) drivers specified on the BINDINGS=
statement in the PROTOCOL.INI file exceeds the maximum number of devices to
bind (MAXBIND).
Correct the PROTOCOL.INI file to ensure that the number of MAC names specified
in the BINDINGS= statement does not exceed 12.
ΓòÉΓòÉΓòÉ 6.67. LT00097 ΓòÉΓòÉΓòÉ
System resources are not available to hold the current parameter configuration
in PROTOCOL.INI. IBM NETBEUI did not load.
Either the sum of the configuration parameters require more than 64KB, or there
is not enough memory to allocate the necessary storage for the device driver.
If this is a 286 processor system, the sum of all of the configuration
parameters must fit in 64KB. If this is a 386 or higher processor system, all
parameters except the link and session control blocks must fit in 64KB.
Refer to your network planning and administration guides for additional
information about suggested values. Reduce the resources required by changing
the PROTOCOL.INI file, or add more memory, and try the operation again.
ΓòÉΓòÉΓòÉ 6.68. LT00098 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a request to allocate GDT selectors. The
return code is X.
The device driver tried to allocate one or more GDT selectors and the system
service returned an unsuccessful error code.
Reduce the number of GDTs used by device drivers that install before
NETBEUI.OS2. It may be possible to do this by changing the configuration
options in the PROTOCOL.INI file for the drivers that install before
NETBEUI.OS2, or it may be necessary to change the CONFIG.SYS file so that
NETBEUI.OS2 loads earlier. For additional information about the return code
displayed with the message, type HELP nnnn from the OS/2 command prompt. If
the problem persists, reduce the number of GDT selectors specified in the
NETBEUI section of the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.69. LT00099 ΓòÉΓòÉΓòÉ
The operating system installed is not compatible with this program.
This program requires a compatible version of OS/2 in order to run.
Check your documentation and install the proper version of OS/2 and try the
operation again, or delete the IBM NETBEUI section from CONFIG.SYS.
ΓòÉΓòÉΓòÉ 6.70. LT00100 ΓòÉΓòÉΓòÉ
The value specified for the node address is not valid for adapter X. IBM
NETBEUI did not load.
The value specified for the node address (NETADDRESS) must contain 12
hexadecimal numbers. Hexadecimal numbers can consist of the digits 0 through 9
and the letters A through F (uppercase or lowercase).
Correct the node address and try the operation again.
ΓòÉΓòÉΓòÉ 6.71. LT00101 ΓòÉΓòÉΓòÉ
More values than allowed are specified for keyword X. IBM NETBEUI did not load.
The value for the keyword in the PROTOCOL.INI file represents a configuration
parameter for a media access control (MAC) device driver. The maximum number
of MAC drivers allowed is 12.
Correct the PROTOCOL.INI file to ensure that the number of values for the
keyword is less than or equal to the maximum number of MAC drivers allowed.
ΓòÉΓòÉΓòÉ 6.72. LT00200 ΓòÉΓòÉΓòÉ
An error occurred while updating the following file:
X
Make sure that this file is not in use in any other OS/2 or DOS session.
Return to this session and select Retry to continue configuration.
Select Exit if you want to end configuration.
An OS/2 error occurred while updating the specified file. The file was not
updated.
Switch to another OS/2 session and make sure the file is not in use by another
session. Select Retry to perform the operation again.
For additional information, see the FFST/2 message log if you are using FFST/2
or the LANTRAN.LOG file.
Select Cancel to return to the window displayed before the update error
occurred.
If you cannot correct the error, select Exit to return to the
installation/configuration program.
ΓòÉΓòÉΓòÉ 6.73. LT00201 ΓòÉΓòÉΓòÉ
An error occurred while reading the following file:
X
Make sure that this file is not in use in any other OS/2 or DOS session.
Return to this session and select Retry to continue configuration.
Select Exit if you want to end configuration.
An OS/2 error occurred while attempting to read the specified file. The file
could not be read.
Switch to another OS/2 session and make sure the file is not in use by another
session. Select Retry to perform the operation again.
For additional information, see the FFST/2 message log if you are using FFST/2
or the LANTRAN.LOG file.
Select Cancel to return to the previous window. (Cancel is not available for
some configurations.)
If you cannot correct the error, select Exit to return to the installation or
configuration program.
ΓòÉΓòÉΓòÉ 6.74. LT00202 ΓòÉΓòÉΓòÉ
An error occurred while copying from subdirectory:
X
to subdirectory:
X
Make sure that files being copied are not in use in either of these
subdirectories in any other OS/2 or DOS session.
Return to this session and select Retry to continue configuration.
Select Exit if you want to end configuration.
An OS/2 error occurred while copying the specified file to the specified
subdirectory.
Switch to another OS/2 session and verify that the file is not in use by
another session. Select Retry to perform the operation again.
For additional information, see the FFST/2 message log if you are using FFST/2
or the LANTRAN.LOG file.
Select Ignore to continue.
Select Cancel to return to the previous window.
If you cannot correct the error, select Exit to return to the
installation/configuration program.
ΓòÉΓòÉΓòÉ 6.75. LT00203 ΓòÉΓòÉΓòÉ
The value for the X field must be between X and X. (or) The value for the X
field must be one of the following: (or) The value for the X field must be
between X and X in steps of X. (or) The length of the X field cannot be longer
than X characters.
The value in an entry field is out of range.
Select OK to close this message and return to the field indicated by the
cursor. Type the correct information as indicated by the message. For more
information, press F1 on that field to display help information for the field.
ΓòÉΓòÉΓòÉ 6.76. LT00204 ΓòÉΓòÉΓòÉ
The PROTOCOL.INI file was not found at the path specified.
Select OK and re-specify the full path.
An incorrect or incomplete path was typed in the Path field in the Select
Default PROTOCOL.INI File window.
Select OK to return to the previous window. Type the path to the PROTOCOL.INI
file in the Path field.
ΓòÉΓòÉΓòÉ 6.77. LT00205 ΓòÉΓòÉΓòÉ
The network adapter drivers were not found at the path specified.
Select OK and re-specify the full path.
An incorrect or an incomplete path was specified in the Copy Additional Network
Adapter Drivers window. Ensure that the drivers, initialization (.NIF) files,
and supplementary files are all at the specified path.
If the path is incorrect or incomplete, select OK to return to the previous
window. Type the path in the Path field.
If some of the files are not at the path, switch to another session and copy
the files to the specified path. Return to this window and select OK. Specify
the path again, if necessary.
ΓòÉΓòÉΓòÉ 6.78. 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.
One of the network adapter and protocol driver combinations in the Current
Configuration list is not complete. One of the network adapters does not have a
protocol driver.
Select OK to close this message. Complete the configuration by assigning a
protocol driver to the network adapter driver indicated by the cursor or by
removing the network adapter driver from the Current Configuration list.
ΓòÉΓòÉΓòÉ 6.79. 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.
You tried to remove a network adapter before removing the associated protocol
drivers.
Select OK to close the message. If you want to remove a network adapter, you
must first remove the protocol drivers associated with the network adapter.
ΓòÉΓòÉΓòÉ 6.80. 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.
You tried to update the PROTOCOL.INI file, but there are duplicate logical
adapter numbers for a specific protocol driver.
Select OK and change one of the logical adapter numbers.
ΓòÉΓòÉΓòÉ 6.81. LT00209 ΓòÉΓòÉΓòÉ
A decimal number must be entered. (or) A hexadecimal number must be entered.
The value in an entry field is out of range. The range of correct values is
indicated in the message.
Select OK to close this message and return to the field indicated by the
cursor. Type the correct information. If you do not know the correct data,
press F1 on that field to display help information for the field.
ΓòÉΓòÉΓòÉ 6.82. LT00210 ΓòÉΓòÉΓòÉ
An error occurred while attempting to update X.
An OS/2 error occurred during the attempt to update the specified file.
Switch to another OS/2 session and ensure that the file is not in use by
another session. Select Retry to perform the operation again.
For additional information, see the FFST/2 message log if you are using FFST/2,
or see the LANTRAN.LOG file or the LAPSHIST.LOG file.
Select Cancel to return to the window displayed before the update error
occurred.
If you cannot correct the error, select Exit to return to the installation or
configuration program.
ΓòÉΓòÉΓòÉ 6.83. LT00211 ΓòÉΓòÉΓòÉ
An error occurred while attempting to read X.
An OS/2 error occurred during the attempt to read the specified file.
Switch to another OS/2 session and ensure that the file is not in use by
another session. Select Retry to perform the operation again.
For additional information, see the FFST/2 message log if you are using FFST/2,
or see the LANTRAN.LOG file or the LAPSHIST.LOG file.
Select Cancel to return to the previous window. (Cancel is not available in
some installation paths.)
If you cannot correct the error, select Exit to return to the installation or
configuration program.
ΓòÉΓòÉΓòÉ 6.84. LT00212 ΓòÉΓòÉΓòÉ
An error occurred while copying from subdirectory X to subdirectory X.
An OS/2 error occurred during the attempt to copy the specified file to the
specified subdirectory.
Switch to another OS/2 session and ensure that the file is not in use by
another session. Select Retry to perform the operation again.
For additional information, see the FFST/2 message log if you are using FFST/2,
or see the LANTRAN.LOG file or the LAPSHIST.LOG file.
Select Ignore to continue. However, the files may not be copied.
Select Cancel to return to the previous window.
Select Exit to return to the installation/configuration program.
ΓòÉΓòÉΓòÉ 6.85. LT00300 ΓòÉΓòÉΓòÉ
The configuration parameters supplied to LTSVCFG are incorrect. Defaults will
be used for all adapters.
A syntax error occurred in the configuration parameters supplied to the LTSVCFG
configuration tool.
Refer to your documentation for additional information about parameter syntax.
Correct the syntax and retry the operation.
ΓòÉΓòÉΓòÉ 6.86. LT00301 ΓòÉΓòÉΓòÉ
IBM LANVDD: There is not enough memory available for NCB areas.
There is not adequate memory for LANVDD to run properly.
There are several things that might fix this error:
o Add additional memory to this system.
o Reduce the number of active applications and devices.
o Reduce the number of NetBIOS commands requested. This request is controlled
by the NetBIOS command NCB.RESET.
ΓòÉΓòÉΓòÉ 6.87. LT00302 ΓòÉΓòÉΓòÉ
IBM LANVDD: There is not enough memory available for transport command
buffers.
There is not adequate memory for LANVDD to run properly.
There are several things that might fix this error:
o Add additional memory to this system.
o Reduce the number of active applications and devices.
o Reduce the size of the buffer in the transport command.
ΓòÉΓòÉΓòÉ 6.88. 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.
The protocol stack and device drivers were not loaded.
Ensure that the CONFIG.SYS file contains a DEVICE= statement for LANDD.OS2 or
NETBIOS.OS2. If the CONFIG.SYS file contains these statements, check the
LANTRAN.LOG file for additional information. If you do not need Virtual 802.2
and Virtual NetBIOS support, delete the DEVICE= statements for LANVDD.OS2 and
LANPDD.OS2 from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.89. LT00305 ΓòÉΓòÉΓòÉ
LANPDD was unable to register with the Virtual DOS Machine Manager.
LANPDD could not register with the Virtual DOS Machine Manager. Registration is
required for LANVDD/LANPDD coexistence.
Ensure that Virtual DOS support was selected at installation. If Virtual DOS
Support is not required, remove LANVDD and LANPDD from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.90. LT00307 ΓòÉΓòÉΓòÉ
IBM LANPDD: A failure occurred during initialization.
An initialization error has been reported, which has caused the device driver
to not install.
Check the LANTRAN.LOG file to identify the specific condition that caused the
failure. A message detailing that condition will be logged prior to this
message.
ΓòÉΓòÉΓòÉ 6.91. LT00308 ΓòÉΓòÉΓòÉ
An unexpected error was returned from a GetDOSVar request.
The address to the system global information segment is not valid.
Try the operation again. If the problem persists, note the message number and
contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.92. LT00309 ΓòÉΓòÉΓòÉ
The number of DOS Sessions that LANVDD can support has been exceeded.
NetBIOS is supported in a maximum of 16 VDM sessions. One has surpassed this
limit.
If NetBIOS is required, reduce the number of DOS sessions in use or run your
NetBIOS applications in a DOS session that already exists.
ΓòÉΓòÉΓòÉ 6.93. LT00310 ΓòÉΓòÉΓòÉ
The virtual DOS machine manager could not allocate a software hook required for
LANDDD internal operations.
A failure occurred when trying to allocate either a Context, Return, or
WAITVIRR hook with the VDM Manager.
Ensure that there are adequate disk and memory resources on your machine before
starting a VDM session or run with fewer VDM sessions.
ΓòÉΓòÉΓòÉ 6.94. LT00311 ΓòÉΓòÉΓòÉ
The operating system installed is not compatible with this program.
The version of the operating system required for this program to run is OS/2
2.0 or greater.
Install a version of OS/2 that is 2.0 or greater or delete the IBMPDD and
LANVDD sections from the CPMFOG/SYS file.
ΓòÉΓòÉΓòÉ 6.95. LT00312 ΓòÉΓòÉΓòÉ
The OS/2 802.2 device driver, LANDD.OS2, is not available. DOS 802.2 support is
ended for all VDMs.
The IBM OS/2 802.2 protocol stack (LANDD.OS2) is not installed or is not
operational. LANVDD cannot support the DOS 802.2 API if the OS/2 802.2
protocol stack is not present.
Ensure that the CONFIG.SYS file contains a DEVICE= statement for LANDD.OS2. If
the CONFIG.SYS file contains the statement, check the LANTRAN.LOG file for
additional information.
ΓòÉΓòÉΓòÉ 6.96. LT00314 ΓòÉΓòÉΓòÉ
LANVDD.OS2 was unable to map a virtual address to a linear address in system
memory.
The operating system may be damaged.
Restart OS/2 and retry the request. If this message persists, report this
problem and the contents of the LANTRAN.LOG file to an IBM service
representative.
ΓòÉΓòÉΓòÉ 6.97. LT00315 ΓòÉΓòÉΓòÉ
A status indication was received for an unknown application ID.
The IBM OS/2 802.2 protocol stack (LANDD.OS2) notified LANVDD of a status event
for an application unknown to LANVDD.
Restart OS/2 and retry the request. If this message persists, report this
problem and the contents of the LANTRAN.LOG file to an IBM service
representative.
ΓòÉΓòÉΓòÉ 6.98. LT00316 ΓòÉΓòÉΓòÉ
A status indication was lost or ignored.
The IBM OS/2 802.2 protocol stack (LANDD.OS2) notified LANVDD of a status event
for a SAP LANVDD does not own.
Restart OS/2 and retry the operation. If this message persists, report this
problem and the contents of the LANTRAN.LOG file to an IBM service
representative.
ΓòÉΓòÉΓòÉ 6.99. LT00317 ΓòÉΓòÉΓòÉ
LANVDD is unable to access DOS memory.
LANVMEM.SYS was not loaded as part of the DOS device settings in this DOS
environment.
Ensure that the DOS device driver, LANVMEM.SYS, is being loaded as part of the
DOS device settings for the specific DOS environment.
ΓòÉΓòÉΓòÉ 6.100. LT00318 ΓòÉΓòÉΓòÉ
The maximum number of OS/2 802.2 user applications was reached.
The number of active 802.2 applications is the configured maximum.
Run the LAPS (LAN Adapter and Protocol Support) install program and choose
Configure. Increase the value for the OS/2 802.2 resource, Maximum Number of
Users.
ΓòÉΓòÉΓòÉ 6.101. LT00319 ΓòÉΓòÉΓòÉ
The maximum number of OS/2 802.2 SAPs was reached.
The number of open 802.2 SAPs is the configured maximum.
Run the LAPS (LAN Adapter and Protocol Support) install program and choose
Configure. Increase the value for the OS/2 802.2 resource, Maximum SAPs.
ΓòÉΓòÉΓòÉ 6.102. LT00320 ΓòÉΓòÉΓòÉ
LANVDD was unable to allocate the requested OS/2 SAP buffers.
The operating system could not provide system memory for a LANVDD request.
Stop any unnecessary applications and retry the request. If this message
persists, add more memory to your system.
ΓòÉΓòÉΓòÉ 6.103. LT00322 ΓòÉΓòÉΓòÉ
LANDD did not complete a LANVDD BufferFree request successfully.
The operating system may be damaged.
Restart OS/2 and retry the request. If this message persists, report this
problem and the contents of the LANTRAN.LOG file to an IBM service
representative.
ΓòÉΓòÉΓòÉ 6.104. LT00323 ΓòÉΓòÉΓòÉ
LANVDD was unable to allocate internal memory elements.
The operating system could not provide system memory for a LANVDD request.
Stop any unnecessary applications and retry the request. If this message
persists, add more memory to your system.
ΓòÉΓòÉΓòÉ 6.105. LT00324 ΓòÉΓòÉΓòÉ
A LANVDD buffer allocation request was cancelled.
LANVDD could not allocate system memory for status elements.
Stop any unnecessary applications and retry the request. If this message
persists, add more memory to your system.
ΓòÉΓòÉΓòÉ 6.106. LT00325 ΓòÉΓòÉΓòÉ
LANVDD received a DLC status indication for a SAP that LANVDD
did not open. The IBM OS/2 802.2 protocol stack (LANDD.OS2) notified LANVDD of
a status event for a SAP that LANVDD does not own.
Restart OS/2 and retry your request. If this message persists, report this
problem and the contents of the LANTRAN.LOG file to an IBM service
representative.
ΓòÉΓòÉΓòÉ 6.107. LT00326 ΓòÉΓòÉΓòÉ
LANVDD was unable to simulate local busy to a DOS application.
LANVDD does not have enough internal resources to complete the request. LANVDD
received an expected return code from LANDD on a DLC.FLOW.CONTROL.
Restart the application and retry the request. If this message persists, report
this problem and the contents of the LANTRAN.LOG file to an IBM service
representative.
ΓòÉΓòÉΓòÉ 6.108. LT10001 ΓòÉΓòÉΓòÉ
The protocol manager could not be opened.
An unexpected error occurred when the program attempted to open the protocol
manager.
Check the drive and directory to ensure that the protocol manager is located in
the specified path.
ΓòÉΓòÉΓòÉ 6.109. LT10002 ΓòÉΓòÉΓòÉ
The adapter was not found or is not responding.
There is no physical adapter in this machine or the adapter is not responding
to a request to start.
If there is no adapter in this machine, install a PC Network* adapter or remove
the device driver statement from the CONFIG.SYS file. If there is already an
adapter in this machine, check the cable and ensure that the connection to the
IBM PC Network adapter is functioning properly. Then run the hardware
diagnostics for the PC Network adapter to ensure the adapter and options are
correctly installed.
ΓòÉΓòÉΓòÉ 6.110. LT10003 ΓòÉΓòÉΓòÉ
Conflicting adapter mode parameter values were found in the PROTOCOL.INI file.
Multiple adapter mode parameters that are set to identical values were found
while processing the PC Network device driver section of the PROTOCOL.INI file.
This conflict does not allow the physical adapters to be mapped properly to MAC
modules identified in the PROTOCOL.INI file.
Examine the adapter mode parameters in the PC Network device driver section of
the PROTOCOL.INI file and correct the conflicting values.
ΓòÉΓòÉΓòÉ 6.111. LT10005 ΓòÉΓòÉΓòÉ
Resources are not available to set up the adapter as configured in
PROTOCOL.INI.
The adapter cannot be initialized using the parameters and options configured
in the PROTOCOL.INI file.
Adjust the values specified in the PROTOCOL.INI file to allow the queues and
buffer pools to be set up.
ΓòÉΓòÉΓòÉ 6.112. LT10006 ΓòÉΓòÉΓòÉ
An error occurred while attempting to create a data segment for the alternate
adapter.
An error condition was returned from a request to create a data segment for the
alternate adapter.
Ensure that the adapter is properly installed and set up or do not use the
second adapter.
ΓòÉΓòÉΓòÉ 6.113. LT10007 ΓòÉΓòÉΓòÉ
A failure occurred during initialization. Press any key to continue.
This is a generic initialization failure message. If any error is encountered
by the IBM PC Network device driver during IPL time, the specific message
related to the error will be followed by this generic message.
Resolve the specific error message that displayed prior to this message, if
present. Otherwise, ensure that the protocol manager is located in the proper
directory and that the protocol manager statement exists in the CONFIG.SYS
file.
ΓòÉΓòÉΓòÉ 6.114. LT10013 ΓòÉΓòÉΓòÉ
An error occurred while attempting to set up a FIFO address or an IRQ level, or
during the POST for the primary IBM PC Network adapter.
An error occurred while attempting to set up a FIFO address or an IRQ level, or
while checking the power-on self-test for the primary IBM PC Network adapter.
Use the reference diskette that came with your computer to ensure that the FIFO
address, the IRQ level, and the power-on self-test are set properly.
ΓòÉΓòÉΓòÉ 6.115. LT10014 ΓòÉΓòÉΓòÉ
An error occurred while attempting to set up a FIFO address or an IRQ level, or
during the POST for the alternate IBM PC Network adapter.
An error occurred while attempting to set up a FIFO address or an IRQ level, or
while checking the power-on self-test for the primary IBM PC Network.
Use the reference diskette that came with your computer to ensure that the FIFO
address, IRQ level, and power-on self-test are set properly.
ΓòÉΓòÉΓòÉ 6.116. LT20022 ΓòÉΓòÉΓòÉ
A failure during initialization of the IBMTOK.OS2 device driver has occurred.
This is a generic initialization failure message. If the IBMTOK.OS2 device
driver encounters any errors during initialization, the specific message
related to the error will accompany this generic message.
Resolve the specific error message that accompanies this message. In addition,
ensure that the Protocol Manager device driver, PROTMAN.OS2, is located in the
\IBMCOM directory and that a DEVICE statement for PROTMAN.OS2 exists in the
CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.117. LT20023 ΓòÉΓòÉΓòÉ
An unrecognized parameter X was found in PROTOCOL.INI.
The parameter displayed was found while processing the IBM Token-Ring Network
Driver section of the PROTOCOL.INI file. The parameter is not valid.
Correct the parameter or remove it from the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.118. LT20024 ΓòÉΓòÉΓòÉ
A value specified for a parameter in PROTOCOL.INI is not valid.
The value provided for the parameter is not the correct type or is not a valid
value.
Change the value for the parameter in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.119. LT20025 ΓòÉΓòÉΓòÉ
A configuration error was found in PROTOCOL.INI.
Conflicting parameter values were found while processing the IBM Token-Ring
Network Driver section of the PROTOCOL.INI file.
Examine the configuration parameters and correct the conflicting values in the
PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.120. LT20026 ΓòÉΓòÉΓòÉ
The adapter is not responding or was not found.
One of the following conditions has caused this error:
o The logical primary/alternate setting in the PROTOCOL.INI file does not map
to the physical primary/alternate setting.
o The adapter is not responding to a request to start.
o There is no physical adapter in this machine.
If there is already an adapter in this system, check the logical
primary/alternate setting. Check the cable and ensure that the connection to
the token-ring network addressable unit (NAU) is functioning properly. Then
run the hardware diagnostics for the token-ring adapter to ensure that the
adapter and options are correctly installed.
If there is no adapter in this machine, install a token-ring adapter or remove
the device driver statement from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.121. LT20027 ΓòÉΓòÉΓòÉ
The protocol manager could not be opened.
An unexpected error occurred when the program attempted to open the protocol
manager.
Check the drive and directory to ensure that the protocol manager is located in
the specified path.
ΓòÉΓòÉΓòÉ 6.122. LT20029 ΓòÉΓòÉΓòÉ
The network status has changed. An open or short circuit has been detected in
the lobe data path. The adapter will be closed.
The IBM Token-Ring Network adapter encountered a wire fault.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.123. LT20030 ΓòÉΓòÉΓòÉ
There are not adequate receive buffers for the adapter to open.
The requested DIR.OPEN.ADAPTER parameter has not allowed enough receive buffer
space in the adapter shared RAM area.
Reduce the RAM requirements by reconfiguring the parameters in the PROTOCOL.INI
file. The parameters that will reduce the space requirements for the receive
buffer are the data hold buffers (if more than 1 is specified), and Number of
queue elements.
ΓòÉΓòÉΓòÉ 6.124. LT20032 ΓòÉΓòÉΓòÉ
An invalid node address error occurred when the program attempted to open the
adapter.
The node address defined is not valid.
Specify a valid node address. Refer to the IBM Token-Ring Network architecture
reference for node address restrictions.
ΓòÉΓòÉΓòÉ 6.125. LT20033 ΓòÉΓòÉΓòÉ
The receive buffer length defined is not valid. The adapter was not opened.
The receive buffer length defined in the PROTOCOL.INI file is not valid. The
value specified must be greater than the allowable maximum, less than the
allowable minimum, or not a multiple of 8.
Specify a valid receive buffer length.
ΓòÉΓòÉΓòÉ 6.126. LT20034 ΓòÉΓòÉΓòÉ
The adapter transmit buffer length defined is not valid. The adapter was not
opened.
The adapter transmit buffer length defined in the PROTOCOL.INI file is not
valid. The value specified must be greater than the allowable maximum, less
than the allowable minimum, or not a multiple of 8.
Specify a valid adapter transmit buffer length.
ΓòÉΓòÉΓòÉ 6.127. LT20037 ΓòÉΓòÉΓòÉ
An unexpected error caused the Open Adapter Command in the IBMTOK.OS2 device
driver to fail. The open return code is X.
The adapter was closed because of an unexpected error condition.
See the message log, LANTRAN.LOG, for additional information about this error.
The error must be corrected before you can use this adapter.
ΓòÉΓòÉΓòÉ 6.128. LT20038 ΓòÉΓòÉΓòÉ
The network status has changed. An adapter hardware error has been detected
following the beacon auto-removal process. The adapter will be closed.
The IBM Token-Ring Network adapter has either detected a monitor contention
failure or received a beacon frame from the ring. The problem may be that your
adapter speed is different from the speed at which the LAN is running.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.129. LT20039 ΓòÉΓòÉΓòÉ
The network status has changed. A remove MAC frame has been received. The
adapter will be closed.
A command forcing the adapter to remove itself from the ring was received.
Note the identification number of this message and contact your LAN support
personnel for assistance.
ΓòÉΓòÉΓòÉ 6.130. LT20041 ΓòÉΓòÉΓòÉ
An open error occurred during the lobe media test phase.
The IBM Token-Ring Network adapter has detected a problem on your local lobe
between the adapter and the Multistation Access Unit (MSAU).
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.131. LT20042 ΓòÉΓòÉΓòÉ
An open error occurred during the physical insertion phase.
The IBM Token-Ring Network adapter has detected one of the following open
errors while trying to insert into the LAN:
o Ring Failure
o Ring beaconing
o Timeout
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.132. LT20043 ΓòÉΓòÉΓòÉ
An open error occurred during the address verification phase.
The IBM Token-Ring Network adapter has detected one of the following open
errors during the address verification phase of the adapter open process:
o Signal loss
o Timeout
o Ring failure
o Ring beaconing
o Duplicate node
o REMOVE command received
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.133. LT20044 ΓòÉΓòÉΓòÉ
An open error occurred during the roll call poll.
The IBM Token-Ring Network adapter has detected one of the following open
errors during the roll call poll phase of the adapter open process:
o Signal loss
o Timeout
o Ring failure
o Ring beaconing
o REMOVE command received
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.134. LT20045 ΓòÉΓòÉΓòÉ
An open error occurred during the request parameter phase.
The IBM Token-Ring Network adapter has detected one of the following open
errors during the request parameter phase of the adapter open process:
o Signal loss
o Timeout
o Ring failure
o Ring beaconing
o Parameter request
o REMOVE command received
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.135. LT20051 ΓòÉΓòÉΓòÉ
The open error type is Function failure.
The IBM Token-Ring Network adapter has detected a lobe media failure while
trying to open the adapter.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.136. LT20052 ΓòÉΓòÉΓòÉ
The open error type is Signal loss.
The IBM Token-Ring Network adapter has detected a signal loss failure while
trying to open the adapter.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.137. LT20055 ΓòÉΓòÉΓòÉ
The open error type is Timeout.
The IBM Token-Ring Network adapter has detected an insertion timer expiration
while trying to open the adapter. This condition indicates that the ring may
be congested, experiencing a high bit-error rate, or is losing an unusually
high number of tokens or frames.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.138. LT20056 ΓòÉΓòÉΓòÉ
The open error type is Ring failure.
The IBM Token-Ring Network adapter has detected a ring failure while trying to
open the adapter.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.139. LT20057 ΓòÉΓòÉΓòÉ
The open error type is Ring beaconing.
The IBM Token-Ring Network adapter has detected a monitor contention failure or
has received a beacon frame from the ring while trying to open the adapter.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.140. LT20058 ΓòÉΓòÉΓòÉ
The open error type is Duplicate node address.
The IBM Token-Ring Network adapter has detected that another station on the
ring has an adapter address equal to the address specified for your adapter.
Contact your system administrator to get a unique node address and then use
advanced configuration for LAN Adapter and Protocol Support to change the node
address.
ΓòÉΓòÉΓòÉ 6.141. LT20059 ΓòÉΓòÉΓòÉ
The open error type is Parameter request.
The IBM Token-Ring Network adapter has detected a parameter request error while
trying to open the adapter.
1. Check and secure all cable connections between your adapter and the
Multistation Access Unit (MSAU). Correct any related problems and try the
operation again.
2. If there are no related problems, refer to the documentation that was
shipped with your adapter to run adapter diagnostics; then try the
operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.142. LT20060 ΓòÉΓòÉΓòÉ
The open error type is REMOVE received.
While attempting to insert into the ring, a command forcing this adapter to
remove from the ring was received.
Note the identification number of this message and then contact your LAN
support personnel.
ΓòÉΓòÉΓòÉ 6.143. LT20063 ΓòÉΓòÉΓòÉ
The open error type is No monitor detected.
RPL station is the first station attempting to insert into the ring.
1. Retry the operation.
2. If the problem persists, refer to the documentation that was shipped with
your adapter to run adapter diagnostics; then try the operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.144. LT20064 ΓòÉΓòÉΓòÉ
The open error type is Monitor contention failed for RPL.
Physical insertion of RPL station onto the ring failed.
1. Check the adapter configuration and retry the open request.
2. If the problem persists, refer to the documentation that was shipped with
your adapter to run adapter diagnostics; then try the operation again.
3. If the problem persists, print or save the LANTRAN.LOG file and contact
your system coordinator.
ΓòÉΓòÉΓòÉ 6.145. LT20070 ΓòÉΓòÉΓòÉ
For this micro-code level, the value specified for XMITBUFS in the file
PROTOCOL.INI must be greater than 1. Run-time errors may occur if this value
is not increased. IBMTOK.OS2 has defaulted this value to 2. See the help for
this message for further corrective action.
A problem was detected on micro-code level "00 00 00 C2 45 50".
Request and install engineering change ECA0066, part number 92F9122, on your
system, or use the configuration feature of the LAN Adapter and Protocol
Support installation program to change the value for the number of transmit
buffers to be greater than 1.
ΓòÉΓòÉΓòÉ 6.146. LT30002 ΓòÉΓòÉΓòÉ
Device X: A failure occurred during initialization.
This is a generic initialization failure message. If any error is encountered
by the device driver during IPL, the specific message related to the error will
be followed by this generic message.
If an error-specific message was displayed first, resolve the error-specific
message. If no error-specific message was displayed, ensure that the protocol
manager is located in the proper directory and that the protocol manager
statement exists in the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.147. LT30003 ΓòÉΓòÉΓòÉ
This protocol used by this adapter is not supported.
This adapter uses a protocol that is not supported by this product.
Consult the ES/LS user documentation for a list of supported adapters.
ΓòÉΓòÉΓòÉ 6.148. LT30004 ΓòÉΓòÉΓòÉ
Device X: The value specified for a parameter in PROTOCOL.INI is not valid.
The value provided for the parameter is not valid.
Review the PROTOCOL.INI file to determine the parameter that contains the
incorrect value. Change the value and try the operation again.
ΓòÉΓòÉΓòÉ 6.149. LT30005 ΓòÉΓòÉΓòÉ
Device X: An unrecognized keyword was found in PROTOCOL.INI.
A configuration parameter is defined in the PROTOCOL.INI file that is not
recognized as a valid keyword.
Review the PROTOCOL.INI file and determine the keyword that caused the error.
Correct the keyword and try the operation again.
ΓòÉΓòÉΓòÉ 6.150. LT30006 ΓòÉΓòÉΓòÉ
Device X: The 3270 emulation adapter was not found.
Probable causes are:
o The 3270 emulation adapter is not installed or is installed improperly.
o The number of IBMXLN.OS2 drivers specified in the CONFIG.SYS file exceeds the
number of 3270 emulation adapters installed.
Ensure that the 3270 emulation adapter is properly installed and that the
CONFIG.SYS file does not contain more DEVICE= statements for IBMXLN.OS2 than
there are 3270 emulation adapters present in this system.
ΓòÉΓòÉΓòÉ 6.151. LT30007 ΓòÉΓòÉΓòÉ
There are too many IBMXLN devices defined in CONFIG.SYS.
The CONFIG.SYS file contains too many DEVICE= statements for IBMXLN.OS2. The
maximum supported number for a Micro Channel PS/2 system is 4. The maximum
number for a non-Micro Channel PC system is 1.
Remove the excess DEVICE= statements from the CONFIG.SYS file and try the
operation again.
ΓòÉΓòÉΓòÉ 6.152. LT30009 ΓòÉΓòÉΓòÉ
Device X: The protocol manager could not be opened.
An unexpected error occurred when the program attempted to open the protocol
manager.
Check the drive and directory to ensure that the protocol manager is located in
the specified path. Check the CONFIG.SYS file to ensure that a DEVICE=
statement for PROTMAN.OS2 is listed before the DEVICE= statement for
IBMXLN.OS2, and try the operation again.
ΓòÉΓòÉΓòÉ 6.153. LT30010 ΓòÉΓòÉΓòÉ
Device X: An unexpected error was returned from a DOSDevIOCtl request.
The system service DOSDevIOCtl returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.154. LT30011 ΓòÉΓòÉΓòÉ
Device X: An error occurred when the program tried to get configuration
information from the protocol manager.
An attempt to obtain configuration information from the protocol manager was
unsuccessful.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.155. LT30012 ΓòÉΓòÉΓòÉ
Device X: The version of the protocol manager installed is not compatible with
this device.
The version of the protocol manager installed will not run with this device.
Install a compatible version of the protocol manager and try the operation
again.
ΓòÉΓòÉΓòÉ 6.156. LT30013 ΓòÉΓòÉΓòÉ
Device X: An unexpected error was returned from an AllocGDTSelector request.
The system service AllocGDTSelector returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.157. LT30014 ΓòÉΓòÉΓòÉ
Device X: An unexpected error was returned from a PhysToGDTSelector request.
The system service PhysToGDTSelector returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.158. LT30015 ΓòÉΓòÉΓòÉ
Device X: The MAC driver is not registered or cannot be found.
An attempt to register the device name with the protocol manager was
unsuccessful.
Review the PROTOCOL.INI file to ensure that the bracketed names are unique and
try the operation again.
ΓòÉΓòÉΓòÉ 6.159. LT30016 ΓòÉΓòÉΓòÉ
Device X: An unexpected error was returned from a PhysToVirt request.
The system service PhysToVirt returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.160. LT30017 ΓòÉΓòÉΓòÉ
Device X: There was no entry found in PROTOCOL.INI for driver name X. Default
values will be used.
No entry was found for the driver name in the PROTOCOL.INI file.
If default values are acceptable, no action is required; otherwise, build a
PROTOCOL.INI file entry for the device and try the operation again.
ΓòÉΓòÉΓòÉ 6.161. LT30018 ΓòÉΓòÉΓòÉ
Device X: Duplicate driver name X parameters exist in PROTOCOL.INI.
The PROTOCOL.INI file contains more than 1 entry with the same driver name
parameter.
Correct or remove the duplicate driver name parameter and try the operation
again.
ΓòÉΓòÉΓòÉ 6.162. LT30022 ΓòÉΓòÉΓòÉ
Device X: The establishment controller is not responding.
The establishment controller is not responding to a request issued by the
device. The adapter has been closed.
Ensure the device is attached by coax to the controller and that the controller
is turned on; re-open the adapter to reactivate peer communication protocols.
If the problem persists, restart your system.
ΓòÉΓòÉΓòÉ 6.163. LT30023 ΓòÉΓòÉΓòÉ
Device X: An unexpected error was returned from a SetIRQ request.
The system service SetIRQ returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.164. LT30024 ΓòÉΓòÉΓòÉ
Device X: A RESET command was received from the controller.
The controller has stopped peer communication protocols by issuing a RESET
command to the device.
Re-open the adapter to activate the peer communication protocols to the
controller.
ΓòÉΓòÉΓòÉ 6.165. LT30025 ΓòÉΓòÉΓòÉ
Device X: A X protocol error was received from the controller.
The controller has detected a protocol error from the device or has been
requested to remove the device from the network.
If the protocol error returned is INVALID ENABLE INFO, ensure that the address
defined for the adapter in the PROTOCOL.INI file is unique. Re-open the
adapter to reactivate peer communication protocols to the controller. If the
problem persists, contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.166. LT30026 ΓòÉΓòÉΓòÉ
Device X: A X protocol error was sent to controller.
The device has detected a protocol error from the controller and has closed the
adapter.
Re-open the adapter to reactivate peer communication protocols. If the error
persists, contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.167. LT30027 ΓòÉΓòÉΓòÉ
Device X: This controller does not support peer communication protocols.
The controller that is attached by coax to the device does not support the 3174
Peer Communications protocol.
Ensure the controller attached to the device contains 3174 Peer Communications
support. If support is available, try the operation again. If the problem
persists, contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.168. LT30028 ΓòÉΓòÉΓòÉ
Device X: The RDEF command from the controller is not valid.
The RDEF command from the controller was not acceptable to the device.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.169. LT30029 ΓòÉΓòÉΓòÉ
Device X: An unexpected error was returned from a TickCount request.
The system service TickCount returned an unsuccessful error code.
Try the operation again. If the problem persists, contact your vendor sales
representative.
ΓòÉΓòÉΓòÉ 6.170. LT40004 ΓòÉΓòÉΓòÉ
The microcode file X could not be opened.
An unexpected error occurred when the program attempted to open the microcode
file.
Ensure that the microcode file, MONT400.BIN, is installed in the drive and
directory identified in the message. If the file does not exist or if the
problem persists, re-install the device driver.
ΓòÉΓòÉΓòÉ 6.171. LT40005 ΓòÉΓòÉΓòÉ
The microcode file X could not be read.
An unexpected error occurred when the program attempted to read the microcode
file.
Re-install the device driver.
ΓòÉΓòÉΓòÉ 6.172. LT40006 ΓòÉΓòÉΓòÉ
The bootstrap file X could not be opened.
An unexpected error occurred when the program attempted to open the bootstrap
file.
Ensure that the bootstrap file, WRTRAM.BIN, is installed in the drive and
directory identified in the message. If the file does not exist or if the
problem persists, re-install the device driver.
ΓòÉΓòÉΓòÉ 6.173. LT40007 ΓòÉΓòÉΓòÉ
The bootstrap file X could not be read.
An unexpected error occurred when the program attempted to read the bootstrap
file.
Re-install the device driver.
ΓòÉΓòÉΓòÉ 6.174. LT40008 ΓòÉΓòÉΓòÉ
The parameter specified in PROTOCOL.INI for keyword X is not the proper
character type.
The value provided for the keyword in the IBMTRBM module in the PROTOCOL.INI
file is not the correct type.
Change the value in the PROTOCOL.INI file to the correct type for the
parameter.
ΓòÉΓòÉΓòÉ 6.175. LT40009 ΓòÉΓòÉΓòÉ
An unrecoverable error occurred in the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A NDIS device driver program.
An internal software error occurred.
Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.176. LT40010 ΓòÉΓòÉΓòÉ
All IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapters must be set
to the same interrupt level.
One or more IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapters are
set to a different interrupt level. To function properly, these adapters must
all be set to the same interrupt level.
Use the reference diskette that came with your computer to ensure that all IBM
Token-Ring Network 16/4 Busmaster Server Adapter/A adapters are set to the same
interrupt level.
ΓòÉΓòÉΓòÉ 6.177. LT40011 ΓòÉΓòÉΓòÉ
A data-check error occurred while attempting to load the bootstrap code onto
the adapter.
The bootstrap code was unable to load properly onto the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A adapter.
Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.178. LT40012 ΓòÉΓòÉΓòÉ
A checksum error occurred while attempting to load the bootstrap code onto the
adapter.
The bootstrap code was unable to load properly onto the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A adapter.
Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.179. LT40014 ΓòÉΓòÉΓòÉ
The parameter values have forced the control-block size to exceed the allowable
limit.
The parameters specified require more space for processing than can be handled.
The maximum allowable control-block size is 64KB.
Reduce the value specified for the MAXTRANSMITS or MINRCVBUFFS parameter to
change the amount of storage required for the control-blocks.
The control-block area can be computed using the following formula:
334 + (142 * MAXTRANSMITS) + (20 * MINRCVBUFFS)
The control-block work area must be less than 64KB.
ΓòÉΓòÉΓòÉ 6.180. LT40015 ΓòÉΓòÉΓòÉ
The adapter is not responding.
The adapter is not responding to a request to load the bootstrap code.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.181. LT40016 ΓòÉΓòÉΓòÉ
A 2KB window error occurred while attempting to load the bootstrap code onto
the adapter.
The adapter is not responding to a request to load the bootstrap code.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.182. LT40017 ΓòÉΓòÉΓòÉ
An error occurred while attempting to run the bootstrap code.
The adapter is not responding to a request to run the bootstrap code.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.183. LT40018 ΓòÉΓòÉΓòÉ
A parameter error occurred while attempting to run the bootstrap code.
The adapter is not responding to a request to run the bootstrap code.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.184. LT40019 ΓòÉΓòÉΓòÉ
A write error occurred while attempting to load the bootstrap code onto the
adapter.
The bootstrap code was unable to load properly onto the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A adapter.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.185. LT40020 ΓòÉΓòÉΓòÉ
A checksum error occurred while attempting to load the microcode onto the
adapter.
The microcode was unable to load properly onto the IBM Token-Ring Network 16/4
Busmaster Server Adapter/A adapter.
Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.186. LT40021 ΓòÉΓòÉΓòÉ
The microcode encountered a program-status error while attempting to write to
the adapter.
The microcode was unable to write properly to the IBM Token-Ring Network 16/4
Busmaster Server Adapter/A adapter.
Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.187. LT40022 ΓòÉΓòÉΓòÉ
A reset error occurred while attempting to initialize the adapter microcode.
The adapter is not responding to a request to initialize the microcode.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.188. LT40023 ΓòÉΓòÉΓòÉ
A parameter error occurred while attempting to run the microcode.
The adapter is not responding to a request to run the microcode.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.189. LT40024 ΓòÉΓòÉΓòÉ
The burned-in address could not be found on the IBM Token-Ring Network 16/4
Busmaster Server Adapter/A adapter.
The burned-in address on the adapter could not be located.
Either use the set network address (NETADDRESS) parameter in the PROTOCOL.INI
file to override the burned-in address or run the hardware diagnostics for the
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapter and contact your
vendor sales representative.
ΓòÉΓòÉΓòÉ 6.190. LT40025 ΓòÉΓòÉΓòÉ
Duplicate device driver statements exist in CONFIG.SYS.
Only one occurrence of the device driver statement for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A NDIS MAC device driver is required to
support multiple adapters. Additional instances of the device driver statement
in the CONFIG.SYS file are ignored.
Remove the duplicate device driver statements from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.191. LT40026 ΓòÉΓòÉΓòÉ
The required parameter DRIVERNAME was not found in PROTOCOL.INI.
The parameter specifying the driver name (DRIVERNAME) was not found in the
PROTOCOL.INI file. This parameter is required.
Change the PROTOCOL.INI file to specify the proper information.
ΓòÉΓòÉΓòÉ 6.192. LT40027 ΓòÉΓòÉΓòÉ
The protocol manager could not be opened.
An unexpected error occurred when the program attempted to open the protocol
manager. The IBM Token-Ring Network 16/4 Busmaster Server Adapter/A NDIS MAC
device driver has been removed.
Check the drive and directory to ensure that the protocol manager is located in
the specified path.
ΓòÉΓòÉΓòÉ 6.193. 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.
The device driver was unable to register with the protocol manager.
Re-install the protocol manager and try the operation again.
ΓòÉΓòÉΓòÉ 6.194. LT40029 ΓòÉΓòÉΓòÉ
No physical adapter was found in this machine.
There was no adapter found in this machine. IBM Token-Ring Network 16/4
Busmaster Server Adapter/A adapters are required to run the MAC device driver.
Install an IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapter in
this machine, or remove the device driver statement from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.195. LT40030 ΓòÉΓòÉΓòÉ
The unrecognized parameter X was found in PROTOCOL.INI.
An unrecognized parameter was found while processing the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A section of the PROTOCOL.INI file.
Correct the parameter or remove it from the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.196. LT40031 ΓòÉΓòÉΓòÉ
The value specified for network address in PROTOCOL.INI is not valid. The
burned-in address will be substituted.
The value specified for the network address parameter in the PROTOCOL.INI file
is not valid for one of the following reasons:
o Invalid local station address
o Too long
o Too short
o Contains non-hexadecimal characters
o Not enclosed in double quotes
Remove or correct the network address parameter (NETADDRESS). A valid value for
this parameter is 12 characters long, is enclosed in double quotes, and
contains only valid hexadecimal characters within the range of 400000000000
through 40007FFFFFFF.
ΓòÉΓòÉΓòÉ 6.197. LT40033 ΓòÉΓòÉΓòÉ
A duplicate network address was found while inserting onto the ring.
The network address that the adapter wants to use on the token-ring is being
used by another node.
Either modify the PROTOCOL.INI file to provide a different value for the
network address (NETADDRESS) parameter, use the default burned-in address, or
remove the other node that is using this network address from the ring.
ΓòÉΓòÉΓòÉ 6.198. LT40034 ΓòÉΓòÉΓòÉ
Ring failure or beaconing was encountered while inserting onto the ring.
The ring speed is different from the speed of the node attempting to insert
onto the ring.
Use the reference diskette that came with your computer to ensure that the
adapter is configured at the same speed as the token-ring.
ΓòÉΓòÉΓòÉ 6.199. LT40035 ΓòÉΓòÉΓòÉ
A hardware failure occurred while attempting to open the adapter.
When the adapter tried to insert onto the token-ring, a hardware error occurred
on the adapter.
Run the hardware diagnostics for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter. Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.200. LT40036 ΓòÉΓòÉΓòÉ
A lobe media error has occurred. Ensure that the token-ring cable is connected
to the adapter.
While attempting to open the adapter, an indication was received that the
adapter is not properly connected to the token-ring.
Ensure that the token-ring cable is connected to the adapter and to the
token-ring multistation access unit (MAU).
If the error persists, use a different token-ring cable and check to ensure
that the connection to the MAU is functioning properly. Then run the hardware
diagnostics for the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
adapter.
ΓòÉΓòÉΓòÉ 6.201. LT40040 ΓòÉΓòÉΓòÉ
This version of the microcode is not supported.
The version of the microcode contained in MONT400.BIN is down-level.
Re-install the microcode from the installation diskette.
ΓòÉΓòÉΓòÉ 6.202. LT40043 ΓòÉΓòÉΓòÉ
An unrecoverable error occurred during an address translation in the IBM
Token-Ring 16/4 Network Busmaster Server Adapter/A NDIS device driver.
This message is displayed only when there is an AOX adapter installed in this
system. The AOX adapter acts as a replacement processor or a dual processor,
which requires that busmaster adapters perform extra translation of physical
addresses. This error message can be caused by one of the following
situations:
o At initialization, when the device driver is being installed, a block of
physical memory is obtained. If the physical address crosses a "memory
seam," this error is displayed.
o While running, the upper protocol layer provides the device driver with a
physical address. If the physical address crosses a "memory seam", this
error is displayed. The device driver cannot continue to run. The adapter
is stopped and the request from the protocol is rejected.
Restart your system and try the operation again. If the problem persists,
re-install the system and run diagnostics on the AOX adapter. If the problem
continues to persist, contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.203. LT40044 ΓòÉΓòÉΓòÉ
The configuration values have forced the control-block size to exceed the
available memory.
The configuration parameters specified require more space for processing than
can be handled with the available system memory.
Reduce the value specified for the MAXTRANSMITS or MINRCVBUFFS parameter to
change the amount of storage required.
Use the following formula to compute the maximum value:
H(i) = RCVAREA(i) + ALLOCSIZECB(i)
A H(i) value should be computed for each IBM Token-Ring Network 16/4 Busmaster
Adapter, and the sum of all H(i) values must be less than 1 MB.
Use the following formula to compute the receive area for each adapter:
RCVAREA = MINRCVBUFFS x SIZWORKBUFF
Use the following formula to compute the control block area for each adapter.
The control block area must be less than 64KB.
ALLOCSIZECB = 334 + (142 x MAXTRANSMITS) + (20 x MINRCVBUFFS)
ΓòÉΓòÉΓòÉ 6.204. LT80198 ΓòÉΓòÉΓòÉ
The attempt to add the Multiple Link Interface Driver(MLID) protocol ID failed.
The ODI2NDI.OS2 cannot function.
The attempt to add this MLID protocol ID has failed. The IBM NetWare Requester
Support (ODI2NDI.OS2) will not work.
You may have too many protocol IDs defined. Delete those protocol IDs that are
not required.
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.205. LT80199 ΓòÉΓòÉΓòÉ
The attempt to allocate memory for Virtual Boards failed. ODI2NDI.OS2 cannot
function.
The attempts by IBM NetWare Requester Support (ODI2NDI.OS2) to obtain memory
from OS/2 failed.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.206. LT80204 ΓòÉΓòÉΓòÉ
The Link Support Layer (LSL.SYS) is not installed. ODI2NDI.OS2 cannot
function.
The IBM NetWare Requester Support (ODI2NDI.OS2) driver was unable to locate the
LSL support module.
Ensure that the LSL.SYS driver statement is in the CONFIG.SYS file and that it
precedes the ODI2NDI.OS2 driver statement. An example follows:
.
.
.
DEVICE=<path>\LSL.SYS
DEVICE=<path>\DDAEMON.EXE
.
.
.
DEVICE=C:\IBMCOM\ODI2NDI.OS2
.
.
.
DEVICE=<path>\IPX.SYS
.
.
.
Also ensure that the LSL.SYS driver loaded without errors.
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.207. LT80208 ΓòÉΓòÉΓòÉ
An error occurred when ODI2NDI.OS2 tried to set the packet filter for adapter
X. Adapter X cannot be used by ODI2NDI.OS2.
IBM NetWare Requester Support (ODI2NDI.OS2) was unable to specify which frames
to receive.
Some NDIS MAC drivers do not support setting the MAC packet filter. This may
be the case for the NDIS MAC driver that you are using. Also, ensure that the
MAC driver has loaded and initialized properly and that the hardware associated
with the MAC driver is operational. Check for any messages that the MAC driver
may have displayed or logged.
See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG
file.
ΓòÉΓòÉΓòÉ 6.208. LT80209 ΓòÉΓòÉΓòÉ
An error occurred when ODI2NDI.OS2 tried to set the lookahead size for adapter
X. Adapter X cannot be used by ODI2NDI.OS2.
The IBM NetWare Requester Support (ODI2NDI.OS2) has tried to specify the amount
of data in the frame that ODI2NDI.OS2 requires to be available for
interrogation of the frame. This action will ensure that the frame is owned
ODI2NDI.OS2.
Some NDIS MAC drivers do not support the setting of this size. This may be the
case for the NDIS MAC driver that you are using. Also, ensure that the MAC
driver has loaded and initialized properly and that the hardware associated
with the MAC driver is operational. Check for any messages that the MAC driver
may have displayed or logged.
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.209. LT80210 ΓòÉΓòÉΓòÉ
An error occurred when ODI2NDI.OS2 tried to set the node address for adapter X.
Adapter X cannot be used by ODI2NDI.OS2.
The attempt by IBM NetWare Requester Support (ODI2NDI.OS2) to set the node
address for the specified adapter was unsuccessful. This error might occur if
another protocol, for example IBM 802.2, has set the node address to a value
different from the node address configured for ODI2NDI.OS2.
Use the LAPS installation program to ensure that all protocols configured to
use the adapter are configured for the same node address. If the IBM IEEE 802.2
protocol is configured to use the adapter, but only ODI2NDI.OS2 has the node
address configured, ODI2NDI.OS2 should be configured to use the adapter
universal address.
Also, some NDIS MAC drivers do not support the setting of a local address. This
may be the case for the NDIS MAC driver that you are using.
Finally, ensure that the MAC driver has loaded and initialized properly and
that the hardware associated with the MAC driver is operational. Check for any
messages that the MAC driver may have displayed or logged.
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.210. LT80211 ΓòÉΓòÉΓòÉ
An error occurred when ODI2NDI.OS2 tried to open adapter X. Adapter X cannot be
used by ODI2NDI.OS2.
The attempt by IBM NetWare Requester Support (ODI2NDI.OS2) to open the
specified adapter was unsuccessful.
Use the LAPS installation program to ensure that the MAC driver has loaded and
initialized properly. Also verify that the hardware associated with the MAC
driver is operational. Check for any messages that the MAC driver may have
displayed or logged.
See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG
file.
ΓòÉΓòÉΓòÉ 6.211. LT80213 ΓòÉΓòÉΓòÉ
ODI2NDI.OS2 was unable to bind to MAC X. Adapter X cannot be used by
ODI2NDI.OS2.
IBM NetWare Requester Support (ODI2NDI.OS2) has tried bind to the NDIS MAC
driver as specified in the current LAPS configuration but was unsuccessful.
Use the LAPS installation program to ensure that the MAC driver has loaded and
initialized properly. Also verify that the hardware associated with the MAC
driver is operational. Check for any messages that the MAC driver may have
displayed or logged.
See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG
file.
ΓòÉΓòÉΓòÉ 6.212. LT80217 ΓòÉΓòÉΓòÉ
The OpenAdapter request to adapter X did not complete within the required time
limit. Adapter X cannot be used by ODI2NDI.OS2.
IBM NetWare Requester Support (ODI2NDI.OS2) tried to open the specified
adapter, but the open has not yet completed.
Ensure that the MAC driver has loaded and initialized properly and that the
hardware associated with the MAC driver is operational. Check for any messages
that the MAC driver may have displayed or logged.
See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG
file.
ΓòÉΓòÉΓòÉ 6.213. LT80218 ΓòÉΓòÉΓòÉ
There is no section for ODI2NDI.OS2 in PROTOCOL.INI. ODI2NDI.OS2 cannot
function.
IBM NetWare Requester Support (ODI2NDI.OS2) has not been configured in the
current LAPS configuration.
Use the LAPS installation program to configure IBM NetWare Requester Support or
remove the ODI2NDI.OS2 device driver statement from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.214. LT80219 ΓòÉΓòÉΓòÉ
No MAC driver bindings were specified in PROTOCOL.INI. The ODI2NDI.OS2 cannot
function.
IBM NetWare Requester Support (ODI2NDI.OS2) has not been configured in the
current LAPS configuration.
Use the LAPS installation program to configure IBM NetWare Requester Support.
ΓòÉΓòÉΓòÉ 6.215. LT80220 ΓòÉΓòÉΓòÉ
Too many MAC driver bindings were specified in PROTOCOL.INI. ODI2NDI.OS2 cannot
function.
The IBM NetWare Requester Support (ODI2NDI.OS2) was configured for too many
adapters. ODI2NDI.OS2 can be configured for a maximum of 4 adapters.
Use the LAPS installation program to decrease the number of network adapters
for which IBM NetWare Requester Support is configured.
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.216. LT80221 ΓòÉΓòÉΓòÉ
ODI2NDI.OS2 could not locate the Protocol Manager. ODI2NDI.OS2 cannot
function.
The IBM NetWare Requester Support (ODI2NDI.OS2) could not find the protocol
Manager (PROTMAN.OS2).
Ensure that the following statement is in your CONFIG.SYS file:
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.217. LT80222 ΓòÉΓòÉΓòÉ
ODI2NDI.OS2 could not access PROTOCOL.INI. ODI2NDI.OS2 cannot function.
The IBM NetWare Requester Support (ODI2NDI.OS2) either could no find the
PROTOCOL.INI file or encountered an error while trying to open or read this
file.
Use the LAPS installation program to ensure that you have configured at least
one adapter for IBM NetWare Requester Support.
For additional information, see the FFST/2 message log, if you are using
FFST/2, or see the LANTRAN.LOG file.
ΓòÉΓòÉΓòÉ 6.218. LT80223 ΓòÉΓòÉΓòÉ
ODI2NDI.OS2 could not register with the Protocol Manager. ODI2NDI.OS2 cannot
function.
An error occurred when the IBM NetWare Requester Support (ODI2NDI.OS2) tried to
register with the Protocol Manager.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.219. LT80224 ΓòÉΓòÉΓòÉ
Frame type X configured for ODI2NDI.OS2 is inconsistent with other frame types
configured for adapter X. ODI2NDI.OS2 may not function as desired.
The adapter is configured to use both Token-Ring and Ethernet frame types,
which is not allowed.
Use the LAPS installation program to ensure that IBM NetWare Requester Support
for the specified adapter is configured to use either Token Ring frame types or
Ethernet frame types, but not both.
ΓòÉΓòÉΓòÉ 6.220. LT80225 ΓòÉΓòÉΓòÉ
The frame types configured for ODI2NDI.OS2 are not supported by adapter X.
Adapter X cannot be used by ODI2NDI.OS2.
The frame types configured for IBM NetWare Requester Support (ODI2NDI.OS2) are
not compatible with the MAC driver of the specified adapter. For example,
Ethernet frame types have been configured for a Token Ring adapter.
Use the LAPS installation program to ensure that IBM NetWare Requester Support
for the specified adapter is configured to use frame types that are supported
by the adapter.
ΓòÉΓòÉΓòÉ 6.221. LT80226 ΓòÉΓòÉΓòÉ
ODI2NDI.OS2 is configured for an incorrect node address, X. ODI2NDI.OS2 may not
function as desired.
The node address configured for IBM NetWare Requester Support (ODI2NDI.OS2) is
not correct.
Use the LAPS installation program to ensure that IBM NetWare Requester Support
is configured to use a valid node address. A valid node address consists of 12
hexadecimal digits and may be preceded by an I to indicate IEEE node address
format or a T to indicate 802.5 node address format.
ΓòÉΓòÉΓòÉ 6.222. LT80227 ΓòÉΓòÉΓòÉ
A node address was not configured for ODI2NDI.OS2 for adapter X. Adapter X
cannot be used by ODI2NDI.OS2.
The adapter node address was not configured for IBM NetWare Requester Support
(ODI2NDI.OS2). The node address must be configured for ODI2NDI.OS2.
Use the LAPS installation program to ensure that IBM NetWare Requester Support
for the specified adapter has a node address configured.
ΓòÉΓòÉΓòÉ 6.223. LT80250 ΓòÉΓòÉΓòÉ
Too many parameters were specified.
More than one parameter was specified on the NWFIXUP command line.
Specify no more than one parameter for NWFIXUP.
ΓòÉΓòÉΓòÉ 6.224. LT80251 ΓòÉΓòÉΓòÉ
The correct syntax for the command is: Н<path>┘ NWFIXUP Н<filespec>┘
More than one parameter was specified on the NWFIXUP command line.
Specify no more than one parameter for NWFIXUP.
ΓòÉΓòÉΓòÉ 6.225. LT80252 ΓòÉΓòÉΓòÉ
The filespec is not valid.
The filespec supplied as a command-line parameter is not valid. The drive or
path specification was incorrect, or the file could not be found.
Provide a valid filespec as an argument for the command.
ΓòÉΓòÉΓòÉ 6.226. LT80254 ΓòÉΓòÉΓòÉ
NWFIXUP did not complete successfully.
NWFIXUP encountered an error that prevented it from completing all operations
successfully.
See the error message displayed immediately before this one for more detail.
ΓòÉΓòÉΓòÉ 6.227. LT80255 ΓòÉΓòÉΓòÉ
An OS/2 error occurred while querying the current drive.
A call to the OS/2 DosQCurDisk function returned with an error.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.228. LT80256 ΓòÉΓòÉΓòÉ
An OS/2 error occurred during the attempt to query the current directory.
A call to the OS/2 DosQCurDir function returned with an error.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.229. LT80257 ΓòÉΓòÉΓòÉ
An OS/2 error occurred during the attempt to query the boot drive.
A call to the OS/2 DosGetInfoSeg function returned with an error.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.230. LT80258 ΓòÉΓòÉΓòÉ
The CONFIG.SYS file could not be parsed.
An error occurred during the attempt to open the CONFIG.SYS file and read it
into memory.
Ensure that the CONFIG.SYS file being used is not marked as read only and is
not currently in use by any other process. Ensure that enough free memory
(about 128KB) is available to perform the parsing operation.
ΓòÉΓòÉΓòÉ 6.231. LT80259 ΓòÉΓòÉΓòÉ
A DEVICE= statement invoking ODI2NDI.OS2 could not be deleted from the
CONFIG.SYS file.
A line could not be deleted from the parsed CONFIG.SYS file image. The line
contains DEVICE=<path>ODI2NDI.OS2.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.232. LT80260 ΓòÉΓòÉΓòÉ
A DEVICE= statement invoking LSL.SYS was not found.
A line containing DEVICE=<path>LSL.SYS could not be located within the parsed
CONFIG.SYS file image.
Ensure that the correct CONFIG.SYS file is being used. Also, ensure that the
NetWare requester has been installed. If the correct file is being used, and
if it contains the LSL.SYS invocation, contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.233. LT80261 ΓòÉΓòÉΓòÉ
A DEVICE= statement invoking ODI2NDI.OS2 could not be added to the CONFIG.SYS
file.
An error occurred during the attempt to add a line to the parsed CONFIG.SYS
file image. The line contains DEVICE=<path>ODI2NDI.OS2.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.234. LT80262 ΓòÉΓòÉΓòÉ
The MLID device driver could not be disabled in the CONFIG.SYS file.
An error occurred during the attempt to disable a line in the parsed CONFIG.SYS
file image. The REM command could not be prefixed to the line containing
DEVICE=<MLID driver>.
Contact an IBM service representative.
ΓòÉΓòÉΓòÉ 6.235. LT80263 ΓòÉΓòÉΓòÉ
The CONFIG.SYS file image was not written out to disk.
An error occurred during the attempt to replace the CONFIG.SYS file with the
revised version.
Run CHKDSK to determine whether the problem lies with the file system. If no
disk problems are found, contact an IBM service representative.
================================================================================
Note about Standard Microsystems Messages
The messages for the Standard Microsystems and 3Com network adapter
drivers have the same prefix of MAC. The following MAC-prefix messages are
issued by the Standard Microsystems network adapter drivers.
Where Western Digital Corporation was mentioned in previous releases of
LAPS documentation, Standard Microsystems Corporation now provides that
support.
ΓòÉΓòÉΓòÉ 6.236. MAC0001 ΓòÉΓòÉΓòÉ
The WD8003 adapter was either not found or not specified in the PROTOCOL.INI
file.
There were either no entries found in the PROTOCOL.INI file for this device
driver, the adapter is not installed, or there is a hardware problem with the
adapter.
Ensure that a Standard Microsystems Ethernet adapter is installed in this
system, and ensure that a DRIVERNAME= entry exists in the PROTOCOL.INI file
for the MACWD$ or MACWD2$ device driver. Retry the operation. If the problem
persists, contact your vendor service representative.
ΓòÉΓòÉΓòÉ 6.237. MAC0002 ΓòÉΓòÉΓòÉ
The parameters in the PROTOCOL.INI do not match the adapter configuration.
POS data or AT bus software configured adapter data does not match the
PROTOCOL.INI entry.
Correct the PROTOCOL.INI file to ensure that the configuration values specified
correspond to the adapter configuration.
ΓòÉΓòÉΓòÉ 6.238. MAC0003 ΓòÉΓòÉΓòÉ
Multiple WD8003 adapter parameters were specified in the PROTOCOL.INI file.
More than one entry was found in the PROTOCOL.INI file for the MACWD$ or
MACWD2$ device driver.
Ensure that the DRIVERNAME entry appears only once in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.239. MAC0004 ΓòÉΓòÉΓòÉ
The installed WD8003 adapter is not supported.
The adapter installed in this system is not supported by the MAC device driver.
Install a supported version of the adapter.
ΓòÉΓòÉΓòÉ 6.240. MAC0005 ΓòÉΓòÉΓòÉ
A parameter value in the PROTOCOL.INI file is out of range.
One of the parameters in the MACWD$ or MACWD2$ section of the PROTOCOL.INI file
is out of range.
Ensure the parameter values are valid in the PROTOCOL.INI file.
================================================================================
Note about 3Com Messages
The messages for the 3Com and Standard Microsystems network adapter
drivers have the same prefix of MAC. The following MAC-prefix messages are
issued by the 3Com network adapter drivers. There is no online message
help available for the 3Com network adapter drivers.
ΓòÉΓòÉΓòÉ 6.241. MAC0001 ΓòÉΓòÉΓòÉ
Initialization Failure.
The Etherlink II or Etherlink MC driver failed to load. A message specifying
the error displays prior to this message.
Take the action recommended for the specific error message.
ΓòÉΓòÉΓòÉ 6.242. MAC0002 ΓòÉΓòÉΓòÉ
Syntax Error in PROTOCOL.INI.
The value specified in the PROTOCOL.INI file for a given keyword is of the
wrong type. Either the value is a string and should be a number or it is a
number and should be a string.
Correct the value in the PROTOCOL.INI file. If the value should be a
hexadecimal number, ensure that it is prefixed with '0x'. Check for the
possibility that the driver has selected the wrong section of the PROTOCOL.INI
file and is trying to interpret parameters that apply to some other driver.
This could happen if the DriverName = lines are not correct. Check that the
indicated section of the PROTOCOL.INI file is the one you intend the driver to
use.
ΓòÉΓòÉΓòÉ 6.243. MAC0003 ΓòÉΓòÉΓòÉ
Syntax Error in PROTOCOL.INI - Driver Name Not Found.
The driver has looked at all of the PROTOCOL.INI file and found no section in
which the DriverName = line specified ELNKII$, or ELNKMC$, or any of the other
valid variants of a ELNK driver name.
Check the DriverName = lines in the PROTOCOL.INI file. Check that you have the
right PROTOCOL.INI file in the directory PROTMAN is using. The correct
directory is configuration-dependent. It may be specified by a /I:path
parameter on the DEVICE=...PROTMAN.... line in the CONFIG.SYS file. If not, it
is probably \IBMCOM.
ΓòÉΓòÉΓòÉ 6.244. MAC0004 ΓòÉΓòÉΓòÉ
Syntax Error in PROTOCOL.INI - Invalid Parameter Value.
The value specified in the PROTOCOL.INI file for a given keyword is not within
the allowed range for that keyword.
Correct the value in the PROTOCOL.INI file. Check all values to ensure that
they are within the allowed range for that keyword. Check for the possibility
that the driver has selected the wrong section of the PROTOCOL.INI file and is
trying to interpret parameters that apply to some other driver. This could
happen if the DriverName = lines are not correct. Check that the indicated
section of the PROTOCOL.INI file is the one you intend the driver to use.
ΓòÉΓòÉΓòÉ 6.245. MAC0005 ΓòÉΓòÉΓòÉ
Syntax error in PROTOCOL.INI - unrecognized keyword.
The driver has encountered a parameter keyword in the PROTOCOL.INI file that it
does not understand.
Edit the PROTOCOL.INI file. Find the indicated section. Within that section,
find the parameter line that starts with the given parameter keyword. Decide
what is wrong with the line. The keyword may be misspelled, or the line may
not belong in this section. It may be a comment line whose initial semicolon
(;) is missing. Correct the keyword or delete the line. Check for the
possibility that the driver has selected the wrong section of the PROTOCOL.INI
file and is trying to interpret parameter keywords that apply to some other
driver. This could happen if the DriverName = lines are not correct. Check
that the indicated section of the PROTOCOL.INI file is the one you intend the
driver to use.
ΓòÉΓòÉΓòÉ 6.246. MAC0006 ΓòÉΓòÉΓòÉ
Network interface hardware not found or not responding.
The driver could not find an Etherlink II or Etherlink MC network adapter card.
Check to ensure that there is an Etherlink network adapter card present. If
the Slotnumber parameter is used in the PROTOCOL.INI file, ensure that it
contains a valid slot number.
ΓòÉΓòÉΓòÉ 6.247. MAC0007 ΓòÉΓòÉΓòÉ
IOBASE in PROTOCOL.INI conflicts with the configured IOBASE.
The IOBASE parameter in the PROTOCOL.INI file conflicts with the IO Base
address on the Etherlink II network adapter card.
Change the IOBASE parameter in the PROTOCOL.INI file to match the IO Base
address on the network adapter card.
ΓòÉΓòÉΓòÉ 6.248. MPT0001 ΓòÉΓòÉΓòÉ
A transport services provider must be selected.
ΓòÉΓòÉΓòÉ 6.249. MPT0002 ΓòÉΓòÉΓòÉ
A TCP/IP configuration option must be selected.
ΓòÉΓòÉΓòÉ 6.250. MPT0003 ΓòÉΓòÉΓòÉ
Please make the appropriate selection from the menu.
ΓòÉΓòÉΓòÉ 6.251. MPT0004 ΓòÉΓòÉΓòÉ
One or more required parameters are missing.
ΓòÉΓòÉΓòÉ 6.252. MPT0005 ΓòÉΓòÉΓòÉ
Configure another non-native NetBIOS command sequence.
ΓòÉΓòÉΓòÉ 6.253. MPT0006 ΓòÉΓòÉΓòÉ
The IPC configuration process has completed.
ΓòÉΓòÉΓòÉ 6.254. MPT0007 ΓòÉΓòÉΓòÉ
Do you want to save the entered Socket/MPTS configuration data?
ΓòÉΓòÉΓòÉ 6.255. MPT0008 ΓòÉΓòÉΓòÉ
Check only one selection on the menu.
ΓòÉΓòÉΓòÉ 6.256. MPT0009 ΓòÉΓòÉΓòÉ
Problems were encountered while updating the Interm file (MPTCONFG.INI).
ΓòÉΓòÉΓòÉ 6.257. MPT0010 ΓòÉΓòÉΓòÉ
Problems were encountered while updating the MPTStart file (MPTSTART.CMD).
ΓòÉΓòÉΓòÉ 6.258. MPT0011 ΓòÉΓòÉΓòÉ
Problems were encountered while updating the MPTSetup file (MPTSETUP.CMD).
ΓòÉΓòÉΓòÉ 6.259. MPT0012 ΓòÉΓòÉΓòÉ
The selected LAN Adapter Information was saved.
ΓòÉΓòÉΓòÉ 6.260. MPT0013 ΓòÉΓòÉΓòÉ
Select one of the transport services providers.
ΓòÉΓòÉΓòÉ 6.261. MPT0014 ΓòÉΓòÉΓòÉ
Do you want to exit the TCP/IP configuration?
ΓòÉΓòÉΓòÉ 6.262. MPT0015 ΓòÉΓòÉΓòÉ
Please select the appropriate information.
ΓòÉΓòÉΓòÉ 6.263. MPT0016 ΓòÉΓòÉΓòÉ
Do you want to delete the selected information?
ΓòÉΓòÉΓòÉ 6.264. MPT0017 ΓòÉΓòÉΓòÉ
Do you want to exit the NetBIOS configuration?
ΓòÉΓòÉΓòÉ 6.265. MPT0019 ΓòÉΓòÉΓòÉ
A valid family was not selected. Choose either nb or inet.
ΓòÉΓòÉΓòÉ 6.266. MPT0020 ΓòÉΓòÉΓòÉ
A valid nb address was not entered. The first digit cannot be an asterisk.
ΓòÉΓòÉΓòÉ 6.267. MPT0021 ΓòÉΓòÉΓòÉ
A valid nb address is outside the range of 1 to 16 bytes.
ΓòÉΓòÉΓòÉ 6.268. MPT0022 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. The inet address is outside the range of
0 to 255.
ΓòÉΓòÉΓòÉ 6.269. MPT0023 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. The inet address can only contain up to
four sections.
ΓòÉΓòÉΓòÉ 6.270. MPT0024 ΓòÉΓòÉΓòÉ
The family field is missing.
ΓòÉΓòÉΓòÉ 6.271. MPT0025 ΓòÉΓòÉΓòÉ
A required address field is missing.
ΓòÉΓòÉΓòÉ 6.272. MPT0026 ΓòÉΓòÉΓòÉ
The route type is missing.
ΓòÉΓòÉΓòÉ 6.273. MPT0027 ΓòÉΓòÉΓòÉ
A valid route type was not entered. Please enter default, net, subnet, or
host.
ΓòÉΓòÉΓòÉ 6.274. MPT0028 ΓòÉΓòÉΓòÉ
The Route destination field is missing.
ΓòÉΓòÉΓòÉ 6.275. MPT0029 ΓòÉΓòÉΓòÉ
The Route field is missing.
ΓòÉΓòÉΓòÉ 6.276. MPT0030 ΓòÉΓòÉΓòÉ
A valid metric value was not entered. The metric value should be between 0 and
15.
ΓòÉΓòÉΓòÉ 6.277. MPT0031 ΓòÉΓòÉΓòÉ
A valid adapter number was not entered. The adapter number should be between 0
and 15.
ΓòÉΓòÉΓòÉ 6.278. MPT0032 ΓòÉΓòÉΓòÉ
A program error has occurred. Call your technical support.
ΓòÉΓòÉΓòÉ 6.279. MPT0033 ΓòÉΓòÉΓòÉ
A valid type selection was not made. Select either Default or Network.
ΓòÉΓòÉΓòÉ 6.280. MPT0034 ΓòÉΓòÉΓòÉ
The maximum transmission unit (MTU) is missing.
ΓòÉΓòÉΓòÉ 6.281. MPT0035 ΓòÉΓòÉΓòÉ
A valid maximum transmission unit (MTU) name was not entered.
ΓòÉΓòÉΓòÉ 6.282. MPT0036 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. The address contains data that is not
valid.
ΓòÉΓòÉΓòÉ 6.283. MPT0037 ΓòÉΓòÉΓòÉ
The native NetBIOS configuration process has completed.
ΓòÉΓòÉΓòÉ 6.284. MPT0038 ΓòÉΓòÉΓòÉ
The Broadcast address field is missing.
ΓòÉΓòÉΓòÉ 6.285. MPT0039 ΓòÉΓòÉΓòÉ
The Socket/MPTS User address field is missing.
ΓòÉΓòÉΓòÉ 6.286. MPT0040 ΓòÉΓòÉΓòÉ
The Socket/MPTS Provider address field is missing.
ΓòÉΓòÉΓòÉ 6.287. MPT0041 ΓòÉΓòÉΓòÉ
The IP address field is missing.
ΓòÉΓòÉΓòÉ 6.288. MPT0042 ΓòÉΓòÉΓòÉ
The Subnet Mask address field is missing.
ΓòÉΓòÉΓòÉ 6.289. MPT0043 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. The address contained too many periods.
ΓòÉΓòÉΓòÉ 6.290. MPT0044 ΓòÉΓòÉΓòÉ
The adapter address cannot contain alphabetic characters.
ΓòÉΓòÉΓòÉ 6.291. MPT0045 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. A period is the first character.
ΓòÉΓòÉΓòÉ 6.292. MPT0046 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. A period is the last character.
ΓòÉΓòÉΓòÉ 6.293. MPT0047 ΓòÉΓòÉΓòÉ
A valid nb address was not entered. A period is the first character.
ΓòÉΓòÉΓòÉ 6.294. MPT0048 ΓòÉΓòÉΓòÉ
A valid nb address was not entered. The address contains too many periods.
ΓòÉΓòÉΓòÉ 6.295. MPT0049 ΓòÉΓòÉΓòÉ
A valid nb address was not entered. The address contains no periods.
ΓòÉΓòÉΓòÉ 6.296. MPT0050 ΓòÉΓòÉΓòÉ
A valid inet address was not entered. The address contains no periods.
ΓòÉΓòÉΓòÉ 6.297. MPT0051 ΓòÉΓòÉΓòÉ
If any new data or changed data, or both, has been entered, it will not be
saved. Do you still want to cancel?
ΓòÉΓòÉΓòÉ 6.298. MPT0052 ΓòÉΓòÉΓòÉ
The local preference list information is required.
ΓòÉΓòÉΓòÉ 6.299. MPT0053 ΓòÉΓòÉΓòÉ
The LAN Adapter has previously been selected. Make a new selection.
ΓòÉΓòÉΓòÉ 6.300. MPT0054 ΓòÉΓòÉΓòÉ
Problems were encountered while opening the Interm file (MPTCOMFG.INI).
ΓòÉΓòÉΓòÉ 6.301. MPT0055 ΓòÉΓòÉΓòÉ
Do you really want to remove the TCP/IP access configuration information?
ΓòÉΓòÉΓòÉ 6.302. MPT0056 ΓòÉΓòÉΓòÉ
Do you really want to remove the NetBIOS access configuration information?
ΓòÉΓòÉΓòÉ 6.303. MPT0057 ΓòÉΓòÉΓòÉ
Select the appropriate configuration process for removal.
ΓòÉΓòÉΓòÉ 6.304. MPT0058 ΓòÉΓòÉΓòÉ
Do you really want to remove the IPC access configuration information?
ΓòÉΓòÉΓòÉ 6.305. MPT0059 ΓòÉΓòÉΓòÉ
TCP/IP protocol is not configured. Return to LAPS to configure this protocol.
ΓòÉΓòÉΓòÉ 6.306. MPT0060 ΓòÉΓòÉΓòÉ
NetBIOS protocol is not configured. Return to LAPS to configure this protocol.
ΓòÉΓòÉΓòÉ 6.307. MPT0061 ΓòÉΓòÉΓòÉ
You must configure TCP/IP before configuring Socket/MPTS.
ΓòÉΓòÉΓòÉ 6.308. MPT0062 ΓòÉΓòÉΓòÉ
The TCP/IP configuration process has completed.
ΓòÉΓòÉΓòÉ 6.309. MPT0063 ΓòÉΓòÉΓòÉ
A valid nb address was not entered.
ΓòÉΓòÉΓòÉ 6.310. MPT0064 ΓòÉΓòÉΓòÉ
Do you want to exit the Socket/MPTS configuration?
ΓòÉΓòÉΓòÉ 6.311. MPT0065 ΓòÉΓòÉΓòÉ
Problems were encountered while opening the Interim file (MPTCONFG.INI).
ΓòÉΓòÉΓòÉ 6.312. MPT0066 ΓòÉΓòÉΓòÉ
Only one default type can be selected per machine. Make another selection.
ΓòÉΓòÉΓòÉ 6.313. MPT0067 ΓòÉΓòÉΓòÉ
You can only enter an existing nb address. Select an nb address from the list
of nb addresses.
ΓòÉΓòÉΓòÉ 6.314. MPT0068 ΓòÉΓòÉΓòÉ
This Multi-Protocol Transport Services protocol address cannot be deleted
because of an existing local preference list.
ΓòÉΓòÉΓòÉ 6.315. MPT0069 ΓòÉΓòÉΓòÉ
A valid hostname was not entered. The name must be a single section or four
sections separated with periods.
ΓòÉΓòÉΓòÉ 6.316. MPT0070 ΓòÉΓòÉΓòÉ
A valid domain name was not entered. The name must contain three sections
separated with periods.
ΓòÉΓòÉΓòÉ 6.317. MPT0071 ΓòÉΓòÉΓòÉ
Do you really want to delete this nameserver statement?
ΓòÉΓòÉΓòÉ 6.318. MPT0072 ΓòÉΓòÉΓòÉ
The maximum number of nameservers are configured.
ΓòÉΓòÉΓòÉ 6.319. MPT0073 ΓòÉΓòÉΓòÉ
You have entered a duplicate NetBIOS address.
ΓòÉΓòÉΓòÉ 6.320. PRO0002 ΓòÉΓòÉΓòÉ
PROTOCOL.INI could not be read.
A drive or data error occurred when the program attempted to read the
PROTOCOL.INI file.
If the PROTOCOL.INI file is being read from a diskette, ensure that the
diskette is properly inserted into the drive and that the drive door is closed.
If the PROTOCOL.INI file is being read from a fixed disk, re-create the
PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.321. PRO0003 ΓòÉΓòÉΓòÉ
PROTOCOL.INI could not be opened.
One of the following conditions caused an error to occur when the program
attempted to open the PROTOCOL.INI file:
o The file could not be found in the default directory \IBMCOM or in the
directory specified on the DEVICE= command following the /I: option switch.
o The file is damaged.
Re-install the network drivers and protocol manager.
If the PROTOCOL.INI file is being read from a diskette drive, ensure that the
diskette is inserted properly and that the drive door is closed.
ΓòÉΓòÉΓòÉ 6.322. PRO0004 ΓòÉΓòÉΓòÉ
The unrecognized parameter X was found in PROTOCOL.INI.
A configuration parameter is defined in the PROTOCOL.INI file that is not
associated with a logical module. The parameter may be out of order.
Review the PROTOCOL.INI file and ensure that all configuration parameters
appear under the appropriate logical module name and are enclosed in brackets.
ΓòÉΓòÉΓòÉ 6.323. PRO0005 ΓòÉΓòÉΓòÉ
System resources are not available to hold PROTOCOL.INI.
The system does not have enough memory to hold the the PROTOCOL.INI file image.
Reduce the size of the PROTOCOL.INI file or add more memory and retry the
operation.
ΓòÉΓòÉΓòÉ 6.324. PRO0006 ΓòÉΓòÉΓòÉ
The numeric value specified for configuration parameter X in PROTOCOL.INI is
not valid.
The numeric value of the configuration parameter exceeds 2**32 or the network
address value is not valid.
Review the PROTOCOL.INI file and ensure that all numeric values for
configuration parameters are less than 2**32 (4,294,967,296 decimal or
100,000,000 hexadecimal).
ΓòÉΓòÉΓòÉ 6.325. PRO0007 ΓòÉΓòÉΓòÉ
The value specified in keyword X is not a valid hexadecimal number.
An incorrect character was specified in a hexadecimal number.
Review the PROTOCOL.INI file to determine the parameter that contains the
incorrect hexadecimal number. Hexadecimal numbers can consist of the digits 0
through 9 only and the letters A through F (uppercase or lowercase).
Hexadecimal values always begin with the prefix 0x or 0X.
ΓòÉΓòÉΓòÉ 6.326. PRO0008 ΓòÉΓòÉΓòÉ
A numeric value specified in keyword X in PROTOCOL.INI is not a valid number.
An incorrect character was specified in a numeric field.
Review the PROTOCOL.INI file to determine the parameter that contains the
incorrect number. Numeric values can consist of digits 0 through 9 only.
ΓòÉΓòÉΓòÉ 6.327. PRO0009 ΓòÉΓòÉΓòÉ
The end double quotation mark is missing for keyword X in PROTOCOL.INI.
A character string that begins with a double quotation mark is not ended with
one on the same line.
Find the character string in the PROTOCOL.INI file and end it with a double
quotation mark.
ΓòÉΓòÉΓòÉ 6.328. PRO0010 ΓòÉΓòÉΓòÉ
The option specified is not valid.
The only valid option on the DEVICE=path\PROTMAN.OS2 line must begin with /I:
or /i:. If a device and path name are specified, that value overrides the
default path \IBMCOM in locating the PROTOCOL.INI file.
Correct the option and try the operation again.
ΓòÉΓòÉΓòÉ 6.329. PRO0011 ΓòÉΓòÉΓòÉ
An equal sign was not found following keyword X.
A configuration keyword that requires a value must be followed by an equal sign
and value in the PROTOCOL.INI file.
Correct the parameter and retry the operation.
ΓòÉΓòÉΓòÉ 6.330. PRO0012 ΓòÉΓòÉΓòÉ
An unrecoverable error occurred during initialization.
An internal software error occurred during OS/2 Protocol Manager
initialization.
Contact your vendor sales representative.
ΓòÉΓòÉΓòÉ 6.331. PRO0021 ΓòÉΓòÉΓòÉ
A general failure occurred when the program tried to bind X to X.
A general failure error code (0xFF) was returned during the binding process.
Re-install the OS/2 Protocol Manager and try the operation again.
ΓòÉΓòÉΓòÉ 6.332. PRO0022 ΓòÉΓòÉΓòÉ
An unspecified failure error occurred when the program tried to bind X to X.
A unspecified failure error code was returned during the binding process.
Re-install the OS/2 Protocol Manager and try the operation again.
ΓòÉΓòÉΓòÉ 6.333. PRO0023 ΓòÉΓòÉΓòÉ
The protocol manager could not be found.
The protocol manager could not be found for one of the following reasons:
o The protocol manager failed to properly install.
o The NETBIND command was issued from the compatibility mode of OS/2.
Re-install the protocol manager and retry the operation, or run the NETBIND
command from the OS/2 protect mode.
ΓòÉΓòÉΓòÉ 6.334. PRO0024 ΓòÉΓòÉΓòÉ
The NETBIND command has already been processed.
The NETBIND command was requested after the network was active.
No action is necessary; the command will be discarded.
ΓòÉΓòÉΓòÉ 6.335. PRO0025 ΓòÉΓòÉΓòÉ
An error occurred when the program tried to bind X to X.
An error condition was returned from a request to bind. The possible causes
are:
o The protocol/mac driver statements are not correctly specified in the
CONFIG.SYS file, or the protocol/mac drivers failed during the system
startup.
o The protocol/mac drivers have incorrect binding information in the
PROTOCOL.INI file.
Review the PROTOCOL.INI file to determine whether the module names specified
in the binding list match the module names enclosed in brackets. Check that
the required protocol/mac driver statements are included in the CONFIG.SYS
file.
ΓòÉΓòÉΓòÉ 6.336. PRO0026 ΓòÉΓòÉΓòÉ
The media access control (MAC) driver is not registered or cannot be found.
The request to bind X to X cannot be completed.
The MAC driver is not registered or cannot be found. The request to bind the
protocol driver to the MAC was not successful.
Check for additional messages from the MAC driver indicating an error, and
check the bindings list in the PROTOCOL.INI file for an incorrect name.
Correct the error and try the operation again.
ΓòÉΓòÉΓòÉ 6.337. PRO0027 ΓòÉΓòÉΓòÉ
The adapter was not found when the program tried to bind X to X.
There was no adapter found in this machine to satisfy the bind request.
Install an adapter in this machine or remove the device driver statement.
ΓòÉΓòÉΓòÉ 6.338. PRO0028 ΓòÉΓòÉΓòÉ
A hardware failure occurred when the program tried to bind X to X.
An unexpected hardware failure occurred when the protocol manager tried to bind
the media access control (MAC) driver.
Run the hardware diagnostics for the indicated adapter. Contact your vendor
sales representative.
ΓòÉΓòÉΓòÉ 6.339. PRO0029 ΓòÉΓòÉΓòÉ
A configuration parameter failure occurred when the program tried to bind X to
X.
Certain configuration parameters are unacceptable to either the media access
control (MAC) driver or the protocol manager.
Check for additional messages from the MAC driver and correct the syntax
problem in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.340. PRO0030 ΓòÉΓòÉΓòÉ
Multiple adapters are trying to use the same interrupt level. The request to
bind X to X cannot be completed.
Multiple adapters have been set to use the same interrupt level when 1 or more
adapters do not share interrupts, causing an unrecoverable conflict.
Run the hardware diagnostics for the adapters and correct the interrupt
conflict. Correct the option and try the operation again.
ΓòÉΓòÉΓòÉ 6.341. PRO0031 ΓòÉΓòÉΓòÉ
The version of the media access control (MAC) driver installed is not supported
by the protocol manager. The request to bind X to X cannot be completed. An
equal sign was not found following keyword X.
A down-level or unsupported version of the MAC driver is installed on this
machine.
Install the supported version of the MAC driver.
ΓòÉΓòÉΓòÉ 6.342. PRO0032 ΓòÉΓòÉΓòÉ
A media access control (MAC) driver initialization failure has occurred. The
request to bind X to X cannot be completed.
A parameter configured in the PROTOCOL.INI file is not valid.
Check for additional messages from the MAC driver indicating an error and check
the bindings list in the PROTOCOL.INI file for an incorrect name. Correct the
error and try the operation again.
ΓòÉΓòÉΓòÉ 6.343. PRO0033 ΓòÉΓòÉΓòÉ
The binding of the media access control (MAC) driver was not successful.
The possible causes are:
o A protocol/MAC driver failed during system startup.
o A protocol/MAC driver has incorrect binding information.
If the error was caused by a failed driver, correct the problem and try the
operation again.
ΓòÉΓòÉΓòÉ 6.344. UBI0004 ΓòÉΓòÉΓòÉ
X initialization failed.
The driver encountered an error during its initialization. A message specifying
the error displays prior to this message.
Take the action recommended for the specific error message.
ΓòÉΓòÉΓòÉ 6.345. UBI0005 ΓòÉΓòÉΓòÉ
The driver's call to the GetDOSVar DevHlp system call failed.
The OS/2 GetDOSVar DevHlp system call failed. The driver cannot proceed with
its initialization. The OS/2 system may not be configured properly, or the
file that starts the driver (UBNEI.OS2) may be corrupted.
Verify that the system is configured properly. Verify that the system is
otherwise functioning correctly. Try using another copy of the UBNEI.OS2 file.
ΓòÉΓòÉΓòÉ 6.346. UBI0006 ΓòÉΓòÉΓòÉ
No Protocol Manager driver (PROTMAN$) is installed.
The driver was unable to open \DEV\PROTMAN$.
The Protocol Manager driver (PROTMAN) must be successfully installed before
UBNEI is installed. Make sure that the CONFIG.SYS file contains a DEVICE= line
that loads the PROTMAN driver, and make sure that this line comes before the
DEVICE= line that loads UBNEI. Verify that the PROTMAN driver loads
successfully. Check for error messages from the PROTMAN driver during its
loading.
ΓòÉΓòÉΓòÉ 6.347. UBI0007 ΓòÉΓòÉΓòÉ
There is no PROTOCOL.INI information at all.
The driver call to the GetProtocolManagerInfo function of the PROTMAN$ driver
failed. A possible cause may be that the PROTMAN driver could not find the
PROTOCOL.INI file.
Make sure that the PROTOCOL.INI file is in the directory PROTMAN expects it to
be in. The correct directory is configuration-dependent. It may be specified
by a /I:path parameter on the DEVICE=...PROTMAN... line in the CONFIG.SYS file.
If not, it is probably \IBMCOM.
ΓòÉΓòÉΓòÉ 6.348. UBI0008 ΓòÉΓòÉΓòÉ
There is no section in PROTOCOL.INI with DriverName equal to X$, or to Xn$, n =
2, ..., 9.
The driver has looked at all of the PROTOCOL.INI file and found no section
where the DriverName = line specified UBNEI$, or UBNEI2$, or any of the other
valid variants of a UBNEI driver name.
Check the DriverName = lines in the PROTOCOL.INI file. Check that you have the
right PROTOCOL.INI file in the directory PROTMAN is using. The correct
directory is configuration-dependent. It may be specified by a /I:path
parameter on the DEVICE=...PROTMAN... line in the CONFIG.SYS file. If not, it
is probably \IBMCOM.
ΓòÉΓòÉΓòÉ 6.349. UBI0009 ΓòÉΓòÉΓòÉ
There is no section in PROTOCOL.INI with DriverName equal to X$.
The driver has checked the PROTOCOL.INI file and found no section where the
DriverName = line specified its driver name.
Check the DriverName = lines in the PROTOCOL.INI file. Check that you have the
right PROTOCOL.INI file in the directory PROTMAN is using. The correct
directory is configuration-dependent. It may be specified by a /I:path
parameter on the DEVICE=...PROTMAN... line in the CONFIG.SYS file. If not, it
is probably \IBMCOM.
ΓòÉΓòÉΓòÉ 6.350. UBI0010 ΓòÉΓòÉΓòÉ
X is already installed.
A driver with the specified name is already installed. The probable cause of
this error is that the CONFIG.SYS file contains two lines that say
DEVICE=...UBNEI... but the PROTOCOL.INI file contains only one section with a
UBNEI DriverName line.
If you want to load multiple copies of the UBNEI driver, you must put a
separate section for each of them in the PROTOCOL.INI file. If you do not want
to load multiple copies of the driver, you should delete all but one of the
DEVICE=...UBNEI... lines from the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.351. UBI0011 ΓòÉΓòÉΓòÉ
The X X drivers called for by PROTOCOL.INI are already installed.
The driver checked the PROTOCOL.INI file and found X sections in which the
DriverName = line specifies UBNEI$, UBNEI2$, or one of the other variants of
its name, but a driver with each of these names is already installed. There is
a discrepancy between the CONFIG.SYS and PROTOCOL.INI files. The CONFIG.SYS
file contains more DEVICE=...UBNEI... lines than the number of sections in the
PROTOCOL.INI file that specify DriverName = UBNEI$ (or UBNEI2$, and so on).
Either delete one of the DEVICE= lines or add another UBNEI section to the
PROTOCOL.INI file. If you have the right number of sections, check that each
of their DriverName = lines specifies a different variant of the driver name.
ΓòÉΓòÉΓòÉ 6.352. UBI0012 ΓòÉΓòÉΓòÉ
The parameter keyword "X" in the НX┘ section of PROTOCOL.INI is misspelled, or
not supported by X.
The driver has encountered a PROTOCOL.INI parameter keyword that it does not
understand.
Edit the PROTOCOL.INI file. Find the indicated section. Within that section,
find the parameter line that starts with the given parameter keyword. Decide
what is wrong with the line. The keyword may be misspelled, or the line may
not belong in this section. It may be a comment line whose initial ';' is
missing. Correct the keyword or delete the line.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameter keywords that apply to
some other driver. This could happen if the DriverName = lines are not
correct. Check that the indicated section of the PROTOCOL.INI file is the one
you intend the driver to use.
ΓòÉΓòÉΓòÉ 6.353. UBI0013 ΓòÉΓòÉΓòÉ
Too many parameter values are specified for "X" in the НX┘ section of
PROTOCOL.INI.
The PROTOCOL.INI line containing the given keyword specifies too many values.
Correct the line in the PROTOCOL.INI file. Ensure that there are no extra
characters between the '=' sign and the parameter value, or after the value.
Also ensure that there are no spaces, tabs, commas, or semicolons within the
parameter value.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameters that apply to some
other driver. This could happen if the DriverName = lines are not correct.
Check that the indicated section of the PROTOCOL.INI file is the one you intend
the driver to use.
ΓòÉΓòÉΓòÉ 6.354. UBI0014 ΓòÉΓòÉΓòÉ
The type of value given for "X" in the НX┘ section of PROTOCOL.INI is wrong.
The value specified in the PROTOCOL.INI file for the given keyword is of the
wrong type. Either the value is a string and should be a number, or it is a
number and should be a string.
Correct the value in the PROTOCOL.INI file. If the value should be a
hexadecimal number, make sure it is prefixed with '0x'.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameters that apply to some
other driver. This could happen if the DriverName = lines are not correct.
Check that the indicated section of the PROTOCOL.INI file is the one you intend
the driver to use.
ΓòÉΓòÉΓòÉ 6.355. UBI0015 ΓòÉΓòÉΓòÉ
The value given for "X" in the НX┘ section of PROTOCOL.INI is too large for X.
The value given in the PROTOCOL.INI file for the specified parameter is larger
than the maximum value the driver supports.
Correct the value in the PROTOCOL.INI file.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameters that apply to some
other driver. This could happen if the DriverName = lines are not correct.
Check that the indicated section of the PROTOCOL.INI file is the one you intend
the driver to use.
ΓòÉΓòÉΓòÉ 6.356. UBI0016 ΓòÉΓòÉΓòÉ
The value given for "X" in the НX┘ section of PROTOCOL.INI is too small for X.
The value given in the PROTOCOL.INI file for the specified parameter is smaller
than the minimum value the driver supports.
Correct the value in the PROTOCOL.INI file.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameters that apply to some
other driver. This could happen if the DriverName = lines are not correct.
Check that the indicated section of the PROTOCOL.INI file is the one you intend
the driver to use.
ΓòÉΓòÉΓòÉ 6.357. UBI0017 ΓòÉΓòÉΓòÉ
A bad parameter value is given for "X" in the НX┘ section of PROTOCOL.INI.
The value given in the PROTOCOL.INI file for the specified parameter s not
valid. If the value is a string, it is not one of the strings the driver
expects for this parameter. If the value is a number, it fails to meet some
special requirement for this parameter. Examples of special requirements are:
the value of ReceiveBufSize must be even; the last 4 digits of the hexadecimal
value of MemoryWindow must be 0000 or 8000; the last digit of the hexadecimal
value of IO_Port must be 0 or 8.
Correct the value in the PROTOCOL.INI file. Check the spelling of string
parameter values.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameters that apply to some
other driver. This could happen if the DriverName = lines are not correct.
Check that the indicated section of the PROTOCOL.INI file is the one you intend
the driver to use.
ΓòÉΓòÉΓòÉ 6.358. UBI0018 ΓòÉΓòÉΓòÉ
The value specified for "X" in the НX┘ section of PROTOCOL.INI is too long.
The string value specified in the PROTOCOL.INI file for the parameter keyword
given in the message contains too many characters.
Correct the value in the PROTOCOL.INI file.
Check for the possibility that the driver has selected the wrong section of the
PROTOCOL.INI file and is trying to interpret parameters that apply to some
other driver. This could happen if the DriverName = lines are not correct.
Check that the indicated section of the PROTOCOL.INI file is the one you intend
the driver to use.
ΓòÉΓòÉΓòÉ 6.359. UBI0019 ΓòÉΓòÉΓòÉ
GDT selector allocation failed.
The OS/2 AllocateGDTSelector DevHlp system call failed when the driver tried to
get the two GDT selectors it needs for referencing the adapter memory and for
referencing buffers passed to it by the physical address. The OS/2 system may
not be configured properly or may be corrupted. The file that runs the driver
(UBNEI.OS2) may be corrupted.
Verify that the system otherwise functions correctly. Try using another copy
of the UBNEI.OS2 file.
ΓòÉΓòÉΓòÉ 6.360. UBI0020 ΓòÉΓòÉΓòÉ
Conversion of the adapter memory window address to a GDT virtual address
failed.
The OS/2 PhysToGDTSelector DevHlp system call failed when the driver tried to
set up the GDT selector it uses to reference the adapter memory. The OS/2
system may not be configured properly or may be corrupted. The file that runs
the driver (UBNEI.OS2) may be corrupted.
Verify that the system otherwise functions correctly. Try using another copy
of the UBNEI.OS2 file. Check the value of the MemoryWindow parameter in the
PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.361. UBI0021 ΓòÉΓòÉΓòÉ
Conversion of the NIU memory window address to a virtual address failed.
The OS/2 PhysToVirt DevHlp system call failed when the driver tried to convert
the physical address of the adapter memory window to a virtual address. The
OS/2 system may not be configured properly or may be corrupted. The file that
runs the driver (UBNEI.OS2) may be corrupted.
Verify that the system otherwise functions correctly. Try using another copy
of the UBNEI.OS2 file. Check the value of the MemoryWindow parameter in the
PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 6.362. UBI0022 ΓòÉΓòÉΓòÉ
Slot X does not contain an NIUps adapter.
Either there is no adapter in the given slot, or the adapter in that slot is
not an NIUps.
Determine manually or by using the PS/2 hardware configuration utilities (the
programs on the Reference Diskette) the slot that the NIUps is in. Change the
SlotNumber = line to specify the correct slot. Note that, unless you have more
than one NIUps in your PS/2, it is not necessary to specify the SlotNumber =
parameter. The driver automatically finds the right slot.
ΓòÉΓòÉΓòÉ 6.363. UBI0023 ΓòÉΓòÉΓòÉ
The NIUps in slot X is not enabled.
There is an NIUps adapter in the slot specified by the SlotNumber = line, but
the adapter is disabled.
Verify that the SlotNumber = line is correct. Use the PS/2 hardware
configuration utilities (the programs on the Reference Diskette) to enable the
NIUps adapter in the specified slot.
ΓòÉΓòÉΓòÉ 6.364. UBI0024 ΓòÉΓòÉΓòÉ
Either there are no enabled NIUps adapters, or they are all reserved by other X
drivers.
The driver cannot find an NIUps adapter to use. There may be no NIUps adapters
installed. An adapter may be installed, but not enabled. An enabled adapter
may be present, but it may have been reserved by a previously installed
instance of the driver.
Verify that you have installed the NIUps adapter. Use the PS/2 hardware
configuration utilities (the programs on the Reference Diskette) to verify that
the adapter is enabled. Check for a discrepancy between the CONFIG.SYS file and
your adapter hardware configuration. The CONFIG.SYS file may contain extra
DEVICE=...UBNEI... lines, that is, more than the number of NIUps adapters that
are installed.
ΓòÉΓòÉΓòÉ 6.365. UBI0025 ΓòÉΓòÉΓòÉ
The NIUps is configured for an illegal window size.
The window size configuration of the NIUps adapter is not valid. Window size
configuration is done using the PS/2 hardware configuration utilities (the
programs on the Reference Diskette), based on information in the @7012.ADF file
that comes with the NIUps. A good @7012.ADF file does not allow an invalid
window size to be configured.
Try using the Reference Diskette programs to set the window size again. The
item you change to do this is Shared RAM PS/2 Memory Address Range. Change this
item to a different value and then change it back to the one you want. Or leave
it at the different value if you can.
Try removing the NIUps adapter and re-installing it. Try putting it in a
different slot. Try recopying @7012.ADF from the original diskette. Try using a
fresh copy of the UBNEI.OS2 file.
ΓòÉΓòÉΓòÉ 6.366. UBI0026 ΓòÉΓòÉΓòÉ
The NIU failed its diagnostic tests. Please check the network connection,
configuration parameters, and hardware installation.
Either the built-in diagnostic tests of the adapter failed, or there is some
problem in the communication between the adapter and the driver. There may be a
problem with the adapter hardware, or there may be a problem with the adapter
network cable connection or with its configuration or with parameters in the
PROTOCOL.INI file.
Check that the adapter is properly connected to its network cable. Verify that
the AdapterType parameter value in the PROTOCOL.INI file is correct for your
adapter. Check the jumpered configuration of the adapter, especially the shared
memory window and I/O ports jumpers, and verify that the PROTOCOL.INI
MemoryWindow and IO_Port parameter values correspond to the jumper settings.
ΓòÉΓòÉΓòÉ 6.367. UBI0027 ΓòÉΓòÉΓòÉ
The adapter was reset successfully, but it did not respond after that.
The adapter appeared to respond properly to the initial communication from the
driver, but the adapter did not respond properly after that. There may be a
problem with the adapter hardware, or there may be a problem with parameters in
the PROTOCOL.INI file, or with the adapter configuration.
Verify that the AdapterType parameter value in the PROTOCOL.INI file is correct
for your adapter. Check the jumpered configuration of the adapter, especially
the shared memory window and I/O ports jumpers, and verify that the
PROTOCOL.INI MemoryWindow and IO_Port parameter values correspond to the jumper
settings.
ΓòÉΓòÉΓòÉ 6.368. UBI0028 ΓòÉΓòÉΓòÉ
The adapter passed its diagnostic tests but failed to halt.
The adapter worked properly up through the point of reporting successful
completion of its diagnostics, but it failed to respond to the next attempt
from the driver to communicate with it. There may be a problem with the adapter
hardware, or there may be a problem with parameters in the PROTOCOL.INI file,
or with the adapter configuration.
Verify that the AdapterType parameter in the PROTOCOL.INI file is correct for
your adapter. Check the jumpered configuration of the adapter, especially the
shared memory window and I/O ports jumpers, and verify that the PROTOCOL.INI
MemoryWindow and IO_Port parameter values correspond to the jumper settings.
ΓòÉΓòÉΓòÉ 6.369. UBI0029 ΓòÉΓòÉΓòÉ
The adapter passed its diagnostic tests and was halted, loaded, and started,
but it did not complete its initialization.
The adapter worked properly through all the preliminary stages of
initialization. Its operational program has been loaded into it, and it is
running, but it has failed to complete its initialization phase. There may be a
problem with the adapter hardware, or the adapter operational program may be
corrupted. There may be a problem with parameters in the PROTOCOL.INI file, or
with the adapter configuration.
Try using another copy of the UBNEI.OS2 file. The adapter operational code is
in this file. Verify that the AdapterType parameter in the PROTOCOL.INI file is
correct for your adapter. Check the jumpered configuration of the adapter,
especially the shared memory window and I/O ports jumpers, and verify that the
PROTOCOL.INI MemoryWindow and IO_Port parameter values correspond to the jumper
settings.
ΓòÉΓòÉΓòÉ 6.370. UBI0030 ΓòÉΓòÉΓòÉ
The adapter passed diagnostics and seemed to initialize properly, but its
adapter-to-PC interrupt does not work.
The adapter has been initialized successfully and has started running its
operational code, but a test of the adapter-to-PC interrupt has failed. There
may be a problem with the adapter hardware, or there may be a problem with the
IRQ_Level parameter in the PROTOCOL.INI file or with the configured interrupt
level of the adapter.
Check that the adapter jumpered configuration of interrupt level agrees with
the value of the IRQ_Level parameter in the PROTOCOL.INI file. Verify that the
interrupt level that has been chosen for the adapter is not being used by
another adapter or by a system device.
ΓòÉΓòÉΓòÉ 6.371. UBI0031 ΓòÉΓòÉΓòÉ
Working storage GDT selector allocation failed.
The OS/2 AllocateGDTSelector DevHlp system call failed when the driver tried to
get the GDT selectors it needs for referencing its multicast address list,
queued request descriptors, and queued transmit descriptors. The MaxTransmits
parameter in the PROTOCOL.INI file may be too large. The OS/2 system may be
misconfigured or corrupted. The file that runs the driver (UBNEI.OS2) may be
corrupted.
Try to verify that the system otherwise functions correctly. Try using another
copy of the UBNEI.OS2 file. If you have set the MaxTransmits parameter in the
PROTOCOL.INI file to a very large value, try reducing it.
ΓòÉΓòÉΓòÉ 6.372. UBI0032 ΓòÉΓòÉΓòÉ
The memory needed for working storage could not be allocated.
The driver was unable to allocate the memory it needs for its multicast address
list, queued request descriptors, and queued transmit descriptors. Either,
under DOS, there was not enough memory available, or, under the OS/2 program,
the OS/2 AllocPhys DevHlp system call failed when the driver tried to allocate
the memory. Some of the configuration parameters in the PROTOCOL.INI file may
be too large. The system may be misconfigured or corrupted. The file that runs
the driver may be corrupted.
The amount of memory the driver tries to allocate for working storage depends
on the values of the MaxRequests, MaxTransmits, and MaxMulticast parameters in
the PROTOCOL.INI file. The MaxTransmits parameter has much more effect than the
other two. If you have specified large values for these parameters, try
reducing them. Try to verify that the system otherwise functions correctly.
Try using another copy of the UBNEI.OS2 file.
ΓòÉΓòÉΓòÉ 6.373. UBI0033 ΓòÉΓòÉΓòÉ
Setup of the GDT selectors for working storage failed.
The OS/2 PhysToGDTSelector DevHlp system call failed when the driver tried to
initialize the GDT selectors it uses to reference its multicast address list,
queued request descriptors, and queued transmit descriptors. The OS/2 system
may be misconfigured or corrupted. The file that runs the driver (UBNEI.OS2)
may be corrupted.
Try to verify that the system otherwise functions correctly. Try using another
copy of the UBNEI.OS2 file.
ΓòÉΓòÉΓòÉ 6.374. UBI0034 ΓòÉΓòÉΓòÉ
The configured number of receive buffers is too large.
The values of the PROTOCOL.INI ReceiveBuffers and/or ReceiveBufSize parameters
are too large for the driver to handle. This error occurs only when the
ReceiveMethod = ReceiveChain, HostBuffered option is used.
Reduce the values of the ReceiveBuffers and/or ReceiveBufSize parameters in the
PROTOCOL.INI file. Try using another value for ReceiveMethod. Try using a fresh
copy of the driver executable file (UBNEI.OS2).
ΓòÉΓòÉΓòÉ 6.375. UBI0035 ΓòÉΓòÉΓòÉ
The memory needed for receive buffers could not be allocated.
The driver was unable to allocate the memory it needs for receive buffers and
receive buffer descriptors. Either, under DOS, there was not enough memory
available, or, under the OS/2 program, the OS/2 AllocPhys DevHlp system call
failed when the driver tried to allocate the memory. This error occurs only
when the ReceiveMethod = ReceiveChain, HostBuffered option is used.
Reduce the values of the ReceiveBuffers and/or ReceiveBufSize parameters in the
PROTOCOL.INI file. Try using another value for ReceiveMethod. Try using a fresh
copy of the file that runs the driver (UBNEI.OS2).
ΓòÉΓòÉΓòÉ 6.376. UBI0036 ΓòÉΓòÉΓòÉ
Receive buffer GDT selector allocation failed.
The OS/2 AllocateGDTSelector DevHlp system call failed when the driver tried to
get the GDT selectors it needs for receive buffers and receive buffer
descriptors. The OS/2 system may be misconfigured or corrupted. The file that
runs the driver (UBNEI.OS2) may be corrupted. This error occurs only when the
ReceiveMethod = ReceiveChain, HostBuffered option is used. If you have
specified a large number of receive buffers and/or a large receive buffer size,
this error is more likely to occur.
Try to verify that the system is otherwise functioning correctly. Try using
another copy of the UBNEI.OS2 file. Try decreasing the value of the
ReceiveBuffers and ReceiveBufSize parameters. Try using another value for
ReceiveMethod.
ΓòÉΓòÉΓòÉ 6.377. UBI0037 ΓòÉΓòÉΓòÉ
Setup of the GDT selector for ReceiveChain descriptors failed.
The OS/2 PhysToGDTSelector DevHlp system call failed when the driver tried to
initialize the GDT selector it is using for receive buffer descriptors. The
OS/2 system may be misconfigured or corrupted. The file that runs the driver
(UBNEI.OS2) may be corrupted. This error occurs only when the ReceiveMethod =
ReceiveChain, HostBuffered option is used.
Try to verify that the system is otherwise functioning correctly. Try using
another copy of the UBNEI.OS2 file. Try using another value for ReceiveMethod.
ΓòÉΓòÉΓòÉ 6.378. UBI0038 ΓòÉΓòÉΓòÉ
Setup of the GDT selectors for ReceiveChain buffers failed.
The OS/2 PhysToGDTSelector DevHlp system call failed when the driver tried to
initialize the GDT selectors it is using for receive buffers. The OS/2 system
may be misconfigured or corrupted. The file that runs the driver (UBNEI.OS2)
may be corrupted. This error occurs only when the ReceiveMethod = ReceiveChain,
HostBuffered option is used. If you have specified a large number of receive
buffers and/or a large receive buffer size, this error is more likely to occur.
Try to verify that the system is otherwise functioning correctly. Try using
another copy of the UBNEI.OS2 file. Try decreasing the values of the
ReceiveBuffers and ReceiveBufSize parameters. Try using another value for
ReceiveMethod.
ΓòÉΓòÉΓòÉ 6.379. UBI0039 ΓòÉΓòÉΓòÉ
The X module was unable to register with the Protocol Manager.
The driver call to the RegisterModule function of the PROTMAN$ driver failed.
There may be a problem with the Protocol Manager. You may be attempting to
install more NDIS drivers than the Protocol Manager can handle. The file that
runs the driver (UBNEI.OS2) may be corrupted.
Verify that the PROTMAN driver loads successfully. Check for error messages
during its loading. Verify that other NDIS drivers are able to install
successfully. Check the CONFIG.SYS file to see whether an unusually large
number of NDIS drivers are being installed before UBNEI. Try using a fresh copy
of the UBNEI.OS2 file.
ΓòÉΓòÉΓòÉ 6.380. UBI0040 ΓòÉΓòÉΓòÉ
Interrupt handler installation failed.
The OS/2 SetIRQ DevHlp system call failed. The driver cannot install its
interrupt routine in the interrupt vector the adapter is configured to use. The
likely cause of this problem is a conflict between this driver and a previously
installed driver over the use of the interrupt level.
Try changing the interrupt level. For the NIUps adapter, do this using the
PS/2 hardware configuration utilities (the programs on the Reference Diskette).
For the other types of adapters UBNEI supports, you must change the adapter
jumpers and change the value of the IRQ_Level parameter in the PROTOCOL.INI
file.
ΓòÉΓòÉΓòÉ 6.381. XI00001 ΓòÉΓòÉΓòÉ
An error occurred while accessing the file "X". The specified file may be in
use by another process. Alternatively, the operating system may have returned a
"no more files" or "path not found" error in response to a MPTS request.
The file is locked, there are no more files in the path, or the path was not
found.
Remove MPTS if it is already installed, and then re-install MPTS.
ΓòÉΓòÉΓòÉ 6.382. 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.
The exception number was not found in the exception stack.
Record the circumstances, and report the error to your IBM service
representative.
ΓòÉΓòÉΓòÉ 6.383. XI00003 ΓòÉΓòÉΓòÉ
An error occurred in the MPTS exception handler. Unable to process current
error condition. The MPTS exception handler stack has been changed.
An internal error in MPTS has occurred.
Record the circumstances, and report the error to your IBM service
representative.
ΓòÉΓòÉΓòÉ 6.384. 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.
The file may have been locked or erased by another process.
Remove MPTS, and re-install MPTS if help information is needed.
ΓòÉΓòÉΓòÉ 6.385. XI00005 ΓòÉΓòÉΓòÉ
An error occurred while reading the file "X". MPTS encountered an error while
trying to copy the specified file.
Anything that results in a file not being successfully copied can cause this
error.
Record the circumstances and contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.386. XI00006 ΓòÉΓòÉΓòÉ
An error occurred during configuration. An error occurred while configuring
MPTS.
The specific cause should have been given in a preceding error message.
Correct the error condition and then try to configure MPTS again.
ΓòÉΓòÉΓòÉ 6.387. XI00007 ΓòÉΓòÉΓòÉ
An error occurred while initializing the system for configuration. An error
occurred while initializing the system for MPTS configuration.
The specific cause should have been given by a preceding error message.
Correct the error condition, and restart configuration.
ΓòÉΓòÉΓòÉ 6.388. XI00008 ΓòÉΓòÉΓòÉ
An OS/2 system error occurred. This message has a number of possible causes.
This message may be received in the following situations: .
o MPTS was not able to insert text into a string.
o MPTS was not able to start a "CopyParams" thread.
o MPTS encountered a null current record in the exception handler.
Record the circumstances, and contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.389. XI00009 ΓòÉΓòÉΓòÉ
An error occurred while creating the directory "X". This error message is
displayed if a call to DosMkDir fails.
MPTS was unable to create a subdirectory needed for installation.
If the target subdirectory already exists, remove it, and then try to install
MPTS again. Otherwise, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.390. XI00010 ΓòÉΓòÉΓòÉ
A memory allocation error occurred. A call to DosAllocSeg returned with an
error.
MPTS was unable to allocate memory.
Terminate any unnecessary applications and retry the operation.
ΓòÉΓòÉΓòÉ 6.391. XI00011 ΓòÉΓòÉΓòÉ
Source files for MPTS could not be found on entered path "X". This message is
displayed if the MPTS product files could not be found on the entered path.
You have entered an incorrect path for the MPTS files.
Enter the path where the MPTS files can be found and try again.
ΓòÉΓòÉΓòÉ 6.392. XI00012 ΓòÉΓòÉΓòÉ
A Presentation Manager error occurred. MPTS is unable to continue. This
message is displayed if any of the WinXxx function calls fails.
A error occurred within the OS/2 Presentation Manager interface.
Shut down the system, reboot, and perform the operation again.
ΓòÉΓòÉΓòÉ 6.393. XI00013 ΓòÉΓòÉΓòÉ
Insufficient space on drive "X" for MPTS installation. MPTS checks to ensure
that sufficient free disk space is available before continuing with
installation.
The target drive has insufficient space to install MPTS.
Delete any unnecessary files on the target drive, and try to install MPTS
again.
ΓòÉΓòÉΓòÉ 6.394. XI00014 ΓòÉΓòÉΓòÉ
An error occurred while attempting to update "X". This error is returned if
MPTS was unable to update the CONFIG.SYS file specified (location of CONFIG.SYS
is indicated).
The CONFIG.SYS file may have been opened by another process after MPTS was
invoked.
If another process has opened the CONFIG.SYS file, terminate that process.
Exit MPTS and try again.
ΓòÉΓòÉΓòÉ 6.395. XI00016 ΓòÉΓòÉΓòÉ
An error occurred while attempting to write to the file "X". MPTS encountered
an error while writing data to the specified file.
The target drive may be full.
Delete any unnecessary files on the target drive, and retry the operation.
ΓòÉΓòÉΓòÉ 6.396. XI00017 ΓòÉΓòÉΓòÉ
Unable to load the DLL "X". MPTS was either unable to load the specified
dynamic link library or to determine the address of a procedure within the DLL.
The MPTS DLL may be missing or damaged.
Check the IBMCOM\DLL directory for files with an extension of DLL. If fewer
than five files are present, or if any seem to have been altered, contact your
IBM service representative.
ΓòÉΓòÉΓòÉ 6.397. XI00018 ΓòÉΓòÉΓòÉ
One or more source files is missing from the MPTS installation diskette. MPTS
was unable to find a file needed for installation.
The MPTS diskette may have been damaged.
Contact IBM for a replacement MPTS diskette.
ΓòÉΓòÉΓòÉ 6.398. XI00019 ΓòÉΓòÉΓòÉ
Unable to preserve the current PROTOCOL.INI file. This error indicates that
MPTS was unable to copy the current PROTOCOL.INI file to a temporary directory.
Either the TMPCOM directory was removed after MPTS was invoked or a copy of the
PROTOCOL.INI file that cannot be overwritten was created after invocation.
Remove MPTS and start the installation again.
ΓòÉΓòÉΓòÉ 6.399. XI00020 ΓòÉΓòÉΓòÉ
An error occurred unpacking the file "X". This error indicates that the file
unpacking program could not be started.
Either the unpacking program could not be run or an error occurred while
unpacking files.
Record the circumstances, and contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.400. XI00021 ΓòÉΓòÉΓòÉ
An error occurred while attempting to process a locked file.
A file that needed to be replaced was locked and could not be replaced.
Record circumstances and contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.401. XI00022 ΓòÉΓòÉΓòÉ
The device "X" is not ready.
When MPTS attempted to access a device, the operating system returned a device
not ready error code.
If the device is a diskette drive, ensure that the diskette is fully inserted
and that the drive door is closed. If the device is a network drive, ensure
that drive is on-line. If the problem, persists, have the drive serviced.
ΓòÉΓòÉΓòÉ 6.402. XI00023 ΓòÉΓòÉΓòÉ
Unable to copy "X" to the path specified by the L1 parameter. This error
indicates that MPTS was unable to perform logging.
MPTS was unable to copy the specified file to the place specified by the L1
parameter.
Contact your LAN administrator.
ΓòÉΓòÉΓòÉ 6.403. XI00024 ΓòÉΓòÉΓòÉ
Unattended configuration was unable to create the PROTOCOL.INI file.
This error can be returned if MPTS encounters a problem during any of the
following actions: creating a PROTOCOL.INI file based on a response file,
updating the target CONFIG.SYS file based on contents of a PROTOCOL.INI file,
including VDD/PDD support, or checking for locked files.
Verify that the response file used to create the PROTOCOL.INI file is correct.
Ensure that the product is properly installed. If the problem persists,
contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.404. XI00025 ΓòÉΓòÉΓòÉ
Initialization of CID failed.
MPTS CID functions were unable to initialize. Possible reasons include invalid
MPTS program invocation, invalid response file or missing response file, or
unable to locate imbedded response files.
Ensure that the MPTS invocation is correct and that the response file
referenced is valid. If the problem persists, record the circumstances and
contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.405. XI00026 ΓòÉΓòÉΓòÉ
MPTS must be installed before configuration or installing additional drivers
can be performed.
The response file has requested an action that cannot be performed when MPTS is
not installed. MPTS is currently not installed and the response file does not
specify that installation should be performed.
Note: If the response file being used is attempting to install additional
network drivers, verify that the target parameter is specified and is the
location where MPTS is installed.
Install MPTS or change the response file.
ΓòÉΓòÉΓòÉ 6.406. XI00032 ΓòÉΓòÉΓòÉ
No network information files were found at "X". This message indicates that no
NIFs were found at the specified path.
The NIFs may have been deleted by another process.
Exit MPTS, and install MPTS again.
ΓòÉΓòÉΓòÉ 6.407. XI00033 ΓòÉΓòÉΓòÉ
The network information file, "X", is not valid. This network driver support
will not be installed. MPTS was unable to copy one or more of the files
associated with this NIF.
Either the NIF is damaged or the associated files have been deleted by another
process.
Reinstall MPTS.
ΓòÉΓòÉΓòÉ 6.408. XI00034 ΓòÉΓòÉΓòÉ
The installation of the driver, "X", failed. This message indicates that MPTS
was unable to copy one or more files to the temporary directory used for
installation.
MPTS was not able to preserve an existing driver file before copying a new one.
Remove MPTS and re-install.
ΓòÉΓòÉΓòÉ 6.409. XI00035 ΓòÉΓòÉΓòÉ
The driver X could not be installed and the previous version could not be
restored. If the installation of a driver fails, and a previous copy of the
driver has been preserved, MPTS will try to restore the previous copy.
The previously saved copy of a driver file could not be restored after
installation of the new driver failed.
Remove MPTS and re-install.
ΓòÉΓòÉΓòÉ 6.410. XI00036 ΓòÉΓòÉΓòÉ
The previous version of the driver "X" could not be restored. MPTS attempts to
preserve a copy of an existing driver before copying a new version of the
driver.
MPTS could not restore the previous copy of a driver after the attempt to
preserve the existing copy failed.
Remove MPTS and re-install.
ΓòÉΓòÉΓòÉ 6.411. XI00037 ΓòÉΓòÉΓòÉ
The file "X" was not found on the source for additional network drivers.
The specified path does not exist. This error indicates that the specified path
for the network information files was not valid.
If you are using MPTS in attended mode, enter the correct path and try again.
If you are using MPTS in an unattended environment, ensure that the value for
the target parameter is correct and try again.
ΓòÉΓòÉΓòÉ 6.412. XI00039 ΓòÉΓòÉΓòÉ
Some files were locked by the operating system during the installation of
additional network drivers. For this reason, Install will no longer be
selectable during this invocation of MPTS. Files that are locked are currently
in use by the operating system and cannot be replaced.
A file that MPTS is trying to replace is already in use.
The CURRENTLY BOOTED DRIVE must be rebooted after installation is complete to
allow the MPTS locked files device driver to replace the locked files. If this
is a multiboot system and if the currently booted drive is not rebooted before
MPTS is used, system integrity cannot be guaranteed.
ΓòÉΓòÉΓòÉ 6.413. XI00040 ΓòÉΓòÉΓòÉ
LAN Adapter and Protocol Support is currently running. Only one invocation can
run at a time.
MPTS is already running.
Switch to the session where MPTS is running.
ΓòÉΓòÉΓòÉ 6.414. XI00041 ΓòÉΓòÉΓòÉ
The value provided for MPTS installation target parameter is not valid.
The value supplied for the /T: parameter on the MPTS invocation command line or
within the MPTS response file is not valid. The target must reference a valid
location that is not a removable media.
Ensure that the target provided for MPTS installation is valid and that it
references fixed media.
ΓòÉΓòÉΓòÉ 6.415. XI00042 ΓòÉΓòÉΓòÉ
Error reading response file.
MPTS encountered an error while reading the response file specified with the
MPTS invocation by the /r: parameter.
Ensure that the reference to the response file on the MPTS invocation is valid
and that all imbed files are also accessible. If the problem persists, contact
your IBM service representative.
ΓòÉΓòÉΓòÉ 6.416. XI00043 ΓòÉΓòÉΓòÉ
Cannot read the file "X". As part of its operation, MPTS must access many
files.
MPTS encountered an error while trying to read a file.
Record the circumstances and contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.417. XI00044 ΓòÉΓòÉΓòÉ
MPTS was unable to migrate the OS/2 1.3 Extended Edition configuration file X.
The specified OS/2 Extended Edition 1.3 configuration file could not be
successfully migrated to a PROTOCOL.INI file.
Retry the operation.
ΓòÉΓòÉΓòÉ 6.418. XI00045 ΓòÉΓòÉΓòÉ
Error processing PROT_SECTION in the response file; the SECTION_NAME keyword is
missing. The response file provided on the MPTS invocation contains a invalid
PROT_SECTION.
A PROT_SECTION in the response file specified on MPTS invocation is not valid.
Ensure that the response file is correct and retry the operation. If the
problem persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.419. XI00046 ΓòÉΓòÉΓòÉ
Internal software error during configuration. MPTS checks the values in a
response file against the parameters in the appropriate NIF and adjusts them if
necessary.
MPTS detected an internal error while validating the contents of a response
file against the corresponding NIF.
Record the circumstances and contact your IBM service representative to obtain
a new copy of MPTS.
ΓòÉΓòÉΓòÉ 6.420. XI00047 ΓòÉΓòÉΓòÉ
Section name "X" is invalid and cannot be used for configuration. MPTS checks
the values in a response file against the parameters in the appropriate NIF and
corrects them if necessary.
The response file is not valid.
Record the circumstances and contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.421. XI00049 ΓòÉΓòÉΓòÉ
Error trying to write a file.
An error occurred when MPTS tried to write to the CONFIG.SYS file. After all
necessary changes have been made, MPTS attempts to write a revised version of
the CONFIG.SYS file.
Ensure that the CONFIG.SYS file exists and that it is not in use by another
program. Retry the operation. If the problem persists, contact your IBM
service representative.
ΓòÉΓòÉΓòÉ 6.422. XI00050 ΓòÉΓòÉΓòÉ
Unable to migrate the OS/2 Extended Edition 1.3 configuration file "X" because
no LAN information was available.
No LAN configuration is supported in the specified OS/2 Extended Edition 1.3
configuration file.
Ensure that the OS/2 Extended Edition 1.3 configuration file specified in the
response file is correct and that it contains necessary configuration
information. Retry the operation. If the problem persists, contact your IBM
Service representative.
ΓòÉΓòÉΓòÉ 6.423. XI00051 ΓòÉΓòÉΓòÉ
Unable to open the OS/2 Extended Edition 1.3 configuration file "X".
MPTS was unable to open the specified OS/2 Extended Edition 1.3 configuration
file.
Ensure the filename provided in the response file or the MPTS window is correct
and references an existing OS/2 Extended Edition 1.3 configuration file. Retry
the operation. If the problem persists, contact your IBM Service
representative.
ΓòÉΓòÉΓòÉ 6.424. XI00052 ΓòÉΓòÉΓòÉ
Unable to read the OS/2 Extended Edition 1.3 configuration file "X".
MPTS encountered an error while trying to read the configuration file
specified.
Ensure the filename provided for migration is correct and references an
existing OS/2 Extended Edition 1.3 configuration file.
ΓòÉΓòÉΓòÉ 6.425. XI00053 ΓòÉΓòÉΓòÉ
MPTS was unable to migrate the OS/2 Extended Edition 1.3 configuration file "X"
because it is not a verified configuration file.
The configuration file specified has not been verified. OS/2 Extended Edition
1.3 configuration is verified by using the Communications Manager verification
function. The specified configuration file cannot be accepted because it has
not been verified by this function.
Run the verify function from the Communications Manager Advanced Configuration
function. Restart MPTS and retry the operation.
ΓòÉΓòÉΓòÉ 6.426. XI00054 ΓòÉΓòÉΓòÉ
The version of configuration file "X" is not supported for migration.
The migration of the specified configuration is not supported because it is not
a supported version. MPTS supports migration of OS/2 Extended Edition 1.3
configuration files only.
Ensure the configuration file supplied is the correct version and retry the
operation.
ΓòÉΓòÉΓòÉ 6.427. 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.
MPTS was unable to modify the SYSLEVEL.OS2 file to reflect that the current
system is OS/2 1.3 Standard Edition. The current system level is not correct.
The current system may not support appropriate CSD updates and MPTS re-install
requests will not be processed correctly. Correct the system by re-installing
OS/2 Extended Edition Version 1.3 and then re-installing MPTS.
ΓòÉΓòÉΓòÉ 6.428. XI00056 ΓòÉΓòÉΓòÉ
There is no value specified in the response file for the keyword X and the
associated Network Information File (.NIF) does not provide a default.
The specified parameter is a required parameter, however, it was not provided
in the response file and there is not a default value included in the
corresponding NIF file.
Ensure that the parameter is included in the response file.
ΓòÉΓòÉΓòÉ 6.429. XI00057 ΓòÉΓòÉΓòÉ
Error processing a PROT_SECTION in the response file. The NIF keyword is
missing.
The response file contained a PROT_SECTION keyword, however, the required NIF
keyword that identifies the corresponding NIF file was missing.
Ensure that the response file is correct and retry the operation.
ΓòÉΓòÉΓòÉ 6.430. XI00058 ΓòÉΓòÉΓòÉ
No Network Information Files (.NIF) were found.
MPTS was unable to configure drivers because no network information files
(.NIF) could be located on the system.
Re-install MPTS and retry the operation.
ΓòÉΓòÉΓòÉ 6.431. XI00059 ΓòÉΓòÉΓòÉ
MPTS attempted to update CONFIG.SYS and the current PROTOCOL.INI file does not
contain any configuration information.
You have requested to complete the configuration however, MPTS configuration
has not been performed.
Select CONFIGURE on the MPTS main window to perform the necessary
configuration. Continue if no configuration is necessary.
ΓòÉΓòÉΓòÉ 6.432. XI00060 ΓòÉΓòÉΓòÉ
Not all parameters were specified.
The number of parameters supplied on a command line is less than that required
by the program.
See an additional message for an example of the correct parameter usage.
ΓòÉΓòÉΓòÉ 6.433. XI00061 ΓòÉΓòÉΓòÉ
Too many parameters were specified.
The number of parameters supplied on a command line differs from that required
by the program.
See an additional message for an example of the correct parameter usage.
ΓòÉΓòÉΓòÉ 6.434. XI00062 ΓòÉΓòÉΓòÉ
The specified source is not valid.
The source parameter provided on the program invocation is not valid.
Ensure that the value for the source parameter is correct and refers to a valid
OS/2 location.
ΓòÉΓòÉΓòÉ 6.435. XI00063 ΓòÉΓòÉΓòÉ
The source must be a valid path specification.
The source parameter provided on the program invocation line does not refer to
a valid OS/2 path.
Ensure that the value for the source parameter is correct and refers to a valid
OS/2 location.
ΓòÉΓòÉΓòÉ 6.436. XI00064 ΓòÉΓòÉΓòÉ
The specified target is not valid.
The target parameter provided on the program invocation line does not refer to
a valid OS/2 path.
Ensure that the value for the target parameter is correct and refers to a valid
OS/2 location.
ΓòÉΓòÉΓòÉ 6.437. XI00065 ΓòÉΓòÉΓòÉ
The target must be a valid drive specification.
The target parameter provided on the program invocation line does not refer to
a valid OS/2 drive.
Ensure that the value for the target parameter is correct and refers to a valid
OS/2 drive. Ensure that the media is properly inserted in the specified drive.
ΓòÉΓòÉΓòÉ 6.438. XI00066 ΓòÉΓòÉΓòÉ
The target must be a valid path specification.
The target parameter provided on the program invocation line does not refer to
a valid OS/2 path.
Ensure that the value for the target parameter is correct and refers to a valid
OS/2 path.
ΓòÉΓòÉΓòÉ 6.439. XI00068 ΓòÉΓòÉΓòÉ
Unable to execute X; the return code is X.
The identified program could not be run. The program could not be located or
is not installed correctly.
Obtain a new copy of the MPTS program diskette and retry the operation. Ensure
that the target system supports the XCOPY command. If the problem persists,
contact your IBM Service representative.
ΓòÉΓòÉΓòÉ 6.440. XI00069 ΓòÉΓòÉΓòÉ
X returned an error; the exit code is X.
The identified program encountered a failure during execution. The exit code
provided is the return code from the program with the exception.
See related messages for more information. Refer to specific program
documentation for more information on the exit code specified.
ΓòÉΓòÉΓòÉ 6.441. XI00070 ΓòÉΓòÉΓòÉ
X did not complete successfully.
The specified program did not complete successfully.
Refer to associated messages for more information.
ΓòÉΓòÉΓòÉ 6.442. XI00071 ΓòÉΓòÉΓòÉ
Missing dynamic link module or entry point; object name is X.
The specified file is missing or could not be located. The MPTS program
diskette may be damaged; it does not contain the necessary files.
Create a new copy of the MPTS program diskette and retry the operation. If the
problem persists, contact your IBM Service representative.
ΓòÉΓòÉΓòÉ 6.443. XI00073 ΓòÉΓòÉΓòÉ
Unable to copy X; the return code is X.
An error occurred while trying to copy the specified file.
Refer to the appropriate OS/2 documentation for more information using the
specified return code. Retry the operation. If the problem persists, contact
your IBM Service representative.
ΓòÉΓòÉΓòÉ 6.444. XI00074 ΓòÉΓòÉΓòÉ
Unable to obtain information for X; the return code is X.
The specified return code was returned from the operating system in an attempt
to obtain file system information on the specified file.
Retry the operation. If the problem persists, contact your IBM Service
representative.
ΓòÉΓòÉΓòÉ 6.445. XI00075 ΓòÉΓòÉΓòÉ
Unable to open X; the return code is X.
The specified return code was returned from the operating system while
attempting to open the specified file.
Ensure that the file is not marked read-only. Ensure that no other program is
using the file. Retry the operation. If the problem persists, contact your
IBM Service representative.
ΓòÉΓòÉΓòÉ 6.446. XI00076 ΓòÉΓòÉΓòÉ
Unable to seek within X; the return code is X.
The specified return code was returned in response to a system request to
access the specified file.
Ensure that no other process is using the file. Retry the operation. Contact
your IBM Service representative if the problem persists.
ΓòÉΓòÉΓòÉ 6.447. XI00077 ΓòÉΓòÉΓòÉ
Unable to read from X; the return code is X.
The OS/2 program returned an error in response to a DosRead request.
Run the CHKDSK program against the affected drive. This error can be caused by
soft media defects.
ΓòÉΓòÉΓòÉ 6.448. XI00078 ΓòÉΓòÉΓòÉ
Unable to write to X; the return code is X.
OS/2 returned the specified error attempting to write the specified file.
Retry the operation. If the problem persists, contact your IBM Service
representative.
ΓòÉΓòÉΓòÉ 6.449. XI00079 ΓòÉΓòÉΓòÉ
Unable to close X; the return code is X.
An attempt to close the specified file resulted in a program error. The return
code specified reflects the OS/2 error.
Retry the operation. If the problem persists, contact your IBM Service
representative.
ΓòÉΓòÉΓòÉ 6.450. XI00080 ΓòÉΓòÉΓòÉ
Unable to delete X; the return code is X.
An attempt to remove the specified file was denied by the operating system with
the specified return code.
Ensure that no other process is using the file. Ensure that the file is not
marked read-only. Retry the operation. If the problem persists, contact your
IBM service representative.
ΓòÉΓòÉΓòÉ 6.451. XI00081 ΓòÉΓòÉΓòÉ
Error reading from X; not all bytes were read.
Fewer than the requested number of bytes were read from a file.
Ensure that no other process is trying to use the file. Retry the operation. If
the problem persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.452. XI00082 ΓòÉΓòÉΓòÉ
Error writing to X; not all bytes were written.
Fewer than the specified number of bytes were written to a file. The most
likely cause is a disk that is full.
Delete unnecessary files on the affected disk to free space. Retry the
operation. If the problem persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.453. XI00083 ΓòÉΓòÉΓòÉ
Unable to allocate memory; the return code is X.
An attempt to allocate the memory necessary for processing failed with the
specified OS/2 program return code.
Stop any unnecessary programs that are running and retry the operation. If the
problem persists, perform a system shutdown and retry the operation.
ΓòÉΓòÉΓòÉ 6.454. XI00084 ΓòÉΓòÉΓòÉ
Error while parsing X.
An error occurred while parsing the identified file.
Ensure that the file specified is a valid network information file (.NIF).
Retry the operation. If the problem persists, contact your IBM service
representative.
ΓòÉΓòÉΓòÉ 6.455. XI00085 ΓòÉΓòÉΓòÉ
Usage: Н<path>┘ LAPSDISK <source> <target>
This is an incorrect LAPSDISK program invocation.
See the associated messages.
ΓòÉΓòÉΓòÉ 6.456. XI00086 ΓòÉΓòÉΓòÉ
Usage: Н<path>┘ LAPSRSP <source> <target> {/t: /i: /c: /u:}
This is an incorrect LAPSRSP program invocation.
LAPSRSP requires the specified syntax. See the associated messages to correct
the problem.
ΓòÉΓòÉΓòÉ 6.457. XI00087 ΓòÉΓòÉΓòÉ
LAPSRSP requires a colon to separate the keyword and the value.
The LAPSRSP program expects a colon between a keyword and the value for a
command-line switch.
Ensure that the LAPSRSP command line contains a colon between all the keywords
and their values.
ΓòÉΓòÉΓòÉ 6.458. XI00088 ΓòÉΓòÉΓòÉ
A LAPSRSP switch is specified but the value is not provided.
A valid switch was specified on the LAPSRSP command line, but a value was not
supplied.
Ensure that all the LAPSRSP switches contain valid values and retry the
operation.
ΓòÉΓòÉΓòÉ 6.459. XI00089 ΓòÉΓòÉΓòÉ
An invalid switch was specified on the LAPSRSP command line.
The switch provided on the LAPSRSP program invocation was not correct.
Verify the LAPSRSP command line and retry the operation.
ΓòÉΓòÉΓòÉ 6.460. XI00090 ΓòÉΓòÉΓòÉ
Invalid installation value.
The value supplied for the installation type was not valid. The installation
value is supplied in the following format: /i: <installation level>
(where <installation level> is either PRODUCT or ADDITIONAL).
Ensure that a valid installation level is specified and retry the operation.
ΓòÉΓòÉΓòÉ 6.461. XI00091 ΓòÉΓòÉΓòÉ
Invalid target drive specification.
The value supplied for the /t: parameter was not valid. The value is supplied
in the following format: /t:<d:> where <d:> is a valid OS/2 drive letter.
Ensure the value supplied for the /t option for LAPSRSP is valid and retry the
operation (the drive letter must be followed by a colon).
ΓòÉΓòÉΓòÉ 6.462. XI00092 ΓòÉΓòÉΓòÉ
Invalid upgrade level value.
A value supplied from the /u: option was not valid. The value is supplied in
the following format:/u:<value> where value is OLD, SAME or NEW.
Ensure the value supplied for the /u: parameter is valid and retry the
operation.
ΓòÉΓòÉΓòÉ 6.463. XI00095 ΓòÉΓòÉΓòÉ
The Network Information File (.NIF) filename must be valid and include the
filename extension.
The NIF file name provided on the program invocation is not valid.
Ensure that the NIF name specified is valid (including the filename extension).
Retry the operation.
ΓòÉΓòÉΓòÉ 6.464. XI00096 ΓòÉΓòÉΓòÉ
Unable to locate any Network Information Files (.NIF) on target drive.
THINLAPS was unable to locate any NIF files on the target drive.
Retry the operation. If the problem persists, contact your IBM service
representative.
ΓòÉΓòÉΓòÉ 6.465. XI00097 ΓòÉΓòÉΓòÉ
Unexpected error while searching for Network Information Files (.NIF).
THINLAPS was unable to find the necessary .NIF files on the target drive.
Obtain a new copy of the MPTS diskette and retry the operation. If the problem
persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.466. XI00098 ΓòÉΓòÉΓòÉ
Warning: Creating new CONFIG.SYS on the target drive.
THINLAPS expects a CONFIG.SYS file on the target drive to append the necessary
device statements for the LAN Transport to. The CONFIG.SYS file on the target
drive was not found and one was created that contains the necessary device
statements for the requested transport files to load.
Append the CONFIG.SYS file created by THINLAPS to the CONFIG.SYS file to be
used to IPL the machine.
ΓòÉΓòÉΓòÉ 6.467. XI00099 ΓòÉΓòÉΓòÉ
An error occurred while attempting to add LAPSDEL invocation to MAINTDEL.CMD.
An invocation string for the LAPSDEL utility program could not be added to the
MAINTDEL.CMD file. MPTS builds a MAINTDEL.CMD file as part of its processing
for C/I/D.
Retry the operation. If the problem persists, contact your IBM service
representative.
ΓòÉΓòÉΓòÉ 6.468. XI00102 ΓòÉΓòÉΓòÉ
SHPIINST.DLL could not be successfully loaded.
MPTS was not able to load the SHPIINST.DLL file.. MPTS must be able to load the
SHPIINST.DLL file when performing an installation on an OS/2 maintenance system
because Presentation Manager support is not available.
Ensure that the SEMAINT program was successful. Retry the operation. If the
problem persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.469. XI00103 ΓòÉΓòÉΓòÉ
The MPTS installation was not successful.
An error occurred while processing the IBMLVL.INI file. This file is used to
indicate to MPTS whether the LAN transports are already installed and the
version of the installed product. If this file is missing or is not correct,
future re-installs or updates will not be successful. This error can also
occur if the OS/2 services to update this file are currently installed.
Remove the LAN transports and retry the operation. If MPTS does not support
the Remove function, MPTS must be manually removed and re-installed.
ΓòÉΓòÉΓòÉ 6.470. XI00104 ΓòÉΓòÉΓòÉ
MPTS did not install due to UPGRADE_LEVEL specified in the response file.
MPTS has detected the presence of an already-installed version of MPTS that
should not be replaced, based on the value of the UPGRADE_LEVEL keyword in the
response file.
No action is necessary if this is the desired behavior. Otherwise, change the
UPGRADE_LEVEL parameter in the response file.
ΓòÉΓòÉΓòÉ 6.471. XI00106 ΓòÉΓòÉΓòÉ
An error occurred trying to create the file "X".
MPTS could not create a backup for the CONFIG.SYS file. MPTS attempts to make a
backup of the CONFIG.SYS file before making any changes to the original file.
Ensure the file specified does not already exist. Retry the operation. If the
problem persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.472. XI00107 ΓòÉΓòÉΓòÉ
Error while attempting to copy the file "X".
MPTS encountered an error while trying to copy a file. MPTS must copy a number
of files as part of its operations. MPTS may fail to copy a file because the
source file does not exist or because the replacement file is currently in use
by the system and cannot be replaced.
Ensure that the source file exists. If the source file is part of the MPTS
packed diskette image, obtain a new copy of the MPTS diskette and retry the
operation. If the target file already exists on the system, verify that the
operation is a re-install and that the IBMLVL.INI file exists in the root of
the drive where MPTS is already installed. If the file does not exist, MPTS
must be manually removed from the system and re-installed.
ΓòÉΓòÉΓòÉ 6.473. XI00108 ΓòÉΓòÉΓòÉ
MPTS was unable to read or update the IBMLVL.INI file correctly. Because the
install status of MPTS is undefined, MPTS will be removed from the system.
MPTS encountered an error while accessing the IBMLVL.INI file. MPTS needs to
read and update the IBMLVL.INI file (found in the root directory of the boot
drive) as part of its operations.
If the IBMLVL.INI file exists, erase the file and restart MPTS. If the problem
persists, contact your IBM service representative.
ΓòÉΓòÉΓòÉ 6.474. XI00109 ΓòÉΓòÉΓòÉ
CONFIG.SYS could not be successfully updated with the configuration information
provided by MPTS. Your system may not be operational when restarted.
An error occurred when MPTS tried to update the CONFIG.SYS file. MPTS may need
to update the CONFIG.SYS file after configuration has been completed.
Retry the operation. If the problem persists, restore the backup configuration
file, CONFIG.LAP, to the CONFIG.SYS file and retry the operation. If the
problem still persists, contact your IBM Service representative.
ΓòÉΓòÉΓòÉ 6.475. XI00111 ΓòÉΓòÉΓòÉ
The file 'X' was not found in the ZIP file of the MPTS product image.
THINLAPS attempted to extract one or more files from a ZIP file of the MPTS
product image. The file was not found in the ZIP file.
No action is required. THINLAPS attempts to copy the file directly from the
appropriate subdirectory. If the copy fails, another message displays; refer
to help for that message.
ΓòÉΓòÉΓòÉ 6.476. XI00114 ΓòÉΓòÉΓòÉ
THINLAPS was unable to copy the 'X'; the return code is 'X'.
An error occurred while THINLAPS attempted to copy the specified file from the
appropriate subdirectory.
Make sure that the MAC.NIF file and it's support files (except .MSG files) are
located in the proper subdirectories. The MAC.NIF file and it's support files
(except .MSG) should be located in the \IBMCOM\MACS subdirectory off the target
path of the LAPSDISK utility. Message files (.MSG) should be located in the
\IBMCOM subdirectory off the target path of the LAPSDISK utility.
ΓòÉΓòÉΓòÉ 6.477. XI00115 ΓòÉΓòÉΓòÉ
Error while attempting MPTS installation due to UPGRADE_LEVEL. The installed
version is the same as the version being installed. To reinstall the same
version an UPGRADE_LEVEL of NEW or SAME must be specified.
MPTS detected an existing version of MPTS that is the same or newer that the
version being installed. Since the UPGRADE_LEVEL parameter is set to OLD, this
version will not be replaced.
No action is necessary if this is the desired behavior. Otherwise, change the
UPGRADE_LEVEL parameter in the response file. If no UPGRADE_LEVEL parameter is
specified, the default is OLD.
ΓòÉΓòÉΓòÉ 6.478. XI00141 ΓòÉΓòÉΓòÉ
MPTS was unable to create the PROTOCOL.INI file for NDIS support.
MPTS, running in attended mode with the /N parameter specified on the command
line, encountered an error while attempting to create the PROTOCOL.INI file for
NDIS support.
Retry the operation. If the problem persists, contact your IBM service
representative.
ΓòÉΓòÉΓòÉ 6.479. XI00142 ΓòÉΓòÉΓòÉ
A CONFIG.SYS file cannot be located at the value specified for the /TU:
parameter.
The /TU parameter on the MPTS program invocation identifies the location (drive
and path) where the CONFIG.SYS file is located that will be updated with MPTS
configuration information.
Run MPTS again using a valid CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.480. XI00143 ΓòÉΓòÉΓòÉ
NetBIOS configuration values exceed acceptable configuration requirements.
The configuration values that were migrated cannot be tuned. NetBIOS parameters
were migrated; however, the memory requirements for this configuration exceed
the value supported for the NetBIOS protocol stack. NetBIOS memory usage
limitations are computed using the current system processor as a limitation.
If you are using a 286-based machine to prepare a PROTOCOL.INI file for a
386/486-based machine, memory usage limitations will be greater.
Reconfigure the resultant PROTOCOL.INI file to lower the necessary NetBIOS
capacity parameters in order to ensure that the NetBIOS protocol stack loads
successfully. Refer to the MPTS product documentation for the NetBIOS
parameter tuning guidelines.
ΓòÉΓòÉΓòÉ 6.481. XI00144 ΓòÉΓòÉΓòÉ
LANDD configuration values exceed acceptable configuration requirements.
The configuration values that were migrated cannot be tuned. The IEEE 802.2
parameters were migrated; however, the memory requirements for this
configuration exceed the value supported for the IEEE 802.2 protocol stack.
IEEE 802.2 memory usage limitations are computed using the current system
processor as a limitation. If you are using a 286-based machine to prepare a
PROTOCOL.INI file for a 386/486-based machine, memory usage limitations will be
greater.
Reconfigure the resultant PROTOCOL.INI file to lower the necessary IEEE 802.2
capacity parameters in order to ensure that the protocol stack loads
successfully. Refer to the MPTS product documentation for the specific
parameter tuning guidelines.
ΓòÉΓòÉΓòÉ 6.482. XI00150 ΓòÉΓòÉΓòÉ
The "/P:" parameter is not valid or was not followed by a valid filespec.
The fourth parameter supplied on the THINLAPS command line was not in the
format: /P:<PROTOCOL.INI filespec>. The /P: parameter is used to specify the
name of a user-supplied PROTOCOL.INI file that should be used instead of the
one generated by THINLAPS.
Ensure that the parameter is in the correct format and that it specifies the
name of a valid PROTOCOL.INI file. Retry the operation.
ΓòÉΓòÉΓòÉ 6.483. XI00151 ΓòÉΓòÉΓòÉ
The syntax for this parameter is "/P:<PROTOCOL.INI filespec>".
The fourth parameter supplied on the THINLAPS command line was not in the
format: /P:<PROTOCOL.INI filespec>. The /P: parameter is used to specify the
name of a user-supplied PROTOCOL.INI file that should be used instead of the
one generated by THINLAPS.
Ensure that the parameter is in the correct format and that it specifies the
name of a valid PROTOCOL.INI file. Retry the operation.
ΓòÉΓòÉΓòÉ 7. When and How to Contact IBM ΓòÉΓòÉΓòÉ
IBM can provide assistance to you for suspected program defects. A description
of available services follows. Procedures for recommended and required
preliminary preparations are also provided in this chapter.
Note to Customers Outside of the U.S.A.:
The IBM Personal Software Solutions Center is only available for
customers in the U.S.A. All other customers must contact their
authorized IBM sales representative.
The services IBM provides are designed to be used exclusively as part of an
overall problem determination process and should be used only after:
o Referred to Using Diagnostic Tools, and were referred to this chapter for
procedures to contact IBM
or
o Responded to an error message as directed in the messages section of this
publication, and the last instruction referred you to this chapter for
procedures to contact IBM
By following these procedures, you can resolve most problems without having to
call IBM.
ΓòÉΓòÉΓòÉ 7.1. Types of Assistance IBM Provides ΓòÉΓòÉΓòÉ
IBM provides the following types of assistance:
o The IBM Personal Software Solutions Center
The IBM Personal Software Solutions Center helps resolve program defects in
supported software. IBM Personal Software Solutions Center personnel are
trained and experienced in resolving users' problems.
o Your dealer (outside of the U.S.A.)
Dealers outside the U.S.A. are designated as Customer Technical Service
Locations (CTSLs). If you are not registered as a CTSL, report any problems
to your dealer.
In addition to being able to provide the service that best meets the needs of
your users, these services offer:
o Fast response to many problems
You have direct access to an IBM database or to a representative who can
search the database to determine if problems similar to those experienced by
users you support have already been reported and resolved.
o 24-hour service
The Solutions Center is open for problem reporting 24 hours a day, 7 days a
week.
When you contact IBM, you will have direct access to the latest information or
be in direct contact with Solutions Center specialists and databases.
ΓòÉΓòÉΓòÉ 7.2. Using the IBM Personal Software Solutions Center ΓòÉΓòÉΓòÉ
This section describes when you should contact the IBM Personal Software
Solutions Center, steps you should take before calling, and how the Solutions
Center works for you.
ΓòÉΓòÉΓòÉ 7.2.1. When to Contact the IBM Personal Software Solutions Center ΓòÉΓòÉΓòÉ
When you contact the Solutions Center, be prepared to provide the customer
number or access code that has been assigned to your installation. The access
code is the Asian version of the customer number. Unless otherwise noted,
everything that applies to the customer number also applies to the access code.
This number or code is unique to your installation and identifies you as an
eligible user of the Solutions Center. Your customer number or access code is
normally given to you by your authorized IBM marketing representative. Record
your customer number or access code here for future reference:
CUSTOMER NUMBER __________________________
ACCESS CODE __________________________
In addition, you should gather and have at hand the necessary information, to
enable the Solutions Center to assist you. When you are ready, contact your
Solutions Center.
If you are a customer in the U.S.A, contact the Solutions Center at:
1-800-992-4777
Note to Customers Outside of the U.S.A.:
This number is not available for customers outside the U.S.A. To
determine the number to dial for purchases made outside the U.S.A.,
contact your authorized IBM sales representative.
ΓòÉΓòÉΓòÉ 7.2.2. How the IBM Personal Software Solutions Center Works ΓòÉΓòÉΓòÉ
The Solutions Center helps you resolve program defects in supported software.
Based upon the symptoms you report, IBM researches the problem and documents
the solution.
The following is a description of the Solutions Center process:
1. When you call the Solutions Center, a dispatcher asks for the following
basic information:
o Your customer number or access code. This number or code is used to
verify authorization.
o The program product on which you are reporting a problem.
o A brief description of your problem. The description is used in
researching previous reports of this problem and determining which
Solutions Center representative can best respond to your problem.
2. The dispatcher assigns a Problem Management Record (PMR) number to the
problem you reported and transfers the call to Level 1 support.
3. While you are still on the phone, Level 1 support researches the problem
based upon the symptoms you report and tries to find a solution or help
you determine what caused the problem. If Level 1 support is unable to
resolve the problem, they will transfer the problem to Level 2 support.
4. If the problem is new and unique, Level 2 support continues to research
potential causes and actions. For purposes of IBM internal recording,
Level 2 support creates an IBM report known as an Authorized Program
Analysis Report (APAR) if there are suspected errors in the code.
If you are asked to forward any data to IBM to assist in problem analysis,
include the APAR number with this data.
5. When a solution to the problem is identified, IBM closes the APAR and
calls you back to tell you the problem cause and solution.
Note:
Keep a record of your PMR or APAR number for this problem in case you
have to contact IBM again.
If you have any questions your Solutions Center representative can answer
questions about a reported problem or about the process described in this
chapter.
ΓòÉΓòÉΓòÉ 7.2.3. Additional IBM Support ΓòÉΓòÉΓòÉ
Inquiries that are not resolved by the first or second level of support are
routed to Level 2.5 support. Level 2.5 performs an in-depth analysis of the
problem. Level 3 support (usually a developer) fixes any errors in the code and
works with Level 2.5 support to resolve the problem.
Normally, all communications with the customer are handled by Level 2 support.
When Level 2 calls you back about your problem, you may be asked to take some
additional action or gather some additional information. When you call back,
refer to the problem number that was assigned to you so that the correct level
of service is assigned to your problem.
The Solutions Center will enter Authorized Program Analysis Report (APAR) data
if required. The APAR is created automatically within the Solutions Center
from information you supply. The Solutions Center will enter the APAR data for
any new problems you report, tell you the APAR number assigned, and give you
the address where the supporting documentation should be sent.
ΓòÉΓòÉΓòÉ 7.3. Sending Problem Determination Information to IBM ΓòÉΓòÉΓòÉ
Information should be sent to IBM for analysis only upon direction from the
Software Solutions Center. If a Solutions Center representative requests that
you send information to IBM, read the information in this section before
sending the information.
The information in this section describes:
o Your right to privacy
o The types of problem determination information to send to IBM for various
types of problems
o Where to mail information to IBM
Note to Customers Outside of the U.S.A.:
Customers outside the U.S.A. should contact their authorized IBM
sales representative for information about where to address their
mail.
ΓòÉΓòÉΓòÉ 7.3.1. Understanding Your Right to Privacy ΓòÉΓòÉΓòÉ
Do not send information to IBM that is considered to be confidential or
proprietary by you or the end user. IBM is under no obligation of any kind with
regard to information or material submitted by system support personnel. IBM
reserves the right to publish or disclose such information to third parties.
Notes:
1. Send only faxes or copies of problem information to IBM. Originals
should be kept for your own records.
2. IBM does not return printouts, diskettes, or other problem
determination data received from system support personnel.
ΓòÉΓòÉΓòÉ 7.3.2. Types of Problem Determination Information to Send to IBM ΓòÉΓòÉΓòÉ
If you need technical assistance, please perform the following tasks before
calling the Solutions Center:
o Read the section in your manual that describes the commands or procedures
you are using.
o Press F1 for additional help information.
o Contact the automated services at 1-800-992-4777 for instant access to
commonly asked questions for various products, as well as tips and
techniques. In addition, information is available in pre-recorded messages
that can be sent directly to your fax machine.
o If, after completing the preceding steps, you still need to contact
Technical Support, you should call 1-800-237-5511. Support is provided for
IBM software products running on the full range of hardware platforms. If
you are sure that your problem is confined to the Personal Systems platform,
you can directly contact support for software products by calling
1-800-992-4777.
To assist the specialist, do the following:
- Have your product registration number available.
- Have the name and address of your company available.
- Have your phone and fax number available.
- Be at your computer.
- Have your computer manuals available.
- Write down what you were doing when the problem occurred. List the steps
you followed prior to the problem occurring.
- Write down the exact text of any error messages displayed on your screen.
- Be able to describe your questions in detail.
- If your printer is working and your problems pertain to printing, have a
sample printout available.
If you are asked to send information to IBM, include copies of the following
information:
o The output of any diagnostic procedures (examination of log utilities,
traces, and dumps) performed using the procedures provided in Using
Diagnostic Tools.
o For certain problems, it may also be appropriate to send diskettes with
copies of files containing log, trace, or dump information that may be
related to the problem. The files you may need to send depend on the nature
of the problem and the components being used.
o Provide a description of the software or hardware environment for the
workstation where the problem occurred or was reported. Include the
following information:
- Base operating system name and version number
- Product names, version numbers, and service levels installed
- Type and brand of cards installed (for example, token ring, ethernet)
- Communication protocols (for example, APPC, NetBIOS, TCP/IP)
- Memory size
- Hard disk size (including space remaining where SWAPPER.DAT resides)
- Any other information that relates to the problem
o Provide a step-by-step description of how you re-create the problem, if you
are able to do so. If the problem is intermittent, then describe any common
symptoms that you notice when the problem occurs.
Describe any changes to your environment that may have caused the problem.
o Provide any other information that may be useful in diagnosing your problem.
For example, you might include the name of the last command typed or the
last task completed before the problem occurred.
ΓòÉΓòÉΓòÉ 7.3.2.1. Information You Should Send IBM ΓòÉΓòÉΓòÉ
For all Socket/MPTS problems, if you have been directed by IBM Support Center
personnel to submit information to IBM, include the names and a copy on
diskettes of the contents of the following files:
o All available trace files
o AUTOEXEC.BAT
o CONFIG.SYS
o FFST/2 message log
o IBMLVL.INI
o LANTRAN.LOG
o LAPSHIST.LOG
o OS2.INI
o PROTOCOL.INI
o STARTUP.CMD
o SYSLEVEL.OS2
o SYSLEVEL.TRP
o SYSLOG
In addition, you need to provide the following:
o Remote location information including the link type and associated hardware
and software (include version numbers)
o Hardware information including the user's machine type and the type of
network adapter being used
ΓòÉΓòÉΓòÉ 7.3.3. Mailing or Faxing Problem Information to IBM ΓòÉΓòÉΓòÉ
Information should be sent to IBM for analysis only upon direction from the IBM
Personal Software Solutions Center.
Note to Customers Outside of the U.S.A.:
Customers outside the U.S.A. should contact their authorized IBM sales
representative for information about where to address their mail.
You can send this information to IBM either by mail or by fax. To send
information by fax, call 1-800-426-8602. To send information by mail, use the
following address:
IBM Corporation
Personal Systems Support Family
11400 Burnet Road
Internal Zip 2901
Austin, Texas 78758
Defects may be reported to IBM electronically using Talklink or CompuServe or
by mail or fax. For information about reporting defects electronically, call
1-800-992-4777. To send defect information by fax, call 1-800-426-8602. To
send defect information by mail, use the following address:
IBM Corporation
Personal Systems Support Family
11400 Burnet Road
Internal Zip 2901
Austin, Texas 78758