The Developer Connection…ice Driver Kit for OS/2 3/DEV3-D1.ISO/docs/cmmsgref.inf

OS/2 Help File | 1993-08-15 | 1.3 MB | 56,512 lines

ΓòÉΓòÉΓòÉ 1. About This Book ΓòÉΓòÉΓòÉ

IBM* Communications Manager/2 Version 1.1 (referred to in this book as
Communications Manager) is a communications services platform. This platform
provides a wide range of services for IBM Operating System/2* (OS/2*)
workstations that communicate with host computers and with other workstations.
Communications Manager users can choose from among a variety of remote
connectivity options.

It is assumed that you are using OS/2 Version 1.30.1 with corrective service
diskette (CSD) 5200 (which is equivalent to OS/2 Version 1.30.2), OS/2 Version
1.30.2, or OS/2 Version 2.0 (or later) as your base operating system. The term
OS/2, as used in the Communications Manager documentation and on the display
during the running of the programs, refers to some or all components of the
base operating system. If you use a base operating system that is functionally
equivalent to OS/2 Version 1.30.2 or OS/2 Version 2.0, the Communications
Manager documentation still applies.

This book provides information for you to:

o Identify messages that occur as a result of system or user problems
o Obtain information from the messages to resolve such problems.

To view additional material about this book, press the Esc (Escape) key to
return to the Contents. Next, select the plus sign (+) or press the + key.


ΓòÉΓòÉΓòÉ 1.1. Double-Byte Character Set Support ΓòÉΓòÉΓòÉ

Communications Manager supports double-byte character sets (DBCS), in which
each character is represented by 2 bytes. Languages such as Japanese, Chinese,
and Korean, which contain more symbols than can be represented by 256 code
points, require double-byte character sets. Because each character requires 2
bytes, the typing, display, and printing of DBCS characters require hardware
and programs that support DBCS.

Where information applies specifically to DBCS, it is noted in this information
unit.


ΓòÉΓòÉΓòÉ 1.2. Conventions Used in This Book ΓòÉΓòÉΓòÉ

The following conventions are used in this book.


ΓòÉΓòÉΓòÉ 1.2.1. Text Conventions ΓòÉΓòÉΓòÉ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé BOLD      Γöé Bold type indicates the following:              Γöé
Γöé         Γöé                               Γöé
Γöé         Γöé o  The names of window controls, such as lists, check    Γöé
Γöé         Γöé   boxes, entry fields, and menu choices.  They appear in  Γöé
Γöé         Γöé   the text as they appear in the window.          Γöé
Γöé         Γöé                               Γöé
Γöé         Γöé o  Verbs, functions, and parameters that you can use in a  Γöé
Γöé         Γöé   program or at a command prompt.  These values are case  Γöé
Γöé         Γöé   sensitive and should be entered exactly as they appear  Γöé
Γöé         Γöé   in the text.                       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Italics     Γöé Italics indicate a variable that you supply a value for.   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé UPPERCASE    Γöé Uppercase indicates constants, file names, keywords, and   Γöé
Γöé         Γöé options that you can use in a program or at a command    Γöé
Γöé         Γöé prompt.  You can enter these values in uppercase or lower-  Γöé
Γöé         Γöé case.                            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "Example type" Γöé Example type indicates information that you are instructed  Γöé
Γöé         Γöé to type at a command prompt or in a window.         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 1.2.2. Numbers Conventions ΓòÉΓòÉΓòÉ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Hexadecimal   Γöé Represented as X'xxxx' except in certain instances where   Γöé
Γöé         Γöé they are represented with text ("The location hex xxxx is  Γöé
Γöé         Γöé the address of...").  In an example of assembler language  Γöé
Γöé         Γöé code, a hexadecimal number is represented by a lowercase h  Γöé
Γöé         Γöé following the hexadecimal characters.            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Binary     Γöé Represented as B'xxxx xxxx' or B'x' except in certain    Γöé
Γöé         Γöé instances where they are represented with text ("A value of Γöé
Γöé         Γöé binary xxxx xxxx is...").                  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Bit positions  Γöé Start with 0 at the rightmost position (least significant  Γöé
Γöé         Γöé bit).                            Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 1.2.2.1. Variable Insert Information ΓòÉΓòÉΓòÉ

Some messages include variable parameters such as program names, adapter
numbers, and file names (for example, name(8)). These variable parameters are
explained after the message and before the originator.  The length of the field
is indicated in the message and in the explanation.


ΓòÉΓòÉΓòÉ 1.3. Where to Find More Information ΓòÉΓòÉΓòÉ

Both Information and Planning Guide and the online Overview contain a complete
description of both the Communications Manager library and related
publications.


ΓòÉΓòÉΓòÉ 2. Before You Begin ΓòÉΓòÉΓòÉ

This chapter provides introductory material about Communications Manager
messages.

To view the introductory material, press the Esc (Escape) key to return to the
Contents. Next, select the plus sign (+) or press the + key.


ΓòÉΓòÉΓòÉ 2.1. Understanding Communications Manager Messages ΓòÉΓòÉΓòÉ

The messages in this book are divided into chapters by message prefix. The
chapters are in alphanumeric order based on the message type.

Each chapter contains a brief description of the message type. Within each
chapter, the messages are listed in numeric order. The chapter prefix plus the
number sequence make up the alphanumeric message identification number. The
message identification numbers end in either I, W, E, C or N. These additional
letters indicate the severity of the message.

I     Informational message. This message indicates two possible situations:

   o A condition has occurred that requires no user interaction.  The only
     actions available to the user are to acknowledge the message or get help.

   o A condition has occurred and the user must perform an action (such as
     selecting Yes to acknowledge a question).

W     Warning message. This message indicates that an undesirable condition has
      occurred but the user can allow the process to continue. The user may be
      able to correct the condition and continue, cancel the request, or get
      help.

E     Error message. This message indicates that a highly undesirable condition
      occurred that requires a response from the user.

C     Critical message. This message indicates a possible error condition.

N     Non-critical message. This message is informational only.


ΓòÉΓòÉΓòÉ 2.2. Finding Communications Manager Messages ΓòÉΓòÉΓòÉ

You can find Communications Manager messages in several locations depending on
the origin of the message. In some cases, an originator is identified as the
source of the message. The originator may be a function reporting a problem
that occurred elsewhere, such as at the host computer or an application
program. Use the text of the message, along with the information provided for
each message, to help determine the source of the problem.

Communications Manager messages can be found in the following locations:

o FFST/2 Message Log (the default log file name is OS2MLOG.DAT)

  First Failure Support Technology/2 (FFST/2) is a software problem
  determination tool for OS/2 system software and applications.  FFST/2
  automatically captures data about each error at the time the error occurs.

  The FFST/2 message log stores messages and status information associated with
  Communications Manager or any product that uses FFST/2. If you do not specify
  a file name for the log during FFST/2 configuration or change it in the
  CONFIG.SYS file, messages and status information are stored in the default
  message log file (OS2MLOG.DAT). Information stored in the message log can be
  viewed, printed, or written to an ASCII file for later analysis.

  You can obtain help for each message while viewing the message log by
  double-clicking on a message choice. You can also request help for each
  message from the OS/2 command line. For information about requesting online
  help, see Obtaining Online Help. Refer to Problem Determination Guide for
  information about how to access the FFST/2 message log.

  Note:  Some messages in this book may instruct you to check the OS/2 system
         error log for related errors and additional information. For a
         description of the OS/2 system error log, refer to Problem
         Determination Guide.

o Popup messages

  Popup messages are presentation manager windowed messages. The system
  displays popup messages when performing an action, such as entering data or
  deleting a file. Additional information may be available as part of the popup
  message. You can access help information by selecting the Help push button in
  the popup message window.

o OS/2 Full-screen messages

  When a function encounters a message or an error condition and a screen
  interface is not available, you are notified of the condition with a message
  that is displayed on the OS/2 screen. These types of messages, such as device
  driver messages, generally occur at initial program load time or during
  execution of a command at an OS/2 prompt. OS/2 full-screen messages can also
  occur during run-time operation of Communications Manager. See Obtaining
  Online Help for information about requesting online help from the OS/2
  command line.

o UPGRADE.LOG

  This log, which is located in the \CMLIB directory, stores messages which are
  logged when you upgrade from a previous version of Communications Manager.
  You can view this log by using FFST/2.

  Messages recorded in this log are duplicated in the default FFST/2 message
  log.

o VERIFY.LOG

  This log, which is located in the \CMLIB directory, stores messages which are
  logged during verification. You can view this log by using FFST/2.

  Messages recorded in this log are duplicated in the default FFST/2 message
  log.

o CMRINST.LOG

  This log stores messages returned by the configuration and installation tool.

o CM.LOG

  This ascii log file, which is located in the \CMLIB directory, serves as an
  audit trail file for Communications Manager installation.

  You can view this log file by selecting the Communications Manager Services
  window and selecting Communications Manager Setup.  From the Communications
  Manager Setup window, select Options and then select View audit trail....

  You can also view this log from the OS/2 command line by changing to the
  \CMLIB directory and typing:

         type cm.log | more

For information on messages and errors and how they can be accessed, refer to
Problem Determination Guide.


ΓòÉΓòÉΓòÉ 2.3. Obtaining Online Help ΓòÉΓòÉΓòÉ

For the Communications Manager messages that have online Help information
available, you can select the Help push button to display help. Help
information is displayed in a separate window, listing the explanation and user
response for the message.

For most Communications Manager messages, you can also access message help from
the OS/2 command line by typing:

     HELP XXXxxxx | MORE

(where XXX represents the message prefix and xxxx is the message number). Help
information is displayed on the OS/2 screen, listing the explanation and user
response for the error condition.

All available help is presented in Message Reference. Because of OS/2
restrictions, the following notes apply to command line help:

Note:

 1. No command line help is available for informational messages (any message
    with a message number ending in "I"). OS/2 displays "No help is available
    for the message ID number requested."

 2. No command line help is available for messages with help exceeding 2K.
    OS/2 displays "SYS0316: The message passed to the message retriever was
    truncated."

 3. No command line help is available for messages that are popped up and not
    logged. OS/2 displays "SYS0317: The system cannot find message  xxxx  in
    message file XXXH.MSG."


ΓòÉΓòÉΓòÉ 2.4. Resolving Problems ΓòÉΓòÉΓòÉ

When a problem occurs, obtain a copy of Problem Determination Guide and follow
the step-by-step instructions for resolving problems.

If Problem Determination Guide is not available, try the following:

o If a message is logged or displayed, access help information by selecting the
  Help push button.

  For some messages, you can receive online help from the OS/2 command line.
  For information about requesting online help, see Obtaining Online Help.

  Perform the action indicated by the help.

o Look up the message in this book.

  If the message help information tells you that related error information may
  be logged in the OS/2 system error log, note the date and time that the
  message was logged in the FFST/2 message log.  Use the problem ID from the
  FFST/2 message log to cross reference the OS/2 system error log for any
  entries that were logged concurrently with the message.  Check any error log
  entries that were logged around the time that the message was logged.

o Contact a support person at your company.  See Summary of Local Support
  Personnel Roles for a summary of system support personnel who may be
  available.

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé    Summary of Local Support Personnel Roles         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé      Summary of Local Support Personnel Roles          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Support Person    Γöé Support Provided   Γöé Types of Problems   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Service personnel   Γöé Establish and main-  Γöé All types of prob-  Γöé
Γöé            Γöé tain problem-related Γöé lems.         Γöé
Γöé            Γöé records.  Assist   Γöé            Γöé
Γöé            Γöé users in problem   Γöé            Γöé
Γöé            Γöé determination.    Γöé            Γöé
Γöé            Γöé Interface with IBM.  Γöé            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Local hardware per-  Γöé Maintain system    Γöé Hardware problems   Γöé
Γöé sonnel        Γöé hardware and provide Γöé that cannot be    Γöé
Γöé            Γöé related problem-   Γöé resolved using the  Γöé
Γöé            Γöé recovery procedures  Γöé procedures described Γöé
Γöé            Γöé and assistance.    Γöé in Problem Determi-  Γöé
Γöé            Γöé            Γöé nation Guide.     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Communications    Γöé Configure, help    Γöé Damage to, loss of,  Γöé
Γöé Manager system    Γöé install, and verify  Γöé or errors in config- Γöé
Γöé administrator     Γöé correct operation of Γöé uration files or   Γöé
Γöé            Γöé Communications    Γöé related profiles.   Γöé
Γöé            Γöé Manager.       Γöé            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Network adminis-   Γöé Set up and maintain  Γöé LAN hardware or    Γöé
Γöé trator        Γöé LANs to which work-  Γöé system performance  Γöé
Γöé            Γöé stations are con-   Γöé problems.       Γöé
Γöé            Γöé nected.        Γöé            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Host personnel    Γöé Maintain and con-   Γöé Host system failure. Γöé
Γöé            Γöé figure systems con-  Γöé            Γöé
Γöé            Γöé trollers and host   Γöé            Γöé
Γöé            Γöé computers to func-  Γöé            Γöé
Γöé            Γöé tion with the Commu- Γöé            Γöé
Γöé            Γöé nications Manager   Γöé            Γöé
Γöé            Γöé program.       Γöé            Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Application program- Γöé Write, install, and  Γöé Problems resulting  Γöé
Γöé mers         Γöé debug application   Γöé from application   Γöé
Γöé            Γöé programs.       Γöé programming errors  Γöé
Γöé            Γöé            Γöé (refer to Start Here Γöé
Γöé            Γöé            Γöé for sources of    Γöé
Γöé            Γöé            Γöé debugging informa-  Γöé
Γöé            Γöé            Γöé tion).        Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 3. ACS Messages ΓòÉΓòÉΓòÉ

This chapter lists the ACS messages generated by Communications Manager.

See Before You Begin, for an introduction to Communications Manager messages.

Refer to Problem Determination Guide for additional information including
problem determination procedures, recommendations, diagnostic tools, reference
information, and instructions for contacting IBM.

To view the ACS messages, press Ctrl+C to return to the Contents. Next, select
the plus sign (+) or press the + key to view the list of ACS messages.


ΓòÉΓòÉΓòÉ 3.1. ACS0001 through ACS0097 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.1.1. ACS0001 ΓòÉΓòÉΓòÉ

ACS0001-E Subsystem Management cannot perform the requested APPC function at
this time, or the function is not available.

Originator: Subsystem Management

Explanation: An APPC communication interface error occurred.

User Response:

o Return to the main Subsystem Management window.

o Select Options from the menu bar, and then select Refresh.

o If the Communications Manager kernel does not have a status of Started,
  select Service, and then select Start from the menu bar.

o If the SNA subsystem does not have a status of Started, select Service, and
  then select Start from the menu bar.

o If either service does not start, note the resulting error message.

o If both services start, retry the operation that caused this message to
  appear.


ΓòÉΓòÉΓòÉ 3.1.2. ACS0002 ΓòÉΓòÉΓòÉ

ACS0002-I The requested APPC transaction program is not active.

Originator: Subsystem Management

User Response: Select Refresh from the menu bar to view an updated list of
active transaction programs.


ΓòÉΓòÉΓòÉ 3.1.3. ACS0005 ΓòÉΓòÉΓòÉ

ACS0005-W Transaction program name(64) was not deactivated.

where
name(64)        = transaction program name

Originator: Subsystem Management

Explanation: Either the program was already deactivated, or there is a problem
with the SNA Communications Subsystem.  Additional related messages might be
logged.

User Response:

o Check Subsystem Management to see whether the program is still active.  If
  the transaction program is not active, the problem has been resolved.

o Check the system message log for related messages.  If other messages
  indicate an SNA Communications Subsystem problem, take the corrective action
  recommended in the Help for those messages.  Then retry this operation.

o If the program is still active and deactivation does not work, there is a
  problem with the SNA Communications Subsystem.

o Check other SNA Communications Subsystem error messages for additional
  actions you can take.


ΓòÉΓòÉΓòÉ 3.1.4. ACS0012 ΓòÉΓòÉΓòÉ

ACS0012-W The request to deactivate the sessions for LU alias name(8), partner
LU alias name(8), and mode name name(8) was not completed.

where
name(8)         = LU alias name
name(8)         = partner LU alias name
name(8)         = mode name

Originator: Subsystem Management

Explanation: Either these sessions were already deactivated, or there is a
problem with the SNA Communications Subsystem.  Additional related messages
might be logged.

User Response:

o Select Refresh from the menu bar in the LU 6.2 Sessions window to see if the
  sessions have already been deactivated.

o Message ACS3356 is logged with this message.  Check the system error log for
  possible related error log entries.


ΓòÉΓòÉΓòÉ 3.1.5. ACS0017 ΓòÉΓòÉΓòÉ

ACS0017-E The file name name(40) is incorrect.  Specify a correct file name.

where
name(40)        = file name

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.6. ACS0019 ΓòÉΓòÉΓòÉ

ACS0019-E The specified path name(40) is incorrect.  Specify a valid path.

where
name(40)        = path name

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.7. ACS0020 ΓòÉΓòÉΓòÉ

ACS0020-E There is not enough space on the disk in drive d: to create this
file.  Specify a different disk drive, or free some disk space.

where
d:              = target drive

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.8. ACS0021 ΓòÉΓòÉΓòÉ

ACS0021-E There is not enough memory available to allocate the storage
specified for the trace buffer.  Specify a smaller storage size.

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.9. ACS0024 ΓòÉΓòÉΓòÉ

ACS0024-W A dump is about to begin.  For best results, end all unnecessary
applications and do not start any transaction programs.  When the dump begins,
all traces will be stopped automatically.

Originator: Problem Determination

User Response:

o Select OK to begin the dump if you think that the current level of system
  activity will not affect this dump.

o Select Cancel to cancel the dump request if too many applications are
  running.  End the unnecessary applications before beginning the dump.


ΓòÉΓòÉΓòÉ 3.1.10. ACS0028 ΓòÉΓòÉΓòÉ

ACS0028-E The specified file name(40) does not exist.  Specify the name of an
existing file.

where
name(40)        = file name

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.11. ACS0036 ΓòÉΓòÉΓòÉ

ACS0036-E There is not enough space on the disk in drive d: to copy the entire
storage trace to a file.  Specify a different disk, or free some disk space.

where
d:              = target drive

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.12. ACS0037 ΓòÉΓòÉΓòÉ

ACS0037-I XMODEM file transfer is operating in CRC error detection mode.

Originator: File Transfer

Explanation: The XMODEM file transfer is operating in CRC error detection mode.

User Response:

o Select Yes to create the specified directory and install Communications
  Manager in it.

o Select No and type the name of a valid directory to install Communications
  Manager in a different, existing directory.

Note: The default directory is c:\CM


ΓòÉΓòÉΓòÉ 3.1.13. ACS0038 ΓòÉΓòÉΓòÉ

ACS0038-E Not enough memory is available for the selected operation. Reduce the
number of programs running or add memory to the system; then retry the
operation.

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.14. ACS0039 ΓòÉΓòÉΓòÉ

ACS0039-E Not enough memory is available to complete the save operation. Reduce
the number of programs running on the system or add memory to the system; then
retry the operation.

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.1.15. ACS0076 ΓòÉΓòÉΓòÉ

ACS0076-I Verification for configuration name(255) has started.

where
name(255)       = configuration file name

Originator: Configuration Services - Verify

User Response: If errors occur during verification, note the configuration name
and the time that this message was logged, then check the verify log for
additional messages.  To view the verify log:

o Go to the FFST/2 folder:

o Select Message Log Formatter

o Substituting the disk drive letter of the disk drive that contains the active
  CMLIB directory for <drive>, either:

   - Type <drive>:\CMLIB\VERIFY.LOG in the File Name field, or

   - Change the formatter directory to <drive>:\CMLIB, then select VERIFY.LOG

o Select Open in the Message Log Formatter Open window.

If errors do not occur during verification, no additional messages are logged.


ΓòÉΓòÉΓòÉ 3.1.16. ACS0077 ΓòÉΓòÉΓòÉ

ACS0077-W Verification for configuration name(255) has ended with errors.

where
name(255)       = configuration file name

Originator: Configuration Services - Verify

User Response: Note the configuration name and the time that this message was
logged, then check the verify log for additional messages. To view the verify
log:

o Go to the FFST/2 folder.

o Select Message Log Formatter.

o Substituting the disk drive letter of the disk drive that contains the active
  CMLIB directory for <drive>, either:

   - Type <drive>:\CMLIB\VERIFY.LOG in the File Name field, or

   - Change the formatter directory to <drive>:\CMLIB, then select VERIFY.LOG.

o Select Open in the Message Log Formatter Open window.


ΓòÉΓòÉΓòÉ 3.1.17. ACS0078 ΓòÉΓòÉΓòÉ

ACS0078-E The local DTE address in X.25 link profile name(8) and the remote DTE
address in X.25 SVC directory entry profile name(8) are both set to
address(15). Change the DTE address field of one of the profiles to a different
address.

where
name(8)         = X.25 link name
name(8)         = X.25 directory name
address(15)     = X.25 DTE address

Originator: Configuration Services - Verify

Explanation: The remote DTE address of an X.25 SVC directory record entry
profile cannot be the same as the local DTE address of the associated X.25 link
profile.


ΓòÉΓòÉΓòÉ 3.1.18. ACS0079 ΓòÉΓòÉΓòÉ

ACS0079-W Verification for configuration name(255) has ended, but either
warning messages or information messages, or both, have been logged.

where
name(255)       = configuration file name

Originator: Configuration Services - Verify

User Response: Note the configuration name and the time that this message was
logged, then check the verify log for additional messages. To view the verify
log:

o Go to the FFST/2 folder.

o Select Message Log Formatter.

o Substituting the disk drive letter of the disk drive that contains the active
  CMLIB directory for <drive>, either:

   - Type <drive>:\CMLIB\VERIFY.LOG in the File Name field, or

   - Change the formatter directory to <drive>:\CMLIB, then select VERIFY.LOG.

o Select Open in the Message Log Formatter Open window.


ΓòÉΓòÉΓòÉ 3.1.19. ACS0083 ΓòÉΓòÉΓòÉ

ACS0083-E No more free system memory is available.  Verify cannot continue.

Originator: Configuration Services - Verify

Explanation: Verify was not able to allocate sufficient memory to continue.

User Response: If other non-essential processes are running, either stop them,
or wait for them to terminate, then retry Verify. If no other non-essential
processes are running, the system may not have sufficient memory installed to
be able to run Verify.


ΓòÉΓòÉΓòÉ 3.1.20. ACS0084 ΓòÉΓòÉΓòÉ

ACS0084-E The alternate APPN control file option name(4) was specified, but no
file name was given.

where
name(4)         = NLS token string

Originator: Configuration Services - Verify

Explanation: CMVERIFY was run with the option to use an alternate APPN control
file during Verify processing, but the alternate APPN control file name was not
specified.

User Response: If an alternate APPN control file is to be used during Verify
processing, rerun CMVERIFY with the file name after the option flag. If no
alternate APPN control file is to be used during Verify processing, rerun
CMVERIFY without specifying the alternate APPN control file option flag.


ΓòÉΓòÉΓòÉ 3.1.21. ACS0085 ΓòÉΓòÉΓòÉ

ACS0085-E The keylock option name(4) was specified, but no keylock key value
was given.

where
name(4)         = keylock token string

Originator: Configuration Services - Verify

Explanation: CMVERIFY was run with the option to use a keylock key value during
Verify processing, but the key value was not specified.

User Response: If the configuration is keylocked, rerun CMVERIFY with the 1 to
8 alphanumeric character keylock key value specified after the keylock option
flag. If the configuration is not keylocked, rerun CMVERIFY without specifying
the keylock option flag.


ΓòÉΓòÉΓòÉ 3.1.22. ACS0086 ΓòÉΓòÉΓòÉ

ACS0086-E The option name(4) is not a valid CMVERIFY option.

where
name(4)         = unsupported option

Originator: Configuration Services - Verify

Explanation: CMVERIFY was given an option flag that did not match any of those
supported.

User Response: Type CMVERIFY to display a list of valid options, then rerun
CMVERIFY with the correct options.


ΓòÉΓòÉΓòÉ 3.1.23. ACS0087 ΓòÉΓòÉΓòÉ

ACS0087-E No Communications Manager configuration name was specified.

Originator: Configuration Services - Verify

Explanation: CMVERIFY was invoked with options, but no Communications Manager
configuration name was specified.

User Response: Either rerun CMVERIFY with the desired Communications Manager
configuration name specified, or type CMVERIFY for more information.


ΓòÉΓòÉΓòÉ 3.1.24. ACS0088 ΓòÉΓòÉΓòÉ

ACS0088-E The alternate APPN control file name(255) does not exist.

where
name(255)       = file name string

Originator: Configuration Services - Verify

Explanation: The alternate APPN control file name passed to CMVERIFY cannot be
found.  Either the file name must have path information specified, or the file
must reside in a directory specified by the DPATH environment variable.

User Response: Either rerun CMVERIFY with a valid alternate APPN control file
name, or create the named alternate APPN control file and then run CMVERIFY as
before.


ΓòÉΓòÉΓòÉ 3.1.25. ACS0089 ΓòÉΓòÉΓòÉ

ACS0089-E The alternate NETWORK.INI file name(255) does not exist.

where
name(255)       = NETWORK.INI name string

Originator: Configuration Services - Verify

Explanation: The alternate NETWORK.INI file name passed to CMVERIFY cannot be
found.  Either the file name must have path information specified, or the file
must reside in a directory specified by the DPATH environment variable.
NETWORK.INI is created on a workstation when the software for the ISDN adapter
is installed (the Port Connection Manager software).

User Response: If the NETWORK.INI name that you entered is correct, but the
specified NETWORK.INI file does not exist, do one of the following:

o If the following conditions are true:

the configuration being verified is for another workstation, the other
workstation has Port Connection Managers installed and configured, and this
workstation does not have the Port Connection Manager software installed

o then either:

run CMVERIFY again, but do not specify the /i parameter, or install the Port
Connection Manager software on this workstation, following the adapter
manufacturer instructions, and then select Connection Manager configuration.

o If the following conditions are true:

the configuration being verified is for this workstation, and the Port
Connection Manager software for the ISDN adapter has not been installed on the
workstation, follow the adapter manufacturer instructions for installing the
adapter software

o then select Connection Manager configuration.

If the NETWORK.INI name that you entered is incorrect, run CMVERIFY again,
either:

o using the correct NETWORK.INI name after the /i option, or

o not specifying a NETWORK.INI name after the /i option to use the default
  NETWORK.INI name (<active cmlib path>\NETWORK.INI).


ΓòÉΓòÉΓòÉ 3.1.26. ACS0090 ΓòÉΓòÉΓòÉ

ACS0090-E CMVERIFY was run with the keylock option, but the keylock key value
specified was not between 1 and 8 alphanumeric characters long.

Originator: Configuration Services - Verify

User Response: If the configuration is keylocked, rerun CMVERIFY with the 1 to
8 alphanumeric character keylock key value specified after the keylock option
flag. If the configuration is not keylocked, rerun CMVERIFY without specifying
the keylock option flag.


ΓòÉΓòÉΓòÉ 3.1.27. ACS0091 ΓòÉΓòÉΓòÉ

ACS0091-E type(8) profile name(8), referenced by type(4) session name(8), does
not exist. Correct the keyboard profile name in the session configuration or
create the missing keyboard profile.

where
type(8)         = keyboard type strings
name(8)         = keyboard profile name
type(4)         = "3270/5250" emulator type strings
name(8)         = emulator session record name

Originator: Configuration Services - Verify

User Response: To gain access to the 3270 emulation or the 5250 keyboard
profile:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select the Options pull-down menu in the Communciations Manager Configuration
  Definition window.  Then select Configure any profile or feature... from the
  Options pull-down menu.

o Select 3270 emulation or 5250 emulation and then select Configure... in the
  Commmunications Manager Profile List window.

o Select Keyboard and then select the File pull-down menu in the 3270 Emulation
  or the 5250 Emulation window.  Then select Open from the File pull-down menu
  to change the keyboard profile.


ΓòÉΓòÉΓòÉ 3.1.28. ACS0094 ΓòÉΓòÉΓòÉ

ACS0094-E The SRPI session ID ID(8) specifies a 3270 long session name that is
not defined in any 3270 emulation session.  Either change the long session name
within the SRPI configuration or create a new 3270 emulation session with the
same long session name as that specified in the SRPI session.

where
ID(8)           = SRPI session ID

Originator: Configuration Services - Verify

User Response: To access the 3270 emulator configuration:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select 3270 emulation, and then select Configure in the Communications
  Manager Configuration List window.

To access the SRPI configuration:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select 3270 SRPI and then select Configure in the Communications Manager
  Configuration List window.


ΓòÉΓòÉΓòÉ 3.1.29. ACS0096 ΓòÉΓòÉΓòÉ

ACS0096-I Verification for configuration name(255) has ended.  No error or
warning conditions were found.

where
name(255)       = configuration file name

Originator: Configuration Services - Verify


ΓòÉΓòÉΓòÉ 3.1.30. ACS0097 ΓòÉΓòÉΓòÉ

ACS0097-I Dynamic update option selected.

Originator: Configuration Services - Verify

Explanation: CMVERIFY was called with the dynamic update parameter specified.

User Response: If you do not want dynamic update, rerun CMVERIFY without
specifying the dynamic update parameter.  For further CMVERIFY syntax
information, type CMVERIFY ?.


ΓòÉΓòÉΓòÉ 3.2. ACS0098 through ACS0134 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.2.1. ACS0098 ΓòÉΓòÉΓòÉ

ACS0098-I Dynamic update option not selected.

Originator: Configuration Services - Verify

Explanation: CMVERIFY was called without the dynamic update parameter
specified.

User Response: If you do not want dynamic update, rerun CMVERIFY with the
dynamic update parameter specified.  For further CMVERIFY syntax information,
type CMVERIFY ?.


ΓòÉΓòÉΓòÉ 3.2.2. ACS0099 ΓòÉΓòÉΓòÉ

ACS0099-I ISDN parameters will be verified.  Default NETWORK.INI to be used.

Originator: Configuration Services - Verify

Explanation: CMVERIFY was called with the ISDN verify option selected, and
without an alternate NETWORK.INI file name specified.

User Response: If you do not want the verification of ISDN parameters, rerun
CMVERIFY without the specifying the ISDN verify option. If you want the
verification of ISDN parameters, but an alternate NETWORK.INI file is to be
used, rerun CMVERIFY, specifying both the ISDN verify option and an alternate
NETWORK.INI file name. For further CMVERIFY syntax information, type CMVERIFY
?.


ΓòÉΓòÉΓòÉ 3.2.3. ACS0100 ΓòÉΓòÉΓòÉ

ACS0100-I ISDN parameters will be verified.  Alternate NETWORK.INI file
name(255) to be used.

where
name(255)       = alternate NETWORK.INI name

Originator: Configuration Services - Verify

Explanation: CMVERIFY was called with both the ISDN verify option and an
alternate NETWORK.INI file name specified.

User Response: If you do not want the verification of ISDN parameters, rerun
CMVERIFY without specifying the ISDN verify option. If you want the
verification of ISDN parameters, but no alternate NETWORK.INI file is to be
used, rerun CMVERIFY, specifying the ISDN verify option without an alternate
NETWORK.INI file name. For further CMVERIFY syntax information, type CMVERIFY
?.


ΓòÉΓòÉΓòÉ 3.2.4. ACS0101 ΓòÉΓòÉΓòÉ

ACS0101-I ISDN parameters will not be verified.

Originator: Configuration Services - Verify

Explanation: CMVERIFY was called without the ISDN verify option specified.

User Response: If you want verification of ISDN parameters, and if the default
NETWORK.INI file is to be used, rerun CMVERIFY, specifying the ISDN verify
option without an alternate NETWORK.INI file name. If you want verification of
ISDN parameters, and if an alternate NETWORK.INI file is to be used, rerun
CMVERIFY, specifying the ISDN verify option as well as an alternate NETWORK.INI
file name. If you want further CMVERIFY syntax information, type CMVERIFY ?.


ΓòÉΓòÉΓòÉ 3.2.5. ACS0102 ΓòÉΓòÉΓòÉ

ACS0102-E The configuration name cannot be specified as name(255) since it has
already been specified as name(255).

where
name(255)       = second configuration name
name(255)       = first configuration name

Originator: Configuration Services - Verify

Explanation: CMVERIFY has been called with two or more configuration name
parameters.  CMVERIFY can only be passed a single configuration name.

User Response: If one of the two configuration name parameters listed is
intended to be a CMVERIFY option, rerun the CMVERIFY file using the parameter
with the proper option syntax. If one of the two configuration name parameters
listed was not intended to be either a configuration name or a CMVERIFY option,
rerun CMVERIFY without specifying the parameter. If both configuration name
parameters listed are Communications Manager configurations that need to be
verified, rerun CMVERIFY separately for each one. For further CMVERIFY syntax
information, type CMVERIFY ?.


ΓòÉΓòÉΓòÉ 3.2.6. ACS0103 ΓòÉΓòÉΓòÉ

ACS0103-E Configuration name(255) was not created with this version of
Communications Manager.  The configuration will need to be upgraded.

where
name(255)       = configuration file name

Originator: Configuration Services - Verify

Explanation: The named configuration was created on a past release of
Communications Manager, and therefore must be upgraded to be used with this
release.

User Response: To upgrade the configuration to this release of Communications
Manager, run CMUPGRAD with the configuration name specified.


ΓòÉΓòÉΓòÉ 3.2.7. ACS0104 ΓòÉΓòÉΓòÉ

ACS0104-I For directions on viewing the Verify messages, type HELP ACSnnnn at
the OS/2 command prompt.

where
nnnn            = ACS message number string

Originator: Configuration Services - Verify

Explanation: CMVERIFY has ended with warning or error messages being logged.

User Response: For directions on how to use the Message Log Formatter to view
the messages logged by Verify, type HELP ACSnnnn at the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.2.8. ACS0106 ΓòÉΓòÉΓòÉ

ACS0106-E An internal error caused APPC to stop. Stop all transaction programs.
Then stop and restart Communications Manager.

Originator: SNA Communications Services (APPC)

User Response: If the problem persists, note the time, date, and message
number; then contact your service coordinator.

Note: Associated error log entries might have been logged at the same time and
date as this message.


ΓòÉΓòÉΓòÉ 3.2.9. ACS0107 ΓòÉΓòÉΓòÉ

ACS0107-E A system error occurred while running APPC.  The request code is
rc(4) and the return code is rc(4).

where
rc(4)           = OS/2 request code
rc(4)           = OS/2 return code

Originator: SNA Communications Services (APPC)

User Response: Note the request code, return code, time, date, and message
number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.2.10. ACS0108 ΓòÉΓòÉΓòÉ

ACS0108-E A system resource limitation was reached while running APPC.  The
request code is rc(4) and the return code is rc(4).

where
rc(4)           = OS/2 request code
rc(4)           = OS/2 return code

Originator: SNA Communications Services (APPC)

User Response: 1.  Make more memory available by stopping other programs that
are not being used. 2.  Check that swapping is enabled in the CONFIG.SYS file.
3.  Restart the system. If the problem persists, note the following:

o The request code

o The names of other active programs

o Time, date, return codes and message number; then contact your service
  coordinator.


ΓòÉΓòÉΓòÉ 3.2.11. ACS0109 ΓòÉΓòÉΓòÉ

ACS0109-E An internal error was found in configuration file name(64) when APPC
was started.  Ensure that the configuration file name is correct, and then
restart Communications Manager.

where
name(64)        = configuration file name

Originator: SNA Communications Services (APPC)

User Response: If necessary, restore the configuration file using a backup copy
or create a new configuration file.  Then restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.2.12. ACS0110 ΓòÉΓòÉΓòÉ

ACS0110-E APPC previously ended because of an internally detected error. Stop
all transaction programs that use APPC, including Communications Manager
Subsystem Manager.  Then restart APPC.

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 3.2.13. ACS0111 ΓòÉΓòÉΓòÉ

ACS0111-W Adapter num(2) for name(5) Data Link Control (DLC) cannot be
activated. APPC is started and active, but cannot use this adapter.  You can
continue to use APPC with another available adapter.

where
num(2)          = adapter number
name(5)         = DLC name

Originator: SNA Communications Services (APPC)

User Response:

o Ensure that the adapter for this DLC is present.

o Verify that the configuration file specifies the proper adapter number and
  type.

If you change the configuration file, you must stop and restart Communications
Manager.


ΓòÉΓòÉΓòÉ 3.2.14. ACS0112 ΓòÉΓòÉΓòÉ

ACS0112-E APPC initiation failed while attempting to load a dynamic link
routine.  Critical file name(8) was not found, or it was modified or damaged.
The error type is rc(4). Restore this file to the Communications Manager
directory using a backup copy.

where
name(8)         = file name
rc(4)           = error code

Originator: SNA Communications Services (APPC)

User Response: If you do not have a backup copy of this file, reinstall
Communications Manager.


ΓòÉΓòÉΓòÉ 3.2.15. ACS0113 ΓòÉΓòÉΓòÉ

ACS0113-E A request to start transaction program name(64) was received, but was
not completed.  Start the specified transaction program.

where
name(64)        = transaction program name

Originator: SNA Communications Services (APPC)

Explanation: One or more of the following conditions exists:

o The transaction program has not been loaded.

o The transaction program has not yet called APPC.

o The transaction program file was not created correctly or is damaged.

User Response: If you have already started the specified transaction program,
ensure that you have a working copy of the transaction program.


ΓòÉΓòÉΓòÉ 3.2.16. ACS0114 ΓòÉΓòÉΓòÉ

ACS0114-E APPC initiation failed while attempting to load a translation table
file.  Translation table file name(64) is not valid.

where
name(64)        = transaction program name

Originator: SNA Communications Services (APPC)

Explanation: Likely causes of the error are:

o A character in the translation table was not valid.  The only characters
  valid in a translation table are numerals 0 - 9 and the uppercase letters A -
  F.

o A translation table file name was not correctly specified in the
  configuration file.

o The translation table file was not created correctly.  A valid translation
  table file contains 32 lines.  Each line must contain 32 characters and end
  in a carriage return and line feed (CR/LF).

o The file was modified or damaged.

User Response: Ensure that the proper translation table file name was
specified. If the translation table file was modified or damaged, restore it
from a backup copy or create a new file.  Then restart APPC.


ΓòÉΓòÉΓòÉ 3.2.17. ACS0115 ΓòÉΓòÉΓòÉ

ACS0115-W APPC initiation failed while attempting to load a translation table
file.  Translation table file name(64) is too small.

where
name(64)        = translation table file name

Originator: SNA Communications Services (APPC)

Explanation: Likely causes of the error are:

o The specified translation table file was less than 1088 bytes in length.

o A translation table file name was not correctly specified in the
  configuration file.

o The translation table file was not created correctly.  A valid translation
  table file contains 32 lines.  Each line must contain 32 characters and end
  in a CR/LF.

o The file was modified or damaged.

User Response: Ensure that the proper translation table file name was
specified. If the translation table file was modified or damaged, restore it
from a backup copy or create a new file.  Then restart APPC.


ΓòÉΓòÉΓòÉ 3.2.18. ACS0117 ΓòÉΓòÉΓòÉ

ACS0117-W APPC initiation failed while attempting to load translation table
file name(64).  The return code rc(4) occurred.

where
rc(4)           = return code
name(64)        = translation table file name

Originator: SNA Communications Services (APPC)

Explanation: Likely causes of the error are:

o A translation table file name was not correctly specified in the
  configuration file.

o The file has been modified or damaged.

User Response: Ensure that the proper translation table file name was
specified. If the translation table file was modified or damaged, restore it
from a backup copy or create a new file.  Then restart APPC.

Note: This return code is from the DosOpen command.  For additional
information, type HELP nnnn at the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.2.19. ACS0118 ΓòÉΓòÉΓòÉ

ACS0118-E APPC initiation failed while attempting to open configuration file
name(64).  The return code rc(4) occurred because the file was modified or
damaged.

where
name(64)        = configuration file name
rc(4)           = return code

Originator: SNA Communications Services (APPC)

User Response: Restore the configuration file from a backup copy or create a
new one.  Then restart Communications Manager.

Note: This return code is from the DosOpen command.  For additional
information, type HELP nnnn at the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.2.20. ACS0121 ΓòÉΓòÉΓòÉ

ACS0121-E SDLC adapter adapter number could not be activated.

where
adapter number  = adapter number

Originator: Synchronous Data Link Control (SDLC)

User Response: For the native (non-ISDN) SDLC environment, ensure that:

o A DEVICE= statement is specified in the CONFIG.SYS file.

o There are no interrupt level conflicts which prevent the specified adapter
  from being accessed in the appropriate mode (Shareable or Non-shareable).

o The specified adapter is properly installed.

o The specified adapter is functioning properly.  Refer to the IBM Guide to
  Operations for additional information.

For the SDLC using ISDN environment, ensure that:

o The CONFIG.SYS file contains a DEVICE= statement for the SDLC using ISDN
  device driver(s).

o The CONFIG.SYS file contains a DEVICE= statement for the PROTMAN.OS2 file.

o The CONFIG.SYS file contains a RUN= statement for NETBIND.EXE.

o The PROTOCOL.INI file exists and contains the correct BINDINGS= statement for
  the SDLC using ISDN device driver(s).


ΓòÉΓòÉΓòÉ 3.2.21. ACS0122 ΓòÉΓòÉΓòÉ

ACS0122-I Dial a valid telephone number to establish the SDLC connection for
this adapter.

Originator: Synchronous Data Link Control (SDLC)


ΓòÉΓòÉΓòÉ 3.2.22. ACS0123 ΓòÉΓòÉΓòÉ

ACS0123-E Transmission is blocked on session name(8).  Switch to the specified
3270 logical terminal session and display the host ECF logo.  SRPI data will be
transmitted when the logo has been displayed.  Resume any tasks that might have
been interrupted.

where
name(8)         = SRPI session name

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: An unsolicited message arrived from the host system while ECF data
was being transmitted to or from the host system.


ΓòÉΓòÉΓòÉ 3.2.23. ACS0124 ΓòÉΓòÉΓòÉ

ACS0124-W SRPI server name(8) is unknown to the host system on Session ID
ID(8).  The Send_Request did not complete.

where
name(8)         = SRPI server name
ID(8)           = SRPI session ID

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: The SRPI application attempted to request information from an
unknown SRPI server on the host system.  Because this server does not appear in
the host's routing table, the host system did not recognize the request from
the workstation.

User Response: Determine why the server name is missing from the host routing
table.

o If the specified SRPI server is not available on the host system, have the
  host system administrator install it.

o If the SRPI server is available but incorrectly named in the configuration
  file, correct the name.

o If the SRPI server name is derived from an SRPI server profile, update the
  SRPI server profile with the correct name.


ΓòÉΓòÉΓòÉ 3.2.24. ACS0125 ΓòÉΓòÉΓòÉ

ACS0125-W SRPI server name(8) is not defined in the SRPI configuration.  The
Send_Request did not complete.

where
name(8)         = SRPI server name

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: The specified SRPI server name is not defined as an alias in the
configuration file.  In addition, default routing is not defined in the
configuration file.

User Response:

o Ensure that the SRPI application specified the correct server alias in the
  configuration file.

o Add an SRPI server profile to the configuration file that defines the desired
  server alias.

o Add an SRPI server that defines a default route to the desired 3270 session.


ΓòÉΓòÉΓòÉ 3.2.25. ACS0126 ΓòÉΓòÉΓòÉ

ACS0126-W SRPI has ended unexpectedly.  Stop all applications using SRPI. Stop
and restart the 3270 Terminal Emulator sessions.  Then restart any applications
using SRPI.

Originator: SRPI (Sender-Requester Programming Interface)


ΓòÉΓòÉΓòÉ 3.2.26. ACS0128 ΓòÉΓòÉΓòÉ

ACS0128-E The specified service could not be started because file name(12), or
one of the file's imported dynamic link libraries, could be missing or located
in the wrong directory.

where
name(12)        = critical file name

Originator: Communications Manager Kernel

User Response: Ensure that the file is located in the correct directory:

o If it is an executable file, move it to the current CMLIB directory.

o If it is a dynamic link library, move it to the current CMLIB\DLL directory.

If the specified file exists in the correct directory, then one or more of the
associated dynamic link library files could be missing or in the wrong
directory.

o Determine which dynamic link library files are associated with the file.

o Ensure that each dynamic link library file is located in the current
  CMLIB/DLL directory.

o If any of the files are missing, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.2.27. ACS0129 ΓòÉΓòÉΓòÉ

ACS0129-E Communications Manager cannot be started from the OS/2 command prompt
by invoking the name of the executable file.

Originator: Communications Manager Kernel

User Response: Communications Manager can be started by:

o Typing CM from the OS/2 command prompt with an optional configuration name.

o Autostarting Communications Manager from the CONFIG.SYS file by adding
  run=path\CM.CMD with an optional configuration name.

o Starting the Communications Manager kernel from subsystem management.

o Starting communications from the Communications Manager/2 folder.


ΓòÉΓòÉΓòÉ 3.2.28. ACS0131 ΓòÉΓòÉΓòÉ

ACS0131-E The specified configuration name(255) has not been successfully
verified. Close this window and restart Communications Manager using a valid
configuration

where
name(255)       = configuration file name

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.2.29. ACS0132 ΓòÉΓòÉΓòÉ

ACS0132-E Communications Manager is already active with a configuration that is
different than the one specified in this request.  The active configuration is
name(12).

where
name(12)        = configuration file name

Originator: Communications Manager Kernel

User Response: To run Communications Manager with the configuration specified
in this request, stop Communications Manager, and then restart it with the new
configuration.  To start from the OS/2 command prompt, type CM X where X is
your configuration or use the Replace Default Configuration utility to make the
desired configuration the default, then select Start Communications in the
Communications Manager/2 folder.


ΓòÉΓòÉΓòÉ 3.2.30. ACS0134 ΓòÉΓòÉΓòÉ

ACS0134-E An error occurred while attempting to access the configuration
name(255).

where
name(255)       = configuration file name

Originator: Communications Manager Kernel

Explanation: One possible cause of the error is that the configuration is in
use and locked by another application.

User Response:

o Allow the application using the configuration to complete, or terminate that
  application, then restart Communications Manager.

o For detailed information, use FFST/2 to access the Message Log and review the
  associated error log entry.


ΓòÉΓòÉΓòÉ 3.3. ACS0141 through ACS0242 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.3.1. ACS0141 ΓòÉΓòÉΓòÉ

ACS0141-E The specified configuration name(255) is not valid or cannot be found
in the Communications Manager subdirectory.  Close this window and restart
Communications Manager using a valid configuration and path.

where
name(255)       = configuration file name

Originator: Communications Manager Kernel

Explanation: The specified configuration, path, or both is not correct.

User Response: If you are using the Default configuration, use the Replace
Default Configuration utility to specify a different configuration.
Communications Manager can be restarted from the Communications Manager/2
folder or from an OS/2 command prompt. Make sure the configuration is typed
correctly at the OS/2 command prompt. Do not include the path value on the OS/2
command prompt. The path information will be extracted from the CMConfigPath
parameter in the CM.INI file.


ΓòÉΓòÉΓòÉ 3.3.2. ACS0142 ΓòÉΓòÉΓòÉ

ACS0142-E The specified configuration file name is longer than the 8-character
maximum.

Originator: Communications Manager Kernel

User Response: Close this window and restart Communications Manager using a
valid configuration file name that is 8 or fewer characters. Do not specify a
path or extension.


ΓòÉΓòÉΓòÉ 3.3.3. ACS0143 ΓòÉΓòÉΓòÉ

ACS0143-I All Communications Manager services have ended successfully.

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.3.4. ACS0144 ΓòÉΓòÉΓòÉ

ACS0144-E The selected service, type(8), cannot be started.  The maximum number
of screen groups has been reached.  Close one or more screen groups and try to
start the service again.

where
type(8)         = type of service

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.3.5. ACS0145 ΓòÉΓòÉΓòÉ

ACS0145-E One or more of the selected services cannot be auto-started.  The
maximum number of screen groups has been reached.  Close one or more screen
groups and try to start the services again.

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.3.6. ACS0157 ΓòÉΓòÉΓòÉ

ACS0157-W The NETWORK.INI file name(255) does not exist.  Ignore this message
if this configuration is to be used on a different workstation, and if Port
Connection Managers are installed and configured on the other workstation.

where
name(255)       = NETWORK.INI name

Originator: Configuration Services - Verify

Explanation: The fully-qualified NETWORK.INI file name specified does not
exist.  NETWORK.INI is created on a workstation when the software for the ISDN
adapter is installed (the Port Connection Manager software).

User Response: If the NETWORK.INI name that you entered is correct, but the
specified NETWORK.INI file does not exist, do one of the following:

o If all of the following conditions exist:

the CMVERIFY OS/2 command prompt interface is being used, the configuration
being verified is for another workstation, the other workstation has Port
Connection Managers installed and configured, and this workstation does not
have the Port Connection Manager software installed

o then perform the following actions:

run CMVERIFY again, but do not specify the /i parameter, or install the Port
Connection Manager software on this workstation following the adapter
manufacturer instructions, and then select Connection Manager configuration.

o If the configuration being verified is for this workstation and the Port
  Connection Manager software for the ISDN adapter has not been installed on
  the workstation, follow the adapter manufacturer instructions for installing
  the adapter software. Then select Connection Manager configuration.

If the NETWORK.INI name that you entered is incorrect, do one of the following:

o If the CMVERIFY OS/2 command prompt interface is being used, run CMVERIFY
  again, either:

using the correct NETWORK.INI name after the /i option, or not specifying a
NETWORK.INI name after the /i option to use the default NETWORK.INI name
(<active cmlib path>\NETWORK.INI).

o If you are using the Configuration windows, run Configuration again and type
  the correct NETWORK.INI name when prompted.


ΓòÉΓòÉΓòÉ 3.3.7. ACS0158 ΓòÉΓòÉΓòÉ

ACS0158-E The NETWORK.INI file name(255) is corrupted.

where
name(255)       = NETWORK.INI name

Originator: Configuration Services - Verify

Explanation: The fully-qualified NETWORK.INI file name specified has been
damaged.  NETWORK.INI is created on a workstation when the software for the
ISDN adapter is installed (the Port Connection Manager software).

User Response:

o If you have a backup copy of your NETWORK.INI file, make a copy of this
  backup with the same name and path as the corrupted file.

If you do not have a backup copy of your NETWORK.INI file, reinstall the
adapter software, following the adapter manufacturer instructions, and then
select Connection Manager configuration.

o If the CMVERIFY OS/2 command prompt interface is being used, run CMVERIFY
  again, either:

   - using the NETWORK.INI name after the /i option, or

   - not specifying a NETWORK.INI name after the /i option to use the default
     NETWORK.INI name (<active cmlib path>\NETWORK.INI).

o If using the Configuration windows, run Configuration again and enter the
  correct NETWORK.INI name when prompted.


ΓòÉΓòÉΓòÉ 3.3.8. ACS0159 ΓòÉΓòÉΓòÉ

ACS0159-E A Connection Manager configuration call failed during ISDN parameter
verification.

Originator: Configuration Services - Verify

User Response:

o Run Connection Manager configuration again.

o If the problem persists, reinstall the ISDN feature, then run Connection
  Manager configuration again.

o If the problem still persists, note the time, date, and this message number;
  then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.3.9. ACS0169 ΓòÉΓòÉΓòÉ

ACS0169-W Verification of the configuration is complete. Warning messages were
logged.

Originator: Configuration Services

User Response: Check the associated verify log entries for additional
information.  To view the verify log:

o Go to the FFST/2 folder.

o Select Message Log Formatter.

o Substituting the disk drive letter of the disk drive that contains the active
  CMLIB directory for <drive>, either:

o Type <drive>:\CMLIB\VERIFY.LOG in the File Name field, or

o Change the formatter directory to <drive>:\CMLIB, then select VERIFY.LOG.

o Select Open in the Message Log Formatter Open window.


ΓòÉΓòÉΓòÉ 3.3.10. ACS0170 ΓòÉΓòÉΓòÉ

ACS0170-E Verification of the configuration is complete.  Error messages were
logged.  Communications Manager cannot be started using this configuration.

Originator: Configuration Services

User Response: Check the associated verify log entries for additional
information.  To view the verify log:

o Go to the FFST/2 folder:

o Select Message Log Formatter

o Substituting the disk drive letter of the disk drive that contains the active
  CMLIB directory for <drive>, either:

o Type <drive>:\CMLIB\VERIFY.LOG in the File Name field, or

o Change the formatter directory to <drive>:\CMLIB, then select VERIFY.LOG

o Select Open in the Message Log Formatter Open window.


ΓòÉΓòÉΓòÉ 3.3.11. ACS0176 ΓòÉΓòÉΓòÉ

ACS0176-E A storage trace record is incorrect.  Part of the trace might have
been saved to the target file name(40).  Retry the operation.

where
name(40)        = file name

Originator: Problem Determination

Explanation: An incorrect record was encountered while the storage trace data
was being copied to the file.  Data will be stored incorrectly in the future.
The copy was ended and the partial file was closed.


ΓòÉΓòÉΓòÉ 3.3.12. ACS0179 ΓòÉΓòÉΓòÉ

ACS0179-W An incoming allocation request indicated that transaction program
name(64) could not be started.

where
name(64)        = transaction program name

Originator: SNA Communications Services (APPC)

Explanation: Likely causes of the error are:

o A transaction program file specification is not correct in the configuration
  file.

o The transaction program file was not created correctly or is damaged.

User Response:

o Ensure that you have a working copy of the transaction program.

o Ensure that the transaction program file specification is correct in the
  configuration file.

o If the file is not in the specified path, copy it to that path, or change the
  configuration for this transaction program by specifying desired path and
  file name.

o If you change the configuration file to update the transaction program file
  specification, you must stop and restart the attach manager to use the new
  file.

o If the configuration file is changed to update the transaction program file
  specification, the attach manager must be stopped and restarted to use the
  new file.

Note: The incoming allocation request that started the Load Transaction Program
request was rejected.  The partner node must send the allocation request again
in order to use the updated transaction program file specification.


ΓòÉΓòÉΓòÉ 3.3.13. ACS0196 ΓòÉΓòÉΓòÉ

ACS0196-E The 3270 Terminal Emulator session was stopped and restarted, but an
active SRPI application was not stopped.  Stop all applications that were using
the SRPI feature when the 3270 Terminal Emulator session was stopped.  Then
restart the appropriate applications.

Originator: SRPI (Sender-Requester Programming Interface)


ΓòÉΓòÉΓòÉ 3.3.14. ACS0226 ΓòÉΓòÉΓòÉ

ACS0226-I TRANS100  The file transfer was canceled because the specified
terminal session is not available.  Switch to a different session, or wait for
the specified session to become available.  Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.15. ACS0227 ΓòÉΓòÉΓòÉ

ACS0227-E File transfer is blocked for session name(8).  Switch to the
specified Terminal Emulator session and clear the emulator screen.
Transmission of file transfer data will resume when the screen is cleared.

where
name(8)         = session name

Originator: File Transfer

Explanation: An unsolicited message arrived from the host system while file
transfer data was being transmitted to or from the host system.


ΓòÉΓòÉΓòÉ 3.3.16. ACS0228 ΓòÉΓòÉΓòÉ

ACS0228-I TRANS014  The file transfer was canceled because the file from the
host system could not be received.  Retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.17. ACS0229 ΓòÉΓòÉΓòÉ

ACS0229-I TRANS015  The file transfer was canceled because the required amount
of host storage (memory) is not available.  Note the time, date, and this
message number; then, contact the host service coordinator to obtain more
storage.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.18. ACS0230 ΓòÉΓòÉΓòÉ

ACS0230-I TRANS016  The file transfer was canceled because an incorrect request
code was detected.

Originator: File Transfer

Explanation: The sending or receiving Communications Manager file transfer
application sent a parameter that is not valid.

User Response: Note the time, date, and this message number, then contact the
host service coordinator to check that the current version of the host file
transfer program is properly installed on the host computer.


ΓòÉΓòÉΓòÉ 3.3.19. ACS0231 ΓòÉΓòÉΓòÉ

ACS0231-I TRANS017  The file transfer was canceled because the Time Sharing
Options (TSO) data set name is incorrect or missing.  Specify the correct name,
and then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.20. ACS0232 ΓòÉΓòÉΓòÉ

ACS0232-I TRANS017  The file transfer was canceled because the VM/CMS file name
is incorrect or missing.  Specify the correct name, and then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.21. ACS0233 ΓòÉΓòÉΓòÉ

ACS0233-I TRANS018  The file transfer was canceled because the option specified
is not valid. Specify a valid option, and then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.22. ACS0234 ΓòÉΓòÉΓòÉ

ACS0234-I TRANS124 Message msg(254) was received from the host system.  For
assistance, see the host documentation.

where
msg(254)        = host application message

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.23. ACS0235 ΓòÉΓòÉΓòÉ

ACS0235-I TRANS026  The file transfer ended unexpectedly.  Retry the file
transfer.

Originator: File Transfer

Explanation: An internal error occurred while a file transfer was in progress,
and the file transfer ended. Like causes include OS/2 errors and program
errors.

User Response: Try the file transfer again. If the problem persists, view the
system error log and contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.3.24. ACS0236 ΓòÉΓòÉΓòÉ

ACS0236-I TRANS027  The file transfer was canceled at the user's request.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.25. ACS0237 ΓòÉΓòÉΓòÉ

ACS0237-I File transfer is complete.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.26. ACS0238 ΓòÉΓòÉΓòÉ

ACS0238-I TRANS004  The file transfer is complete.  Some records were separated
because one or more records exceeded the record length of the destination file.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.27. ACS0239 ΓòÉΓòÉΓòÉ

ACS0239-I TRANS007  The file transfer was canceled because the host connection
was not established.  Establish the host connection, and then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.28. ACS0240 ΓòÉΓòÉΓòÉ

ACS0240-I TRANS011  The file transfer was canceled because the host connection
was disconnected.  Re-establish the host connection, and then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.29. ACS0241 ΓòÉΓòÉΓòÉ

ACS0241-I TRANS013  The file transfer was canceled because the host program
detected an error in the file data or because the wrong version of the host
program is being used.  Retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.3.30. ACS0242 ΓòÉΓòÉΓòÉ

ACS0242-I TRANS035  The file transfer was canceled because the specified VM/CMS
disk is a read-only disk.

Originator: File Transfer

Explanation: You do not have write access to the specified VM/CMS disk.

User Response:

o Specify a VM/CMS disk for which you have write access, and retry the file
  transfer.

o If the specified disk is the required disk for the host file, contact the
  disk owner to gain write access to the disk.  Then retry the file transfer.


ΓòÉΓòÉΓòÉ 3.4. ACS0243 through ACS0272 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.4.1. ACS0243 ΓòÉΓòÉΓòÉ

ACS0243-I TRANS036  The file transfer was canceled because the specified VM/CMS
disk cannot be accessed.

Originator: File Transfer

Explanation: You do not have access to the specified VM/CMS disk.

User Response:

o Specify a VM/CMS disk for which you have access and retry the file transfer.

o If the specified disk is the required disk for the host file, obtain access
  to the VM/CMS disk and retry the file transfer.


ΓòÉΓòÉΓòÉ 3.4.2. ACS0244 ΓòÉΓòÉΓòÉ

ACS0244-I TRANS037  The file transfer was canceled because the specified VM/CMS
disk is full.

Originator: File Transfer

Explanation: Likely causes are:

o The disk contains the maximum number of files

o The file contains the maximum number of data blocks.

User Response: Specify another disk with enough space, or remove files from the
specified disk.  If the workstation file is large (over 1MB), consider dividing
it into several files.  Then retry the file transfer.


ΓòÉΓòÉΓòÉ 3.4.3. ACS0245 ΓòÉΓòÉΓòÉ

ACS0245-I TRANS099  The file transfer was canceled because the host system
returned error code rc(4).  Retry the file transfer.

where
rc(4)           = system error code

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.4. ACS0246 ΓòÉΓòÉΓòÉ

ACS0246-I TRANS000  The file transfer was canceled because the host system
detected an error in the file data, or because an unidentified system error
occurred during file transfer. Retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.5. ACS0247 ΓòÉΓòÉΓòÉ

ACS0247-I TRANS017  The file transfer was canceled because the CICS file name
is incorrect or missing.  Specify the correct CICS file name, and then retry
the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.6. ACS0248 ΓòÉΓòÉΓòÉ

ACS0248-I TRANS019  The file transfer was canceled because an error occurred
while processing the host file.

Originator: File Transfer

Explanation: One of the following errors occurred:

o For VM/TSO, there is not enough space available for data on the host system.

o For CICS, two possible errors are:

o During a host system GET operation, the file name did not match the name of
  the current terminal file, or an error occurred while constructing or reading
  the file.

o During a host system PUT operation, the file could not be stored in the
  temporary storage for the current file, or an error occurred while reading
  the file data.

User Response:

o For VM/TSO, free some space on the host system, and respond to any host
  session messages.  Then retry the file transfer.

o For CICS, check the contents of the current file for this workstation. If you
  provided the data for the file, check your program for program errors and
  resource constraints.  Then retry the file transfer.


ΓòÉΓòÉΓòÉ 3.4.7. ACS0249 ΓòÉΓòÉΓòÉ

ACS0249-I TRANS025  The file transfer was canceled because the keyboard input
is inhibited for the host session.  Switch to the emulator session to determine
why the keyboard is inhibited.  Correct the problem, and then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.8. ACS0250 ΓòÉΓòÉΓòÉ

ACS0250-I TRANS027  File transfer was canceled because the communication
sequence with the host was disrupted.  Clear the screen for the emulator
session.  Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.9. ACS0251 ΓòÉΓòÉΓòÉ

ACS0251-I TRANS028  The file transfer was canceled because option parm(254) is
not valid.  Correct the option, and then retry the file transfer.

where
parm(254)       = file transfer option parameter

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.10. ACS0252 ΓòÉΓòÉΓòÉ

ACS0252-I TRANS029  The file transfer was canceled because option parm(254) is
not valid with RECEIVE.  Correct the command or the option.  Then retry the
file transfer.

where
parm(254)       = file transfer option parameter

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.11. ACS0253 ΓòÉΓòÉΓòÉ

ACS0253-I TRANS030  The file transfer was canceled because option parm(254) is
not valid with APPEND. Remove the option from the command.  Then retry the file
transfer.

where
parm(254)       = file transfer option parameter

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.12. ACS0254 ΓòÉΓòÉΓòÉ

ACS0254-I TRANS031  The file transfer was canceled because option parm(254)
cannot be used without the SPACE option. Remove the option from the command, or
add the SPACE option to the command.  Then retry the file transfer.

where
parm(254)       = file transfer option parameter

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.13. ACS0255 ΓòÉΓòÉΓòÉ

ACS0255-I TRANS032  The file transfer was canceled because option parm(254) is
not valid with a host system partitioned data set. Remove the option from the
command.  Then retry the file transfer.

where
parm(254)       = file transfer option parameter

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.14. ACS0256 ΓòÉΓòÉΓòÉ

ACS0256-I TRANS033  The file transfer was canceled because only one of these
options (TRACKS, CYLINDERS, AVBLOCK) can be used at a time.  Remove the
unnecessary options from the command.  Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.15. ACS0257 ΓòÉΓòÉΓòÉ

ACS0257-I TRANS034  The file transfer was canceled because the specified VM/CMS
file was not found. Specify the correct name for an existing VM/CMS file. Then
retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.16. ACS0258 ΓòÉΓòÉΓòÉ

ACS0258-I TRANS010  The host system is not responding to the workstation file
transfer program (SEND or RECEIVE).  Switch to the emulator session.

Originator: File Transfer

Explanation: Likely causes are:

o The system is operating slowly, or you are communicating with a remote host
  system.

o There is a network problem.

o The required file transfer program is not installed on the host system.

o Transmission of the file transfer is blocked because of an unsolicited
  message.  (On VM, the host displays HOLDING.)

o You are not logged on to the host.

o The data transfer buffer is too large.

o The host computer cannot be configured to support EXTENDED DATA STREAM for
  this terminal.

User Response:

o If the system is working slowly, sometimes this message is displayed, but the
  file transfer continues.  Wait for the transfer to be completed.

o If the host session displays HOLDING, or is not accepting input, clear the
  emulator screen.  This should start the file transfer.

o If the host keyboard is locked, an indicator is displayed at the bottom of
  the screen.  Wait until the indicator is removed.  Then retry the file
  transfer.

o To stop the file transfer:

o If the required host file transfer program is not installed on the host
  system, press the Cancel (Esc) key.

o If you initiated file transfer from a menu, press the Break key.

o If you initiated file transfer from the OS/2 command prompt, press the
  Control (Ctrl) and Pause keys.

o If you are not logged on, cancel the file transfer, log on to the host
  system, and then retry the file transfer.

o In the 3270 terminal emulation logical profile, set the data buffer size to a
  smaller value.

Note: You may have to press the Reset key to clear the operator information
area.  If necessary, end the host program.


ΓòÉΓòÉΓòÉ 3.4.17. ACS0259 ΓòÉΓòÉΓòÉ

ACS0259-I TRANS101  The file transfer was canceled because transmission errors
occurred during the XMODEM file transfer.  The data might be corrupted.  These
errors might be caused by a faulty communication line.  Reestablish the
connection, and then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.18. ACS0260 ΓòÉΓòÉΓòÉ

ACS0260-I TRANS102  The file transfer was canceled because no data was received
within the last 90 seconds.  Retry the file transfer.

Originator: File Transfer

Explanation: Likely causes are:

o The sending system did not begin the SEND XMODEM operation within 90 seconds
  after the RECEIVE request was sent.

o An error originated with the sender.

User Response:

o Check the file that should have received the data.  If no data was received,
  verify that the sender is using a compatible XMODEM protocol.  If the sender
  is not using a compatible protocol, retry the file transfer with a protocol
  that is compatible.

o If the sender is using the correct protocol, ensure that the SEND operation
  begins within 90 seconds after the RECEIVE request is sent.

o If a transmission error caused only part of a file to be sent, check with the
  sender to see if there was a temporary problem with that system.  Retry the
  file transfer when the sender's communications problems are resolved.


ΓòÉΓòÉΓòÉ 3.4.19. ACS0261 ΓòÉΓòÉΓòÉ

ACS0261-I TRANS103  The file transfer was canceled because the connection was
disconnected or is not active.  Reestablish the connection, and then retry the
file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.20. ACS0262 ΓòÉΓòÉΓòÉ

ACS0262-I TRANS104  The file transfer was canceled because the receiving system
is not ready.  Retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.21. ACS0263 ΓòÉΓòÉΓòÉ

ACS0263-I TRANS105  The file transfer was canceled because the previous block
of data was not acknowledged by the receiving system. Check for a temporary
problem with the receiving system.  Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.22. ACS0264 ΓòÉΓòÉΓòÉ

ACS0264-I TRANS106  The end of transmission (EOT) was not acknowledged by the
receiving system.  Check with the receiving system to correct the problem.
Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.23. ACS0265 ΓòÉΓòÉΓòÉ

ACS0265-I TRANS107  An ASCII terminal emulation menu is displayed.  The session
is not available for file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.24. ACS0266 ΓòÉΓòÉΓòÉ

ACS0266-I The file transfer request is being processed.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.25. ACS0267 ΓòÉΓòÉΓòÉ

ACS0267-I Number of bytes transferred:  num(10).

where
num(10)         = current number of bytes transferred

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.26. ACS0268 ΓòÉΓòÉΓòÉ

ACS0268-I Number of blocks transferred:  num(10).

where
num(10)         = current number of blocks transferred

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.27. ACS0269 ΓòÉΓòÉΓòÉ

ACS0269-I TRANS005  File transfer was canceled because the workstation file
name was incorrect or was not found. Correct the file name, and then retry the
file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.28. ACS0270 ΓòÉΓòÉΓòÉ

ACS0270-I TRANS006  The file transfer was canceled because a required part of
the workstation file name or the host file name is missing. Specify the
complete file name, and then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.29. ACS0271 ΓòÉΓòÉΓòÉ

ACS0271-I TRANS022  The file transfer was canceled because the host session ID
ID(8) is not valid.  Correct the session ID, and then retry the file transfer.

where
ID(8)           = host session ID

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.4.30. ACS0272 ΓòÉΓòÉΓòÉ

ACS0272-I File transfer is being canceled.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5. ACS0281 through ACS0322 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.5.1. ACS0281 ΓòÉΓòÉΓòÉ

ACS0281-W The 3270 Terminal Emulator detected an unsupported keyboard type.
Verify that an IBM Personal Computer AT keyboard or IBM Enhanced keyboard is
being used.  If the problem persists, run hardware diagnostics to determine the
error.  Replace the keyboard if necessary.

Originator: 3270 Terminal Emulation


ΓòÉΓòÉΓòÉ 3.5.2. ACS0282 ΓòÉΓòÉΓòÉ

ACS0282-W The 3270/5250 emulation program could not find the critical file
name(12).  Restore the file from a backup copy to the Communications Manager
directory, or reinstall Communications Manager.

where
name(12)        = file name

Originator: 3270 Terminal Emulation


ΓòÉΓòÉΓòÉ 3.5.3. ACS0286 ΓòÉΓòÉΓòÉ

ACS0286-I TRANS108  The file transfer was canceled because the specified host
code page is not valid.  Correct the host code page, and then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.4. ACS0287 ΓòÉΓòÉΓòÉ

ACS0287-I TRANS109  The file transfer was canceled because the specified
workstation code page is either not valid or not found. Correct the workstation
code page, and then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.5. ACS0288 ΓòÉΓòÉΓòÉ

ACS0288-I TRANS110  The file transfer was canceled because the specified
emulation session is already being used by another file transfer or SRPI
application. Specify a different session and then retry the command, or wait
until the process using the session has been completed, and then retry the
command.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.6. ACS0294 ΓòÉΓòÉΓòÉ

ACS0294-E File transfer ended unexpectedly.  Check the error log for additional
information.  Retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.7. ACS0296 ΓòÉΓòÉΓòÉ

ACS0296-I TRANS111  The file transfer was canceled because the workstation file
could not be accessed.  Specify a different file name or directory. Then retry
the file transfer.

Originator: File Transfer

Explanation: Likely causes are:

o A RECEIVE operation was specified for a read-only workstation file or
  directory.

o A SEND operation was specified for a write-only workstation file or
  directory.


ΓòÉΓòÉΓòÉ 3.5.8. ACS0297 ΓòÉΓòÉΓòÉ

ACS0297-I TRANS112  The file transfer was canceled because the specified
workstation drive is locked.  Unlock the workstation disk or diskette drive, or
specify a different workstation file name or directory. Then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.9. ACS0298 ΓòÉΓòÉΓòÉ

ACS0298-I TRANS113  The file transfer was canceled because the workstation disk
or diskette is full.  Free space on the disk or diskette, or use one with more
available space.  Then retry the operation.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.10. ACS0299 ΓòÉΓòÉΓòÉ

ACS0299-I TRANS114  The workstation disk or diskette is not formatted correctly
for the specified drive.  Retry the file transfer with a properly formatted
disk or diskette for the specified drive.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.11. ACS0300 ΓòÉΓòÉΓòÉ

ACS0300-I TRANS115  The file transfer was canceled because the specified
directory contains the maximum number of files allowed. Reduce the number of
files in the specified directory, or specify a different directory. Then retry
the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.12. ACS0301 ΓòÉΓòÉΓòÉ

ACS0301-I TRANS116  The file transfer was canceled because no more workstation
files can be opened. End an active application, and then retry the file
transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.13. ACS0302 ΓòÉΓòÉΓòÉ

ACS0302-I TRANS117  The file transfer was canceled because the specified
workstation file is already in use. Wait until the file is available, and then
retry the file transfer, or specify a different workstation file name or
directory, and then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.14. ACS0303 ΓòÉΓòÉΓòÉ

ACS0303-I TRANS118  The file transfer was canceled because the file transfer
data cannot be received on a write-protected disk or diskette. Specify a
different workstation disk or diskette.  Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.15. ACS0304 ΓòÉΓòÉΓòÉ

ACS0304-I TRANS119  The file transfer was canceled because the workstation
diskette drive is not ready.  Ensure that the diskette is inserted correctly
and that the diskette drive door or latch is closed, or specify a different
workstation diskette drive.  Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.16. ACS0305 ΓòÉΓòÉΓòÉ

ACS0305-I TRANS120  The file transfer was canceled because the workstation
drive was specified incorrectly.  Specify the correct name for the workstation
disk or diskette drive. Then retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.5.17. ACS0306 ΓòÉΓòÉΓòÉ

ACS0306-I TRANS121  The file transfer was canceled because the workstation file
could not be accessed. Retry the file transfer with another workstation disk or
diskette.

Originator: File Transfer

Explanation: Likely causes are:

o The disk or diskette is unformatted or damaged.

o A required system resource is not available.

o A programming error occurred.


ΓòÉΓòÉΓòÉ 3.5.18. ACS0310 ΓòÉΓòÉΓòÉ

ACS0310-W The send or receive list has been changed or created but not saved
yet. Unless the list is saved, the changes will be lost.

Originator: File Transfer

User Response: Do one of the following:

o To save the list from this message box, select the Save push button. If a
  name for the list of files has not been specified, the Save as... window
  appears so a name for the list of files can be specified.

o If you do not want to save a newly created list, or changes made to an
  existing list, select Discard.

o Select Cancel to close this message box and return to the Send or Receive
  window.


ΓòÉΓòÉΓòÉ 3.5.19. ACS0311 ΓòÉΓòÉΓòÉ

ACS0311-E Another file with this file name already exists in the specified
directory.

Originator: File Transfer

User Response: Do one of the following:

o Select OK if you want to overwrite the existing file with this file.

o If you do not want to overwrite the existing file, select Cancel and give the
  new file a unique name. Then retry the operation.


ΓòÉΓòÉΓòÉ 3.5.20. ACS0312 ΓòÉΓòÉΓòÉ

ACS0312-W The specified file does not exist in the specified directory.

Originator: File Transfer

User Response: Correct the file name and retry the operation.


ΓòÉΓòÉΓòÉ 3.5.21. ACS0313 ΓòÉΓòÉΓòÉ

ACS0313-E The transfer type that is specified does not exist.

Originator: File Transfer

User Response: Specify an existing transfer type by typing one in the field or
selecting one from the drop-down list of available transfer types. Then retry
the operation.


ΓòÉΓòÉΓòÉ 3.5.22. ACS0314 ΓòÉΓòÉΓòÉ

ACS0314-E The code page specified is not valid.

Originator: File Transfer

User Response: Select a code page from the drop-down list.  Then retry the
operation.


ΓòÉΓòÉΓòÉ 3.5.23. ACS0315 ΓòÉΓòÉΓòÉ

ACS0315-E The transfer type specified already exists.

Originator: File Transfer

User Response: Specify a unique transfer type name.  Then retry the operation.


ΓòÉΓòÉΓòÉ 3.5.24. ACS0316 ΓòÉΓòÉΓòÉ

ACS0316-E The number entered exceeds the maximum value allowed.

Originator: File Transfer

User Response: Specify a valid number. The valid range is described on the
right side of the field.


ΓòÉΓòÉΓòÉ 3.5.25. ACS0317 ΓòÉΓòÉΓòÉ

ACS0317-E Drive name(1) is not ready.

where
name(1)         = drive name

Originator: File Transfer

User Response: Do one of the following:

o Make the drive ready, and select Retry.

o Select Cancel and specify another drive. Then retry the operation.


ΓòÉΓòÉΓòÉ 3.5.26. ACS0318 ΓòÉΓòÉΓòÉ

ACS0318-E The total length of the fully-qualified file name exceeds the maximum
length allowed.

Originator: File Transfer

Explanation: The file name is converted to the fully-qualified file name, which
consists of the drive, path, and file name.  When it is converted, the total
length of the file name will exceed the maximum length of 258 bytes.
Single-byte characters take 1 byte per character; double-byte characters take 2
bytes per character.

User Response:

o Do one of the following:

   - Move the file into a directory with a shorter path name.

   - Shorten the file name.

   - Then retry the operation.


ΓòÉΓòÉΓòÉ 3.5.27. ACS0319 ΓòÉΓòÉΓòÉ

ACS0319-E The specified source file name did not match any templates that are
currently defined.

Originator: File Transfer

User Response: Create a new template, or change an existing template so the
source file name matches it. Then retry the operation.


ΓòÉΓòÉΓòÉ 3.5.28. ACS0320 ΓòÉΓòÉΓòÉ

ACS0320-E Allocation units must be Default when the Quantity is 0 or is not
specified.

Originator: File Transfer

User Response: Change the Allocation unit to Default, or specify the Quantity
to a valid value other than 0.


ΓòÉΓòÉΓòÉ 3.5.29. ACS0321 ΓòÉΓòÉΓòÉ

ACS0321-W The requested window is already active.

Originator: File Transfer

Explanation: The requested file transfer window is already active in one of the
following situations:

o Only one Transfer Type Definition or Templates window can be active for each
  host type.

For example, the Transfer Type Definition window can run on an MVS session
window and a VM session window at the same time, but it cannot be run on two VM
session windows at the same time. The Transfer Type Definition or Templates
window can be activated from CMSETUP, when a different configuration file is in
use, even if it is already active in an emulator session.

o Only one Miscellaneous Send/Receive Settings window can be active for a given
  configuration.

For example, if you are using the Miscellaneous Send/Receive Settings window to
define a configuration from Communications Manager Setup, you must close that
window before you can open a Miscellaneous Send/Receive Settings window from a
3270 emulator session that uses the same configuration.

User Response: See the window list to find where the requested window is
already active. Use the active window to complete the operation.


ΓòÉΓòÉΓòÉ 3.5.30. ACS0322 ΓòÉΓòÉΓòÉ

ACS0322-E The file transfer profiles are locked by another session so they
cannot be loaded or saved.

Originator: File Transfer

Explanation: The file transfer profiles are profiles of the Communications
Manager configuration which contain the transfer type, the templates, and the
miscellaneous settings.

User Response: Do one of the following:

o If you can identify the session locking the profiles, end that session.

o Retry the operation. If the same message reappears, select Cancel to end the
  current job.


ΓòÉΓòÉΓòÉ 3.6. ACS0323 through ACS0401 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.6.1. ACS0323 ΓòÉΓòÉΓòÉ

ACS0323-E The specified file name is too long or contains a character that is
not valid.

Originator: File Transfer

User Response: Enter a correct file name.  Then retry the operation.


ΓòÉΓòÉΓòÉ 3.6.2. ACS0324 ΓòÉΓòÉΓòÉ

ACS0324-I The target file name exceeded the maximum length and was truncated.

Originator: File Transfer

User Response: To prevent this condition from recurring:

o If the action was started from the Test Template window, change the file name
  in the template.

o If the action was started from the Send Files to Host window or the Receive
  Files from Host window, select Edit and change the target file name.


ΓòÉΓòÉΓòÉ 3.6.3. ACS0325 ΓòÉΓòÉΓòÉ

ACS0325-I The file transfer is complete.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.6.4. ACS0326 ΓòÉΓòÉΓòÉ

ACS0326-E A file transfer configuration window is still active.  Close the
window before exiting the 3270 Emulation window.

Originator: Configuration Services - Emulators


ΓòÉΓòÉΓòÉ 3.6.5. ACS0327 ΓòÉΓòÉΓòÉ

ACS0327-W The print queue or print object was deleted.

Originator: Emulator

Explanation: An error occurred when the user failed to install a printer on
OS/2, or when the print queue or print object was deleted.

User Response: Choose one of the following:

o Install your printer.

o Define a print queue or print object in print manager.


ΓòÉΓòÉΓòÉ 3.6.6. ACS0328 ΓòÉΓòÉΓòÉ

ACS0328-E 3270 emulation cannot use a 3270 emulation credit card adapter.

Originator: Emulator (3270/5250 emulation)

Explanation: The 3270 emulation credit card adapter could not obtain an I/O
address, a shared memory segment (8 K bytes), or an interrupt request (IRQ).

User Response: Do the following:

o Remove adapters and associated software you no longer use, and reconfigure
  your workstation.

o If you change the system configuration but the problem remains, use the
  adapter diagnostics to test the hardware components of the adapter.

o For more information, see the installation and testing instructions for the
  credit card adapter.


ΓòÉΓòÉΓòÉ 3.6.7. ACS0329 ΓòÉΓòÉΓòÉ

ACS0329-E The transfer type that is specified does not exist.

Originator: File Transfer

User Response:

o Do one of the following:

   - Specify an existing transfer type by typing one in the field or selecting
     one from the drop-down list of available transfer types.

   - Create a new transfer type.  When the new transfer type is saved, it is
     added to the transfer type drop-down list.

o Then retry the operation.


ΓòÉΓòÉΓòÉ 3.6.8. ACS0330 ΓòÉΓòÉΓòÉ

ACS0330-W The change requested for a key in %1 state causes the same key to be
remapped in the other mode.

Originator: Keyboard Remap Utility

Explanation: Changing a key defined as a character to a function in either
Alphanumeric or Hiragana mode causes the same key in the opposite mode to be
given the same function.

User Response: Choose one of the following:

o Select OK to save the new key definition.

o Select Cancel to stop the remap operation.


ΓòÉΓòÉΓòÉ 3.6.9. ACS0331 ΓòÉΓòÉΓòÉ

ACS0331-W The change requested for a key in %1 state causes the same key to be
erased in the other mode.

Originator: Keyboard Remap Utility

Explanation: An erased key definition can be changed to a character value, the
change does not affect the key definition in the other mode. Changing a key
defined as a function to a character value in either Alphanumeric or Hiragana
modes causes the same key in the opposite mode to be erased.

User Response: Choose one of the following: - Select Cancel to stop the remap
operation. - Select OK to erase the key definition.


ΓòÉΓòÉΓòÉ 3.6.10. ACS0332 ΓòÉΓòÉΓòÉ

ACS0332-W The copy or move of an existing function to a key defined as a
character causes that key in the other mode to be remapped.

Originator: Keyboard Remap Utility

Explanation: Copying or moving a source key defined as a function to a target
character in either Alphanumeric or Hiragana modes causes the same target key
in the opposite mode to be given the same function.

User Response: Choose one of the following:

o Select Cancel to stop the remap operation.

o Select OK to remap the base and shift functions.


ΓòÉΓòÉΓòÉ 3.6.11. ACS0333 ΓòÉΓòÉΓòÉ

ACS0333-W The copy or move of an existing character to a key defined as a
function causes that key in the other mode to be erased.

Originator: Keyboard Remap Utility

Explanation: Copying or moving a key defined as a character to a function value
in either Alphanumeric or Hiragana modes causes the same key in the opposite
mode to be erased. An erased key definition can be changed to a character
value, the change does not affect the key definition in the other mode.

User Response: Choose one of the following: - Select Cancel to stop the remap
operation. - Select OK to erase the key definition of the other state.  If you
want to erase the definition and keep the other state, assign a character then
retry the remap operation.


ΓòÉΓòÉΓòÉ 3.6.12. ACS0334 ΓòÉΓòÉΓòÉ

ACS0334-W The swap of a key definition within one mode causes the key
definition in the other mode to be swapped.

Originator: Keyboard Remap Utility

Explanation: Swapping a key defined as a character with one defined as a
function when the character definition in the other mode is not defined causes
both modes to be swapped.

User Response: Choose one of the following:

o Select Cancel to stop the remap operation.

o Select OK to remap both key definitions.


ΓòÉΓòÉΓòÉ 3.6.13. ACS0335 ΓòÉΓòÉΓòÉ

ACS0335-W The key definition data cannot print because the paper size is not
valid.

Originator: Keyboard Remap Utility

Explanation: The print keyboard function allows the user to print the key
definition data. The configuration file name, profile name, and any comments
are printed at the top of each printout.

User Response: Correct the paper size in Presentation Manager and print the key
definition data, then retry the print operation.


ΓòÉΓòÉΓòÉ 3.6.14. ACS0336 ΓòÉΓòÉΓòÉ

ACS0336-I This key cannot be remapped because the key's function is reserved
based on the keyboard.

Originator: Keyboard Remap Utility

Explanation:

User Response:


ΓòÉΓòÉΓòÉ 3.6.15. ACS0337 ΓòÉΓòÉΓòÉ

ACS0337-E The maximum number of strings exceeded the limit.

Originator: Keyboard Remap Utility

Explanation: The update to the keyboard profile was rejected because the
maximum number of strings allowed was exceeded. The maximum number allowed is
64 strings per keyboard profile.

User Response: Erase any strings that are not needed, then retry the operation.


ΓòÉΓòÉΓòÉ 3.6.16. ACS0338 ΓòÉΓòÉΓòÉ

ACS0338-E The string added exceeds the maximum length allowed for a string.

Originator: Keyboard Remap Utility

Explanation: The update to the keyboard profile was rejected because the
maximum length allowed for a string was exceeded. The maximum number allowed
for each string is 1024 bytes. Each string may have a combination of a
single-byte and a double-byte character. A double-byte character requires two
bytes and the single-byte character requires two bytes.

User Response: Enter the string that does not exceed the limits, then retry the
operation.


ΓòÉΓòÉΓòÉ 3.6.17. ACS0339 ΓòÉΓòÉΓòÉ

ACS0339-E The Selected Keyboard Profile is not Valid for this Environment.

Originator: Keyboard Remap Utility

Explanation: This message is displayed when the user selects a keyboard profile
that is not valid.  The keyboard profile for countries using single-byte
character set (SBCS) cannot be used for countries using double-byte character
set (DBCS).

User Response: Select the keyboard profile that match your environment.


ΓòÉΓòÉΓòÉ 3.6.18. ACS0340 ΓòÉΓòÉΓòÉ

ACS0340-W The 3270 emulator on short session name ID(1) has received an
unexpected return code (RC) from the name(8) compression algorithm component.

where
ID(1)           = short session name ID
name(8)         = return code (RC) from name

Originator: Emulator (3270/5250 emulation)

Explanation: This condition occurs when the 3270 emulator was unable to
successfully compress or decompress the request/response unit (RU) data.  If
this error occurs while decompressing for the compressed Outbound RU data, the
Operator Information Area (OIA) on the display shows the specific PROG740.

User Response: Do the following: 1.  Use FFST/2 to access the system error log
and review the error log entry. 2.  Note the date, time, and problem ID from
the FFST/2 message log formatter.  To locate and review the associated error
log entries, use FFST/2 to access the system error log. Follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.


ΓòÉΓòÉΓòÉ 3.6.19. ACS0341 ΓòÉΓòÉΓòÉ

ACS0341-I The 3270 emulator on short session name ID(1) could not get
sufficient resources to use the Systems Network Architecture (SNA) data
compression.

where
ID(1)           = short session name ID

Originator: Emulator (3270/5250 emulation)

Explanation: This condition occurs when compression resources (maximum
compression level or tokens) specified at the local node are exceeded.  The
3270 emulation starts without SNA data compression.

User Response: To be able to use SNA data compression on your 3270 session, use
the Local Node Options panel of Communications Manager Setup or use the
DEFINE_LOCAL_CP verb in the node definitions file (NDF).  Either of these
allows you to set the necessary compression resources (maximum compression
level or tokens) at the local node. You must set Lempel-Ziv Algorithm (LZ9) as
the maximum compression level, with sufficient tokens for run length encoding
(RLE) compression and LZ9 decompression.


ΓòÉΓòÉΓòÉ 3.6.20. ACS0357 ΓòÉΓòÉΓòÉ

ACS0357-W This string cannot be properly separated into characters and
functions.  Check the string for errors starting at the cursor location.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.6.21. ACS0372 ΓòÉΓòÉΓòÉ

ACS0372-W The 3270 Terminal Emulator could not use the 3270 DFT device driver
as specified in the CONFIG.SYS file, or the DFTDD.SYS file is missing or
damaged.

Originator: 3270 Terminal Emulation

Explanation: The 3270 Terminal Emulator detected one of the following
conditions while attempting to open the 3270 DFT device driver:

o The device driver was not specified in the DEVICE= statement of the
  CONFIG.SYS file.

o The DFTDD.SYS file is missing or damaged.

o A system error caused the device driver to be unusable.

User Response:

o Ensure that the DEVICE= statement in the CONFIG.SYS file is correct:
  DEVICE=DFTDD.SYS.

o If the DFTDD.SYS file is missing or damaged, stop Communications Manager.

o Copy the file from a backup copy to a Communications Manager directory.

o Restart the system.


ΓòÉΓòÉΓòÉ 3.6.22. ACS0382 ΓòÉΓòÉΓòÉ

ACS0382-E The critical system file ACSACDI.DAT could not be found.  The
selected profile operation cannot be performed.

Originator: Configuration Services

User Response:

o Stop Communications Manager.

o Copy this file from a backup diskette and retry the operation.

o If you do not have a backup, reinstall and restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.6.23. ACS0385 ΓòÉΓòÉΓòÉ

ACS0385-E The CMVERIFY syntax file name(255) is not in the current DPATH.

where
name(255)       = CMVERIFY syntax file name

Originator: Configuration Services - Verify

Explanation: The CMVERIFY syntax file was not found.

User Response: Either:

o Change the DPATH variable in CONFIG.SYS to include the directory where the
  CMVERIFY syntax file resides, or

o Restore the CMVERIFY syntax file (possibly from a backup) into one of the
  directories listed in the DPATH variable.


ΓòÉΓòÉΓòÉ 3.6.24. ACS0395 ΓòÉΓòÉΓòÉ

ACS0395-W There is not enough memory to complete the dump of the ACDI data.
Free memory by ending any application that is not being used.  Then retry the
dump procedure.

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.6.25. ACS0396 ΓòÉΓòÉΓòÉ

ACS0396-E Configuration name(8) was not found or could not be read.  ACDI was
not started.

where
name(8)         = file name

Originator: ACDI API

Explanation: The ACDI configuration could not be opened and read because of one
of the following reasons:

o Too many files were open at the time the request was made.

o The configuration is damaged.

o The configuration has been erased.

User Response:

o Check to see if the configuration exists.  If necessary, restore the
  configuration using a backup copy, or create a new configuration. Then
  restart Communications Manager.

o If too many files are open, close some files, or increase the FILES=
  statement in the CONFIG.SYS file.  Then retry the operation.


ΓòÉΓòÉΓòÉ 3.6.26. ACS0397 ΓòÉΓòÉΓòÉ

ACS0397-E ACDI did not start because resources could not be allocated. Restart
ACDI.  If the problem persists, free memory by reducing the number of active
programs, and then restart ACDI.

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.6.27. ACS0398 ΓòÉΓòÉΓòÉ

ACS0398-I The asynchronous device driver is being installed.

Originator: Asynchronous Device Driver


ΓòÉΓòÉΓòÉ 3.6.28. ACS0399 ΓòÉΓòÉΓòÉ

ACS0399-I The asynchronous device driver for name(8) is installed.

where
name(8)         = port name

Originator: Asynchronous Device Driver


ΓòÉΓòÉΓòÉ 3.6.29. ACS0400 ΓòÉΓòÉΓòÉ

ACS0400-W The port name specified in the DEVICE= statement in the CONFIG.SYS
file for the asynchronous device driver is not valid.

Originator: ACDI API

User Response:

o If you are using an IBM AT or XT/286 system, specify either COM1 or COM2 as
  the port name in the DEVICE= statement in the CONFIG.SYS file.

o If you are using a PS/2, specify either COM1, COM2, or COM3 as the port name
  in the DEVICE= statement in the CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 3.6.30. ACS0401 ΓòÉΓòÉΓòÉ

ACS0401-I The asynchronous device driver for name(8) is not installed.

where
name(8)         = port name

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.7. ACS0402 through ACS0483 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.7.1. ACS0402 ΓòÉΓòÉΓòÉ

ACS0402-W The installed device driver is the wrong version for this system. The
specified device driver supports only the IBM Personal Computer AT and XT/286.

Originator: ACDI API

User Response: Ensure that the proper device driver is installed on the system.
The following is a list of valid device drivers and the systems they support:

o ASYNCDDA  -  IBM PC AT and other AT-type computers

o ASYNCDDB  -  PS/2 with Micro Channel or other Micro Channel-type computers

o ASYNCDDC  -  PS/2 with Micro Channel or Micro Channel computers that have a
  communications port with DMA capability

o ASYNCDDE  -  ACDI redirection over a LAN on all machines.

Check the CONFIG.SYS file for the correct device entry for the hardware:
DEVICE= ASYNCxxx.SYS.


ΓòÉΓòÉΓòÉ 3.7.2. ACS0403 ΓòÉΓòÉΓòÉ

ACS0403-W The installed device adapter is not supported.

Originator: ACDI API

User Response: Install a supported device adapter, or remove the DEVICE=
statement from the CONFIG.SYS file. The following is a list of supported device
adapters:

o IBM PC AT and PC XT/286

Serial/Parallel Adapter (asynchronous) P/N 6450215 Memory Expansion Adapter
(asynchronous) P/N 55X3679

o IBM Personal System/2

Dual Async Adapter/A Multiprotocol Adapter/A (SDLC, asynchronous) Note which
type of hardware adapter is installed on this workstation, and refer to the
Communications Manager documentation to see whether the adapter is supported.


ΓòÉΓòÉΓòÉ 3.7.3. ACS0404 ΓòÉΓòÉΓòÉ

ACS0404-W The interrupt level is already in use by another adapter.

Originator: ACDI API

Explanation: The asynchronous device driver was unable to install because the
needed interrupt level is already in use.  The communications ports require the
following interrupt levels:

o COM1 requires IRQ4

o COM2 requires IRQ3

o COM3 requires IRQ3.

User Response: Set the interrupt levels on the installed adapters to avoid a
conflict.


ΓòÉΓòÉΓòÉ 3.7.4. ACS0405 ΓòÉΓòÉΓòÉ

ACS0405-W The asynchronous device driver could not be installed because system
resources are not available for the device driver. Reduce the number of device
drivers loaded in the system and retry.

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.7.5. ACS0412 ΓòÉΓòÉΓòÉ

ACS0412-E Not enough system resources were available to start ACDI. Free memory
by ending other application programs that are not being used.  If the problem
persists, increase the value of the THREADS= statement in the CONFIG.SYS file.
Then restart the system.

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.7.6. ACS0413 ΓòÉΓòÉΓòÉ

ACS0413-W No more space is available for saving string characters.  Only 4096
characters are allowed.  Delete some characters from this or another key
definition.  Then, try the operation again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.7.7. ACS0415 ΓòÉΓòÉΓòÉ

ACS0415-I XMODEM file transfer is operating in CHECKSUM error detection mode.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.7.8. ACS0419 ΓòÉΓòÉΓòÉ

ACS0419-E The specified file name(40) is already being used by another program.
Specify a different file name, or cancel the program that is using the file.

where
name(40)        = file name

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.7.9. ACS0423 ΓòÉΓòÉΓòÉ

ACS0423-W The incoming call directory entry name name(16) in X.25 link profile
name(8) was not found in the Connection Manager Incoming Call Directory.

where
name(16)        = ICRT entry name
name(8)         = X.25 link name

Originator: Configuration Services - Verify

Explanation: Ignore this message if this configuration is being created for
another workstation with a different Connection Manager Incoming Call
Directory.

User Response:

o If the configuration is for this workstation, create the missing entry in the
  Connection Manager Incoming Call Directory.

o If the configuration is for another workstation with the same Connection
  Manager directory as this workstation, enter one of the existing entry names
  in the incoming call directory entry name field for the X.25 link profile.


ΓòÉΓòÉΓòÉ 3.7.10. ACS0424 ΓòÉΓòÉΓòÉ

ACS0424-W The device adapter is being used by another device driver or is not
installed on the system.

Originator: ACDI API

User Response: Check the CONFIG.SYS file to ensure that the proper device
driver is using the adapter.  Check the system to ensure that an adapter is
installed.


ΓòÉΓòÉΓòÉ 3.7.11. ACS0426 ΓòÉΓòÉΓòÉ

ACS0426-E There is not enough disk space available for dump file name(64). Free
space on the target drive, or use a different target drive.  Then retry the
dump operation.

where
name(64)        = dump file name

Originator: Problem Determination

Explanation: The dump cannot be completed.  Dump files typically are large and
cannot be stored on more than one disk or diskette.


ΓòÉΓòÉΓòÉ 3.7.12. ACS0427 ΓòÉΓòÉΓòÉ

ACS0427-W The adapter installed on this system is not compatible with the
asynchronous communications device driver installed on this system. Check the
CONFIG.SYS file to ensure that the correct device driver is specified for the
installed adapter, or install an adapter that is compatible with the specified
device driver.

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.7.13. ACS0428 ΓòÉΓòÉΓòÉ

ACS0428-W The num(4) port interrupt level is not set to the correct value.
Using the reference diskette, set the hardware interrupt levels to level 4 for
COM1 and level 3 for COM2 and COM3.

where
num(4)          = communications port number

Originator: ACDI API


ΓòÉΓòÉΓòÉ 3.7.14. ACS0433 ΓòÉΓòÉΓòÉ

ACS0433-W The function name will not fit in the field. Either delete some
characters in the current field or assign the function to another key.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.7.15. ACS0450 ΓòÉΓòÉΓòÉ

ACS0450-E Path pathname could not be accessed.

where
pathname        = path

Originator: Emulator (3270/5250 emulation)

Explanation: Access was denied for one of the following reasons:

o The specified path is a secured path. You do not have authority to access the
  folder.

o Your user ID is not in the system directory.

User Response: Do one of the following:

o Submit the request again using a different folder.

o Have the security officer give you authority to access the folders in the
  path specified.

o Add your user ID in the system directory.


ΓòÉΓòÉΓòÉ 3.7.16. ACS0451 ΓòÉΓòÉΓòÉ

ACS0451-E PC organizer cannot run on the version of DisplayWrite 5/2 being
used.  Version 1.1.2 or higher is needed.

Originator: Emulator (3270/5250 emulation)

User Response: Install DisplayWrite 5/2 Version 1.1.2 or higher.


ΓòÉΓòÉΓòÉ 3.7.17. ACS0452 ΓòÉΓòÉΓòÉ

ACS0452-E More than one DisplayWrite 5/2 (DW 5/2) editing session was
requested.  Only one editing session is allowed.

Originator: Emulator (3270/5250 emulation)

User Response: If you already cancelled a DW 5/2 editing request from the host,
close the DW 5/2 editing session associated with it.  Then retry the operation.

o If not, return to the editing session.  You cannot start a new editing
  session until the first editing session is closed.


ΓòÉΓòÉΓòÉ 3.7.18. ACS0453 ΓòÉΓòÉΓòÉ

ACS0453-E DisplayWrite 5/2 could not process an edit request.

Originator: Emulator (3270/5250 emulation)

User Response: Retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.


ΓòÉΓòÉΓòÉ 3.7.19. ACS0454 ΓòÉΓòÉΓòÉ

ACS0454-E PC organizer detected a system error.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.

o If the problem persists, follow your local network operating procedures.  If
  this does not resolve the problem, contact your service representative.

o Note the date, time, and problem ID from the FFST/2 message log formatter.
  To locate and review the associated error log entries, use FFST/2 to access
  the system error log.


ΓòÉΓòÉΓòÉ 3.7.20. ACS0455 ΓòÉΓòÉΓòÉ

ACS0455-E The specified editor, DisplayWrite 5/2, is not available from double
byte character set (DBCS) devices.  Change the editor of choice to
OfficeVision/400.

Originator: Emulator (3270/5250 emulation)


ΓòÉΓòÉΓòÉ 3.7.21. ACS0456 ΓòÉΓòÉΓòÉ

ACS0456-E PC organizer timed out while waiting for a response from the host.

Originator: Emulator (3270/5250 emulation)

User Response: Do one of the following:

o To retry the operation again, select Retry.

o To cancel the operation, select Cancel.


ΓòÉΓòÉΓòÉ 3.7.22. ACS0457 ΓòÉΓòÉΓòÉ

ACS0457-E Program name was not found.

where
name            = program name

Originator: Emulator (3270/5250 emulation)

User Response: Check that the program name was entered correctly.  If it was,
make sure the specified program is installed and retry the operation.


ΓòÉΓòÉΓòÉ 3.7.23. ACS0458 ΓòÉΓòÉΓòÉ

ACS0458-E PC organizer could not assign a system drive.

Originator: Emulator (3270/5250 emulation)

Explanation: PC organizer requires a shared folders system drive to be assigned
before using the word processing function.

User Response: Use the Shared Folders Assign command to explicitly assign a
system drive.


ΓòÉΓòÉΓòÉ 3.7.24. ACS0459 ΓòÉΓòÉΓòÉ

ACS0459-E The request to edit a document failed.

Originator: Emulator (3270/5250 emulation)

Explanation: The failure occurred for one of the following reasons:

o The file extension specified is either .RFT or .FFT; both are reserved.

o The fully-qualified file name is longer than 44 characters.

User Response: Correct the file name.


ΓòÉΓòÉΓòÉ 3.7.25. ACS0460 ΓòÉΓòÉΓòÉ

ACS0460-E The editor could not interpret the request it received from PC
organizer.

Originator: Emulator (3270/5250 emulation)

User Response: End the PC organizer session.  Restart it and retry the
operation. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.


ΓòÉΓòÉΓòÉ 3.7.26. ACS0461 ΓòÉΓòÉΓòÉ

ACS0461-E DisplayWrite 5/2 (DW 5/2) was not loaded.

Originator: Emulator (3270/5250 emulation)

Explanation: DW 5/2 was not loaded correctly with the information provided in
the editor of choice fields.

User Response: Correct the editor of choice fields to reflect the correct
location of DW 5/2 and the appropriate startup sequence.


ΓòÉΓòÉΓòÉ 3.7.27. ACS0480 ΓòÉΓòÉΓòÉ

ACS0480-E A local system error occurred while starting word processing (WP)
support for this 5250 session.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.

o If the problem persists, follow your local network operating procedures.  If
  this does not resolve the problem, contact your service representative.

o Note the date, time, and problem ID from the FFST/2 message log formatter.
  To locate and review the associated error log entries, use FFST/2 to access
  the system error log.


ΓòÉΓòÉΓòÉ 3.7.28. ACS0481 ΓòÉΓòÉΓòÉ

ACS0481-E 5250 emulation received a command from the host.  The command is
either unrecognized, unsupported, or not valid in the current state.

Originator: Emulator (3270/5250 emulation)

User Response: Do the following:

o Restart the emulator and retry the operation.

o If the problem persists, restart your workstation.

o If the problem still persists, follow your local network operating
  procedures.  If this does not resolve the problem, contact your service
  representative.


ΓòÉΓòÉΓòÉ 3.7.29. ACS0482 ΓòÉΓòÉΓòÉ

ACS0482-E 5250 emulation received a word processing (WP) command from the host.
One or more of the command parameters are either unrecognized, unsupported, or
not valid in the current state.

Originator: Emulator (3270/5250 emulation)

User Response: Do the following:

o Restart the emulator and retry the operation.

o If the problem persists, restart your workstation.

o If the problem still persists, follow your local network operating
  procedures.  If this does not resolve the problem, contact your service
  representative.


ΓòÉΓòÉΓòÉ 3.7.30. ACS0483 ΓòÉΓòÉΓòÉ

ACS0483-I Text is being pasted over the right boundary.  Some of the marked
text will be lost and existing text will be realigned unless the operation is
cancelled.

Originator: Emulator (3270/5250 emulation)

User Response: Do one of the following:

o To end this paste operation, select Cancel.  Move the clipboard text so it
  does not go over the right boundary, and retry.

o To continue this paste operation, select OK to paste the clipboard text
  regardless of the realignment.


ΓòÉΓòÉΓòÉ 3.8. ACS0490 through ACS0544 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.8.1. ACS0490 ΓòÉΓòÉΓòÉ

ACS0490-E A local system error occurred while 5250 emulation was initializing
the FMA support function.

Originator: Emulator (3270/5250 emulation)

Explanation: 5250 emulation detected an error when it was initializing the
resources for the FMA support function or it was getting information from the
FMA support device driver.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred. If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.8.2. ACS0491 ΓòÉΓòÉΓòÉ

ACS0491-E A local system error occurred while 5250 emulation was processing the
request for the FMA support function.

Originator: Emulator (3270/5250 emulation)

Explanation: 5250 emulation detected an error when it was processing the
request for the FMA support function. The data transfer between AS/400 and PC
resulted in a failure.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred. If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.8.3. ACS0492 ΓòÉΓòÉΓòÉ

ACS0492-E A local system error occurred while 3270/5250 emulation was
processing the panel resources.

Originator: Emulator (3270/5250 emulation)

Explanation: 3270/5250 emulation detected an error when it was loading or
processing the panel resources to display the panels. The files REDJ2.PDL,
REDJ2.PML and REDJ2.HLP may not exist in the \CMLIB sub-directory or may be
damaged.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred. If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.8.4. ACS0493 ΓòÉΓòÉΓòÉ

ACS0493-W The 3270/5250 emulation program could not find the critical file
name(12).

where
name(12)        = system critical file name

Originator: Emulator (3270/5250 emulation)

Explanation: An error occurred when the 3270/5250 emulation program is trying
to open the specified critical file.

User Response: Reinstall Communications Manager.  Type CMSETUP at the OS/2
command prompt for the source drive containing the Communications Manager
product files.  If you are installing from diskettes, be sure that
Communications Manager diskette #1 is inserted in the source drive.


ΓòÉΓòÉΓòÉ 3.8.5. ACS0494 ΓòÉΓòÉΓòÉ

ACS0494-E 3270 emulation could not use the 3270 coaxial (DFT) device driver as
specified in the CONFIG.SYS file, or DFTDD.SYS file is missing or damaged.
Check the message log and the error log for additional information.

Originator: Emulator (3270/5250 emulation)

Explanation: 3270 emulation could not use the 3270 Coaxial(DFT) device driver
as specified in the CONFIG.SYS file, or DFTDD.SYS file is missing or damaged.
In case of using a 3270 credit card, DFTDD.SYS, Card Service, or Socket Service
is missing or damaged.

User Response: Check the 3270 emulation adapter is installed in a system, and
verify DFTDD.SYS in the CONFIG.SYS file is set properly. In case of using a
3270 credit card, check the 3270 credit card is plugged in a socket correctly,
and verify DFTDD.SYS, Card Service, and Socket Service in the CONFIG.SYS are
set properly.


ΓòÉΓòÉΓòÉ 3.8.6. ACS0497 ΓòÉΓòÉΓòÉ

ACS0497-W The function that cannot be combined with functions or strings is
contained in the key definition. Change the cursored state of the key
definition and try the operation again.

Originator: Keyboard Remap Utility

Explanation: You should not include the Scroll Lock, Num Lock, or Caps Lock as
keystrokes in strings used to define key actions. You should not include key
states assigned to window operations, such as Move Window and Size Window, in
strings. Including these key states in strings doesn't support.

User Response: Do not use a function key with a string, or change the selected
key state and try the operation again.


ΓòÉΓòÉΓòÉ 3.8.7. ACS0498 ΓòÉΓòÉΓòÉ

ACS0498-E The file name(8) is not a valid file transfer list.  Select another
list file.

where
name(8)         = name of file transfer list

Originator: File Transfer

User Response: Select an existing file transfer list.


ΓòÉΓòÉΓòÉ 3.8.8. ACS0499 ΓòÉΓòÉΓòÉ

ACS0499-Q The current configuration file is locked. You cannot change the
configuration file. Do you want to continue?

Originator: Converged Emulator

User Response: Do one of the following:

o Select Yes to continue this operation.

o Select No to stop this operation.


ΓòÉΓòÉΓòÉ 3.8.9. ACS0500 ΓòÉΓòÉΓòÉ

ACS0500-W Compression tokens may have been lost because of an OS/2 system
error.  If so, they cannot be recovered.

Originator: SNA Session Compression

Explanation: The number of configured compression tokens may have been
corrupted due to an error which occurred during one of the following
situations:

o While getting tokens at the start of a session

o While freeing tokens at the end of a session

User Response: To see how many tokens are still available for compression,
follow these steps:

o Select Subsystem Management in the Communications Manager Folder.

o Select SNA Subsystem.

o Select Display Active Configuration.

o Select Display from the menu bar.

o Select APPN from the pull-down menu.

o Select Node from the pull-down menu.

The number of tokens available for compression appears in the window. If there
is a sufficient number of tokens for the remaining sessions to be started with
compression, continue processing. Otherwise, restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.8.10. ACS0501 ΓòÉΓòÉΓòÉ

ACS0501-W The amount of memory required for the Systems Network Architecture
(SNA) session level compression requested cannot be allocated. Because
sufficient resources were not available, the session started without
compression.

Originator: SNA Session Compression


ΓòÉΓòÉΓòÉ 3.8.11. ACS0502 ΓòÉΓòÉΓòÉ

ACS0502-I There is not enough memory available to support compression for LU
char(17).  The session started without compression.

where
char(17)        = LU NAME

Originator: LU 6.2

User Response: If the session must have compression active, free memory by
stopping unused applications.  After the applications have stopped, terminate
the session and start it again.


ΓòÉΓòÉΓòÉ 3.8.12. ACS0503 ΓòÉΓòÉΓòÉ

ACS0503-I The session that requested the char1(4) and vchar2(4) started with
char3(4) and char4(4) compression because of insufficient tokens or because the
node compression level is too low.

where
char1(4)        = requested plu to slu
vchar2(4)       = requested slu to plu
char3(4)        = actual plu to slu
char4(4)        = actual slu to plu

Originator: LU 6.2


ΓòÉΓòÉΓòÉ 3.8.13. ACS0504 ΓòÉΓòÉΓòÉ

ACS0504-E The partner LU requested (RLE) and LZ9 compression in series. This
option is not supported by Communications Manager. The session ended.

Originator: LU 6.2

Explanation: The session cannot be started because Communications Manager does
not support this option.

User Response: Contact your service representative for more information.


ΓòÉΓòÉΓòÉ 3.8.14. ACS0505 ΓòÉΓòÉΓòÉ

ACS0505-E A compression protocol error occurred while trying to establish a
session with LU char(17). The session ended.

where
char(17)        = LU name

Originator: LU 6.2

Explanation: A higher level of compression has been requested on the BIND
response than is defined on the BIND request.

User Response: Contact your service representative for more information.


ΓòÉΓòÉΓòÉ 3.8.15. ACS0506 ΓòÉΓòÉΓòÉ

ACS0506-I An OS/2 system error occurred while trying to free compression
resources for LU char(17).  Session setup continues.

where
char(17)        = lu name

Originator: LU 6.2


ΓòÉΓòÉΓòÉ 3.8.16. ACS0507 ΓòÉΓòÉΓòÉ

ACS0507-I An error occurred while trying to allocate compression resources for
a session being started by LU char(17).  The session cannot be started.

where
char(17)        = LU name

Originator: LU 6.2

Explanation: A lower level of compression has been requested on the BIND
response than is defined on the BIND request.  The error occurred when trying
to exchange compression resources.

User Response: Stop Communications Manager (CM) and all CM applications.  Then
restart CM.  If the problem persists, contact your service representative for
more information.


ΓòÉΓòÉΓòÉ 3.8.17. ACS0508 ΓòÉΓòÉΓòÉ

ACS0508-I An OS/2 system error occurred while attempting to free compression
resources for LU char(17) while the session ended.

where
char(17)        = LU NAME

Originator: LU 6.2


ΓòÉΓòÉΓòÉ 3.8.18. ACS0509 ΓòÉΓòÉΓòÉ

ACS0509-E An internal processing error has occurred while compressing data. All
subsequent data is sent without compression.

Originator: LU 6.2

User Response: Contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.19. ACS0510 ΓòÉΓòÉΓòÉ

ACS0510-E A compressed request or response unit (RU) has been received on a
session that started without compression. Because compression is not active on
this session, the session ended.

Originator: LU 6.2

Explanation: Compressed data cannot be decompressed if it is received on a
session that started without compression.

User Response: Follow your local network operating procedure.  If this does not
resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.20. ACS0511 ΓòÉΓòÉΓòÉ

ACS0511-E A protocol error has occurred on a session using compression. The
session ended. A reset decompression control sequence was expected. Because it
was not received, the compressor and decompressor are not synchronized.

Originator: LU 6.2

User Response: Follow your local network operating procedure.  If this does not
resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.21. ACS0512 ΓòÉΓòÉΓòÉ

ACS0512-E A protocol error has occurred on a session using compression. The
session ended. A decompression control sequence that is not valid has been
received.  Because of this, the compressor and decompressor are not
synchronized.

Originator: LU 6.2

User Response: Follow you local network operating procedure.  If this does not
resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.22. ACS0513 ΓòÉΓòÉΓòÉ

ACS0513-E An error occurred while trying to decompress data.  The session
ended.  The length of a decompressed request or response unit (RU) did not
match the length given in the compression header.

Originator: LU 6.2

User Response: Follow you local network operating procedure.  If this does not
resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.23. ACS0514 ΓòÉΓòÉΓòÉ

ACS0514-E A protocol error has occurred on a session using compression. The
session ended.  A compression header that was received shows that the
compression algorithm used to compress the request or response unit (RU) is not
valid. The compression algorithm was not negotiated by the two LUs during
session activation.

Originator: LU 6.2

User Response: Follow your local network operating procedures.  If this does
not resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.24. ACS0515 ΓòÉΓòÉΓòÉ

ACS0515-E The partner LU sent a compressed RU which when decompressed exceeded
the maximum receive RU size.

Originator: LU 6.2

User Response: Follow your local network operating procedure.  If this does not
resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.25. ACS0516 ΓòÉΓòÉΓòÉ

ACS0516-E An internal processing error has occurred during decompression. The
session ended.

Originator: LU 6.2

User Response: Contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.26. ACS0517 ΓòÉΓòÉΓòÉ

ACS0517-E An error occurred while compressing data. All subsequent data is sent
without compression.

Originator: SNA Session Compression

User Response: End the current session and then restart it.


ΓòÉΓòÉΓòÉ 3.8.27. ACS0518 ΓòÉΓòÉΓòÉ

ACS0518-E An error occurred on a session using compression. The session ended.

Originator: LU 6.2

User Response: Contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.28. ACS0519 ΓòÉΓòÉΓòÉ

ACS0519-E An error occurred while decompressing RLE data.  The session ended.

Originator: LU 6.2

Explanation: RLE control information that is not valid has been encountered
while decompressing data.

User Response: Follow you local network operating procedure.  If that does not
relsove the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.29. ACS0520 ΓòÉΓòÉΓòÉ

ACS0520-E Incorrect compression indicators have been received in the BIND. The
session is started without compression.

Originator: LU 6.2

Explanation: A BIND was received with incorrect compression indicators in bits
6 and 7 of byte 25.

User Response: If compression is required, stop the session, then restart. If
the problem persists, follow your local network operating procedures.  If this
does not resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.8.30. ACS0544 ΓòÉΓòÉΓòÉ

ACS0544-W Because the number of links created is greater than the maximum
number of links defined, all links will not be started.

Originator: Configuration Services - Verify

User Response: Do one of the following:

o Delete the number of created link(s) so that the number of links created is
  equivalent to the maximum number of link stations defined.

o Set the number of maximum link stations to be equivalent to the number of
  links created.


ΓòÉΓòÉΓòÉ 3.9. ACS0554 through ACS0661 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.9.1. ACS0554 ΓòÉΓòÉΓòÉ

ACS0554-E The diskette drive d: is not ready.  Make the drive ready and retry
the operation.

where
d:              = drive name

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.9.2. ACS0555 ΓòÉΓòÉΓòÉ

ACS0555-E The diskette drive is not ready. Check the drive and select Retry
when the drive is ready.

Originator: Configuration Services - Advanced

Explanation: One of the following situations might have occurred:

o The drive is empty.

o The drive door is open.

o The drive is in use.

User Response: Do one of the following. Then retry the operation:

o Insert the diskette in the drive.

o Close the drive door.

o Wait until the drive is available.


ΓòÉΓòÉΓòÉ 3.9.3. ACS0575 ΓòÉΓòÉΓòÉ

ACS0575-I Configuration file name(8) has been upgraded.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.9.4. ACS0581 ΓòÉΓòÉΓòÉ

ACS0581-E The CODEPAGE= statement in CONFIG.SYS specifies a primary code page
that is different from the Communications Manager code page, name(4).

where
name(4)         = primary code page

Originator: Communications Manager Kernel

Explanation: Some characters may not be displayed correctly on Communications
Manager windows.

User Response: Set the primary code page in the CODEPAGE= statement in the
CONFIG.SYS file to the Communications Manager-supported code page.


ΓòÉΓòÉΓòÉ 3.9.5. ACS0584 ΓòÉΓòÉΓòÉ

ACS0584-I TRANS027 The file transfer was canceled because the maximum time-out
value was reached.  Retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.9.6. ACS0606 ΓòÉΓòÉΓòÉ

ACS0606-E The X.25 physical link name(8) could not be disconnected.

where
name(8)         = X.25 physical link name

Originator: Subsystem Management

Explanation: There was a problem with the X.25 subsystem that prevented the
physical link from being disconnected.

User Response:

o Refresh the window and check the status of the link.

o Message ACS3356 is logged with this message.  Check the system error log for
  possible related error log entries.

o Check the FFST/2 message log for possible related messages.


ΓòÉΓòÉΓòÉ 3.9.7. ACS0608 ΓòÉΓòÉΓòÉ

ACS0608-W An unexpected return code was received by the local 5250 emulator
from the underlying SNA support.

Originator: 5250 Work Station Feature

User Response: Ensure that all physical connections are secure, and that the
host is operational.  Review the local FFST/2 message and error logs for
related entries.  Review the host problem determination logs for detailed
information concerning this failure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o Locate the Additional Data section of the associated error log entry.  Locate
  the APPC verb issued, primary and secondary return codes, and sense data.
  APPC verb and return code descriptions can be found in the APPC Programming
  Reference.  Sense data descriptions are available in the Problem
  Determination Guide.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code (in byte-reversed format).

   - 02/02/ Reserved

   - 04/02/ Location identifier

   - 06/02/ Reserved

   - 08/02/ APPC verb operation code.

   - 10/02/ Primary return code.

   - 12/04/ Secondary return code.

   - 16/04/ Sense data, if necessary.


ΓòÉΓòÉΓòÉ 3.9.8. ACS0609 ΓòÉΓòÉΓòÉ

ACS0609-E The session limits could not be changed because a field contains an
incorrect value.

Originator: Subsystem Management

Explanation:

o The value in Number of sessions for this mode must be greater than or equal
  to the value in Minimum number of contention winners source.

o The value in Minimum number of contention winners source must be greater than
  or equal to the value in Number of automatically activated sessions.

User Response: Identify and correct the entries that are in error.


ΓòÉΓòÉΓòÉ 3.9.9. ACS0611 ΓòÉΓòÉΓòÉ

ACS0611-E The device driver installed is not supported for this system. Install
the proper device driver for this type of system.

Originator: Asynchronous Device Driver

User Response: The following is a list of valid device drivers and the systems
they support:

o ASYNCDDA  -  IBM PC AT and other AT-type computers

o ASYNCDDB  -  PS/2 with Micro Channel or other Micro Channel-type computers

o ASYNCDDC  -  PS/2 with Micro Channel or Micro Channel computers that have a
  communications port with DMA capability

o ASYNCDDE  -  ACDI redirection over a LAN on all machines.

Check the CONFIG.SYS file for the correct device entry for the hardware:
DEVICE= ASYNCxxx.SYS.


ΓòÉΓòÉΓòÉ 3.9.10. ACS0612 ΓòÉΓòÉΓòÉ

ACS0612-I The high-speed asynchronous device driver is being installed.

Originator: Asynchronous Device Driver


ΓòÉΓòÉΓòÉ 3.9.11. ACS0613 ΓòÉΓòÉΓòÉ

ACS0613-I The asynchronous device driver is installed for name(8).

where
name(8)         = port name

Originator: Asynchronous Device Driver


ΓòÉΓòÉΓòÉ 3.9.12. ACS0614 ΓòÉΓòÉΓòÉ

ACS0614-E The asynchronous device driver for name(8) is not installed.

where
name(8)         = port name

Originator: Asynchronous Device Driver

User Response: Check subsequent messages for specific error conditions that
have occurred.


ΓòÉΓòÉΓòÉ 3.9.13. ACS0615 ΓòÉΓòÉΓòÉ

ACS0615-E The interrupt level is being used by another adapter.

Originator: Asynchronous Device Driver

User Response: Select a different interrupt level that does not conflict with
the other adapters installed on this system.


ΓòÉΓòÉΓòÉ 3.9.14. ACS0616 ΓòÉΓòÉΓòÉ

ACS0616-E The device adapter is being used by another device driver or is not
installed.

Originator: Asynchronous Device Driver

User Response: Check the CONFIG.SYS file to ensure that it does not contain
duplicate DEVICE= statements.  If the adapter is not installed, either install
an adapter, or remove the DEVICE= statement from the CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 3.9.15. ACS0617 ΓòÉΓòÉΓòÉ

ACS0617-W The clipboard is not available when the keyboard is locked. Unlock
the keyboard before using the clipboard.

Originator: Converged Emulator

Explanation: Clipboard functions are not available when the keyboard is locked.

User Response: Wait until the host application has unlocked the keyboard before
using the clipboard functions.


ΓòÉΓòÉΓòÉ 3.9.16. ACS0618 ΓòÉΓòÉΓòÉ

ACS0618-W You are trying to paste text that is different than the existing text
into a protected field at the same location. The text in the protected field
will not be changed.

Originator: Converged Emulator

Explanation: You have attempted to paste a field of protected text over another
field of protected text, and the two protected fields are not identical.

User Response: Choose one of the following methods to complete the paste
operation:

o Select Cancel to stop the operation.

   Make sure that protected fields in the clipboard text and protected fields
   in the pasted text are identical.

   Retry the operation.

o Select OK to paste only the unprotected fields into the marked area.  The
  differences in the protected fields will be ignored.


ΓòÉΓòÉΓòÉ 3.9.17. ACS0619 ΓòÉΓòÉΓòÉ

ACS0619-W The session limit negotiation failed on partner LU name(17), mode
name(8).  The Change Number of Sessions (CNOS) return code is rc(12).

where
name(17)        = fully qualified PLU name
name(8)         = mode name
rc(12)          = CNOS primary and secondary return codes

Originator: SNA Communications Services (APPC)

Explanation: One of the following conditions caused the session limit
negotiation to fail:

o Your partner changed the session limit.

o Your partner is not configured for parallel sessions.

o The communications line or the partner you are trying to communicate with is
  not active.

User Response: Take the action indicated by the CNOS return code you received:

o 0002-00000151 - No action is required because your partner has already raised
  the session limits.

o 0003-00000004 and 0003-00000005 - Make sure that both the communications line
  and your partner are active.  Then make sure that the partner LU destination
  address is correct in your configuration file.  Your partner LU profile
  should also be configured for parallel sessions.  Then stop and restart APPC
  or activate an APPC session for the specified mode name.

o 0018-00000156 - No action is required on your part.  Your partner set the
  Maximum Negotiable Session Limit to 0.  Your partner should specify a higher
  session limit.

o 0018-00000157 - Make sure that both partners are configured with appropriate
  LU names and mode names.  Then stop and restart APPC, and restart your
  transaction program (TP).

o 0017-00000000 - APPC is currently processing a CNOS verb issued by a local
  LU.  Retry the CNOS verb after a short delay.


ΓòÉΓòÉΓòÉ 3.9.18. ACS0622 ΓòÉΓòÉΓòÉ

ACS0622-E A 5250 emulator-internal error occurred.

Originator: 5250 Work Station Feature

User Response: Review the FFST/2 message and error logs for related entries.
Follow any recommended actions.  Ensure the active configuration file is
verified.  Restart your computer and retry the operation you were attempting
when the problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code

   - 02/02/ Reserved

   - 04/02/ Location identifier

   - 06/02/ Reserved


ΓòÉΓòÉΓòÉ 3.9.19. ACS0630 ΓòÉΓòÉΓòÉ

ACS0630-I APPC did not find any configured logical links or active virtual
circuits in the system.

Originator: Subsystem Management


ΓòÉΓòÉΓòÉ 3.9.20. ACS0647 ΓòÉΓòÉΓòÉ

ACS0647-W The AS/400 virtual device name(10) is already being used by another
job on the host system.  Session ID(1) did not start.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response:

o Change the 5250 Terminal Emulator session profile to use a different
  workstation ID.  The virtual device name is specified in your terminal or
  printer profile as the workstation ID.

o If your session is currently blank, choose a unique ID.  Try to restart the
  session.


ΓòÉΓòÉΓòÉ 3.9.21. ACS0648 ΓòÉΓòÉΓòÉ

ACS0648-W The AS/400 virtual device name(10) is not configured correctly for
the 5250 Terminal Emulator or the device already exists on the host system, but
it is not connected to a virtual controller.  Session ID(1) did not start.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response:

o Change the 5250 Terminal Emulator session profile to use a different
  workstation ID.  The virtual device name is specified in your terminal or
  printer profile as the workstation ID.

o If the ID for your session is currently blank, choose a unique ID. Then try
  to restart the session.


ΓòÉΓòÉΓòÉ 3.9.22. ACS0649 ΓòÉΓòÉΓòÉ

ACS0649-I The high speed asynchronous device driver was installed for name(4).

where
name(4)         = ACDI

Originator: Asynchronous Device Driver


ΓòÉΓòÉΓòÉ 3.9.23. ACS0650 ΓòÉΓòÉΓòÉ

ACS0650-I The high speed asynchronous device driver was not installed for
name(4).

where
name(4)         = ACDI

Originator: Asynchronous Device Driver


ΓòÉΓòÉΓòÉ 3.9.24. ACS0652 ΓòÉΓòÉΓòÉ

ACS0652-W name(10) is not recognized as a virtual workstation controller on the
host system.  Session ID(1) did not start.

where
name(10)        = AS/400 virtual controller name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response:

o Ensure that the appropriate virtual controller exists on the host system and
  that it is activated.

o Check the host system for messages and logs that will help identify the cause
  and recovery action.


ΓòÉΓòÉΓòÉ 3.9.25. ACS0653 ΓòÉΓòÉΓòÉ

ACS0653-W Local 5250 emulator could not initialize a session.

Originator: 5250 Work Station Feature

User Response: Review the host problem determination logs for detailed
information concerning this failure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code

   - 02/02/ Reserved

   - 04/02/ Location identifier

   - 06/02/ Reserved


ΓòÉΓòÉΓòÉ 3.9.26. ACS0655 ΓòÉΓòÉΓòÉ

ACS0655-W The AS/400 virtual device name(10) is not authorized to use the
workstation ID specified in your terminal or printer session profile. Session
ID(1) did not start.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response: Contact your system administrator to get authorization
information.


ΓòÉΓòÉΓòÉ 3.9.27. ACS0656 ΓòÉΓòÉΓòÉ

ACS0656-W A host system operator canceled the AS/400 system job that was
starting the 5250 Terminal Emulator.  Session ID(1) at partner LU alias name
name(8) was canceled.

where
ID(1)           = short session ID
name(8)         = AS/400 system name

Originator: 5250 Work Station Feature

User Response: Contact the system operator to find out why the job was
canceled.  Restart the 5250 Terminal Emulator after the problem has been
resolved.


ΓòÉΓòÉΓòÉ 3.9.28. ACS0659 ΓòÉΓòÉΓòÉ

ACS0659-W The AS/400 message queue name(10) specified for printer operational
messages could not be found on the host system where your session ID(1) was
attaching.  Session ID(1) did not start.

where
name(10)        = AS/400 message queue name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response:

o Correct the message queue name.

o Contact your system administrator.


ΓòÉΓòÉΓòÉ 3.9.29. ACS0660 ΓòÉΓòÉΓòÉ

ACS0660-W An AS/400 virtual workstation controller is not available at partner
LU alias name name(10).  Session ID(1) did not start.  Retry the operation.

where
name(10)        = AS/400 virtual controller name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The host system does not have a virtual workstation controller
available for your 5250 Terminal Emulator session.


ΓòÉΓòÉΓòÉ 3.9.30. ACS0661 ΓòÉΓòÉΓòÉ

ACS0661-W The AS/400 device name(10) could not be created.  Session ID(1) did
not start.  Retry the operation.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The host system was unable to create the virtual device while
starting the 5250 Terminal Emulator session.


ΓòÉΓòÉΓòÉ 3.10. ACS0662 through ACS0784 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.10.1. ACS0662 ΓòÉΓòÉΓòÉ

ACS0662-E An AS/400 virtual device name(10) could not be changed.  Session
ID(1) did not start.  Retry the operation.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: Converged Emulator

Explanation: The AS/400 was not able to change the virtual device to match the
device description.

User Response: Check the host system for related messages and logs that will
help identify the cause and recovery actions.


ΓòÉΓòÉΓòÉ 3.10.2. ACS0663 ΓòÉΓòÉΓòÉ

ACS0663-W The AS/400 virtual device name(10) could not be activated.  Session
ID(1) did not start.  Retry the operation.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The host system could not activate the virtual device for the 5250
Terminal Emulator after creating or changing it.


ΓòÉΓòÉΓòÉ 3.10.3. ACS0664 ΓòÉΓòÉΓòÉ

ACS0664-W Local 5250 emulator could not initialize a session.

Originator: 5250 Work Station Feature

Explanation: The host was unable to activate a virtual device as requested by
the local 5250 emulator.

User Response: Review the host problem determination logs for detailed
information concerning this failure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code

   - 02/02/ Reserved

   - 04/02/ Location identifier

   - 06/02/ Reserved


ΓòÉΓòÉΓòÉ 3.10.4. ACS0666 ΓòÉΓòÉΓòÉ

ACS0666-W The AS/400 system session is not configured correctly. Session ID(1)
did not start.

where
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The AS/400 system does not recognize the session data passed by
the 5250 Terminal Emulator.

User Response: Do one of the following:

o Change the host type to AS/400 in the 5250 Terminal Emulator session profile.

o Change the partner LU alias for the session to correspond to a System/36.

o Check the profile configuration for your APPC partner logical unit.

Retry the operation.


ΓòÉΓòÉΓòÉ 3.10.5. ACS0667 ΓòÉΓòÉΓòÉ

ACS0667-W The System/36 session is not configured correctly. Session ID(1) did
not start.

where
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The System/36 does not recognize the session data passed by the
5250 Terminal Emulator.

User Response: Do one of the following:

o Change the host type to System/36 in the 5250 Terminal Emulator session
  profile.

o Change the partner LU alias for the session to correspond to an AS/400
  system.

o Check the profile configuration for your APPC partner logical unit.

Retry the operation.


ΓòÉΓòÉΓòÉ 3.10.6. ACS0669 ΓòÉΓòÉΓòÉ

ACS0669-W The user ID or password for partner LU alias name name(8) is not
valid.  Session ID(1) did not start.

where
name(8)         = partner LU alias name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: Before you can communicate with the host, the user ID and password
must be defined on the host system or conversation security must be turned off
at the host system.

User Response: Start the 5250 Terminal Emulator session with a different user
ID and password or define the current user ID and password on the host system.
If you are trying to connect to a System/36 and you are getting a sense code of
080F6051, ensure that you have the LOCATION PROFILE set up to accept the
sign-on from a remote location.


ΓòÉΓòÉΓòÉ 3.10.7. ACS0670 ΓòÉΓòÉΓòÉ

ACS0670-W The partner LU name is not correct, or the LU is not active. Session
ID(1) did not start.

where
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The session profile specifies the name of an AS/400 system or
System/36 that cannot be contacted.

User Response: Check to see if the APPC partner LU alias (name) of the host
system is specified correctly in the 5250 Terminal Emulator session
assignments.


ΓòÉΓòÉΓòÉ 3.10.8. ACS0671 ΓòÉΓòÉΓòÉ

ACS0671-I TRANS125  The file transfer was canceled because the specified file
transfer is to a logical printer session, which is not a supported session
type.  Specify a different terminal session and retry the file transfer.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.10.9. ACS0674 ΓòÉΓòÉΓòÉ

ACS0674-W The outgoing call directory entry name name(16) in X.25 link profile
name(8) was not found in the Connection Manager Outgoing Call Directory.

where
name(16)        = OCDT entry name
name(8)         = X.25 link name

Originator: Configuration Services - Verify

Explanation: Ignore this message if this configuration is being created for
another workstation with a different Connection Manager Outgoing Call
Directory.

User Response:

o If the configuration is for this workstation, create the missing entry in the
  Connection Manager Outgoing Call Directory.

o If the configuration is for another workstation with the same Connection
  Manager directory as this workstation, enter one of the existing entry names
  in the outgoing call directory entry name field for the X.25 link profile.


ΓòÉΓòÉΓòÉ 3.10.10. ACS0675 ΓòÉΓòÉΓòÉ

ACS0675-W System/36 resources are not available now.  Session ID(1) did not
start.

where
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The System/36 host you are connecting to might be busy or might
have a software problem.

User Response: Start the session at a later time. If the problem occurs again,
configure the session to connect to a system that is not a double-byte
character set (DBCS) system.


ΓòÉΓòÉΓòÉ 3.10.11. ACS0676 ΓòÉΓòÉΓòÉ

ACS0676-W The local 5250 emulator failed to connect to a DBCS preferred host.

Originator: 5250 Work Station Feature

Explanation: A local 5250 emulator session is configured to connect to a
double-byte character set (DBCS) preferred host.  However, 5250 DBCS support is
not currently available in the local emulator.

User Response: Reconfigure the session to connect to a non-DBCS preferred host.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code

   - 02/02/ Reserved

   - 04/02/ Location identifier

   - 06/02/ Reserved


ΓòÉΓòÉΓòÉ 3.10.12. ACS0678 ΓòÉΓòÉΓòÉ

ACS0678-E A data link control (DLC) error occurred while trying to start a
session.  Session ID(1) did not start.

where
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response:

o Run the diagnostic tests for the IBM Token-Ring, Twinaxial, SDLC, or X.25
  adapter in use.

o If the tests are successful, restart the 5250 Terminal Emulator.


ΓòÉΓòÉΓòÉ 3.10.13. ACS0680 ΓòÉΓòÉΓòÉ

ACS0680-W An emulator System/36 printer session is not configured properly.

Originator: 5250 Work Station Feature

Explanation: The local 5250 emulator configuration defines a printer session to
a host System/36.  This session should be reconfigured as a display session.

User Response: Reconfigure the local subconsole session to be a display
session.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code

   - 02/02/ Reserved

   - 04/02/ Location Identifier

   - 06/02/ Reserved


ΓòÉΓòÉΓòÉ 3.10.14. ACS0686 ΓòÉΓòÉΓòÉ

ACS0686-W Vital Product Data Manager (VPDM) experienced a system error and is
now inactive.

Originator: Vital Product Data Manager

Explanation: VPDM requested a system service and the request failed.

User Response: If Vital Product Data will be requested from this workstation by
the host, then take the following actions:

o Restart the system.

o If the problem persists, record the time stamp and component ID entry in the
  OS/2 System Error Log and report this information to your service
  coordinator.

System operations will continue normally, with the exception that Vital Product
Data will not be reported to the host. Otherwise, this error will not affect
the operation of the system and may be ignored.


ΓòÉΓòÉΓòÉ 3.10.15. ACS0687 ΓòÉΓòÉΓòÉ

ACS0687-E Vital Product Data Manager (VPDM) Initialization failed with a return
code of %1.

Originator: Vital Product Data Manager

Explanation: Vital Product Data Manager (VPDM) Initialization failed. No VPDM
function will be performed.

User Response: Stop and the restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.10.16. ACS0688 ΓòÉΓòÉΓòÉ

ACS0688-W Vital Product Data Manager (VPDM) Termination failed with a return
code of %1.

Originator: Vital Product Data Manager

Explanation: Vital Product Data Manager (VPDM) Termination failed. This will
not cause an error if a complete Communications Manager shutdown was in
progress. Return code 2304 (0x0900) is a general internal error condition.

User Response: If SNA was being shutdown via Subsystem Management, VPDM may not
successfully reinitialize when the SNA subsystem is restarted unless
Communications Manager is completely shutdown and restarted. Otherwise, no user
response is needed.


ΓòÉΓòÉΓòÉ 3.10.17. ACS0700 ΓòÉΓòÉΓòÉ

ACS0700-E An unexpected return code %1 was received from the Communications
Manager/2 utilities interface %2.

Originator: Common Services

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code can not be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry.  The last four digits of the minor error
  code provide the request code of the associated function call.

o If the request code/return code combination indicates a resource error,
  attempt to free the resource.  For resource errors that appear to be
  internal, reduce the number of active programs in the system.  Examples of
  such errors are memory, semaphores, and threads.


ΓòÉΓòÉΓòÉ 3.10.18. ACS0758 ΓòÉΓòÉΓòÉ

ACS0758-E X.25 Permanent Virtual Circuit (PVC) name(8) specified in X.25
Directory entry name(8) is not configured in X.25 link name(8). Ensure that the
PVC is configured in the X.25 link.

where
name(8)         = X.25 Permanent Virtual Circuit profile name
name(8)         = X.25 directory entry name
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

User Response: To configure an X.25 link:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select PVCs in the X.25 Links window.


ΓòÉΓòÉΓòÉ 3.10.19. ACS0770 ΓòÉΓòÉΓòÉ

ACS0770-E The specified logical channel number already exists in another
Permanent Virtual Circuit (PVC) for this link. Specify a different logical
channel number.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.10.20. ACS0773 ΓòÉΓòÉΓòÉ

ACS0773-W The ACDI API is set to load in the configuration auto-start, but
could not be started because it is not installed.

Originator: Communications Manager Kernel

User Response: Do one of the following:

o To install ACDI, select Communications Manager Setup from the Communications
  Manager/2 folder.  Specify the name of the configuration you want to install.

o Change the configuration so ACDI API is not loaded.


ΓòÉΓòÉΓòÉ 3.10.21. ACS0774 ΓòÉΓòÉΓòÉ

ACS0774-W An X.25 program issued X25Listen for a routing table entry name that
is already associated to another X.25 application.  A routing table entry can
only be associated to one X.25 application.

Originator: X.25 API

User Response: Check the X.25 applications to find out which two applications
use the X25Listen verb to associate to the same routing table entry.  Then,
modify one of the programs so that only one application is associated with the
routing table entry name.


ΓòÉΓòÉΓòÉ 3.10.22. ACS0776 ΓòÉΓòÉΓòÉ

ACS0776-W The X.25 network has sent diagnostic information to the local DTE for
link name(8) in slot num(2), indicating either a protocol violation on the part
of the local DTE or diagnostic information about the X.25 network.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

User Response:

o Note the time and the date of this message.  Then look for the alert entry
  associated with this message in the FFST/2 System Error Log. Identify and
  check the cause diagnostic code fields in Advanced Problem Determination for
  Communications.

o Check to be sure that the X.25 configuration data matches the attached local
  network parameters.

o Check to be sure that any local X.25 switching equipment or other equipment
  is correctly installed and configured.

o If the X.25 network to which the link is connected is operating normally, try
  again any operations that did not complete successfully.


ΓòÉΓòÉΓòÉ 3.10.23. ACS0777 ΓòÉΓòÉΓòÉ

ACS0777-W An X.25 packet-level timer for link name(8) in slot num(2) expired
before one of the following packets was received:  Restart confirmation; Call
Connected;  Call Accepted;  DCE or DTE Reset Confirmation; DCE or DTE Clear
Confirmation. All retry attempts have failed and virtual calls have been
cleared.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

Explanation: If the packet time-out value is not large enough, the physical
X.25 link may be terminated.  This can occur when network congestion is high
and the physical line speed is slow.

User Response:

o See the FFST/2 OS/2 System Error Log for the alert entry associated with this
  message to identify the timer that has expired.  Also note the associated
  retry and timer settings.

o You may want to increase the packet time-out value so that it is large enough
  to support possible network congestion.  To display the Packet Time-out
  Values window:

   - Select Setup in the Communications Manager Setup window.

   - Select the configuration name and then select OK in the Open a
     Configuration window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select X.25 links and then select Configure in the Communications Manager
     Configuration List window.

   - Select the link name and then select Change in the X.25 Links window.

   - Select Packet timeout values and then select Change in the X.25 Link
     Parameters window.

o Check to be sure that the X.25 configuration data matches the attached local
  X.25 network subscription parameters.

o Check to be sure that any local X.25 switching equipment or other equipment
  is correctly installed and configured.

o If the X.25 network to which the link is connected is operating normally, try
  to reestablish any virtual circuits that were lost when the timer expired.


ΓòÉΓòÉΓòÉ 3.10.24. ACS0778 ΓòÉΓòÉΓòÉ

ACS0778-W An X.25 supervisory packet has caused one of the following to occur
for link name(8) in slot num(2): A switched virtual call has been cleared; A
virtual circuit (switched or permanent) has been reset; The packet level has
been restarted, causing all existing virtual calls to be cleared and all
permanent virtual circuits to be reset.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

User Response:

o See the FFST/2 System Error Log alert entry associated with this message to
  identify the packet type and to check the associated cause and diagnostic
  codes.  Error log information is described in Advanced Problem Determination
  for Communications.

o Ensure that the X.25 configuration data matches the attached local network
  parameters.

o Ensure that any local X.25 switching equipment or other equipment is
  correctly installed and configured.

o If the X.25 network to which the link is connected is operating normally, try
  to reestablish any virtual circuits that were lost.


ΓòÉΓòÉΓòÉ 3.10.25. ACS0779 ΓòÉΓòÉΓòÉ

ACS0779-W Link name(8) in slot num(2) was reset because a frame reject response
was received, indicating a link access protocol balance failure.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

User Response:

o See the FFST/2 System Error Log alert entry associated with this message to
  identify the type of link error.  Error log information is described in
  Advanced Problem Determination for Communications.

o Check to be sure that the X.25 configuration data matches the attached local
  network parameters.

o Check to be sure that any local X.25 switching equipment or other equipment
  is correctly installed and configured.

o You may want to increase the T1 retransmission value to support possible
  network congestion.  If the T1 retransmission value is not large enough, the
  physical X.25 link may terminate. This will usually occur when network
  congestion is high and the physical line speed is slow.  To modify the T1
  parameter in the Frame Values window:

   - Select Setup in the Setup window.

   - Select the configuration name and then select OK in the Open a
     Configuration window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select X.25 links and then select Configure in the Communications Manager
     Configuration List window.

   - Select the link name and then select Change in the X.25 Links window.

   - Select Frame values and then select Change in the X.25 Link Parameters
     window.

o If the X.25 network to which the link is connected is operating normally, try
  to reconnect the link.


ΓòÉΓòÉΓòÉ 3.10.26. ACS0780 ΓòÉΓòÉΓòÉ

ACS0780-E A link failure for link name(8) in slot num(2) has been detected.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

Explanation: One of the following X.25 link error conditions has been detected
by the X.25 adapter:

o A command frame has been sent N2 times without receiving the appropriate
  response.

o An unexpected disconnect frame has been received.

o A request to initialize the link has been denied.

User Response:

o See the FFST/2 System Error Log alert entry associated with this message to
  identify the type of link failure.  Error log information is described in
  Advanced Problem Determination for Communications.

o Check to be sure that the X.25 configuration data matches the attached local
  network parameters.

o Check to be sure that any local X.25 switching or other equipment is
  correctly installed and configured.

o If the X.25 network to which the link is connected is operating normally, try
  to reconnect the link.


ΓòÉΓòÉΓòÉ 3.10.27. ACS0781 ΓòÉΓòÉΓòÉ

ACS0781-E The X.25 API detected an error on the local X.21 leased line facility
for link name(8) in slot num(2).

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

Explanation: The X.25 link was disconnected because of an X.21 attachment
error, or the X.25 link could not be connected because the local DCE was not
ready.

User Response:

o Be sure that the X.21 cable is attached correctly and is the correct type of
  cable for the X.25 Interface Co-Processor/2.

o Check to be sure that the X.25 configuration data matches the attached local
  X.25 network subscription parameters.

o If the modem and cable are installed and functioning properly, use the IBM
  Personal System/2 Reference Diskette to verify that the adapter is installed
  and configured correctly.


ΓòÉΓòÉΓòÉ 3.10.28. ACS0782 ΓòÉΓòÉΓòÉ

ACS0782-E Link name(8) in slot num(2) has been disconnected or could not
establish a call because of an error on the local Transpac VX32 modem.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

User Response:

o Check to be sure that the VX32 modem is on.

o If the VX32 modem cannot establish a link, check to be sure that the X.25
  subscription number and link parameters are correct.

o The VX32 modem link parameter has been selected.  Check to be sure that the
  X.25 configuration data matches the attached local network parameters.

o Check that the modem cable is attached correctly and is one of the valid IBM
  cable options for the X.25 Interface Co-Processor/2.

o If the modem and cable are installed and working properly, use the IBM
  Personal System/2 Reference Diskette to verify that the adapter is installed
  and configured correctly.


ΓòÉΓòÉΓòÉ 3.10.29. ACS0783 ΓòÉΓòÉΓòÉ

ACS0783-E An X.25 link was disconnected or could not be established because of
an error on the local modem for link name(8) in slot num(2).

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

User Response:

o Check to be sure that the modem is powered on.

o Check to be sure that the modem cable is attached correctly and is the
  correct type of cable for the X.25 Interface Co-Processor/2.

o If the modem and cable are installed and functioning properly, use the IBM
  Personal System/2 Reference Diskette to verify that the adapter is installed
  and configured correctly.

o Check to be sure that any local X.25 switching equipment or other equipment
  is correctly installed and configured.

o Check to be sure that the X.25 configuration data matches the attached local
  network.


ΓòÉΓòÉΓòÉ 3.10.30. ACS0784 ΓòÉΓòÉΓòÉ

ACS0784-W Both the QLLC (1980) and QLLC (1984) Routing Table entries are not
configured for X.25 link name(8). If no SNA X.25 incoming calls are to be
received on the link, no action is necessary. If SNA X.25 incoming calls are to
be received on the link, configure X.25 Routing Table entries for QLLC (1980)
and QLLC (1984).

where
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

Explanation: The specified X.25 link is configured for SNA (a DLC exists for
the link) and has switched virtual circuits (SVCs) defined for it, but QLLC
(1980) and QLLC (1984) routing table entries are not configured for the
specified link.

User Response: To configure an X.25 routing table entry:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 routing table and then select Configure in the Communications
  Manager Configuration List window.


ΓòÉΓòÉΓòÉ 3.11. ACS0786 through ACS0835 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.11.1. ACS0786 ΓòÉΓòÉΓòÉ

ACS0786-E The X.25 API detected an error on the adapter in slot num(2).

where
num(2)          = slot number

Originator: X.25 API

User Response:

o Ensure that the X.25 API configuration data matches the physical
  configuration of the system (adapters, links, modems, and cables) and the
  X.25 network subscription.

o Check to be sure that the X.25 adapter is installed and functioning
  correctly.  To configure an X.25 adapter in the X.25 Links Parameter window:

   - Select Setup in the Communications Manager Setup window.

   - Select the configuration name and then select OK in the Open a
     Configuration window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select X.25 links and then select Configure in the Communications Manager
     Configuration List window.

o Restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.11.2. ACS0787 ΓòÉΓòÉΓòÉ

ACS0787-E The X.25 API detected a configuration error on the adapter in slot
num(2).

where
num(2)          = slot number

Originator: X.25 API

User Response:

o Ensure that the X.25 API configuration data matches the physical
  configuration of the system (adapters, links, modems, and cables) and the
  X.25 network subscription.  To display the adapter configuration data in the
  X.25 Link Parameters window:

   - Select Setup in the Setup window.

   - Select the configuration name and then select OK in the Open a
     Configuration window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Definition. Definition window.

   - Select X.25 links and then select Configure in the Communications Manager
     Configuration List window.

   - Select the link name and then select Change in the X.25 Links window.

o Restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.11.3. ACS0788 ΓòÉΓòÉΓòÉ

ACS0788-E The X.25 API detected a software error on the adapter in slot num(2).

where
num(2)          = slot number

Originator: X.25 API

User Response:

o Ensure that the X.25 API configuration data matches the physical
  configuration of the system (adapters, links, modems, and cables) and the
  X.25 network subscription.  To display the adapter configuration data in the
  X.25 Link Parameters window:

   - Select Setup in the Setup window.

   - Select the configuration name and then select OK in the Open a
     Configuration window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select X.25 links and then select Configure in the Communications Manager
     Configuration List window.

   - Select the link name and then select Change in the X.25 Links window.

o Restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.11.4. ACS0789 ΓòÉΓòÉΓòÉ

ACS0789-E The X.25 API cannot be initialized because of insufficient system
resources.

Originator: X.25 API

Explanation: Other active programs may be using too many OS/2 resources, or
there may not be enough threads defined in the CONFIG.SYS file.

User Response: Stop enough other active programs to free OS/2 resources, and
check to be sure that the CONFIG.SYS file defines enough threads.


ΓòÉΓòÉΓòÉ 3.11.5. ACS0790 ΓòÉΓòÉΓòÉ

ACS0790-E The X.25 API ended because of a configuration error or a resource
error.

Originator: X.25 API

User Response:

o Ensure that the X.25 API is the only program being used by the X.25 adapter.

o Ensure that the configuration file in use is valid and is not corrupted.  If
  necessary, restore it from a backup file.

o Ensure that the X.25 API configuration data matches the physical
  configuration of the system (adapters, links, modems, and cables) and the
  X.25 network subscription.  To display the adapter configuration data in the
  X.25 Link Parameters window:

   - Select Setup in the Setup window.

   - Select the configuration name and then select OK in the Open a
     Configuration window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select X.25 links and then select Configure in the Communications Manager
     Configuration List window.

   - Select the link name and then select Change in the X.25 Links window.


ΓòÉΓòÉΓòÉ 3.11.6. ACS0791 ΓòÉΓòÉΓòÉ

ACS0791-E The X.25 API ended because an error occurred while it was accessing
the X.25 device driver.

Originator: X.25 API

User Response:

o Ensure that no programs except the X.25 API are using the X.25 adapter
  directly or through the device driver.

o Check to be sure that the X.25 device driver is installed correctly.

o Review the FFST/2 System Error Log for error log entries associated with this
  message.  Error log information is described in Advanced Problem
  Determination for Communications.


ΓòÉΓòÉΓòÉ 3.11.7. ACS0792 ΓòÉΓòÉΓòÉ

ACS0792-E The X.25 API detected a hardware error on the adapter in slot num(2).

where
num(2)          = slot number

Originator: X.25 API

User Response: If the modem and cable are installed and functioning properly,
use the IBM Personal System/2 Reference Diskette to verify that the adapter is
installed and configured correctly.


ΓòÉΓòÉΓòÉ 3.11.8. ACS0793 ΓòÉΓòÉΓòÉ

ACS0793-W An X.25 application cannot be started because the maximum number of
40 active applications has been reached. Decrease the number of X.25
applications running.

Originator: X.25 API


ΓòÉΓòÉΓòÉ 3.11.9. ACS0794 ΓòÉΓòÉΓòÉ

ACS0794-W An X.25 application ended prematurely because of an unexpected error.
X25AppTerm was not issued to end the X.25 application.

Originator: X.25 API

User Response: Ensure that the X.25 application is installed and that the X.25
feature is configured correctly for it. If the problem persists, note the time,
date, and message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.11.10. ACS0795 ΓòÉΓòÉΓòÉ

ACS0795-W An X.25 application issued X25PVCAlloc for Permanent Virtual Circuit
name(8), which is already in use.

where
name(8)         = Permanent Virtual Circuit name

Originator: X.25 API

User Response: Ensure that the X.25 permanent virtual circuits (PVCs) are
configured correctly for the X.25 application.


ΓòÉΓòÉΓòÉ 3.11.11. ACS0796 ΓòÉΓòÉΓòÉ

ACS0796-E The twinaxial data link control (DLC) received an unexpected
Terminate Link command from the host.

Originator: Twinaxial Data Link Control

User Response: If the host system is active, restart the twinaxial link.


ΓòÉΓòÉΓòÉ 3.11.12. ACS0797 ΓòÉΓòÉΓòÉ

ACS0797-E An unexpected internal program error occurred in the twinaxial data
link control (DLC).

Originator: Twinaxial Data Link Control

User Response: Check the error log for additional information about the program
error. Note the time, date, and message number; then contact your service
coordinator.


ΓòÉΓòÉΓòÉ 3.11.13. ACS0798 ΓòÉΓòÉΓòÉ

ACS0798-E The twinaxial data link control (DLC) was not able to create a thread
because the maximum number of threads was reached.

Originator: Twinaxial Data Link Control

User Response: 1.  Stop any unnecessary programs, or increase the maximum
number of threads allowed in the system by increasing the value in the THREAD=
statement in the CONFIG.SYS file. 2.  Restart the workstation and
Communications Manager. 3.  Retry the operation.


ΓòÉΓòÉΓòÉ 3.11.14. ACS0799 ΓòÉΓòÉΓòÉ

ACS0799-E The twinaxial data link control (DLC) ended because of insufficient
memory.

Originator: Twinaxial Data Link Control

User Response: Do one of the following:

o Install more system memory.

o Release memory by stopping programs that are currently running.


ΓòÉΓòÉΓòÉ 3.11.15. ACS0800 ΓòÉΓòÉΓòÉ

ACS0800-E The link station closed because the twinaxial data link control (DLC)
received a host command that is not valid or not supported.

Originator: Twinaxial Data Link Control

User Response: Check the error log for more information about the host command.
Note the time, date, and message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.11.16. ACS0801 ΓòÉΓòÉΓòÉ

ACS0801-E A twinaxial adapter check occurred because the adapter card is not
seated properly or it had an internal failure.

Originator: Twinaxial Data Link Control

User Response: 1.  Stop Communications Manager and turn off the workstation. 2.
Disconnect all electrical connections. 3.  Inspect the adapter to ensure that
it is properly seated. 4.  Reconnect all electrical connections. 5.  Turn on
the workstation and restart Communications Manager. 6.  Retry the operation.


ΓòÉΓòÉΓòÉ 3.11.17. ACS0802 ΓòÉΓòÉΓòÉ

ACS0802-E A twinaxial link failure occurred because the twinaxial cable is
loose or defective.

Originator: Twinaxial Data Link Control

User Response: 1.  Inspect the twinaxial cable connection to the workstation.
2.  Ensure proper connection and retry the operation. 3.  If the problem
persists, try a different physical twinaxial connection and restart
Communications Manager.


ΓòÉΓòÉΓòÉ 3.11.18. ACS0803 ΓòÉΓòÉΓòÉ

ACS0803-E A device driver error occurred while initializing the twinaxial data
link control (DLC).

Originator: Twinaxial Data Link Control

Explanation: Likely causes of the error are:

o The DEVICE= statement is missing from the CONFIG.SYS file.

o The device driver was not specified correctly.

o One of the device driver files was not found.

User Response: 1.  Stop Communications Manager. 2.  Add an appropriate DEVICE=
statement to the CONFIG.SYS file or correct the existing DEVICE= statement. 3.
Restart the workstation. 4.  Retry the operation. If the problem persists,
reinstall Communications Manager and retry the operation.


ΓòÉΓòÉΓòÉ 3.11.19. ACS0804 ΓòÉΓòÉΓòÉ

ACS0804-E The workstation address specified in the twinaxial data link control
(DLC) configuration is already being used.  Two users are configured to the
same workstation address, and the initialization was not completed.

Originator: Twinaxial Data Link Control

User Response:

o Check the workstation address in the twinaxial data link control (DLC)
  configuration.

o If the address is not correct, configure the workstation address correctly,
  and then retry the twinaxial link.


ΓòÉΓòÉΓòÉ 3.11.20. ACS0813 ΓòÉΓòÉΓòÉ

ACS0813-W The System/36 workstation ID ID(2) is already in use.  Session ID(1)
did not start.

where
ID(2)           = workstation ID
ID(1)           = short session ID

Originator: 5250 Work Station Feature

Explanation: The workstation ID that was initially assigned for the session is
now being used by another session. If the session that did not start is a
printer session, the problem could be:

o A user configured a printer with a specific workstation ID rather than using
  the default created by System/36.

o A user configured a printer with a printer ID that was already assigned.

If the session that did not start is a display session, the problem could be:

o A user configured a workstation ID that is already being used by another
  session.

o A user did not sign off the workstation before exiting Communications
  Manager.

User Response:

o For printer sessions, the configured printer ID may become available after
  the current user of the ID stops the session.  At that time, restart 5250
  Terminal emulation and retry the operation.

o If you need the printer session immediately, restart 5250 terminal emulation
  with a printer session that has a workstation ID not currently in use.

o For display sessions, change 5250 terminal emulation session profile to use a
  different workstation ID.  If the ID for your session is currently blank,
  specify a unique ID.


ΓòÉΓòÉΓòÉ 3.11.21. ACS0814 ΓòÉΓòÉΓòÉ

ACS0814-W The virtual device name(10) on the AS/400 host associated with your
workstation was not allocated.  Session ID(1) did not start.

where
name(10)        = AS/400 virtual device name
ID(1)           = short session ID

Originator: 5250 Work Station Feature

User Response: Check the host system for related messages and logs that will
help identify the cause and recovery actions.


ΓòÉΓòÉΓòÉ 3.11.22. ACS0825 ΓòÉΓòÉΓòÉ

ACS0825-E The X.25 DLC profile name(8), referred to by X.25 SNA directory entry
name(8), does not exist.

where
name(8)         = X.25 DLC name
name(8)         = X.25 directory name

Originator: Configuration Services - Verify

Explanation: No X.25 DLC profile was found with the same name as the X.25 link
specified by the preceding X.25 SNA directory entry.

User Response: Either configure the X.25 DLC profile or change the X.25 SNA
directory entry link name to refer to existing X.25 link and X.25 DLC profiles.


ΓòÉΓòÉΓòÉ 3.11.23. ACS0826 ΓòÉΓòÉΓòÉ

ACS0826-W The shared random access memory (RAM) location twinaxial DLC profile
and this 3270 Terminal emulation profile for coaxial (DFT) overlap.

Originator: Configuration Services - Verify

User Response: Change the shared RAM location in the twinaxial DLC. To access
the twinaxial DLC:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and select OK in the Open Configuration window.

o Select any feature working through the twinaxial workstation connection and
  then select Configure in the Communications Manager Configuration Definition
  window.

o Select twinaxial DLC and then select Configure in the Communications Manager
  Profile List window.


ΓòÉΓòÉΓòÉ 3.11.24. ACS0828 ΓòÉΓòÉΓòÉ

ACS0828-E An initialization error occurred loading IBM Realtime Interface
Co-Processor OS/2 Support on the X.25 adapter in slot num(2).  IBM Realtime
Interface Co-Processor OS/2 Support cannot be used for communications.

where
num(2)          = X.25 slot number

Originator: Communications Manager Kernel

User Response:

o Run diagnostics on the specified adapter.

o Replace or repair the specified adapter, if necessary.

o Retry the operation.

o If the adapter is not the problem, select Communications Manager Setup from
  the Communications Manager/2 folder. Select Installation. Specify the name of
  the configuration you want to install.


ΓòÉΓòÉΓòÉ 3.11.25. ACS0829 ΓòÉΓòÉΓòÉ

ACS0829-E An error occurred loading IBM Realtime Interface Co-Processor OS/2
Support on the X.25 adapter in slot num(2).  IBM Realtime Interface
Co-Processor OS/2 Support cannot be used for communications.

where
num(2)          = X.25 slot number

Originator: Communications Manager Kernel

User Response:

o Check the system error log for secondary status information.

o Run diagnostics on the specified adapter.

o Replace or repair the specified adapter, if necessary.

o Retry the operation.

o If the adapter is not the problem, select Communications Manager Setup from
  the Communications Manager/2 folder.  Select Installation. Specify the name
  of the configuration that you want to install.


ΓòÉΓòÉΓòÉ 3.11.26. ACS0830 ΓòÉΓòÉΓòÉ

ACS0830-E An initialization error occurred loading the X.25 adapter driver on
the X.25 adapter in slot num(2).  The X.25 adapter driver cannot be used for
communications.  There could be an adapter malfunction.

where
num(2)          = X.25 slot number

Originator: Communications Manager Kernel

User Response:

o Run diagnostics on the specified adapter.

o Replace or repair the specified adapter, if necessary.

o Retry the operation.

o If the adapter is not the problem, select Communications Manager Setup from
  the Communications Manager/2 folder. Select Installation. Specify the name of
  the configuration you want to install.


ΓòÉΓòÉΓòÉ 3.11.27. ACS0831 ΓòÉΓòÉΓòÉ

ACS0831-E An error occurred loading the X.25 adapter drive on the X.25 adapter
in slot num(2).  The X.25 adapter driver cannot be used for communications.

where
num(2)          = X.25 slot number

Originator: Communications Manager Kernel

User Response:

o Check the system error log for secondary status information.

o Run diagnostics on the specified adapter.

o Replace or repair the specified adapter, if necessary.

o Retry the operation.

o If the adapter is not the problem, select Setup from the Communications
  Manager/2 folder to access installation. Specify the name of the
  configuration that you want to install.


ΓòÉΓòÉΓòÉ 3.11.28. ACS0832 ΓòÉΓòÉΓòÉ

ACS0832-E The X.25 API could not be started because the X.25 device driver is
not the correct version.  Reinstall Communications Manager.

Originator: Communications Manager Kernel

User Response: Select Communications Manager Setup from the Communications
Manager/2 folder.  Select Installation.  Specify the name of the configuration
that you want to install or create a new configuration to be used by the
installation process.


ΓòÉΓòÉΓòÉ 3.11.29. ACS0834 ΓòÉΓòÉΓòÉ

ACS0834-E Code page num(5) is outside the range of 65280 to 65534 and is not
supported.

where
num(5)          = code page number

Originator: General Convert Utility

Explanation: Only IBM-supplied code page numbers that are supported by
Communications Manager are honored outside the range of 65280 to 65534. User
defined code pages created with numbers outside this range are ignored.

User Response: Specify another code page number or rename the user defined code
page definition file to a number inside the range 65280 to 65534.  Retry the
operation specifying the new number.


ΓòÉΓòÉΓòÉ 3.11.30. ACS0835 ΓòÉΓòÉΓòÉ

ACS0835-E Code page definition file name(9) was not found in the CMLIB
subdirectory.

where
name(9)         = code page definition file name

Originator: General Convert Utility

Explanation: Code page definition files must be in the CMLIB subdirectory with
a file name and file extension of .CPT.  The file name is the decimal code page
number and it cannot be more than 5 digits. IBM supplied code page numbers are
in the range of 1 to 65279. User defined code page numbers must be in the range
of 65280 to 65534.

User Response: Ensure that the correct code page number is specified and is in
the CMLIB subdirectory.  Retry the operation.


ΓòÉΓòÉΓòÉ 3.12. ACS0836 through ACS0921 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.12.1. ACS0836 ΓòÉΓòÉΓòÉ

ACS0836-E Code page definition file name(9) has less than 256 character names
or does not have the proper format.

where
name(9)         = code page definition file name

Originator: General Convert Utility

Explanation: Exactly 256 character names must appear in a code page definition
file.  A code page definition file must be 256 lines long, not including blank
lines.  Each non-blank line contains exactly one character name.  A character
name begins with the first non-blank character of the line.  It ends with the
first blank or the end of the line, whichever comes first.  Therefore, a
character name cannot contain imbedded blanks.  A character name longer than 40
characters is truncated.  The message occurs for one of the following reasons:

o A user defined code page number is specified for an operation and the
  associated code page definition file has less than 256 character names in it.

o The user defined code page definition file is not in the proper format.

User Response: Do one of the following and retry the operation:

o Add more character names to the code page definition file.

o Correct the format problems with the user defined code page definition file.

o Specify a different code page number.


ΓòÉΓòÉΓòÉ 3.12.2. ACS0837 ΓòÉΓòÉΓòÉ

ACS0837-E Code page definition file name(9) has more than 256 character names
or does not have the proper format.

where
name(9)         = code page definition file name

Originator: General Convert Utility

Explanation: Exactly 256 character names must appear in a code page definition
file.  A code page definition file must be 256 lines long, not including blank
lines.  Each non-blank line contains exactly one character name.  A character
name begins with the first non-blank character of the line.  It ends with the
first blank or the end of the line, which ever comes first.  Therefore, a
character name cannot contain imbedded blanks.  A character name longer than 40
characters is truncated. The message occurs for one of the following reasons:

o A user defined code page number is specified for an operation and the
  associated code page definition file has more than 256 character names in it.

o The user defined code page definition file is not in the proper format.

User Response: Do one of the following and retry the operation:

o Remove excessive character names from the code page definition file.

o Correct the format problems with the user defined code page definition file.

o Specify a different code page number.


ΓòÉΓòÉΓòÉ 3.12.3. ACS0838 ΓòÉΓòÉΓòÉ

ACS0838-E Error rc(5) was detected while opening code page definition file
name(9).

where
rc(5)           = open file failure return code
name(9)         = code page definition file name

Originator: General Convert Utility

Explanation: One of the following could cause this error:

o A user defined code page number was specified which does not have a
  corresponding code page definition file in the CMLIB subdirectory.

o A user defined code page definition file is not named properly. The file name
  is a five digit number in the range of 65280 to 65534. The file extension
  must be .CPT.

o The code page definition file is damaged or modified.

User Response:

o Ensure that the specified code page has a code page definition file in the
  CMLIB subdirectory.

o For more information about the error, type HELP nnnn at the OS/2 command
  prompt, where nnnn is the open error return code specified in the message.

o If the help information indicates that the file is damaged, restore it from a
  backup copy or create a new file.

o Retry the operation.


ΓòÉΓòÉΓòÉ 3.12.4. ACS0839 ΓòÉΓòÉΓòÉ

ACS0839-E Code page definition file name(9) has exceeded the maximum of 128
user defined character names or does not have the proper format.

where
name(9)         = code page definition file name

Originator: General Convert Utility

Explanation: A user defined character name is one which is not found in any of
the IBM supplied code page definition files. A code page definition file must
be 256 lines long, not including blank lines.  Each non-blank line contains
exactly one character name.  A character name begins with the first non-blank
character of the line. It ends with the first blank or the end of the line,
which ever comes first.  Therefore, a character name cannot contain imbedded
blanks.  A character name longer than 40 characters is truncated.

User Response: Do one of the following and then retry the operation.

o Replace some of the user defined character names with IBM defined character
  names so that there are not more than 128 user defined character names.

o Correct the format problems with the user defined code page definition file.

o Specify a different code page number.


ΓòÉΓòÉΓòÉ 3.12.5. ACS0840 ΓòÉΓòÉΓòÉ

ACS0840-W The X.25 API tried to write to an X.25 application queue but the
queue was closed.  Correct the application and try the operation again.

Originator: X.25 API


ΓòÉΓòÉΓòÉ 3.12.6. ACS0843 ΓòÉΓòÉΓòÉ

ACS0843-E No incoming call directory entry name was specified in name(8) DLC
num(4).

where
name(8)         = SDLC/IDLC DLC name
num(4)          = SDLC/IDLC number

Originator: Configuration Services - Verify

Explanation: The DLC profile is to be used over ISDN, and has the Accept
Incoming Calls option selected, but does not have an incoming call directory
entry name specified.

User Response:

o If incoming calls are not to be accepted with this DLC, reconfigure the DLC
  with the Accept Incoming Calls option deselected, and rerun Verify.

o If incoming calls are to be accepted with this DLC, reconfigure the DLC,
  specifying the desired incoming call directory entry name.


ΓòÉΓòÉΓòÉ 3.12.7. ACS0844 ΓòÉΓòÉΓòÉ

ACS0844-E The file CM.INI was not found. Verify cannot continue.

Originator: Configuration Services - Verify

User Response: The CM.INI file must exist for Communications Manager to run. If
the CM.INI file was accidentally renamed, change the file name back to CM.INI.
If the CM.INI file does not exist, reinstall Communications Manager.


ΓòÉΓòÉΓòÉ 3.12.8. ACS0845 ΓòÉΓòÉΓòÉ

ACS0845-W The incoming call directory entry name name(16) in name(8) DLC DLC
num(4) was not found in the Connection Manager Connection Manager Incoming Call
Directory.  Ignore this message if this configuration is being created for
another workstation with a different Connection Manager Incoming Call
Directory.

where
name(16)        = ICRT entry name
name(8)         = SDLC/IDLC DLC name
num(4)          = SDLC/IDLC number

Originator: Configuration Services - Verify

User Response:

o If the configuration is for this workstation, create the missing entry in the
  Connection Manager Incoming Call Directory.

o If the configuration is for another workstation with the same Connection
  Manager directory as this workstation, enter one of the existing entry names
  in the incoming call directory entry name field for the DLC profile.


ΓòÉΓòÉΓòÉ 3.12.9. ACS0846 ΓòÉΓòÉΓòÉ

ACS0846-E The SNA/APPC service was selected to be loaded but was not
configured.

Originator: Verify and Convert Configuration File

Explanation: The SNA/APPC service was selected but was not configured.

User Response: Configure the SNA/APPC service.


ΓòÉΓòÉΓòÉ 3.12.10. ACS0848 ΓòÉΓòÉΓòÉ

ACS0848-E No more than 7 SNA routing table entries can be configured for an
X.25 link.  This limit has been reached.  Choose a different link name and
retry the operation.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.12.11. ACS0869 ΓòÉΓòÉΓòÉ

ACS0869-E The X.25 permanent virtual circuit (PVC) link name(8) is configured
to use SNA, but there is no X.25 DLC for this link.

where
name(8)         = X.25 Permanent Virtual Circuit link profile name

Originator: Configuration Services - Verify

User Response: If you can change your workstation configuration, either
configure an X.25 data link control (DLC) for this link or do not specify X.25
to use SNA. To configure an X.25 data link control (DLC) for this link,
complete the following steps:

o Select Options in the Communications Manager Configuration Definition window.

o Select Configure any profile or feature.  The Communications Manager
  Configuration List window appears.

o Select DLC - X.25 (for ISDN or non-ISDN).  The X.25 DLC (for ISDN or
  Non-ISDN) Adapter Parameters window appears.

o Type in the name of the link associated with the PVC, and then select OK. To
  change the X.25 configuration so that it uses non-SNA PVCs instead of SNA
  PVCs:

o Select Options in the Communications Manager Configuration Definition window.

o Select Configure any profile or feature.  The Communications Manager
  Configuration List window appears.

o Select X.25 links from the Profile or Feature Name list.  The X.25 Links
  window appears.

o Select the link you want to change.  Then select the PVCs push button. The
  X.25 Permanent Virtual Circuits window appears.

o Select the PVC you want to change, and then select Change....  The Permanent
  Virtual Circuit window appears.

o Select Non-SNA in the Type list.  Then select OK. If you cannot change your
  workstation configuration, note the time, date, and this message number; then
  contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.12. ACS0870 ΓòÉΓòÉΓòÉ

ACS0870-E The total number of incoming and outgoing connections for X.25 DLC
name(8) exceeds the number of switched virtual circuits (SVCs) defined in X.25
link name(8).

where
name(8)         = X.25 DLC profile name
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

User Response: Ensure that the number of incoming connections specified in the
X.25 DLC Adapter Parameters window and the number of outgoing connections do
not exceed the number of switched virtual circuits specified in the Virtual
Circuit Ranges window.  The number of outgoing connections is the number of
remote SNA switched virtual circuit directory entries configured for the X.25
link. You can do any of the following to correct the problem:

o Decrease the number of incoming connections

o Decrease the number of outgoing connections

o Increase the number of switched virtual circuits.

To do any of the above, begin by completing the following steps:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

To decrease the number of incoming connections, complete the following steps:

o Select DLC - X.25 (for ISDN or non-ISDN), and then select Configure in the
  Communications Manager Configuration List window.  The X.25 DLC (for ISDN or
  Non-ISDN) Adapter Parameters window appears.

o Change the value in the Number of incoming connections field so that the
  number of incoming connections is less than the combined total of in-only and
  two-way switched virtual circuits.

To decrease the number of outgoing connections, complete the following steps:

o Select X.25 directory entries, and then select Configure in the
  Communications Manager Configuration List window.

o Select an SNA SVC directory entry name for this link.

o Select Delete or (if you want to keep the directory entry) Change....

o If you selected Change..., the SNA SVC Directory Entry window appears.

o Change the link name so that the SNA switched virtual circuit directory entry
  is no longer associated with the link specified in the message.

To increase the number of switched virtual circuits, complete the following
steps:

o Select X.25 links, and then select Configure... in the Communications Manager
  Configuration List window.

o Select the link name, and then select Change... in the X.25 Links window.

o Select Virtual circuit ranges and then select Change... in the X.25 Link
  Parameters window.  The Virtual Circuit Ranges window appears.

o Change the ranges so that the following rules apply:

   - The number of incoming connections is less than or equal to the combined
     total of in-only and two-way switched virtual circuits.

   - The number of outgoing connections must be less than or equal to the
     combined total of out-only and two-way switched virtual circuit.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.13. ACS0871 ΓòÉΓòÉΓòÉ

ACS0871-E X.25 link name(8) specified in X.25 DLC name(8) does not exist.

where
name(8)         = X.25 link profile name
name(8)         = X.25 DLC profile name

Originator: Configuration Services - Verify

User Response: If you can change your workstation configuration, either refer
to an existing X.25 link or configure the missing X.25 link. To configure an
X.25 link:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.14. ACS0872 ΓòÉΓòÉΓòÉ

ACS0872-E X.25 link name(8) specified in X.25 Routing Table entry name(8) does
not exist.

where
name(8)         = X.25 link profile name
name(8)         = X.25 routing table entry name

Originator: Configuration Services - Verify

User Response: If you can change your workstation configuration, either refer
to an existing X.25 link or configure the missing X.25 link. To configure a
link:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.15. ACS0873 ΓòÉΓòÉΓòÉ

ACS0873-E X.25 permanent virtual circuit (PVC) link name(8) specified in X.25
directory entry name(8) does not exist.

where
name(8)         = X.25 Permanent Virtual Circuit link profile name
name(8)         = X.25 directory entry name

Originator: Configuration Services - Verify

User Response: If you can change your workstation configuration, either refer
to an existing X.25 PVC link or create the missing X.25 PVC link. To create an
X.25 PVC link:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select PVCs in the X.25 Links window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.16. ACS0874 ΓòÉΓòÉΓòÉ

ACS0874-E X.25 link name(8) referenced in X.25 Directory entry name(8) does not
exist.

where
name(8)         = X.25 link profile name
name(8)         = X.25 directory entry name

Originator: Configuration Services - Verify

User Response: If you can change your workstation configuration, either refer
to an existing X.25 link or create the missing X.25 link. To create an X.25
link:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.17. ACS0875 ΓòÉΓòÉΓòÉ

ACS0875-E The logical channel number specified for X.25 permanent virtual
circuit (PVC) name(8) is outside of the PVC range defined in X.25 link name(8).

where
name(8)         = X.25 Permanent Virtual Circuit profile name
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

User Response: Ensure that the logical channel number for the PVC is within the
PVC range specified in the virtual circuit ranges for the X.25 link.  If you
can change your workstation configuration:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

To change the virtual circuit ranges:

o Select the link name and then select Change in the X.25 Links window.

o Select Virtual circuit ranges and then select Change in the X.25 Link
  Parameters window.

To change the PVC logical channel number:

o Select PVCs in the X.25 Links window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.18. ACS0876 ΓòÉΓòÉΓòÉ

ACS0876-E The number of permanent virtual circuits (PVCs) configured for X.25
link name(8) exceeds the number of PVCs specified in the Virtual Circuit Ranges
window.

where
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

Explanation: All PVC logical channel numbers do not have corresponding PVCs
configured in the X.25 link.

User Response: Ensure that the number of PVCs configured for the link do not
exceed the number of PVCs specified in the Virtual Circuit Ranges window.  If
you can change your workstation configuration:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

To change the virtual circuit ranges:

o Select the link name and then select Change in the X.25 Links window.

o Select Virtual circuit ranges and then select Change in the X.25 Link
  Parameters window.

To change the PVC logical channel number:

o Select PVCs in the X.25 Links window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.19. ACS0879 ΓòÉΓòÉΓòÉ

ACS0879-E The packet sequence number modulus in X.25 link name(8) is 8, but a
window size in the associated X.25 permanent virtual circuit (PVC) is
configured to be greater than 7.

where
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

User Response: Ensure that you selected a valid packet sequence number modulus.
If the packet sequence number modulus is 8, the PVC profile window size is in a
range of 1 to 7.  If it is 128, the PVC profile window size is in a range of 1
to 127. If you can change your workstation configuration:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

To change the PVC window sizes:

o Select the link name and then select PVCs in the X.25 Links window.

o Select the PVC name and then select Change in the X.25 Permanent Virtual
  Circuits window.

To change the modulus number to 128:

o Select the link name and then select Change in the X.25 Links window.

o Select SVC/PVC window sizes and then select Change in the X.25 Parameters
  window.

If you cannot change your workstation configuration, note the time, date, and
message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.20. ACS0880 ΓòÉΓòÉΓòÉ

ACS0880-E The Local CCITT compliance in X.25 link name(8) is 1980 and the
packet size in permanent virtual circuit (PVC) name(8) is greater than the
allowable range of 1024.  Ensure that the packet size is 1024 or less.

where
name(8)         = link name
name(8)         = Permanent Virtual Circuit name

Originator: Configuration Services - Verify

User Response: To check the packet size:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select PVCs in the X.25 Links window.

o Select the PVC name and then select Change in the X.25 Permanent Virtual
  Circuits window.

If you cannot change your workstation configuration, note the time, date, and
message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.21. ACS0882 ΓòÉΓòÉΓòÉ

ACS0882-E At least one virtual circuit range must be specified in X.25 link
name(8), and none is specified.

where
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

User Response: Configure the virtual circuit ranges in the X.25 link. To
configure the virtual circuit ranges in an X.25 link:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select Change in the X.25 Links window.

o Select Virtual circuit ranges and then select Change in the X.25 Link
  Parameters window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.22. ACS0883 ΓòÉΓòÉΓòÉ

ACS0883-E The local data terminal equipment (DTE) address field in X.25 link
name(8) is blank.  A value is required for this field.

where
name(8)         = X.25 link profile name

Originator: Configuration Services - Verify

User Response: Configure the local DTE address in the X.25 Link Parameters
window for the link.  The address must be integer values in the range of 1 to
15.  To configure the Local DTE address:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select Change in the X.25 Links window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.23. ACS0885 ΓòÉΓòÉΓòÉ

ACS0885-E A conflict exists between X.25 remote permanent virtual circuit (PVC)
directory entry name(8) and the SNA circuit field of X.25 PVC name(8).

where
name(8)         = X.25 Permanent Virtual Circuit directory entry name
name(8)         = X.25 Permanent Virtual Circuit profile name

Originator: Configuration Services - Verify

User Response: If the directory entry is a remote SNA PVC entry, the SNA
circuit field in the X.25 PVC must be set to Yes. If the specified directory
entry is a remote non-SNA PVC entry, the SNA circuit field in the X.25 PVC must
be set to No.  To change the SNA circuit field in an X.25 PVC:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select PVCs in the X.25 Links window.

o Select the PVC name and then select Change in the X.25 Permanent Virtual
  Circuits window.

If you cannot change your workstation configuration, note the time, date, and
this message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.12.24. ACS0886 ΓòÉΓòÉΓòÉ

ACS0886-E The number of virtual circuits associated with X.25 link profile
name(8) exceeds 128.

where
name(8)         = X.25 link name

Originator: Configuration Services - Verify

Explanation: The total number of X.25 Virtual Circuits (VCs) configured for the
named X.25 link profile exceeds 128.

User Response: Either delete some of the PVCs or delete some of the remote
switched virtual circuit (SVC) directory entries.  In the Virtual Circuit
Ranges window, the following fields cannot contain values that total 128 or
greater.

o Number of PVCs

o Number of Incoming-Only SVCs

o Number of Two-Way SVCs

o Number of Outgoing-Only SVCs.

If you reduce any of the preceding values, make sure you delete the associated
entries.  To delete PVCs or remote SVC directory entries:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

To delete PVCs:

o Select X.25 links and then select Configure in the Communications Manager
  Configuration List window.

o Select the link name and then select PVCs in the X.25 Links window.

To delete remote SVC entries:

o Select X.25 directory entries and then select Configure in the Communications
  Manager Configuration List window.


ΓòÉΓòÉΓòÉ 3.12.25. ACS0903 ΓòÉΓòÉΓòÉ

ACS0903-W X.25 DLC profile name(8) is configured and is specified to be loaded,
but it is not referred to by any other profile.

where
name(8)         = X.25 DLC name

Originator: Configuration Services - Verify

User Response: If you do not want to use the X.25 DLC, no action is necessary.
If you want to use the X.25 DLC, it must be referred to by the appropriate
profile.


ΓòÉΓòÉΓòÉ 3.12.26. ACS0911 ΓòÉΓòÉΓòÉ

ACS0911-W The 5250 emulation is configured but cannot be used because the
SNA/APPN service is not configured to be loaded.

Originator: Configuration Services - Verify

User Response: If you are using the 5250 emulation, configure the SNA/APPN
service to be loaded in the Workstation Information window. To access the
Workstation Information window:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Options on the menu bar in the Communications Manager Configuration
  Definition window.

o Select Change workstation information from the Options pull-down menu.


ΓòÉΓòÉΓòÉ 3.12.27. ACS0915 ΓòÉΓòÉΓòÉ

ACS0915-E 5250 printer session name(8) requires that session ID(8) be
configured as a System/36 display session.

where
name(8)         = 5250 emulation printer session name
ID(8)           = session ID

Originator: Configuration Services - Verify

Explanation: 5250 session has the subconsole assigned to either a session that
does not exist, a printer session, or a display session whose host type is not
System/36.

User Response: Change the subconsole to either a display or a system console
session with host type set to System/36, or create the missing display or
system console session, setting the session's host type to System/36.


ΓòÉΓòÉΓòÉ 3.12.28. ACS0919 ΓòÉΓòÉΓòÉ

ACS0919-E APPC partner LU alias name(8) specified in the 5250 emulation profile
name(8) does not exist.

where
name(8)         = APPC partner LU alias name
name(8)         = 5250 emulation profile name

Originator: Configuration Services - Verify

User Response: Either configure the missing APPC partner logical unit (LU)
alias or change the 5250 Emulation session profile to specify an existing APPC
partner LU alias.


ΓòÉΓòÉΓòÉ 3.12.29. ACS0920 ΓòÉΓòÉΓòÉ

ACS0920-E The LU alias name(8) does not exist.

where
name(8)         = APPN LU alias name

Originator: Configuration Services - Verify

Explanation: The 5250 profile has an APPN LU alias that has not been
configured.

User Response: Either configure the new APPN LU alias name or change the 5250
emulation profile.


ΓòÉΓòÉΓòÉ 3.12.30. ACS0921 ΓòÉΓòÉΓòÉ

ACS0921-E The Communications Manager configuration verification process
encountered errors while trying to read configuration name(12). Retry
verification of your Communications Manager configuration.

where
name(12)        = configuration file name

Originator: Configuration Services - Verify

User Response: If this error persists, recreate your configuration and then
retry verification. To retry verification of the configuration file, enter
CMVERIFY configuration_name.CFG at the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.13. ACS0922 through ACS1049 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.13.1. ACS0922 ΓòÉΓòÉΓòÉ

ACS0922-E Verification of configuration name(12) cannot be performed at this
time because emulation session record name(8) in this configuration is in use
by another process.

where
name(12)        = configuration file name
name(8)         = emulator session record name

Originator: Configuration Services - Verify

User Response: Either stop the other process or wait until the other process
has terminated.  Then, retry verification. To retry verification of the
configuration file, enter CMVERIFY configuration_name.CFG at the OS/2 command
prompt.


ΓòÉΓòÉΓòÉ 3.13.2. ACS0923 ΓòÉΓòÉΓòÉ

ACS0923-E Verification of configuration name(12) cannot be performed at this
time because the configuration file is in use by another process.

where
name(12)        = configuration file name

Originator: Configuration Services - Verify

User Response: Either stop the other process or wait until the other process
has terminated.  Then, retry verification. To retry verification of the
configuration file, enter CMVERIFY configuration_name.CFG at the OS/2 command
prompt.


ΓòÉΓòÉΓòÉ 3.13.3. ACS0924 ΓòÉΓòÉΓòÉ

ACS0924-E Verification of configuration name(12) cannot be completed at this
time because the configuration is in use by another process.  All emulation
session information in this configuration was found to be correct.

where
name(12)        = configuration file name

Originator: Configuration Services - Verify

User Response: To complete the verification of this configuration, either stop
the process using the configuration or wait until the process has terminated.
Then, retry verification. To retry verification of the configuration file,
enter CMVERIFY configuration_name.CFG at the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.13.4. ACS0942 ΓòÉΓòÉΓòÉ

ACS0942-W The X.25 API tried to write to an X.25 application queue, but no
queue space was available. To free queue space, stop some of the other
applications that are currently running and try the operation again.

Originator: X.25 API


ΓòÉΓòÉΓòÉ 3.13.5. ACS0943 ΓòÉΓòÉΓòÉ

ACS0943-W An application tried to issue an X.25 API verb, but not enough memory
segments were available.  To free memory segments, stop some of the other X.25
applications that are currently running and try the operation again.

Originator: X.25 API


ΓòÉΓòÉΓòÉ 3.13.6. ACS0944 ΓòÉΓòÉΓòÉ

ACS0944-W An application tried to issue an X.25 API verb, but the maximum
number of verbs has already been queued.

Originator: X.25 API

Explanation: One of the following has occurred:

o An application issued more than the maximum number of verbs allowed by X.25.

o Too many verbs were queued to an X.25 adapter.

o Other concurrently running X.25 applications issued the maximum number of
  verbs allowed by X.25.

User Response: To free queue space, stop some of the other applications that
are currently running and try the operation again.


ΓòÉΓòÉΓòÉ 3.13.7. ACS0945 ΓòÉΓòÉΓòÉ

ACS0945-W The X.25 API detected a software error in a single virtual circuit
and ended a connection on link name(8) in slot num(2).

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

User Response: Ensure that the X.25 API configuration data matches the physical
configuration for the system (adapters, links, modems, and cables) and the X.25
network subscription.


ΓòÉΓòÉΓòÉ 3.13.8. ACS0946 ΓòÉΓòÉΓòÉ

ACS0946-W There is not enough memory to process a verb issued by an X.25
application.  Either stop some of the currently running programs, or increase
the amount of memory.

Originator: X.25 API


ΓòÉΓòÉΓòÉ 3.13.9. ACS0947 ΓòÉΓòÉΓòÉ

ACS0947-E The X.25 API could not be initialized because of a configuration
error.

Originator: X.25 API

User Response:

o Check the configuration to ensure that it has not been altered or damaged.
  If necessary, restore the configuration from a backup file.

o Ensure that the X.25 API configuration data matches the physical
  configuration of the system (adapters, links, modems, and cables) and the
  X.25 network subscription.


ΓòÉΓòÉΓòÉ 3.13.10. ACS0948 ΓòÉΓòÉΓòÉ

ACS0948-W An application tried to obtain an X.25 connection on link name(8) in
slot num(2), but the maximum number of connections was already in use.

where
name(8)         = link name
num(2)          = slot number

Originator: X.25 API

Explanation: Either no more connections are supported by the X.25 API or no
more virtual circuits were available when the connection was attempted.

User Response:

o Increase the number of connections available by running fewer X.25
  applications concurrently.

o If not enough virtual circuits are available, increase the number by changing
  the network subscription and reconfiguring the link.


ΓòÉΓòÉΓòÉ 3.13.11. ACS0949 ΓòÉΓòÉΓòÉ

ACS0949-W The X.25 adapter in slot num(2) cannot be used because some of the
adapter software has been purged for problem determination purposes. Restart
Communications Manager to restore the adapter software.

where
num(2)          = slot number

Originator: X.25 API


ΓòÉΓòÉΓòÉ 3.13.12. ACS0951 ΓòÉΓòÉΓòÉ

ACS0951-W ASCII terminal emulation feature configurations were not upgraded and
are not included in the resulting configuration file.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.13.13. ACS0954 ΓòÉΓòÉΓòÉ

ACS0954-W The maximum number of short sessions for this configuration have been
reached.

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.13.14. ACS0963 ΓòÉΓòÉΓòÉ

ACS0963-W The adapter in slot num(2) is not an IBM X.25 Interface
Co-Processor/2 adapter and is not supported for the X.25 API.

where
num(2)          = slot number

Originator: Communications Manager Kernel

User Response: Ensure that an IBM Interface Co-Processor/2 is in the slot
indicated by the Communications Manager X.25 adapter profile configuration.


ΓòÉΓòÉΓòÉ 3.13.15. ACS0964 ΓòÉΓòÉΓòÉ

ACS0964-E The X.25 API could not be started for the X.25 adapter in slot num(2)
because the adapter is set for local operation instead of Remote operation.

where
num(2)          = slot number

Originator: Communications Manager Kernel

User Response: Select Communications Manager Setup from the Communications
Manager/2 folder and reconfigure the X.25 adapter to operate in Remote mode.
Restart your system and retry the operation.


ΓòÉΓòÉΓòÉ 3.13.16. ACS0965 ΓòÉΓòÉΓòÉ

ACS0965-E The X.25 API could not be started for the X.25 adapter in slot num(2)
because the adapter is set for data terminal equipment (DTE) operation instead
of data circuit-terminating equipment (DCE) operation.

where
num(2)          = slot number

Originator: Communications Manager Kernel

User Response: Select Communications Manager Setup from the Communications
Manager/2 folder and reconfigure the specified X.25 adapter to operate in data
circuit-terminating equipment (DCE) mode.  Restart the system and retry the
operation.


ΓòÉΓòÉΓòÉ 3.13.17. ACS0966 ΓòÉΓòÉΓòÉ

ACS0966-E One or more X.25 adapters did not start because an unexpected return
code was received from the X.25 device driver. Check the system error log for
additional information.

Originator: Communications Manager Kernel

Explanation: The X.25 Realtime Interface Co-Processor Adapter installation
requires that you copy two files from the adapter reference diskette to the
CMLIB directory.  One is the device driver and the other contains the adapter
microcode which is downloaded to the adapter during Communications Manager
startup.  If either of these files are missing, Communications Manager cannot
start the X.25 adapters.

User Response:

o Refer to the documentation that came with the X.25 adapter and ensure that
  you copied the required files to the CMLIB directory.

o Ensure that the device driver is listed in a DEVICE= statement in the
  CONFIG.SYS file.

o Run diagnostics on the X.25 adapter and replace or repair the adapters.

o Retry the operation.

o If the problem persists, reinstall Communications Manager by selecting
  Communications Manager Setup from the Communications Manager/2 folder to
  access installation.  Specify the name of the configuration that you want to
  install or create a new configuration to be installed. Retry the operation
  after installation is complete.


ΓòÉΓòÉΓòÉ 3.13.18. ACS0967 ΓòÉΓòÉΓòÉ

ACS0967-E Communications Manager could not find a critical system file
(ICARICDL.DLL) required to start the X.25 API.  Reinstall Communications
Manager and retry the operation.

Originator: Communications Manager Kernel

User Response: Access installation by selecting Communications Manager Setup
from the Communications Manager/2 folder.  Installation can be performed using
an existing configuration, or a new configuration can be created and installed.


ΓòÉΓòÉΓòÉ 3.13.19. ACS0968 ΓòÉΓòÉΓòÉ

ACS0968-E The X.25 API could not be started because an error was detected while
Communications Manager was attempting to start the X.25 device driver.

Originator: Communications Manager Kernel

User Response: Check the message log for additional information. If no other
related messages exist, reinstall your configuration. Select Communications
Manager Setup from the Communications Manager/2 folder. Installation can be
performed using an existing configuration or a new configuration can be created
for installation. The installation process will make the necessary file
modifications to your system.


ΓòÉΓòÉΓòÉ 3.13.20. ACS0969 ΓòÉΓòÉΓòÉ

ACS0969-E The SRPI API could not be initialized because of a software error.
The error type is rc(4), the subtype is rc(8), and the return code is rc(4).
Retry the operation.

where
rc(4)           = major error code
rc(8)           = minor error code
rc(4)           = return code

Originator: Communications Manager Kernel

User Response:

o If the problem persists, access installation by selecting Communications
  Manager Setup from the Communications Manager/2 folder.  Specify the name of
  a configuration that you want installed or create a new configuration to be
  installed.

o Check the system error log for additional information.

o Refer to the Problem Determination Guide for information on interpreting the
  error log data.


ΓòÉΓòÉΓòÉ 3.13.21. ACS0970 ΓòÉΓòÉΓòÉ

ACS0970-E The X.25 API could not be started because the X.25 device driver is
not installed.  The X.25 device driver must be configured in the CONFIG.SYS
file.

Originator: Communications Manager Kernel

User Response:

o If you want to use the X.25 application programming interface (API), update
  the CONFIG.SYS file to install the X.25 device driver (ICARICIO.SYS).  Then
  restart your system.

o If you do not want to use the X.25 API, change Communications Manager
  configuration so it does not load X.25 API support.


ΓòÉΓòÉΓòÉ 3.13.22. ACS0971 ΓòÉΓòÉΓòÉ

ACS0971-E A power-on self test (POST) error occurred on the X.25 adapter in
slot num(2).  Check the system error log for secondary status information.

where
num(2)          = slot number

Originator: Communications Manager Kernel

Explanation: The specified adapter cannot be used for communications. The
possible cause for a POST error is an adapter malfunction.

User Response: Run diagnostics and replace or repair the specified adapter.
Retry the operation.


ΓòÉΓòÉΓòÉ 3.13.23. ACS0972 ΓòÉΓòÉΓòÉ

ACS0972-E A power-on self test (POST) error occurred on the X.25 adapter in
slot num(2).

where
num(2)          = slot number

Originator: Communications Manager Kernel

Explanation: The specified adapter cannot be used for communications. The
possible cause for a POST error is an adapter malfunction.

User Response: Run diagnostics and replace or repair the specified adapter.
Retry the operation. If the problem persists, refer to the Problem
Determination Guide for additional information.


ΓòÉΓòÉΓòÉ 3.13.24. ACS0973 ΓòÉΓòÉΓòÉ

ACS0973-I APPC did not find any active gateway sessions in the system.

Originator: Subsystem Management


ΓòÉΓòÉΓòÉ 3.13.25. ACS0977 ΓòÉΓòÉΓòÉ

ACS0977-E The X.25 API could not be started because no X.25 adapters were found
or the X.25 adapters could not be successfully started.

Originator: Communications Manager Kernel

Explanation: Likely causes of the error are:

o No X.25 adapters were installed.

o The X.25 adapters are malfunctioning.

o The X.25 device driver (ICARICIO.SYS) is not installed.

o A software failure occurred.

User Response: Do one of the following:

o If you want to use the X.25 API, check the message log for additional
  information.  Install X.25 adapters, run adapter diagnostics, and update the
  CONFIG.SYS file.

o If you do not want to use the X.25 API, change the configuration so that X.25
  API support is not loaded.


ΓòÉΓòÉΓòÉ 3.13.26. ACS0989 ΓòÉΓòÉΓòÉ

ACS0989-Q Are you sure you want to stop Communications Manager and stop all
communications abnormally?

Originator: Communications Manager Kernel

Explanation: You selected Stop Communications Abnormally from the
Communications Manager/2 folder or issued a CMSTOP request with an abnormal
parameter at an OS/2 command prompt.

User Response:

o Select Yes to immediately stop all communications. When all communications
  have stopped, Communications Manager ends and message ACS0143 (All
  Communications Manager services have ended successfully.) is displayed.

o Select No to remove this message and return to the Communications Manager/2
  folder or the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.13.27. ACS0990 ΓòÉΓòÉΓòÉ

ACS0990-Q Are you sure you want to stop Communications Manager when all
communication requests are complete?

Originator: Communications Manager Kernel

Explanation: You selected Stop Communications Normally from the Communications
Manager/2 folder or issued a CMSTOP request at an OS/2 command prompt.

User Response:

o Select Yes to stop all communications.  When all communications have stopped,
  Communications Manager ends and message ACS0143 (All Communications Manager
  services have ended successfully.) is displayed.

o Select No to remove this message and return to the Communications Manager/2
  folder or to the OS/2 command prompt.


ΓòÉΓòÉΓòÉ 3.13.28. ACS1016 ΓòÉΓòÉΓòÉ

ACS1016-E name(1) already exists as the short session or long session name of
another session.  Specify a different session name.

where
name(1)         = short session name

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.13.29. ACS1017 ΓòÉΓòÉΓòÉ

ACS1017-E The specified LU local address address(2) already exists.  Specify a
different address.

where
address(2)      = LU local NAU address

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.13.30. ACS1049 ΓòÉΓòÉΓòÉ

ACS1049-I Twinaxial support is initializing.

Originator: Twinaxial Data Link Control


ΓòÉΓòÉΓòÉ 3.14. ACS1050 through ACS1161 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.14.1. ACS1050 ΓòÉΓòÉΓòÉ

ACS1050-I Twinaxial support initialized successfully.

Originator: Twinaxial Data Link Control


ΓòÉΓòÉΓòÉ 3.14.2. ACS1051 ΓòÉΓòÉΓòÉ

ACS1051-W Twinaxial support was not initialized because the Twinaxial adapter
was not found or is not functioning correctly.

Originator: Twinaxial Data Link Control

Explanation: Likely causes of the error are:

o The adapter card is not the correct one for your workstation.

o The adapter card malfunctioned.

o The adapter card is not installed.

User Response: Install or replace the adapter card. If the problem persists, or
if you do not want Twinaxial support, remove Twinaxial Data Link Control (DLC)
from the configuration file.


ΓòÉΓòÉΓòÉ 3.14.3. ACS1052 ΓòÉΓòÉΓòÉ

ACS1052-W Twinaxial support was not initialized.  The Twinaxial support was not
found at I/O port X'2nnA' or it is not functioning properly.

where
nn              = part of adaptor port address

Originator: Twinaxial Data Link Control

Explanation: Likely causes of the error are:

o The I/O port address is not correct.

o The adapter malfunctioned.

o The adapter is not installed.

User Response: Do the following: 1.  Run Diagnostics. 2.  Check the CONFIG.SYS
file and remove the device driver if it is no longer needed. 3.  Check the port
address.  If the address is correct, replace the adapter with switch settings
according to hardware specifications.


ΓòÉΓòÉΓòÉ 3.14.4. ACS1053 ΓòÉΓòÉΓòÉ

ACS1053-W Twinaxial support was not initialized because of a hardware
diagnostic failure.  The twinaxial adapter was found, but it is not functioning
correctly. Contact your service coordinator to replace or service the adapter.

Originator: Twinaxial Data Link Control


ΓòÉΓòÉΓòÉ 3.14.5. ACS1055 ΓòÉΓòÉΓòÉ

ACS1055-I Accessing Twinaxial adapter.  Please wait.

Originator: Twinaxial Data Link Control


ΓòÉΓòÉΓòÉ 3.14.6. ACS1056 ΓòÉΓòÉΓòÉ

ACS1056-W Twinaxial support was not initialized because a critical adapter file
was missing or damaged. Reinstall Communications Manager.

Originator: Twinaxial Data Link Control


ΓòÉΓòÉΓòÉ 3.14.7. ACS1057 ΓòÉΓòÉΓòÉ

ACS1057-W Twinaxial support was not initialized because interrupt level num(1)
is already in use. Select another hardware interrupt level in the Specify
Twinaxial Adapter Setup menu and retry the operation.

where
num(1)          = interrupt level number

Originator: Twinaxial Data Link Control


ΓòÉΓòÉΓòÉ 3.14.8. ACS1058 ΓòÉΓòÉΓòÉ

ACS1058-W Twinaxial support did not initialize because an available shared RAM
location address could not be found.  Select a specific shared random access
memory (RAM) location address in the Twinaxial adapter setup that does not
conflict with any other adapter.

Originator: Twinaxial Data Link Control

Explanation: You selected to use the first available address for the shared RAM
location, but an available address could not be found.

User Response: Assign one of the following specific shared RAM addresses: AC000
BC000 CC000 DC000 EC000


ΓòÉΓòÉΓòÉ 3.14.9. ACS1091 ΓòÉΓòÉΓòÉ

ACS1091-E The X.25 physical link name(8) could not be connected.

where
name(8)         = X.25 physical link name

Originator: Subsystem Management

Explanation: There was a problem with the X.25 subsystem that prevented the
physical link from being connected.

User Response:

o Refresh the window and check the status of the link.

o Message ACS3356 is logged with this message.  Check the system error log for
  related error log entries.

o Check the FFST/2 message log for possible related messages.


ΓòÉΓòÉΓòÉ 3.14.10. ACS1096 ΓòÉΓòÉΓòÉ

ACS1096-E The workstation IDs (I1, #D, #P, T1, T2, T3, T4) are reserved for
System/36.  Specify a new workstation ID.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.14.11. ACS1119 ΓòÉΓòÉΓòÉ

ACS1119-E A help processing error was detected.

Originator: Converged Emulator

Explanation: An error occurred during processing of the emulator help facility.

User Response: Retry the operation. If the problem persists, note the time,
date, and message number.  Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.14.12. ACS1120 ΓòÉΓòÉΓòÉ

ACS1120-E Help is not available for this application.

Originator: Converged Emulator

Explanation: The dynamic link library (DLL) containing the help information was
not found.

User Response: Reinstall Communications Manager to restore the help
information. Refer to the Workstation Installation Guide for detailed
instructions. If the problem persists, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.14.13. ACS1122 ΓòÉΓòÉΓòÉ

ACS1122-E ALERT: The local X.25 adapter in slot num(2) received a QLLC command
or response that is not supported or is not valid.  Permanent virtual circuit
num(4) is no longer active.  The command or response originated at the remote
data terminal equipment (DTE).

where
num(2)          = slot number
num(4)          = Permanent Virtual Circuit number

Originator: X.25 Data Link Control

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.14. ACS1123 ΓòÉΓòÉΓòÉ

ACS1123-E ALERT: The local X.25 adapter in slot num(2) received a qualified
logical link control (QLLC) command or response that is unsupported or is not
valid. The switched virtual circuit for remote address address(15) is no longer
active.

where
num(2)          = slot number
address(15)     = Switched Virtual Circuit remote address

Originator: X.25 Data Link Control

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.15. ACS1124 ΓòÉΓòÉΓòÉ

ACS1124-E ALERT: A qualified logical link control (QLLC) communications
protocol error occurred on permanent virtual circuit num(4) of the local X.25
adapter in slot num(2). The virtual circuit may no longer be active.

where
num(4)          = Permanent Virtual Circuit number
num(2)          = slot number

Originator: X.25 Data Link Control

Explanation: The remote DTE generated a protocol error.  Depending on the
severity of the error, a permanent virtual circuit (PVC) is now reset. An alert
is forwarded only if the virtual circuit is no longer active.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.16. ACS1125 ΓòÉΓòÉΓòÉ

ACS1125-E ALERT: A qualified logical link control (QLLC) communications
protocol error occurred on the switched virtual circuit for remote address
address(15) of the local X.25 adapter in slot num(2). The virtual circuit may
no longer be active.

where
address(15)     = Switched Virtual Circuit remote address
num(2)          = slot number

Originator: X.25 Data Link Control

Explanation: The remote DTE generated a protocol error.  Depending on the
severity of the error, a switched virtual circuit (SVC) is now disconnected. An
alert is forwarded only if the virtual circuit is no longer active.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.17. ACS1126 ΓòÉΓòÉΓòÉ

ACS1126-E ALERT: The local X.25 adapter in slot num(2) received a qualified
logical link control (QLLC) frame reject response. Permanent virtual circuit
num(4) is no longer active.

where
num(2)          = slot number
num(4)          = Permanent Virtual Circuit number

Originator: X.25 Data Link Control

Explanation: The QLLC frame reject response (QFRMR) originated at the remote
DTE.  The alert ID provides a more specific indication as to why the QFRMR was
generated:

o 3DA4F8CD The local node sent to the remote DTE an invalid or unsupported
  command

o 8BC327F3 No reason given by remote DTE.

o 9C064C98 Either the local node or the X.25 network sent a command to the
  remote DTE that should not have included an information field (I-field).

o D82E7FD3 The local node sent to the remote DTE a command or data with an
  information field (I-field) that was too large.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.18. ACS1127 ΓòÉΓòÉΓòÉ

ACS1127-E ALERT: The local X.25 adapter in slot num(2) received a qualified
logical link control (QLLC) frame reject response. The switched virtual circuit
for remote address address(15) is no longer active.

where
num(2)          = slot number
address(15)     = Switched Virtual Circuit remote address

Originator: X.25 Data Link Control

Explanation: The QLLC frame reject response (QFRMR) originated at the remote
DTE.  The alert ID provides a more specific indication as to why the QFRMR was
generated:

o 3DA4F8CD The local node sent to the remote DTE an invalid or unsupported
  command

o 8BC327F3 No reason given by remote DTE.

o 9C064C98 Either the local node or the X.25 network sent a command to the
  remote DTE that should not have included an information field (I-field).

o D82E7FD3 The local node sent to the remote DTE a command or data with an
  information field (I-field) that was too large.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.19. ACS1128 ΓòÉΓòÉΓòÉ

ACS1128-E ALERT: The local X.25 data link control software (DLC) detected an
internal error and stopped.

Originator: X.25 Data Link Control

Explanation: All switched virtual circuits (SVCs) have been disconnected and
all permanent virtual circuits (PVCs) are inoperative.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Also, ensure the local X.25 configuration matches the X.25 network
  subscription.  Retry the operation you were attempting when the problem
  occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.20. ACS1129 ΓòÉΓòÉΓòÉ

ACS1129-E ALERT: The local X.25 adapter in slot num(2) received an improperly
formatted qualified logical link control (QLLC) response.  Permanent virtual
circuit num(4) is no longer active.

where
num(2)          = slot number
num(4)          = Permanent Virtual Circuit number

Originator: X.25 Data Link Control

Explanation: A problem in either the remote DTE or the X.25 network caused an
improperly formatted Qualified Logical Link Control (QLLC) response to be sent
to the local X.25 node with an information field (I-field). The response should
not have included an I-field.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.21. ACS1130 ΓòÉΓòÉΓòÉ

ACS1130-E ALERT: The local X.25 adapter in slot num(2) received an improperly
formatted qualified logical link control (QLLC) response.  The switched virtual
circuit for remote address name(15) is no longer active.

where
num(2)          = slot number
name(15)        = Switched Virtual Circuit remote address

Originator: X.25 Data Link Control

Explanation: A problem in either the remote DTE or the X.25 network caused an
improperly formatted Qualified Logical Link Control (QLLC) response to be sent
to the local X.25 node with an information field (I-field). The response should
not have included an I-field.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Review the remote node's message and error log for
entries that might provide further detail. Ensure that the remote X.25
configuration matches the physical configuration of the system (adapters,
links, modems, and cables) and the X.25 network subscription.  Especially,
review the X.25 link configuration.  Further, ensure that the remote X.25
configuration is compatible with the local node's X.25 configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, restore the configuration file from your backup
  copy.  Retry the operation you were attempting when the problem occurred. If
  the problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.22. ACS1131 ΓòÉΓòÉΓòÉ

ACS1131-E ALERT: The local X.25 data link control (DLC) sent a qualified
logical link (QLLC) command the maximum number of times and received no
response.  Permanent virtual circuit num(4) of the X.25 adapter in slot num(2)
is no longer active.

where
num(4)          = Permanent Virtual Circuit number
num(2)          = slot number

Originator: X.25 Data Link Control

Explanation: The local X.25 DLC has retried a Qualified Logical Link Control
(QLLC) command the maximum number of times without receiving a response from
the remote DTE.  The configured retry and time-out counts are defaulted high
enough to account for normal network transmission difficulties.

User Response: Review the formatted alert for more information and locate the
remote DTE.  Ensure that the remote DTE is powered on.  Check and secure all
cable connections between the remote adapter and the X.25 network.  Ensure that
all X.25 applications are active on the remote node.

o If none of these conditions apply, review the remote node's message and error
  log for entries that might provide further detail. Ensure that the remote
  X.25 configuration is compatible with the local node's X.25 configuration.
  Especially, review the retry count and the time-out count in the remote DTE
  X.25 link configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.23. ACS1132 ΓòÉΓòÉΓòÉ

ACS1132-E ALERT: The local X.25 data link control (DLC) sent a qualified
logical link (QLLC) command the maximum number of times and received no
response.  The switched virtual circuit address address(15) of the X.25 adapter
in slot number num(2) is no longer active.

where
address(15)     = Switch Virtual Circuit remote address
num(2)          = slot number

Originator: X.25 Data Link Control

Explanation: The local X.25 DLC has retried a Qualified Logical Link Control
(QLLC) command the maximum number of times without receiving a response from
the remote DTE.  The configured retry and time-out counts are defaulted high
enough to account for normal network transmission difficulties.

User Response: Review the formatted alert for more information and locate the
remote DTE.  Ensure that the remote DTE is powered on.  Check and secure all
cable connections between the remote adapter and the X.25 network.  Ensure that
all X.25 applications are active on the remote node.

o If none of these conditions apply, review the remote node's message and error
  log for entries that might provide further detail. Ensure that the remote
  X.25 configuration is compatible with the local node's X.25 configuration.
  Especially, review the retry count and the time-out count in the remote DTE
  X.25 link configuration.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.24. ACS1133 ΓòÉΓòÉΓòÉ

ACS1133-E ALERT: The X.25 data link control (DLC) has disconnected or reset all
virtual circuits due to a lack of operating system resources at the local node.

Originator: X.25 Data Link Control

Explanation: X.25 DLC received an error return code from the X.25 subsystem
because the X.25 subsystem was unable to access the network, or OS/2 was unable
to create a thread or was unable to allocate random access memory (RAM) as
requested by the local X.25 DLC.

User Response: Make sure the X.25 adapter and cables are connected properly.
You can also use Subsystem Management to query the status of X.25 connections.
If the error occurs intermittently while many applications are running
concurrently, the system may be running out of resources. For this condition,
check the CONFIG.SYS file to verify that the value specified in the THREADS=
statement is sufficient for the amount of activity required.  If necessary,
increase this value.  Also, ensure that the MEMMAN parameter in the local
CONFIG.SYS file is set to SWAP, MOVE.  After any changes, restart your computer
and retry the operation you were attempting when the problem occurred.

o If the problem persists, free more OS/2 resources by ending any unnecessary
  active programs, or add additional RAM to the local workstation.  Often, this
  condition occurs when other active programs consume RAM or system semaphores
  required by local X.25 software.

o If the problem persists, ensure that your CONFIG.SYS file contains the
  appropriate DEVICE= statements which load the X.25 device drivers, or
  reinstall the X.25 software.  Restart your computer and retry the operation
  you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.25. ACS1134 ΓòÉΓòÉΓòÉ

ACS1134-E ALERT: Permanent virtual circuit num(4) of the local X.25 adapter in
slot num(2) was reset by the remote data terminal equipment (DTE). The virtual
circuit is no longer active.

where
num(4)          = Permanent Virtual Circuit number
num(2)          = slot number

Originator: X.25 Data Link Control

Explanation: An X.25 virtual circuit is no longer active because the remote DTE
detected a problem.

User Response: Review the formatted alert; especially review the cause code and
diagnostic code.  Refer to the X.25/SNA architecture for detailed
interpretation of these codes.

o Review the formatted alert and locate the remote DTE.  Review the remote
  node's message and error log for entries that might provide further detail.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.26. ACS1135 ΓòÉΓòÉΓòÉ

ACS1135-E ALERT: The remote data terminal equipment (DTE) either cleared or
reset the switched virtual circuit for remote address address(15) on the X.25
adapter in slot num(2). The virtual circuit is no longer active.

where
address(15)     = Switched Virtual Circuit remote address
num(2)          = slot number

Originator: X.25 Data Link Control

Explanation: An X.25 virtual circuit is no longer active because the remote DTE
detected a problem.

User Response: Review the formatted alert; especially review the cause code and
diagnostic code.  Refer to the X.25/SNA architecture for detailed
interpretation of these codes.

o Review the formatted alert and locate the remote DTE.  Review the remote
  node's message and error log for entries that might provide further detail.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the entry with the problem ID, date and time closest to the recorded
values from this message entry and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.14.27. ACS1138 ΓòÉΓòÉΓòÉ

ACS1138-W An emulator request to bypass the AS/400 logon screen was rejected.

Originator: 5250 Work Station Feature

Explanation: The configuration for the local 5250 emulator specified bypassing
the AS/400 logon screen.  When the emulator session was initiated, the request
was rejected.  The logon screen is displayed.

User Response: Check the AS/400 system for problem determination information
identifying the cause.  QRMTSIGN system value may have been incorrectly set.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data may be logged in the Additional Data section of the
  associated error log entry:

   - Offset/Length/Field Description

   - 00/02/ Internal return code

   - 02/02/ Reserved

   - 04/02/ Location identifier

   - 06/02/ Reserved


ΓòÉΓòÉΓòÉ 3.14.28. ACS1147 ΓòÉΓòÉΓòÉ

ACS1147-E The specified local network addressable unit (NAU) address is the
same as the local NAU address in SNA LUA definition name(8).  Specify a unique
Local NAU address.

where
name(8)         = SNA LUA definition name

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.14.29. ACS1156 ΓòÉΓòÉΓòÉ

ACS1156-W Either the Synchronous Data Link Control (SDLC) adapter associated
with 5250 emulation has Free Unused Links set to Yes, or the logical link
associated with 5250 emulation has its Limited Resource parameter set to Yes.
These parameters cannot be set to Yes if the AS/400 is to be used with 5250
emulation.

Originator: Configuration Services - Verify

Explanation: Either the Free Unused Links parameter on the SDLC adapter profile
is not correctly set or the Limited Resource parameter for the link is not
correctly set.  The link cannot be freed or limited if it is used by the AS/400
system with 5250 emulation.

User Response: To change the SDLC adapter profile so that the Free Unused Links
field is set to No:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select DLC - SDLC then select Configure in the Communications Manager Profile
  List window.

To change the Limited Resource parameter in the logical link definition:

o If the configuration was only changed with Communications Manager Setup
  windows, then no changes need to be made to the Limited Resource parameter.

o If the Node Definitions File (.NDF) was created manually, edit your
  <configuration name>.NDF file, changing the Limited Resource parameter in the
  logical link definition to either NO or USE_ADAPTER_DEFINITION. Run CMVERIFY
  to Verify the changed configuration.

o If the configuration was created with CID, edit your response file, changing
  the Limited Resource parameter in the logical link definition to either No or
  Use Adapter Definition.  Run your altered response file through CID to create
  the new configuration files.


ΓòÉΓòÉΓòÉ 3.14.30. ACS1161 ΓòÉΓòÉΓòÉ

ACS1161-I FMA Support Device Driver is already installed.

Originator: FMA Device Driver


ΓòÉΓòÉΓòÉ 3.15. ACS1162 through ACS1237 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.15.1. ACS1162 ΓòÉΓòÉΓòÉ

ACS1162-I FMA Support Device Driver is not installed.

Originator: FMA Device Driver


ΓòÉΓòÉΓòÉ 3.15.2. ACS1163 ΓòÉΓòÉΓòÉ

ACS1163-I FMA Support Device Driver is assigned to drive d::.

where
d:              = target drive

Originator: FMA Device Driver


ΓòÉΓòÉΓòÉ 3.15.3. ACS1164 ΓòÉΓòÉΓòÉ

ACS1164-I FMA Support Device Driver is not installed.

Originator: FMA Device Driver


ΓòÉΓòÉΓòÉ 3.15.4. ACS1165 ΓòÉΓòÉΓòÉ

ACS1165-I Assigned drive is d::

where
d:              = target drive

Originator: FMA Device Driver


ΓòÉΓòÉΓòÉ 3.15.5. ACS1170 ΓòÉΓòÉΓòÉ

ACS1170-W You are attempting to paste text into a protected field that is
different from the existing text in the protected field. Or you are attempting
to paste single-byte character set (SBCS) into double-byte character set (DBCS)
fields or DBSC text into SBCS fields.

Originator: DBCS Emulation

Explanation: One of the following conditions caused this error:

o The text being pasted is not the same as the text in the protected field.
  The text in the protected field will not be changed.

o SBCS characters are being pasted over DBCS characters.

o DBCS characters are being pasted over SBCS characters.

User Response:

o Select Cancel to end the operation.

o Select Continue to complete the paste operation.  Text that is not the same
  as the protected field will be ignored.  If a character set error is
  detected, the left portion of the line will be filled with spaces.


ΓòÉΓòÉΓòÉ 3.15.6. ACS1172 ΓòÉΓòÉΓòÉ

ACS1172-E The 3270 emulation keyboard profiles in this configuration file have
not been upgraded.

Originator: DBCS Services

Explanation: The 3270 terminal emulation keyboard profiles were not copied from
the previous configuration into this configuration during upgrade.

User Response: Copy all 3270 terminal emulation keyboard profiles from your
previous configuration into this configuration.


ΓòÉΓòÉΓòÉ 3.15.7. ACS1205 ΓòÉΓòÉΓòÉ

ACS1205-E IBM carrier sense multiple access with collision (CSMA/CD) LAN access
was denied for adapter num(2) because of a Remove command.

where
num(2)          = adapter number

Originator: LAN

User Response: 1.  Stop and restart Communications Manager. 2.  Retry the
operation. If the problem persists, note the time, date, and message number;
then contact your LAN personnel. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.15.8. ACS1206 ΓòÉΓòÉΓòÉ

ACS1206-E Adapter num(2) cannot access the carrier sense multiple access with
collision detection (CSMA/CD) Network because a type type(2) error occurred
while the adapter was trying to access the network.

where
num(2)          = adapter number
type(2)         = alert type

Originator: LAN

User Response: 1.  Stop Communications Manager. 2.  Check and secure all cable
connections between the adapter and the CSMA/CD LAN. 3.  Retry the operation.


ΓòÉΓòÉΓòÉ 3.15.9. ACS1207 ΓòÉΓòÉΓòÉ

ACS1207-E A hardware error occurred on carrier sense multiple access with
collision detection Network adapter num(2).

where
num(2)          = adapter number

Originator: LAN

User Response: 1.  Stop Communications Manager. 2.  Note the time, date, and
message number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.15.10. ACS1208 ΓòÉΓòÉΓòÉ

ACS1208-E LAN support has stopped for CSMA/CD Network adapter num(2) because of
a Remove command.

where
num(2)          = adapter number

Originator: LAN

User Response: 1.  Stop and restart Communications Manager. 2.  Retry the
operation. If the problem persists, note the time, date, and message number;
then contact your LAN personnel. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.15.11. ACS1209 ΓòÉΓòÉΓòÉ

ACS1209-E Verification of configuration name(12) completed without errors, but
some of the SNA resources might not have been dynamically updated.

where
name(12)        = configuration file name

Originator: Configuration Services - Verify

User Response: Check previous messages to determine which resources were not
updated.  Take corrective actions based on those messages; then stop and
restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.15.12. ACS1218 ΓòÉΓòÉΓòÉ

ACS1218-I Configuration name(8) has been upgraded.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.13. ACS1219 ΓòÉΓòÉΓòÉ

ACS1219-E Configuration name(8) cannot be found in the specified directory.
Upgrade did not complete successfully.
Check that the specified configuration file is typed correctly and
the name is located in the specified directory.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.14. ACS1220 ΓòÉΓòÉΓòÉ

ACS1220-E File name(8) is not a valid configuration or the configuration
is damaged.  Upgrade did not complete successfully.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade

User Response: Check that the specified configuration is typed correctly and
that it is a valid configuration name. If the configuration is damaged, use a
backup copy to replace it and retry the operation.


ΓòÉΓòÉΓòÉ 3.15.15. ACS1221 ΓòÉΓòÉΓòÉ

ACS1221-E The version of configuration name(8)
is not supported by this Upgrade function.  Upgrade did not complete
successfully.  The upgrade facility works only on configurations
at the EE 1.3, Extended Services, or CM/2 version levels.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.16. ACS1222 ΓòÉΓòÉΓòÉ

ACS1222-E The configuration name(8) is already in use by another process.
Upgrade did not complete successfully.
Try the operation again when it is no longer being used by another
process.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.17. ACS1223 ΓòÉΓòÉΓòÉ

ACS1223-E An unexpected system error occurred during upgrade.  The
configuration did not upgrade successfully.  Check the upgrade
log for a more detailed description of the error.

Originator: Configuration Services - Upgrade

User Response:

o Be sure that the specified configuration is typed correctly and that it is a
  valid name.

o If the configuration file is damaged, use a backup copy to replace it.  Then
  retry the operation.


ΓòÉΓòÉΓòÉ 3.15.18. ACS1224 ΓòÉΓòÉΓòÉ

ACS1224-I The correct syntax for CMUPGRAD function is:
CMUPGRAD <cfgname> [/w]
Required parameter:
<cfgname> - name of the Communications Manager configuration to be

       upgraded.  "cfgname" may be fully-qualified, or have

      relative or no path information included.

Optional parameter:
/w <workstation LAN requester> - Will upgrade configuration for use on

                 a LAN redirected workstation.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.19. ACS1225 ΓòÉΓòÉΓòÉ

ACS1225-E The APPN LU alias in the 5250 emulation was not specified.  This is a
required parameter.  Specify an existing APPN LU alias in the 5250 emulation
profile.

Originator: Configuration Services - Verify


ΓòÉΓòÉΓòÉ 3.15.20. ACS1226 ΓòÉΓòÉΓòÉ

ACS1226-E The APPC mode name name(8) specified in 5250 session does not exist.
Either configure the APPC mode name or change the mode name in the 5250 session
profile configuration.

where
name(8)         = APPC mode name

Originator: Configuration Services - Verify


ΓòÉΓòÉΓòÉ 3.15.21. ACS1228 ΓòÉΓòÉΓòÉ

ACS1228-E Configuration cfg_name is already at the current version level.
The upgrade facility works only on configurations at the EE 1.3,
Extended Services, or Communications Manager/2 1.0 levels.

where
cfg_name        = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.22. ACS1229 ΓòÉΓòÉΓòÉ

ACS1229-I The specified configuration name is too long.
The maximum length of the configuration name is 8 characters.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.23. ACS1230 ΓòÉΓòÉΓòÉ

ACS1230-E Configuration name(8) must be verified before it can be upgraded. The
configuration was not upgraded.

where
name(8)         = configuration file name

Originator: Configuration Services - Upgrade

Explanation: The named configuration must be verified before it can be
upgraded.

User Response: Using the system that the configuration was created on, correct
the configuration and verify it.  Then retry the upgrade.


ΓòÉΓòÉΓòÉ 3.15.24. ACS1231 ΓòÉΓòÉΓòÉ

ACS1231-E The link to remote address address(12) could not be established.  The
XID negotiation between the local node and the partner node was not successful.

where
address(12)     = destination address

Originator: SNA Communications Services (APPC)

Explanation: Errors detected during the XID negotiation are preventing the link
between the local node and the partner node from being established.  The remote
address identifies the partner node.

User Response: One of the following reasons prevented the link from being
established:

o The XID negotiation between the local node and the remote node was not
  successful. Check your configuration for errors, then retry.

o The remote node is not responding because a hardware error occurred or the
  workstation is down.

o Either the local node or the remote node is out of link stations.


ΓòÉΓòÉΓòÉ 3.15.25. ACS1232 ΓòÉΓòÉΓòÉ

ACS1232-E The configuration file was not upgraded successfully because of
an error found during verification.  Check the upgrade log for
additional information.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.26. ACS1233 ΓòÉΓòÉΓòÉ

ACS1233-I EE 1.3 or ES 1.0 5250 long session names have been changed to unique
long session names for the converged emulator. The format of the unique name is
<id>#5250, where id is the short id of the 5250 session.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.27. ACS1234 ΓòÉΓòÉΓòÉ

ACS1234-I 5250 color profile names that were duplicates of 3270 color profile
names were changed to the associated 5250 short session IDs during the upgrade
process.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.15.28. ACS1235 ΓòÉΓòÉΓòÉ

ACS1235-E There is not enough space on the disk or diskette to back up your
entire configuration.

Originator: Configuration Services - Upgrade

Explanation: The disk or diskette you are using to back up your configuration
requires more space.

User Response: Delete any unwanted files from the disk or diskette you are
using, and retry the backup.  If you prefer, you can use a different disk or
diskette that has more space.  If you do this, complete the following steps:

o Copy the configuration to a disk or diskette with sufficient space.

o Go to the Open Configuration window, and select the directory and file for
  the configuration you copied.

o Return to the Upgrade Configuration window, and select the backup option.

o Retry the upgrade.


ΓòÉΓòÉΓòÉ 3.15.29. ACS1236 ΓòÉΓòÉΓòÉ

ACS1236-W Any trace or dump settings stored in your configuration file were not
upgraded.

Originator: Configuration Services - Upgrade

Explanation: In EE 1.3 or Extended Services Communications Manager, trace and
dump settings are stored in configuration files. In Communications Manager/2
only one set of the trace and dump settings are stored in ASCRASTD.INI.
Because of the incompatibilities between the two formats, the settings were not
upgraded with your configuration file.

User Response: No user response is required.  Trace and dump settings can be
updated or changed by using the problem determination aids windows in the
Communications Manager/2 folder.  Trace settings can also be updated or changed
by using CMTRACE from the OS/2 command prompt. For more information on trace
and dump services, refer to the Problem Determination Guide.


ΓòÉΓòÉΓòÉ 3.15.30. ACS1237 ΓòÉΓòÉΓòÉ

ACS1237-I Upgrade of configuration name(255) has started.

where
name(255)       = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.16. ACS1238 through ACS1291 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.16.1. ACS1238 ΓòÉΓòÉΓòÉ

ACS1238-I Upgrade of configuration name(255) has ended successfully.

where
name(255)       = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.16.2. ACS1239 ΓòÉΓòÉΓòÉ

ACS1239-I Since verify errors occurred during the upgrade process,
configuration name(8) has been backed up.  The name of the backup configuration
is name(8).

where
name(8)         = source configuration file name
name(8)         = backup configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.16.3. ACS1240 ΓòÉΓòÉΓòÉ

ACS1240-I Upgrade of configuration name(255) has ended with errors. If verify
errors occurred during the upgrade, you can correct the verify errors by going
into CMSETUP. If upgrade errors occurred during the upgrade, you can go to the
upgrade log and correct the problems using the help information for the upgrade
error.

where
name(255)       = configuration file name

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.16.4. ACS1241 ΓòÉΓòÉΓòÉ

ACS1241-E No more free system memory is available.  Upgrade cannot continue.

Originator: Configuration Services - Upgrade

Explanation: Upgrade was not able to allocate sufficient memory to continue.

User Response: If other non-essential processes are running, either stop them,
or wait for them to terminate, then retry Upgrade. If no other non-essential
processes are running, the system may not have sufficient memory installed to
be able to run Upgrade.


ΓòÉΓòÉΓòÉ 3.16.5. ACS1242 ΓòÉΓòÉΓòÉ

ACS1242-E An OS/2 error occurred during the Communications Manager
configuration upgrade process.  Upgrade cannot continue.

Originator: Configuration Services - Upgrade

Explanation: During upgrade processing, a call to an OS/2 routine did not
complete.

User Response: Check for messages in the system error log.


ΓòÉΓòÉΓòÉ 3.16.6. ACS1247 ΓòÉΓòÉΓòÉ

ACS1247-W The password for user ID ID(8) cannot be longer than 10 characters.
APPC conversation security is downgraded to None.  Specify a password using
user profile management (UPM) of 10 characters or less.

where
ID(8)           = user ID

Originator: SNA Communications Services (APPC)

Explanation: When the password is not valid, APPC security is changed to None.
This security level might cause the remote LU to reject the ATTACH request.


ΓòÉΓòÉΓòÉ 3.16.7. ACS1249 ΓòÉΓòÉΓòÉ

ACS1249-E The keyboard remap/view function provided by the keyboard utility is
not installed.
Use Communications Manager Setup to install the keyboard remap function.

Originator: Converged Emulator

Explanation: The required files for the requested keyboard remap/view function
are missing or damaged.

User Response:

o Use Communications Manager Setup to install the keyboard remap function
  before trying the operation again.

   - Start Communications Manager Setup.

   - Select Install additional functions.... from the Options pull-down. The
     Install Additional Functions window appears.

   - Select Keyboard Remap from the function list box, and then select OK.

   - Follow the instructions on the subsequent windows.

If the problem persists after following these instructions, note the time, date
and message number.  Check the error log for additional information.  Then,
contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.16.8. ACS1250 ΓòÉΓòÉΓòÉ

ACS1250-W Coaxial (DFT) emulation cannot be started because 3174 Peer
Communications is using the adapter.  3174 Peer Communications is configured to
use all available adapters.

Originator: Converged Emulator

User Response: If you need a 3270 coaxial (DFT) session, remove at least one of
the 3174 Peer Communications device statements from the CONFIG.SYS file to free
up at least one coaxial (DFT) adapter.  Then restart your system.


ΓòÉΓòÉΓòÉ 3.16.9. ACS1259 ΓòÉΓòÉΓòÉ

ACS1259-W The SNA network definitions could not be found for this
configuration.  This configuration contains features that require SNA data
(5250 sessions, 3270 non-DFT sessions, SRPI non-DFT, or DLC profiles).  Ignore
this message if you do not want to use these features; otherwise, ensure that
the SNA network definitions are configured correctly.

Originator: Configuration Services - Verify

User Response: To ensure that the SNA network definitions are configured
correctly:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select SNA local node characteristics.  Ensure the information is correct.

o Select SNA connections from the Communications Manager Configuration List
  window, and ensure that the connections are configured correctly.

o Return to the Communications Manager Configuration List window and select SNA
  features.  Ensure the SNA feature information is correct.


ΓòÉΓòÉΓòÉ 3.16.10. ACS1263 ΓòÉΓòÉΓòÉ

ACS1263-E 106 Enhanced Keyboard configuration name(8) specified in type(4)
terminal emulation profile name(8) does not exist.

where
name(8)         = keyboard configuration name
type(4)         = "3270/5250" emulation type
name(8)         = long session name

Originator: Configuration Services - Verify

User Response: Either change the 3270 terminal emulation or the 5250 terminal
emulation to specify a valid 106 Enhanced Keyboard profile or create the
missing 106 Enhanced Keyboard profile.  To access the emulator:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu in
  the Communications Manager Configuration Definition window.

o Select 3270 terminal emulation or 5250 emulation and then select Configure in
  the Communications Manager Configuration List window.

o Select Keyboard from the 3270 emulation or 5250 emulation window.


ΓòÉΓòÉΓòÉ 3.16.11. ACS1267 ΓòÉΓòÉΓòÉ

ACS1267-E One or more of the selected services could not be started.

Originator: Communications Manager Kernel

Explanation: One or more of the configured services is not installed on this
system.

User Response: Select Communications Manager Setup from the Communications
Manager/2 folder to access installation. Specify the name of the configuration
with the services you want to install.


ΓòÉΓòÉΓòÉ 3.16.12. ACS1269 ΓòÉΓòÉΓòÉ

ACS1269-I No LU aliases were found which support persistent verification and
have signed-on users.

Originator: Subsystem Management


ΓòÉΓòÉΓòÉ 3.16.13. ACS1271 ΓòÉΓòÉΓòÉ

ACS1271-I No users are signed on to the LU alias name(8).

where
name(8)         = LU alias name

Originator: Subsystem Management

Explanation: This occurs when you view an outdated list of LU aliases with
signed-on users on the Signed-On Users window. It also occurs when you select
Refresh in the Signed-On User Details window and no users are signed on.

User Response: Return to the SNA Subsystem window and select Signed-on Users to
receive an updated list of LU aliases.


ΓòÉΓòÉΓòÉ 3.16.14. ACS1272 ΓòÉΓòÉΓòÉ

ACS1272-W The APPC display buffer limit has been exceeded.  The current
configuration is too large to display the requested information. Subsystem
Management data will be incomplete.  Detailed data may not be accurate.

Originator: Subsystem Management

Explanation: The APPC DISPLAY verb provides a maximum of 64K of information
about the current configuration.  The current configuration requires more than
64K of memory to display the requested information. Subsystem Management will
display as much information as APPC provides.  However, detailed data for LU
6.2 sessions, logical links, and signed-on users may be inaccurate.

o The number of sessions listed for LU 6.2 Sessions will be accurate, but the
  LU 6.2 Sessions Details window may not show data for all of the sessions. For
  example, the number of sessions may be shown as 10, even though only 6
  session IDs are listed in the LU 6.2 Sessions Details window.  Also, session
  details may not indicate an active transaction program conversation when
  there is one.

o For the Logical Link Details window, the Preferred Server field might show
  'No' when it should be 'Yes'.

o For the Signed-On Users window, the Number of Signed-On Users column may show
  a smaller than actual number of user IDs signed on to an LU. This also means
  that not all user IDs may be listed on the corresponding Signed-On User
  Details window.

All other information displayed will be accurate.


ΓòÉΓòÉΓòÉ 3.16.15. ACS1275 ΓòÉΓòÉΓòÉ

ACS1275-E A 3270 coaxial (DFT) session is specified to be auto-loaded but the
session does not exist in the 3270 emulation profile.

Originator: Configuration Services - Verify

User Response: Use Communications Manager Setup to do one of the following:

o Configure a 3270 coaxial (DFT) session.

o Change the Workstation Information so the 3270 coaxial (DFT) session is not
  auto-loaded.


ΓòÉΓòÉΓòÉ 3.16.16. ACS1276 ΓòÉΓòÉΓòÉ

ACS1276-E A 3270 non-coaxial session is configured to be auto-loaded but the
session does not exist in the 3270 emulation profile.

Originator: Configuration Services - Verify

User Response: Use Communications Manager Setup to do one of the following:

o Configure the 3270 non-coaxial session.

o Change the Workstation Information so the 3270 non-coaxial session is not
  auto-loaded.


ΓòÉΓòÉΓòÉ 3.16.17. ACS1278 ΓòÉΓòÉΓòÉ

ACS1278-I TRANS126 The specified workstation file has critical extended
attributes that will not be sent to the host.  Press Ctrl+Break to cancel the
file transfer.  Otherwise, the file transfer will continue.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.16.18. ACS1279 ΓòÉΓòÉΓòÉ

ACS1279-W Verification for configuration name(255) has ended with severe
errors. Verification did not complete.

where
name(255)       = configuration file name

Originator: Configuration Services - Verify

Explanation: During Verify processing one or more calls to DOS or internal
Communications Manager file access routines have failed.

User Response: Note the configuration name and the time that this message was
logged.  Then check the verify log for additional messages. To view the verify
log:

o Open the FFST/2 folder from the Desktop Manager:

o Select Message Log Formatter

o Substituting the disk drive letter of the disk drive that contains the active
  CMLIB directory for <drive>, either:

o Type <drive>:\CMLIB\VERIFY.LOG in the File Name field, or

o Change the formatter directory to <drive>:\CMLIB, then select VERIFY.LOG

o Select Open in the Message Log Formatter Open window.

If no related messages appear in the verify log, then check for additional
messages in the system error log.  From the FFST/2 folder:

o Either select System Error Log from the FFST/2 folder or enter Syslog at the
  OS/2 command prompt.

o Select 1. Display system log file.

o Enter LOG0001.DAT as the log file name, and press Enter.

o Use the Problem Determination Guide along with the logged error information
  to determine the source of the problem.


ΓòÉΓòÉΓòÉ 3.16.19. ACS1280 ΓòÉΓòÉΓòÉ

ACS1280-E One or more of the requested emulator sessions did not start.

Originator: Converged Emulator

Explanation: A bad return code was received from the OS/2 API or the emulator
internal function used in starting the session.

User Response: Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.16.20. ACS1281 ΓòÉΓòÉΓòÉ

ACS1281-E The emulator is ending because of an unrecoverable error. Check the
error log for additional information.

Originator: Converged Emulator

Explanation: The emulator has stopped because of an error.

User Response: Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.16.21. ACS1282 ΓòÉΓòÉΓòÉ

ACS1282-E One or more emulation sessions did not start.  Not enough memory is
available.  Make more memory available by reducing the number of programs
running on your system or by adding memory to your system. Retry the operation.

Originator: Converged Emulator

Explanation: At least one of the requested emulation sessions did not start
because there is not enough memory available.

User Response: End one or more programs not in use to free some memory at the
workstation; then retry the operation. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.16.22. ACS1283 ΓòÉΓòÉΓòÉ

ACS1283-E One or more emulator sessions did not start because not enough
threads are available.  Make more threads available by reducing the number of
programs running on your system or by changing the THREADS parameter in the
CONFIG.SYS file.

Originator: Converged Emulator

Explanation: One or more emulation sessions did not start because of a lack of
available threads.

User Response: Increase the number of threads available in the system by
changing the THREADS parameter in the CONFIG.SYS file. Check the error log for
additional information.


ΓòÉΓòÉΓòÉ 3.16.23. ACS1284 ΓòÉΓòÉΓòÉ

ACS1284-E 5250 emulation did not start because of an unrecoverable error. Check
the error log for additional information.

Originator: Converged Emulator

Explanation: One or more 5250 emulation sessions did not start.

User Response: Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.16.24. ACS1285 ΓòÉΓòÉΓòÉ

ACS1285-E 3270 emulation could not use the 3270 coaxial (DFT) device driver as
specified in the CONFIG.SYS file, or the DFTDD.SYS file is missing or damaged.
Check the message log and the error log for additional information.

Originator: Converged Emulator

Explanation: One or more coaxial (DFT) emulator sessions did not start.

User Response: Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.16.25. ACS1286 ΓòÉΓòÉΓòÉ

ACS1286-E 3270 non-coaxial emulation did not start because of an unrecoverable
error. Check the error log for additional information.

Originator: Converged Emulator

Explanation: One or more emulator sessions did not start.

User Response: Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.16.26. ACS1287 ΓòÉΓòÉΓòÉ

ACS1287-E Sessions configured for print support did not start.  The file
name(12) may be missing or corrupted.  Check the error log for additional
information.

where
name(12)        = host print DLL name

Originator: Converged Emulator

Explanation: One or more emulation sessions configured for print support did
not start.

User Response: Check the error log for additional information.


ΓòÉΓòÉΓòÉ 3.16.27. ACS1288 ΓòÉΓòÉΓòÉ

ACS1288-E One or more emulation sessions did not start because the keyboard
profile name(8) is in use.  Finish configuring the keyboard profile before
attempting to restart the sessions.

where
name(8)         = keyboard profile name

Originator: Converged Emulator

Explanation: You attempted to start an emulation session and the keyboard
profile for that session is in use.  The session did not start.

User Response: Complete the keyboard profile configuration for the requested
session, and retry the operation.


ΓòÉΓòÉΓòÉ 3.16.28. ACS1289 ΓòÉΓòÉΓòÉ

ACS1289-E One or more emulation sessions did not start because the color
profile name(8) is in use.  Finish configuring the color profile before
attempting to restart the sessions.

where
name(8)         = color profile name

Originator: Converged Emulator

Explanation: You attempted to start an emulator session and the color profile
for that session is in use.  The session did not start.

User Response: Complete the color profile configuration for the requested
session, then retry the operation.


ΓòÉΓòÉΓòÉ 3.16.29. ACS1290 ΓòÉΓòÉΓòÉ

ACS1290-E One or more emulator sessions did not start because the configuration
information is in use.  Finish configuring the sessions before attempting to
restart the sessions.

Originator: Converged Emulator

Explanation: You attempted to start an emulator session and the configuration
data for that session is in use.  The session did not start.

User Response: Complete the session configuration and retry the operation.


ΓòÉΓòÉΓòÉ 3.16.30. ACS1291 ΓòÉΓòÉΓòÉ

ACS1291-E The printer information for one or more emulator sessions was not
saved.  Check the error log for additional information.

Originator: Converged Emulator

Explanation: The changes to the printer configuration were not saved.

User Response: Retry the operation. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.17. ACS1292 through ACS1760 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.17.1. ACS1292 ΓòÉΓòÉΓòÉ

ACS1292-E The window information for one or more emulation sessions was not
saved.  Check the error log for additional information.

Originator: Converged Emulator

Explanation: The changes to the session configuration were not saved.

User Response: Retry the operation. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.17.2. ACS1293 ΓòÉΓòÉΓòÉ

ACS1293-E The color profile name(8) was not saved. Check the error log for
additional information.

where
name(8)         = color profile name

Originator: Converged Emulator

Explanation: The changes to your color profile were not saved.

User Response: Retry the operation. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.17.3. ACS1294 ΓòÉΓòÉΓòÉ

ACS1294-E The alarm configuration for one or more sessions was not saved. Check
the error log for additional information.

Originator: Converged Emulator

Explanation: The changes to your alarm configuration were not saved.

User Response: Retry the operation. Check the error log for additional
information.


ΓòÉΓòÉΓòÉ 3.17.4. ACS1326 ΓòÉΓòÉΓòÉ

ACS1326-E The type(8) name entered for type(4) session ID(1) does not match any
type(8) configurations, but does match one type(8) configuration.

where
type(8)         = keyboard type string
type(4)         = "3270/5250" emulator type string
ID(1)           = short session ID
type(8)         = keyboard type string

Originator: Configuration Services - Verify

User Response: Either correct the keyboard profile in the appropriate session,
or create the missing keyboard profile. To gain access to the 3270 emulation or
the 5250 emulation keyboard profile:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select the Options pull-down menu in the Communications Manager Configuration
  Definition window.  Select Configure any profile or feature... from the
  Options pull-down menu.

o Select 3270 emulation or 5250 Emulation and then select Configure... in the
  Communications Manager Profile List window.

o Select Keyboard and then select the File pull-down menu in the 3270 Emulation
  or the 5250 Emulation window.  Then select Open to change the keyboard
  profile.


ΓòÉΓòÉΓòÉ 3.17.5. ACS1330 ΓòÉΓòÉΓòÉ

ACS1330-W The keyboard type you are using is different from the last keyboard
used with this configuration.  As a result, a different keyboard profile
mapping will be used.

Originator: Converged Emulator

Explanation: There are two possible causes:

o The keyboard type for the workstation has been changed.

o A new configuration is being used with a different keyboard type.

User Response: Review the keyboard profile to ensure that it is the mapping you
want to use.  When you change keyboard types, a different keyboard profile
mapping is normally used.


ΓòÉΓòÉΓòÉ 3.17.6. ACS1344 ΓòÉΓòÉΓòÉ

ACS1344-I You have pasted data into the last position of an Auto-Enter field.
This will cause the Enter key to be sent to the host system and the remainder
of your pasted data will be discarded.

Originator: Converged Emulator

User Response:

o Select OK to discard the remainder of the pasted data. The Enter key will be
  sent to the host system.

o Select Cancel to continue pasting.  The Enter key will not be sent to the
  host system when data is placed in the last position of any Auto-Enter field
  for the duration of this paste.


ΓòÉΓòÉΓòÉ 3.17.7. ACS1356 ΓòÉΓòÉΓòÉ

ACS1356-W The emulation window information will not be saved because the
keylock is on.

Originator: Converged Emulator

Explanation: The Desktop SAVE option has been selected, but the keylock is on.

User Response: Turn off the keylock and select the SAVE option again.


ΓòÉΓòÉΓòÉ 3.17.8. ACS1402 ΓòÉΓòÉΓòÉ

ACS1402-E Sessions configured for data confidentiality support did not start.
Name(12) might be missing or corrupted.  Check the error log to determine the
cause.

where
Name(12)        = workstation security services DLL name

Originator: Converged Emulator

Explanation: Likely causes are:

o The data confidentiality support is not installed on the workstation.  This
  support is either the workstation security services program or a user
  supplied program.

o The subdirectory that contains the CSUESAPI.DLL file is not specified in the
  LIBPATH statement in the CONFIG.SYS file.

o The file specified in the message has been corrupted.

User Response:

o Be sure that the work station security services program or a user supplied
  program that provides the data confidentiality support is installed on the
  workstation.

o Be sure that the subdirectory that contains the CSUESAPI.DLL file is
  specified in the LIBPATH statement in the CONFIG.SYS file.

If both of these conditions are true, then the file name specified in the
message is either missing or corrupted.  Reinstall the file.


ΓòÉΓòÉΓòÉ 3.17.9. ACS1414 ΓòÉΓòÉΓòÉ

ACS1414-E The data confidentiality support required for this session was not
loaded.  Name(12) might be missing or corrupted.  Check the error log for
additional information.

where
Name(12)        = workstation security services DLL name

Originator: Converged Emulator

Explanation: Likely causes are:

o The data confidentiality support is not installed on the workstation. This
  support is either the workstation security services program or a user
  supplied program.

o The subdirectory that contains the CSUESAPI.DLL file is not specified in the
  LIBPATH statement in the CONFIG.SYS file.

o The file specified in the message has been corrupted.

User Response:

o Be sure that the work station security services program or a user supplied
  program that provides the data confidentiality support is installed on the
  workstation.

o Be sure that the subdirectory that contains the CSUESAPI.DLL file is
  specified in the LIBPATH statement in the CONFIG.SYS file.

If both of these conditions are true, then the file name specified in the
message is either missing or corrupted.  Reinstall the file.


ΓòÉΓòÉΓòÉ 3.17.10. ACS1440 ΓòÉΓòÉΓòÉ

ACS1440-Q One of the source or target states is not remappable. Do you want to
continue?

Originator: Keyboard Remap Utility

User Response:

o Select Yes to copy, move, or swap the remappable states.

o Select No to end the operation.


ΓòÉΓòÉΓòÉ 3.17.11. ACS1441 ΓòÉΓòÉΓòÉ

ACS1441-E The source or target state definition of this key cannot be remapped.
It either contains a function that cannot be remapped, or a character,
function, or string cannot be found.

Originator: Keyboard Remap Utility

User Response: Stop the remapping process, edit the definition, and then try
the operation again.


ΓòÉΓòÉΓòÉ 3.17.12. ACS1442 ΓòÉΓòÉΓòÉ

ACS1442-W The string is not valid. Modify the cursored state of the open key
and try the operation again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.17.13. ACS1443 ΓòÉΓòÉΓòÉ

ACS1443-W The search item is not a valid character.  Make sure functions are
enclosed in brackets and strings are in double quotes.
When you type a definition:
- Type characters without delimiters
- Enclose functions in square brackets; for example:  [delete]
- Enclose strings in double quotation marks; for example:  "hi"
- An example of a combination string and function is:  "logon usera" [enter]

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.17.14. ACS1444 ΓòÉΓòÉΓòÉ

ACS1444-E The key cannot be opened.  Close one or more opened keys.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.17.15. ACS1445 ΓòÉΓòÉΓòÉ

ACS1445-Q The contents of the open key titled name(8) have changed. Do you want
to save its contents to the profile?

where
name(8)         = key title name

Originator: Keyboard Remap Utility

User Response:

o Select Yes to save all states of the open key.

o Select No to not save the changes and to return to the open key window.


ΓòÉΓòÉΓòÉ 3.17.16. ACS1446 ΓòÉΓòÉΓòÉ

ACS1446-W The name(5) of the open key titled name(8) is not valid. Change the
state (value) of the key to a valid character, function, or string.

where
name(5)         = key state name
name(8)         = key title name

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.17.17. ACS1447 ΓòÉΓòÉΓòÉ

ACS1447-W The name(5), name(5), name(5), name(5), name(5), and name(5) values
of the open key titled name(8) are not valid. Modify a character, function, or
string for the states
When you type a definition:
- Type characters without delimiters
- Enclose functions in square brackets; for example:  [delete]
- Enclose strings in double quotation marks; for example:  "hi"
- An example of a combination string and function is:  "logon usera" [enter]

where
name(5)         = kind of state name
name(5)         = kind of state name
name(5)         = kind of state name
name(5)         = kind of state name
name(5)         = kind of state name
name(5)         = kind of state name
name(8)         = key name

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.17.18. ACS1448 ΓòÉΓòÉΓòÉ

ACS1448-Q The profile name already exists.  Do you want to replace it?

Originator: Keyboard Remap Utility

User Response:

o Select Yes to replace the profile with the changes.

o Select No to cancel the save operation.


ΓòÉΓòÉΓòÉ 3.17.19. ACS1449 ΓòÉΓòÉΓòÉ

ACS1449-Q You have chosen to copy states between two keys.  Do you want to
proceed?

Originator: Keyboard Remap Utility

User Response:

o Select Yes to complete the copy operation.

o Select No to cancel the copy operation.


ΓòÉΓòÉΓòÉ 3.17.20. ACS1464 ΓòÉΓòÉΓòÉ

ACS1464-E If there are any 3270 or 5250 logical terminal with presentation
space print configured, or logical printers active, the Host Print Control
window cannot be closed.

Originator: Converged Emulator

Explanation: You have attempted to close the Host Print Control window.

User Response: No action is required. The End task push button on the Task list
cannot be used to close the Host Print Control window.  The Task list entry for
Host Print Control is removed and the window made invisible when it no longer
contains any entries.  It is only closed when all 3270 and 5250 sessions with
print capabilities have been stopped.


ΓòÉΓòÉΓòÉ 3.17.21. ACS1465 ΓòÉΓòÉΓòÉ

ACS1465-Q You requested that the maximum number of sessions be changed to zero.
This will end the sessions.  Do you want the currently active transactions to
be completed first before the sessions are ended?

Originator: Subsystem Management

User Response:

o Select Yes to end the session after all queued transactions have been
  completed.

o Select No to end the session before the currently queued transactions have
  been completed.

o Select Cancel to close the window without any action.


ΓòÉΓòÉΓòÉ 3.17.22. ACS1466 ΓòÉΓòÉΓòÉ

ACS1466-W You have changed the number of sessions for this mode. Current
sessions will be ended.

Originator: Subsystem Management

Explanation: The only way to change session limits in APPC for a particular LU,
PLU, and Mode triplet is to end all the current sessions using this triplet and
then establish new sessions.

User Response: Do one of the following:

o Select OK to confirm the request and end the current sessions for this
  triplet and establish the new ones with the requested limits.

o Select Cancel to close the window without ending the sessions.


ΓòÉΓòÉΓòÉ 3.17.23. ACS1600 ΓòÉΓòÉΓòÉ

ACS1600-E Emulation services cannot be started from an OS/2 command prompt.

Originator: Converged Emulator

Explanation: You attempted to start emulation from the OS/2 command prompt.

User Response: Emulator cannot be started from the OS/2 command prompt.
Emulator can be started only from the Communications Manager program.


ΓòÉΓòÉΓòÉ 3.17.24. ACS1601 ΓòÉΓòÉΓòÉ

ACS1601-E The configuration changes will not be reflected in the emulator
sessions because the emulator could not load name(12).
Other emulator functions will continue.

where
name(12)        = run-time configuration DLL name

Originator: Converged Emulator

Explanation: An error occurred during the loading of one of the configuration
programs.  Runtime configuration changes will not be available from the
emulator.

User Response: Reinstall Communications Manager and retry the operation. Check
the error log for additional information.


ΓòÉΓòÉΓòÉ 3.17.25. ACS1702 ΓòÉΓòÉΓòÉ

ACS1702-W SNA shutdown is currently in progress. Your request cannot be
processed at this time.

Originator: Subsystem Management

Explanation: A request to stop SNA is already being processed.

User Response: Wait for all termination activity to complete, then restart SNA.


ΓòÉΓòÉΓòÉ 3.17.26. ACS1710 ΓòÉΓòÉΓòÉ

ACS1710-E The request to establish the LU 6.2 session was rejected because the
value in the Fully qualified name field is incorrect or a name in the Alias
list has not been selected.

Originator: Subsystem Management

Explanation: Likely causes are:

o The Fully qualified name radio button in the Partner LU group is selected,
  but the Fully qualified name entry fields contain incorrect values.  The
  Workstation id field (second entry) is blank, or one of the entry fields
  contains a character that is not valid.  Valid characters are:  A-Z, a-z,
  0-9, @, #, $.

o The Alias radio button in the Partner LU group is selected, but a name in the
  Alias drop-down list has not been selected.

User Response: Do one of the following:

o Correct the value in the Fully qualified name field.

o Select a name in the Alias drop-down list.


ΓòÉΓòÉΓòÉ 3.17.27. ACS1714 ΓòÉΓòÉΓòÉ

ACS1714-E The requested trace function cannot begin because a dump is in
progress.  Stop the dump or wait until it is completed. Then retry the trace
function.

Originator: Problem Determination

Explanation: Problem determination aids (PDA) dump services are active.  You
cannot perform trace functions and dump simultaneously.


ΓòÉΓòÉΓòÉ 3.17.28. ACS1755 ΓòÉΓòÉΓòÉ

ACS1755-E INTERNAL ERROR: An internal Communications Manager configuration
process has failed.

Originator: Configuration Services - Verify

User Response: Retry verification of your Communications Manager configuration.
From the OS/2 command prompt, enter CMVERIFY configuration_name.CFG. If the
problem persists, note the time, date, and this message number; then contact
your service coordinator.


ΓòÉΓòÉΓòÉ 3.17.29. ACS1756 ΓòÉΓòÉΓòÉ

ACS1756-E INTERNAL ERROR: The selected search key name(8) does not exist in
Communications Manager configuration file name(12).

where
name(8)         = profile search key name
name(12)        = configuration file name

Originator: Configuration Services - Verify

User Response: Retry verification of your Communications Manager configuration.
From the OS/2 command prompt, enter CMVERIFY configuration_name.CFG. If this
error persists, recreate your Communications Manager configuration.  Then,
retry verification.


ΓòÉΓòÉΓòÉ 3.17.30. ACS1760 ΓòÉΓòÉΓòÉ

ACS1760-E The Communications Manager configuration verification process
encountered errors while trying to write Communications Manager configuration
file name(12).

where
name(12)        = configuration file name

Originator: Configuration Services - Verify

User Response: Retry verification of your Communications Manager configuration.
From the OS/2 command prompt, enter CMVERIFY configuration_name.CFG. If this
error persists, recreate your Communications Manager configuration.  Then,
retry verification.


ΓòÉΓòÉΓòÉ 3.18. ACS1765 through ACS1949 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.18.1. ACS1765 ΓòÉΓòÉΓòÉ

ACS1765-E File transfer configuration name(8) referenced by 3270 terminal
emulation session name(8) does not exist.

where
name(8)         = file transfer profile name
name(8)         = converged emulator 3270 session record name

Originator: Configuration Services - Verify

User Response: Either correct the file transfer configuration name in the 3270
emulation session configuration or create the missing file transfer
configuration.  To access the 3270 terminal emulation configuration from the
Communications Manager Setup window:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select Configure any profile or feature from the Options pull-down menu.

o Select 3270 terminal emulation and then select Configure in the
  Communications Manager Configuration List window.

o Select File transfer from the 3270 Emulation window.

To access 3270 terminal emulation configuration on the emulator session, select
Emulator operations from the system menu.


ΓòÉΓòÉΓòÉ 3.18.2. ACS1787 ΓòÉΓòÉΓòÉ

ACS1787-E The local DTE address must be unique for all X.25 links.  Specify a
new address.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.18.3. ACS1805 ΓòÉΓòÉΓòÉ

ACS1805-W There is not enough memory to load the profile and run the Keyboard
Utility. To obtain more memory, reduce the number of programs running.  Then,
try the Keyboard Utility again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.4. ACS1806 ΓòÉΓòÉΓòÉ

ACS1806-W The code page number is not valid.  Enter a valid code page number.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.5. ACS1807 ΓòÉΓòÉΓòÉ

ACS1807-W The code page does not exist.  Enter a valid code page number.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.6. ACS1810 ΓòÉΓòÉΓòÉ

ACS1810-W The function or character name is not valid.  Enter a valid function
or character name.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.7. ACS1811 ΓòÉΓòÉΓòÉ

ACS1811-W The search item was not found.  Enter a different search item and try
the Find key function again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.8. ACS1813 ΓòÉΓòÉΓòÉ

ACS1813-W The clipboard operation cannot be completed because there is not
enough memory.  Reduce the number of active programs and try the operation
again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.9. ACS1814 ΓòÉΓòÉΓòÉ

ACS1814-W The clipboard operation cannot be completed because of text format
problems.  Correct the text format and try the operation again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.10. ACS1815 ΓòÉΓòÉΓòÉ

ACS1815-Q Reset will not save any unsaved changes. Do you want to reset?

Originator: Keyboard Remap Utility

User Response:

o Select Yes to reset all unsaved changes.

o Select No to cancel Reset.


ΓòÉΓòÉΓòÉ 3.18.11. ACS1816 ΓòÉΓòÉΓòÉ

ACS1816-Q One or more X.25 directory entries refer to this permanent virtual
circuit (PVC).  Do you want to delete the associated directory entries?

Originator: Configuration Services

Explanation: You are attempting to delete a PVC that has associated directory
entries.

User Response:

o Select Yes to delete the associated directory entries.

o If No is selected, each of the directory entries must be associated with a
  new PVC or each of the associated directory entries must be deleted.


ΓòÉΓòÉΓòÉ 3.18.12. ACS1818 ΓòÉΓòÉΓòÉ

ACS1818-E An internal print error rc(44) has occurred.

where
rc(44)          = internal print error code

Originator: Keyboard Remap Utility

User Response: Try the operation again.  If the problem persists, note the
time, date, problem ID, and this message number.  Check the OS/2 System Error
Log in the FFST/2 folder for associated error log entries. Then, contact your
service coordinator.


ΓòÉΓòÉΓòÉ 3.18.13. ACS1820 ΓòÉΓòÉΓòÉ

ACS1820-E The local CCITT compliance has changed to 1980.  There are packet
sizes in the link greater than the 1024 maximum packet size for 1980.

Originator: Configuration Services

User Response: Select SVC/PVC packet sizes from the Additional parameters list,
and change the packet sizes to those valid for 1980.


ΓòÉΓòÉΓòÉ 3.18.14. ACS1821 ΓòÉΓòÉΓòÉ

ACS1821-E A host file name must be specified in order to process(6) a file.
Enter a host file name in the host file name field and try the file transfer
again.

where
process(6)      = send or receive file transfer direction

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.18.15. ACS1822 ΓòÉΓòÉΓòÉ

ACS1822-E A workstation file name must be specified in order to process(6) a
file. Enter a valid workstation file name in the Workstation file name field
and try the file transfer again.

where
process(6)      = send or receive file transfer direction

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.18.16. ACS1823 ΓòÉΓòÉΓòÉ

ACS1823-E Name(25) ended unexpectedly.  Check the system error log for
additional information.

where
Name(25)        = component name

Originator: Subsystem Management

Explanation: An unexpected error occurred.  Examples of this type of error are
DOS and Presentation Manager errors.


ΓòÉΓòÉΓòÉ 3.18.17. ACS1858 ΓòÉΓòÉΓòÉ

ACS1858-E No permanent virtual circuits (PVCs) or switched virtual circuits
(SVCs) have been configured for name(20). Set the SVC count to 1, or configure
a PVC for this link.

where
name(20)        = link name

Originator: Configuration Services

User Response:

o To set the SVC count to 1 or more:

    1. Select the link name and then select Change in the X.25 Links window.

    2. Select Virtual circuit ranges and then select Change in the X.25 Link
       Parameters window.

o To configure a PVC:

    1. Select the link name and then select PVCs in the X.25 Links window.

    2. Select Create in the X.25 Permanent Virtual Circuits window.


ΓòÉΓòÉΓòÉ 3.18.18. ACS1870 ΓòÉΓòÉΓòÉ

ACS1870-E The remote DTE address cannot be the same as the local DTE address
specified for the associated link.  Specify either a new remote DTE address or
a new local DTE address for this link.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.18.19. ACS1871 ΓòÉΓòÉΓòÉ

ACS1871-E The local DTE address cannot be the same as the SVC remote DTE
address specified for the associated link.  Specify either a new local DTE
address or a new SVC remote DTE address for this link.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.18.20. ACS1931 ΓòÉΓòÉΓòÉ

ACS1931-E The long session name name(8) already exists.  Specify a different
name.

where
name(8)         = long session name

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.18.21. ACS1935 ΓòÉΓòÉΓòÉ

ACS1935-W The file name name(40) already exists.  Select Replace to overwrite
the file with the new data.  Select Cancel to specify a new file name.

where
name(40)        = file name

Originator: Problem Determination

Explanation: You are trying to save trace or dump information in a file with
the same name as an existing file.


ΓòÉΓòÉΓòÉ 3.18.22. ACS1936 ΓòÉΓòÉΓòÉ

ACS1936-W The dump cannot begin because a trace is in progress.  Stop the trace
or wait until it is completed.  Then retry the dump.

Originator: Problem Determination

Explanation: Problem determination aids (PDA) trace services are active. You
cannot run a dump and trace at the same time.


ΓòÉΓòÉΓòÉ 3.18.23. ACS1941 ΓòÉΓòÉΓòÉ

ACS1941-Q The current profile has been modified. Do you want to save it?

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.24. ACS1942 ΓòÉΓòÉΓòÉ

ACS1942-E You have chosen to copy, move, or swap the source or target states
with one or more warning states included.  Select OK to complete the operation.
Select Cancel to cancel the operation.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.25. ACS1943 ΓòÉΓòÉΓòÉ

ACS1943-E The profile you are updating is also used by other sessions. Each
session using the profile will be affected by any changes you make. Select OK
to update and save the profile. Select Cancel to cancel the operation.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.26. ACS1944 ΓòÉΓòÉΓòÉ

ACS1944-W The Print Keyboard operation was not successful.  Try the operation
again.

Originator: Keyboard Remap Utility

User Response: If the problem persists, note the time, date, and this message
number.  Check the system error log for additional information. From the FFST/2
folder, select System Error Log.


ΓòÉΓòÉΓòÉ 3.18.27. ACS1945 ΓòÉΓòÉΓòÉ

ACS1945-I TRANS127 The specified PC file has critical extended attributes (EAs)
which will not be sent to the host. Do you want to continue this transfer?

Originator: File Transfer

Explanation: An application may use extended attributes (EAs) to attach
standard or application-specific information to a file. EAs are maintained
separately and managed by the file system.

An application may mark any EA critical to the application's use in processing
a file.

File transfer will not send EA information.  Existing EAs are preserved when a
PC file is received over an existing PC file.

User Response: Do one of the following:

o Select Continue to continue this operation.

o Select Cancel current file to cancel transfer for the file shown in Current
  PC file. Other files still will be transferred; only the current file is
  canceled.

o Select Cancel transfer to cancel transfer for all files in the transfer
  request. (You cannot cancel files that were already transferred.)
The OS/2 utility EAUTIL allows you to separate EAs and to rejoin EAs with their
file objects.  Refer to the online OS/2 Command Reference for a description of
EAUTIL.


ΓòÉΓòÉΓòÉ 3.18.28. ACS1946 ΓòÉΓòÉΓòÉ

ACS1946-W The data entered is longer than the maximum string length of 1024.
Reduce the string length to 1024 characters or less and submit the request
again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.18.29. ACS1948 ΓòÉΓòÉΓòÉ

ACS1948-E Color configuration name(8) specified in the type(4) terminal
emulation session name(8) does not exist. Either correct the color
configuration name in the session configuration, or create the missing color
configuration.

where
name(8)         = color profile name
type(4)         = "3270/5250" emulator session type string
name(8)         = converged emulator session record name

Originator: Configuration Services - Verify

User Response: To access the emulator configuration:

o Select Setup in the Communications Manager Setup window.

o Select the configuration name and then select OK in the Open Configuration
  window.

o Select 3270 Terminal Emulator or 5250 Terminal Emulator and then select
  Change in the Communications Manager Configuration Definition window.

o Select 3270 Terminal Emulator or 5250 Terminal Emulator and then select
  Configure in the Communications Manager Profile List window.


ΓòÉΓòÉΓòÉ 3.18.30. ACS1949 ΓòÉΓòÉΓòÉ

ACS1949-E The Communications Manager configuration file handle name(4) passed
to the IS_LR_VFYD stage of the verification process is not valid.  Retry
verification of your Communications Manager configuration.  If the problem
persists, recreate your Communications Manager configuration.  Then, retry
verification.

where
name(4)         = configuration file handle name

Originator: Configuration Services - Verify


ΓòÉΓòÉΓòÉ 3.19. ACS1950 through ACS2025 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.19.1. ACS1950 ΓòÉΓòÉΓòÉ

ACS1950-E The configuration name name(255) does not refer to a valid
Communications Manager configuration file.

where
name(255)       = configuration name

Originator: Configuration Services - Verify

User Response: If the Communications Manager configuration listed does not
exist, either rerun CMVERIFY and specify a valid configuration, or create a
configuration with the given name. If the Communications Manager configuration
listed does exist, recreate the configuration and rerun CMVERIFY as before.


ΓòÉΓòÉΓòÉ 3.19.2. ACS1983 ΓòÉΓòÉΓòÉ

ACS1983-E An OS/2 error occurred during the Communications Manager
configuration verification process.  Verify cannot continue.

Originator: Configuration Services - Verify

Explanation: During Verify processing, a call to an OS/2 routine did not
complete.

User Response: Check for messages in the system error log.

o From the FFST/2 folder, select System Error Log. (You can also enter SYSLOG
  at the OS/2 command prompt.)

o If you are running OS/2 1.3, then:

   - Select 1.  Display system log file.

   - Enter LOG0001.DAT as the log file name, and press Enter. (These steps are
     not required if you are using OS/2 2.0.)

o Use the Problem Determination Guide, along with the information in the system
  error log, to determine the source of the problem.


ΓòÉΓòÉΓòÉ 3.19.3. ACS1984 ΓòÉΓòÉΓòÉ

ACS1984-E The NAU address range cannot overlap or fall within the defined NAU
address ranges for this or any other defined LU pool.  Specify a unique NAU
address range.

Originator: Configuration Services

Explanation: An address range must always have a start value and an end value
that does not overlap or fall within the NAU address ranges defined for any
other LU pool.

For example, the address ranges could be 1 to 32, 37 to 91, 101 to 219, and 236
to 238.  The values are decimal.

The address ranges could not be 1 to 32 or 28 to 45, because the 28 overlaps
the 1 to 32 range.

The address ranges could not be 1 to 32 or 12 to 15, because the 12 to 15 are
within the 1 to 32 range.


ΓòÉΓòÉΓòÉ 3.19.4. ACS1985 ΓòÉΓòÉΓòÉ

ACS1985-E The pool name is already defined.  Specify a unique pool name.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.19.5. ACS1986 ΓòÉΓòÉΓòÉ

ACS1986-E A system error ended a Communications Manager function. Problem
determination aids (PDA) trace or dump services received an unexpected return
code from an internal function call.

Originator: Problem Determination

User Response: Check the FFST/2 Message Log for other related messages from RAS
that occurred around the time of this message. Use the date, time, and problem
id from the messages to find more detailed problem diagnosis information in the
OS/2 System Error Log.  If you cannot diagnose the problem using the available
information, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.6. ACS2000 ΓòÉΓòÉΓòÉ

ACS2000-E An incorrect network management message was received from a
workstation.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that sent the incorrect network management message.  The error log also
contains a copy of the message. If a host focal point has been defined, this
message will be sent to the host without appending gateway information to the
message.


ΓòÉΓòÉΓòÉ 3.19.7. ACS2001 ΓòÉΓòÉΓòÉ

ACS2001-E A workstation denied an activate physical unit (ACTPU) request from
this gateway.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that denied the request.  The error log also contains a copy of the response.
This error may be caused by an incorrect configuration at the workstation or
the gateway.  Check the ACTPU response for any sense code information, then
check the configuration at both machines.  Correct any errors. If the problem
persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.8. ACS2002 ΓòÉΓòÉΓòÉ

ACS2002-E A workstation denied a deactivate physical unit (DACTPU) request from
this gateway.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that denied the request.  The error log also contains a copy of the response.
This error may be caused by an incorrect configuration at the workstation or
the gateway.  Check the DACTPU response for any sense code information, then
check the configuration at both machines.  Correct any errors. If the problem
persists, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.9. ACS2003 ΓòÉΓòÉΓòÉ

ACS2003-E A workstation denied an activate logical unit (ACTLU) request from
this gateway.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that denied the request.  The error log also contains a copy of the response.
This error may be caused by an incorrect configuration at the workstation or
the gateway.  Check the ACTLU response for any sense code information, then
check the configuration at both machines.  Correct any errors. If the problem
persists, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.10. ACS2004 ΓòÉΓòÉΓòÉ

ACS2004-E A workstation denied a deactivate logical unit (DACTLU) request from
this gateway.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that denied the request.  The error log also contains a copy of the response.
This error may be caused by an incorrect configuration at the workstation or
the gateway.  Check the DACTLU response for any sense code information, then
check the configuration at both machines.  Correct any errors. If the problem
persists, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.11. ACS2005 ΓòÉΓòÉΓòÉ

ACS2005-E A workstation denied an UNBIND request from this gateway.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that denied the request.  The error log also contains a copy of the response.
This error may be caused by an incorrect configuration at the workstation, the
gateway, or the host. Check the UNBIND response for any sense code information,
then check the configuration at all three machines.  Correct any errors. If the
problem persists, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.12. ACS2006 ΓòÉΓòÉΓòÉ

ACS2006-E A workstation sent a response, but the gateway has no record of
sending a corresponding request.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that sent the unknown response.  The error log also contains a copy of the
response. This error may be caused by an incorrect configuration at the
workstation or the gateway.  Check the response for its type and any sense code
information, then check the configuration at both machines.  Correct any
errors. If the error persists, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.13. ACS2007 ΓòÉΓòÉΓòÉ

ACS2007-E A host denied a NOTIFY request from this gateway.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the host that
denied the request.  The error log also contains a copy of the response. This
error may be caused by an incorrect configuration at the host or the gateway.
Check the NOTIFY response for any sense code information, then check the
configuration at both machines.  Correct any errors. If the problem persists
and there is not a host problem, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.14. ACS2008 ΓòÉΓòÉΓòÉ

ACS2008-W The gateway is unable to create a session.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
for which the gateway could not create a local form session ID (LFSID).  The
error log also contains a copy of the LFSID internal control block. This error
may be caused by an incorrect configuration at the workstation or the gateway.
This condition can also be caused by a transmission error between the gateway
and the host or workstation. To correct the situation, first try to de-activate
the link on which the error occurred, and then re-establish the connection.  If
the problem persists, check the configuration at both machines, and correct any
errors.  If the problem still persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.15. ACS2009 ΓòÉΓòÉΓòÉ

ACS2009-E A DEFINE_GATEWAY_WORKSTATION command refers to a workstation link
name that could not be found.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of the DEFINE_GATEWAY_WORKSTATION command that is in error. Change
the command to refer to a known workstation link name defined through an
existing DEFINE_LOGICAL_LINK command or define the link name using a new
DEFINE_LOGICAL_LINK command.  Then re-issue both commands. If the problem
persists, stop Communications Manager and restart it. If the problem still
persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.16. ACS2010 ΓòÉΓòÉΓòÉ

ACS2010-E The gateway was unable to allocate an implicit LU.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that was requesting an implicit LU.  Correct the problem or problems indicated
by the previous error and message log entries. If the problem persists, contact
your service coordinator.


ΓòÉΓòÉΓòÉ 3.19.17. ACS2011 ΓòÉΓòÉΓòÉ

ACS2011-W A workstation requested an activate physical unit (ACTPU) from the
gateway, but the gateway has no explicit or implicit LU definition for the
workstation.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that was requesting an ACTPU from the gateway. Either the gateway should have
an implicit or explicit definition for this link, or the workstation is
configured incorrectly.  Correct the configuration problems and re-issue the
DEFINE_GATEWAY commands or stop and restart Communications Manager. If the
problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.18. ACS2012 ΓòÉΓòÉΓòÉ

ACS2012-E The gateway cannot create an implicit LU because all LU names have
been used.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
link name, destination address, adapter number, and DLC name of the workstation
that was requesting an implicit LU from the gateway. There is only a limited
number of names that the gateway will use for implicit LU names.  Implicit LU
names are prefixed with @GPxx, where xx can range from 00 to FF in hexadecimal
characters.  If more than 256 different workstations request an implicit LU at
the same time, they cannot all be fulfilled.  If this is the case, ensure that
fewer than 256 workstations request implicit LUs at one time. It is also
possible that some other application is creating names that conflict with the
gateway implicit LU name format.  If this is the case, change the application.
If the problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.19. ACS2013 ΓòÉΓòÉΓòÉ

ACS2013-E The gateway cannot create a workstation LU with the same name as an
existing local LU 6.2 definition.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  The command requests a
workstation LU with the same name as an existing local LU 6.2. If this command
was configured through CMSETUP or by editing an .NDF file, it will
automatically take effect the next time Communications Manager is restarted
with this configuration file. If the command must take effect before you
restart Communications Manager again, either change the LU name in the
DEFINE_GATEWAY_WORKSTATION command or the DEFINE_LOCAL_LU command and re-issue
both commands. The local LU can also be deleted through a DELETE_LOCAL_LU
command. If the problem persists, stop Communications Manager and restart it.
If the problem still persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.20. ACS2014 ΓòÉΓòÉΓòÉ

ACS2014-E The gateway cannot create a workstation LU with the same LU name
being used by another SNA application, such as LUA, 3270, or LU 6.2.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  The command requests a
workstation LU with the same name as an existing non-gateway LU. If this
command was configured through CMSETUP or by editing an .NDF file, it will
automatically take effect the next time Communications Manager is restarted
with this configuration file. If the command must take effect before the next
restart, do one of the following:

o Change the LU name in the DEFINE_GATEWAY_WORKSTATION command.

o Change the command that created the LU name before the
  DEFINE_GATEWAY_WORKSTATION command was created.

Then, re-issue both commands.  If the problem persists, stop Communications
Manager and restart it.  If the problem still persists, contact your local
service coordinator.


ΓòÉΓòÉΓòÉ 3.19.21. ACS2015 ΓòÉΓòÉΓòÉ

ACS2015-E The gateway cannot find a host with the given link name.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_HOST or DEFINE_GATEWAY_WORKSTATION command that
refers to an unknown host link name. Change the command to refer to a known
host link name defined through an existing DEFINE_LOGICAL_LINK command or
define the link name using a new DEFINE_LOGICAL_LINK command.  Then re-issue
both commands. If the problem persists, stop Communications Manager and restart
it. If the problem still persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.22. ACS2016 ΓòÉΓòÉΓòÉ

ACS2016-E The gateway cannot create a workstation LU with an incorrect host NAU
address.  The NAU address cannot be '00'X or 'FF'X.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_HOST or DEFINE_GATEWAY_WORKSTATION command.  The
command requested a host NAU address of '00'X or 'FF'X. Change the command to
refer to a host NAU address with any value between '01'X and 'FE'X, and then
re-issue the command. If the problem persists, contact your local service
coordinator.


ΓòÉΓòÉΓòÉ 3.19.23. ACS2017 ΓòÉΓòÉΓòÉ

ACS2017-W The gateway cannot re-define an LU name because it is being used by
an active gateway workstation.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  The command requests an LU
name that is being used by an active gateway workstation LU. If this command
was configured through CMSETUP or by editing an .NDF file, it will
automatically take effect the next time Communications Manager is restarted
with this configuration file. If the command must take effect before you
restart Communications Manager again, de-activate the link to the workstation,
and then re-issue the DEFINE_GATEWAY_WORKSTATION command. If an emulator is
running at the workstation, you may have to de-activate the link at the
workstation to prevent it from re-activating the link during the command
invocation. If the problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.24. ACS2018 ΓòÉΓòÉΓòÉ

ACS2018-W The gateway cannot re-define a workstation NAU address because the
workstation is active.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  The command requests a
workstation NAU address that is being used by an active gateway workstation. If
this command was configured through CMSETUP or by editing an .NDF file, it will
automatically take effect the next time Communications Manager is restarted
with this configuration file. If the command must take effect before you
restart it again, de-activate the link to the workstation, and then re-issue
the DEFINE_GATEWAY_WORKSTATION command. If an emulator is running at the
workstation, you may have to de-activate the link at the workstation to prevent
it from re-activating the link during the command invocation. If the problem
persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.25. ACS2019 ΓòÉΓòÉΓòÉ

ACS2019-W The gateway cannot re-define host NAU address because the NAU address
is being used by another gateway workstation or another SNA application.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION or DEFINE_GATEWAY_HOST command.  The
command requests a host NAU address that is being used by another gateway
workstation or SNA application. If this command was configured through CMSETUP
or by editing an .NDF file, it will automatically take effect the next time
Communications Manager is restarted with this configuration file. If the
command must take effect before the next time you restart, change the gateway
command to refer to a different host NAU address and re-issue it.  If that is
not possible, de-activate the link to the workstation, and then re-issue the
DEFINE_GATEWAY_WORKSTATION command. If an emulator is running at the
workstation, you may have to de-activate the link at the workstation to prevent
it from re-activating the link during the command invocation. If the problem
persists after de-activating the workstation link, stop Communications Manager
and restart it. If the problem still persists, contact your local service
coordinator.


ΓòÉΓòÉΓòÉ 3.19.26. ACS2020 ΓòÉΓòÉΓòÉ

ACS2020-E The gateway cannot create a workstation LU because its pool class
does not exist.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  The command requests a
host pool class that does not exist. Change the command to refer to an existing
pool class defined by a DEFINE_GATEWAY_HOST command, or add the new pool class
through a DEFINE_GATEWAY_HOST command. Then re-issue both commands. If the
problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.27. ACS2021 ΓòÉΓòÉΓòÉ

ACS2021-E The gateway cannot create a workstation LU with an incorrect
workstation NAU address. The NAU address cannot be 0 ('00'X) or 255 ('FF'X).

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  The command requested a
workstation NAU address of '00'X or 'FF'X. Change the command to refer to a NAU
address with any value from '01'X to 'FE'X, and re-issue the command. If the
problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.28. ACS2022 ΓòÉΓòÉΓòÉ

ACS2022-E The gateway cannot define a pool class with an incorrect time-out
value. The time-out value must be any value from 0 to 999.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_HOST command.  The command requests an
auto-logoff time-out value greater than 999 ('3E7'X). Change the command to
refer to a time-out value between 0 and 999 and re-verify the configuration.  A
time-out value of 0 means that this pool class will not be timed. If the
problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.29. ACS2023 ΓòÉΓòÉΓòÉ

ACS2023-W The gateway cannot re-define a DEFINE_GATEWAY_WORKSTATION command
because the link to the workstation is active.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry which includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command that redefines an active
gateway workstation. If this command was configured through CMSETUP or by
editing an .NDF file, then without any further user intervention it will take
effect the next time Communications Manager/2 1.0 or higher is restarted with
this configuration file. If the command must take effect before the next
workstation restart, de-activate the link to the workstation then re-issue the
DEFINE_GATEWAY_WORKSTATION command. If an emulator is running at the
workstation, then you may have to de-activate the link at the workstation to
prevent it from re-activating the link during the command invocation. If the
problem persists, contact your local service coordinator.


ΓòÉΓòÉΓòÉ 3.19.30. ACS2025 ΓòÉΓòÉΓòÉ

ACS2025-E The gateway cannot create a workstation LU because the requested LU
name is not an EBCDIC Type-A name.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command.  This command specifies an
LU name that is not EBCDIC Type-A.  An EBCDIC Type-A name consists of: up to 8
characters long; all uppercase letters, numbers, @, #, $; starts with a letter
or @, #, $; and is padded on the right with EBCDIC blanks. Change the command
to specify a valid EBCDIC Type-A name and then re-issue the
DEFINE_GATEWAY_WORKSTATION command. If the problem persists, contact your local
service coordinator.


ΓòÉΓòÉΓòÉ 3.20. ACS2026 through ACS2127 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.20.1. ACS2026 ΓòÉΓòÉΓòÉ

ACS2026-E The gateway cannot create the pool class because its name contains
non-printable ASCII characters.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry that includes the
parameters of a DEFINE_GATEWAY_HOST command that specifies a pool class name
containing non-printable ASCII characters.  An ASCII character is non-printable
if its numeric value is less than 32 ('20'X). Change the DEFINE_GATEWAY_HOST
command to specify a pool class name with all characters greater than or equal
to 32 and re-issue the command. If the problem persists, contact your local
service coordinator.


ΓòÉΓòÉΓòÉ 3.20.2. ACS2027 ΓòÉΓòÉΓòÉ

ACS2027-E The gateway cannot create an implicit workstation LU definition for
this DLC because it is not a supported DLC for this configuration.

Originator: SNAGATE (SNA Gateway)

User Response: The error log contains a corresponding entry which includes the
parameters of a DEFINE_GATEWAY_WORKSTATION command that specifies an implicit
LU definition for an unsupported DLC type. The names of all defined DLCs can be
found by using the Communications Manager Subsystem Manager, or by issuing the
DISPLAY verb.  All DLC names should be specified with uppercase ASCII
characters and padded on the right with ASCII blanks ('20'x). Change the
command to specify a valid DLC name and then re-issue the
DEFINE_GATEWAY_WORKSTATION command. If the problem persists, contact your local
service coordinator.


ΓòÉΓòÉΓòÉ 3.20.3. ACS2100 ΓòÉΓòÉΓòÉ

ACS2100-E Changes to the configuration cannot be saved because the
configuration is temporarily locked by another program.

Originator: Keylock

User Response: Either wait for the other program to remove the lock on the
configuration or end that program. If you want to save the changes, continue to
select Retry until the other program removes the lock on the configuration.
You will not receive a specific message when the lock is removed.


ΓòÉΓòÉΓòÉ 3.20.4. ACS2101 ΓòÉΓòÉΓòÉ

ACS2101-E name(255) is not a valid configuration file or it cannot be found.
Select another configuration.

where
name(255)       = configuration file name

Originator: Configuration Services - Replace


ΓòÉΓòÉΓòÉ 3.20.5. ACS2102 ΓòÉΓòÉΓòÉ

ACS2102-I The replace operation has completed successfully.  The new Default
configuration is name(8).  You may need to reinstall this configuration.

where
name(8)         = configuration file name

Originator: Configuration Services - Replace

Explanation: You may need to reinstall this configuration if additional product
files are necessary.

User Response: To ensure that all necessary product files are either updated or
installed, install this configuration by selecting Installation... in the
Communications Manager Setup window.


ΓòÉΓòÉΓòÉ 3.20.6. ACS2103 ΓòÉΓòÉΓòÉ

ACS2103-I The configuration selected is already the current default
configuration. To change the default configuration, select a different
configuration.

Originator: Configuration Services - Replace


ΓòÉΓòÉΓòÉ 3.20.7. ACS2104 ΓòÉΓòÉΓòÉ

ACS2104-E The new configuration has not been verified.  Verify this
configuration or select one that has been verified.

Originator: Configuration Services - Replace

Explanation: You have tried to run the replace function with a Communications
Manager configuration file that has not been verified.

User Response:

 1. Select Setup in the Communications Manager Setup window.

 2. Select the configuration name and select OK in the Open Configuration
    window.

 3. Update the features list for the configuration in the Communications
    Manager Configuration Definition window. Next, select Change in the window.

 4. Configure all required profiles on the Communications Manager Profile List
    window.

 5. After the profiles have been configured, select Close to return to the
    previous window (Communications Manager Configuration Definition).

 6. Select Close in the Communications Manager Configuration Definition window
    and Verify will be run automatically for the configuration file.


ΓòÉΓòÉΓòÉ 3.20.8. ACS2105 ΓòÉΓòÉΓòÉ

ACS2105-E The values entered for the new password and the confirmation of the
new password must be the same.  Enter the passwords again and make sure they
are identical.

Originator: Keylock


ΓòÉΓòÉΓòÉ 3.20.9. ACS2106 ΓòÉΓòÉΓòÉ

ACS2106-E An unexpected return code was received from an OS/2 function call.

Originator: Configuration Services - Advanced

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code cannot be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry. The last four digits of the minor error
  code provide the request code of the associated function call. Refer to OS/2
  Technical Library for interpretation and description of the OS/2 request
  code.  Locate the return code in the Additional Data section of the
  associated error log entry. The return code is the first four digits of this
  data, and is in byte-reversed format.

   - For example, if the first 2 bytes are x'1234', this actually represents a
     return code of x'3412'.  The OS/2 return codes are defined under the OS/2
     function calls in OS/2 Technical Library.

o If the request code/return code combination indicates a resource error,
  attempt to free the resource.  For resource errors that appear to be
  internal, reduce the number of active programs in the system. Examples of
  such errors are memory, semaphores, and threads.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/02/ OS/2 return code (in byte-reversed format). Refer to OS/2 Technical
     Library for interpretation.

   - 02/08/Reserved

   - 08/02/Reserved unless the originator is APPC. For APPC loader:  OS/2
     function call reference number.

   - 10/17/Reserved unless the originator is APPC. For APPC:  ASCII name of the
     OS/2 function call (for example, DOSFREEMODULE).


ΓòÉΓòÉΓòÉ 3.20.10. ACS2107 ΓòÉΓòÉΓòÉ

ACS2107-E An unexpected return code was received from an OS/2 function call.

Originator: Configuration Services - Advanced

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code cannot be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry. The last four digits of the minor error
  code provide the request code of the associated function call. Refer to OS/2
  Technical Library for interpretation and description of the OS/2 request
  code.  Locate the return code in the Additional Data section of the
  associated error log entry. The return code is the first four digits of this
  data, and is in byte-reversed format.

   - For example, if the first 2 bytes are x'1234', this actually represents a
     return code of x'3412'.  The OS/2 return codes are defined under the OS/2
     function calls in OS/2 Technical Library.

o If the request code/return code combination indicates a resource error,
  attempt to free the resource.  For resource errors that appear to be
  internal, reduce the number of active programs in the system. Examples of
  such errors are memory, semaphores, and threads.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/02/ OS/2 return code (in byte-reversed format). Refer to OS/2 Technical
     Library for interpretation.

   - 02/08/Reserved

   - 08/02/Reserved unless the originator is APPC. For APPC loader:  OS/2
     function call reference number.

   - 10/17/Reserved unless the originator is APPC. For APPC:  ASCII name of the
     OS/2 function call (for example, DOSFREEMODULE).


ΓòÉΓòÉΓòÉ 3.20.11. ACS2108 ΓòÉΓòÉΓòÉ

ACS2108-E An unexpected return code was received from an OS/2 PM function call.

Originator: Configuration Services - Advanced

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 PM function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code can not be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry.  The last four digits of the minor error
  code provide the request code of the associated function call.  Refer to OS/2
  Technical Library for interpretation and description of the OS/2 PM request
  code.

o Locate the return code in the Additional Data section of the associated error
  log entry.  The return code is the first four digits of this data.  The
  return code is in byte-reversed format. For example, if the first 2 bytes are
  x'0800', this actually represents a return code of x'0008'.  The OS/2 return
  codes are defined under the OS/2 PM function calls in OS/2 Technical Library.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ OS/2 return code (in byte-reversed format).  Refer to OS/2 Technical
     Library for interpretation.

   - 2/8/ Reserved


ΓòÉΓòÉΓòÉ 3.20.12. ACS2109 ΓòÉΓòÉΓòÉ

ACS2109-E An unexpected return code was received from WMS.

Originator: Configuration Services - Advanced

Explanation: A local Communications Manager function may have failed.

User Response: WMS is a graphics subsystem associated with OS/2 Presentation
Manager.  Often, this condition is logged in association with other entries;
review the FFST/2 message log and the system error log for details concerning
the nature of any failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed WMS function call and the
  return code; refer to the WMS Technical Library for detailed descriptions of
  the function call and return code.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.20.13. ACS2110 ΓòÉΓòÉΓòÉ

ACS2110-Q Will the configuration name(dynamic) be used for this workstation?

where
name(dynamic)   = configuration name

Originator: Configuration Services - Advanced

User Response: Select one of the following choices:

o To run the configuration on the workstation you are currently using, select
  Yes.

o To run the configuration on a different machine, select No.

o To exit this window without making a change, select Cancel.


ΓòÉΓòÉΓòÉ 3.20.14. ACS2111 ΓòÉΓòÉΓòÉ

ACS2111-Q Would you like to return to Communications Manager Configuration to
change the settings?

Originator: Configuration Services - Advanced

User Response:

o Select Yes if you want to change the configuration settings. You will be
  returned to the Communications Manager Configuration Definition window.

o Select No if you do not want to change the configuration settings.


ΓòÉΓòÉΓòÉ 3.20.15. ACS2112 ΓòÉΓòÉΓòÉ

ACS2112-E Communications Manager was not able to verify name(8) because of the
errors logged in the verify log.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced

User Response: Check and correct the verification errors.  Then retry the
operation.


ΓòÉΓòÉΓòÉ 3.20.16. ACS2113 ΓòÉΓòÉΓòÉ

ACS2113-Q Configuration name(8) contains verification rc(10).  Would you like
to invoke the FFST/2 message log formatter to view the verify log?

where
name(8)         = configuration name
rc(10)          = error level

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.17. ACS2114 ΓòÉΓòÉΓòÉ

ACS2114-Q Your configuration requires additional installation.  Would you like
to begin the installation process?

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.18. ACS2115 ΓòÉΓòÉΓòÉ

ACS2115-Q Errors occurred during the upgrade of your configuration.  Would you
like to invoke the FFST/2 message log formatter to view the upgrade log?

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.19. ACS2116 ΓòÉΓòÉΓòÉ

ACS2116-Q The configuration name(8) was not found.  Would you like to create
it?

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.20. ACS2117 ΓòÉΓòÉΓòÉ

ACS2117-E The configuration name(8) is being used by another program.  Select
another configuration, or stop the program using the configuration. Then retry
the operation.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.21. ACS2118 ΓòÉΓòÉΓòÉ

ACS2118-E The configuration name(8) does not have a valid Communications
Manager format.  Select another configuration.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.22. ACS2119 ΓòÉΓòÉΓòÉ

ACS2119-E Configuration name(8) could not open.  Close any files that are
currently open and retry the operation.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.23. ACS2120 ΓòÉΓòÉΓòÉ

ACS2120-E Configuration name(8) does not exist.  Select another configuration
to open.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.24. ACS2121 ΓòÉΓòÉΓòÉ

ACS2121-Q Would you like to dynamically update your SNA resources?

Originator: Configuration Services - Advanced

Explanation: The workstation has been configured so that it uses configured
Systems Network Architecture (SNA) resources (Gateway, APPN, 3270 non-DFT, or
SRPI non-DFT).  Communications Manager is also active with this configuration.
The following SNA resources will be dynamically updated:

o SNA Connections Changes

o Local LU Definitions Changes

o Mode Changes

o TP Definition and Security Changes

o CPIC Side Information Changes

o Conversation Security Changes

o LU to LU Security Changes

User Response:

o Select Yes to update the currently running SNA resources with the changes
  made during configuration.

o Select No to end without updating the SNA resources.


ΓòÉΓòÉΓòÉ 3.20.25. ACS2122 ΓòÉΓòÉΓòÉ

ACS2122-E Configuration name name(dynamic) is not valid, or the path does not
exist. Specify a valid name or select another configuration to open.

where
name(dynamic)   = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.20.26. ACS2123 ΓòÉΓòÉΓòÉ

ACS2123-E The configuration data can only be displayed because another
application is using a critical file that must be used to change the
configuration data.

Originator: Configuration Services - Advanced

User Response: Do one of the following:

o Select Display Only to display the configuration data.

o Stop the other application using the critical file and select Retry to change
  the configuration data.

o Select Cancel to close this window.


ΓòÉΓòÉΓòÉ 3.20.27. ACS2124 ΓòÉΓòÉΓòÉ

ACS2124-W The specified backup configuration already exists.  Select Cancel to
leave this window and specify another backup configuration.  Select Replace to
replace the existing backup and continue the Upgrade process.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.20.28. ACS2125 ΓòÉΓòÉΓòÉ

ACS2125-E The specified backup configuration is being used by another process.
Select another backup configuration, or stop the process using the specified
backup configuration.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.20.29. ACS2126 ΓòÉΓòÉΓòÉ

ACS2126-E The specified backup configuration file name cannot be the same as
the source configuration name.  You must enter another backup configuration
name.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.20.30. ACS2127 ΓòÉΓòÉΓòÉ

ACS2127-E The specified source configuration is not verified and it cannot be
upgraded.  You can select another configuration from the Open Configuration
window.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.21. ACS2128 through ACS2157 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.21.1. ACS2128 ΓòÉΓòÉΓòÉ

ACS2128-W Terminal and printer definitions that were not assigned to a 5250
session were not upgraded.  These definitions are not included in the upgraded
version of the Communications Manager configuration file.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.21.2. ACS2129 ΓòÉΓòÉΓòÉ

ACS2129-E An unexpected return code returncode(6) was received from an OS/2
function call.

where
returncode(6)   = OS/2 return code

Originator: Configuration Services - Upgrade

Explanation: A local Communications Manager function may have failed.

User Response: Enter the following at the OS/2 command line: HELP <return code>
HELP - OS/2 command <return code> - OS/2 return code in the message text.


ΓòÉΓòÉΓòÉ 3.21.3. ACS2130 ΓòÉΓòÉΓòÉ

ACS2130-E INTERNAL ERROR:  An internal Communications Manager configuration
process failed.

Originator: Configuration Services - Upgrade

User Response: Retry upgrade of the Communications Manager configuration. If
you are not currently installing Communications Manager, type CMUPGRAD
configuration_name.CFG at the OS/2 command prompt. If you are currently
installing Communications Manager, complete the installation before you type
the command. If the problem persists, note the time, date, and this message
number; then contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.21.4. ACS2131 ΓòÉΓòÉΓòÉ

ACS2131-E The names entered for local node and partner LU are the same. The
local node name and partner LU name must be different. Change one of these
names.

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.21.5. ACS2132 ΓòÉΓòÉΓòÉ

ACS2132-E The name(40) profile must be configured first.  Select it first, and
then select other profiles to be configured.

where
name(40)        = profile name

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.21.6. ACS2133 ΓòÉΓòÉΓòÉ

ACS2133-E Your version of configuration name(8) is not supported by this
upgrade function.  Select another configuration to open.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.21.7. ACS2134 ΓòÉΓòÉΓòÉ

ACS2134-E Critical file name(8) was not found or was modified or damaged.

where
name(8)         = system critical file name

Originator: Configuration Services - Advanced

Explanation: An error occurred when trying to open critical file ACSCFG.DAT,
ACSCFGT.DAT or CM.INI.

User Response: Reinstall Communications Manager.  Type CMSETUP at the OS/2
command prompt for the source drive containing the Communications Manager
product files.  If you are installing from diskettes, be sure that
Communications Manager diskette #1 is inserted in the source drive.


ΓòÉΓòÉΓòÉ 3.21.8. ACS2135 ΓòÉΓòÉΓòÉ

ACS2135-E The name(10) initialization file is missing data or contains
corrupted data for the parm(20) parameter.

where
name(10)        = initialization file name
parm(20)        = parameter in initialize file

Originator: Configuration Services - Replace


ΓòÉΓòÉΓòÉ 3.21.9. ACS2136 ΓòÉΓòÉΓòÉ

ACS2136-E An error was encountered during file I/O.  This may be due to a
disk/diskette that may be damaged, unformatted, or not compatible with the
operating system.

Originator: Configuration Services - Advanced

User Response: Do one of the following, then retry the operation:

o Make sure the diskette is properly inserted.

o Use CHKDSK to check that the disk is not damaged.

o Format the disk/diskette for the operating system. Warning: When you format a
  disk/diskette, any information that was previously on the disk/diskette is
  erased.

o Check to be sure you do not have a high density diskette in a low density
  diskette drive.


ΓòÉΓòÉΓòÉ 3.21.10. ACS2137 ΓòÉΓòÉΓòÉ

ACS2137-E An unexpected return code was received from an OS/2 function call.

Originator: Configuration Services - Advanced

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code can not be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry.  The last four digits of the minor error
  code provide the request code of the associated function call.  Refer to OS/2
  Technical Library for interpretation and description of the OS/2 request
  code.  Locate the return code in the Additional Data section of the
  associated error log entry.  The return code is the first four digits of this
  data.  The return code is in byte-reversed format. For example, if the first
  2 bytes are x'1234', this actually represents a return code of x'3412'.  The
  OS/2 return codes are defined under the OS/2 function calls in OS/2 Technical
  Library.

o If the request code/return code combination indicates a resource error,
  attempt to free the resource.  For resource errors that appear to be
  internal, reduce the number of active programs in the system.  Examples of
  such errors are memory, semaphores, and threads.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/02/ OS/2 return code (in byte-reversed format). Refer to OS/2 Technical
     Library for interpretation.

   - 02/08/Reserved

   - 08/02/Reserved unless the originator is APPC. For APPC loader:  OS/2
     function call reference number.

   - 10/17/Reserved unless the originator is APPC. For APPC:  ASCII name of the
     OS/2 function call (for example, DOSFREEMODULE).


ΓòÉΓòÉΓòÉ 3.21.11. ACS2138 ΓòÉΓòÉΓòÉ

ACS2138-E The total number of logical terminal and logical printer sessions
combined is limited to num(2).  Since some sessions were previously configured,
you can now add only num(2) more sessions.

where
num(2)          = Max session limit
num(2)          = Num of configured sessions

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.21.12. ACS2139 ΓòÉΓòÉΓòÉ

ACS2139-E An APPN call failed.  Check the error log for additional information.

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.21.13. ACS2140 ΓòÉΓòÉΓòÉ

ACS2140-E An internal configuration services error occurred.  Check the error
log for additional information.

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.21.14. ACS2141 ΓòÉΓòÉΓòÉ

ACS2141-E The package type of name(8) does not match the package type of this
workstation.  Select another configuration.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced

Explanation: The specified configuration is intended to be used for this
workstation. However, the package type (single user, communication server, or
communication client) of the configuration does not match this workstation's
package type.


ΓòÉΓòÉΓòÉ 3.21.15. ACS2142 ΓòÉΓòÉΓòÉ

ACS2142-Q The package type of name(8) does not match the package type of this
workstation.  Would you like to continue the configuration for another
workstation?

where
name(8)         = configuration name

Originator: Configuration Services - Advanced

Explanation: The configuration file that you are opening for this workstation
has a different package type (single user, communication server or
communication client) than this workstation.

User Response: Continue configuring for another workstation or choose another
configuration to open.


ΓòÉΓòÉΓòÉ 3.21.16. ACS2143 ΓòÉΓòÉΓòÉ

ACS2143-E The SNA local node characteristics must be configured before name(40)
can be configured.

where
name(40)        = feature name

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.21.17. ACS2144 ΓòÉΓòÉΓòÉ

ACS2144-E The specified backup file name contains an incorrect character.
Correct the file name, and then retry the command.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.21.18. ACS2145 ΓòÉΓòÉΓòÉ

ACS2145-E There is not enough space on the disk or diskette to create name(8).
Delete some files or specify a different drive, and then retry the command.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.21.19. ACS2146 ΓòÉΓòÉΓòÉ

ACS2146-E name(8) cannot be created because the diskette is write protected.
Make sure that the proper diskette is being used, or remove the write
protection, and then retry the command.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced

Explanation: No information can be added to or changed on a write-protected
diskette.


ΓòÉΓòÉΓòÉ 3.21.20. ACS2147 ΓòÉΓòÉΓòÉ

ACS2147-Q Dynamic update errors have occurred.  Would you like to invoke the
FFST/2 Message Log Formatter to view the verify log?

Originator: Configuration Services - Advanced

User Response:

o Select YES to invoke the FFST/2 Message Log Formatter to view the FFST/2
  message log.

o Select NO if you do not want to invoke FFST/2.


ΓòÉΓòÉΓòÉ 3.21.21. ACS2148 ΓòÉΓòÉΓòÉ

ACS2148-E There is not enough disk space to update the configuration file. Free
some space and select Retry. WARNING:  If you select Cancel or close the
message window, data will be lost and the file may be unusable.

Originator: Profile Services/Logical Record Services

User Response: Leave the message window displayed and follow these steps:

o Open another OS/2 window.

o Erase unneeded files from the disk to provide more disk space.

o When more space is available, return to the message window and select Retry
  to try the operation again.

Note: If you select Cancel or close the message window, erase the bad
configuration file and create it again.


ΓòÉΓòÉΓòÉ 3.21.22. ACS2149 ΓòÉΓòÉΓòÉ

ACS2149-Q You are currently using name(26).  Do you want to use this feature?

where
name(26)        = profile name

Originator: Configuration Services - Advanced

Explanation: The selected feature is currently set to be installed and to be
used by Communications Manager.

User Response:

o Select Yes to install and use the selected feature.

o Select No if you do not want to install and use the selected feature.

o Select Cancel to close this window and not change the status of the selected
  feature.


ΓòÉΓòÉΓòÉ 3.21.23. ACS2150 ΓòÉΓòÉΓòÉ

ACS2150-Q You are not currently using name(26).  Do you want to use this
feature?

where
name(26)        = profile name

Originator: Configuration Services - Advanced

Explanation: The selected feature is not currently set to be installed and used
by Communications Manager.

User Response:

o Select Yes to install and use the selected feature.

o Select No if you do not want to install and use the selected feature.

o Select Cancel to close this window and not change the status of the selected
  feature.


ΓòÉΓòÉΓòÉ 3.21.24. ACS2151 ΓòÉΓòÉΓòÉ

ACS2151-E Communications Manager was not able to verify name(8) because of the
errors logged in the upgrade log.

where
name(8)         = configuration name

Originator: Configuration Services - Advanced

User Response: Check and correct the verification errors.  Then retry the
operation.


ΓòÉΓòÉΓòÉ 3.21.25. ACS2152 ΓòÉΓòÉΓòÉ

ACS2152-E The function of Programmable Configuration is now supported through
response files.  To change Communications Manager configuration, use the
CMSETUP command with a response file. To list configuration values, use the
CMRECORD command.

Originator: Remote Configuration and Installation Utility


ΓòÉΓòÉΓòÉ 3.21.26. ACS2153 ΓòÉΓòÉΓòÉ

ACS2153-E The password is not valid.  Type the master password or the service
password correctly.

Originator: Keylock


ΓòÉΓòÉΓòÉ 3.21.27. ACS2154 ΓòÉΓòÉΓòÉ

ACS2154-I You are currently using name(26).

where
name(26)        = profile name

Originator: Configuration Services - Advanced

Explanation: The feature that is currently selected is being used by
Communications Manager.  You cannot change the status of this feature.


ΓòÉΓòÉΓòÉ 3.21.28. ACS2155 ΓòÉΓòÉΓòÉ

ACS2155-I Currently, name(26) is not being used.

where
name(26)        = profile name

Originator: Configuration Services - Advanced

Explanation: The feature that is currently selected is not installed for use by
Communications Manager.  You cannot change the status of this feature.


ΓòÉΓòÉΓòÉ 3.21.29. ACS2156 ΓòÉΓòÉΓòÉ

ACS2156-E A workstation LU exists that has this host LU pool in its definition.
Please remove the workstation LUs before attempting to remove this host LU
pool.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.21.30. ACS2157 ΓòÉΓòÉΓòÉ

ACS2157-W Only name(26) of the name(26) requested logical sessions can be
defined because the limit of 254 LUA definitions has been reached.

where
name(26)        = written sessions
name(26)        = user specified sessions

Originator: Configuration Services - Basic

Explanation: Communications Manager requires an LUA definition for each logical
session you define.  Some of the logical sessions you attempted to define were
not created.

User Response: Delete some of the existing LUA definitions that you do not
require, and then define the logical sessions you need.  To delete an existing
LUA definition, go to the Communications Manager Configuration List window, and
select SNA LUA APIs.  Another window appears, prompting you for more
information.


ΓòÉΓòÉΓòÉ 3.22. ACS2158 through ACS2359 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.22.1. ACS2158 ΓòÉΓòÉΓòÉ

ACS2158-E Before you can run LAN protocols over ISDN, you must install and
configure Connection Manager 802.5 virtual MAC driver using the LAN Adapter and
Protocol Support (LAPS) program.

Originator: Configuration Services - Advanced

Explanation: LAN Protocols over ISDN requires installation of Connection
Manager 802.5 virtual MAC driver. This driver is provided on the Communications
Manager diskette labeled ISDN Adapter Device Drivers.  LAPS must be installed
before you can install and configure this network adapter; the configuration is
stored in the PROTOCOL.INI file.

User Response: You can install and configure the Connection Manager 802.5
virtual MAC drive now or later.  If you want to install and configure now,
begin with the steps that follow. If you want to configure later, continue with
the installation and configuration of Communications Manager, and then complete
the steps that follow:

 1. Open another OS/2 window.

 2. Run LAPS.

 3. Select the Install push button.

    The Install Additional Network Drivers window appears. The Source entry
    field should contain A:.

 4. Insert the Communications Manager diskette labeled ISDN Adapter Device
    Drivers in drive A and select the OK push button.

 5. To configure Connection Manager 802.5 virtual MAC Network adapter and its
    associated protocol, select the Configure push button.

 6. Select Configure LAN transports and Continue...

 7. Add the Connection Manager 802.5 Virtual MAC driver from the Network
    Adapters list to the Current Configuration List and select OK.

    Note:  The configuration information is stored in the PROTOCOL.INI file.


ΓòÉΓòÉΓòÉ 3.22.2. ACS2159 ΓòÉΓòÉΓòÉ

ACS2159-E A Permanent connection name was not specified.  Specify an Incoming
or Outgoing call directory entry.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.22.3. ACS2160 ΓòÉΓòÉΓòÉ

ACS2160-E The access definition must include at least one machine name.

Originator: Configuration Services

Explanation: The access definition must include the machine name of at least
one client workstation authorized by the definition to access logical units
(LUs) at the communications server.

User Response: Add a machine name.  Select the Machine name list, then select a
name from the Available for use list.  If the name you want to add does not
appear in the Available for use list, select Create.


ΓòÉΓòÉΓòÉ 3.22.4. ACS2161 ΓòÉΓòÉΓòÉ

ACS2161-E The access definition must include at least one user or group ID.

Originator: Configuration Services

Explanation: The access definition must include the ID of at least one user or
group authorized by the definition to access the communications server.

User Response: Add a user ID or a group ID.  Select the User/Group ID list,
then select an ID from the Available for use list.  If the user or group ID you
want to add does not appear in the Available for use list, select Create.


ΓòÉΓòÉΓòÉ 3.22.5. ACS2162 ΓòÉΓòÉΓòÉ

ACS2162-E The access definition must include at least one LU alias.

Originator: Configuration Services

Explanation: The access definition must include at least one alias for a
logical unit (LU) at the communications server to which access is authorized.

User Response: Add an alias from the list of available LU aliases. If the alias
you want to add does not appear in that list, select Create.


ΓòÉΓòÉΓòÉ 3.22.6. ACS2163 ΓòÉΓòÉΓòÉ

ACS2163-E This LU name is already being used in another LUA definition. Please
enter a unique LU name.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.22.7. ACS2164 ΓòÉΓòÉΓòÉ

ACS2164-W Multiple definitions have been selected for deletion.  Do you wish to
delete all of the selected definitions ?

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.22.8. ACS2165 ΓòÉΓòÉΓòÉ

ACS2165-E The Communications Manager/2 code server does not have the necessary
product files needed to support configuration name{30}. Install a configuration
at the code server that will support your redirected workstation.

where
name{30}        = feature name

Originator: Configuration Services - Advanced

User Response: One of the following must be done:

o A different configuration must be selected.

o A configuration must be installed on the code server workstation that
  supports the specified feature.


ΓòÉΓòÉΓòÉ 3.22.9. ACS2166 ΓòÉΓòÉΓòÉ

ACS2166-E The configuration name(8) is not valid to install on a LAN redirected
workstation.  Select a Communications Manager/2 version 1.1 configuration.

where
name(8)         = configuration file name

Originator: Configuration Services - Advanced

Explanation: The specified configuration was created with a prior version of
Communications Manager.  It cannot be installed on this workstation.

User Response: Do one of the following:

o Select a configuration that was created using Communications Manager/2
  version 1.1.

o Select a configuration that has been updated to the current level.

o Update the selected configuration on a Communications Manager single user
  workstation.


ΓòÉΓòÉΓòÉ 3.22.10. ACS2167 ΓòÉΓòÉΓòÉ

ACS2167-I The configuration name(8) specifies features that are not supported
on a LAN redirected workstation.  Communications Manager is installing the
configuration without those features.

where
name(8)         = configuration file name

Originator: Configuration Services - Advanced


ΓòÉΓòÉΓòÉ 3.22.11. ACS2168 ΓòÉΓòÉΓòÉ

ACS2168-E The X.25 link is configured for the D-channel.  The system detected
packet sizes that are greater than the maximum allowed for the D-channel, which
is 256.

Originator: Configuration Services

User Response: Select SVC/PVC packet sizes from the Additional parameters list,
and change the packet sizes to those valid for D-channel.


ΓòÉΓòÉΓòÉ 3.22.12. ACS2169 ΓòÉΓòÉΓòÉ

ACS2169-E The X.25 link is configured for D-channel. The frame values will be
overwritten with the valid values for D-channel.

Originator: Configuration Services

User Response: Do one of the following:

o Select OK to overwrite the frame values.

o Select Cancel to return to the X.25 Link Parameters panel.


ΓòÉΓòÉΓòÉ 3.22.13. ACS2170 ΓòÉΓòÉΓòÉ

ACS2170-E The current password is not valid.  Enter a valid master or service
password to complete this operation.

Originator: Keylock


ΓòÉΓòÉΓòÉ 3.22.14. ACS2171 ΓòÉΓòÉΓòÉ

ACS2171-E The master password cannot be changed with the service password.
Enter a valid master password to complete this operation.

Originator: Keylock


ΓòÉΓòÉΓòÉ 3.22.15. ACS2172 ΓòÉΓòÉΓòÉ

ACS2172-E Keylock allows you to protect a configuration against unauthorized or
accidental changes. The syntax: KEYLOCK config_name current_pswd /L /U /CM
new_master_pswd /CS new_service_pswd /EM /ES.  Refer to the manual for more
information.

Originator: Keylock


ΓòÉΓòÉΓòÉ 3.22.16. ACS2173 ΓòÉΓòÉΓòÉ

ACS2173-E The Keylock operation has completed successfully.

Originator: Keylock


ΓòÉΓòÉΓòÉ 3.22.17. ACS2174 ΓòÉΓòÉΓòÉ

ACS2174-E The local/remote service access point (SAP) address defined is not
divisible by 4.

Originator: Configuration Services

Explanation: The value assigned to the local or remote SAP must be divisible by
4.

User Response: Define a value for the local or remote SAP ranging from X'04' to
X'9C' that is divisible by 4.  Then retry the operation.


ΓòÉΓòÉΓòÉ 3.22.18. ACS2175 ΓòÉΓòÉΓòÉ

ACS2175-E The specified incoming call directory entry name{13} is currently
assigned to another virtual port.  Specify a unique incoming call directory
entry.

where
name{13}        = Incoming Call Directory Entry Name

Originator: Configuration Services

Explanation: Each incoming call directory entry can be assigned to only one
virtual port.

User Response: Do one of the following:

o Select or type the name of a different incoming call directory entry for this
  virtual port.

o Assign a different incoming call directory entry to the virtual port that is
  currently associated with the specified directory entry.

   - Reconfigure that virtual port using a different entry name.

   - Configure this virtual port with the specified incoming call directory
     entry.


ΓòÉΓòÉΓòÉ 3.22.19. ACS2177 ΓòÉΓòÉΓòÉ

ACS2177-E Unexpected return code rc(4) was received by ESLANX.

where
rc(4)           = Return code

Originator: Configuration Services - Advanced

Explanation: The attempt to update LAN Transport information was unsuccessful.

User Response: Use the following list of return codes to guide corrective
action:

o 11  -- Unsupported version of LAN transport.  ESLANX requires the level of
  LAN Transport supplied by Extended Services 1.0.

o 12  -- Error accessing IBMLVL.INI.

o 90  -- Disk is full.

o 513 -- Cannot load IBMLXCFG.DLL.  Ensure that this file is in the /IBMCOM/DLL
  subdirectory.

o OTHER -- Contact your local support personnel.


ΓòÉΓòÉΓòÉ 3.22.20. ACS2181 ΓòÉΓòÉΓòÉ

ACS2181-W ACDI device string profiles which were not associated with a COM port
were not upgraded.  These device string profiles are not included in the
upgraded version of the Communications Manager configuration file.

Originator: Configuration Services - Upgrade


ΓòÉΓòÉΓòÉ 3.22.21. ACS2204 ΓòÉΓòÉΓòÉ

ACS2204-E An internal program error has occurred.

Originator: Installation

User Response: Review the FFST/2 message and error logs for related entries.
Earlier messages and error logs will be helpful for problem determination.
Restart your computer and retry the operation you were attempting when the
problem occurred.


ΓòÉΓòÉΓòÉ 3.22.22. ACS2350 ΓòÉΓòÉΓòÉ

ACS2350-E ALERT:  Local X.25 subsystem software has recognized a failure in a
local adapter and has stopped all communications.

Originator: X.25 API

Explanation: This alert indicates adapter errors that flow across the NDIS
interface.  For example, this condition is reported when the B-channel for data
transmission is lost by the B-MAC.

User Response: Using subsystem management, check the link status for errors.
If the link status indicates Error Level 1 or Error Level 2, disconnect the
link and attempt to restart it.  If the link status indicates Adapter Error or
Adapter Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restart your computer and retry the operation you were
  attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.23. ACS2351 ΓòÉΓòÉΓòÉ

ACS2351-E ALERT:  The SDLC communication link has been deactivated because the
ISDN B-channel has been lost.

Originator: Synchronous Data Link Control (SDLC)

Explanation: This condition is reported by the Media Access Control (MAC)
driver when the B-channel for data transmission has been lost.

User Response: Access Subsystem Management and reactivate the link and the DLC.
Retry the operation you were attempting when the problem occurred.  If the
problem persists, note the time, date, and identification number of this
message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.24. ACS2353 ΓòÉΓòÉΓòÉ

ACS2353-E ALERT:  The local X.25 node received a frame reject that reset an
X.25 link.

Originator: X.25 API

Explanation: A locally generated frame reject (FRMR) was received during the
information-transfer state.  The FRMR was generated because the control field
was not valid or was unknown.

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.25. ACS2354 ΓòÉΓòÉΓòÉ

ACS2354-E ALERT: Local SNA could not establish a link.

Originator: SNA Communications Services (APPN)

Explanation: The Configuration Services component of SNA stopped XID
negotiation for link bring-up because the retry limit for link activation XID
exchanges was exceeded.  This retry limit is constant and is set high enough to
handle transient error conditions.

User Response: Review the formatted alert and locate the remote CP name.  This
field indicates the attempted destination node. Also, locate the sense data in
the formatted alert.  This field indicates the specific reason for the
connection failure. Refer to Problem Determination Guide for detailed
descriptions of sense data.  Finally, locate the link name and local adapter
number in the formatted alert.  These fields help to isolate the local
connection that failed.

o Often, this alert occurs for one or more of the following reasons:

   - Your local Communications Manager configuration was copied to another node
     or your configuration was copied from another node.  When this occurs,
     local token ring addresses and local node addresses are duplicated on
     multiple nodes, preventing all but one node from making the desired
     connection.  To correct this situation, ensure that all locally defined
     addresses and local node IDs are unique. For example, use the adapter's
     universally administered address when configuring LAN adapters.

   - If this is the first attempt to make the connection since configuration,
     ensure that the remote node has authorized the connection.  For example,
     AS/400 hosts often require configuration of remote node LAN adapter
     addresses before permitting connection. To correct this situation, contact
     the communications system programmer at the remote node.

o Access subsystem management and reactivate the link to the remote node.
  Retry the operation you were attempting when the problem occurred.  If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.26. ACS2355 ΓòÉΓòÉΓòÉ

ACS2355-E ALERT: The local node detected an error while attempting to open the
token-ring network adapter.

Originator: Token-Ring or Other LAN Type

Explanation: An error caused by a signal loss, by expiration of the insertion
timer, by a ring failure, or by a parameter request has prevented the
token-ring network adapter from entering into the network.

User Response: Check and secure the local token-ring node.  Restart your
computer and retry the operation you were attempting when the problem occurred.
If the problem persists, note the time, date and identification number of this
message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.27. ACS2356 ΓòÉΓòÉΓòÉ

ACS2356-E ALERT:  An RTS error was detected for an asynchronous communication
link.

Originator: Asynchronous Device Driver

Explanation: The local node detected an RTS error that may have resulted in the
loss of the communication link.  Request to send (RTS) was not dropped; clear
to send (CTS) was lost during transmission.

User Response: CTS was unexpectedly negated by local data communications
equipment (DCE) or by directly attached data terminal equipment (DTE).  Loss
may indicate a normal disconnection by remote DCE/DTE, an abnormal
disconnection within the telephone network, a malfunction of either the local
or remote DCE, or a loose cable.

o If loss of connection was unexpected, check and secure all connections
  between the local adapter and modem. Verify that the DCEs are functioning
  properly by running the appropriate modem diagnostics.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.28. ACS2357 ΓòÉΓòÉΓòÉ

ACS2357-E ALERT:  The local node detected a CTS error which deactivated the
SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The Clear-to-Send (CTS) modem signal was lost during data
transmission, resulting in the deactivation of the SDLC communication link.
Transmission of the frame was ended, and the SDLC communication link was
deactivated.

User Response: Check and secure the cable connections between the local adapter
and modem.

o Ensure that the modem and adapter are set up and operating correctly by
  running the appropriate diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.29. ACS2358 ΓòÉΓòÉΓòÉ

ACS2358-E ALERT: The local X.25 node either sent a packet that cleared a
switched, virtual circuit call or a restart packet that cleared all existing
virtual circuit calls and reset all existing permanent virtual circuits.

Originator: X.25 API

Explanation: The local DTE sent a supervisory packet that either cleared a
single virtual circuit call or restarted the packet level.

o Both of these conditions are X.25 API alerts generated by
  packet-layer-control layer 3.

User Response: Review the formatted alert and locate the packet type and the
DTE-originated cause code and diagnostic code.  This data will provide a more
precise indication of the failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.22.30. ACS2359 ΓòÉΓòÉΓòÉ

ACS2359-E ALERT:  The SDLC communication link was deactivated because of a
transmission failure at the local node.

Originator: Synchronous Data Link Control (SDLC)

Explanation: For SDLC connections, a transmit failure occurred because a
transmit interrupt was not received within a specified time interval after
issuing the transmit command to the adapter (transmit interrupt time-out
failure). For SDLC using ISDN connections, a transmit failure occurred because
the SDLC protocol driver did not receive a Transmit Confirmation from the Media
Access Control (MAC) driver within a specified time interval after issuing the
transmit command.

User Response: Review the formatted alert and locate the remote node.  Check
the DLC profile in the local configuration to ensure that it is compatible with
the remote node and with the desired type of use.

o Ensure that the adapter is configured correctly and that all cables are
  connected securely.

o Ensure that the adapter is set up and operating correctly by running the
  appropriate diagnostics.

o For SDLC connections, ensure that the modem is set up and operating correctly
  by running the appropriate diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23. ACS2360 through ACS2390 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.23.1. ACS2360 ΓòÉΓòÉΓòÉ

ACS2360-E ALERT:  The local X.25 node sent a frame reject that reset an X.25
link.

Originator: X.25 API

Explanation: The local node received a frame from the remote node during
information-transfer state that contained an information field (I-field) that
exceeded maximum length.  As a result, the local node sent back a frame reject
(FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, review the formatted
  alert in order to locate the remote node.  Perform the previous recommended
  actions on the remote node.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.2. ACS2361 ΓòÉΓòÉΓòÉ

ACS2361-E ALERT:  Lack of OS/2 resources at the local node prevented the X.25
subsystem from initializing properly.

Originator: X.25 API

Explanation: OS/2 was unable to create a thread as requested by local X.25
software.  Other active programs may be using too many OS/2 resources, or not
enough threads may be defined in the CONFIG.SYS file.

o This is an X.25 API alert generated by software and subsystem layer 4.

User Response: Check the CONFIG.SYS file to verify that the value specified in
the THREADS= statement is sufficient for the amount of activity required.  If
necessary, increase this value and restart your computer.  Retry the operation
you were attempting when the problem occurred.

o If the problem persists, free more OS/2 resources by ending any unnecessary
  active programs, or add additional RAM to the local workstation.  Often, this
  condition occurs when other active programs consume RAM or system semaphores
  required by local X.25 software.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.3. ACS2362 ΓòÉΓòÉΓòÉ

ACS2362-E ALERT: The SDLC communication link could not be established because
the remote node is not responding.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The remote node did not respond to the exchange station ID (XID)
commands that were sent by the local node.  The number of times that the XID
command was sent to the remote node has exceeded the configured XID repoll
count.

User Response: Review the formatted alert and locate the remote node.

o For SDLC connections, check and secure the cable connections between the
  local adapter and modem.  Verify that the local adapter and modem are
  functioning properly by running the appropriate diagnostics. Ensure that the
  remote node has not been powered off.  Check and secure the cable connections
  between the remote adapter and its modem.  Verify that the remote adapter and
  modem are functioning properly by running the appropriate diagnostics.

o For SDLC using ISDN connections, check and secure the cable connections
  between the local adapter and the network.  Check and secure the cable
  connections between the remote adapter and the network.  Verify that the
  local and remote adapters are functioning properly by running the appropriate
  diagnostics.

o For SDLC using ISDN connections with side stream dialing, ensure that the
  physical connection has been established using the Dial Utilities.

o Check the DLC profile in your configuration to ensure that it is compatible
  with the remote node and the desired type of use. Increase the value of the
  XID repoll count parameter in the DLC profile to allow the remote node a
  longer period of time in which to respond.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact the local support personnel at the remote node.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.4. ACS2363 ΓòÉΓòÉΓòÉ

ACS2363-E ALERT: The local node has detected an inactive link condition and has
deactivated the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The local node has not received any data from the remote node
within a specified time period and has deactivated the SDLC communication link.

User Response: Review the formatted alert and locate the remote node.

o For SDLC connections, check and secure the cable connections between the
  local adapter and modem.  Verify that the local adapter and modem are
  functioning properly by running the appropriate diagnostics. Ensure that the
  remote node has not been powered off.  Check and secure the cable connections
  between the remote adapter and its modem.  Verify that the remote adapter and
  modem are functioning properly by running the appropriate diagnostics.

o For SDLC using ISDN connections, check and secure the cable connections
  between the local adapter and the network.  Check and secure the cable
  connections between the remote adapter and the network.  Verify that the
  local and remote adapters are functioning properly by running the appropriate
  diagnostics.

o For SDLC using ISDN connections with side stream dialing, ensure that the
  physical connection has been established using the Dial Utilities.

o Check the DLC profile in the local configuration to ensure that it is
  compatible with the remote node, specifically with the non-return-to-zero
  inverted (NRZI) parameter (for SDLC connections only).  Ensure that the
  proper link station address is being used.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.5. ACS2364 ΓòÉΓòÉΓòÉ

ACS2364-E ALERT: The remote node sent a response that is not valid, which
deactivated the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: An information field (I-field) is not allowed with the response
that was received from the remote node; this usually means there is a software
error in the remote SDLC software.

User Response: Review the formatted alert and locate the remote node. Check the
DLC profile in the remote configuration to ensure that it is compatible with
the local node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.6. ACS2365 ΓòÉΓòÉΓòÉ

ACS2365-E ALERT:  Local SNA was unable to allocate sufficient resources to
establish an intermediate session.

Originator: SNA Communications Services (APPN)

Explanation: The Session Connection Manager component of SNA was unable to
allocate enough RAM to establish a session connector (an intermediate session
where the local node serves as a routing node) for implementing a requested
intermediate session.  The Session Connector Manager issued an UNBIND for the
session.

User Response: If this error condition appears occasionally, no response is
required.  This alert simply indicates that this network node is processing.
The transaction program that initiated the session was notified of the failure
and recovers according to its defined error recovery logic.

o If this error condition appears frequently, you may need to increase the RAM
  on this workstation.  Additional RAM permits more intermediate sessions and
  reduces the likelihood of this alert.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.7. ACS2367 ΓòÉΓòÉΓòÉ

ACS2367-E ALERT: The remote node sent a command or response that is unsupported
or not valid and the SDLC communication link was deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The remote node sent a command or response to the local node that
was either unrecognized, unsupported, or not valid in the local node's current
state; this usually indicates an error in the remote SDLC software.

User Response: Review the formatted alert and locate the remote node. Check the
DLC profile in the remote configuration to ensure that it is compatible with
the local node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.8. ACS2368 ΓòÉΓòÉΓòÉ

ACS2368-E ALERT: The local PC Network adapter is generating a continuous
carrier condition. The local adapter has been closed. Physical intervention may
be required.

Originator: PC Network

User Response: Check and secure all cable connections between your adapter and
the PC Network LAN.  Ensure that the adapter is operating correctly by running
the appropriate diagnostics. Access subsystem management and reactivate, if
necessary, the DLC and link for this adapter.  Retry the operation you were
attempting when the problem occurred.  If the problem persists, note the time,
date, and identification number of this message and contact your local support
personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.9. ACS2369 ΓòÉΓòÉΓòÉ

ACS2369-E ALERT:  An X.25 link has been disconnected because of an X.21
attachment error, or the X.25 link could not be established because the local
DCE was not ready.

Originator: X.25 API

Explanation: An error relating to an X.21 attachment has caused the X.25 link
to be disconnected (if connected), or there was a failure to successfully
establish a call because the local DCE was not ready.

o This is an X.25 API alert generated by physical-level layer 1.

User Response: Ensure that the correct X.21 cable is being used and secure all
cable connections between the local adapter and the X.25 network.

o Verify that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that the specified adapter is properly installed.

o Using subsystem management, check the link status for errors.  If the link
  indicates Error Level 1 or Error Level 2, disconnect the link and attempt to
  restart it. If the link status indicates Adapter Error or Adapter Access
  Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.10. ACS2370 ΓòÉΓòÉΓòÉ

ACS2370-E ALERT:  An error occurred while attempting to access the X.25 adapter
device driver.

Originator: X.25 API

Explanation: An X.25 Interface Co-Processor/2 device driver is inoperative.

User Response: Ensure that no X.25 application programs are using the X.25
adapter directly or through the device driver.

o Verify that the X.25 device driver ICARICIO.SYS has been loaded properly
  during execution of CONFIG.SYS.  Add the appropriate DEVICE= statement in
  CONFIG.SYS, or reinstall the X.25 subsystem if the file is not present.
  Restart your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, reinstall the software for the appropriate X.25 adapter.
  Restart your computer and retry the operation you were attempting when the
  problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.11. ACS2371 ΓòÉΓòÉΓòÉ

ACS2371-E ALERT:  An X.25 link has been disconnected or could not be
established because the local autocall unit is not responding.

Originator: X.25 API

Explanation: The local Transpac VX32 modem is not responding.

o This is an X.25 API alert generated by physical-level layer 1.

User Response: Ensure that the VX32 modem is powered on.  Ensure that the
correct modem cable is being used and secure all cable connections between the
adapter and the modem.

o If the modem could not establish a link, verify that the configured
  subscription number and link parameters are correct; review other X.25
  configuration data to ensure that it matches the physical configuration of
  the system (adapters, links, modems, and cables).

o Ensure that the specified adapter is installed.

o Using subsystem management, check the link status for errors.  If the link
  indicates Error Level 1 or Error Level 2, disconnect the link and attempt to
  restart it.  If the link status indicates Adapter Error or Adapter Access
  Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.12. ACS2372 ΓòÉΓòÉΓòÉ

ACS2372-E ALERT:  The receive sequence count (Nr) from the remote node was not
valid.  The SDLC communication link was deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The receive sequence count (Nr) received from the remote node does
not refer to either the next information frame (I-frame) to be transmitted or
to an I-frame that has been transmitted but not acknowledged.  This is often
because of an error in the remote SDLC software.

User Response: Review the formatted alert and locate the remote node. Ensure
that the DLC profile in the remote configuration file is compatible with the
local node and is suited for the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.13. ACS2373 ΓòÉΓòÉΓòÉ

ACS2373-E ALERT:  The local X.25 node sent a frame reject that reset an X.25
link.

Originator: X.25 API

Explanation: The local node received a frame from the remote node during
information-transfer state that was not valid or contained an unknown control
field.  As a result, the local node sent back a frame reject (FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using Subsystem Management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, review the formatted
  alert in order to locate the remote node.  Perform the previous recommended
  actions on the remote node.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.14. ACS2374 ΓòÉΓòÉΓòÉ

ACS2374-E ALERT: A problem on the token-ring network caused beaconing to
continue beyond the time allotted for the automatic recovery process. Because
the failing adapter could not be isolated, ALL adapters on the ring have been
closed. Physical intervention is required.

Originator: Token-Ring or Other LAN Type

Explanation: The Beaconing condition is most often caused by a cabling problem
at the multistation access unit (MAU), a defective cable, or a defective
adapter.

User Response: Ensure that there are no breaks in connections from ring-in (RI)
to one MAU, to ring-out (RO) from a second MAU.  Inspect all cables for breaks.
Run the appropriate diagnostics on all LAN adapters on the failing ring.

o Note the time, date, and identification number of this message and contact
  your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.15. ACS2375 ΓòÉΓòÉΓòÉ

ACS2375-E ALERT:  The receive sequence count (Nr) was not valid.  The local
node sent a frame reject (FRMR) and deactivated the LAN communication link.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Review the formatted alert and locate the remote station.  Run
the appropriate adapter diagnostics on the remote adapter. Access subsystem
management and reactivate, if necessary, the link for this adapter.  Retry the
operation you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.16. ACS2376 ΓòÉΓòÉΓòÉ

ACS2376-E ALERT:  Command or response received from a remote node was not valid
and deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: There is a communications protocol error in the qualified logical
link control (QLLC).  The error, which originated in the remote DTE, caused
either the switched virtual circuit (SVC) to be disconnected or the permanent
virtual circuit (PVC) to be inoperative.

o This is an X.25 DLC alert generated by logical-link-control layer 10.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Ensure that the currently active configuration
profile at the remote DTE is compatible with its X.25 connection and with the
configuration of the local DTE. Using subsystem management, check the link
status for errors.  If the link status indicates Error Level 1 or Error Level
2, disconnect the link and attempt to restart it.  If the link status indicates
Adapter Error or Adapter Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.17. ACS2377 ΓòÉΓòÉΓòÉ

ACS2377-E ALERT:  A protocol error was received from a remote DTE which may
have deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: There is a communications protocol error in the qualified logical
link control (QLLC).  The error, which originated in the remote DTE, caused
either the switched virtual circuit (SVC) to be disconnected or the permanent
virtual circuit (PVC) to be inoperative.

o This is an X.25 DLC alert generated by logical-link-control layer 10.

User Response: Review the formatted alert for more information and locate the
remote DTE.  This alert is usually generated as a result of a configuration
error at the remote DTE.  Ensure that the currently active configuration
profile at the remote DTE is compatible with its X.25 connection and with the
configuration of the local DTE. Using subsystem management, check the link
status for errors. If the link status indicates Error Level 1 or Error Level 2,
disconnect the link and attempt to restart it.  If the link status indicates
Adapter Error or Adapter Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.18. ACS2378 ΓòÉΓòÉΓòÉ

ACS2378-E ALERT:  The local node could not establish the SDLC connection within
the Data Set Ready (DSR) time-out period.

Originator: Synchronous Data Link Control (SDLC)

Explanation: This may have happened because the telephone number either was
incorrect or was not dialed in time, a busy signal was received, a critical
computer line was down, or a configuration error occurred.

User Response: Ensure that the correct telephone number was dialed. If the
number was correct, but more time is required for dialing, increase the value
of the DSR time-out parameter in the DLC profile.

o If the connection is not established, ensure that the communications lines
  are operating.

o Check your modem to verify that it is set up and operating properly by
  running the appropriate modem diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Redial the
  telephone number when prompted.  Retry the operation you were attempting when
  the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.19. ACS2379 ΓòÉΓòÉΓòÉ

ACS2379-E ALERT:  A received information field (I-field) exceeded the maximum
length.  The local node sent a frame reject (FRMR) and deactivated the LAN
communication link.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Review the formatted alert and locate the remote station. Run
the appropriate adapter diagnostics on the remote adapter. Access subsystem
management and reactivate, if necessary, the DLC  for this adapter.  Retry the
operation you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.20. ACS2380 ΓòÉΓòÉΓòÉ

ACS2380-E ALERT:  An unsupported command was received.  The local node sent a
frame reject (FRMR) and deactivated the LAN communication link.

Originator: PC Network, ETHERAND, or Token-Ring

User Response: Review the formatted alert and locate the remote station.  Run
the appropriate adapter diagnostics on the remote adapter. Access subsystem
management and reactivate, if necessary, the link for this adapter.  Retry the
operation you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel. Your local support
  personnel should run adapter diagnostics at the remote station.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.21. ACS2381 ΓòÉΓòÉΓòÉ

ACS2381-E ALERT:  A command with an unsupported information field (I-field) was
received.  The local node sent a frame reject (FRMR) and deactivated the LAN
communication link.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Review the formatted alert and locate the remote station. Run
the appropriate adapter diagnostics on the remote adapter. Access subsystem
management and reactivate, if necessary, the link for this adapter.  Retry the
operation you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.22. ACS2382 ΓòÉΓòÉΓòÉ

ACS2382-E ALERT:  X.25 software detected the failure of a logical or physical
X.25 adapter.

Originator: X.25 API

Explanation: The X.25 API detected an adapter error.

User Response: Check and secure all connections between the local adapter and
the modem.  Verify that the local adapter and modem are functioning properly by
running the appropriate diagnostics.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.23. ACS2383 ΓòÉΓòÉΓòÉ

ACS2383-E ALERT:  The remote node is not responding to the commands being sent
by the local node.  The SDLC communication link was deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The remote node did not respond to the non-exchange station ID
(non-XID) commands that were sent by the local node. The number of times that
the command was sent to the remote node has exceeded the configured non-XID
repoll count.

User Response: Review the formatted alert and locate the remote node.

o For SDLC connections, check and secure the cable connections between the
  local adapter and modem.  Verify that the local adapter and modem are
  functioning properly by running the appropriate diagnostics. Ensure that the
  remote node has not been powered off.  Check and secure the cable connections
  between the remote adapter and its modem.  Verify that the remote adapter and
  modem are functioning properly by running the appropriate diagnostics.

o For SDLC using ISDN connections, check and secure the cable connections
  between the local adapter and the network.  Check and secure the cable
  connections between the remote adapter and the network.  Verify that the
  local and remote adapters are functioning properly by running the appropriate
  diagnostics.

o For SDLC using ISDN connections with side stream dialing, ensure that the
  physical connection has been established using the Dial Utilities.

o Check the DLC profile in the local configuration to ensure that it is
  compatible with the remote node and the desired type of use. Increase the
  value of the Non-XID repoll count parameter in the DLC profile to allow the
  remote node a longer period of time in which to respond.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.24. ACS2384 ΓòÉΓòÉΓòÉ

ACS2384-E ALERT:  The local node detected an error while attempting to activate
the SDLC Data Link Control (DLC).

Originator: Synchronous Data Link Control (SDLC)

Explanation: One of the following errors was detected while attempting to
activate the SDLC DLC:

o For SDLC connections:

   - The SDLC device driver was not loaded because a DEVICE= statement for the
     device driver is not in the CONFIG.SYS file.

   - The SDLC interrupt levels (IRQ 3 and IRQ 4) could not be accessed in the
     mode (Shareable or Non-shareable) specified in the DEVICE= statement in
     the CONFIG.SYS file.

   - The specified adapter is not installed.

   - The specified adapter is not functioning properly.

o For SDLC using ISDN connections:

   - The SDLC using ISDN device drivers were not loaded because a DEVICE=
     statement for the device drivers was not in the CONFIG.SYS file.

   - The SDLC using ISDN device drivers were not loaded because the PROTMAN.OS2
     file was not loaded.

   - The CONFIG.SYS file did not contain a RUN= statement for NETBIND.EXE.

   - The PROTOCOL.INI file could not be found or did not contain the correct
     BINDINGS= statement for the SDLC using ISDN device driver.

User Response:

o For SDLC connections, ensure that:

   - The CONFIG.SYS file contains a DEVICE= statement for the SDLC device
     driver.

   - There are no conflicts with other devices that prevent the SDLC interrupt
     levels from being accessed in the specified mode (Shareable or
     Non-shareable).

   - The specified adapter is properly installed.

   - The specified adapter is functioning properly.  Refer to the adapter
     documentation for additional information.

o For SDLC using ISDN connections, ensure that:

   - The CONFIG.SYS file contains a DEVICE= statement for the SDLC using ISDN
     device drivers.

   - The CONFIG.SYS file contains a DEVICE= statement for the PROTMAN.OS2 file.

   - The CONFIG.SYS file contains a RUN= statement for NETBIND.EXE.

   - The PROTOCOL.INI file exists and contains the correct BINDINGS= statement
     for the SDLC using ISDN device driver.

o Make the appropriate changes and restart your computer.  Retry the operation
  you were attempting when the problem occurred.  If the problem persists, note
  the time, date, and identification number of this message and contact your
  local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.25. ACS2385 ΓòÉΓòÉΓòÉ

ACS2385-E ALERT: Local SNA could not establish a link.

Originator: SNA Communications Services (APPN)

Explanation: The Configuration Services component of SNA terminated XID
negotiation for link bring-up because the remote node violated protocols for
XID exchange (that is, an XID state check).

User Response: Review the formatted alert and locate the link name. If the link
name is IMPLICIT, consider this alert to be informational because the failed
link was configured at a remote node.  A corresponding alert was generated at
the remote node and the problem should be resolved there.

o If the link name is IMPLICIT, the link was defined locally. Locate the sense
  data from the formatted alert and refer to Problem Determination Guide for a
  detailed description of sense data. Correct the problem as indicated by the
  sense data.

o Access subsystem management and reactivate the link to the remote node.
  Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.26. ACS2386 ΓòÉΓòÉΓòÉ

ACS2386-E ALERT:  Local SNA received unsupported network management data.

Originator: SNA Communications Services (APPN)

Explanation: The Management Services component of SNA detected a protocol error
on a received Multiple Domain Support Message Unit (MDS MU).  The MDS MU was
ignored.

o MDS MUs are generated by SNA and by user MS applications to transport various
  Management Services data.  Consequently, the MDS MU prompting this alert may
  refer to an error in the system MS software or application MS software.  The
  unsupported MDS MU has been logged in Additional Data section of an
  associated error log entry.

User Response: This alert does not reflect any connectivity problem; it
indicates that a network management application (local or remote) is
functioning improperly.  If you do not want to locate the offending
application, treat this alert as informational.

o Otherwise, locate the sense data in the formatted alert and examine the
  descriptions provided in Problem Determination Guide.  This sense data
  provides the best indication of the cause of the error and its severity. In
  general, sense data beginning with 08A8, 08A9, CCCC, or FFFF tends to be
  transient routing and transaction errors that are logged for informational
  purposes only.  However, this may not always be the case. For example, the
  sense data 08A80003 represents an error because of an unknown application.
  This error can be considered informational if the intended destination
  application has not registered itself to local SNA yet, or it may be
  considered more serious if the application really does not exist anywhere in
  the network.  The first case signifies a timing race condition in the
  network; the latter case represents a serious application error.  SNA cannot
  distinguish the degree of severity, so it always generates an alert.

o Sense data beginning with 080C, 086C, 086D, 086F, 0870, or 08AA tends to be
  serious protocol errors in the MDS MU.  The unsupported MDS MU contains GDS
  variables for the source and destination nodes.  Refer to IBM Systems Network
  Architecture Network Product Formats for details concerning parsing the MDS
  MU.  Locating the source node should assist in isolating the offending MS
  application.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.27. ACS2387 ΓòÉΓòÉΓòÉ

ACS2387-E ALERT:  A local token-ring adapter is indicating a hardware failure.

Originator: Token-Ring or Other LAN Type

User Response: Ensure that the specified adapter is operating correctly by
running the appropriate diagnostics.  Restart your computer and retry the
operation you were attempting when the problem occurred. If the problem
persists, note the time, date, and identification number of this message and
contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.28. ACS2388 ΓòÉΓòÉΓòÉ

ACS2388-E ALERT:  An unsupported command was sent by the local DTE or the X.25
network that may have deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: As a result, the remote DTE sent a frame reject (FRMR) back to the
local X.25 DTE.

o This is an X.25 DLC alert generated by logical-link-control layer 6.

User Response: Review the formatted alert for more information and locate the
remote DTE.  Ensure that the currently active configuration profile at the
remote DTE is compatible with its X.25 connection and with the configuration of
the local DTE.

o Using subsystem management, check the link status for errors. If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.29. ACS2389 ΓòÉΓòÉΓòÉ

ACS2389-E ALERT:  Data has been discarded because the local asynchronous
communications application did not remove data from the receive buffer (which
is full).

Originator: Asynchronous Device Driver

Explanation: Data recovery because of this condition is completely the
responsibility of the application program.

User Response: Change the connection to a lower baud rate. Retry the operation
you were attempting when the problem occurred. If the problem persists, note
the time, date, and identification number of this message and contact your
local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.23.30. ACS2390 ΓòÉΓòÉΓòÉ

ACS2390-E ALERT:  An unexpected OS/2 function call or 802.2 LAN transport error
has closed the local logical LAN adapter.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24. ACS2391 through ACS2421 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.24.1. ACS2391 ΓòÉΓòÉΓòÉ

ACS2391-E ALERT:  The local X.25 node sent a frame reject that reset an X.25
link.

Originator: X.25 API

Explanation: The local node received a frame from the remote node during
information-transfer state that has an information field that was not valid. As
a result, the local node sent back a frame reject (FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, review the formatted
  alert in order to locate the remote node.  Perform the previous recommended
  actions on the remote node.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.2. ACS2392 ΓòÉΓòÉΓòÉ

ACS2392-E ALERT: A hardware failure on the PC Network caused a continuous
carrier condition to occur beyond the allotted time. The failure has closed the
local adapter. Physical intervention is required.

Originator: PC Network

Explanation: The continuous carrier condition is most often caused by an
improperly terminated network, a defective cable, or a defective adapter.

User Response: Inspect the network for termination and cabling problems. Run
the appropriate diagnostics on all LAN adapters on the failing network.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.3. ACS2393 ΓòÉΓòÉΓòÉ

ACS2393-E ALERT:  While initializing, local token-ring access was rejected by a
remote LAN administrator.

Originator: Token-Ring or Other LAN Type

User Response: This error is the result of your workstation being prevented
from accessing the LAN because of the actions of a remote LAN administrator.
Note the time, date, and identification number of this message and contact your
LAN administrator to understand why the remove command was issued against the
local adapter.  Once the problem is corrected, access subsystem management and
reactivate, if necessary, the DLC and the link for this adapter.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.4. ACS2394 ΓòÉΓòÉΓòÉ

ACS2394-E ALERT:  A transmission problem at the local node has deactivated the
SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: A transmitted frame was ended automatically because of a direct
memory access (DMA) underrun.  The DMA channel was too slow in supplying the
adapter with bytes of data to be transmitted.

User Response: Verify that the local adapter is functioning properly by running
the appropriate adapter diagnostics.  Ensure that the proper arbitration level
is assigned to the adapter.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.5. ACS2395 ΓòÉΓòÉΓòÉ

ACS2395-E  ALERT:  The local X.25 node received a diagnostic packet from the
X.25 network indicating either a protocol violation on the part of the local
node or diagnostic information concerning the X.25 network.

Originator: X.25 API

Explanation: The local DTE received a diagnostic packet from the X.25 network
indicating either a protocol violation on the part of the local DTE or
diagnostic information concerning the X.25 network.

o This is an X.25 API alert generated by packet-layer-control layer 3.

User Response: Review the formatted alert and locate the diagnostic code. This
code provides a more precise indication of the failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.6. ACS2396 ΓòÉΓòÉΓòÉ

ACS2396-E ALERT:  Local X.25 DLC software detected a software problem and
stopped.

Originator: X.25 Data Link Control

Explanation: This is an X.25 DLC alert generated by logical-link-control layer.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, note the time,
date, and identification number of this message and contact your local support
personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.7. ACS2397 ΓòÉΓòÉΓòÉ

ACS2397-E ALERT:  The token-ring network adapter failed to initialize because
of a lobe cable problem between the local adapter and the multistation access
unit (MAU).

Originator: Token-Ring or Other LAN Type

User Response: Check and secure all cable connections between your adapter and
the MAU.  Ensure that the adapter is operating correctly by running the
appropriate diagnostics.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem still persists, note the time, date, and identification number
  of this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.8. ACS2398 ΓòÉΓòÉΓòÉ

ACS2398-E ALERT: Local SNA received a protocol error on an APPN request.

Originator: SNA Communications Services (APPN)

Explanation: The Directory Services component of SNA detected a protocol error
on a received LOCATE request.  LOCATE requests are sent by APPN nodes to
determine the location of a remote node before establishing a session.

o The LOCATE request did not include a FIND request, which was either left off
  by the originator of the LOCATE request or deleted by the propagator of the
  LOCATE request.  The erroneous LOCATE request was ignored.

User Response: This alert does not reflect any connectivity problem for the
local node; it identifies a remote APPN node that has improperly solicited
information from the local node.  If you do not want to locate the offending
node, treat this alert as informational.

o Otherwise, review the formatted alert and locate the adjacent CP name. This
  name should help you isolate the offending node.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.9. ACS2399 ΓòÉΓòÉΓòÉ

ACS2399-E ALERT:  A remove command was received from a remote LAN administrator
that has forced the local token-ring adapter to exit from the ring.

Originator: Token-Ring or Other LAN Type

User Response: Note the time, date, and identification number of this message
and contact your LAN administrator in order to understand why the remove
command was issued against the local adapter.

o Once the problem is corrected, access subsystem management and reactivate, if
  necessary, the DLC and the link for this adapter. Retry the operation you
  were attempting when the problem occurred. If the problem still persists,
  note the time, date, and identification number of this message and contact
  your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.10. ACS2400 ΓòÉΓòÉΓòÉ

ACS2400-E ALERT:  A LAN link time-out has occurred because the remote node is
not responding.

Originator: PC Network, ETHERAND, or Token-Ring

Explanation: The retransmission poll count (8) has been reached before a
response was received from the remote node.

User Response: Review the formatted alert and locate the remote node. Ensure
that the specified remote node has not been powered off. Check the connections
between the remote node and the LAN. Check the FFST/2 error log at the remote
node for related failures and correct any related problems.

o If your workstation and the remote node are on separate networks and are
  connected by a bridge, verify that the bridge software is operational.

o If none of the preceding actions apply to the problem, increase the locally
  configured Group 1 response timer-T1.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.  Then contact your LAN administrator.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.11. ACS2401 ΓòÉΓòÉΓòÉ

ACS2401-E ALERT: Local SNA could not establish a link.

Originator: SNA Communications Services (APPN)

Explanation: The Configuration Services component of SNA received an
unacceptable SET MODE command; the SET MODE command was ignored.

User Response: Review the formatted alert and locate the link name.

o If the link name is IMPLICIT, consider this alert to be informational because
  the failed link was configured at a remote node.  A corresponding alert was
  generated at the remote node and the problem should be resolved there.

o If the link name is IMPLICIT, the link was defined locally.  Locate the sense
  data from the formatted alert and refer to Problem Determination Guide for a
  detailed description of sense data.  Correct the problem as indicated by the
  sense data.

o Access subsystem management and reactivate the link to the remote node.
  Retry the operation you were attempting when the problem occurred.  If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.12. ACS2403 ΓòÉΓòÉΓòÉ

ACS2403-E ALERT:  The Asynchronous communication link was not established
because of a local DCE or a directly attached DTE.

Originator: Asynchronous Device Driver

Explanation: Request to send (RTS) was raised, but a time-out occurred while
waiting for a clear to send (CTS) signal to be asserted.

User Response: Check and secure all cables between the local adapter and modem.
Verify that the DCE or the directly attached DTE is functioning properly.  Run
the appropriate adapter and modem diagnostics.

o Repeat this procedure at the remote node and modem.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.13. ACS2404 ΓòÉΓòÉΓòÉ

ACS2404-E ALERT: A Clear-to-Send (CTS) time-out at the local node has
deactivated the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The Request-to-Send (RTS) modem signal was raised to transmit, but
a time-out occurred while waiting for the Clear-to-Send (CTS) modem signal to
be raised.

User Response: Check and secure the cable connections between the local adapter
and modem.

o Review the formatted alert and locate the remote node.  Check the DLC profile
  in the local configuration to ensure that it is compatible with the remote
  node and the desired type of use.

o Ensure that the local adapter and modem are set up and operating correctly by
  running the appropriate diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.14. ACS2405 ΓòÉΓòÉΓòÉ

ACS2405-E ALERT: The local PC Network adapter did not detect the carrier signal
on the network and closed the adapter.

Originator: PC Network

User Response: Check and secure all cable connections between your adapter and
the PC Network LAN.

o Run the appropriate diagnostics on the local adapter.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter. Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.15. ACS2406 ΓòÉΓòÉΓòÉ

ACS2406-E ALERT: The local X.25 node sent a reset request packet that reset all
virtual circuits on a link.

Originator: X.25 API

Explanation: The local DTE sent a reset request packet that reset all virtual
circuits on a link.

o This is an X.25 API alert generated by packet-layer-control layer 3.

User Response: Review the formatted alert and locate the DTE-originated cause
code and diagnostic code.  These codes provide a more precise indication of the
failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.16. ACS2407 ΓòÉΓòÉΓòÉ

ACS2407-E ALERT:  The PC Network or ETHERAND communication link was not
established because the remote station did not respond.

Originator: A local PC Network or ETHERAND

Explanation: The remote did not respond to the local attempt to initiate
asynchronous balanced mode extended.

User Response: Review the formatted alert and locate the remote station.
Ensure that the specified remote node has not been powered off and the remote
software is still operation.  Check and secure all the connections between the
remote adapter and the LAN.

o Check the FFST/2 error log in the remote node for related failures and
  correct any related problems.

o Access subsystem management and reactivate, if necessary, the link for this
  adapter. Retry the operation you were attempting when the problem occurred.
  If the problem persists, note the time, date, and identification number of
  this message; then contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.17. ACS2408 ΓòÉΓòÉΓòÉ

ACS2408-E ALERT: Local SNA received a protocol error on an APPN request.

Originator: SNA Communications Services (APPN)

Explanation: A Session Connector component of SNA detected a protocol error on
a received UNBIND request.  The Session Connector signalled the Session
Connector Manager to UNBIND this intermediate session.  An intermediate session
is a session that does not begin or terminate at your node; rather, your node
serves as a routing node.

User Response: This alert does not reflect any connectivity problem for the
local node; it identifies a remote APPN node that has improperly solicited
action from the local node.  If you do not want to locate the offending node,
treat this alert as informational.

o Otherwise, review the formatted alert and locate the destination LU name.
  Trace all APPC activity with this LU to identify the offending remote node.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.18. ACS2409 ΓòÉΓòÉΓòÉ

ACS2409-E ALERT:  The X.25 virtual circuit was deactivated because the remote
DTE did not respond to a command.

Originator: X.25 Data Link Control

Explanation: The local X.25 DLC has retried a command the maximum number of
times without receiving a response from the remote DTE.

o This is an X.25 DLC alert generated by logical-link-control layer 3.

User Response: Review the formatted alert and locate the remote DTE.  Ensure
that the remote DTE is powered on and that all cable connections between the
remote DTE and the X.25 network are secure. Ensure that the currently active
configuration profile at the remote DTE is compatible with both its X.25
connection and with the configuration of the local DTE.  Especially, check the
retry count and the configured time-out for the remote DTE.  Using subsystem
management, check the link status for errors.  If the link status indicates
Error Level 1 or Error Level 2, disconnect the link and attempt to restart it.
If the link status indicates Adapter Error or Adapter Access Error, contact
your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.19. ACS2410 ΓòÉΓòÉΓòÉ

ACS2410-E ALERT: The local PC Network adapter did not detect its own carrier
signal as it attempted to enter into the network. The adapter has been closed.

Originator: PC Network

User Response: Check and secure all cable connections between the local adapter
and the PC Network.  For baseband, ensure that the wrap plug has not been
removed.

o Check the local FFST/2 message and error logs for related adapter open
  failure indications; these failures would have occurred during CONFIG.SYS
  execution.  If the FFST/2 logs contain no relevant information, review the
  contents of the file LANTRAN.LOG in the \IBMCOM subdirectory. Correct any
  indicated problems.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.20. ACS2411 ΓòÉΓòÉΓòÉ

ACS2411-E ALERT: Local SNA has received an internal error.

Originator: SNA Communications Services (APPN)

Explanation: The Topology Database Manager component of SNA has detected a wrap
condition for the Resource Sequence Number (RSN) field associated with a
Topology Database Update (TDU).  TDUs flow between control points (CPs) to
exchange updates in the network topology.  The TDU in error was ignored.

o This wrap condition should not occur unless an internal Topology Database
  Manager error has occurred.

User Response: Your node has detected an internal SNA error in your Topology
Database Manager component.  It is recommended that you reinitialize
Communications Manager by exiting and then restarting it.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.21. ACS2412 ΓòÉΓòÉΓòÉ

ACS2412-E ALERT: Local X.25 DLC detected a software problem and stopped.

Originator: X.25 Data Link Control

Explanation: This is an X.25 DLC alert generated by logical link control.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, note the time,
date, and identification number of this message and contact your local support
personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.22. ACS2413 ΓòÉΓòÉΓòÉ

ACS2413-E ALERT: The remote DTE sent a reset or clear packet that may have
deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: This is an X.25 DLC alert generated by logical link control.

User Response: Review the formatted alert; especially review the cause code and
diagnostic code.  Using subsystem management, check the link status for errors.
If the link status indicates Error Level 1 or Error Level 2, disconnect the
link and attempt to restart it.  If the link status indicates Adapter Error or
Adapter Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.23. ACS2414 ΓòÉΓòÉΓòÉ

ACS2414-E ALERT:  The local twinaxial adapter had a hardware failure.

Originator: Twinaxial Data Link Control

Explanation: The twinaxial adapter either is not seated properly or has
experienced an internal failure.

User Response: Ensure that the adapter is properly installed and that it is
functioning properly.  Run the appropriate adapter diagnostics.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.24. ACS2415 ΓòÉΓòÉΓòÉ

ACS2415-E ALERT:  The host unexpectedly deactivated the twinaxial communication
link.

Originator: Twinaxial Data Link Control

User Response: Determine whether or not the host system is active. If the host
system is active, access subsystem management and reactivate the link for this
adapter.  Retry the operation you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.25. ACS2416 ΓòÉΓòÉΓòÉ

ACS2416-E ALERT: An internal software error at the local node has deactivated
the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The SDLC software has detected an internal error or inconsistency
that has caused the SDLC communication link to be deactivated.

o This alert is placed only in the local FFST/2 error log; it is not forwarded
  from the local node.

User Response: For SDLC connections, check and secure the cable connections
between the local adapter and modem.  Verify that the local adapter and modem
are functioning properly by running the appropriate diagnostics.

o For SDLC using ISDN connections, check and secure the cable connections
  between the local adapter and the network.  Verify that the local adapter is
  functioning properly by running the appropriate diagnostics.

o For SDLC using ISDN connections with side stream dialing, ensure that the
  physical connection has been established using the Dial Utilities.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.26. ACS2417 ΓòÉΓòÉΓòÉ

ACS2417-E ALERT:  Local twinaxial software detected a permanent software
problem and stopped.

Originator: Twinaxial Data Link Control

Explanation: The unexpected software-program error occurred in the twinaxial
DLC.

User Response: Access subsystem management and reactivate, if necessary, the
DLC and the link.  Retry the operation you were attempting when the problem
occurred.  If the problem persists, note the time, date, and identification
number of this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.27. ACS2418 ΓòÉΓòÉΓòÉ

ACS2418-E ALERT:  The local node detected a DSR error which may have
deactivated the asynchronous communication link.

Originator: Asynchronous Device Driver

Explanation: Data Set Ready (DSR) was negated unexpectedly by a local DCE or by
a directly attached DTE.

User Response: Loss of connection may indicate a normal disconnection by a
remote DCE/DTE, an abnormal disconnection within the telephone network, a
malfunction of either a local or a remote DCE, or a loose cable.

o If the loss of connection was unexpected, verify that the local cables are
  attached securely and that the DCEs are functioning properly.  Ensure that
  the local modem is powered on and run the appropriate modem diagnostics.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.28. ACS2419 ΓòÉΓòÉΓòÉ

ACS2419-E SDLC ALERT: The local node has detected the loss of the Data Set
Ready (DSR) modem signal and has deactivated the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: After the SDLC connection was established successfully, the Data
Set Ready (DSR) modem signal was lost, making it impossible to send or receive
data.

User Response: Ensure that the local modem is set up, powered on, and
functioning correctly.  Check and secure all local cable connections. Run the
appropriate diagnostics on the local modem and adapter.

o Review the formatted alert and locate the remote node.  Ensure that the
  remote node is powered on.  Ensure that the remote modem is set up, powered
  on, and functioning correctly.  Check and secure all remote cable
  connections.  Run the appropriate diagnostics on the remote modem and
  adapter.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.29. ACS2420 ΓòÉΓòÉΓòÉ

ACS2420-E ALERT:  The remote node sent out a frame reject (FRMR) after
receiving an incorrect Nr (receive sequence count) from the local node.  The
communication link has been deactivated.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Run the appropriate adapter diagnostics on the local adapter.
Access subsystem management and reactivate, if necessary, the link for this
adapter.  Retry the operation you were attempting when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.24.30. ACS2421 ΓòÉΓòÉΓòÉ

ACS2421-E ALERT:  The remote LAN node sent out a frame reject (FRMR) after
receiving an information field (I-field) that exceeded the maximum length from
the local node.  The communication link has been deactivated.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Usually, this condition occurs when the remote station is PU
Type 2.0 and link parameters are not negotiable. Ensure that the adapter
configuration for both nodes contain a comparable value for the maximum I-field
parameter.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25. ACS2422 through ACS2452 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.25.1. ACS2422 ΓòÉΓòÉΓòÉ

ACS2422-I ALERT: The local node timed out while waiting for a Disconnect
command from the remote node.  The SDLC communication link has been
deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The remote node did not respond to a request to disconnect the
link within a specified time interval.

o This alert is placed only in the local FFST/2 error log; it is not forwarded
  from the local node.

User Response: Review the formatted alert and locate the remote node.

o For SDLC connections, check and secure the cable connections between the
  local adapter and modem.  Verify that the local adapter and modem are
  functioning properly by running the appropriate diagnostics. Ensure that the
  remote node has not been powered off.  Check and secure the cable connections
  between the remote adapter and its modem.  Verify that the remote adapter and
  modem are functioning properly by running the appropriate diagnostics.

o For SDLC using ISDN connections, check and secure the cable connections
  between the local adapter and the network.  Check and secure the cable
  connections between the remote adapter and the network.  Verify that the
  local and remote adapters are functioning properly by running the appropriate
  diagnostics.

o For SDLC using ISDN connections with side stream dialing, ensure that the
  physical connection has been established using the Dial Utilities.

o Check the DLC profile in the local configuration and ensure that it is
  compatible with the remote node and with the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.2. ACS2423 ΓòÉΓòÉΓòÉ

ACS2423-E ALERT:  The remote node sent out a frame reject (FRMR) after
receiving an unsupported command from the local node. The LAN communication
link has been deactivated.

Originator: PC Network, ETHERAND, or Token-Ring

User Response: Run the appropriate adapter diagnostics on the local adapter.
Access subsystem management and reactivate, if necessary, the DLC and  the link
for this adapter.  Retry the operation you were attempting when the problem
occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.3. ACS2424 ΓòÉΓòÉΓòÉ

ACS2424-E ALERT:  The local PC Network or Ethernet Network adapter did not
initialize while attempting to enter into the network.

Originator: A local PC Network or ETHERAND

User Response: Check and secure all cable connections between the local adapter
and the PC Network or Ethernet Network.

o Run the appropriate diagnostics on the local adapter.  Access subsystem
  management and reactivate, if necessary, the DLC and the link for this
  adapter.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.4. ACS2425 ΓòÉΓòÉΓòÉ

ACS2425-E ALERT: An error was received from the remote DTE that may have
deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: An error was received from the remote DTE which may have resulted
in the permanent deactivation of the X.25 virtual circuit. The remote DTE sent
a frame reject (FRMR), but did not specify a reason. No information field
(I-field) was included in the FRMR response.

o This is an X.25 DLC alert generated by logical link control.

User Response: Review the formatted alert and locate the remote DTE. Ensure
that the currently active configuration profile at the remote DTE is compatible
with both its X.25 connection and with the configuration of the local DTE.
Using subsystem management, check the link status for errors.  If the link
status indicates Error Level 1 or Error Level 2, disconnect the link and
attempt to restart it. If the link status indicates Adapter Error or Adapter
Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.5. ACS2426 ΓòÉΓòÉΓòÉ

ACS2426-E ALERT:  The remote node sent out a frame reject (FRMR) after
receiving a command with an unsupported information field (I-field) from the
local node.  The LAN communication link has been deactivated.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Run the appropriate adapter diagnostics on the local adapter.
Access subsystem management and reactivate, if necessary, the DLC and the link
for this adapter.  Retry the operation you were attempting when the problem
occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.6. ACS2427 ΓòÉΓòÉΓòÉ

ACS2427-E ALERT: The SDLC communication link could not be established because
of a lack of operating system resources at the local node.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The operating system was unable to create a thread as requested by
local SDLC software.

User Response: Check the CONFIG.SYS file to verify that the value specified in
the THREADS= statement is sufficient for the amount of activity required.  If
necessary, increase this value and restart your computer.

o You can free more resources by ending any unnecessary active programs.

o If the problem persists, add additional RAM to the local workstation, and
  restart your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.7. ACS2428 ΓòÉΓòÉΓòÉ

ACS2428-E ALERT:  Lack of OS/2 resources at the local node ended all twinaxial
communications.

Originator: Twinaxial Data Link Control

Explanation: OS/2 was unable to create a thread or allocate memory as requested
by local Twinaxial software.

User Response: Check the CONFIG.SYS file to verify that the value specified in
the THREADS= statement is sufficient for the amount of activity required.  If
necessary, increase this value and restart your computer.

o You can free more resources by ending any unnecessary active programs. Access
  subsystem management and reactivate, if necessary, the link and the DLC for
  this adapter.

o If the problem persists, add additional RAM to the local workstation and
  restart your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.8. ACS2429 ΓòÉΓòÉΓòÉ

ACS2429-E ALERT:  An X.25 link failure has been detected.

Originator: X.25 API

Explanation: The remote node sent an unexpected DISCONNECT command during link
initialization or during information transfer state.

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.9. ACS2430 ΓòÉΓòÉΓòÉ

ACS2430-E ALERT:  The token-ring communication link was not established because
the remote node did not respond.

Originator: Token-Ring, or Other LAN Type

Explanation: The remote did not respond to the local attempt to initiate
asynchronous balanced mode extended.

User Response: Review the formatted alert and locate the remote station.
Ensure that the specified remote node has not been powered off and the remote
software is still operation.  Check and secure all the connections between the
remote adapter and the LAN.

o Access subsystem management and reactivate, if necessary, the DLC and the
  link for this adapter.  Retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.10. ACS2431 ΓòÉΓòÉΓòÉ

ACS2431-E ALERT: The local DTE or the X.25 network generated a protocol error
that may have deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: The local DTE or the X.25 network generated a protocol error that
may have resulted in the permanent deactivation of the X.25 virtual circuit.
Either the local DTE or the X.25 network caused a command to be sent to the
remote DTE with an information field (I-field).  However, the command should
not have included an I-field. As a result, a frame reject (FRMR) was sent to
local X.25 software.

o This is an X.25 DLC alert generated by logical link control.

User Response: Review the formatted alert for more information and locate the
remote DTE.  Ensure that the currently active configuration profile at the
local DTE is compatible with both its X.25 connection and with the
configuration of the remote DTE. Using subsystem management, check the link
status for errors.  If the link status indicates Error Level 1 or Error Level
2, disconnect the link and attempt to restart it.  If the link status indicates
Adapter Error or Adapter Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.11. ACS2432 ΓòÉΓòÉΓòÉ

ACS2432-E ALERT:  There is not enough system memory available to allocate the
necessary storage to create a new local logical LAN adapter instance.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Ensure that the MEMMAN parameter in the local CONFIG.SYS file is
set to SWAP, MOVE.  If it is not, correct the problem and restart your
computer.

o You can free more resources by ending any unnecessary active programs. Access
  subsystem management and reactivate, if necessary, the DLC and the link for
  this adapter.

o If the problem persists, add additional RAM to the workstation, and restart
  your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.12. ACS2433 ΓòÉΓòÉΓòÉ

ACS2433-E ALERT: The SDLC communication link was deactivated or could not be
established because of a lack of operating system resources at the local node.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The operating system was unable to allocate random access memory
(RAM) as requested by local SDLC software.

User Response: Ensure that the MEMMAN parameter in the local CONFIG.SYS file is
set to SWAP, MOVE.  If it is not, correct the problem and restart your
computer.

o You can free more resources by ending any unnecessary active programs. Access
  Subsystem Management and reactivate the SDLC DLC and link.

o If the problem persists, add additional RAM to the local workstation and
  restart your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.13. ACS2434 ΓòÉΓòÉΓòÉ

ACS2434-E ALERT:  Lack of OS/2 resources at the local node ended all twinaxial
communications.

Originator: Twinaxial Data Link Control

Explanation: OS/2 was unable to allocate memory as requested by local Twinaxial
software.

User Response: Ensure that the MEMMAN parameter in the local CONFIG.SYS file is
set to SWAP, MOVE.  If it is not, correct the problem and restart your
computer.

o You can free more resources by ending any unnecessary active programs. Access
  subsystem management and reactivate, if necessary, the link and DLC for this
  adapter.

o If the problem persists, add additional RAM to the local workstation and
  restart your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.14. ACS2435 ΓòÉΓòÉΓòÉ

ACS2435-E ALERT: All local Twinaxial communications failed to be established
because the Twinaxial device-driver failed to install properly.

Originator: Twinaxial Data Link Control

Explanation: This initialization problem was caused by a hardware/software
mismatch because of one of the following:  The DEVICE= statement is missing
from the CONFIG.SYS file, the specified device driver is incorrect, or one of
the device-driver files was not found.

User Response: If the local CONFIG.SYS file was recently altered, restore it
and restart your computer.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, reinstall Twinaxial software.

o Retry the operation you were attempting when the problem occurred. If the
  problem still persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.15. ACS2436 ΓòÉΓòÉΓòÉ

ACS2436-E ALERT: A protocol error at the local node has caused the SDLC
communication link to be deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: As a result of a protocol error generated by the local node, a
frame reject (FRMR) response was received.  However, the reason that the remote
node sent the FRMR response frame is unknown because the frame did not contain
an information field (I-field).

User Response: Review the formatted alert and locate the remote node. Check the
DLC profile in the local configuration to ensure that it is compatible with the
remote node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.16. ACS2437 ΓòÉΓòÉΓòÉ

ACS2437-E ALERT: The local Token-Ring Network adapter detected a lobe wire
fault and closed the adapter.

Originator: Token-Ring or Other LAN Type

User Response: Check and secure all cable connections between the specified
local adapter and the multistation access unit (MAU).

o Ensure that the specified local adapter is operating correctly by running the
  appropriate diagnostics.  Access subsystem management and reactivate, if
  necessary, the DLC and the link for this adapter. Retry the operation you
  were attempting when the problem occurred. If the problem persists, note the
  time, date, and identification number of this message and contact your local
  support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.17. ACS2438 ΓòÉΓòÉΓòÉ

ACS2438-E ALERT: Local SNA was unable to establish a session because of an
internal error.

Originator: SNA Communications Services (APPN)

Explanation: The Address Space Manager component of SNA detected an error that
prevented the set up of an SNA session.  The associated BIND was rejected.

User Response: Reinitialize your local node by exiting and restarting
Communications Manager.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.18. ACS2440 ΓòÉΓòÉΓòÉ

ACS2440-E ALERT:  An X.25 link was disconnected or could not be established
because of a failure in the local modem.

Originator: X.25 API

Explanation: A modem failure in the X.25 subsystem has been detected. Data
carrier detect and data set ready are polled at regular intervals. If either or
both of these signals remain low, the line is disconnected and a fault is
assumed within the modem or its associated cable.

o This is an X.25 API alert generated by physical-level layer 1.

User Response: Ensure that the correct modem cable is being used and secure all
cable connections between the local adapter and modem. Ensure that the modem is
powered up and operating properly. Run the appropriate modem diagnostics.

o Ensure that the specified adapter is installed and operating properly. Run
  the appropriate adapter diagnostics.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Ensure that the currently active configuration profile is compatible with the
  local X.25 connection.

o Using subsystem management, check the X.25 physical link status for errors.
  If the link status indicates Error Level 1 or Error Level 2, attempt to
  restart it.  If the link status indicates Adapter Error or Adapter Access
  Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.19. ACS2441 ΓòÉΓòÉΓòÉ

ACS2441-E ALERT: A protocol error at the local node has caused the SDLC
communication link to be deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: An information field (I-field) was not permitted in the command
that was sent by the local node to the remote node.  As a result, a frame
reject (FRMR) was sent to the local node.

User Response: Check the DLC profile in the local configuration; ensure that it
is compatible with the remote node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.20. ACS2442 ΓòÉΓòÉΓòÉ

ACS2442-E ALERT:  The local node sent a command that is unsupported or not
valid to the remote node which deactivated the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The local node sent a command to the remote node that was either
unrecognized, unsupported, or not valid in the remote node's current state.  As
a result, the remote node sent a frame reject (FRMR) response back to the local
node.

User Response: Check the DLC profile in the local configuration; ensure that it
is compatible with the remote node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.21. ACS2443 ΓòÉΓòÉΓòÉ

ACS2443-E ALERT: A configuration error was detected that may have prevented the
establishment of, or deactivated all, local LAN communications.

Originator: PC Network, ETHERAND, or Token-Ring

User Response: Review the formatted alert (especially the reference code) to
determine the cause of the failure.  The initial digits of the reference code
provide a precise failure indication:

o x'XXXXXX46' - The maximum number of link stations specified in 802.2
  configuration has been exceeded.  Do one or more of the following:

   - Use subsystem management to deactivate one or more adjacent link stations
     that are using the specified adapter.

   - Wait until some or all of the applications that are using the link
     stations have ended, and a link station is available.

   - Increase the configured maximum link stations for the specified adapter in
     the 802.2 configuration.

   - x'XXXX2259' - The specified number of configured queue elements is too
     small to satisfy current requests for the specified LAN adapter.  Increase
     the number of Timer control blocks in the 802.2 configuration.

   - x'XXXX0B59' - The specified number of configured queue elements is too
     small to satisfy current requests for the specified LAN adapter.  Increase
     the number of I-Frame descriptors in the 802.2 configuration.

   - x'XXXXXX59' - The specified number of configured queue elements is too
     small to satisfy current requests for the specified LAN adapter. Increase
     the number of UI-Frame descriptors in the 802.2 configuration.

   - x'XXXXXX5A' - An initialization failure has occurred. Review the FFST/2
     message log and error log for details.  If no relevant information is
     available review the file LANTRAN.LOG in the \IBMCOM subdirectory.

   - x'XXXXXX5E' - The requested LAN adapter is not installed.  In protocol
     configuration, configure an appropriate network adapter.

   - x'XXXXXX61' - The maximum number of users in the 802.2 configuration has
     been exceeded.  Do one or more of the following:

   - Deactivate an 802.2 application that is using failed adapter.

   - Increase the configured maximum number of users for the specified adapter
     in the 802.2 configuration.

o x'XXXX51A4' - The LAN DLC is unable to create another OS/2 thread of
  execution.  Increase the value specified for the THREADS= statement in your
  CONFIG.SYS.

o x'XXXXB1B101' - Local LAN software failed to locate the device driver
  ACSLANDD.SYS.  Ensure that a DEVICE= statement is correctly specified in
  CONFIG.SYS to load the device driver ACSLANDD.SYS.

o x'XXXXB1B103' - Local LAN software failed to locate the device driver
  LANDD.OS2.  Ensure that a DEVICE= statement is correctly specified in
  CONFIG.SYS to load the device driver LANDD.OS2.  Review the FFST/2 message
  log, or the file LANTRAN.LOG, for additional information.

o After any configuration change, restart your computer. Retry the operation
  you were attempting when the problem occurred. If the problem persists or if
  the failure cause is not listed in the preceding section, note the time,
  date, and identification number of this message and contact your local
  support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.22. ACS2444 ΓòÉΓòÉΓòÉ

ACS2444-E ALERT: The local node generated a protocol error which deactivated
the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The local node sent an information field (I-field) that exceeded
the remote node's available buffer.

User Response: Review the formatted alert and locate the remote node.

o Check the DLC profile in the local configuration and ensure that it is
  compatible with the remote node and with the desired type of use.
  Specifically, ensure the maximum RU size is compatible.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.23. ACS2445 ΓòÉΓòÉΓòÉ

ACS2445-E ALERT: The SDLC communication link has been deactivated because the
remote node is no longer able to send or receive data.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The remote node has sent a Disconnected Mode response to a command
sent by the local node.  While in disconnected mode, a node cannot send or
receive data frames; therefore, the SDLC communication link has been
deactivated.

User Response: Review the formatted alert and locate the remote node.

o Check the DLC profile in the local configuration and ensure that it is
  compatible with the remote node and with the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.24. ACS2446 ΓòÉΓòÉΓòÉ

ACS2446-E ALERT: Local SNA detected an error during the CP-CP session.

Originator: SNA Communications Services (APPN)

Explanation: The Topology Database Manager component of SNA detected an error
during the exchange of Topology Database Updates (TDUs). TDUs flow between
control points (CPs) to update the network topology.

o This error occurred due to one of the following conditions:

   - the received TDU reports an error

   - the TDUs were received out of sequence

   - the TDU was not received before the time limit expired.

o The Topology Database Manager instructed Session Services to UNBIND the CP-CP
  session.  This effectively broke the APPN control point connection between
  your node and the node in error.

User Response: Review the formatted alert and locate the remote CP name. Access
subsystem management and reactivate the link that was deactivated.  Retry the
operation you were attempting when the problem occurred.  If the problem
persists, note the time, date, and identification number of this message and
contact your local support personnel.  Your local support personnel should
remove the remote node from the network until the precise nature of the failure
is isolated.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.25. ACS2447 ΓòÉΓòÉΓòÉ

ACS2447-E ALERT:  The receive sequence count (Nr) sent to the remote node was
not valid.  The SDLC communication link was deactivated.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The receive sequence count (Nr) sent to the remote node does not
refer to either the next information frame (I-frame) to be transmitted or to an
I-frame that has been transmitted but not acknowledged.  As a result, a frame
reject (FRMR) was sent back to the local node.

User Response: Review the formatted alert and locate the remote node.

o Check the DLC profile in the local configuration and ensure that it is
  compatible with the remote node and with the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.26. ACS2448 ΓòÉΓòÉΓòÉ

ACS2448-E ALERT:  The local X.25 node sent a frame reject that reset an X.25
link.

Originator: X.25 API

Explanation: The local node received a frame from the remote node during
information-transfer state containing an N(r) (receive sequence count) that was
not valid.  As a result, the local node sent back a frame reject (FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, review the formatted
  alert in order to locate the remote node.  Perform the previous recommended
  actions on the remote node.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.27. ACS2449 ΓòÉΓòÉΓòÉ

ACS2449-E ALERT:  The local X.25 node received a frame reject that reset an
X.25 link.

Originator: X.25 API

Explanation: The local node sent a frame to the remote node during
information-transfer state containing an N(r) (receive sequence count) that was
not valid.  As a result, the remote DTE sent back a frame reject (FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.28. ACS2450 ΓòÉΓòÉΓòÉ

ACS2450-E ALERT:  While initializing, PC Network or ETHERAND  access was
rejected by a remote LAN administrator.

Originator: ETHERAND or PC Network

Explanation: As the local adapter was attempting to insert into the ring,
access was denied.  A remove command was received from a remote network
administrator which prevented the adapter from entering the LAN.

User Response: This error is the result of your workstation being prevented
from accessing the LAN because of the actions of a remote LAN administrator.
Note the time, date, and identification number of this message and contact your
LAN administrator to understand why the remove command was issued against the
local adapter.  Once the problem is corrected, access subsystem management and
reactivate, if necessary, the DLC and the link for this adapter.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.29. ACS2451 ΓòÉΓòÉΓòÉ

ACS2451-E ALERT: A twinaxial link has been deactivated because the local
twinaxial cable is either loose or defective.

Originator: Twinaxial Data Link Control

User Response: Check and secure the local twinaxial cable. Access subsystem
management and reactivate, if necessary, the link and the DLC.  Retry the
operation you were attempting when the problem occurred.

o If the problem persists, install a different physical twinaxial connection,
  and retry the operation you were attempting when the problem occurred.

o If the problem still persists, note the time, date, and identification number
  of this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.25.30. ACS2452 ΓòÉΓòÉΓòÉ

ACS2452-E ALERT: The local token-ring network adapter detected a beaconing
condition on the ring while attempting to enter into the LAN. The adapter has
been closed.

Originator: Token-Ring or Other LAN Type

Explanation: The Beaconing condition is most often caused by the speed of your
adapter being different than the speed at which the LAN is running, a cabling
problem at the multistation access unit (MAU), a defective cable, or a
defective adapter.

User Response: Contact your local support personnel in order to identify the
speed of the LAN.  Start your system using the reference diskette to adjust the
speed of the local adapter.  Restart your computer and retry the operation you
were attempting when the problem occurred. Ensure that there are no breaks in
connections from ring-in (RI) to one MAU, to ring-out (RO) from a second MAU.
Inspect all cables for breaks.  Run the appropriate diagnostics on all LAN
adapters on the failing ring.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26. ACS2453 through ACS2482 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.26.1. ACS2453 ΓòÉΓòÉΓòÉ

ACS2453-E ALERT: The local X.25 node received a restart packet that caused all
virtual circuits to be cleared and all permanent virtual circuits to be reset.

Originator: X.25 API

Explanation: The local DTE received a restart indication packet that caused all
virtual circuits on a link to be reset.

o This is an X.25 API alert generated by packet-layer-control layer 3.

User Response: Review the formatted alert and locate the DCE-originated cause
code and diagnostic code.  These codes provide a more precise indication of the
failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.2. ACS2454 ΓòÉΓòÉΓòÉ

ACS2454-E ALERT:  An X.25 link failure has been detected.

Originator: X.25 API

Explanation: The local node retried a command frame for the maximum number of
times (N2 times) without receiving the appropriate response. As a result, the
local node entered the disconnected state.

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.  You may want to increase the configured T1
retransmission value to support possible network congestion.  If the T1
retransmission value is not large enough, the physical X.25 link may terminate.
This will usually occur when network congestion is high and the physical line
speed is slow.  The T1 parameter is defined under X.25 links configuration.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.3. ACS2455 ΓòÉΓòÉΓòÉ

ACS2455-E ALERT:  The local X.25 node received a frame reject that reset an
X.25 link.

Originator: X.25 API

Explanation: The local node sent a frame to the remote node during
information-transfer state containing an information field (I-field) that was
not valid.  As a result, the remote DTE sent back a frame reject (FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.4. ACS2456 ΓòÉΓòÉΓòÉ

ACS2456-E APPN ALERT: An SNA link was not established.

Originator: SNA Communications Services (APPN)

Explanation: The Configuration Services component of local SNA terminated XID
negotiation for link bring-up because an XID was received from a remote node
that was incorrect in format or contained unacceptable values.

User Response: Review the formatted alert and locate the link name.  If the
link name is IMPLICIT, consider this alert to be informational because the
failed link was configured at a remote node.  A corresponding alert was
generated at the remote node and the problem should be resolved there.

o If the link name is not IMPLICIT, the link was defined locally. Locate the
  sense data from the formatted alert and refer to the Problem Determination
  Guide for a detailed description of sense data. Correct the problem as
  indicated by the sense data.

o Access subsystem management and reactivate the link to the remote node. Retry
  the operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.5. ACS2457 ΓòÉΓòÉΓòÉ

ACS2457-E ALERT:  The local station sent an XID to initialize a logical link
for a LAN logical adapter, but the retry count was exceeded before a response
was received from the remote station.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Review the formatted alert. 2.  Locate the
remote station. 3.  Check to see that the remote station has not been powered
off.  If it has, power it on and retry the operation. 4.  If the local station
and the remote station are on separate networks and are connected by a bridge,
check to see that the bridge software is still operating properly.  If it is
not, correct the problem and retry the operation. 5.  Check the FFST/2 message
log at the remote station for errors and correct them.  Then retry the
operation. 6.  At the remote station, do the following:

o In the LAN Adapter and Protocol Support (LAPS) 802.2 configuration, increase
  the number of link stations for the specified adapter.

o Use Communications Manager Setup to access the appropriate data link control
  (DLC) adapter profile for the active configuration.  In the DLC adapter
  profile, increase the maximum number of link stations.  Then restart the
  system and retry the operation.

If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP.  From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.6. ACS2458 ΓòÉΓòÉΓòÉ

ACS2458-E ALERT: The PC Network or Ethernet Network adapter check indicates a
local hardware failure.

Originator: ETHERAND or PC Network

User Response: Ensure that the specified adapter is functioning properly by
running the appropriate diagnostics.  Access subsystem management and
reactivate, if necessary, the link and DLC for this adapter.  Retry the
operation you were attempting when the problem occurred.  If the problem
persists, note the time, date, and identification number of this message and
contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.7. ACS2459 ΓòÉΓòÉΓòÉ

ACS2459-E ALERT: The local X.25 node received a clear or reset packet that
either cleared a switched virtual circuit call or reset a virtual circuit
(switched or permanent).

Originator: X.25 API

Explanation: The local DTE received a clear indication packet or reset
indication packet that either cleared or reset a virtual circuit.

o Both of these conditions are X.25 API alerts generated by
  packet-layer-control layer 3.

User Response: Review the formatted alert and locate the DCE-originated cause
code and diagnostic code.  These codes provide a more precise indication of the
failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.8. ACS2460 ΓòÉΓòÉΓòÉ

ACS2460-E ALERT: The local X.25 subsystem software detected an error and
stopped.

Originator: X.25 API

Explanation: Either an error was found as the configuration file was being
loaded, an unexpected return code was received from OS/2, or an X.25 program
logic error was detected.

o This is an X.25 API generated alert.

User Response: Ensure that the correct configuration file is active.  If the
proper configuration file is in use, restore the configuration file from your
backup copy.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, ensure that the local X.25
  configuration matches the physical configuration of the system (adapters,
  links, modems, and cables) and the X.25 network subscription.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.9. ACS2461 ΓòÉΓòÉΓòÉ

ACS2461-E ALERT: The local token-ring network adapter failed to insert itself
in the ring because the adapter detected another station on the network with
the same address.

Originator: Token-Ring or Other LAN Type

User Response: Reconfigure the local adapter to use a unique adapter address.
Usually, a unique address can be selected by configuring to use the adapter's
universally administered address rather than a locally administered address.
However, some configurations (for example, Gateway) require the use of locally
administered addresses;  in this case, contact your LAN administrator for a
unique locally administered address.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message; then contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.10. ACS2462 ΓòÉΓòÉΓòÉ

ACS2462-E ALERT: The remote node sent a command that was not valid to the local
node which deactivated the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: A Set Normal Response Mode (SNRM) command was received from the
remote node while the local node was in normal response mode (NRM).

User Response: Check the DLC profile in the local configuration and ensure that
it is compatible with the remote node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.11. ACS2463 ΓòÉΓòÉΓòÉ

ACS2463-E ALERT: The local node generated a protocol error to the remote DTE
that may have deactivated the X.25 virtual circuit.

Originator: X.25 Data Link Control

Explanation: The local X.25 DLC sent either a command or some data to the
remote DTE with an information field (I-field) that was too large.  The remote
DTE sent back a frame reject (FRMR).

o This is an X.25 DLC alert generated by logical-link-control layer 8.

User Response: Review the formatted alert and locate the remote DTE. This alert
usually indicates a hardware/software mismatch at the remote DTE.  Ensure that
the currently active configuration profile at the remote DTE is compatible with
both its X.25 connection and with the configuration of the local DTE.  Using
subsystem management, check the link status for errors.  If the link status
indicates Error Level 1 or Error Level 2, disconnect the link and attempt to
restart it.  If the link status indicates Adapter Error or Adapter Access
Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.12. ACS2464 ΓòÉΓòÉΓòÉ

ACS2464-E ALERT:  The twinaxial communication link could not be established
because the locally configured controller address is already in use.

Originator: Twinaxial Data Link Control

Explanation: The controller address is the workstation address specified in the
twinaxial DLC configuration.  A hardware/software mismatch exists because two
users were incorrectly configured to the same workstation address and
initialization could not be completed.

User Response: Ensure that the local workstation address has been configured
correctly.  Restart your computer and retry the operation you were attempting
when the problem occurred.

o If the problem persists, note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.13. ACS2465 ΓòÉΓòÉΓòÉ

ACS2465-E ALERT: The local node detected an error, and deactivated the SDLC
communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The local node detected an error, that may have originated at
either the local node or the remote node.  This error caused the SDLC
communication link to be deactivated.

o This alert is placed only in the local log; it is not forwarded from this
  node.

User Response: Review the formatted alert and locate the remote node.

o Check the DLC profile in the local configuration and ensure that it is
  compatible with the remote node and the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.14. ACS2466 ΓòÉΓòÉΓòÉ

ACS2466-E ALERT:  The local PC Network or Ethernet Network adapter failed to
insert itself into the LAN because the adapter detected another station on the
network with the same address.

Originator: ETHERAND or PC Network

User Response: Reconfigure the local adapter to use a unique adapter address.
Usually, a unique address can be selected by configuring to use the adapter's
universally administered address rather than a locally administered address.
However, some configurations (for example, Gateway) require the use of locally
administered addresses; in this case, contact your LAN administrator for a
unique locally administered address.

o Restart your computer and retry the operation you were attempting when the
  problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.15. ACS2467 ΓòÉΓòÉΓòÉ

ACS2467-E ALERT:  The local node detected a loss of carrier detect and
deactivated the asynchronous connection.

Originator: Asynchronous Device Driver

Explanation: The carrier detect was lost on a switched line.

User Response: Carrier detect was unexpectedly negated by either a local DCE or
by a directly attached DTE.  Loss of connection may indicate a normal condition
by a remote DCE/DTE, an abnormal disconnection within the telephone network, a
malfunction of either a local or remote DCE, or a loose cable.

o If loss of connection was unexpected, check and secure all connections
  between the local adapter and modem.  Verify that the DCE is functioning
  properly and run the appropriate modem diagnostics.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.16. ACS2468 ΓòÉΓòÉΓòÉ

ACS2468-E ALERT:  An X.25 link failure has been detected.

Originator: X.25 API

Explanation: The local node transmitted a Set Asynchronous Balanced Mode (SABM)
command to initialize the link and received a Disconnect Mode (DM) frame.  As a
result, the local node was unable to initialize the link.

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.17. ACS2469 ΓòÉΓòÉΓòÉ

ACS2469-E ALERT:  The local token ring network adapter is indicating a hardware
failure.

Originator: Token-Ring or Other LAN Type

User Response: Ensure that the specified local adapter is operating correctly
by running the appropriate diagnostics. Access subsystem management and
reactivate, if necessary, the DLC and the link for this adapter.  Retry the
operation you were attempting when the problem occurred. If the problem
persists, note the time, date, and identification number of this message and
contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.18. ACS2470 ΓòÉΓòÉΓòÉ

ACS2470-E ALERT: The remote node attempted to establish a LAN communication
link that already exists.

Originator: PC Network, ETHERAND, or Token-Ring

Explanation: A SABME (set asynchronous balance mode extended) command has been
received that reset an active link.

User Response: Review the formatted alert and locate the remote station.  Check
the FFST/2 error log in the remote station for related failures and correct any
related problems.

o Ensure that the specified remote adapter is operating correctly by running
  the appropriate diagnostics.  Access subsystem management and reactivate, if
  necessary, the DLC and the link for this adapter. Retry the operation you
  were attempting when the problem occurred. If the problem persists, note the
  time, date, and identification number of this message and contact your local
  support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.19. ACS2471 ΓòÉΓòÉΓòÉ

ACS2471-E ALERT:  The local node received an unsupported command from the host
that deactivated the twinaxial communication link.

Originator: Twinaxial Data Link Control

Explanation: This error is usually indicative of a protocol error at the host.

User Response: Access subsystem management and reactivate, if necessary, the
link and DLC for this adapter. Retry the operation you were attempting when the
problem occurred. If the problem persists, note the time, date, and
identification number of this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.20. ACS2472 ΓòÉΓòÉΓòÉ

ACS2472-E ALERT: A local X.25 packet-layer timer has expired while sending a
command to a remote node.  All retry attempts have failed and virtual calls
have been cleared.

Originator: X.25 API

Explanation: The local DCE generates this alert for one of several conditions:

o Time limit T20 expired at the local node before receipt of a restart
  confirmation packet and after transfer of a restart indication packet.

o Time limit T21 expired at the local node before receipt of a call accepted
  packet, and after transfer of an incoming call packet.

o Time limit T22 expired at the local node before receipt of a DTE or DCE reset
  confirmation packet and after transfer of a reset indication packet.

o Time limit T23 expired at the local node before receipt of a DTE or DCE clear
  confirmation packet and after transfer of a clear indication packet.

o If the packet time-out value is not large enough, the physical X.25 link may
  be terminated.  This can occur when network congestion is high and the
  physical line speed is slow.

All these conditions are X.25 API alerts generated by packet-layer-control.

User Response: Review the formatted alert and locate the timer name. You may
want to increase the locally configured packet time-out value so that it is
large enough to support peak network congestion. Packet time-out values are
configured under X.25 link configuration.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.21. ACS2473 ΓòÉΓòÉΓòÉ

ACS2473-I APPN ALERT:  Local SNA discarded a PIU that was not valid.

Originator: SNA Communications Services (APPN)

Explanation: The Path Control component of local SNA detected an error in a
received Path Information Unit (PIU).  The PIU in error is ignored.

o PIUs are the basic data transport packet for SNA.  This error is generated
  when required fields of the PIU do not meet SNA standards.

User Response: If this error log entry appears intermittently, no action is
required.  This error log indicates that received data was discarded because of
an SNA error.  Normal error recovery mechanisms should prompt the
retransmission of this discarded data packet.

o If the problem persists, review the formatted alert and locate the link name
  and Remote node CP name.  Note the time, date, and identification number of
  this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.22. ACS2474 ΓòÉΓòÉΓòÉ

ACS2474-E ALERT: The local node may not have properly cleared a previous
switched asynchronous connection.

Originator: Asynchronous Device Driver

Explanation: On a switched line, Data Set Ready (DSR) was on before Data
Terminal Ready (DTR) was raised.  Based upon the configuration, DSR is required
to be negated for at least 100 milliseconds to indicate that the local DCE has
completed clearing the call from the previous connection.

User Response: Verify that the previous call has cleared.  Check and secure all
connections between the local adapter and modem.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, run the appropriate diagnostics on the local adapter and
  modem.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.23. ACS2475 ΓòÉΓòÉΓòÉ

ACS2475-E ALERT: A modem signaling problem at the local node has deactivated
the SDLC communication link.

Originator: Synchronous Data Link Control (SDLC)

Explanation: On a switched modem, the data set ready (DSR) signal was present
before data terminal ready (DTR) was raised.

User Response: Check and secure the cable connections between the local adapter
and modem.  Verify that the local adapter and modem are functioning properly by
running the appropriate diagnostics.

o Check the DLC profile in the local configuration.  Ensure that it is
  compatible with the remote node and with the desired type of use.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.24. ACS2476 ΓòÉΓòÉΓòÉ

ACS2476-E ALERT: The SDLC communication link has been deactivated because the
number of frames received from the remote node exceeded the current receive
window count.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The local node received more frames than allowed by the link-level
pacing count; that is, it received too many frames without being given an
opportunity to acknowledge the frames it had already received.

User Response: Review the formatted alert and locate the remote node. Check the
DLC profile in the local configuration and ensure that it is compatible with
the remote node and with the desired type of use. Specifically, ensure that the
send and receive window counts in the local DLC profile have been set correctly
and are compatible with the send and receive window counts at the remote node.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.25. ACS2477 ΓòÉΓòÉΓòÉ

ACS2477-E ALERT:  A remove command was received from a remote LAN administrator
which has forced the PC Network or ETHERAND adapter to exit from the network.

Originator: ETHERAND or PC Network

User Response: Note the time, date, and identification number of this message
and contact your LAN administrator to understand why the remove command was
issued against the local adapter.

o Once the problem has been corrected, access subsystem management and
  reactivate, if necessary, the DLC and the link for this adapter. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.26. ACS2478 ΓòÉΓòÉΓòÉ

ACS2478-E ALERT: The local token-ring adapter has removed itself from the ring
because the adapter is causing a beaconing condition on the network.

Originator: Token-Ring or Other LAN Type

User Response: Ensure that the adapter is operating correctly by running the
appropriate diagnostics.  Access subsystem management and reactivate, if
necessary, the DLC and the link for this adapter. Retry the operation you were
attempting when the problem occurred. If the problem persists, note the time,
date, and identification number of this message and contact your local support
personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.27. ACS2479 ΓòÉΓòÉΓòÉ

ACS2479-E ALERT:  A signaling problem at the local node prevented the
establishment of the asynchronous communication link.

Originator: Asynchronous Device Driver

Explanation: On a nonswitched line, data set ready (DSR) was not present after
data terminal ready (DTR) was raised.  In other words, the local DCE failed to
assert DSR.

User Response: Check and secure all connections between the local adapter and
modem.

o Ensure that the local modem is set up and operating correctly.  Run the
  appropriate modem diagnostics.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.28. ACS2480 ΓòÉΓòÉΓòÉ

ACS2480-E ALERT: The SDLC communication link could not be established because
the data set ready (DSR) signal was not received from the modem.

Originator: Synchronous Data Link Control (SDLC)

Explanation: On a non-switched modem, the data set ready (DSR) signal was not
present after the data terminal ready (DTR) signal was raised.

User Response: Check and secure the cable connections between the local adapter
and modem.

o Review the formatted alert and locate the remote node. Check the DLC profile
  in the local configuration and ensure that it is compatible with the remote
  node and the desired type of use.

o Ensure that the local modem and adapter are set up and operating correctly by
  running the appropriate adapter and modem diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.29. ACS2481 ΓòÉΓòÉΓòÉ

ACS2481-E ALERT: The local X.25 node sent a restart packet that caused all
existing virtual circuit calls to be cleared and reset all existing permanent
virtual circuits.

Originator: X.25 API

Explanation: The local DCE sent a restart packet that reset all virtual
circuits on the X.25 link.

o This is an X.25 API alert generated by packet-layer-control layer 3.

User Response: Review the formatted alert and locate the DCE-originated cause
code and diagnostic code.  This data will provide a more precise indication of
the failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.26.30. ACS2482 ΓòÉΓòÉΓòÉ

ACS2482-E ALERT: A local X.25 packet-layer timer has expired while sending a
command to a remote node.  All retry attempts have failed and virtual calls
have been cleared.

Originator: X.25 API

Explanation: The local DTE generates this alert for one of several conditions:

o Time limit T20 expired at the local node before receipt of a restart
  confirmation packet and after transfer of a restart request packet. This is
  an X.25 API alert generated by packet-layer-control layer 6.

o Time limit T21 expired at the local node before receipt of a call connected
  packet or a clear indication packet, and after transfer of a call request
  packet.  This is an X.25 API alert generated by packet-layer-control layer 8.

o Time limit T22 expired at the local node before receipt of a DTE or DCE reset
  confirmation packet and after transfer of a reset request packet.  This is an
  X.25 API alert generated by packet-layer-control layer 7.

o Time limit T23 expired at the local node before receipt of a DTE or DCE clear
  confirmation packet and after transfer of a clear request packet.  This is an
  X.25 API alert generated by packet-layer-control layer 9.

o If the packet time-out value is not large enough, the physical X.25 link may
  be terminated.  This can occur when network congestion is high and the
  physical line speed is slow.

User Response: Review the formatted alert and locate the timer name. You may
want to increase the locally configured packet time-out value so that it is
large enough to support peak network congestion. Packet time-out values are
configured under X.25 link configuration.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27. ACS2483 through ACS2704 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.27.1. ACS2483 ΓòÉΓòÉΓòÉ

ACS2483-E ALERT:  The local X.25 node received a frame reject that reset an
X.25 link.

Originator: X.25 API

Explanation: The local node sent a frame to the remote node during
information-transfer state that contained an oversized information field
(I-field).  As a result, the remote DTE sent back a frame reject (FRMR).

o This is an X.25 API alert generated by Link Access Protocol-Balanced (LAPB)
  layer 2.

User Response: Ensure that the local X.25 configuration matches the physical
configuration of the system (adapters, links, modems, and cables) and the X.25
network subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.2. ACS2484 ΓòÉΓòÉΓòÉ

ACS2484-E ALERT: An application with a proper system key issued a reset command
which has closed associated local LAN DLC resources.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Note the time, date, and identification number of this message
and contact your System administrator to understand why the reset command was
issued against the local adapter.

o Once the problem has been corrected, access subsystem management and
  reactivate, if necessary, the DLC and the link for this adapter. Retry the
  operation you were attempting when the problem occurred.

o If the problem persists, verify that the local adapter is functioning
  correctly by executing the appropriate adapter diagnostics.  Access subsystem
  management and reactivate, if necessary, the DLC and the link for this
  adapter.  Retry the operation you were attempting when the problem occurred.

o If the problem still persists, note the time, date, and identification number
  of this message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.3. ACS2485 ΓòÉΓòÉΓòÉ

ACS2485-E ALERT:  The local node may not have properly cleared a previous
switched asynchronous connection.

Originator: Asynchronous Device Driver

Explanation: On a switched connection, Data Set Ready (DSR) did not drop after
Data Terminal Ready (DTR) was dropped.  In other words, the local DCE may have
failed to properly clear the previous connection.

User Response: Check and secure all connections between the local adapter and
modem.

o Ensure that the local modem is set up and operating correctly.  Run the
  appropriate modem diagnostics.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, note the time, date, and identification number of this
  message and contact your local support personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.4. ACS2486 ΓòÉΓòÉΓòÉ

ACS2486-E ALERT: The SDLC communication link was deactivated because a time-out
occurred while waiting for the Data Set Ready (DSR) modem signal to drop.

Originator: Synchronous Data Link Control (SDLC)

Explanation: Data Terminal Ready (DTR) was dropped and a time-out occurred
while waiting for Data Set Ready (DSR) to drop (switched modems only).

User Response: Check and secure the cable connections between the local adapter
and modem.

o Review the formatted alert and locate the remote node. Check the DLC profile
  in the local configuration and ensure that it is compatible with the remote
  node and the desired type of use.

o Ensure that the local modem and adapter are set up and operating correctly by
  running the appropriate adapter and modem diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.5. ACS2487 ΓòÉΓòÉΓòÉ

ACS2487-E ALERT: The SDLC communication link could not be established because
the Clear-to-Send (CTS) modem signal was activated prematurely.

Originator: Synchronous Data Link Control (SDLC)

Explanation: The Request-to-Send (RTS) modem signal was not raised but the
Clear-to-Send (CTS) modem signal is active.  The CTS signal should be made
active in response to the RTS signal being activated.

User Response: Check and secure the cable connections between the local adapter
and modem.

o Review the formatted alert and locate the remote node. Check the DLC profile
  in the local configuration and ensure that it is compatible with the remote
  node and the desired type of use.

o Ensure that the local modem and adapter are set up and operating correctly by
  running the appropriate adapter and modem diagnostics.

o Access Subsystem Management and reactivate the SDLC DLC and link. Retry the
  operation you were attempting when the problem occurred. If the problem
  persists, note the time, date, and identification number of this message and
  contact your local support personnel.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.6. ACS2488 ΓòÉΓòÉΓòÉ

ACS2488-E ALERT: The local X.25 node received a restart packet that caused all
existing virtual circuit calls to be cleared and reset all existing permanent
virtual circuits.

Originator: X.25 API

Explanation: The local DCE received a restart request packet that contains a
cause code and a nonzero diagnostic code.

o This is an X.25 API alert generated by packet-layer-control layer 3.

User Response: Review the formatted alert and locate the cause code and
diagnostic code.  This data will provide a more precise indication of the
failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.7. ACS2489 ΓòÉΓòÉΓòÉ

ACS2489-E ALERT: The local X.25 node sent a clear or reset packet that either
cleared a switched virtual circuit call or reset a virtual circuit (switched or
permanent).

Originator: X.25 API

Explanation: The local DCE sent a supervisory packet that either cleared a
switched virtual circuit or reset a virtual circuit (switched or permanent).

o Both of these conditions are X.25 API alerts generated by
  packet-layer-control layer 3.

User Response: Review the formatted alert and locate the packet type and the
DCE-originated cause code and diagnostic code.  This data will provide a more
precise indication of the failure.

o Ensure that the local X.25 configuration matches the physical configuration
  of the system (adapters, links, modems, and cables) and the X.25 network
  subscription.

o Ensure that any local X.25 switching equipment is correctly installed and
  configured.

o Using subsystem management, check the link status for errors.  If the link
  status indicates Error Level 1 or Error Level 2, disconnect the link and
  attempt to restart it.  If the link status indicates Adapter Error or Adapter
  Access Error, contact your local support personnel.

o Retry the operation you were attempting when the problem occurred. If the
  problem persists, restore the configuration file from your backup copy.

o Restart Communications Manager and retry the operation you were attempting
  when the problem occurred.  If the problem persists, note the time, date, and
  identification number of this message and contact your local support
  personnel.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file (EPWALERT.DMP). From the drop-down list,
select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.8. ACS2490 ΓòÉΓòÉΓòÉ

ACS2490-E ALERT:  The maximum number of link stations specified in the 802.2
configuration was exceeded.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Review the formatted alert, identify the LAN logical adapter
number, and do one of the following:

o Wait until some of the applications that are using the link stations have
  ended and a link station becomes available for you.  Then retry the
  operation.

o In the LAN Adapter and Protocol Support (LAPS) 802.2 configuration, increase
  the maximum number of link stations for the specified adapter.  Restart your
  system and retry the operation.

If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.9. ACS2491 ΓòÉΓòÉΓòÉ

ACS2491-E ALERT:  The specified number of timer control blocks in the 802.2
configuration is too low to satisfy the current request.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Review the formatted alert and identify
the LAN logical adapter number. 2.  In the LAN Adapter and Protocol Support
(LAPS) 802.2 configuration, increase the number of timer control blocks to
equal the maximum link stations value. 3.  Restart your system and retry the
operation. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.10. ACS2492 ΓòÉΓòÉΓòÉ

ACS2492-E ALERT:  The specified number of I-frame descriptors in the 802.2
configuration is too low to satisfy the current request.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Review the formatted alert and identify
the LAN logical adapter number. 2.  In the LAN Adapter and Protocol Support
(LAPS) 802.2 configuration, increase the number of I-frame descriptors. 3.
Restart your system and retry the operation. If the problem persists, follow
your local network operating procedures.  If this does not resolve the problem,
contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP.  From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.11. ACS2493 ΓòÉΓòÉΓòÉ

ACS2493-E ALERT:  The specified number of UI-frame descriptors in the 802.2
configuration is too low to satisfy the current request.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Review the formatted alert and identify
the LAN logical adapter number. 2.  In the LAN Adapter and Protocol Support
(LAPS) 802.2 configuration, increase the number of UI-frame descriptors. 3.
Restart your system and retry the operation. If the problem persists, follow
your local network operating procedures.  If this does not resolve the problem,
contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.12. ACS2494 ΓòÉΓòÉΓòÉ

ACS2494-E ALERT:  An error was detected while attempting to initialize the LAN
transport.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Check for media access control (MAC)
driver errors in the FFST/2 message log or in the LANTRAN.LOG file, which is
located in the IBMCOM directory. 2.  If no errors were found, add the the
RUN=d:\IBMCOM\NETBIND.EXE statement in the CONFIG.SYS file, where d is the
drive where LAN Adapter and Protocol Support (LAPS) resides. 3.  Restart your
system and retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.13. ACS2495 ΓòÉΓòÉΓòÉ

ACS2495-E ALERT:  The LAN logical adapter that was requested is not configured
in the LAN Adapter and Protocol Support (LAPS).

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Review the formatted alert and identify
the LAN logical adapter number. 2.  In the LAPS configuration, configure the
network driver and 802.2 protocol for the appropriate logical adapter number.
3.  Restart your system and retry the operation. If the problem persists,
follow your local network operating procedures.  If this does not resolve the
problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.14. ACS2496 ΓòÉΓòÉΓòÉ

ACS2496-E ALERT:  The maximum number of users in the 802.2 configuration was
exceeded.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Review the formatted alert, identify the LAN logical adapter
number, and do one of the following:

o Stop one or more of the 802.2 applications that are using the logical
  adapter.  Then retry the operation.

o In the LAN Adapter and Protocol Support (LAPS) 802.2 configuration, increase
  the maximum number of users for the specified adapter.  Restart your system
  and retry the operation.

If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.15. ACS2497 ΓòÉΓòÉΓòÉ

ACS2497-E ALERT:  The LAN data link control (DLC) was unable to start another
operating system thread because the specified value for the maximum number of
threads in the CONFIG.SYS file is too low.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  In the CONFIG.SYS file, increase the value
specified in the THREADS= statement. 2.  Restart your system and retry the
operation. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.16. ACS2498 ΓòÉΓòÉΓòÉ

ACS2498-E ALERT:  The ACSLANDD.SYS device driver is not active.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

Explanation: The DEVICE=d:\CMLIB\ACSLANDD.SYS statement, where d is the drive
where Communications Manager resides, is missing in the CONFIG.SYS file because
is was removed or Communications Manager Setup ended before updating the
CONFIG.SYS file.

User Response: Do the following: 1.  Use Communications Manager Setup to access
the active configuration.  Exit Communications Manager Setup and select OK to
update the system files. 2.  Restart your system and retry the operation. If
the problem persists, follow your local network operating procedures.  If this
does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.17. ACS2499 ΓòÉΓòÉΓòÉ

ACS2499-E ALERT:  The LANDD.OS2 device driver is not active.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

User Response: Do the following: 1.  Check for initialization errors in the
FFST/2 message log or the LANTRAN.LOG file, which is located in the IBMCOM
directory and correct them. 2.  Install and configure the LAN Adapter and
Protocol Support (LAPS) for the 802.2 interface. 3.  Restart your system and
retry the operation. If the problem persists, follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.18. ACS2500 ΓòÉΓòÉΓòÉ

ACS2500-W ALERT:  The local station attempted to initiate a logical link, but
the number of links allowed for outgoing calls at the local station was
exceeded.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

Explanation: The total number of link stations allowed for the LAN data link
control (DLC) is determined by the maximum number of link stations value
specified in the Communications Manager DLC adapter profile or the number of
link stations that the LAN transport has available.  Whichever number is lower
is the total number of link stations that are allowed.  The minimum number of
link stations reserved for incoming calls is determined by the percent of
incoming calls value specified in the DLC adapter profile.  The remaining link
stations are used for either incoming or outgoing calls, whichever are
activated first.

User Response: The system will continue to process, no user response is
mandatory.  However, to initiate the logical link, review the formatted alert,
identify the LAN logical adapter number, and do one of the following:

o In the LAN Adapter and Protocol Support (LAPS) 802.2 configuration, increase
  the maximum number of link stations for the specified adapter.  Then restart
  your system and retry the operation.

o Use Communications Manager Setup to access the appropriate DLC adapter
  profile for the active configuration.  In the DLC adapter profile increase
  the maximum number of link stations or decrease the percent of incoming calls
  to allow more outgoing links.  Then restart Communications Manager and retry
  the operation.

o Use Subsystem Management to stop logical links that are using the specified
  adapter.  Then retry the operation.

If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.19. ACS2501 ΓòÉΓòÉΓòÉ

ACS2501-W ALERT:  A remote station attempted to initiate a logical link, but
there are no link stations available at the local station.

Originator: PC Network, ETHERAND, Token-Ring, or Other LAN Type

Explanation: The total number of link stations allowed for the LAN data link
control (DLC) is determined by the maximum number of link stations value
specified in the Communications Manager DLC adapter profile or the number of
link stations that the LAN transport has available.  Whichever number is lower
is the total number of link stations that are allowed.

User Response: The system will continue to process, no user response is
mandatory.  However, to access the incoming link, review the formatted alert,
identify the LAN logical adapter number, and do one of the following:

o In the LAN Adapter and Protocol Support (LAPS) 802.2 configuration, increase
  the number of maximum link stations for the specified adapter.  Then restart
  your system and retry the operation.

o Use Communications Manager Setup to access the appropriate data link control
  (DLC) adapter profile for the active configuration.  In the DLC adapter
  profile increase the maximum number of link stations.  Then restart
  Communications Manager and retry the operation.

o Use Subsystem Management to stop logical links that are using the specified
  adapter.  Then retry the operation.

If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.27.20. ACS2690 ΓòÉΓòÉΓòÉ

ACS2690-W Communications Manager shutdown is currently in progress. This
request cannot be processed at this time.

Originator: Communications Manager Kernel

Explanation: A request to stop communications is already being processed.

User Response: Wait for all termination activity to complete, then restart
Communications Manager.


ΓòÉΓòÉΓòÉ 3.27.21. ACS2691 ΓòÉΓòÉΓòÉ

ACS2691-W The specified parameter is not valid or the number of parameters
specified is not correct.

Originator: Communications Manager Kernel

Explanation:

o If you are trying to start Communications Manager, the only parameter that
  can be specified is a valid configuration name.

o If you are trying to stop Communications Manager, only one parameter can be
  specified and it must be either Abnormal or Normal.


ΓòÉΓòÉΓòÉ 3.27.22. ACS2692 ΓòÉΓòÉΓòÉ

ACS2692-W Communications Manager is already active.

Originator: Communications Manager Kernel

User Response: Do one of the following:

o If Communications Manager is starting, allow the startup to complete.

o If Communications Manager is stopping, allow the stop to complete before
  attempting to restart. If you need to end the connection services and
  emulation sessions immediately, issue an ABNORMAL stop.


ΓòÉΓòÉΓòÉ 3.27.23. ACS2693 ΓòÉΓòÉΓòÉ

ACS2693-W The name(20) feature is not supported on a LAN redirected
workstation. Communications Manager is starting without the feature.

where
name(20)        = feature name

Originator: Communications Manager Kernel

User Response: Do one of the following:

o If the feature is required, install Communications Manager for a single user
  workstation.

o If the feature is not required, either ignore this message or install a
  configuration for a LAN redirected workstation.


ΓòÉΓòÉΓòÉ 3.27.24. ACS2694 ΓòÉΓòÉΓòÉ

ACS2694-W The name(20) data link control (DLC) is not supported on a LAN
redirected workstation.  Communications Manager is activating other DLCs that
are supported.

where
name(20)        = adapter name

Originator: SNA Communications Services (APPC)

User Response: Do one of the following:

o If the DLC is required, install Communications Manager for a single user
  workstation.

o If the DLC is not required, either ignore this message or install a
  configuration for a LAN redirected workstation.


ΓòÉΓòÉΓòÉ 3.27.25. ACS2695 ΓòÉΓòÉΓòÉ

ACS2695-W A LAN redirected workstation is not supported as a network node. The
workstation is activated as an end node.

Originator: SNA Communications Services (APPC)

User Response: Do one of the following:

o If it is required that the workstation serve as a network node, install
  Communications Manager for a single user workstation.

o If it is not required that the workstation serve as a network node, either
  ignore this message or install a configuration for a LAN redirected
  workstation.


ΓòÉΓòÉΓòÉ 3.27.26. ACS2700 ΓòÉΓòÉΓòÉ

ACS2700-E The selected local LU alias, partner LU, and mode triplet is already
being used by one or more LU 6.2 sessions.

Originator: Subsystem Management

User Response:

o Change one of the triplet entries (local LU alias, partner alias, or mode) to
  one that is not currently being used.

o Close this window and select Change limits from the Session list to change
  the session limits of the existing triplet.


ΓòÉΓòÉΓòÉ 3.27.27. ACS2701 ΓòÉΓòÉΓòÉ

ACS2701-E An error occurred while changing or establishing the requested LU 6.2
session limits for LU alias name(8), partner LU name name(17), and mode name
name(8).

where
name(8)         = LU alias name
name(17)        = PLU name
name(8)         = mode name

Originator: Subsystem Management

User Response: Select Refresh from the menu bar of the current window and do
one of the following:

o If you are changing the session limits, make sure the selected LU alias,
  partner LU name, and mode name have active sessions.

o If you are trying to establish the session limits, make sure there are no
  active sessions for the selected LU alias, partner LU name, and mode name.


ΓòÉΓòÉΓòÉ 3.27.28. ACS2702 ΓòÉΓòÉΓòÉ

ACS2702-E The request to activate the logical link name(8) was not completed.

where
name(8)         = link name

Originator: Subsystem Management

User Response: Select Refresh from the menu bar of this window and check to see
if the link is already active.


ΓòÉΓòÉΓòÉ 3.27.29. ACS2703 ΓòÉΓòÉΓòÉ

ACS2703-E The request to activate the name(8) data link control (DLC) was not
completed.

where
name(8)         = DLC name

Originator: Subsystem Management

User Response: Select Refresh from the menu bar of this window and check to see
if the DLC is already active.  If it is not activated:

o Ensure that the adapter is not missing or in the wrong slot. Also, check that
  the wrong slot number was not used in the configuration.

o Ensure that the physical connection for the adapter is not broken, severed,
  or unplugged.

o Ensure that the adapter hardware is operating properly.  If it is not, you
  may have to replace the adapter.

o Be sure that there are no incorrect DEVICE= statements.  Also, make sure the
  DEVICE= statements are in the correct order.


ΓòÉΓòÉΓòÉ 3.27.30. ACS2704 ΓòÉΓòÉΓòÉ

ACS2704-E The request to deactivate the name(8) data link control (DLC) was not
completed.

where
name(8)         = DLC name

Originator: Subsystem Management

User Response: Select Refresh from the menu bar of this window and check to see
if the DLC is already inactive.


ΓòÉΓòÉΓòÉ 3.28. ACS2705 through ACS2755 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.28.1. ACS2705 ΓòÉΓòÉΓòÉ

ACS2705-W All LU 6.2 sessions that are not using the CPSVCMG mode will be
deactivated.  Sessions that are currently using the CPSVCMG mode are reserved
for APPN use and cannot be deactivated by this action.

Originator: Subsystem Management

User Response:

o Select OK to confirm the request and deactivate the sessions.

o Select Cancel to close the window without deactivating the sessions.


ΓòÉΓòÉΓòÉ 3.28.2. ACS2706 ΓòÉΓòÉΓòÉ

ACS2706-E The request to start the service 'name(29)' was not completed.

where
name(29)        = Communications Manager feature name

Originator: Subsystem Management

User Response:

o Select Refresh from the menu bar and check to see if the service is already
  started.

o If you are starting any service other than the Communications Manager kernel,
  be sure that the kernel is started.

o If the kernel fails to start after you select Refresh, check the system error
  log for more detailed information.


ΓòÉΓòÉΓòÉ 3.28.3. ACS2707 ΓòÉΓòÉΓòÉ

ACS2707-E The request to stop the service 'name(29)' was not completed.

where
name(29)        = Communications Manager feature name

Originator: Subsystem Management

User Response:

o Select Refresh from the menu bar and check to see if the service is already
  stopped.

o If you are stopping any service other than the Communications Manager kernel,
  be sure that the kernel is started.

o If the kernel fails to start after you select Refresh, check the system error
  log for more detailed information.


ΓòÉΓòÉΓòÉ 3.28.4. ACS2708 ΓòÉΓòÉΓòÉ

ACS2708-E The logical link or virtual circuit name(8) was not deactivated.

where
name(8)         = logical link or virtual circuit name

Originator: Subsystem Management

User Response:

o Refresh the current window and note the updated list of logical links and
  virtual circuits.  This may tell you that the virtual circuit was already
  deactivated, in which case you do not need to do anything.

o If the virtual circuit was not deactivated, an error occurred.  Try the
  operation again.  If the problem persists, check the system error log for
  additional information.


ΓòÉΓòÉΓòÉ 3.28.5. ACS2709 ΓòÉΓòÉΓòÉ

ACS2709-E The request to activate logical link name(8) did not complete because
the associated adapter is not open.

where
name(8)         = Link Name

Originator: Subsystem Management

Explanation: The associated adapter must be open before a logical link can be
activated.

User Response: Select More details... for the specified link to view the
associated DLC type and adapter number.  Use the Data Link Controls window from
SNA Subsystem Management to activate the associated adapter. Then use the
Logical Links window to activate the link.


ΓòÉΓòÉΓòÉ 3.28.6. ACS2710 ΓòÉΓòÉΓòÉ

ACS2710-E

 The X.25 API has detected a failure on an ISDN X.25 link. This failure
 was caused by an error in the Connection Manager or the Port Connection
 Manager.

Originator: X.25 API

Explanation: This error is the result of one of the following problems:

o There is a mismatch between the configuration of the X.25 link and the
  Connection Manager or Port Connection Manager.

o The Connection Manager has detected an error in its operating environment.

o The Connection Manager has detected an error in the Port Connection Manager.

User Response:

o Check the alert entries associated with this message in the system error log
  to identify the error returned to the X.25 API and the error returned to the
  Connection Manager.  From the FFST/2 folder, select System Error Log.

o Check to see whether the X.25 configuration data matches the attached local
  network parameters.

o Check to be sure that any local X.25 switching equipment or any other
  equipment is correctly installed and configured.


ΓòÉΓòÉΓòÉ 3.28.7. ACS2711 ΓòÉΓòÉΓòÉ

ACS2711-E The X.25 API has ended because of an error in the Connection Manager
or the Port Connection Manager.

Originator: X.25 API

User Response:

o Check the alert entries associated with this message in the system error log
  to identify the error returned to the X.25 API and the error returned to the
  Connection manager.  From the FFST/2 folder, select System Error Log.

o Check the X.25 configuration, the Connection Manager configuration, and the
  Port Connection Manager configuration to ensure that they match each other
  and the attached local network parameters.  To check the Connection Manager
  and Port Connection Manager configurations:

   - Select Setup in the Communications Manager Setup window.

   - Select the configuration name and then select OK in the Open Configuration
     window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select Connection Manager or Port Connection Manager and then select
     Configure in the Communications Manager Configuration List window.

o Correct any problems and restart Communications Manager.


ΓòÉΓòÉΓòÉ 3.28.8. ACS2712 ΓòÉΓòÉΓòÉ

ACS2712-E The X.25 Protocol Driver has ended because of an internal error.  All
X.25 links using ISDN have ended.

Originator: X.25 API

User Response:

o Check the FFST/2 alert entry associated with this message in the system error
  log to identify the specific nature of the error.  From the FFST/2 folder,
  select System Error Log.

o Check to be sure that the X.25 configuration data matches the attached local
  network.

o Shut down the system and then restart it so that the X.25 ISDN subsystem can
  be used.

o Try the connection again.


ΓòÉΓòÉΓòÉ 3.28.9. ACS2713 ΓòÉΓòÉΓòÉ

ACS2713-E The X.25 Subsystem has timed out waiting for a response from the X.25
ISDN Protocol Driver. All X.25 connections using ISDN have ended.

Originator: X.25 API

Explanation:

o The X.25/ISDN Protocol Driver has encountered an internal error and stopped.

.*EXPLANATION:  This error is the result of one of the following:

User Response:

o Check the alert entries associated with this message in the system error log
  to identify the error returned to the X.25 API and any error posted by the
  protocol driver that owns this MAC.

o Check to see whether the X.25 configuration data matches the configuration
  data of the protocol driver.  Also, ensure that the X.25 configuration data
  matches the attached local network and remote node parameters.  To check the
  protocol driver configuration:

   - Select Setup in the Communications Manager Setup window.

   - Select the configuration name and then select OK in the Open Configuration
     window.

   - Select Configure any profile or feature from the Options pull-down menu in
     the Communications Manager Configuration Definition window.

   - Select ISDN - Protocol Driver and then select Configure in the
     Communications Manager Configuration List window.

o Check to be sure that any local X.25 switching equipment or any other
  equipment is correctly installed and configured.


ΓòÉΓòÉΓòÉ 3.28.10. ACS2720 ΓòÉΓòÉΓòÉ

ACS2720-E The active configuration name(8) does not contain any session
configurations for the 3270 Emulator or the 5250 Emulator.

where
name(8)         = configuration file name

Originator: Communications Manager Kernel

User Response: Use a different configuration, or configure 3270 or 5250
sessions in the current configuration.


ΓòÉΓòÉΓòÉ 3.28.11. ACS2721 ΓòÉΓòÉΓòÉ

ACS2721-E The workstation type specified in the Communications Manager
initialization file is not a valid workstation type.

Originator: Communications Manager Kernel

User Response: If you are running on a Single User workstation, the value in
the CMWorkStationType field of the Communications Manager initialization file
should be 1. If you are running on a Redirected workstation, the value in the
CMWorkStationType field of the Communications Manager initialization file
should be 4.


ΓòÉΓòÉΓòÉ 3.28.12. ACS2722 ΓòÉΓòÉΓòÉ

ACS2722-W An attempt was made to access the Communications Manager kernel
services without proper initialization.  Refer to the Communications Manager
Application Programming Guide for information about using the kernel API.

Originator: Communications Manager Kernel

Explanation: A call to the CmkKernelReg service routine is required before
requests for activation or deactivation can be processed.


ΓòÉΓòÉΓòÉ 3.28.13. ACS2723 ΓòÉΓòÉΓòÉ

ACS2723-W This service cannot be stopped because other active services require
that it remains active.  The service will remain active.

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.28.14. ACS2724 ΓòÉΓòÉΓòÉ

ACS2724-W The requested service is not supported by the service routines of the
Communications Manager kernel.  Supported services are APPC, ACDI, SRPI, and
EMULATORS.  Refer to the Communications Manager Application Programming Guide
for information about using the kernel API.

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.28.15. ACS2725 ΓòÉΓòÉΓòÉ

ACS2725-E name(4) cannot be started because it is not configured in the active
configuration file.

where
name(4)         = service name

Originator: Communications Manager Kernel

User Response: Stop and restart Communications Manager with the correct
configuration file, or run CMSETUP and configure the active configuration file
to include the specified service.


ΓòÉΓòÉΓòÉ 3.28.16. ACS2726 ΓòÉΓòÉΓòÉ

ACS2726-E The code pages in the CONFIG.SYS file do not match the code pages
used by Communications Manager.  Some characters might not be displayed
properly.

Originator: Communications Manager Kernel

User Response: Set the proper code pages in the CODEPAGE= statement in the
CONFIG.SYS file.  Then restart the system.


ΓòÉΓòÉΓòÉ 3.28.17. ACS2727 ΓòÉΓòÉΓòÉ

ACS2727-W One or more emulator sessions have been selected to be stopped
abnormally.  Select OK to stop the sessions abnormally.  Select Cancel to
cancel the request.

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.28.18. ACS2728 ΓòÉΓòÉΓòÉ

ACS2728-W Communications Manager is stopping and the 3270/5250 Session Manager
will not be available.

Originator: Communications Manager Kernel


ΓòÉΓòÉΓòÉ 3.28.19. ACS2729 ΓòÉΓòÉΓòÉ

ACS2729-E The version number of configuration name(255) is not compatible with
the current version of Communications Manager.  This configuration must be
upgraded in order to use it.

where
name(255)       = configuration file name

Originator: Communications Manager Kernel

Explanation: The specified configuration was created with a version of
Communications Manager that is different than the current version.

User Response: Run the Communications Manager setup program and select the
specified configuration.  This will invoke the upgrade utility that is used to
make the necessary modifications to run this configuration with the current
version of Communications Manager.  You can also run the upgrade utility from
the OS/2 command prompt by typing CMUPGRAD X where X is the configuration file
name (with or without the extension).


ΓòÉΓòÉΓòÉ 3.28.20. ACS2730 ΓòÉΓòÉΓòÉ

ACS2730-I The current trace buffer has been saved to file name(256).

where
name(256)       = trace file name

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.28.21. ACS2731 ΓòÉΓòÉΓòÉ

ACS2731-E The request to format a trace file has ended because of an internal
error.  The formatted trace files may not have been saved.

Originator: Problem Determination

Explanation:

Problem Determination Aids - Trace uses the command FMTTRACE to format trace
data.  When FMTTRACE encounters a failure, it returns a return code of 1
signifying that failure.  This message is displayed in response to that error
code.

User Response:

Format the trace file using the FMTTRACE command.  The command line parameters
for FMTTRACE match the options available from the Format Trace window.  To get
help for FMTTRACE, type FMTTRACE ? at the command prompt.


ΓòÉΓòÉΓòÉ 3.28.22. ACS2732 ΓòÉΓòÉΓòÉ

ACS2732-I The trace file was not saved because the trace buffer is empty.

Originator: Problem Determination

Explanation: Likely causes are:

o No traces were started and stopped prior to the save attempt.

o No Communications Manager activity occurred while the traces were active.

User Response: Return to the Problem Determination Aids - Trace Services window
and start the needed traces.  After some Communications Manager activity has
taken place, try to save the trace file again.


ΓòÉΓòÉΓòÉ 3.28.23. ACS2733 ΓòÉΓòÉΓòÉ

ACS2733-I The request to format a trace file has completed.  The files have
been saved on the drive and path specified in the request.

Originator: Problem Determination


ΓòÉΓòÉΓòÉ 3.28.24. ACS2734 ΓòÉΓòÉΓòÉ

ACS2734-I No dump file was created.

Originator: Problem Determination

Explanation: The components requested are not active and did not submit any
dump data to Dump Services.

User Response: Activate the components, and then resubmit the dump request.


ΓòÉΓòÉΓòÉ 3.28.25. ACS2750 ΓòÉΓòÉΓòÉ

ACS2750-E Management support for NetWare has ended due to a critical system
error.

Originator: SNA Management Support for NetWare

Explanation: A return code from either a system call or a NetWare application
programming interface (API) call indicates that a critical system error has
occurred.

User Response: Do the following: 1.  Check the NetWare server to determine if
there is a software or hardware problem. 2.  Then check all cables,
connections, and related hardware in the LAN to determine where a possible
failure may have occurred. 3.  Note the date, time, and problem ID from the
FFST/2 message log formatter.  To locate and review the associated error log
entries, use FFST/2 to access the system error log. Follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.


ΓòÉΓòÉΓòÉ 3.28.26. ACS2751 ΓòÉΓòÉΓòÉ

ACS2751-E Management support for NetWare has ended. The reconnect time limit
has expired.

Originator: SNA Management Support for NetWare

Explanation: Management support for NetWare has ended due to a failed
reconnect.  When a data link control (DLC) connection failure is detected,
reconnection is attempted until the time limit expires.

User Response: Do the following: 1.  Check the NetWare server to determine if
there is a software or hardware problem. 2.  Then check all cables,
connections, and related hardware in the LAN to determine where a possible
failure may have occurred. 3.  Note the date, time, and problem ID from the
FFST/2 message log formatter.  To locate and review the associated error log
entries, use FFST/2 to access the system error log. Follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.


ΓòÉΓòÉΓòÉ 3.28.27. ACS2752 ΓòÉΓòÉΓòÉ

ACS2752-E Management support for NetWare has ended. The attempt to reconnect
the link between Communications Manager and the NetWare server failed because
the link was not active.

Originator: SNA Management Support for NetWare

Explanation: A valid link status must be received before the link between
Communications Manager and the NetWare server can be reconnected after a
temporary interruption.

User Response: Do the following: 1.  Check the NetWare server to determine if
there is a software or hardware problem. 2.  Then check all cables,
connections, and related hardware in the LAN to determine where a possible
failure may have occurred. 3.  Note the date, time, and problem ID from the
FFST/2 message log formatter.  To locate and review the associated error log
entries, use FFST/2 to access the system error log. Follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.


ΓòÉΓòÉΓòÉ 3.28.28. ACS2753 ΓòÉΓòÉΓòÉ

ACS2753-E Management support for NetWare has detected a critical system error.
This error will cause management support for NetWare to be ended by the calling
program.

Originator: SNA Management Support for NetWare

User Response: Do the following: 1.  Check the NetWare server to determine if
there is a software or hardware problem. 2.  Then check all cables,
connections, and related hardware in the LAN to determine where a possible
failure may have occurred. 3.  Note the date, time, and problem ID from the
FFST/2 message log formatter.  To locate and review the associated error log
entries, use FFST/2 to access the system error log. Follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.


ΓòÉΓòÉΓòÉ 3.28.29. ACS2754 ΓòÉΓòÉΓòÉ

ACS2754-E Management support for NetWare has ended. A link between
Communications Manager and the NetWare server could not be established because
of a problem reported by the NetWare server.

Originator: SNA Management Support for NetWare

User Response: Do the following: 1.  Check the NetWare server to determine if
there is a software or hardware problem. 2.  Then check all cables,
connections, and related hardware in the LAN to determine where a possible
failure may have occurred. 3.  Note the date, time, and problem ID from the
FFST/2 message log formatter.  To locate and review the associated error log
entries, use FFST/2 to access the system error log. Follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.


ΓòÉΓòÉΓòÉ 3.28.30. ACS2755 ΓòÉΓòÉΓòÉ

ACS2755-E Management support for NetWare has ended because the NetWare server
connection to the host failed.

Originator: SNA Management Support for NetWare

User Response: Do the following: 1.  Check Communications Manager Setup for
your NetWare configuration. 2.  Check the NetWare server for failed or unloaded
NetWare for Systems Application Architecture (SAA) profiles. 3.  Ensure that
your NetWare servers are running with a COMMEXEC version of 1.3.30 or higher.
If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.29. ACS2756 through ACS2800 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.29.1. ACS2756 ΓòÉΓòÉΓòÉ

ACS2756-E Management support for NetWare has ended.  The NetWare user ID or
password configured on Communications Manager does not match the user ID or
password configured on the NetWare server.

Originator: SNA Management Support for NetWare

Explanation: Communications Manager uses the Local Node name from the Local
Node Characteristics window in the Communications Manager Setup program as the
NetWare user ID when attempting to establish a connection to the NetWare
server. The corresponding password is configured on the SNA Management Support
for NetWare window.  The user ID and password must be defined on the NetWare
server.

User Response: Do the following: 1.  Compare the NetWare user ID and password
for Communications Manager and the NetWare server. 2.  Correct any
inconsistencies. 3.  Stop Communications Manager and restart. If the problem
persists, follow your local network operating procedures.  If this does not
resolve the problem, contact your service representative.


ΓòÉΓòÉΓòÉ 3.29.2. ACS2757 ΓòÉΓòÉΓòÉ

ACS2757-E Management support for NetWare has ended.  Communications Manager was
unable to establish a connection to a NetWare server.

Originator: SNA Management Support for NetWare

User Response: Check to make sure that your NetWare servers have a COMMEXEC
loaded with a version of 1.3.30 or higher.  If the version is not 1.3.30 or
higher, upgrade NetWare for Systems Application Architecture (SAA) on your
NetWare servers. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.


ΓòÉΓòÉΓòÉ 3.29.3. ACS2760 ΓòÉΓòÉΓòÉ

ACS2760-E The total number of SVCs configured for link name(20) must be greater
than or equal to the number of incoming and outgoing connections.

where
name(20)        = link name

Originator: Configuration Services

Explanation: The number of incoming connections is specified in the X.25 DLC
and must be less than or equal to the number of in-only and two-way SVCs.  The
number of outgoing connections is the number of remote SNA SVC directory
entries configured for this link and must be less than or equal to the number
of out-only and two-way SVCs.

User Response: Do one of the following:

o Increase the number of SVCs configured on the Virtual Circuit Ranges window,
  or

o Decrease the number of incoming connections specified on the X.25 DLC
  Parameters window, and/or

   Decrease the number of outgoing connections by deleting the number of remote
   SNA SVC directory entries on the X.25 Directory Entries window.


ΓòÉΓòÉΓòÉ 3.29.4. ACS2761 ΓòÉΓòÉΓòÉ

ACS2761-E The total number of dedicated logical adapters exceeds the total
supported by this DLC.  Decrease the number of dedicated logical adapters.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.5. ACS2762 ΓòÉΓòÉΓòÉ

ACS2762-E Each special character must be unique.  Two or more special
characters are the same.  Enter a unique character in each special character
field.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.6. ACS2763 ΓòÉΓòÉΓòÉ

ACS2763-E The answer delay field must contain a value when DTE is selected.
Either enter a value in the answer delay field, or select DCE as the
auto-answer choice.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.7. ACS2764 ΓòÉΓòÉΓòÉ

ACS2764-E The Type field must contain a value when a failure string is defined.
Either select a failure type for the failure string, or erase the text in the
failure string field.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.8. ACS2766 ΓòÉΓòÉΓòÉ

ACS2766-E The specified workstation LU name has already been defined. Specify a
unique workstation LU name.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.9. ACS2767 ΓòÉΓòÉΓòÉ

ACS2767-E The specified workstation NAU address already exists for another
workstation LU name.  Specify a unique workstation NAU address.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.10. ACS2768 ΓòÉΓòÉΓòÉ

ACS2768-E The specified host NAU address already exists for another workstation
LU name.  Specify a unique host NAU address.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.11. ACS2769 ΓòÉΓòÉΓòÉ

ACS2769-E name(20) already exists, enter a unique name.

where
name(20)        = item name

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.12. ACS2770 ΓòÉΓòÉΓòÉ

ACS2770-W Management support for NetWare logged an error because the data
received could not be interpreted.

Originator: SNA Management Support for NetWare

Explanation: Management support for NetWare could not process the data
received.  The data is logged in the system error log.

User Response: Check the NetWare server to determine if there is a software or
hardware problem. Note the date, time, and problem ID from the FFST/2 message
log formatter.  To locate and review the associated error log entries, use
FFST/2 to access the system error log. If the problem persists, follow your
local network operating procedures.  If this does not resolve the problem,
contact your service representative.


ΓòÉΓòÉΓòÉ 3.29.13. ACS2773 ΓòÉΓòÉΓòÉ

ACS2773-W Management support for NetWare logged an error.  The NetWare server
data is not valid.

Originator: SNA Management Support for NetWare

Explanation: Management support for NetWare could not process the data
received.  The data will be logged in the system error log.

User Response: Check the NetWare server to determine if there is a software or
hardware problem. Note the date, time, and problem ID from the FFST/2 message
log formatter.  To locate and review the associated error log entries, use
FFST/2 to access the system error log. If the problem persists, follow your
local network operating procedures.  If this does not resolve the problem,
contact your service representative.


ΓòÉΓòÉΓòÉ 3.29.14. ACS2774 ΓòÉΓòÉΓòÉ

ACS2774-W Management support for NetWare received data that is not valid.

Originator: SNA Management Support for NetWare

Explanation: Management support for NetWare could not process the data. The
data will be logged to the system error log.

User Response: Check the NetWare server to determine if there is a software or
hardware problem. Note the date, time, and problem ID from the FFST/2 message
log formatter.  To locate and review the associated error log entries, use
FFST/2 to access the system error log. If the problem persists, follow your
local network operating procedures.  If this does not resolve the problem,
contact your service representative.


ΓòÉΓòÉΓòÉ 3.29.15. ACS2780 ΓòÉΓòÉΓòÉ

ACS2780-E The incoming call directory entry (ICDE) name name(16) could not be
found.

where
name(16)        = incoming call directory entry name

Originator: Subsystem Management

Explanation: The ICDE entry name was not found among those configured for
Communications Manager.  Possible causes are:

o The ICDE entry name is misspelled.

o The ICDE entry name is correct, but it is configured for a communications
  software package other than Communications Manager.

o The ICDE entry name was correct, but another program has deleted it from the
  currently active configuration.

User Response: Retry the command with the correct ICDE entry name.


ΓòÉΓòÉΓòÉ 3.29.16. ACS2785 ΓòÉΓòÉΓòÉ

ACS2785-E A maximum of 128 virtual circuits can be configured per link.  The
maximum number has been exceeded.

Originator: Configuration Services

User Response: Decrease the number of SVCs configured on the Virtual Circuit
Ranges window, or decrease the number of PVCs configured on the X.25 Permanent
Virtual Circuits window.


ΓòÉΓòÉΓòÉ 3.29.17. ACS2786 ΓòÉΓòÉΓòÉ

ACS2786-E The remote DTE address must be unique for each link associated with a
remote SVC directory entry.  Change the remote DTE address.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.18. ACS2787 ΓòÉΓòÉΓòÉ

ACS2787-I To configure this DLC using ISDN, you must also configure the ISDN
profiles.

Originator: Configuration Services

User Response: To configure the ISDN profiles:

o From the Communications Manager Configuration Definition window, select the
  Options pull-down menu.

o Select Configure any profile or feature to get to the Communications Manager
  Configuration List window.

o Select Connection Manager, Port Connection Manager, or Protocol Driver, then
  select Configure.


ΓòÉΓòÉΓòÉ 3.29.19. ACS2788 ΓòÉΓòÉΓòÉ

ACS2788-I To configure X.25 DLC, you must also configure X.25 links, X.25
directory entries, and X.25 routing table.  If you are configuring for ISDN,
you must also configure the ISDN profiles.

Originator: Configuration Services

User Response: To configure the X.25 and ISDN profiles:

o From the Communications Manager Configuration Definition window, select the
  Options pull-down menu.

o Select Configure any profile or feature to get to the Communications Manager
  Configuration List window.

o Select X.25 links, X.25 directory entries, and X.25 routing table, then
  select Configure.

  Note:  If you are configuring for ISDN, you can configure the following ISDN
  profiles from this list:  Connection Manager, Port Connection Manager, or
  Protocol Driver.


ΓòÉΓòÉΓòÉ 3.29.20. ACS2790 ΓòÉΓòÉΓòÉ

ACS2790-E Both name(20) DLC adapters 0 and 1 have already been configured.

where
name(20)        = connection name

Originator: Configuration Services

Explanation: You are trying to configure a DLC adapter that has previously been
configured.

User Response: To configure an adapter for this DLC, delete the previously
configured adapter.  Go to the appropriate adapter parameters window and, from
the adapter list, delete the adapter you are trying to configure.


ΓòÉΓòÉΓòÉ 3.29.21. ACS2791 ΓòÉΓòÉΓòÉ

ACS2791-I This name is already in the list of items.

Originator: Configuration Services

Explanation: The selected name is already included in this access definition.
No more than one occurrence of each LU name, machine name, LUA pool name, and
user or group ID can appear within a single definition.


ΓòÉΓòÉΓòÉ 3.29.22. ACS2792 ΓòÉΓòÉΓòÉ

ACS2792-I The maximum number of items has been reached.  Each verb definition
can contain up to 255 unique items.

Originator: Configuration Services

Explanation: Examples of items are LU names, LU aliases, machine names,
user/group IDs, and LUA pool names.


ΓòÉΓòÉΓòÉ 3.29.23. ACS2793 ΓòÉΓòÉΓòÉ

ACS2793-E Please enter a unique name.

Originator: Configuration Services

Explanation: A verb definition with this name already exists.


ΓòÉΓòÉΓòÉ 3.29.24. ACS2794 ΓòÉΓòÉΓòÉ

ACS2794-E This LU alias is already used in this or another definition.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.25. ACS2795 ΓòÉΓòÉΓòÉ

ACS2795-E The access definition must include at least one logical unit (LU)
name or logical unit application (LUA) pool name.

Originator: Configuration Services

Explanation: An LUA access definition must include the name of at least one LU
or LUA pool at the communications server to which the users and workstations in
the definition have access.

User Response: Do the following: Add an LU name or an LUA pool name.  Select
the list to which you want to add a name, then select a name from the Available
for use list.  If the name you want to add does not appear in the Available for
use list, select Create.


ΓòÉΓòÉΓòÉ 3.29.26. ACS2796 ΓòÉΓòÉΓòÉ

ACS2796-I The Host link name used for this definition does not exist. This will
cause verification of this configuration to fail.

Originator: Configuration Services

User Response: Select the Connections profile to configure the host links.

o Select SNA Connections and then select Configure in the Communications
  Manager Profile List window.

o Select To host and then select Create in the Connections List window.

o Select the desired adapter type and then select OK in the Adapter List
  window.

o Fill in the fields and then select OK in the Create a Connection to a Host
  window.

o Select Close in the Connections List window to return.


ΓòÉΓòÉΓòÉ 3.29.27. ACS2797 ΓòÉΓòÉΓòÉ

ACS2797-E Define at least one gateway host link and host LU pool before
defining implicit workstations using the gateway.

Originator: Configuration Services

User Response: Select Gateway - Hosts and host LU pools from the Communications
Manager Profile List window to define a gateway host link and host LU pools.


ΓòÉΓòÉΓòÉ 3.29.28. ACS2798 ΓòÉΓòÉΓòÉ

ACS2798-E The XID repoll count of 0 is not valid for a switched line. The
repoll count must be in the range of 1-255 for a switched line, and 0-255 for a
non-switched line.

Originator: Configuration Services


ΓòÉΓòÉΓòÉ 3.29.29. ACS2799 ΓòÉΓòÉΓòÉ

ACS2799-E Define at least one gateway host link before defining explicit
workstations using the gateway.

Originator: Configuration Services

User Response: Select Gateway - Hosts and host LU pools from the Communications
Manager Profile List window to define a gateway host link and optional host LU
pool.


ΓòÉΓòÉΓòÉ 3.29.30. ACS2800 ΓòÉΓòÉΓòÉ

ACS2800-E ALERT:  A link time-out has occurred because the remote station is
not responding.

Originator: IBM IDLC

Explanation: The retransmission threshold (N200) was exceeded before a response
was received from the remote station.

User Response: Do the following: 1.  Review the formatted alert. 2.  Locate the
remote station and identify the virtual port from the adapter number field. 3.
Check the FFST/2 message log on the remote station for errors and correct them.
Then retry the operation. 4.  If the remote software is operational, the link
time-out in the local Communications Manager adapter profile needs to be
increased.  The link time-out value is T200 * (N200+1).  In the IDLC adapter
profile, increase the appropriate protocol parameter (T200 or N200) value.
Restart Communications Manager and retry the operation. If the problem
persists, follow your local network operating procedures.  If this does not
resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30. ACS2801 through ACS2841 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.30.1. ACS2801 ΓòÉΓòÉΓòÉ

ACS2801-E ALERT:  The remote station attempted to establish a logical link that
already exists.  The existing logical link was deactivated.

Originator: IBM IDLC

Explanation: A Set Asynchronous Balance Mode Extended (SABME) command was
received and it deactivated an active link.

User Response: Do the following: 1.  Review the formatted alert and locate the
remote station. 2.  Check the FFST/2 message log for remote station errors and
correct them. 3.  Use Subsystem Management to restart the logical link. 4.
Retry the operation. If the problem persists, follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.2. ACS2802 ΓòÉΓòÉΓòÉ

ACS2802-E ALERT:  The remote station sent a Disconnect Mode (DM) command
causing the logical link to be deactivated.

Originator: IBM IDLC

Explanation: The remote station has notified the local station that the logical
link is disconnected.

User Response: Do the following: 1.  Review the formatted alert and locate the
remote station. 2.  Check the FFST/2 message log for remote station errors and
correct them. 3.  If necessary, use Subsystem Management to restart the logical
link. 4.  Retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.3. ACS2803 ΓòÉΓòÉΓòÉ

ACS2803-E ALERT:  The remote station sent a Frame Reject (FRMR) command,
causing the logical link to be deactivated.  This occurred because a command
that is not supported was received from the local station.

Originator: IBM IDLC

User Response: Use Subsystem Management to restart the logical link for this
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.4. ACS2804 ΓòÉΓòÉΓòÉ

ACS2804-E ALERT:  The remote station sent a Frame Reject (FRMR) command,
causing the logical link to be deactivated.  This occurred because a command
with an information field (I-field) that is not supported was received from the
local station.

Originator: IBM IDLC

User Response: Use Subsystem Management to restart the logical link for this
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.5. ACS2805 ΓòÉΓòÉΓòÉ

ACS2805-E ALERT:  The remote station sent a Frame Reject (FRMR) command,
causing the logical link to be deactivated.  This occurred because a sequence
count (Nr) that is not valid was received from the local station.

Originator: IBM IDLC

User Response: Use Subsystem Management to restart the logical link for this
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.6. ACS2806 ΓòÉΓòÉΓòÉ

ACS2806-E ALERT:  The remote station sent a Frame Reject (FRMR) command,
causing the logical link to be deactivated.  This occurred because an
information field (I-field) that exceeded the maximum length was received from
the local station.

Originator: IBM IDLC

Explanation: This occurs when the remote station is a physical unit (PU), type
2.0, and link parameters are not negotiable.

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the virtual port from the adapter number field. 3.  Change the adapter
configuration so that both stations contain the same value for the maximum
I-field parameter. 4.  Restart Communications Manager and retry the operation.
If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.7. ACS2807 ΓòÉΓòÉΓòÉ

ACS2807-E ALERT:  The local station sent a Frame Reject (FRMR) command, causing
the logical link to be deactivated.  This occurred because the local station
received a command that is not supported.

Originator: IBM IDLC

User Response: Use Subsystem Management to restart the logical link for this
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.8. ACS2808 ΓòÉΓòÉΓòÉ

ACS2808-E ALERT:  The local station sent a Frame Reject (FRMR) command, causing
the logical link to be deactivated.  This occurred because the local station
received a command with an information field (I-field) that is not supported.

Originator: IBM IDLC

User Response: Use Subsystem Management to restart the logical link for this
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.9. ACS2809 ΓòÉΓòÉΓòÉ

ACS2809-E ALERT:  The local station sent a Frame Reject (FRMR) command, causing
the logical link to be deactivated.  This occurred because the local station
received a sequence count (Nr) that is not valid.

Originator: IBM IDLC

User Response: Use Subsystem Management to restart the logical link for this
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named (EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.10. ACS2810 ΓòÉΓòÉΓòÉ

ACS2810-E ALERT:  The local station sent a Frame Reject (FRMR) command, causing
the logical link to be deactivated.  This occurred because the local station
received an information field (I-field) that exceeded the maximum length.

Originator: IBM IDLC

Explanation: This occurs when the remote station is a physical unit (PU), type
2.0, and link parameters are not negotiable.

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the virtual port from the adapter number field. 3.  Change the adapter
configuration for both stations so that they have the same value for the
maximum I-field parameter. 4.  Restart Communications Manager and retry the
operation. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.11. ACS2811 ΓòÉΓòÉΓòÉ

ACS2811-E ALERT:  The local station sent an XID to initialize a logical link
for an integrated data link control (IDLC) logical adapter, but the retry count
was exceeded before a response was received from the remote station.

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Locate the
remote station and identify the virtual port from the adapter number field. 3.
Make sure that the IDLC link address in the Communications Manager
configuration is the same as the one used for the remote station. 4.  If the
IDLC link address is the same value used at the remote station, the time-out
value used to initialize a link needs to be increased.

o The value used to initialize a link is calculated as follows:  (XID timer) *
  (XID retransmission count + 1).

o In the IDLC adapter profile, increase the appropriate protocol parameter (XID
  timer or XID retransmission count) value.

5.  Restart Communications Manager and retry the operation. If the problem
persists, follow your local network operating procedures.  If this does not
resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.12. ACS2812 ΓòÉΓòÉΓòÉ

ACS2812-E ALERT:  The local station sent a Set Asynchronous Balanced Mode
Extended (SABME) command, but the retransmission threshold (N200) was exceeded
before a response was received from the remote station.

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Locate the
remote station and identify the virtual port from the adapter number field. 3.
Check the FFST/2 message log on the remote station for errors and correct them.
Then retry the operation. 4.  If the remote software is operational, the link
time-out in the local Communications Manager adapter profile needs to be
increased.  The link time-out value is T200 * (N200+1).  In the IDLC adapter
profile, increase the appropriate protocol parameter (T200 or N200) values.
Restart Communications Manager and retry the operation. If the problem
persists, follow your local network operating procedures.  If this does not
resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time, and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.13. ACS2813 ΓòÉΓòÉΓòÉ

ACS2813-E ALERT:  There is not enough system memory to create a new integrated
data link control (IDLC) logical adapter.

Originator: IBM IDLC

User Response: Do one or more of the following:

o Change the MEMMAN parameter in the local CONFIG.SYS file to SWAP, MOVE.  Then
  restart your system and retry the operation.

o Free up memory by stopping active programs that are not necessary.  Use
  Subsystem Management to restart the logical link, and if necessary, restart
  the data link control (DLC) for this logical adapter.

o Add additional random access memory (RAM) to the workstation.  Then restart
  your system and retry the operation.

If the problem persists, follow your local network operating procedures.  If
this does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.14. ACS2814 ΓòÉΓòÉΓòÉ

ACS2814-E ALERT:  The integrated data link control (IDLC) logical adapter was
closed because the media access control (MAC) driver detected an internal
software error.

Originator: IBM IDLC

User Response: To find detailed information about this error, check the FFST/2
message log for information logged by the adapter support program and correct
the error.  Then retry the operation. If the problem persists, follow your
local network operating procedures.  If this does not resolve the problem,
contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.15. ACS2815 ΓòÉΓòÉΓòÉ

ACS2815-E ALERT:  The operating system did not respond successfully to a system
request for an integrated data link control (IDLC) logical adapter.

Originator: IBM IDLC

User Response: Restart your system and retry the operation. If the problem
persists, follow your local network operating procedures.  If this does not
resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.16. ACS2816 ΓòÉΓòÉΓòÉ

ACS2816-E ALERT: The integrated data link control (IDLC) protocol driver did
not respond successfully to a request for an IDLC logical adapter.

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the logical adapter number. 3.  Use Subsystem Management to restart the logical
link, and if necessary, restart the data link control (DLC) for this logical
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.17. ACS2817 ΓòÉΓòÉΓòÉ

ACS2817-E ALERT:  The advanced program-to-program communication (APPC) feature
sent a command that is not supported by integrated data link control (IDLC).

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the logical adapter number. 3.  Use Subsystem Management to restart the logical
link, and if necessary, restart the data link control (DLC) for this logical
adapter.  Then retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.18. ACS2818 ΓòÉΓòÉΓòÉ

ACS2818-E ALERT:  The integrated data link control (IDLC) logical adapter was
closed because IDLC data link control (DLC) detected a software error.

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the logical adapter number. 3.  Use Subsystem Management to restart the logical
link, and if necessary, restart the DLC for this logical adapter.  Then retry
the operation. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.19. ACS2819 ΓòÉΓòÉΓòÉ

ACS2819-E ALERT:  The IDLCDD.SYS device driver is not active.

Originator: IBM IDLC

Explanation: The DEVICE=d:\CMLIB\IDLCDD.SYS statement, where d is the drive
where Communications Manager resides, is missing in the CONFIG.SYS file because
it was removed or Communications Manager Setup ended before updating the
CONFIG.SYS file.

User Response: Do the following: 1.  Use Communications Manager Setup to access
the active configuration. 2.  Exit Communications Manager Setup and select OK
to update the system files. 3.  Restart your system and retry the operation. If
the problem persists, follow your local network operating procedures.  If this
does not resolve the problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.20. ACS2820 ΓòÉΓòÉΓòÉ

ACS2820-E ALERT:  Integrated data link control (IDLC) is unable to start
another operating system thread because the maximum number of threads specified
in the CONFIG.SYS file is too low.

Originator: IBM IDLC

User Response: Do the following: 1.  In the CONFIG.SYS file, increase the value
specified in the THREADS= statement. 2.  Restart your system and retry the
operation. If the problem persists, follow your local network operating
procedures.  If this does not resolve the problem, contact your service
representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.21. ACS2821 ΓòÉΓòÉΓòÉ

ACS2821-E ALERT:  The IDLCPD.SYS device driver is not active.

Originator: IBM IDLC

Explanation: The DEVICE=d:\CMLIB\IDLCPD.SYS statement, where d is the drive
where Communications Manager resides, is missing in the CONFIG.SYS file because
it was removed or Communications Manager Setup ended before updating the
CONFIG.SYS file.

User Response: Do the following: 1.  Check for initialization errors in the
FFST/2 message log and correct them. 2.  If no errors were found, use
Communications Manager Setup to access the active configuration.  Exit
Communications Manager Setup and select OK to update the system files. 3.
Restart your system and retry the operation. If the problem persists, follow
your local network operating procedures.  If this does not resolve the problem,
contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.22. ACS2822 ΓòÉΓòÉΓòÉ

ACS2822-E ALERT:  The specified number of transmit elements in the integrated
data link control (IDLC) protocol driver configuration is too low to satisfy
the current request.

Originator: IBM IDLC

User Response: Do the following: 1.  Use Communications Manager Setup to
increase the number of transmit elements for the IDLC protocol driver.  The
number that you specify must be changed for all logical adapters that are
associated with this IDLC data link control (DLC) virtual port. 2.  Restart
your system and retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.23. ACS2823 ΓòÉΓòÉΓòÉ

ACS2823-E ALERT:  The maximum number (16) of applications for the integrated
data link control (IDLC) logical adapter was exceeded.

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the logical adapter number. 3.  Stop one or more of the applications that are
using this logical adapter.  Then retry the operation. If the problem persists,
follow your local network operating procedures.  If this does not resolve the
problem, contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.24. ACS2824 ΓòÉΓòÉΓòÉ

ACS2824-E ALERT:  The integrated data link control (IDLC) logical adapter that
was requested is not configured.

Originator: IBM IDLC

User Response: Do the following: 1.  Review the formatted alert. 2.  Identify
the logical adapter number. 3.  Use Communications Manager Setup to configure
the IDLC protocol driver for the appropriate logical adapter number. 4.
Restart your system and retry the operation. If the problem persists, follow
your local network operating procedures.  If this does not resolve the problem,
contact your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.25. ACS2825 ΓòÉΓòÉΓòÉ

ACS2825-E ALERT:  The maximum number of link stations specified for the
integrated data link control (IDLC) logical adapter was exceeded.

Originator: IBM IDLC

User Response: Do the following: 1.  Use Communications Manager Setup to
increase the number of logical links for the IDLC protocol driver.  The number
that you specify must be changed for all logical adapters that are associated
with this IDLC data link control (DLC) virtual port. 2.  Restart your system
and retry the operation. If the problem persists, follow your local network
operating procedures.  If this does not resolve the problem, contact your
service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.26. ACS2826 ΓòÉΓòÉΓòÉ

ACS2826-E ALERT:  The integrated data link control (IDLC) protocol driver found
an error when it attempted to initialize the media access control (MAC) driver.

Originator: IBM IDLC

User Response: Do the following: 1.  Check for MAC driver errors in the FFST/2
message log and correct them. 2.  If no errors were found, add the
RUN=d:\IBMCOM\NETBIND.EXE statement in the CONFIG.SYS file, where d is the
drive where LAN Adapter and Protocol Support (LAPS) resides. 3.  Restart your
system and retry the operation. If the problem persists, follow your local
network operating procedures.  If this does not resolve the problem, contact
your service representative.

Key Alert Information: For detailed information, record the date, time and
problem ID from the FFST/2 message log formatter.  Access the FFST/2 dump
formatter and open the alert log file named EPWALERT.DMP. From the drop-down
list, select the corresponding problem ID and review the formatted alert.


ΓòÉΓòÉΓòÉ 3.30.27. ACS2838 ΓòÉΓòÉΓòÉ

ACS2838-E The request of a Virtual Port to receive incoming calls has been
denied.  The Virtual Port may not have unique call acceptance criteria.

Originator: ISDN Connection Manager

User Response:

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.  This control block is
     provided for all failures.

   - Connection record:  Provides an internal representation of the data
     related to this connection over ISDN.  This control block is provided for
     call establish, call control, and call clear failures.

   - Active adapter record:  Provides an internal representation of the
     dynamically generated adapter used for this ISDN link.  This control block
     is provided for call establish, call control, and call clear failures.

   - Configured Virtual Port:  Provides an internal representation of the
     configured virtual port adapter from which the "active adapter" was
     generated.  This control block is provided for all call-related failures.

   - SAP status:  Provides the current status of the SAP.  This control block
     is provided for all SAP-related failures.


ΓòÉΓòÉΓòÉ 3.30.28. ACS2839 ΓòÉΓòÉΓòÉ

ACS2839-E Activation or deactivation of the CMI Service Access Point (SAP) has
failed.  If this occurs at start-up, ISDN will NOT be enabled.

Originator: ISDN Connection Manager

User Response:

o Locate the attempted API function and the secondary return code in the Extra
  Symptom String section of the associated system error log entry.

   - Return codes of 30xx or 33xx indicate the CMI completion code.

   - Return codes of 34xx indicate the CCITT cause value in the last byte.

   - Refer to ISDN CMI Programming Guide for corrective action relating to the
     return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.  This control block is
     provided for all failures.

   - Connection record:  Provides an internal representation of the data
     related to this connection over ISDN.  This control block is provided for
     call establish, call control, and call clear failures.

   - Active adapter record:  Provides an internal representation of the
     dynamically generated adapter used for this ISDN link.  This control block
     is provided for call establish, call control, and call clear failures.

   - Configured Virtual Port:  Provides an internal representation of the
     configured virtual port adapter from which the "active adapter" was
     generated.  This control block is provided for all call-related failures.

   - SAP status:  Provides the current status of the SAP.  This control block
     is provided for all SAP-related failures.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.30.29. ACS2840 ΓòÉΓòÉΓòÉ

ACS2840-W The long session name name(8) will be deleted.

where
name(8)         = long session name

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.30.30. ACS2841 ΓòÉΓòÉΓòÉ

ACS2841-E The specified data confidentiality session identifier is not valid.
Specify a valid identifier.

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.31. ACS2842 through ACS3104 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.31.1. ACS2842 ΓòÉΓòÉΓòÉ

ACS2842-W The maximum number of coaxial (DFT) sessions for this configuration
has been reached.

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.31.2. ACS2850 ΓòÉΓòÉΓòÉ

ACS2850-E The profile cannot be saved.

Originator: Keyboard Remap Utility

Explanation: Likely causes for this error are:

o The profile name entered is incorrect or contains a character that is not
  valid.

o The profile is locked.

o There is not enough disk space.

o There is not enough memory.

User Response:

o Check the profile name entered to be sure it is correct and does not contain
  a character that is not valid.

o Check to be sure that the keylock is not on.

o Clear some disk space.

o To obtain additional memory, reduce the number of programs running.


ΓòÉΓòÉΓòÉ 3.31.3. ACS2851 ΓòÉΓòÉΓòÉ

ACS2851-W There is not enough memory to run this function. Reduce the number of
programs running and try the function again.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.4. ACS2852 ΓòÉΓòÉΓòÉ

ACS2852-E Internal Keyboard Utility error psn(15) occurred.  Try the operation
again.  If the problem persists, note the time, date, and this message number;
then, contact your service coordinator.

where
psn(15)         = error occurred position

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.5. ACS2853 ΓòÉΓòÉΓòÉ

ACS2853-I The Keyboard Utility is starting. Please wait.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.6. ACS2854 ΓòÉΓòÉΓòÉ

ACS2854-E File name(12) was not found. Install the file in CMLIB or CMLIB\DLL.

where
name(12)        = file name

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.7. ACS2855 ΓòÉΓòÉΓòÉ

ACS2855-E You have chosen to close or save the open key name(5) when the Extend
window titled name(5) state name(8) still exists. Select OK to update the open
key or select Cancel to cancel the extend window.

where
name(5)         = open key title name
name(8)         = open key state name

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.8. ACS2856 ΓòÉΓòÉΓòÉ

ACS2856-W The file transfer name already exists. Specify a new file transfer
name.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.31.9. ACS2857 ΓòÉΓòÉΓòÉ

ACS2857-W The entry for the specified print properties combination will be
deleted.

Originator: 3270 Print Driver


ΓòÉΓòÉΓòÉ 3.31.10. ACS2858 ΓòÉΓòÉΓòÉ

ACS2858-W The 3270 long session name has not been specified for one or more
SRPI server alias.  Specify a 3270 long session name for each alias.

Originator: Verify and Convert Configuration File


ΓòÉΓòÉΓòÉ 3.31.11. ACS2859 ΓòÉΓòÉΓòÉ

ACS2859-E The server alias name name(8) already exists.  Specify a different
name.

where
name(8)         = server alias name

Originator: Emulator


ΓòÉΓòÉΓòÉ 3.31.12. ACS2860 ΓòÉΓòÉΓòÉ

ACS2860-W The maximum number (4) of Extend windows allowed has been reached.
At least one of the windows must be closed before another Extend window can be
opened.

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.13. ACS2870 ΓòÉΓòÉΓòÉ

ACS2870-Q You have chosen to move states between two keys.  Do you want to
proceed?

Originator: Keyboard Remap Utility

User Response:

o Select Yes to complete the move operation.

o Select No to cancel the move operation.


ΓòÉΓòÉΓòÉ 3.31.14. ACS2871 ΓòÉΓòÉΓòÉ

ACS2871-Q You have chosen to swap states between two keys.  Do you want to
proceed?

Originator: Keyboard Remap Utility

User Response:

o Select Yes to complete the swap operation.

o Select No to cancel the swap operation.


ΓòÉΓòÉΓòÉ 3.31.15. ACS2872 ΓòÉΓòÉΓòÉ

ACS2872-E You have chosen to copy, move, or swap when the content of open key
titled name(5) has been changed.  Please save or reset the open key and try the
operation again.

where
name(5)         = open key title name

Originator: Keyboard Remap Utility


ΓòÉΓòÉΓòÉ 3.31.16. ACS2873 ΓòÉΓòÉΓòÉ

ACS2873-E The coaxial (DFT) session number sessnum(1) already exists.  Specify
a different number.

where
sessnum(1)      = session number name

Originator: Configuration Services - Emulators


ΓòÉΓòÉΓòÉ 3.31.17. ACS2874 ΓòÉΓòÉΓòÉ

ACS2874-E The Workstation ID is incorrect.  Specify a different ID.

Originator: Configuration Services - Emulators


ΓòÉΓòÉΓòÉ 3.31.18. ACS2875 ΓòÉΓòÉΓòÉ

ACS2875-E The library name is incorrect.  Specify a different name.

Originator: Configuration Services - Emulators


ΓòÉΓòÉΓòÉ 3.31.19. ACS2876 ΓòÉΓòÉΓòÉ

ACS2876-W The profile is currently being used by another process. Try the
request again later.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.31.20. ACS2877 ΓòÉΓòÉΓòÉ

ACS2877-W The file transfer ended unexpectedly. Check the system error log for
additional information.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.31.21. ACS2878 ΓòÉΓòÉΓòÉ

ACS2878-E Code page value is not valid. Specify one of the code pages listed in
the drop-down list.

Originator: File Transfer


ΓòÉΓòÉΓòÉ 3.31.22. ACS2879 ΓòÉΓòÉΓòÉ

ACS2879-W The printer driver associated with the queue for this logical printer
session is not valid. Select one of the queues that are associated with the
valid printer driver in the Spooler Options window.

Originator: Configuration Services - Emulators


ΓòÉΓòÉΓòÉ 3.31.23. ACS2880 ΓòÉΓòÉΓòÉ

ACS2880-W The configuration file is being used by another process, such as
advanced configuration, and cannot be updated.  Your changes will not be saved.

Originator: Converged Emulator


ΓòÉΓòÉΓòÉ 3.31.24. ACS2881 ΓòÉΓòÉΓòÉ

ACS2881-I The session that you made changes to no longer exists in the
configuration file.  The session has been deleted by another process, such as
advanced configuration.  Your changes will not be saved.

Originator: Converged Emulator


ΓòÉΓòÉΓòÉ 3.31.25. ACS2885 ΓòÉΓòÉΓòÉ

ACS2885-E The maximum number of emulator terminal sessions has been exceeded.
This number is determined by the operating system.

Originator: Converged Emulator

Explanation: The system is most likely out of VIO handles.

User Response: Terminate other sessions or applications, and then retry the
operation.


ΓòÉΓòÉΓòÉ 3.31.26. ACS3100 ΓòÉΓòÉΓòÉ

ACS3100-E Conversation-level error.

Originator: SNA Communications Services (APPC)

Explanation: One of the following conditions occurred:

o A conversation error caused by failure of an ALLOCATE or SEND_CONVERSATION
  verb issued by a local TP.

o Issuance of any of the following verbs by a local or partner TP:

   - SEND_ERROR

   - MC_SEND_ERROR

   - DEALLOCATE with TYPE(ABEND_PROG, ABEND_SVC, or ABEND_TIMER)

   - MC_DEALLOCATE with TYPE(ABEND).

User Response: Locate the minor error code of the associated error log entry.
This minor error code provides the SNA-defined sense data that further isolates
the cause of the error.  Refer to Problem Determination Guide for sense
data-specific corrective action.

o If the sense data indicates the failure of a DEALLOCATE or SEND_ERROR verb,
  this message and the associated error log are informational, and require no
  user action.

o Otherwise, the indicated error must be corrected before the conversation will
  be successful.  Often, the sense data will indicate that the partner node's
  APPC Attach Manager rejected the ATTACH.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o If the error occurred because of an ATTACH failure, no additional data is
  logged in the associated error log entry.  If the error occurred because of a
  DEALLOCATE or SEND_ERROR verb, the following information is logged in the
  Additional Data section of the associated error log entry:

   - Offset/Length/Field Description

   - 0/1/ X'00' caused by a locally issued verb; X'01' caused by a remotely
     issued verb

   - 1/2/ LL field of the log data (if log data is present)

   - 3/Variable/ Log data from a DEALLOCATE or SEND_ERROR verb (if log data is
     present)

o When a DEALLOCATE or SEND_ERROR verb is issued, up to 32K bytes of log data
  may be included with the verb.  However, this entire field may not be shown
  in the error log; the amount logged is constrained by the RU size negotiated
  for the session.  For example, if the negotiated RU size is 512 bytes, only
  the first 512 bytes of log data are logged.


ΓòÉΓòÉΓòÉ 3.31.27. ACS3101 ΓòÉΓòÉΓòÉ

ACS3101-I Duplicate OAF/DAF received on BIND.

Originator: SNA Communications Services (APPN)

Explanation: A local LU received an incoming BIND request from a partner LU,
but the BIND request carried an OAF/DAF address that duplicated one that was
already active.

User Response: This is an unexpected protocol error by the partner LU.  No
action is required on your part.  If the condition continues, review the
offending Path Information Unit (PIU) that has been recorded in the Additional
Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.31.28. ACS3102 ΓòÉΓòÉΓòÉ

ACS3102-I Received request cannot be routed to an LU.

Originator: SNA Communications Services (APPN)

Explanation: A request or response was received from a partner LU, but the
resources associated with that request could not be found in the resource list
of the local LU.  This commonly occurs when a resource for a session is cleaned
up before all responses or requests have been received.  For example, the local
LU might send a CLEANUP UNBIND request that destroys all resources associated
with that session before the partner LU issues an UNBIND response.  When the
UNBIND response is received, the corresponding resources cannot be found.

User Response: This message and the associated error log entry are
informational.  No action is required on your part.  If the condition
continues, review the offending Path Information Unit (PIU) that has been
recorded in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.31.29. ACS3103 ΓòÉΓòÉΓòÉ

ACS3103-E Resource registration failed.

Originator: SNA Communications Services (APPN)

Explanation: The Directory Services (DS) component of local SNA was unable to
register its APPN resources with its Network Node (NN) server. The NN rejected
the registration attempt.  APPN communications through the NN is not possible.

User Response: Locate the SNA-defined sense data in the Additional Data section
of the associated error log entry; this data serves to isolate the cause of the
error.  See Problem Determination Guide for sense data-specific corrective
action.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/04/ sense data

   - 04/17/ Rejected local resource name

   - 22/17/ NN name


ΓòÉΓòÉΓòÉ 3.31.30. ACS3104 ΓòÉΓòÉΓòÉ

ACS3104-I Unexpected BID was received.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received a BID on a session from the partner node after
the partner node had sent a Bracket Initiation Stopped (BIS). After a BIS has
been received, an UNBIND response should be the next flow received from the
partner LU.

User Response: This is an unexpected protocol error by the partner LU, and may
require no action on your part.  However, if this condition continues, locate
the offending partner LU through tracing or contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32. ACS3105 through ACS3134 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.32.1. ACS3105 ΓòÉΓòÉΓòÉ

ACS3105-I Unexpected RTR was received.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received an unexpected incoming Ready To Receive (RTR)
request.

User Response: This is an unexpected protocol error by the partner LU.  No
action is required on your part.  If this condition continues, locate the
offending partner LU through tracing or contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.2. ACS3106 ΓòÉΓòÉΓòÉ

ACS3106-I Unexpected BIS reply was received.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received a BIS reply from the partner LU, but the local
LU had not sent a BIS request.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If this condition continues, locate the
offending partner LU through tracing or contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.3. ACS3107 ΓòÉΓòÉΓòÉ

ACS3107-I Basic conversation-level error.

Originator: SNA Communications Services (APPC)

Explanation: A conversation-level protocol error was detected by the local LU
for a basic conversation.  APPC deactivated the session with an UNBIND
response, indicating a protocol violation.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If the condition continues, locate the
SNA-defined sense data, which is represented by the minor error code of the
associated error log entry.  This data further isolates the cause of the error.
Refer to Problem Determination Guide for sense data-specific corrective action.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.4. ACS3108 ΓòÉΓòÉΓòÉ

ACS3108-E A conversation-level protocol error was detected by the local LU for
a mapped conversation.

Originator: SNA Communications Services (APPC)

Explanation: APPC internally issued an MC_DEALLOCATE with TYPE(ABEND) to end
the mapped conversation over which the protocol error occurred.

User Response: This is an unexpected protocol error by the partner LU. If this
condition continues, locate the offending partner LU through tracing or contact
your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.5. ACS3109 ΓòÉΓòÉΓòÉ

ACS3109-I Unexpected BIND response was received.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received an incoming BIND response from a partner LU,
but the local LU did not have a corresponding BIND request.

User Response: This is an unexpected protocol error by the partner LU.  No
action is required on your part.  If the condition continues, review the
offending Path Information Unit (PIU) that has been recorded in the Additional
Data section of the associated error log entry, or contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.6. ACS3110 ΓòÉΓòÉΓòÉ

ACS3110-I NS header in PIU is not valid.

Originator: SNA Communications Services (APPC)

Explanation: A frame was received by the local node in a session between a
System Services Control Point (SSCP) and a Logical Unit (LU) or a Physical Unit
(PU).  The Network Services (NS) header of the frame was not recognized on the
session.

User Response: This is an unexpected protocol error by the partner LU.  No
action is required on your part.  If the condition continues, review the
offending Path Information Unit (PIU) that has been recorded in the Additional
Data section of the associated error log entry, or contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.7. ACS3111 ΓòÉΓòÉΓòÉ

ACS3111-I RU received in UNBIND request is not valid.

Originator: SNA Communications Services (APPC)

Explanation: An UNBIND request was locally received with RU errors.

User Response: This is an unexpected protocol error by the partner LU.  No
action is required on your part.  If the condition continues, locate the
SNA-defined sense data, which is represented by the minor error code of the
associated error log entry.  This data further isolates the cause of the error.
Refer to Problem Determination Guide for sense data-specific corrective action.
The sense data, together with the offending Path Information Unit (PIU) that
has been recorded in the Additional Data section of the associated error log
entry, should assist in isolating the error.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.8. ACS3112 ΓòÉΓòÉΓòÉ

ACS3112-E Duplicate network resources.

Originator: SNA Communications Services (APPN)

Explanation: The Directory Services (DS) component of local SNA has detected
duplicate wildcard definitions of APPN network resources. Two independent
wildcard responses to a single LOCATE request were received.

User Response: Locate the fully qualified CP name (in EBCDIC) of the node that
issued the second wildcard response; this name is contained in the Additional
Data section of the associated error log entry.  Contact your local support
personnel with this information, or change the configuration on the remote CP
so that wildcard definitions are not used.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.9. ACS3113 ΓòÉΓòÉΓòÉ

ACS3113-E Network resource location conflict.

Originator: SNA Communications Services (APPN)

Explanation: The Directory Services (DS) component of local SNA detected a
conflict in the definition of the location of an APPN network resource. A
message was received specifying directory location information that is not
consistent with the existing local directory definition.

User Response: Locate the resource name in the Additional Data section of the
associated error log entry.  Review the local configuration to ensure that the
location of this resource is properly defined.  If it is properly defined,
contact your local support personnel and report this condition.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.10. ACS3114 ΓòÉΓòÉΓòÉ

ACS3114-I BIND request received was not valid.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received an incoming BIND request from a partner LU,
but the request had syntax, state, or semantic errors.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If the condition continues, locate the
SNA-defined sense data, which is represented by the minor error code of the
associated error log entry.  This data further isolates the cause of the error.
Refer to Problem Determination Guide for sense data-specific corrective action.
The sense data, together with the offending Path Information Unit (PIU) that
has been recorded in the Additional Data section of the associated error log
entry, should assist in isolating the error.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.11. ACS3115 ΓòÉΓòÉΓòÉ

ACS3115-I Duplicate BIS request was received.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received an incoming BIS request from a partner LU
after having already received one.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If this condition continues, locate the
offending partner LU through tracing or contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.12. ACS3116 ΓòÉΓòÉΓòÉ

ACS3116-I NS request received was not valid.

Originator: SNA Communications Services (APPN)

Explanation: A local LU received from a partner LU a request or response that
was not valid.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If the condition continues, locate the
SNA-defined sense data, which is represented by the minor error code of the
associated error log entry.  This data serves to further isolate the cause of
the error.  Refer to Problem Determination Guide for sense data-specific
corrective action. The sense data, together with the offending Path Information
Unit (PIU) that has been recorded in the Additional Data section of the
associated error log entry, should assist in isolating the error.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.13. ACS3117 ΓòÉΓòÉΓòÉ

ACS3117-I Session-level protocol error.

Originator: SNA Communications Services (APPC)

Explanation: The Half Session component of a local LU detected a protocol error
in an APPC session.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If the condition continues, locate the
SNA-defined sense data which is represented by the minor error code of the
associated error log entry.  This data serves to further isolate the cause of
the error.  Refer to Problem Determination Guide for sense data-specific
corrective action. The sense data, together with tracing Path Information Unit
(PIU) flows with the partner LU, should assist in isolating the error.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.14. ACS3118 ΓòÉΓòÉΓòÉ

ACS3118-I PIU received from the local DLC was not valid.

Originator: SNA Communications Services (APPN)

Explanation: A Path Information Unit (PIU) that contained an error was received
by local SNA from a DLC; however, the PIU did not contain enough information to
create a negative response.

User Response: This is not a protocol error, but rather the evidence of a
resource being cleaned up before the PIU was received; no action is required on
your part.  If the condition continues, locate the SNA-defined sense data,
which is represented by the minor error code of the associated error log entry.
This data serves to further isolate the cause of the error.  Refer to Problem
Determination Guide for sense data-specific corrective action. The sense data,
together with the offending Path Information Unit (PIU) that has been recorded
in the Additional Data section of the associated error log entry, should assist
in isolating the error.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.15. ACS3119 ΓòÉΓòÉΓòÉ

ACS3119-I Bracket error prevented session initialization.

Originator: SNA Communications Services (APPC)

Explanation: A local LU encountered a bracket error when starting a session
with a partner LU.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If this condition continues, locate the
offending partner LU through tracing or contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.16. ACS3120 ΓòÉΓòÉΓòÉ

ACS3120-I User-defined NMVT data logged.

Originator: SNA Communications Services (APPN)

Explanation: This condition was generated by a local MS application program
that issued a TRANSFER_MS_DATA or SEND_MDS_MU verb specifying a user-defined
data type.

User Response: Locate the originator program in the associated error log entry.
The user data logged by this program is recorded in the Additional Data section
of the associated error log entry.  Refer to the user-written programming
documentation for the specified program, and respond as necessary.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.17. ACS3121 ΓòÉΓòÉΓòÉ

ACS3121-I Non-alert NMVT data logged.

Originator: SNA Communications Services (APPN)

Explanation: Network management data was recorded by the local SNA, or, by a
local MS application program that issued a TRANSFER_MS_DATA or SEND_MDS_MU verb
specifying an NMVT data type.  A complete Network Management Vector Transport
(network services header, a management services (MS) major vector, and
appropriate MS subvectors) has been logged.  This condition may indicate the
loss, or impending loss, of an adapter or a network resource.  Alternatively, a
user-written program in your local machine may have issued a TRANSFER_MS_DATA
or SEND_MDS_MU verb.

o In addition to logging this condition locally, the local SNA may have also
  sent this NMVT to an application program that resides in a network management
  focal point.

User Response: Locate the originator program in the associated error log entry.
The NMVT logged by this program is recorded in the Additional Data section of
the associated error log entry.  Refer to the appropriate documentation for the
specified program, and respond as necessary.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.18. ACS3122 ΓòÉΓòÉΓòÉ

ACS3122-I Duplicate network resources.

Originator: SNA Communications Services (APPN)

Explanation: The Directory Services (DS) component of local SNA has detected
duplicate definitions of an APPN network resource.  An extra reply was received
from a single LOCATE request; this indicates that duplicate definitions of an
APPN resource exist in the network.

User Response: Locate the duplicated resource name in the Additional Data
section of the associated error log entry.  Contact your local support
personnel with this information, or change the configuration on the remote node
such that duplicate definitions do not exist.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.19. ACS3123 ΓòÉΓòÉΓòÉ

ACS3123-I DLC link statistics logged.

Originator: ACDI/SDLC/IBMPCNET/IBMTRNET

Explanation: Link statistics are generated by the local SNA on behalf of a DLC
to aid in problem resolution.  Often, link statistics are recorded when a
connection has ended or when DLC-internal counters roll over.  A complete
Network Management Vector Transport (network services header, a problem
determination major vector, and appropriate MS subvectors) has been logged.

o This condition is logged only locally.  Link statistics are not forwarded to
  an application program that resides in a network management focal point.

User Response: This message and the associated error log entry are
informational, and require no user action.  The link statistics are recorded in
the Additional Data section of the associated error log entry.  Refer to
Problem Determination Guide for details concerning link statistics, and the
format of the logged data.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.20. ACS3124 ΓòÉΓòÉΓòÉ

ACS3124-I MDS_MU data logged.

Originator: SNA Communications Services (APPN)

Explanation: Network management data, in the form of a Multiple Domain Support
Message Unit (MDS_MU), has been recorded.  A complete MDS_MU has been logged in
the associated error log entry.  The MDS_MU is an SNA general data stream (GDS)
variable.  The MDS_MU (X'1310') GDS variable consists of three embedded GDS
variables:

o MDS Routing Information (X'1311') GDS variable, which contains origin and
  destination identification and message flags.

o Agent_Unit_of_Work (X'1549') GDS variable, which contains requester
  identification, sequence number, and date-time information.

o Application GDS variable, such as one of the following:

   - Control Point Management Services Unit (X'1212') GDS variable.  The CP-MSU
     contains one or more MS major vectors.

   - SNA Condition Report (X'1532') GDS variable, which contains an SNA report
     code and related error information.

o In addition to logging this condition locally, SNA may have also sent this
  MDS_MU to an application program that resides at the destination node
  identified in the Routing Information GDS variable.

User Response: Often, this condition is logged when the local SNA node is
acting as a pseudo focal point; that is, the local SNA node is configured as a
network node (NN), and is forwarding alert information for served end nodes
(ENs) over an SSCP-PU session to the host.  In this case, treat this message
and the associated error log entry as informational.  Otherwise, refer to the
the MDS_MU that has been recorded in the Additional Data section of the
associated error log entry, for details.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.21. ACS3125 ΓòÉΓòÉΓòÉ

ACS3125-I Error GDS variable was received.

Originator: SNA Communications Services (APPC)

Explanation: An error-data general data stream (GDS) variable was received by a
local LU in a mapped conversation.  APPC internally issued an MC_DEALLOCATE
verb with TYPE(ABEND) to end the mapped conversation over which the error data
was received.

User Response: This is an unexpected protocol error by the partner LU. No
action is required on your part.  If this condition continues, locate the
offending partner LU through tracing or contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.22. ACS3126 ΓòÉΓòÉΓòÉ

ACS3126-I Session-level security received was not valid.

Originator: SNA Communications Services (APPN)

Explanation: A local LU received a BIND request from a partner LU that carried
security information at the session level that was not valid. This condition
indicates an Access Security Information field that is unacceptable to the
partner node.  For security reasons, no further detail is provided.

o Often, this condition occurs when the partner node is running Communications
  Manager and configures a TP definition specifying Conversation Security(YES).
  When a local TP attempts to allocate a conversation with the partner's secure
  TP, the partner's APPC Attach Manager rejects the ATTACH because it does not
  recognize a valid user ID or password.  This error condition is logged on the
  local TP node.

User Response: An ALLOCATE or SEND_CONVERSATION verb was issued by a local TP,
and contained an incorrect USER_ID or PASSWORD parameter. User IDs and
passwords are two of the few APPC configuration fields that are case sensitive.
Verify that local TP verb control blocks specify the proper user ID and
password fields.  Possible solutions may be:

o At the partner node, verify that the TP definition has the properly
  configured user ID and password.  Further, ensure that the partner LU is
  accepting the ATTACH by verifying its partner LU definition of security.

o Also, if the partner node is running Communications Manager, check the Error
  Log for a major error code of 001A.  If present, the entry provides a more
  detailed explanation of the failure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.23. ACS3127 ΓòÉΓòÉΓòÉ

ACS3127-I Conversation-level security received was not valid.

Originator: SNA Communications Services (APPC)

Explanation: A local LU received an incoming allocation request from a partner
LU that carried security information that was not valid at the conversation
level.  This condition indicates an Access Security Information field that is
unacceptable to the local node.  In other words, a local LU received an
incoming allocation request that carried incorrect conversation-level security.

o Often, this condition occurs when the local node configures a TP definition
  specifying Conversation Security(YES).  When a partner TP attempts to
  allocate a conversation with the local secure TP, the local APPC Attach
  Manager rejects the ATTACH because it does not recognize a valid user ID or
  password.  This error condition is logged in the local TP node.

User Response: This is a security error initiated by the partner LU. No action
is required on your part.  If the condition continues, locate the SNA-defined
sense data which is represented by the minor error code of the associated error
log entry; this data further isolates the cause of the error.  Refer to Problem
Determination Guide for sense data-specific corrective action.  In addition,
verify that the local TP definition has the properly configured user ID and
password.  User IDs and passwords are two of the few APPC configuration fields
that are case sensitive. Further, ensure that the local LU definition is
configured to accept the ATTACH by verifying the LU definition of security.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.24. ACS3128 ΓòÉΓòÉΓòÉ

ACS3128-I A local DLC has encountered a connection failure or has encountered
an internal request error.

Originator: SNA Communications Services (APPN)

User Response: Locate the DLC-generated return code, which is represented by
the minor error code of the associated error log entry; this return code
further isolates the cause of the error:

o Minor Error Code/Description

   - 00000101 to 00000600/An Internal failure occurred between the local SNA
     and the DLC.  Restart your computer and retry the operation you were
     attempting when the problem occurred.  If the problem persists, review the
     local adapter configuration and contact your local support personnel.

   - 00000700/Logical Link Establishment Failure:  A protocol error occurred
     during XID negotiation. The local SNA received an XID from a partner DLC
     that violated the SNA-defined syntax or sequencing.  Often, this condition
     occurs when the proper hardware adapter is not installed in the local
     node, or when the software configuration of the local adapter or logical
     link is incorrect.  Locate the SNA-defined sense data in the associated
     error log entry.  This data serves to further isolate the cause of the
     error.  Refer to Problem Determination Guide for sense data-specific
     corrective action.

   - 00000800/Connection Outage:  The DLC recognized a connection failure.
     Often, this condition indicates a failure at the partner machine because
     of restart or power outage. Also, this condition may indicate a cut or
     unplugged communication line.  In either case, alerts are logged to assist
     in problem isolation; review the FFST/2 message and error logs for related
     entries.

   - 00000A00:  The DLC detected an adapter failure.  The adapter is not
     accepting any further commands, and the network connection is closing
     down.  This error may occur when there is particularly heavy traffic on
     the network.  Check the system error log for information identifying the
     specific cause of the adapter failure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry.  (Note that the logical adapter number does not correspond
  to the X.25 slot number or the ISDN virtual adapter, but to an APPC-assigned
  number.)

   - Offset/Length/Field Description

   - 00/08/DLC Name (ASCII)

   - 08/01/Adapter Number

   - 09/01/Length of destination address

   - 10/16/Destination address

   - 26/01/CCB Command ID.  Refer to Problem Determination Guide for
     interpretation.

   - 27/01/Reserved

   - 28/04/Sense data


ΓòÉΓòÉΓòÉ 3.32.25. ACS3129 ΓòÉΓòÉΓòÉ

ACS3129-E Unable to forward non-alert NMVT data.

Originator: SNA Communications Services (APPN)

Explanation: The local SNA was unable to forward non-alert network management
data because the negotiated maximum RU size of the SSCP-PU session is too
small.

User Response: Increase the configured maximum RU size of the SSCP-PU session
session to 512 bytes.  Increasing the session RU size requires configuration
updates at both the local and partner nodes. For additional information, review
the NMVT that has been recorded in the Additional Data section of the
associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.26. ACS3130 ΓòÉΓòÉΓòÉ

ACS3130-I Non-normal UNBIND was received.

Originator: SNA Communications Services (APPN)

Explanation: An unexpected UNBIND request was received by local SNA. Usually,
this indicates a protocol error or the immediate deactivation of sessions.
Often, immediate deactivation of sessions occurs through the immediate exit of
a remote Communications Manager. The UNBIND types x'01' (NORMAL UNBIND) and
x'02' (BIND COMING UNBIND) are normal conditions and are not logged under this
error.

User Response: This is an unexpected UNBIND issued by the partner LU, and may
require no action on your part.  However, if this condition continues, contact
your local support personnel.

o For additional information, locate the UNBIND request type represented by the
  minor error code of the associated error log entry; this UNBIND type serves
  to further isolate the cause of the UNBIND.

o Minor Error Code/Description

   - 00000003/A Session Outage Notification (SON).

   - 00000006/Incorrect parameters:  Often, this condition occurs when side one
     issues a BIND with session_limit=1, conwinners=1, conlosers=1, and then
     the other side issues an identical BIND.  When there is no negotiation for
     single sessions, side one issues this UNBIND.

   - 00000007/Virtual route map.

   - 00000008/Route extension inoperative.

   - 00000009/Hierarchical reset.

   - 0000000A/SSCP gone.

   - 0000000B/Virtual route deactivated.

   - 0000000C/Unrecoverable LU failure.

   - 0000000E/Recoverable LU failure.

   - 0000000F/Cleanup:  Often, this condition occurs because of a
     DEACTIVATE_SESSION verb specifying an immediate deactivation.

   - 00000011/Gateway node cleanup:  Often, this condition occurs when a
     partner LU has issued a CNOS verb to bring down all sessions.

   - 000000FE/Protocol violation:  Often, this condition occurs when a partner
     LU recognizes an APPC conversation-level protocol error and automatically
     UNBINDs the session.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/17/Fully qualified partner LU (EBCDIC)

   - 17/08/Mode name (EBCDIC)


ΓòÉΓòÉΓòÉ 3.32.27. ACS3131 ΓòÉΓòÉΓòÉ

ACS3131-E Internal DLC error.

Originator: SNA Communications Services (APPN)

Explanation: As a result of DLC processing of a request from the local SNA, the
DLC has encountered an internal error.  The DLC has signaled this condition to
SNA, which has generated this error log on behalf of the DLC.

o Often, this condition occurs because of an OS/2 error (for example, trying to
  open a queue that is not available).  Usually, other error conditions are
  logged that provide a more precise indication of the failure.

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, capture the
associated error log information and contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/08/DLC name (ASCII)

   - 08/18/Reserved

   - 26/01/CCB Command ID.  Refer to Problem Determination Guide for
     interpretation.


ΓòÉΓòÉΓòÉ 3.32.28. ACS3132 ΓòÉΓòÉΓòÉ

ACS3132-I Attach Manager rejected an ATTACH because of time-out.

Originator: SNA Communications Services (APPC)

Explanation: This entry was made to record that an incoming ATTACH was locally
received, and subsequently rejected because the INCOMING_ALLOCATE_TIMEOUT
expired before a matching RECEIVE_ALLOCATE verb was received from a local
transaction program.

o Incoming ATTACHes carry the name of the transaction program with which they
  are requesting a conversation.  To begin the conversation, the local
  transaction program issues a RECEIVE_ALLOCATE verb that carries the identical
  name to receive the incoming ATTACH. The incoming ATTACH is queued and held
  for an amount of time waiting for a RECEIVE_ALLOCATE verb.  The amount of
  time that the allocate is held is configured in the TP definition as
  INCOMING_ALLOCATE_TIMEOUT.

User Response: This condition does not necessarily represent an error, and may
require no action on your part.  However, if this condition continues, locate
the local TP name in either the Extra Symptom String section or the Additional
Data section of the associated error log entry.  Verify:

o The local TP is issuing a RECEIVE_ALLOCATE verb using the proper TP name.

o The time-out length configured for the local TP is of sufficient duration.

o The partner TP is allocating a conversation to the local TP using the proper
  TP name.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.29. ACS3133 ΓòÉΓòÉΓòÉ

ACS3133-I Attach Manager rejected an ATTACH because of a full incoming allocate
queue.

Originator: SNA Communications Services (APPC)

Explanation: This entry records that an incoming ATTACH was locally received,
and subsequently rejected because the number of incoming ATTACHes already being
held for the same TP name was equal to the INCOMING_ALLOCATE_QUEUE_DEPTH
configured for the TP.  The incoming ATTACH could not be held without exceeding
the INCOMING_ALLOCATE_QUEUE_DEPTH.

User Response: This condition does not necessarily represent an error, and may
require no action on your part.  However, if this condition continues, locate
the TP name in either the Extra Symptom String section or the Additional Data
section of the associated error log entry.  Verify that:

o The local TP is issuing a RECEIVE_ALLOCATE verb using the proper TP name.

o The queue limit configured for the local TP is of sufficient depth to handle
  peak conditions.

o The partner TP is allocating a conversation to the local TP using the proper
  TP name.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.32.30. ACS3134 ΓòÉΓòÉΓòÉ

ACS3134-E Attach Manager rejected an ATTACH because of a failure to load and
start the TP.

Originator: SNA Communications Services (APPC)

Explanation: This entry records that an incoming ATTACH was received, and
subsequently rejected because the configured filespec for the Attach
Manager-started TP could not be locally loaded and executed.  Usually, this
condition is a result of an OS/2 function call failure.

User Response: The specific OS/2 function call that failed will be represented
by a distinct log entry.  Analysis of the OS/2 function call failure, together
with the local TP name (which has been recorded in either the Extra Symptom
String section or the Additional Data section of the associated error log
entry), should yield the precise nature of the fault.  Verify that:

o The filespec configured for the local TP is correct.

o The directory, or directory search path, configured for the local TP is
  correct.

o The executable file actually resides where configured for the local TP.

o The executable file has a .EXE suffix (if using default TP operation).

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33. ACS3135 through ACS3164 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.33.1. ACS3135 ΓòÉΓòÉΓòÉ

ACS3135-E Attach Manager rejected an ATTACH because of a security violation.

Originator: SNA Communications Services (APPC)

Explanation: An incoming ATTACH was locally rejected because it carried
conversation security that was not valid.  The conversation security is valid
only under the following conditions:

o The user ID is present and valid, and the password has already been verified
  by the partner LU.

o The user ID is present and valid, and the password is valid.

o The user ID is not present, and the TP does not require conversation
  security.

User Response: This condition could be the result of a problem at either the
local or partner node.

o Locate the TP name in either the Extra Symptom String section or the
  Additional Data section of the associated error log entry.  Verify that the
  local TP definition has the properly configured user ID and password. User
  IDs and passwords are two of the few APPC configuration fields that are case
  sensitive.

o For the partner node, verify that all ALLOCATE or SEND_CONVERSATION verbs
  issued by the partner TP contain valid USER_ID or PASSWORD parameters by
  reviewing the verb control blocks.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.2. ACS3136 ΓòÉΓòÉΓòÉ

ACS3136-I Attach Manager rejected an ATTACH because of the stopping of the
Attach Manager.

Originator: SNA Communications Services (APPC)

Explanation: This entry was made to record that an incoming ATTACH was locally
received, and subsequently rejected because the APPC Attach Manager was stopped
(either using subsystem management or by an application program issuing the
STOP_AM verb).

User Response: This message and the associated error log entry are
informational.  No action is required on your part. For additional information,
locate the local TP name that is recorded in either the Extra Symptom String
section or the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.3. ACS3137 ΓòÉΓòÉΓòÉ

ACS3137-I Attach Manager rejected an ATTACH because no RECEIVE_ALLOCATE was
issued.

Originator: SNA Communications Services (APPC)

Explanation: This entry was made to record that an incoming ATTACH was locally
received, and subsequently rejected because the the latest instance of a local
Queued-Attach Manager-started TP ended without issuing the required
RECEIVE_ALLOCATE verb.

User Response: This message and the associated error log entry are
informational.  No action is required on your part.  This condition is
considered informational because a more serious error condition has already
been logged; this condition merely identifies the rejection of a pending
ATTACH.  For additional information, locate the TP name that is recorded in
either the Extra Symptom String section or the Additional Data section of the
associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.4. ACS3138 ΓòÉΓòÉΓòÉ

ACS3138-E An unexpected return code was received from an OS/2 function call.

Originator: Communications Manager

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code can not be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry.  The last four digits of the minor error
  code provide the request code of the associated function call.  Refer to OS/2
  Technical Library for interpretation and description of the OS/2 request
  code.  Locate the return code in the Additional Data section of the
  associated error log entry.  The return code is the first four digits of this
  data.  The return code is in byte-reversed format. For example, if the first
  2 bytes are x'1234', this actually represents a return code of x'3412'.  The
  OS/2 return codes are defined under the OS/2 function calls in OS/2 Technical
  Library.

o If the request code/return code combination indicates a resource error,
  attempt to free the resource.  For resource errors that appear to be
  internal, reduce the number of active programs in the system.  Examples of
  such errors are memory, semaphores, and threads.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/02/ OS/2 return code (in byte-reversed format). Refer to OS/2 Technical
     Library for interpretation.

   - 02/08/Reserved

   - 08/02/Reserved unless the originator is APPC. For APPC loader:  OS/2
     function call reference number.

   - 10/17/Reserved unless the originator is APPC. For APPC:  ASCII name of the
     OS/2 function call (for example, DOSFREEMODULE).


ΓòÉΓòÉΓòÉ 3.33.5. ACS3139 ΓòÉΓòÉΓòÉ

ACS3139-E RECEIVE_ALLOCATE verb never issued by a TP.

Originator: SNA Communications Services (APPC)

Explanation: A local Queued-Attach Manager-started TP ended without issuing the
required RECEIVE_ALLOCATE verb.

o An ATTACH request was received carrying a TP name configured as Queued-Attach
  Manager-Started.  The APPC Attach Manager started a program in the local
  machine using the configured TP filespec. The incoming allocation request was
  held waiting for a RECEIVE_ALLOCATE verb from the program.  However, the
  program ended before issuing any RECEIVE_ALLOCATE verbs.  As a result, all
  pending ATTACHes queued to this TP have been rejected by the Attach Manager.

User Response: Locate the local TP name that is recorded in either the Extra
Symptom String section or the Additional Data section of the associated error
log entry.  Verify that:

o Logic in the local TP always issues a RECEIVE_ALLOCATE verb.

o The local TP is issuing a RECEIVE_ALLOCATE verb using the proper TP name.

o The filespec locally configured for this TP is correct.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.6. ACS3140 ΓòÉΓòÉΓòÉ

ACS3140-E An unexpected parameter or return code was encountered while locally
processing a 3270/5250 SNA Character String (SCS) (LU type 1) printer data
stream.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, record the
contents of the associated error log entry and contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.7. ACS3141 ΓòÉΓòÉΓòÉ

ACS3141-E A session was initiated with an independent partner LU on a link that
supports only sessions with dependent LUs.

Originator: SNA Communications Services (APPC)

User Response: Change the configured LU address (NAU address) of the receiving
LU to a nonzero number.  This indicates that the LU is dependent.

o If this condition continues, review the offending Path Information Unit (PIU)
  that has been recorded in the Additional Data section of the associated error
  log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.8. ACS3142 ΓòÉΓòÉΓòÉ

ACS3142-E A configuration file error was encountered by the local SNA loader.

Originator: SNA Communications Services (APPN)

User Response: Ensure that the active configuration file is properly verified.
If the problem persists, restore the configuration files from your backup copy.

o If the problem persists, contact your service representative and report the
  minor error code of the associated error log entry.  This minor error code
  provides a more precise cause of the error:

   - Minor Error Code/Values

   - 00000001/Unrecognized definition record or no data.

   - 00000004/Read error: Bad file, pointer, or no CR-LF.  This could be caused
     by a .NDF file that verified incorrectly.

   - 00000005/CFG or type missing in header.

   - 00000006/Bad ID or length in verb configuration section.

   - 0000000C/Missing "end of loader" record (Z record).

   - 00000013/Destination data too long (bad I record).

   - 00000014/Header SFLAG not zero.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/Variable/Configuration filespec (ASCIIZ)

   - Variable/4/Minor Error Code


ΓòÉΓòÉΓòÉ 3.33.9. ACS3143 ΓòÉΓòÉΓòÉ

ACS3143-E A system error occurred in the interface between SRPI and 3270
emulation.  Local SRPI has ended.

Originator: SRPI (Sender-Requester Programming Interface)

User Response: Reinstall the emulator and SRPI and retry the operation you were
attempting when the problem occurred.  If the problem persists, contact your
local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/036/Reserved

   - 36/004/CPRB return code

   - 40/002/Reserved

   - 42/002/Process ID

   - 44/002/Thread ID

   - 46/008/Session ID (ASCII)

   - 54/106/Reserved


ΓòÉΓòÉΓòÉ 3.33.10. ACS3144 ΓòÉΓòÉΓòÉ

ACS3144-E Transmission error has ended conversation.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: Either a software error or a transmission error was encountered by
the host Enhanced Connectivity Facility (ECF) program or by local SRPI.  As a
result, an acknowledge SRIU was sent to, or received from, the ECF program.  If
the error was detected by SRPI, notification of the error was sent to the host
ECF program by way of an acknowledge SRIU.  However, if the error was detected
by the host ECF program, notification of the error was sent to SRPI by way of
an acknowledge SRIU.  In either case, the conversation has ended.

User Response: Reestablish the ECF conversation by restarting the host ECF
program.  You can determine the failing conversation's session by locating the
session ID in the Additional Data section of the associated error log entry.

o Retry the operation you were attempting when the problem occurred.  If the
  problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/036/Reserved

   - 36/004/CPRB return code

   - 40/002/Reserved

   - 42/002/Process ID

   - 44/002/Thread ID

   - 46/008/Session ID (ASCII)

   - 54/106/Reserved


ΓòÉΓòÉΓòÉ 3.33.11. ACS3145 ΓòÉΓòÉΓòÉ

ACS3145-E Protocol error has ended conversation.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: Either a software error or a protocol error was encountered by the
host Enhanced Connectivity Facility (ECF) program or by the local SRPI.  As a
result, an acknowledge SRIU was sent to, or received from, the ECF program.  If
the error was detected by SRPI, notification of the error was sent to the host
ECF program by way of an acknowledge SRIU.  However, if the error was detected
by the host ECF program, notification of the error was sent to SRPI by way of
an acknowledge SRIU.  In either case, the conversation has ended.

User Response: Reestablish the ECF conversation by restarting the host ECF
program.  You can determine the failing conversation's session by locating the
session ID in the Additional Data section of the associated error log entry.

o Retry the operation you were attempting when the problem occurred.  If the
  problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/036/Reserved

   - 36/004/CPRB return code

   - 40/002/Reserved

   - 42/002/Process ID

   - 44/002/Thread ID

   - 46/008/Session ID (ASCII)

   - 54/106/Reserved


ΓòÉΓòÉΓòÉ 3.33.12. ACS3146 ΓòÉΓòÉΓòÉ

ACS3146-E Configuration file may be corrupted.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: A system error occurred while SRPI was being used; local SRPI has
ended.  The active configuration file may be damaged.

User Response: Stop all SRPI applications and all emulator sessions. Restart
all sessions and the applications.  If the problem persists, restore the
configuration file from your backup copy.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/036/Reserved

   - 36/004/CPRB return code

   - 40/002/Reserved

   - 42/002/Process ID

   - 44/002/Thread ID

   - 46/104/Reserved


ΓòÉΓòÉΓòÉ 3.33.13. ACS3147 ΓòÉΓòÉΓòÉ

ACS3147-E SRPI server alias not defined.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: An SRPI application provided a server alias that is not locally
defined; the SRPI application request failed.  SRPI was unable to utilize
default routing because this feature is also not locally configured.

User Response: Locate the application-specified alias server name in the
Additional Data section of the associated error log entry.  Select one of the
following corrective actions:

o Ensure that the application-specified alias is correct.

o Locally configure a SRPI server profile that defines a server name that
  corresponds to the application-supplied alias.

o Locally configure a SRPI server to act as a default route.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/008/Locally configured server name (ASCII)

   - 08/028/Reserved

   - 36/004/CPRB return code

   - 40/002/Reserved

   - 42/002/Process ID

   - 44/002/Thread ID

   - 46/104/Reserved


ΓòÉΓòÉΓòÉ 3.33.14. ACS3148 ΓòÉΓòÉΓòÉ

ACS3148-E Server not recognized by host.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: Local SRPI attempted communication with the host Enhanced
Connector Facility (ECF) program; the SRPI application request failed. The ECF
program was unable to locate the specified server name because this name does
not exist in the routing table of the host.

User Response: Locate the server names in the Additional Data section of the
associated error log entry.  Verify:

o The alias server name supplied by the SRPI application is correct.

o The alias service name corresponds to a locally configured actual server
  name, or corresponds to a default route.

o The locally configured server name is available at the host; contact your
  host personnel for assistance.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/08/Locally configured server name (ASCII)

   - 08/28/Reserved

   - 36/04/CPRB return code

   - 40/02/Reserved

   - 42/02/Process ID

   - 44/02/Thread ID

   - 46/08/Session ID (ASCII)

   - 54/08/Reserved

   - 62/08/Locally configured server name (EBCDIC)

   - 70/08/Local alias server name (ASCII)

   - 78/72/Reserved


ΓòÉΓòÉΓòÉ 3.33.15. ACS3149 ΓòÉΓòÉΓòÉ

ACS3149-E A process error was encountered by the host Enhanced Connectivity
Facility (ECF) program; this condition may be the result of host resource
constraints or defects.

Originator: SRPI (Sender-Requester Programming Interface)

User Response: Locate the return code and session ID in the Additional Data
section of the associated error log entry.  The return code is in byte-reversed
format.  For example, if the return code in Additional Data is x'12345678',
this actually represents a return code of x'78563412'. The return code provides
a more precise indication of the failure:

o 03041C00 -- The server on the host attempted to reply with too much data or
  too many parameters. Usually, this indicates a software problem with the host
  server program.  Contact host personnel and report the problem.

o 03041D00 -- A resource is not available at the host.  Retry the operation. If
  the problem persists, contact host personnel.

o 03041F00 -- The locally configured server is known to the host, but is not
  available.  Retry the operation.  If the problem persists, contact host
  personnel.

o 03042200 -- The server ABnormally ENDed (ABENDed) and did not send a reply to
  the local SRPI application.  Usually, this indicates a software problem with
  the host server program.  Contact host personnel and report the problem.

o 03042300 -- The server ABENDed. Usually, this indicates a software problem
  with the host server program.  Contact host personnel and report the problem.

o Others -- Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/36/Reserved

   - 36/04/CPRB return code

   - 40/02/Reserved

   - 42/02/Process ID

   - 44/02/Thread ID

   - 46/08/Session ID (ASCII)

   - 54/96/Reserved


ΓòÉΓòÉΓòÉ 3.33.16. ACS3150 ΓòÉΓòÉΓòÉ

ACS3150-E A local system error occurred while SRPI was being used.

Originator: SRPI (Sender-Requester Programming Interface)

User Response: Reinstall Communications Manager and retry the operation you
were attempting when the problem occurred.  If the problem persists, contact
your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/42/Reserved

   - 42/02/Process ID

   - 44/02/Thread ID

   - 46/08/Session ID (ASCII)

   - 54/96/Reserved


ΓòÉΓòÉΓòÉ 3.33.17. ACS3151 ΓòÉΓòÉΓòÉ

ACS3151-E System error or SRPI application error.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: A local system error or SRPI application error occurred while SRPI
was being used.

User Response: Retry the operation you were attempting when the problem
occurred.  If the problem persists, locate the information recorded in the
Additional Data section of the associated error log entry; this information
should assist in isolating the appropriate SRPI application. See the
documentation supplied with the SRPI application for additional information.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/42/Reserved

   - 42/02/Process ID

   - 44/02/Thread ID

   - 46/08/Session ID (ASCII)

   - 54/96/Reserved


ΓòÉΓòÉΓòÉ 3.33.18. ACS3152 ΓòÉΓòÉΓòÉ

ACS3152-I SNA logical link failure.

Originator: SRPI (Sender-Requester Programming Interface)

Explanation: Local SRPI has recognized that the underlying SNA logical link has
failed, thereby ending all active sessions over that link.

User Response: This message and the associated error log entry are
informational and require no user action.  This condition is informational
because more serious error conditions have already been logged by the
underlying APPN component.  Review the FFST/2 message and error logs for
related entries, and respond as indicated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/42/ Reserved

   - 42/02/ Process ID

   - 44/02/ Thread ID

   - 46/08/ Session ID (ASCII)

   - 54/96/ Reserved


ΓòÉΓòÉΓòÉ 3.33.19. ACS3153 ΓòÉΓòÉΓòÉ

ACS3153-E Program-check error PROG739.  The local 3270/5250 emulator was unable
to encipher a Request Unit (RU) correctly before sending this data to the host.

Originator: Emulator (3270/5250 emulation)

Explanation: This condition occurs when an unexpected return code is received
from the TSS encipher function call.  Usually, this is because of an error in
either the TSS profile or the command configuration data setup via the Hardware
Initialization and Key Management (HIKM) utility.  The encipher verb may not be
enabled in the command configuration data or authorization required to access
the encipher verb was set higher than the authorization level in the TSS
profile's authorization level.

User Response: Contact your local support personnel or reinitialize the adapter
using the HIKM utility.  If the problem persists, run the appropriate TSS
diagnostics on the adapter.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.20. ACS3154 ΓòÉΓòÉΓòÉ

ACS3154-E Unexpected internal RUI verb failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local internal RUI processor received an unexpected error from
an internal RUI verb.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.21. ACS3155 ΓòÉΓòÉΓòÉ

ACS3155-E Unexpected RUI_BID verb failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI_BID verb processor received an unexpected error
concerning an RU (Request Unit) from SNA format and protocol validation logic.
This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the Path Information Unit (PIU) that has
been logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/Up to 13 bytes of the PIU


ΓòÉΓòÉΓòÉ 3.33.22. ACS3156 ΓòÉΓòÉΓòÉ

ACS3156-E An SNA protocol violation was detected by a remote node.

Originator: LUA RUI (LU Application Request Unit Interface)

User Response: Contact your local support personnel or capture an LUA trace.
See Problem Determination Guide for LUA tracing instructions. Examine the trace
output looking for RUs that include SNA-defined Sense Data.  Sense Data will
provide a more specific indication of the violation; see Problem Determination
Guide for Sense Data-specific corrective action.  If no Sense Data is
available, examine the trace output looking for LUA secondary return codes that
might provide a more specific indication of the violation; see the Conventional
LU Application Programming Reference for return code interpretation.

o For additional information, locate the offending Path Information Unit (PIU)
  that has been logged in the Additional Data section of the associated error
  log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/34/Reserved

   - 34/Variable/PIU


ΓòÉΓòÉΓòÉ 3.33.23. ACS3157 ΓòÉΓòÉΓòÉ

ACS3157-W Unexpected event received.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI verb router System Network Architecture Process
(SNAP) received an APPC queue element that was not valid. This is a
Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.24. ACS3158 ΓòÉΓòÉΓòÉ

ACS3158-W Unexpected event received.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI service thread received a request to post an
IN_PROGRESS verb to the LUA application program.  The RUI service thread
handles only completed verbs.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.25. ACS3159 ΓòÉΓòÉΓòÉ

ACS3159-W Unexpected event received.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI processor read incorrect data from an internal
queue.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.26. ACS3160 ΓòÉΓòÉΓòÉ

ACS3160-I Underlying PU support abnormally ended.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local PU support of SNA ABnormally ENDed (ABENDed). This
message and the associated error log entry are informational and may require no
user action.  The reason this condition is informational is that more serious
error conditions have already been logged.

User Response: Review the FFST/2 message and error logs for related entries and
respond as indicated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.27. ACS3161 ΓòÉΓòÉΓòÉ

ACS3161-E Configuration file error.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: Either the local configuration file was damaged or an internal
programming error occurred.

User Response: Restore the configuration file from your backup copy. Retry the
operation you were attempting when the problem occurred.  If the problem
persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.28. ACS3162 ΓòÉΓòÉΓòÉ

ACS3162-E Program-check error PROG738.  The local 3270/5250 emulator was unable
to decipher a Request Unit (RU) correctly after receiving this data to the
host.

Originator: Emulator (3270/5250 emulation)

Explanation: This condition occurs when an unexpected return code is received
from the TSS decipher function call.  Usually, this is because of an error in
either the TSS profile or the command configuration data setup via the Hardware
Initialization and Key Management (HIKM) utility.  The decipher verb may not be
enabled in the command configuration data or authorization required to access
the decipher verb was set higher than the authorization level in the TSS
profile's authorization level.

User Response: Contact your local support personnel or reinitialize the adapter
using the HIKM utility.  If the problem persists, run the appropriate TSS
diagnostics on the adapter.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.33.29. ACS3163 ΓòÉΓòÉΓòÉ

ACS3163-E An unexpected return code was received from PS.

Originator: X.25 API

Explanation: The local X.25 subsystem received an unexpected return code on a
call to the Profile Services (PS) subsystem.  PS is responsible for accessing
Communications Manager configuration files (.CFG files).

User Response: Review the FFST/2 message and error logs for additional entries
that may help isolate the cause of the problem.

o Locate the PS return code in the Additional Data section of the associated
  error log entry.  Use the following list of PS return codes to guide
  corrective action.  The return codes are listed in hex.

o 01 -- .CFG file not found or invalid:  Verify the existence of the .CFG file.
  Ensure that the .CFG file attributes have not been altered.

o 02 -- .CFG file is incorrect or corrupted:  Restore the backup copy of your
  .CFG file.

o 03, 0F -- .CFG file already open:  End all other programs accessing your .CFG
  file or wait for them to complete.

o 04-0A, 0C, 0D, 10-13, 17 -- Internal error:  Contact your local support
  personnel.

o 0B -- Maximum number of open files exceeded:  Reduce the number of currently
  active programs on your workstation.

o 0E -- Incompatible .CFG file:  Use the Communications Manager configuration
  upgrade facility to update your configuration.

o 14 -- OS/2 error:  Review the FFST/2 message and error logs for additional
  information.

o 15 -- All locks on the .CFG file have been released.

o 16 -- Another process has the .CFG file locked.  End all other programs
  accessing your .CFG file or wait for them to complete.

   - Other -- Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/Module ID

   - 2/2/Location

   - 4/2/PS Return Code


ΓòÉΓòÉΓòÉ 3.33.30. ACS3164 ΓòÉΓòÉΓòÉ

ACS3164-I An incoming ATTACH request was locally received for a transaction
program (TP) defined as OPERATOR_PRELOADED, and there is no outstanding
RECEIVE_ALLOCATE verb.

Originator: SNA Communications Services (APPC)

User Response: This message and the associated error log entry are
informational and do not necessarily represent an error situation. The error
data passed with the error log entry contains the TP name. This TP name
corresponds to a name of one of the TPs that was defined in the TP definition
as 'OPERATOR_PRELOADED'.  The program must be started before an attach is
received.

o For detailed information, record the date, time and problem ID from the
  FFST/2 message log formatter.  Access the OS/2 system error log and review
  the corresponding error log entry.


ΓòÉΓòÉΓòÉ 3.34. ACS3165 through ACS3202 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.34.1. ACS3165 ΓòÉΓòÉΓòÉ

ACS3165-E An unexpected return code was received from the IBM X.25 ARTIC DLR.

Originator: Communications Manager Kernel

Explanation: The local Communications Manager kernel received an unexpected
return code from the dynamic link routine interface of the IBM X.25 Interface
Co-Processor/2 device driver.

User Response: Determine the Dynamic Link Routine (DLR) that was called by
locating the minor error code of the associated error log entry.

o The following codes are defined for each DLR:

o 0063    ICADevSecStatus

o 0064    ICADevPrimaryStatus

o 0065    ICADevReadString

o 0069    ICADevGetExtParms

o Locate the DLR return code in the Extra Symptom String section of the
  associated error log entry.  See Realtime Interface Co-Processor OS/2 Support
  User's Guide for details concerning return codes for the various DLR
  interfaces.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.2. ACS3166 ΓòÉΓòÉΓòÉ

ACS3166-E An unexpected return code was received from POSTing the IBM X.25
ARTIC adapter.

Originator: Communications Manager Kernel

Explanation: The local Communications Manager kernel received an unexpected
return code that indicated that a POST error occurred on the IBM X.25 Interface
Co-Processor/2 adapter.

User Response: Locate the slot number and return code in the Extra Symptom
String section of the associated error log entry.  See Realtime Interface
Co-Processor User's Guide or IBM X.25 Interface Co-Processor/2: Technical
Reference for details concerning the return codes.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.3. ACS3167 ΓòÉΓòÉΓòÉ

ACS3167-E An unexpected return code was received from the IBM X.25 ARTIC
adapter loader.

Originator: Communications Manager Kernel

Explanation: The local Communications Manager kernel received an unexpected
return code from the IBM X.25 Interface Co-Processor/2 adapter loader while
attempting to load X.25 code onto the adapter.

User Response: Locate the adapter number and return code in the Extra Symptom
String section of the associated error log entry.  Refer to Realtime Interface
Co-Processor User's Guide for details concerning return codes.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.4. ACS3168 ΓòÉΓòÉΓòÉ

ACS3168-E An unexpected return code was received while stopping the X.25
subsystem.

Originator: Communications Manager Kernel

Explanation: The local Communications Manager kernel received an unexpected
return code while stopping the X.25 subsystem.

User Response: Locate the return code in the Extra Symptom String section of
the associated error log entry.  Refer to the X.25 API return code
documentation for details concerning error return codes.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.5. ACS3169 ΓòÉΓòÉΓòÉ

ACS3169-E An unexpected return code was received while starting the SRPI
subsystem.

Originator: Communications Manager Kernel

Explanation: The local Communications Manager kernel received an unexpected
return code from the SRPI component during SRPI initialization.  This indicates
that the software being initialized is a prior release level or has been
damaged.

User Response: Reinstall SRPI.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.6. ACS3170 ΓòÉΓòÉΓòÉ

ACS3170-E The communications server Attach Manager rejected an ATTACH because
of a failure to load and execute the function that routes attaches to client
workstations.

Originator: SNA Communications Services (APPC)

Explanation: This entry records that an incoming ATTACH was received, and
subsequently rejected because the Attach Manager could not locally load and
execute the function that routes attaches to client workstations.  The most
likely reason for this problem is that the file DMS.DLL has been deleted or
corrupted.  This condition is an internal error resulting from an OS/2 function
call failure on DosLoadModule or DosGetProcAddr for DMS.DLL.

User Response: Check to see if DMS.DLL exists on your system.  If not or in the
event that it may have somehow been corrupted, reinstall Communications
Manager.  If the problem reoccurs the specific OS/2 function call that failed
will be represented by a distinct log entry. Analysis of the OS/2 function call
failure (which has been recorded in either the Extra Symptom String section or
the Additional Data section of the associated error log entry), should give the
OS/2 return code indicating the precise nature of the fault.  You may look up
the return code in the OS/2 programming documentation and proceed, or you may
contact IBM Service with the information from the log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.7. ACS3171 ΓòÉΓòÉΓòÉ

ACS3171-E Attach Manager rejected an ATTACH due to a failure to route the
ATTACH to the client workstation for which it was destined.

Originator: SNA Communications Services (APPC)

Explanation: This entry records that an incoming ATTACH destined for a client
workstation was received by the communications server.  The ATTACH was
subsequently rejected because of a failure to successfully route the ATTACH to
the appropriate client.

User Response: A log entry will identify the name of the TP at the client
workstation for which the ATTACH failed.  The user should:

o Ensure that the client server feature is started on the server workstation.

o Ensure that Communications Manager Client Server/2 is started on the client
  workstation and that the client server feature is started.

o Ensure that the APPC Attach Route has been properly configured to route
  ATTACHes for the correct dependent LUs to the appropriate client workstation.

o Check the message log for any additional errors that may indicate that the
  server workstation was unable to establish a NetBIOS session with the client
  workstation.

o - For the name of the TP, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.8. ACS3172 ΓòÉΓòÉΓòÉ

ACS3172-E An unexpected return code was received from LRS.

Originator: X.25

Explanation: The local X.25 subsystem received an unexpected return code on a
call to the Logical Record Services (LRS) subsystem.  LRS is responsible for
accessing Communications Manager configuration files (.CFG files).

User Response: Review the FFST/2 message log and error log for additional
entries that may help isolate the cause of the problem.

o Locate the LRS return code in the Additional Data section of the associated
  error log entry.  Use the following list of LRS return codes to guide
  corrective action.  The return codes are listed in hex.

o 02-06, 08-0B, 11, 17 -- Internal error:  Contact your local support
  personnel.

o 07 -- OS/2 error:  Review the FFST/2 message and error logs for additional
  information.

o 16 -- Another process has the .CFG file locked.  End all other programs
  accessing your .CFG file or wait for them to complete.

   - Other -- Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/Module ID

   - 2/2/Location

   - 4/2/LRS Return Code


ΓòÉΓòÉΓòÉ 3.34.9. ACS3176 ΓòÉΓòÉΓòÉ

ACS3176-E The local 3270/5250 emulator detected an unsupported keyboard type.
Emulation has ended.

Originator: Emulator (3270/5250 emulation)

User Response: Ensure that an IBM Personal Computer AT keyboard or IBM enhanced
keyboard is being used.  If a supported keyboard is being used, run the
appropriate hardware diagnostics to determine the error. Replace the keyboard
if necessary.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.10. ACS3179 ΓòÉΓòÉΓòÉ

ACS3179-E Configuration file is missing or damaged.

Originator: Emulator (3270/5250 emulation)

Explanation: The local 3270/5250 emulator encountered an error while processing
a configuration file; the configuration file is either missing or damaged.

User Response: Verify the existence of the configuration file in the \CMLIB
subdirectory.  If present, restore the configuration file from your backup
copy.  If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.11. ACS3181 ΓòÉΓòÉΓòÉ

ACS3181-E A local system error occurred while the 3270/5250 emulator was being
used.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred.  If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.12. ACS3182 ΓòÉΓòÉΓòÉ

ACS3182-E The local 3270/5250 emulator detected that the configured emulation
keyboard profile type does not match the actual keyboard for this workstation.

Originator: Emulator (3270/5250 emulation)

User Response: Reconfigure the 3270/5250 feature to specify the keyboard
profile that matches your local keyboard type.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.13. ACS3183 ΓòÉΓòÉΓòÉ

ACS3183-E The local 3270/5250 emulator recognized a failure of the underlying
Communications Manager software or a local hardware adapter.

Originator: Emulator (3270/5250 emulation)

User Response: Review the FFST/2 message and error logs for related entries.
In particular, review the logs for alert conditions and respond as indicated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.14. ACS3184 ΓòÉΓòÉΓòÉ

ACS3184-E The local 3270/5250 emulator detected a machine-check error. The
Operator Information Area (OIA) on the display shows the specific MACHxxx
number.

Originator: Emulator (3270/5250 emulation)

User Response: Review the FFST/2 message and error logs for related entries;
follow any corrective actions for related entries.  Contact your local support
personnel or refer to 3274 Control Unit Description and Programmer's Guide or
3174 Establishment Controller Status Codes for detailed MACHxxx information.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.15. ACS3185 ΓòÉΓòÉΓòÉ

ACS3185-E The local 3270/5250 emulator detected a Communication-check error.
The Operator Information Area (OIA) on the display shows the specific COMMxxx
number.

Originator: Emulator (3270/5250 emulation)

User Response: Review the FFST/2 message and error logs for related entries;
follow any corrective actions for related entries.  Contact your local support
personnel or refer to 3274 Control Unit Description and Programmer's Guide or
3174 Establishment Controller Status Codes for detailed COMMxxx information.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.16. ACS3187 ΓòÉΓòÉΓòÉ

ACS3187-E A local system error occurred while the 3270/5250 emulator was being
used.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred.  If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.17. ACS3189 ΓòÉΓòÉΓòÉ

ACS3189-E The local 3270/5250 emulator detected a problem while attempting to
create a window using OS/2 function calls.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred.  If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.18. ACS3190 ΓòÉΓòÉΓòÉ

ACS3190-E A local system error occurred while the 3270/5250 emulator was being
used.

Originator: Emulator (3270/5250 emulation)

User Response: Press the Reset key and retry the operation.  If the problem
persists and local emulation is configured for Distributed Function Terminal
(DFT) operation, press the Adapter Reset key.  If the problem persists, contact
your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.19. ACS3191 ΓòÉΓòÉΓòÉ

ACS3191-E The local 3270/5250 emulator encountered an error during the
processing of a keystroke.

Originator: Emulator (3270/5250 emulation)

User Response: Press the Reset key and retry the operation.  If the problem
persists, run the appropriate hardware diagnostics.  If the problem persists,
contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.20. ACS3192 ΓòÉΓòÉΓòÉ

ACS3192-E The local 3270/5250 emulator encountered an error during the
processing of a keystroke.

Originator: Emulator (3270/5250 emulation)

User Response: Restore the configuration file from your backup copy. If the
problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.21. ACS3193 ΓòÉΓòÉΓòÉ

ACS3193-E The host or control unit is no longer responding to the local
3270/5250 emulator.  MACH690 error is displayed on the emulation screen.

Originator: Emulator (3270/5250 emulation)

Explanation: Possible causes for this error are:

o This condition may indicate an upstream gateway, server, or controller is no
  longer responding to the emulator.

o The error may result from an inactive logical link.

User Response:

o Determine whether the upstream device is active.  If active, check and secure
  all local adapter cables.

o Use Subsystem Management to reactivate the link. If the problem persists,
  stop the Communications Manager program and restart it again.

o If the problem persists, run the appropriate diagnostics on the local
  adapter.  Verify that the local adapter cable is not damaged; replace as
  necessary.

o If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.22. ACS3194 ΓòÉΓòÉΓòÉ

ACS3194-E The local 3270/5250 emulator recognized that a hardware error
occurred on a local 3278/3279-type adapter.  MACH691 error is displayed on the
emulation screen.

Originator: Emulator (3270/5250 emulation)

User Response: Run the appropriate local hardware diagnostics.  If the problem
persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.23. ACS3195 ΓòÉΓòÉΓòÉ

ACS3195-E The remote control unit is not configured to support Distributed
Function Terminal (DFT) devices.  MACH692 error is displayed on the emulation
screen.

Originator: Emulator (3270/5250 emulation)

User Response: Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.24. ACS3196 ΓòÉΓòÉΓòÉ

ACS3196-E The local 3270/5250 emulator was communicating with a remote 3x74
control unit that uses SNA communication protocol.  The local connection was
switched to a 3x74 control unit that uses non-SNA protocol.  MACH693 error is
displayed on the emulation screen.

Originator: Emulator (3270/5250 emulation)

User Response: Either reconnect to the original SNA control unit or stop and
then restart Communications Manager.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.25. ACS3197 ΓòÉΓòÉΓòÉ

ACS3197-E Switch to SNA protocol was not valid.

Originator: Emulator (3270/5250 emulation)

Explanation: The local 3270/5250 emulator was communicating with a remote 3x74
control unit that uses non-SNA communication protocol.  The local connection
was switched to a 3x74 control unit that uses SNA protocol.

User Response: Either reconnect to the original non-SNA control unit or stop
and then restart Communications Manager.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.26. ACS3198 ΓòÉΓòÉΓòÉ

ACS3198-E The host or control unit is no longer responding to the local
3270/5250 emulator.  COMM695 error is displayed on the emulation screen.

Originator: Emulator (3270/5250 emulation)

Explanation: Usually, this condition indicates the failure of an upstream
gateway, server, or controller.

User Response: Determine whether the upstream device is active.  If active,
check and secure all local adapter cables.

o If your connection is a LAN, also check LANTRAN.LOG for any error indication.
  Make sure you specified the correct destination address and local address (if
  applicable) during customization.

o If the problem continues, contact your local support personnel.


ΓòÉΓòÉΓòÉ 3.34.27. ACS3199 ΓòÉΓòÉΓòÉ

ACS3199-E Unable to load SNA DFT software.

Originator: Emulator (3270/5250 emulation)

Explanation: A problem occurred while Communications Manager was attempting to
load the local SNA Distributed Function Terminal (DFT) software.

User Response: Reinstall Communications Manager and retry the operation you
were attempting when the problem occurred.  If the problem persists, contact
your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.28. ACS3200 ΓòÉΓòÉΓòÉ

ACS3200-E No AEDV support in control unit.

Originator: Emulator (3270/5250 emulation)

Explanation: The microcode in the remote 3x74 control unit does not contain the
extended Asynchronous Event DeVice (AEDV) support required to run the locally
configured 3270/5250 Distributed Function Terminal (DFT) emulation.

User Response: Contact your local support personnel to have the microcode level
for the 3x74 control unit upgraded.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.29. ACS3201 ΓòÉΓòÉΓòÉ

ACS3201-E COMM677 - Communication server failure.

Originator: Emulator (3270/5250 emulation)

Explanation: The communication server could not execute your request.

User Response: Note the time, date, and the COMM number in the OIA; then
contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.34.30. ACS3202 ΓòÉΓòÉΓòÉ

ACS3202-E COMM678 - Unauthorized access to communication server.

Originator: Emulator (3270/5250 emulation)

Explanation: After this 3270 session was started, the user ID or machine name
was changed to an unauthorized value, and the session ended.

o It is possible that when you started the 3270 session, you were logged onto a
  LAN by LAN requestor, then logged off and logged back on using a different
  user ID.  If the second user ID does not have access to the communication
  server, the emulation session will end.

o It is also possible that the server has dynamically updated its resources,
  and the client no longer has access to the resource it was using.

User Response: Check the LUA access definition at the communication server.
Make sure that the user ID you are using has access to the communication
server.  If your emulation session ended, you must restart it after you log on
to an authorized ID.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35. ACS3203 through ACS3292 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.35.1. ACS3203 ΓòÉΓòÉΓòÉ

ACS3203-E The local 3270/5250 emulator detected a Program-check error.  The
Operator Information Area (OIA) on the display shows the specific PROGxxx
number.

Originator: Emulator (3270/5250 emulation)

User Response: Press the Reset key and retry the operation.  If the problem
persists, contact your local support personnel or attempt to isolate the
problem by using the PROGxxx number and the corresponding error descriptions
provided as follows.

o Minor Error Code/  OIA Displayed Message/ Error Description

   - 000002BF/ X PROG703/ SC, DFC, or NC command not supported.

   - 000002C1/ X PROG705/ TH SNF field out of sequence.

   - 000002C2/ X PROG706/ Command chaining error.

   - 000002C3/ X PROG707/ Bracket protocol violation.

   - 000002C4/ X PROG708/ Data traffic not yet started.

   - 000002C5/ X PROG709/ Half-duplex protocol violation.

   - 000002C7/ X PROG711/ Session already bound (wrong LU).

   - 000002C9/ X PROG713/ Session already bound (same LU).

   - 000002CA/ X PROG714/ No LU-LU session.

   - 000002CB/ X PROG715/ LU not active.

   - 000002CC/ X PROG716/ Not enough bytes in the bind RU.

   - 000002CD/ X PROG717/ Bind support level not valid.

   - 000002CE/ X PROG718/ Bind PLU protocol not valid.

   - 000002CF/ X PROG719/ Bind SLU protocol not valid.

   - 000002D0/ X PROG720/ Bind common protocol not valid.

   - 000002D3/ X PROG723/ Bind LU type not valid.

   - 000002D4/ X PROG724/ Bind screen size not valid.

   - 000002D5/ X PROG725/ Host session requires encryption.

   - 000002D6/ X PROG726/ Negative SNA response from the host.

   - 000002D7/ X PROG727/ SNA exception request received.

   - 000002D8/ X PROG728/ Read command error.

   - 000002D9/ X PROG729/ A Read Partition SF type in retry state.

   - 000002DB/ X PROG731/ Bind inbound RU size not valid.

   - 000002DC/ X PROG732/ Bind outbound RU size not valid.

   - 000002DD/ X PROG733/ Host data was received while the session was printing
     the screen.

   - 000002DE/ X PROG734/ A structured field's WCC has the Start Print bit set,
     but it is not the last structured field in the transmission.

   - 000002DF/ X PROG735/ Mismatch between configured Session Level Encryption
     and received BIND.

   - 000002E0/ X PROG736/ Session Level Encryption key problem.

   - 000002E2/ X PROG738/ RU was not deciphered successfully.

   - 000002E3/ X PROG739/ RU was not enciphered successfully.

   - 000002E4/ X PROG740/ RU was not decompressed successfully.

   - 000002EE/ X PROG750/ A 3270 data stream command that was not valid was
     received.

   - 000002EF/ X PROG751/ SFE, MF, or SA order with character set value that is
     not valid in the range x'01'-x'FE'.

   - 000002F0/ X PROG752/ Address in a 3270 command or order not valid.

   - 000002F1/ X PROG753/ Data or command in 3270 data stream not valid.

   - 000002F2/ X PROG754/ Outbound data stream incomplete.

   - 000002F3/ X PROG755/ An unsupported character set was received.

   - 000002F4/ X PROG756/ An unsupported structure field received.

   - 000002F6/ X PROG758/ Set reply mode SF received with mode that is not
     valid.

   - 000002F7/ X PROG759/ Length in a structured field not valid.

   - 000002F8/ X PROG760/ Reserved field not set to 0.

   - 000002F9/ X PROG761/ Wrong PID value received.

   - 00000303/ X PROG771/ Incorrect command received within a structured field.

   - 0000030C/ X PROG780/ Incorrect command received.

   - 0000031D/ X PROG797/ SO is received within a DBCS field

   - 0000031E/ X PROG798/ Invalid orders exist within a DBCS field

   - 0000031F/ X PROG799/ Address is pointing the DBCS second byte.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.2. ACS3204 ΓòÉΓòÉΓòÉ

ACS3204-E COMM679 - No communication server available.

Originator: Emulator (3270/5250 emulation)

Explanation: There is no communication server or the configuration at the
server will not allow this LU name to be accessed by the user ID or machine
name used.

User Response: Ensure that a communication server is active on the LAN you are
accessing.  If so, check the configuration to make sure your LU name and the
access definitions are defined for your machine name and user name.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.3. ACS3205 ΓòÉΓòÉΓòÉ

ACS3205-E A local system error occurred in creating ASCII or EBCDIC translation
tables for emulator functions.

Originator: Emulator (3270/5250 emulation)

Explanation: Likely causes are:

o The code page definition file was not found in the CMLIB subdirectory.

o The code page specified was outside the range of 65280 to 65534.

o The code page definition file has more or less than 256 character names.

o The code page definition file has exceeded the maximum of 128 user-defined
  character names.

o The code page definition file is not in the correct format.

o The code page definition file is damaged.

User Response: Do one of the following and retry the operation. For detailed
information, use FFST/2 to access the system error log and review the
associated error log entry.  Use the date, time, and problem ID from the FFST/2
message log formatter to help locate entries in the system error log.

o Ensure that code page definition files are in the CMLIB subdirectory with a
  file name and file extension of .CPT.  The file name is the decimal code page
  number, and it cannot be more than 5 digits.

   - IBM supplied code page numbers are in the range of 1 to 65279.

   - User defined code page numbers must be in the range of 65280 to 65534.

o Ensure that code page definition files are in the correct format. Rules for
  the correct format are:

   - Exactly 256 character names must appear in a code page definition file.

   - A code page definition file must be 256 lines long, not including blank
     lines.

   - Each non-blank line contains exactly one character name. A character name
     begins with the first non-blank character of the line.  It ends with the
     first blank or the end of the line, whichever comes first. Therefore, a
     character name cannot contain imbedded blanks.

   - A character name longer than 40 characters is truncated.

o Replace some of the user-defined character names with IBM-defined character
  names so that there are not more than 128 user-defined character names.

o Restore the code page definition file from a backup copy or create a new
  file.


ΓòÉΓòÉΓòÉ 3.35.4. ACS3208 ΓòÉΓòÉΓòÉ

ACS3208-E File transfer error.

Originator: Emulator (3270/5250 emulation)

Explanation: A local error occurred during the use of file transfer over a
3270/5250 emulation session.  This error can be caused by a system failure, a
link failure, a host-program error, or a configuration problem. The target file
may be unusable.

User Response: Verify that the host link is active and that the local
configuration file is correct.  Retry the operation.  If the problem persists,
contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.5. ACS3209 ΓòÉΓòÉΓòÉ

ACS3209-E A local system error occurred while the EHLLAPI subsystem of the
3270/5250 emulator was being used.

Originator: EHLLAPI

User Response: Often, this condition occurs because an attempt is made to start
EHLLAPI when the emulator is not started.  Make sure the emulator is started
and retry the operation.

o This message can occur when an outdated level of CMWAIT.EXE is being used.
  Make sure you are using the latest level of CMWAIT.EXE, found on the
  Productivity Aids diskette.

o If the problem persists, run the EHLLAPI API trace and a data trace for the
  particular data link control (DLC) being used, and follow your local network
  operating procedures.  If this does not resolve the problem, contact your
  service representative.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/System return code

   - 2/2/Reserved

   - 4/2/Location identifier

   - 6/2/Offset in component

   - 8/2/PLIST return code


ΓòÉΓòÉΓòÉ 3.35.6. ACS3211 ΓòÉΓòÉΓòÉ

ACS3211-E A critical system error occurred while attempting to use the local
3270/5250 emulation print feature.

Originator: Emulator (3270/5250 emulation)

User Response: This error may occur if the OS/2 print spooler does not have
enough resources (hard disk space or memory) to process the print request.  It
may also occur if the printer has not been installed or set up correctly.

o If the OS/2 print spooler does not have enough resources to process the print
  job, stop the 3270/5250 printer session, free up the OS/2 resources, restart
  the 3270/5250 printer session, and retry the operation. If the problem
  persists, contact your local support personnel.

o If the problem does not appear to be related to lack of OS/2 system
  resources, verify that the printer has been installed correctly.  For more
  information on how to install and set up your printer, refer to the
  READMEDD.DAT file that resides on the printer driver diskette. If the problem
  persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.7. ACS3212 ΓòÉΓòÉΓòÉ

ACS3212-E A critical system error occurred while attempting to use the local
3270/5250 emulation print feature.

Originator: Emulator (3270/5250 emulation)

User Response: This condition may occur if there are not enough OS/2 threads
available to process the print request.  It may also occur if a print job was
requested when the printer status indicated an error.

o Under normal circumstances, the 3270/5250 emulation print feature may
  encounter this condition if several print jobs occur simultaneously.  In this
  case, the condition clears itself as print jobs are completed.

o If the print job does not appear to be proceeding normally, reduce the number
  of currently active local programs, or clear the printer error status and
  retry the operation.  If the problem persists, contact your local support
  personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.8. ACS3215 ΓòÉΓòÉΓòÉ

ACS3215-I The local 3270/5250 emulator was not able to establish an encryption
key.

Originator: Emulator (3270/5250 emulation)

Explanation: This condition occurs when an unexpected return code is received
from a TSS API call.  Usually, this is because of an error in either the TSS
profile or the command configuration data setup via the Hardware Initialization
and Key Management (HIKM) utility.

User Response: Contact your local support personnel or reinitialize the adapter
using the HIKM utility.  If the problem persists, run the appropriate TSS
diagnostics on the adapter.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.9. ACS3216 ΓòÉΓòÉΓòÉ

ACS3216-E A local system error occurred while the 3270/5250 emulator was being
used.

Originator: Emulator (3270/5250 emulation)

User Response: Restart your computer and retry the operation you were
attempting when the problem occurred.  If the problem persists, reinstall
Communications Manager and retry the operation you were attempting when the
problem occurred.  If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/System return code

   - 2/2/Reserved

   - 4/2/Location identifier

   - 6/2/Offset in component


ΓòÉΓòÉΓòÉ 3.35.10. ACS3217 ΓòÉΓòÉΓòÉ

ACS3217-E Insufficient system resources.

Originator: Emulator (3270/5250 emulation)

Explanation: There are insufficient local OS/2 resources to complete the
requested operation.  The problem could be with memory, file handles, screen
groups, semaphores, or threads.

User Response: Reduce the number of currently active local programs, and retry
the operation you were attempting when the problem occurred. If the problem
persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ System return code

   - 2/2/ Reserved

   - 4/2/ Location identifier

   - 6/2/ Offset in component


ΓòÉΓòÉΓòÉ 3.35.11. ACS3218 ΓòÉΓòÉΓòÉ

ACS3218-E Configuration file damaged.

Originator: Emulator (3270/5250 emulation)

Explanation: The local 3270/5250 emulator encountered an error while processing
a configuration file; the configuration file may have been damaged.

User Response: Verify the existence of the configuration file in the \CMLIB
subdirectory.  If present, restore the configuration file from your backup
copy.  If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ System return code

   - 2/2/ Reserved

   - 4/2/ Location identifier

   - 6/2/ Offset in component


ΓòÉΓòÉΓòÉ 3.35.12. ACS3219 ΓòÉΓòÉΓòÉ

ACS3219-E SNA logical link could not be started.

Originator: Emulator (3270/5250 emulation)

Explanation: The local 3270/5250 emulator recognized that the underlying SNA
logical link could not be started.

User Response: Review the FFST/2 message and error logs for related entries;
follow any corrective actions for related conditions.  If no related entries
exist, review the local configuration of the SNA logical links utilized by the
3270/5250 emulator.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2 System return code

   - 2/2 Reserved

   - 4/2 Location identifier

   - 6/2 Offset in component


ΓòÉΓòÉΓòÉ 3.35.13. ACS3220 ΓòÉΓòÉΓòÉ

ACS3220-E Unexpected return code from PU.

Originator: Emulator (3270/5250 emulation)

Explanation: The local 3270/5250 emulator received an unexpected return code
from the underlying PU.  Usually, this indicates the ABnormal ENDing (ABEND) of
underlying SNA support.

User Response: Review the FFST/2 message and error logs for related entries;
follow any corrective actions for related entries.

o For additional information, locate the APPC primary return code in the
  Additional Data section of the associated error log entry.  Refer to APPC
  Programming Guide and Reference for return code interpretation.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ System (APPC) return code

   - 2/2/ Reserved

   - 4/2/ Location identifier

   - 6/2/ Offset in component


ΓòÉΓòÉΓòÉ 3.35.14. ACS3221 ΓòÉΓòÉΓòÉ

ACS3221-E An unexpected return code was received from an OS/2 PM function call.

Originator: Communications Manager

Explanation: A local Communications Manager function may have failed.

User Response: Often, this condition is logged in association with other
entries.  Review the FFST/2 message and error logs for details concerning the
nature of the failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed OS/2 PM function call and the
  return code.  Refer to OS/2 Technical Library for detailed descriptions of
  the function call and return code.

o If the function call and return code can not be located in the Extra Symptom
  String section of the associated error log entry, locate the minor error code
  of the associated error log entry.  The last four digits of the minor error
  code provide the request code of the associated function call.  Refer to OS/2
  Technical Library for interpretation and description of the OS/2 PM request
  code.

o Locate the return code in the Additional Data section of the associated error
  log entry.  The return code is the first four digits of this data.  The
  return code is in byte-reversed format. For example, if the first 2 bytes are
  x'0800', this actually represents a return code of x'0008'.  The OS/2 return
  codes are defined under the OS/2 PM function calls in OS/2 Technical Library.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ OS/2 return code (in byte-reversed format).  Refer to OS/2 Technical
     Library for interpretation.

   - 2/8/ Reserved


ΓòÉΓòÉΓòÉ 3.35.15. ACS3222 ΓòÉΓòÉΓòÉ

ACS3222-I The local 3270/5250 emulator was unable to successfully generate a
random number; this number is required for encryption processing.

Originator: Emulator (3270/5250 emulation)

Explanation: This condition occurs when an unexpected return code is received
from a TSS API call.  Usually, this is because of an error in either the TSS
profile or the command configuration data setup via the Hardware Initialization
and Key Management (HIKM) utility.

User Response: Contact your local support personnel or reinitialize the adapter
using the HIKM utility.  If the problem persists, run the appropriate TSS
diagnostics on the adapter.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.16. ACS3223 ΓòÉΓòÉΓòÉ

ACS3223-E Application program ended abnormally.

Originator: X.25 API

Explanation: A local X.25 application program ended before it had properly
finished its X.25 communications.  X25APPTERM was not issued by the local X.25
application because of an internal programming error or a severe OS/2 error.

User Response: Locate the process ID of the local X.25 application and the
reason for termination code in the Additional Data section of the associated
error log entry.  The reason for termination code is provided by OS/2 when the
X.25 exit list routine of the terminating process was given control.  Refer to
OS/2 Technical Library for an explanation of possible values.

o The reason for termination, together with the problem-determination
  documentation of the failing application program should assist in isolating
  the cause of the failure.  Often, this condition indicates that the local
  X.25 application is not properly installed or the local X.25 support is not
  properly configured.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ Process ID of the X.25 application

   - 2/2/ Reason for termination.


ΓòÉΓòÉΓòÉ 3.35.17. ACS3224 ΓòÉΓòÉΓòÉ

ACS3224-E An X.25 adapter is no longer usable.

Originator: X.25 API

Explanation: A local X.25 adapter is no longer usable because it has been
dumped for problem determination purposes.

User Response: Reinitialize the X.25 adapter by exiting and restarting
Communications Manager.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ Slot number

   - 2/8/ Adapter name


ΓòÉΓòÉΓòÉ 3.35.18. ACS3225 ΓòÉΓòÉΓòÉ

ACS3225-E Lack of X.25 or OS/2 resources available at the local node.

Originator: X.25 API

Explanation: Not enough X.25 API subsystem or OS/2 resources were available to
enable a local X.25 API verb to complete successfully.

User Response: Locate the error code in the Additional Data section of the
associated error log entry.  Use this error code to guide your corrective
action:

o 000E -- A local X.25 application attempted to issue an X.25 API verb, but the
  maximum number of verbs has already been queued.  In other words, the local
  X.25 subsystem was unable to suballocate memory for an internal control
  block. Reduce the number of currently active programs on the local
  workstation; especially, reduce the number of currently active X.25
  applications.  If the problem persists, review the local X.25 applications to
  ensure that the applications do not, as a whole, enqueue an excessive number
  of verbs to local X.25 support, or to an individual X.25 adapter.

o 0010 -- A local X.25 application attempted to issue an X.25 API verb, but
  X.25 support was unable to allocate a memory segment to handle the request.
  Reduce the number of currently active programs on the local workstation;
  especially, reduce the number of currently active X.25 applications.

o 0015 -- The X.25 subsystem has reached its maximum number of supported X.25
  applications.  Reduce the number of currently active X.25 applications.

o 0019 -- The local X.25 subsystem was unable to allocate memory needed to
  process an X.25 API verb.  Reduce the number of currently active programs on
  the workstation, increase the amount of workstation RAM, or modify the local
  X.25 applications such that less memory is required.

o If the problem persists and you suspect an X.25 application error, contact
  your local support personnel or capture an X.25 trace. See Problem
  Determination Guide for X.25 tracing instructions. Examine the trace output
  looking for excessive X.25 API verb or resource use by individual X.25
  applications.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/ Module ID

   - 2/2/ Error code

   - 4/2/ Process ID of X.25 application

   - 6/1/ Verb code

   - 7/1/ Verb options


ΓòÉΓòÉΓòÉ 3.35.19. ACS3226 ΓòÉΓòÉΓòÉ

ACS3226-E The X.25 subsystem was unable to write a verb-completion queue
element to the queue of a local X.25 application program.

Originator: X.25 API

User Response: Locate the error code and process ID in the Additional Data
section of the associated error log entry.  Use the error code to guide your
corrective action:

o 0012 -- Either an X.25 application program has failed to read one or more of
  its verb-completion queues, or OS/2 has reached a workstation-wide limit on
  the number of queue elements outstanding.  Reduce the number of currently
  active programs on the local workstation.  If the problem persists, ensure
  that all local X.25 application programs are properly reading all
  verb-completion queues.

o 0013 -- The local X.25 subsystem was unable to write to a verb-completion
  queue because the queue was closed.  Either the X.25 application closed the
  verb-completion queue prematurely, or the X.25 application program failed to
  properly create the verb-completion queue.  In either case, review the queue
  handling logic in the local X.25 application program.

o If the problem persists and you suspect an X.25 application error, contact
  your local support personnel or capture an X.25 trace. See Problem
  Determination Guide for X.25 tracing instructions. Examine the trace output
  looking for excessive X.25 API verb or resource use by individual X.25
  applications.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/2/Module ID

   - 2/2/Error code

   - 4/2/Process ID of X.25 application

   - 6/1/Verb code

   - 7/1/Verb options

   - 2/ /Application


ΓòÉΓòÉΓòÉ 3.35.20. ACS3227 ΓòÉΓòÉΓòÉ

ACS3227-E Application name conflict.

Originator: X.25 API

Explanation: A local X.25 application program requested a routing-table entry
name or a Permanent Virtual Circuit (PVC) name that was already in use by
another X.25 application program.  The X.25 application program that reported
this error is incompatible with another X.25 application program.

User Response: Locate the error code in the Additional Data field of the
associated error log entry.  An error code value of x'0017' indicates that the
X.25 application failed on the X25Listen service using a routing-table name
that was already in use.  An error code value of x'001A' indicates that the
application failed on the X25PVCAlloc service with a PVC that's already in use.
The name of the routing-table entry or PVC is also provided in the Additional
Data section of the associated error log entry.

o With this information, review all local X.25 applications for usage
  restrictions concerning name conflicts.  Correct the name conflicts between
  the X.25 application programs, or coordinate the execution of the conflicting
  applications such that only one is active at a time.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

o Offset/Length/Field Description

   - 0/2/ Module ID

   - 2/2/ Error code

   - 4/2/ Process ID of X.25 application

   - 6/1/ Verb code

   - 7/1/ Verb options

   - 8/8/ Routing-table or PVC name


ΓòÉΓòÉΓòÉ 3.35.21. ACS3228 ΓòÉΓòÉΓòÉ

ACS3228-E Lack of X.25 subsystem resources available at local node.

Originator: X.25 API

Explanation: Not enough X.25 API subsystem resources were available to enable a
local X.25 API verb to complete successfully.

User Response: Locate the verb code and error code in the Additional Data
section of the associated error log entry.  Use the error code to guide your
corrective action:

o 000F -- A local X.25 application attempted to issue an X.25 API verb, but the
  maximum number of verbs has already been queued.  In other words, the local
  X.25 subsystem was unable to suballocate memory for an internal control
  block. Reduce the number of currently active programs on the local
  workstation; especially, reduce the number of currently active X.25
  applications.  If the problem persists, review the local X.25 applications to
  ensure that the applications do not, as a whole, enqueue an excessive number
  of verbs to local X.25 support, or to an individual X.25 adapter.

o 0016 -- The local X.25 application program issued an X25CALL or X25PVCALLOC
  verb requesting a connection when the configured subsystem-wide maximum were
  already in use.  Ensure that the local X.25 configuration is sufficient to
  handle the peak loads required by all local X.25 application programs; if
  necessary, restore the configuration file from your backup copy. If the local
  configuration is correct, reduce the number of currently active X.25
  application programs.  If the problem persists, ensure that the applications
  are not requesting an excessive number of connections at any one time.

o 001B -- The local X.25 application program issued an X25CALL or X25PVCALLOC
  verb requesting a connection when the configured link maximum were already in
  use.  If there are not enough virtual circuits available on a link, increase
  the number by changing the network subscription, by locally reconfiguring the
  link, or both.  If the problem persists, reduce the number of currently
  active X.25 application programs.  If the problem persists, ensure that the
  applications are not requesting an excessive number of connections at any one
  time.

o If the problem persists and you suspect an X.25 application error, contact
  your local support personnel or capture an X.25 trace. See the Problem
  Determination Guide for X.25 tracing instructions. Examine the trace output
  looking for excessive X.25 API verb or resource use by individual X.25
  applications.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/2/Module ID

   - 02/2/Error code

   - 04/2/Process ID of X.25 application

   - 06/1/Verb code

   - 07/1/Verb options

   - 08/2/Slot number

   - 12/8/Adapter name


ΓòÉΓòÉΓòÉ 3.35.22. ACS3229 ΓòÉΓòÉΓòÉ

ACS3229-E Configuration error or adapter failure.

Originator: X.25 API

Explanation: One of the following conditions occurred:

o A local X.25 adapter software, hardware, or configuration error was detected.

o A local X.25 adapter did not respond to commands.

o The adapter is unusable until the problem is corrected.

User Response: Locate the error code in the Additional Data section of the
associated error log entry.  If this error code indicates a non-configuration
error, restart your workstation.

o If the problem persists or is configuration related, review the local X.25
  configuration to ensure that it accurately represents the physical
  configuration of the system (adapters, links, modems, cables).

o If the problem persists, contact your local support personnel or refer to the
  Additional Data section of the associated error log entry.  The logged data,
  together with  Realtime Interface Co-Processor OS/2 Support User's Guide,
  should assist in isolating the error.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/2/ Module ID

   - 02/2/Error code.  Value and description:

   - x'001E' The X.25 subsystem detected an adapter software or hardware error.

   - x'001F' The X.25 adapter detected a configuration error.

   - x'0020' The X.25 adapter detected a severe device error while dumping the
     adapter.

   - x'0025' The X.25 adapter did not respond to commands.

   - x'0026' The X.25 adapter did not respond to commands while being dumped.

   - x'002C' The X.25 adapter's input queue was not empty.

   - x'002D' The X.25 adapter's output queue was not empty.

   - 04/2/Slot number

   - 06/8/Adapter name

   - 14/2/Return code from the call to the ICADevPrimaryStatus DLR to read the
     RCM primary status byte

   - 16/1/RCM primary status byte

   - 17/2/Return code from the call to the ICADdevGetSecStatus DLR to read the
     RCM secondary status buffer

   - 19/2/Length of RCM secondary status buffer data

   - 21/Variable/RCM secondary status buffer data


ΓòÉΓòÉΓòÉ 3.35.23. ACS3230 ΓòÉΓòÉΓòÉ

ACS3230-I The contents of local X.25 subsystem memory used by the X.25 API was
corrupted.  A message was inserted in the dump file at each point where damage
was detected.

Originator: X.25 API

User Response: This message and the associated error log entry are
informational.  No action is required on your part.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.24. ACS3231 ΓòÉΓòÉΓòÉ

ACS3231-E The local Common Services component of Communications Manager
returned an unexpected return code to the X.25 subsystem.  This condition
indicates an internal failure.  The X.25 API has ended.

Originator: X.25 API

User Response: Restart your workstation.  If the problem persists, restore the
configuration file from your backup copy.  If the problem persists, reinstall
Communications Manager.  If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.25. ACS3234 ΓòÉΓòÉΓòÉ

ACS3234-E The local 3270/5250 emulator recognized a server failure.
Machine-check error MACH680.

Originator: Emulator (3270/5250 emulation)

User Response: Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.26. ACS3238 ΓòÉΓòÉΓòÉ

ACS3238-E The local 3270/5250 emulator received an unexpected error code on an
LUA RUI verb.

Originator: Emulator (3270/5250 emulation)

Explanation: Often, this condition occurs because of an ABnormal ENDing (ABEND)
of communication between the client and the server.

User Response: Review the FFST/2 message and error logs for related entries;
follow any corrective actions for related entries.  For additional information,
locate the return code of the associated error log entry. The return code is
found in the first two bytes of the Additional data field.  See the
Conventional LU Application Programming Reference for return code
interpretation.


ΓòÉΓòÉΓòÉ 3.35.27. ACS3289 ΓòÉΓòÉΓòÉ

ACS3289-E Configuration file error.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: Either the local configuration file was damaged or an internal
programming error occurred.

User Response: Restore the configuration file from your backup copy. Retry the
operation you were attempting when the problem occurred.  If the problem
persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.28. ACS3290 ΓòÉΓòÉΓòÉ

ACS3290-E Configuration file error.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: Either the local configuration file was damaged or an internal
programming error occurred.

User Response: Restore the configuration file from your backup copy. Retry the
operation you were attempting when the problem occurred.  If the problem
persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry. Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.35.29. ACS3291 ΓòÉΓòÉΓòÉ

ACS3291-E Unexpected RUI_INIT verb failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI_INIT verb processor received an unexpected error
concerning an RU (Request Unit) from SNA format and protocol validation logic.
This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the PIU that has been logged in the
Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry. Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

o Offset/Length/Field Description

   - 00/12/ Reserved

   - 12/Variable/ PIU


ΓòÉΓòÉΓòÉ 3.35.30. ACS3292 ΓòÉΓòÉΓòÉ

ACS3292-E Unexpected RUI_TERM verb failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI_TERM verb processor received an unexpected error
concerning an RU (Request Unit) from SNA format and protocol validation logic.
This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the PIU that has been logged in the
Additional Data section of the associated error log entry . For detailed
information, use FFST/2 to access the system error log and review the
associated error log entry.  Use the date, time, and problem ID from the FFST/2
message log formatter to help locate entries in the system error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/Up to 13 bytes of the PIU


ΓòÉΓòÉΓòÉ 3.36. ACS3293 through ACS3322 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.36.1. ACS3293 ΓòÉΓòÉΓòÉ

ACS3293-W Unexpected RUI_READ verb failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI_READ verb processor received an unexpected error
concerning an RU (Request Unit) from SNA format and protocol validation logic.
This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the PIU that has been logged in the
Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/ Reserved

   - 12/Variable/ Up to 13 bytes of the PIU


ΓòÉΓòÉΓòÉ 3.36.2. ACS3294 ΓòÉΓòÉΓòÉ

ACS3294-E Unexpected RUI_WRITE verb failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI_WRITE verb processor received an unexpected error
concerning an RU (Request Unit) from SNA format and protocol validation logic.
This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the PIU that has been logged in the
Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/Up to 13 bytes of the PIU


ΓòÉΓòÉΓòÉ 3.36.3. ACS3295 ΓòÉΓòÉΓòÉ

ACS3295-E Unexpected ACTLU was received.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI processor received an ACTivate Logical Unit (ACTLU)
request from a remote node without first receiving an expected internal
message.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.4. ACS3296 ΓòÉΓòÉΓòÉ

ACS3296-E Unexpected IPR received.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI processor received an unexpected error concerning an
Isolated Pacing Response (IPR) from SNA format and protocol validation logic.
This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the Path Information Unit (PIU) that has
been logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/PIU


ΓòÉΓòÉΓòÉ 3.36.5. ACS3297 ΓòÉΓòÉΓòÉ

ACS3297-E Unexpected request or response failure.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI processor received an unexpected error concerning a
request or response from SNA format and protocol validation logic.  This is a
Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the Path Information Unit (PIU) that has
been logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/Up to 13 bytes of the PIU


ΓòÉΓòÉΓòÉ 3.36.6. ACS3298 ΓòÉΓòÉΓòÉ

ACS3298-E Negative response to NOTIFY was received.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI processor received a negative response to a NOTIFY
command that was sent to a remote node.  The requested SSCP-LU session was not
established.

User Response: Retry the operation.  If the problem persists, contact your
local support personnel or capture an LUA trace.  Refer to Problem
Determination Guide for LUA tracing instructions.  Examine the trace output
looking for RUs that include SNA-defined sense data.  Sense data provides a
more specific indication of the violation; refer to Problem Determination Guide
for sense data-specific corrective action.  For additional information, locate
the Path Information Unit (PIU) that has been logged in the Additional Data
section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/PIU


ΓòÉΓòÉΓòÉ 3.36.7. ACS3299 ΓòÉΓòÉΓòÉ

ACS3299-E LU-LU request was received was not valid.

Originator: LUA RUI (LU Application Request Unit Interface)

Explanation: The local RUI processor received an LU-LU request from the remote
node, but the corresponding LU-LU session has not been established.

User Response: Retry the operation.  If the problem persists, contact your
local support personnel or capture an LUA trace.  Refer to Problem
Determination Guide for LUA tracing instructions.  Examine the trace output
looking for RUs that include SNA-defined sense data.  Sense data will provide a
more specific indication of the violation; refer to Problem Determination Guide
for sense data-specific corrective action.  For additional information, locate
the Path Information Unit (PIU) that has been logged in the Additional Data
section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/Variable/Up to 13 bytes of the PIU


ΓòÉΓòÉΓòÉ 3.36.8. ACS3300 ΓòÉΓòÉΓòÉ

ACS3300-E Unexpected internal message was received.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected message from the
host that could not be handled.  Either a local internal processing error or a
host processing error occurred.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb


ΓòÉΓòÉΓòÉ 3.36.9. ACS3301 ΓòÉΓòÉΓòÉ

ACS3301-E Unexpected SLI_OPEN message was received.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI_OPEN processor received an unexpected message from
the host that could not be handled.  Either a local internal processing error
or a host processing error occurred.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb


ΓòÉΓòÉΓòÉ 3.36.10. ACS3302 ΓòÉΓòÉΓòÉ

ACS3302-E Unexpected SLI_CLOSE message was received.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI_CLOSE processor received an unexpected message from
the host that could not be handled.  Either a local internal processing error
or a host processing error occurred.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb

   - 76/20/Reserved


ΓòÉΓòÉΓòÉ 3.36.11. ACS3303 ΓòÉΓòÉΓòÉ

ACS3303-E Unexpected message from RUI was received.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected message from the
local RUI processor that could not be handled.  This is a Communications
Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb


ΓòÉΓòÉΓòÉ 3.36.12. ACS3304 ΓòÉΓòÉΓòÉ

ACS3304-E Unexpected RUI_INIT verb failure.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected error concerning an
RUI_INIT verb.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb


ΓòÉΓòÉΓòÉ 3.36.13. ACS3305 ΓòÉΓòÉΓòÉ

ACS3305-E Unexpected RUI_TERM verb failure.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected error concerning an
RUI_TERM verb.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb


ΓòÉΓòÉΓòÉ 3.36.14. ACS3306 ΓòÉΓòÉΓòÉ

ACS3306-E Unexpected RUI_READ verb failure.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected error concerning an
RUI_READ verb.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb

   - 76/20/Reserved


ΓòÉΓòÉΓòÉ 3.36.15. ACS3307 ΓòÉΓòÉΓòÉ

ACS3307-E Unexpected RUI_WRITE verb failure.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected error concerning an
RUI_WRITE verb.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb

   - 76/20/ Reserved


ΓòÉΓòÉΓòÉ 3.36.16. ACS3308 ΓòÉΓòÉΓòÉ

ACS3308-E Unexpected RUI_BID verb failure.

Originator: LUA SLI (LU Application Session Level Interface)

Explanation: The local SLI processor received an unexpected error concerning an
RUI_BID verb.  This is a Communications Manager internal error.

User Response: If the problem persists, contact your local support personnel.
For additional information, locate the offending verb record that has been
logged in the Additional Data section of the associated error log entry.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/12/Reserved

   - 12/64/Verb


ΓòÉΓòÉΓòÉ 3.36.17. ACS3309 ΓòÉΓòÉΓòÉ

ACS3309-E The local Common Services component of Communications Manager
returned an unexpected return code to LUA RUI; this condition indicates an
internal failure related to tracing.

Originator: LUA RUI (LU Application Request Unit Interface)

User Response: Restart your workstation.  If the problem persists, reinstall
Communications Manager.  If the problem persists, contact your local support
personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.18. ACS3310 ΓòÉΓòÉΓòÉ

ACS3310-E NMVT Error.

Originator: SNAGATE (SNA gateway)

Explanation: An improperly formatted NMVT was received by the local gateway
node from a remote workstation.  Often, this condition occurs because of an
incorrect length field in a major vector, subvector, or subfield of the
received NMVT.  The gateway node will attempt to forward the erroneous NMVT.

User Response: Usually, the erroneous NMVT is logged as Additional Data in an
associated error log entry (major error code:  0017).  Further, if the NMVT is
an alert, access the FFST/2 dump formatter, open the alert log file
(EPWALERT.DMP), and review the formatted alert.  If available, this data often
helps to isolate the offending workstation, and the workstation application
issuing the incorrect NMVT.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.19. ACS3311 ΓòÉΓòÉΓòÉ

ACS3311-E GDDM/OS2LINK Error.

Originator: Host Graphics

Explanation: An internal software error occurred within the local link software
for the Graphical Data Display Manager (GDDM) application and its utility
programs.

User Response: Review the FFST/2 message and error logs for related entries,
and follow any corrective actions for related conditions. If no related
conditions have been logged, stop Communications Manager and then restart it.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry. Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.20. ACS3312 ΓòÉΓòÉΓòÉ

ACS3312-E Directory database is not valid.

Originator: SNA Communications Services (APPN)

Explanation: Local SNA was unable to read or write to the APPN directory
database file.

User Response: Locate the database filespec contained in the Additional Data
section of the associated error log entry.  Stop Communications Manager and
delete this file from the disk.  Restart Communications Manager.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.21. ACS3313 ΓòÉΓòÉΓòÉ

ACS3313-E Local node is congested.

Originator: SNA Communications Services (APPN)

Explanation: The local SNA node is congested because more than 63% of RAM is in
use.  This condition can be generated by both End Nodes (ENs) and Network Nodes
(NNs).  If no action is taken, Communications Manager will attempt to decrease
memory usage and the local node may experience performance degradation.

User Response: The following are possible congestion situations and recommended
actions:

o If this condition is logged occasionally and mainly during periods of high
  activity, you can treat this message and the associated error log entry as
  informational; no action is required on your part.

o If this condition occurs during periods of expected low activity, increase
  the RAM for the local workstation.

o If the local node is configured as a Network Node (NN) and this error
  condition is frequent, you may want to reroute traffic around this node.
  Refer to the Network Administration and Subsystem Management Guide for a
  discussion of this procedure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.22. ACS3314 ΓòÉΓòÉΓòÉ

ACS3314-E Common Programming Interface for Communications (CPI-C) received a
pointer that is not valid.  The pointer contains either a null or inaccessible
address.

Originator: Common Programming Interface for Communications

User Response: Correct the application program by supplying a valid address to
the memory required for each parameter in the CPI-C call.

o Use FFST/2 to access the system error log and review the associated error log
  entry.  The date, time, and problem ID of this message log entry will help to
  locate the entry in the system error log.

Major error code Type 0052 is the error that is logged when the application
returns CM_PRODUCT_SPECIFIC_ERROR (return code = X'14'). Refer to Common
Programming Interface Communications Reference for details about this return
code.

o The Extra Symptom String section identifies the name of the CPI-C function
  that failed and the return code.

o The position of the incorrect variable is logged in the first byte of the
  Additional Data section.


ΓòÉΓòÉΓòÉ 3.36.23. ACS3315 ΓòÉΓòÉΓòÉ

ACS3315-E Common Programming Interface for Communications (CPI-C)

 received an unexpected return code from advanced program-to-program
 communications (APPC).

Originator: Common Programming Interface for Communications

User Response: Do the following:

o Use FFST/2 to access the system error log and review the associated error log
  entry.  The date, time, and problem ID of this message log entry will help to
  locate the entry in the system error log.

Major error code 0052 is the error that is logged when the application returns
CM_PRODUCT_SPECIFIC_ERROR (return code = X'14'). Refer to Common Programming
Interface Communications Reference for details about this return code.

o The Extra Symptom String section identifies the CPI-C function called by the
  application, the APPC verb that failed, and the APPC return codes. The
  primary return code is shown as "RC/", and the secondary return code is shown
  as "RC2/".


ΓòÉΓòÉΓòÉ 3.36.24. ACS3316 ΓòÉΓòÉΓòÉ

ACS3316-E The Common Programming Interface for Communications (CPI-C)
application program issued an Accept_Conversation (CMACCP) call, but a
transaction program (TP) with an identical tp_id was started by a previous call
to Initialize_Conversation (CMINIT or XCINCT).

Originator: Common Programming Interface for Communications

User Response: Correct the application program logic so that it does not issue
the CMACCP call after a call to CMINIT or XCINCT.

o Use FFST/2 to access the system error log and review the associated error log
  entry.  The date, time, and problem ID of this message log entry will help to
  locate the entry in the system error log.

Major error code 0052 is the error that is logged when the application returns
CM_PRODUCT_SPECIFIC_ERROR (return code = X'14'). Refer to Common Programming
Interface Communications Reference for details about this return code.


ΓòÉΓòÉΓòÉ 3.36.25. ACS3317 ΓòÉΓòÉΓòÉ

ACS3317-E The Common Programming Interface for Communications (CPI-C)
application issued a call that requires Advanced Program-to-Program
Communications (APPC), but APPC is not available.

Originator: Common Programming Interface for Communications

User Response: Ensure that APPC is configured and active. If necessary, use
Subsystem Management to start SNA Services.

o Use FFST/2 to access the system error log and review the associated error log
  entry.  The date, time, and problem ID of this message log entry will help to
  locate the entry in the system error log.

Major error code 0052 is the error that is logged when the application returns
CM_PRODUCT_SPECIFIC_ERROR (return code = X'14'). Refer to Common Programming
Interface Communications Reference for details about this return code.


ΓòÉΓòÉΓòÉ 3.36.26. ACS3318 ΓòÉΓòÉΓòÉ

ACS3318-E The application requested more memory than is available to Common
Programming Interface for Communications (CPI-C).  The maximum amount of memory
that can be used by CPI-C is 655,360 bytes.

Originator: Common Programming Interface for Communications

Explanation: This condition can occur because: 1. There are multiple calls to
Send_Data (CMSEND) or Receive (CMRCV). 2. Too many conversations have been
started by Initialize_Conversation (CMINIT or XCINCT). 3. Too many transaction
programs (TPs) have been started by Start_TP (XCSTP) or Accept_Conversation
(CMACCP) calls.

User Response: Modify the application program to do the following:

o To correct the first condition, use OS/2 shared storage for buffers to avoid
  having the CPI-C component allocate buffers.

o To correct the second condition, deallocate inactive conversations (CMDEAL)
  when conversations are finished.

o To correct the third condition, end any completed TPs using End_TP (XCENDT)
  when transaction processing is complete.

Use FFST/2 to access the system error log and review the associated error log
entry.  The date, time, and problem ID of this message log entry will help to
locate the entry in the system error log. Major error code 0052 is the error
that is logged when the application returns CM_PRODUCT_SPECIFIC_ERROR (return
code = X'14'). Refer to Common Programming Interface Communications Reference
for details about this return code.


ΓòÉΓòÉΓòÉ 3.36.27. ACS3319 ΓòÉΓòÉΓòÉ

ACS3319-E An operator-started transaction program (TP) issued a Common
Programming Interface for Communications (CPI-C) call to Accept_Conversation
(CMACCP).  The OS/2 environment variable APPCTPN is not set.

Originator: Common Programming Interface for Communications

User Response: Correct the application program by setting the OS/2 environment
variable APPCTPN to match the name of the TP on the incoming Attach.

o Use FFST/2 to access the system error log and review the associated error log
  entry.  The date, time, and problem ID of this message log entry will help to
  locate the entry in the system error log.

Major error code 0052 is the error that is logged when the application returns
CM_PRODUCT_SPECIFIC_ERROR (return code = X'14'). Refer to Common Programming
Interface Communications Reference for details about this return code.


ΓòÉΓòÉΓòÉ 3.36.28. ACS3320 ΓòÉΓòÉΓòÉ

ACS3320-E Network management database is not valid.

Originator: SNA Communications Services (APPN)

Explanation: Local SNA was unable to process the network management database
file.  This file contains a record of remote focal points (FPs); remote FPs
serve as centralized analysis applications for various categories of network
management data (for example, alerts).

o Usually, this condition indicates that the APPCMS.DAT file was corrupted.
  Entries from the database that have been successfully processed have been
  preserved.  All unprocessed entries have been discarded; because of the
  nature of this condition, erroneous entries can not be identified further.

User Response: Stop Communications Manager and then restart it.  This ensures
that all DEFINE_REMOTE_FP verbs are processed.  For categories where no
DEFINE_REMOTE_FP verb exists, the command that was used at the remote focal
point to acquire the local node must be reissued, or a DEFINE_REMOTE_FP verb
must be added at the local node for each category.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.29. ACS3321 ΓòÉΓòÉΓòÉ

ACS3321-E Unable to open the network management database.

Originator: SNA Communications Services (APPN)

Explanation: Local SNA was unable to open the network management database file.
This file contains a record of remote focal points (FPs); remote FPs serve as
centralized analysis applications for various categories of network management
data (for example, alerts).

o Usually, this condition indicates that the APPCMS.DAT file has been
  erroneously deleted, moved, or accessed by another process, or had its
  attributes altered.

User Response: Stop Communications Manager and then restart it.  This will
ensure that all DEFINE_REMOTE_FP verbs are processed.  For categories where no
DEFINE_REMOTE_FP verb exists, the command that was used at the remote focal
point to acquire the local node must be reissued, or a DEFINE_REMOTE_FP verb
must be added at the local node for each category.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.36.30. ACS3322 ΓòÉΓòÉΓòÉ

ACS3322-E Unable to write to the network management database.

Originator: SNA Communications Services (APPN)

Explanation: Local SNA was unable to write to the network management database
file.  This file contains a record of remote focal points (FPs); remote FPs
serve as centralized analysis applications for various categories of network
management data (for example, alerts).

o Usually, this condition indicates that the APPCMS.DAT file has been
  irreversibly corrupted.

User Response: Stop Communications Manager and then restart it.  This will
ensure that all DEFINE_REMOTE_FP verbs are processed.  For categories where no
DEFINE_REMOTE_FP verb exists, the command that was used at the remote focal
point to acquire the local node must be reissued, or a DEFINE_REMOTE_FP verb
must be added at the local node for each category.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37. ACS3323 through ACS3363 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 3.37.1. ACS3323 ΓòÉΓòÉΓòÉ

ACS3323-I Revoke MS FP received.

Originator: SNA Communications Services (APPN)

Explanation: The local SNA node received a "revoke MS focal point" message from
a remote MS Entry Point (EP).  The local node received an MS Capabilities FP
Authorization message from an MS entry point, revoking the local MS Focal Point
(FP) for a given MS category.  This occurs when another MS focal point has
acquired the EP node, when the EP node explicitly revokes the local FP, or when
the remote node is also a FP node and has detected a FP loop.  In the latter
case, additional log entries are also generated.

User Response: This message and the associated error log entry are
informational and require no action on your part.  If the revoke is not
desired, that is, you wish for the local node to continue to be the focal point
for the remote node for this category, reissue the command used to originally
acquire the EP.  However, if the revoke reason indicates that the revoke has
been issued to break a focal point loop, the network should be analyzed for
this category to ensure correct nesting of FPs to prevent another loop
condition.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/01/Revoke reason.  Refer to SNA Formats for interpretation.

   - 01/08/MS Category.  Refer to SNA Formats for interpretation.

   - 09/17/Fully qualified CP name of revoking node.

   - 26/17/Fully qualified CP name of new FP node. (If there is no new FP, this
     field is all blanks.)

   - 43/08/MS application name of new FP. (If there is no new FP, this field is
     all blanks.)


ΓòÉΓòÉΓòÉ 3.37.2. ACS3324 ΓòÉΓòÉΓòÉ

ACS3324-E Acquire MS FP request was rejected.

Originator: SNA Communications Services (APPN)

Explanation: The local SNA node received a "reject MS focal point" reply from a
remote node.  The local node sent the remote node an MS Capabilities EP
Authorization request, to acquire a Focal Point (FP) for a given MS category,
and the local node received an MS Capabilities EP Authorization reply rejecting
the request.  This occurs when the remote node does not support the FP
application or the MS category.

User Response: Review the local definition of the FP CP name, and the active
configuration for this category; the remote node may either be a primary FP
defined at the local node, or a backup FP defined at either the local node or
the primary FP.  If all appears correct, locate the remote CP name in the
Additional Data section of the associated error log entry. The focal point
application may need to be started on the remote node.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/01/ Revoke reason.  Refer to SNA Formats for interpretation.

   - 1/08/ MS Category.  Refer to SNA Formats for interpretation.

   - 9/17/ Fully qualified CP name of rejecting node.


ΓòÉΓòÉΓòÉ 3.37.3. ACS3325 ΓòÉΓòÉΓòÉ

ACS3325-E MS FP loop detected.

Originator: SNA Communications Services (APPN)

Explanation: The local SNA node detected a Focal Point (FP) loop.  This
condition occurs when two or more FP nodes exist in the same network, and a
loop of Spheres Of Control (SOCs) exists for a given MS category.  A network
that includes multiple FP nodes requires a hierarchical relationship of SOCs,
such that the highest FP node includes one or more lower (first-level-nested)
FP nodes in their SOCs, and so forth.  An FP loop exists when an intended lower
FP node (erroneously) includes a higher-level FP node in its SOC.

User Response: The local SNA node has automatically broken the FP loop by
revoking its focal point.  An incorrect definition may cause the condition to
recur.  Review the local definition of the FP CP name; ensure that no
higher-level FP node is defined as an intended lower-level FP.  The FP
definition may be either a primary or backup definition.  If all appears
correct, locate the remote CP name in the Additional Data section of the
associated error log entry.  Perform the same configuration review on the
remote node.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 0/07/MS Category.  Refer to SNA Formats for interpretation.

   - 8/17/Fully qualified CP name of revoked FP.


ΓòÉΓòÉΓòÉ 3.37.4. ACS3326 ΓòÉΓòÉΓòÉ

ACS3326-I GDS variable received was not valid.

Originator: SNA Communications Services (APPC)

Explanation: The local node received a General Data Stream (GDS) variable that
was not valid.  This error occurred following a host request to deactivate a
session(s) to a local LU.  This error can occur because of either an incorrect
GDS ID, an incorrect GDS variable length, or an unsupported Communications
Manager function.

User Response: This is message and the associated error log entry are
informational, and require no user action.  This condition is informational
because the local SNA ignores this protocol error from the remote LU; no error
sense data information is returned to the remote node.  If the problem
persists, contact support personnel at the remote node to determine the nature
of this failure.

o For additional information, perform one or more of the following steps:

   - Locate the erroneous GDS variable in the Additional Data section of the
     associated error log entry.

   - In order to locate the remote LU, use subsystem management to display the
     currently active LUs and sessions.

   - Deactivate all users from the remote LU which issued the erroneous GDS
     variable.

   - For detailed information, use FFST/2 to access the system error log and
     review the associated error log entry.  Use the date, time, and problem ID
     from the FFST/2 message log formatter to help locate entries in the system
     error log.


ΓòÉΓòÉΓòÉ 3.37.5. ACS3327 ΓòÉΓòÉΓòÉ

ACS3327-E Conversation-level security downgraded.

Originator: SNA Communications Services (APPC)

Explanation: A password defined through local User Profile Management (UPM) is
incorrect.  Local SNA has downgraded conversation-level security to NONE.

User Response: Locate the user ID in the Additional Data section of the
associated error log entry.  The password associated with this particular user
ID must be changed through UPM so that the password length does not exceed the
10 character maximum.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o The following data is logged in the Additional Data section of the associated
  error log entry:

   - Offset/Length/Field Description

   - 00/10/ User ID

   - 10/01/ Reserved

   - 11/17/ Remote LU name


ΓòÉΓòÉΓòÉ 3.37.6. ACS3328 ΓòÉΓòÉΓòÉ

ACS3328-E An unexpected return code was received from WMS.

Originator: Communications Manager

Explanation: A local Communications Manager function may have failed.

User Response: WMS is a graphics subsystem associated with OS/2 Presentation
Manager.  Often, this condition is logged in association with other entries;
review the FFST/2 message log and the system error log for details concerning
the nature of any failed Communications Manager function.

o Locate the Extra Symptom String section of the associated error log entry.
  Review this section for the name of the failed WMS function call and the
  return code; refer to the WMS Technical Library for detailed descriptions of
  the function call and return code.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.7. ACS3329 ΓòÉΓòÉΓòÉ

ACS3329-E An unexpected return code was received from PS.

Originator: Profile Services

Explanation: The local Profile Services (PS) subsystem encountered an error
processing a configuration file.  PS is responsible for accessing
Communications Manager configuration files (.CFG files).

User Response: Locate the PS return code in either the Extra Symptom String
section or the minor error code of the associated error log entry.  You can
find the associated error log entry in the FFST/2 System Error Log.  Use the
following list of PS return codes to guide corrective action.  The return codes
are listed in hex.

o 01 -- .CFG file not found or invalid:  Verify the existence of the .CFG file.
  Ensure that the .CFG file attributes have not been altered.

o 02 -- .CFG file is incorrect or corrupted:  Restore the backup copy of your
  .CFG file if one exists, otherwise create a new .CFG file.

o 03, 0F -- .CFG file already open:  End all other programs accessing your .CFG
  file or wait for them to complete.

o 04-0A, 0C, 0D, 10-13, 17 -- Internal errors:  Contact your local support
  personnel.

o 0B -- Maximum number of open files exceeded:  Reduce the number of currently
  active programs on your workstation.

o 0E -- Incompatible .CFG file:  Use the Communications Manager configuration
  upgrade facility to update your configuration.

o 14 -- OS/2 error:  Review the FFST/2 message and error logs for additional
  information.

o 15 -- All locks on the .CFG file have been released.

o 16 -- Another process has the .CFG file locked.  End all other programs
  accessing your .CFG file or wait for them to complete.

o OTHER -- Contact your local support personnel.

o For detailed information, use FFST/2 to access the System Error Log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the System
  Error Log.


ΓòÉΓòÉΓòÉ 3.37.8. ACS3330 ΓòÉΓòÉΓòÉ

ACS3330-E An unexpected return code was received from LRS.

Originator: Logical Record Services

Explanation: The local Logical Record Services (LRS) subsystem encountered an
error processing a configuration file.  LRS is responsible for accessing
Communications Manager configuration files (.CFG files).

User Response: Locate the LRS return code in either the Extra Symptom String
section or the minor error code of the associated error log entry.  Use the
following list of LRS return codes to guide corrective action.  The return
codes are listed in hex.

o 02-06, 08-0B, 11, 17 -- Internal error:  Contact your local support
  personnel.

o 07 -- OS/2 error:  Review the FFST/2 message and error logs for additional
  information.

o 16 -- Another process has the .CFG file locked.  End all other programs
  accessing your .CFG file or wait for them to complete.

o OTHER -- Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.9. ACS3331 ΓòÉΓòÉΓòÉ

ACS3331-E An unexpected return code was received from a called dialog system.

Originator: Configuration Services

Explanation: The local Configuration Dialog (CD) system encountered a failure
in one of its called subsystems.

User Response: Locate the failed subsystem's code represented by the minor
error code of the associated error log entry.

o Use the following list of subsystem codes to guide corrective action:

   - 01     3270 Configuration

   - 02     5250 Configuration

   - 03     SRPI

   - 04     ACDI APIs

   - 05     ACDI Configuration

   - 06     ACDI Redirection

   - 07     ARTIC adapter w/out X.25

   - 08     LAN Protocols using ISDN

   - 0E     Communications LUA Access

   - 0F     Communications LUA Pools

   - 10     Connections

   - 11     Local Node Characteristics

   - 12     SNA Features

   - 13     Connection Manager

   - 14     Port Connection Manager

   - 15     Protocol Driver

   - 16     ETHERNET Network DLC

   - 17     PC Network DLC

   - 18     Token-Ring DLC

   - 1A     SDLC DLC

   - 1B     SDLC DLC using ISDN

   - 1C     Twinaxial DLC

   - 1D     X.25 DLC

   - 1E     Gateway Hosts

   - 1F     Gateway Workstations

   - 20     Implicit GW Workstations

   - 21     LUA APIs

   - 22     X.25 Directory Entry

   - 23     X.25 Links

   - 24     X.25 Links

   - 25     X.25 Routing Tables

o Verify that the configuration is accurate in the failed subcomponent. Review
  the FFST/2 message and error logs for other entries that might indicate the
  specific reason for failure.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.10. ACS3333 ΓòÉΓòÉΓòÉ

ACS3333-E Local SNA ABnormally ENDed (ABEND).

Originator: SNA Communications Services (APPN)

User Response: Locate the minor error code of the associated error log entry.
Use the following list of minor error codes to guide your corrective action:

o Minor Error Values/Code

o 1, 7/ No available memory: If this condition occurred while Communications
  Manager was being initialized, possibly not enough disk space is available
  for OS/2 swapping.  Review the FFST/2 message and error logs for entries
  relating to OS/2 function call failures.  Ensure that memory swapping is
  active; review the setting of the MEMMAN= command in your CONFIG.SYS file.
  Also, ensure that sufficient disk space is available on the subdirectory
  indicated by the SWAPPATH= command in your CONFIG.SYS file.  If this
  condition occurred while Communications Manager was already fully
  initialized, this usually indicates that local SNA has exceeded its internal
  memory limit; internal memory is consumed with each configured and active SNA
  resource (for example, TPs, LUs, links, sessions, conversations).  Reduce the
  number of configured resources or reduce the number of active Communications
  Manager applications on the local node.

o 2-6/ Incorrect configuration file: The Communications Manager configuration
  file has been damaged or is otherwise incorrect.  Restore the configuration
  file using your backup copy.

o Any value/ Internal error:  This condition can occur for either of the
  following reasons:

   - Local SNA has exhausted its internal supply of resources.  For example, a
     program is in a loop handling incoming ATTACHes.  As part of the loop, it
     issues a RECEIVE_ALLOCATE verb to get the next ATTACH.  This loop should
     have a TP_ENDED verb at its bottom; otherwise, each new RECEIVE_ALLOCATE
     verb consumes memory for a new TP, which is never freed.  If this loop
     runs long enough, it will consume all available internal memory.

   - An application program can cause APPC to ABEND by issuing a DosKillProcess
     or DosExit call on a given thread while APPC is executing in a critical
     section on another thread; APPC is running on a TP's thread when executing
     an APPC verb.  Similarly, a user can ABEND APPC by pressing Ctrl+Break on
     an application program's thread while APPC is executing a critical
     section.  Finally, APPC can ABEND if a general protection fault (Trap D)
     occurs on a thread while APPC is executing a critical section.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.11. ACS3334 ΓòÉΓòÉΓòÉ

ACS3334-E An unexpected return code was received from CU.

Originator: ISDN Connection Manager

Explanation: The local Configuration Utilities (CU) subsystem encountered an
error while processing a configuration file.  CU is responsible for accessing
Communications Manager configuration files.

User Response: Locate the CU return code in either the Extra Symptom String
section or the minor error code of the associated error log entry.  Use the
following list of CU return codes to guide corrective action:

o 64 -- Keylock is on.

o 10, 23, 33, 43, 56, 62, 63, 74, 80-83 -- .CFG file incorrect or not found:
  Verify the existence of the .CFG file in the \CMLIB subdirectory.  If
  present, restore the .CFG file using your backup copy.

o 20, 30, 40, 46, 50, 53, 60 -- .NDF file incorrect or not found:  Verify the
  existence of the .NDF file in the \CMLIB subdirectory.  If present, restore
  the .NDF file using your backup copy.

o 21, 31, 41, 61, 75, 76 -- .CTL file incorrect or not found:  Re-verify your
  configuration.

o 22, 32, 42, 45, 51, 54, 67 -- .CF2 file incorrect or not found:  Re-verify
  you configuration.

o 24, 34, 44, 52, 55 -- .SEC file incorrect or not found:  Re-verify your
  configuration.

o 77, 120-122, 255 -- Internal Error:  Contact your local service personnel.

o 70-73, 110-111 -- OS/2 error:  Review the FFST/2 message and error logs for
  additional information.

o 101-104, 201, 301-1028 -- WMS error:  Review the FFST/2 message and error
  logs for additional information.

o OTHER -- Contact your local support personnel.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.12. ACS3335 ΓòÉΓòÉΓòÉ

ACS3335-E The local Connection Manager subsystem encountered an unexpected
error during processing of a requested function.

Originator: ISDN Connection Manager

User Response:

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.

o Once the entry is found locate the attempted API function and the secondary
  return code in the Extra Symptom String section of the associated error log
  entry.  Return codes of 30xx or 33xx indicate the CMI completion code, and
  return codes of 34xx indicate the CCITT cause value in the last byte.  Refer
  to the ISDN CMI Programming Guide for corrective action relating to this
  return code.

o If the error is repeatable and a code bug is suspected, IBM can obtain the
  following additional control block information by replacing module CSPS99
  with a debug version.  The FFST/2 dump formatter can then be used to review
  the following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.  This control block is
     provided for all failures.

   - Connection record:  Provides an internal representation of the data
     related to this connection over ISDN.  This control block is provided for
     call establish, call control, and call clear failures.

   - Active adapter record:  Provides an internal representation of the
     dynamically generated adapter used for this ISDN link.  This control block
     is provided for call establish, call control, and call clear failures.

   - Configured Virtual Port:  Provides an internal representation of the
     configured virtual port adapter from which the "active adapter" was
     generated.  This control block is provided for all call-related failures.

   - SAP status:  Provides the current status of the SAP.  This control block
     is provided for all SAP-related failures.


ΓòÉΓòÉΓòÉ 3.37.13. ACS3336 ΓòÉΓòÉΓòÉ

ACS3336-E The local Connection Manager subsystem encountered an error while
attempting a Call Control Confirm function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - Connection record:  Provides an internal representation of the data
     related to this connection over ISDN.

   - Active adapter record:  Provides an internal representation of the
     dynamically generated adapter used for this ISDN link.

   - Configured ISDN adapter:  Provides an internal representation of the
     configured adapter from which the "active adapter" was generated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.14. ACS3337 ΓòÉΓòÉΓòÉ

ACS3337-E The local Connection Manager subsystem encountered an error while
attempting a Call Clear Confirm function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - Connection record:  Provides an internal representation of the data
     related to this connection over ISDN.

   - Active adapter record:  Provides an internal representation of the
     dynamically generated adapter used for this ISDN link.

   - Configured ISDN adapter:  Provides an internal representation of the
     configured adapter from which the "active adapter" was generated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.15. ACS3338 ΓòÉΓòÉΓòÉ

ACS3338-E The local Connection Manager subsystem encountered an error while
attempting a Call Clear Indication function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - Connection record:  Provides an internal representation of the data
     related to this connection over ISDN.

   - Active adapter record:  Provides an internal representation of the
     dynamically generated adapter used for this ISDN link.

   - Configured ISDN adapter:  Provides an internal representation of the
     configured adapter from which the "active adapter" was generated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.16. ACS3339 ΓòÉΓòÉΓòÉ

ACS3339-E The local Connection Manager subsystem encountered an error while
attempting an Enable Incoming Calls function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - Configured ISDN adapter:  Provides an internal representation of the
     configured adapter from which the "active adapter" was generated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.17. ACS3340 ΓòÉΓòÉΓòÉ

ACS3340-E The local Connection Manager subsystem encountered an error while
attempting a Disable Incoming Calls function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value. Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - Configured ISDN adapter:  Provides an internal representation of the
     configured adapter from which the "active adapter" was generated.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.18. ACS3341 ΓòÉΓòÉΓòÉ

ACS3341-E The local Connection Manager subsystem encountered an error while
attempting an Activate SAP Confirm function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - SAP status:  Provides the current status of the SAP.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.19. ACS3342 ΓòÉΓòÉΓòÉ

ACS3342-E The local Connection Manager subsystem encountered an error while
attempting an Deactivate SAP Confirm function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - SAP status:  Provides the current status of the SAP.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.20. ACS3343 ΓòÉΓòÉΓòÉ

ACS3343-E The local Connection Manager subsystem encountered an error while
attempting an Deactivate SAP Indication function.

Originator: ISDN Connection Manager

User Response: Locate the secondary return code in the Extra Symptom String
section of the associated error log entry.  This return code indicates the
Connection Manager completion code (33xx) or the CCITT cause value.  Refer to
Connection Manager documentation for corrective action with regards to this
return code.

o For additional information, use the FFST/2 dump formatter to review the
  following control blocks:

   - Connection Manager Primitive:  Provides the complete information sent by
     the Connection Manager related to this error.

   - SAP status:  Provides the current status of the SAP.

o For detailed information, use FFST/2 to access the system error log and
  review the associated error log entry.  Use the date, time, and problem ID
  from the FFST/2 message log formatter to help locate entries in the system
  error log.


ΓòÉΓòÉΓòÉ 3.37.21. ACS3344 ΓòÉΓòÉΓòÉ

ACS3344-E A major error has occurred in the 3270/5250 Session Management
Interface.

Originator: Communications Manager Kernel

User Response: KEY SYSTEM ERROR LOG INFORMATION:  For detailed information, use
FFST/2 to access the system error log and review the associated error log
entry. Use the date, time, and problem ID from the FFST/2 message log formatter
to help locate entries in the system error log.


ΓòÉΓòÉΓòÉ 3.37.22. ACS3350 ΓòÉΓòÉΓòÉ

ACS3350-W An unexpected return code was received from a Communications Manager
Kernel function call.

Originator: Subsystem Management

Explanation: A local Communications Manager Kernel function may have stopped.

User Response: Review the FFST/2 message log and the system error log for
details concerning the nature of the Communications Manager Kernel function
that stopped.  Then, complete the following steps:

o Locate the Extra Symptom String section of the associated system error log
  entry.  Review this section for the name of the Communications Manager Kernel
  function call that stopped and the associated return code.

o Refer to the Communications Manager Application Programming Guide for
  detailed descriptions of the Communications Manager Kernel functions and
  return codes.


ΓòÉΓòÉΓòÉ 3.37.23. ACS3351 ΓòÉΓòÉΓòÉ

ACS3351-E A system error ended a Communications Manager function. Subsystem
Management received an unexpected return code from an internal function call.

Originator: Subsystem Management

Explanation: A local Communications Manager Subsystem Management function may
have stopped.

User Response: Check the FFST/2 message log for more information about the
specific function failure. Then consult the Communications Manager Problem
Determination Guide for details about the specific error. The following is a
list of subtypes that are logged with this message, and a brief description of
what caused the error.

o 0001  An internal call to open the file 'CM.INI' failed.

o 0002  The file 'CM.INI' has too many lines.

o 0003  An internal request for memory failed.

o 0004  Parameters that are not valid were used on an internal function call.

o 0005  A function call to query the system for APPC Client/Server data
  returned an unexpected return code.

o 0006  A function call to query the system for CPI-C Client/Server data
  returned an unexpected return code.

o 0007  A function call to query the system for LUA Client/Server data returned
  an unexpected return code.

o 0008  A function call to begin a thread failed.

o 0009  An undefined message was received by the internal message queue
  handler.

o 000A  A call to ACSSVC using the CONVERT verb returned an unexpected return
  code.


ΓòÉΓòÉΓòÉ 3.37.24. ACS3356 ΓòÉΓòÉΓòÉ

ACS3356-W An unexpected return code was received from a System Management verb.

Originator: Subsystem Management

Explanation: A local System Management verb may not have succeeded.

User Response: Review the FFST/2 message log and the system error log for
details concerning the nature of the System Management verb. Then complete the
following steps:

o Locate the Extra Symptom Data section of the associated error log entry.
  Review this section for the name of the System Management verb and the
  associated return codes.

o Refer to the Communications Manager System Management Programming Reference
  for detailed descriptions of System Management verbs and their associated
  return codes.


ΓòÉΓòÉΓòÉ 3.37.25. ACS3357 ΓòÉΓòÉΓòÉ

ACS3357-E An internal processing error has occurred in the Communications
Manager Problem Determination system.

Originator: Problem Determination

User Response:

o See the FFST/2 system error log for the entry associated with this message.
  The entry is logged as 00000094 - 0000000n.  Explanations of the entry
  numbers are:

   - 00000094 - 00000001 The RAS daemon (ACSRASP.EXE) failed to start.

   - 00000094 - 00000002 The DFT trace formatter (ACS3ECT.DLL) failed to load
     properly. This error message is preceded by message ACS3138.

   - 00000094 - 00000003 Too many products attempted to register with the
     trace/dump facility.  The maximum allowed is 256.

   - 00000094 - 00000004 An error was encountered when processing data from the
     trace/dump system INI file (ACSRASTD.INI).

   - 00000094 - 00000005 A memory allocation error occurred.

   - 00000094 - 00000006 A dump request failed.

   - 00000094 - 00000007 A trace failed to activate.

   - 00000094 - 00000008 A failure occurred in the window-trace/dump
     interaction code. The requested function failed.

o Try the operation again.

o If the error recurs, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.37.26. ACS3358 ΓòÉΓòÉΓòÉ

ACS3358-E An internal processing error has occurred in the ISDN Common
Utilities.

Originator: ISDN CNM

User Response:

o See the FFST/2 system error log for the entry associated with this message.
  The entry is logged as 00000098 - 0000000n.  Explanations of the entry
  numbers are:

   - 00000098 - 00000001 A call to the CM Trace/Dump Subsystem (ACSRASTD.DLL)
     failed.

   - 00000098 - 00000002 An internal error has occurred.

   - 00000098 - 00000003 The requested dump was unable to complete.

   - 00000098 - 00000004 The requested dump was unable to start.

   - 00000098 - 00000005 A memory allocation error occurred.

   - 00000098 - 00000006 An error occurred while attempting to activate the
     requested service access point (SAP).

   - 00000098 - 00000007 An error occurred while attempting to deactivate the
     requested SAP.

o Try the function again.

o If the error recurs, contact your service coordinator.


ΓòÉΓòÉΓòÉ 3.37.27. ACS3360 ΓòÉΓòÉΓòÉ

ACS3360-E Common Programming Interface for Communications (CPI-C) is busy
processing a previous call.  CPI-C does not process concurrent calls from a
Transaction Program (TP).

Originator: Common Programming Interface for Communications

User Response: Do one of the following:

o Correct the application program by synchronizing calls to CPI-C.

o Use Start_TP (XCSTP) and Initialize_Conversation (XCINCT) to start multiple
  instances of TPs.

Use FFST/2 to access the system error log and review the associated error log
entry.  The date, time, and problem ID of this message log entry will help to
locate the entry in the system error log. Major error code 0052 is the error
that is logged when the application returns CM_PRODUCT_SPECIFIC_ERROR (return
code = X'14'). Refer to Common Programming Interface Communications Reference
for details about this return code.

o The Extra Symptom String section identifies the name of the CPI-C function
  that failed and the return code.


ΓòÉΓòÉΓòÉ 3.37.28. ACS3361 ΓòÉΓòÉΓòÉ

ACS3361-E The Common Programming Interface for Communications (CPI-C) call to
XCINCT or XCENDT is not valid because the CPIC TP ID parameter is set to zero.
When more than one TP is active, XCINCT and XCENDT cannot use a tp_id of zero.

Originator: Common Programming Interface for Communications

User Response: Correct the CPI-C call to either XCINCT or XCENDT by setting the
CPIC TP ID parameter to reference a specific TP.

o Use FFST/2 to access the system error log and review the associated error log
  entry.  The date, time, and problem ID of this message log entry will help to
  locate the entry in the system error log.

Major error code 0052 is the error that is logged when the application returns
CM_PRODUCT_SPECIFIC_ERROR (return code = X'14'). Refer to Common Programming
Interface Communications Reference for details about this return code.

o The Extra Symptom String section identifies the name of the CPI-C function
  that failed and the return code.


ΓòÉΓòÉΓòÉ 3.37.29. ACS3362 ΓòÉΓòÉΓòÉ

ACS3362-E The Module Enabler has encountered an error.

Originator: Module Enabler

User Response: Use the date, time, and problem ID from the FFST/2 message log
formatter to help locate the associated entry in the system error log.  There
you can locate the probe ID, the minor error code and the return code and refer
to Module Enabler documentation for corrective action for the particular error
found.


ΓòÉΓòÉΓòÉ 3.37.30. ACS3363 ΓòÉΓòÉΓòÉ

ACS3363-E The file APPCPD.DAT was not found. Verify cannot continue.

Originator: Configuration Services - Verify

User Response: The APPCPC.DAT file must exist for Communications Manager to
run. If the APPCPC.DAT file was accidentally renamed, change the file name back
to APPCPC.DAT. If the APPCPC.DAT file does not exist, reinstall Communications
Manager.


ΓòÉΓòÉΓòÉ 4. APN Messages ΓòÉΓòÉΓòÉ

This chapter lists the Communications Manager APN messages that can occur
during SNA configuration, verification, migration, or restoration.

See Before You Begin, for an introduction to Communications Manager messages.

Refer to Problem Determination Guide for additional information including
problem determination procedures, recommendations, diagnostic tools, reference
information, and instructions for contacting IBM.

To view the APN messages, press Ctrl+C to return to the Contents. Next, select
the plus sign (+) or press the + key to view the list of APN messages.


ΓòÉΓòÉΓòÉ 4.1. APN0000 through APN0231 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.1.1. APN0000 ΓòÉΓòÉΓòÉ

APN0000-I message text

where
message text    = message text

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.2. APN0004 ΓòÉΓòÉΓòÉ

APN0004-W An attempt to establish a link to the network node server has timed
out. Check the link station status using Communications Manager subsystem
management.  Review FFST /2 message and error logs and look for related
information.

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 4.1.3. APN0005 ΓòÉΓòÉΓòÉ

APN0005-W An attempt to establish a link to the network node server has failed.
Review FFST /2 message and error logs and look for related information.

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 4.1.4. APN0006 ΓòÉΓòÉΓòÉ

APN0006-W None of the links specified to be activated at startup could be
activated. A likely cause is that the specified adapter could not be activated.
Review FFST /2 message and error logs and look for related information.

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 4.1.5. APN0007 ΓòÉΓòÉΓòÉ

APN0007-W Link name(8) could not be activated.  A likely cause is that the
specified adapter could not be activated.  Review FFST /2 message and error
logs and look for related information.

where
name(8)         = link name

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 4.1.6. APN0008 ΓòÉΓòÉΓòÉ

APN0008-W Default directory for inbound attaches directory name specified on
the DEFINE_DEFAULTS verb does not exist.

where
directory name  = directory name

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 4.1.7. APN0009 ΓòÉΓòÉΓòÉ

APN0009-E An internal error was found in configuration file file name .  Verb
code: verb code Return Code: return code .  Ensure that the file name is
correct and verify it using CMVERIFY, and then restart. Refer to the System
Management Programming Reference for more information.

where
file name       = file name
verb code       = verb code
return code     = return code

Originator: SNA Communications Services (APPC)


ΓòÉΓòÉΓòÉ 4.1.8. APN0127 ΓòÉΓòÉΓòÉ

APN0127-I CPICOMM CPI-C/REXX environment registered successfully.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.9. APN0128 ΓòÉΓòÉΓòÉ

APN0128-W CPICOMM CPI-C/REXX environment already registered.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.10. APN0129 ΓòÉΓòÉΓòÉ

APN0129-E Not enough memory available to register CPICOMM CPI-C/REXX
environment.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.11. APN0130 ΓòÉΓòÉΓòÉ

APN0130-E An internal error has occurred while attempting to register the
CPICOMM CPI-C/REXX environment.  RxSubcomRegister return code = return code .

where
return code     = return code

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.12. APN0200 ΓòÉΓòÉΓòÉ

APN0200-E A configuration definition utility error occurred. Check the error
log for additional information.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.13. APN0203 ΓòÉΓòÉΓòÉ

APN0203-W Select Delete to confirm the deletion of the resource definition.
Select Cancel to cancel the delete request.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.14. APN0204 ΓòÉΓòÉΓòÉ

APN0204-E The new password and confirmation password are not the same. Each of
the two passwords entered must match.  Retype both passwords.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.15. APN0206 ΓòÉΓòÉΓòÉ

APN0206-W Select Continue to continue collecting network management data for
host focal point support.

Originator: APPN Configuration

Explanation: The previously deleted connection definition was the host focal
point that Communications Manager used to transmit network management data to
the host.  Since this connection has been deleted you can choose to continue
collecting network management data, or you can stop collecting the data.

User Response:

o Select Continue if another connection exists with an active SSCP-PU session,
  and you want that connection to be used to transmit network management data.
  Host focal point support will be continued.  If there is not an active
  session Communications Manager will continue to collect the data, but will
  not transmit it to the host.

o Select Cancel to stop collecting data.  Host focal point support will be
  disabled.


ΓòÉΓòÉΓòÉ 4.1.16. APN0209 ΓòÉΓòÉΓòÉ

APN0209-W The node to which link_name connects the workstation will no longer
be the preferred network node server.  If you want link_name deleted, select
Delete as follows.

where
link_name       = connection link name

Originator: APPN Configuration

Explanation: The specified connection no longer links the workstation to the
network node that provides server functions for the workstation.

User Response:

o Select Delete to delete the link.

o Select Cancel to keep the existing link.


ΓòÉΓòÉΓòÉ 4.1.17. APN0213 ΓòÉΓòÉΓòÉ

APN0213-E There is not enough memory available to continue processing.

Originator: APPN Configuration

Explanation: It is possible that several programs that each used a lot of
memory are running at the same time.  Because of this, disk space is not
available for memory swapping.

User Response:

o Reduce the number of active programs.

o Free some hard disk space.

o Delay the use of other memory intensive programs until the configuration
  process is complete.


ΓòÉΓòÉΓòÉ 4.1.18. APN0214 ΓòÉΓòÉΓòÉ

APN0214-E Node definitions file NDF_file could not be updated.  Check the error
log for additional information.

where
NDF_file        = APPN configuration file name

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.19. APN0217 ΓòÉΓòÉΓòÉ

APN0217-E The Partner node name field must be filled in before defining partner
LUs.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.20. APN0218 ΓòÉΓòÉΓòÉ

APN0218-E Select an item from the Mode Name drop-down list to complete the CPI
Communications Side Info window.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.21. APN0219 ΓòÉΓòÉΓòÉ

APN0219-E Both the Partner network ID and the Partner node name fields must be
completed when partner LUs are associated with the connection.

Originator: APPN Configuration

Explanation: This connection has partner LUs associated with it.

User Response: Either delete the partner LUs, or complete the partner network
ID and partner node name fields. To delete the partner LUs, do the following.

o Select OK to return to the window.

o Select Define Partner LUs.

o From the Change Partner LUs window, delete all partner LUs.


ΓòÉΓòÉΓòÉ 4.1.22. APN0221 ΓòÉΓòÉΓòÉ

APN0221-W Other SNA definitions exist that refer to the partner LU that was
changed.  Changing the partner LU may affect the other SNA definitions.

Originator: APPN Configuration

Explanation: This partner LU's fully qualified LU name or alias may be
associated with one of the following verbs:

o DEFINE PARTNER LU LOCATION

o DEFINE CPIC SIDE INFO

o CNOS.
Changing the partner LU may affect one of the preceding verbs.

User Response: If you do not want your changes applied to the partner LU,
select Cancel.  Or, if you want to change the verbs associated with the partner
LU, select Cancel, and then make the changes in the node definitions file
(.NDF). If you want your changes applied to the partner LU as well as any
associated verbs, select Change.


ΓòÉΓòÉΓòÉ 4.1.23. APN0222 ΓòÉΓòÉΓòÉ

APN0222-W Other SNA definitions exist that refer to the partner LU.  If you
delete the partner LU, those SNA definitions will also be deleted.

Originator: APPN Configuration

Explanation: This partner LU's fully qualified LU name or alias may be
associated with one of the following verbs:

o DEFINE PARTNER LU LOCATION

o DEFINE CPIC SIDE INFO

o CNOS.

User Response: If you do not want to delete the partner LU, select Cancel.  If
you want to change the verbs associated with the partner LU, select Cancel, and
then make the changes in the node definitions file (.NDF). If you want to
delete the partner LU and any verbs associated with it, select Delete.


ΓòÉΓòÉΓòÉ 4.1.24. APN0223 ΓòÉΓòÉΓòÉ

APN0223-E The Maximum negotiable session limit value must be greater than or
equal to the Mode session limit value.  Select OK for automatic update.

Originator: APPN Configuration

User Response:

o Select OK to automatically change the value for the Maximum negotiable
  session limit to equal that of the Mode session limit.

o Select Cancel to return to the previous window.  Then, change the Mode
  session limit to a value less than or equal to the Maximum negotiable session
  limit.


ΓòÉΓòÉΓòÉ 4.1.25. APN0224 ΓòÉΓòÉΓòÉ

APN0224-E The Mode session limit value must be greater than or equal to the
Minimum contention winners value.  Either decrease the value for the Minimum
contention winners or increase the value for the Mode session limit.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.26. APN0226 ΓòÉΓòÉΓòÉ

APN0226-E Security file SEC_filename.SEC could not be updated.

where
SEC_filename    = security file name

Originator: APPN Configuration

Explanation: The likely causes are:

o The disk is full.

o The security file is being used by another process.

o The security file attribute has been changed to read only.

User Response:

o Free some hard disk space.

o Stop the process using the .SEC file.

o Change the security file so that it is not read only.  From the OS/2 command
  prompt, enter ATTRIB -R file_name.SEC.


ΓòÉΓòÉΓòÉ 4.1.27. APN0228 ΓòÉΓòÉΓòÉ

APN0228-E Hexadecimal format passwords must be 16 characters long.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.28. APN0229 ΓòÉΓòÉΓòÉ

APN0229-E Character format passwords must be 8 characters long.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.29. APN0230 ΓòÉΓòÉΓòÉ

APN0230-E Select a local LU alias to complete the LU to LU Security window.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.1.30. APN0231 ΓòÉΓòÉΓòÉ

APN0231-E Select a Partner LU to complete the LU to LU Security window.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2. APN0232 through APN0291 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.2.1. APN0232 ΓòÉΓòÉΓòÉ

APN0232-E Both the Partner network ID and the Partner node name fields must be
completed or left blank.  These fields are required to define Partner LUs.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.2. APN0237 ΓòÉΓòÉΓòÉ

APN0237-E The required files to configure SNA Features could not be found.

Originator: APPN Configuration

Explanation: The likely causes are:

o The Communications Manager directory is not in the DPATH= statement in the
  CONFIG.SYS file.

o Communications Manager was not installed completely, or parts of it have been
  deleted from the system.

User Response:

o Ensure that the Communications Manager directory is in the DPATH= statement
  in the CONFIG.SYS file.

o If the CONFIG.SYS file is changed, the system must be restarted.

o If Communications Manager, or any part of it, was deleted from the system, it
  must be reinstalled from the installation diskettes.

  WARNING: If maintenance has been applied to Communications Manager (through
  the Corrective Service Diskette (CSD)), the maintenance must be reapplied if
  the Communications Manager installation diskettes are older than the CSD
  diskettes.


ΓòÉΓòÉΓòÉ 4.2.3. APN0239 ΓòÉΓòÉΓòÉ

APN0239-I Deletion of IBM supplied modes is not permitted.

Originator: APPN Configuration

Explanation: You are attempting to delete a mode definition that is one of the
standard IBM-supplied modes.  These mode definitions are shipped as part of the
Communications Manager and cannot be deleted.


ΓòÉΓòÉΓòÉ 4.2.4. APN0240 ΓòÉΓòÉΓòÉ

APN0240-I Changes are not permitted to CPSVCMG or SNASVCMG mode definitions.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.5. APN0242 ΓòÉΓòÉΓòÉ

APN0242-E The configuration control file APPNV.CTL is missing or could not be
found.

Originator: APPN Configuration

User Response:

o Ensure that APPNV.CTL is installed and that the DPATH= statement in the
  CONFIG.SYS file lists the subdirectory where the file is installed.

o If the CONFIG.SYS file is changed, the system must be restarted.

o If APPNV.CTL is missing, reinstall Communications Manager.


ΓòÉΓòÉΓòÉ 4.2.6. APN0243 ΓòÉΓòÉΓòÉ

APN0243-E Node definitions file NDF_filename..NDF could not be opened.

where
NDF_filename.   = APPN configuration file

Originator: APPN Configuration

Explanation: The likely causes are:

o The node definitions file is being used by another process.

o The node definitions file attribute has been changed to read only.

User Response:

o Stop the process using the node definitions file and retry the operation.

o Change the node definitions file so that it is not read only.  From the OS/2
  command prompt, enter ATTRIB -R file_name.NDF.


ΓòÉΓòÉΓòÉ 4.2.7. APN0244 ΓòÉΓòÉΓòÉ

APN0244-E Communications Manager configuration file CFG_filename.CFG could not
be opened.

where
CFG_filename    = Communications Manager configuration file

Originator: APPN Configuration

Explanation: The likely causes are:

o The configuration file is being used by another process.

o The configuration file attribute has been changed to read only.

User Response:

o Stop the process using the configuration file and retry the operation.

o Change the configuration file so that it is not read only.  From the OS/2
  command prompt, enter ATTRIB -R file_name.CFG.


ΓòÉΓòÉΓòÉ 4.2.8. APN0245 ΓòÉΓòÉΓòÉ

APN0245-E A critical Presentation Manager error occurred.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.9. APN0247 ΓòÉΓòÉΓòÉ

APN0247-W A critical error occurred.  Select OK to update the node definitions
file (NDF).  Warning:  If OK is selected, the NDF file NDF_filename will be
replaced by the saved file, but it will not be verified.

where
NDF_filename    = APPN configuration file

Originator: APPN Configuration

User Response:

o Select OK to save the changes and then close this window.

o Select Cancel to close this window without saving the changes.
Communications Manager configuration ends after a selection has been made.


ΓòÉΓòÉΓòÉ 4.2.10. APN0248 ΓòÉΓòÉΓòÉ

APN0248-W The Network node server address that was entered is already defined
on a connection with adjacent node name adj_node_name.  If the adjacent node
name is not correct, select Remove to clear the name.

where
adj_node_name   = Fully qualified adjacent node name

Originator: APPN Configuration

Explanation: The node type for the workstation you are defining a link to must
be a network node, and it should be your workstation's primary network node
server.  This name must be the control point (CP) name of the network node that
is adjacent to your node in the network, and acts as your network node server.

User Response:

o Select Remove to clear the adjacent node name and allow Communications
  Manager to automatically determine the correct adjacent node name at runtime.

o Select Cancel to keep the previously configured adjacent node name.


ΓòÉΓòÉΓòÉ 4.2.11. APN0252 ΓòÉΓòÉΓòÉ

APN0252-E Because the local node type has been changed to a network node, all
Partner LU location definitions must also be changed.

Originator: APPN Configuration

User Response: To change the Partner LU location definitions:

 1. Stop Communications Manager.

 2. Edit the node definitions file (.NDF) ensuring that all the partner LU
    location definitions have a fully qualified network node server, or the
    local node network node server is set to YES.

 3. From the OS/2 command prompt, enter CMVERIFY configuration_name.CFG.


ΓòÉΓòÉΓòÉ 4.2.12. APN0253 ΓòÉΓòÉΓòÉ

APN0253-E The security information file SEC_filename.SEC could not be opened.

where
SEC_filename    = security file name

Originator: APPN Configuration

Explanation: The likely causes are:

o The security file is being used by another process.

o The security file attribute has been changed to read only.

User Response:

o Stop the process that is using the security file and retry the operation.

o Change the security file so that it is not read only.  From the OS/2 command
  prompt, enter ATTRIB -R file_name.SEC.


ΓòÉΓòÉΓòÉ 4.2.13. APN0254 ΓòÉΓòÉΓòÉ

APN0254-E Security information file SEC_filename.SEC could not be read.

where
SEC_filename    = security file name

Originator: APPN Configuration

Explanation: The likely causes are:

o The security file is corrupted.

o The security file is locked by another process.

User Response:

o Stop the process that is using the .SEC file.

o Copy this file from a backup diskette, if one is available.

o Recreate the .SEC file.  From the OS/2 command prompt, enter APPNRST
  configuration_name.  This will recreate the .SEC file and the .NDF file from
  the binary .CF2 file.

  Note:  Make a copy of the .NDF file before restoring the .CF2 file, in case
  the .CF2 file is corrupted.

o Delete the .SEC file, and then go to the SNA Features List window and
  re-enter any security information previously defined.


ΓòÉΓòÉΓòÉ 4.2.14. APN0255 ΓòÉΓòÉΓòÉ

APN0255-E Node definitions file NDF_filename.NDF could not be read.

where
NDF_filename    = APPN configuration filename

Originator: APPN Configuration

Explanation: The likely causes are:

o The node definitions file (NDF) contains an incorrect verb.

o The node definitions file is corrupted.

o The node definitions file is locked by another process.

User Response:

o Look in the message log for information about the problem.

o Refer to the APPNV.CTL file (usually found in the CMLIB directory) for
  information on a valid NDF file syntax.  Correct the NDF file, and then retry
  the operation.

o Stop the process that is using the .NDF file.

o Copy this file from a backup diskette, if one is available.

o Recreate the .NDF file.  From the OS/2 command prompt, enter APPNRST
  configuration_name.  This will recreate the .NDF file and the .SEC file from
  the binary .CF2 file.

  Note:  Make a copy of the .SEC file before restoring the .CF2 file, in case
  the .CF2 file is corrupted.


ΓòÉΓòÉΓòÉ 4.2.15. APN0256 ΓòÉΓòÉΓòÉ

APN0256-E Configuration control file APPNV.CTL could not be read.

Originator: APPN Configuration

Explanation: The likely causes are:

o The configuration control file is corrupted.

o The configuration control file is locked by another process.

User Response:

o Stop the process that is using the configuration control file.

o Copy this file from a backup diskette, if one is available.

If the problem persists, reinstall Communications Manager.


ΓòÉΓòÉΓòÉ 4.2.16. APN0257 ΓòÉΓòÉΓòÉ

APN0257-E Communications Manager configuration file CFG_filename.CFG could not
be read.

where
CFG_filename    = Communications Manager configuration filename

Originator: APPN Configuration

Explanation: The likely causes are:

o The configuration file is corrupted.

o The configuration file is locked by another process.

User Response:

o Stop the process that is using the .CFG file.

o Copy this file from a backup diskette, if one is available.
If the problem persists, contact the service coordinator.


ΓòÉΓòÉΓòÉ 4.2.17. APN0258 ΓòÉΓòÉΓòÉ

APN0258-E The configuration control file APPNV.CTL is corrupted.  Check the
error log for additional information.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.18. APN0261 ΓòÉΓòÉΓòÉ

APN0261-E A critical internal error occurred.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.19. APN0262 ΓòÉΓòÉΓòÉ

APN0262-E A critical system error occurred.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.20. APN0263 ΓòÉΓòÉΓòÉ

APN0263-E The required dynamic link library (DLL) files could not be loaded.

Originator: APPN Configuration

Explanation: The likely causes are:

o The .DLL file is missing or is corrupted.

o The subdirectory that contains the DLL file has been removed from the
  LIBPATH= statement in the CONFIG.SYS file.

User Response:

o If the .DLL file is missing or corrupted, Communications Manager must be
  reinstalled from the installation diskettes.

  WARNING:If maintenance has been applied to Communications Manager (through
  the Corrective Service Diskette (CSD)), the maintenance must be reapplied if
  the Communications Manager installation diskettes are older than the CSD
  diskettes.

o Ensure that the subdirectory that contains the Communications Manager DLL
  files is included in the LIBPATH= statement in the CONFIG.SYS file.

o If the CONFIG.SYS file is changed, the system must be restarted.


ΓòÉΓòÉΓòÉ 4.2.21. APN0264 ΓòÉΓòÉΓòÉ

APN0264-E An internal error occurred.  API function code (hex) = API(8) Return
code (hex) = rc(8) Probe code (hex) = probe(8) Error type (hex) = errtype(8).

where
API(8)          = API code
rc(8)           = return code
probe(8)        = probe code
errtype(8)      = error type

Originator: APPN Configuration

User Response: Stop Communications Manager and restart the system.

If the problem persists, record the preceding information, the time, date, and
this message number.  Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.2.22. APN0265 ΓòÉΓòÉΓòÉ

APN0265-E An internal error occurred while loading the Configuration Definition
utility.  Check the error log for additional information.

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.23. APN0269 ΓòÉΓòÉΓòÉ

APN0269-E The configuration definition utility help file APPNP.HLP is not valid
or could not be found.

Originator: APPN Configuration

User Response:

o Ensure that APPNP.HLP is installed and that the SET HELP= statement in the
  CONFIG.SYS file lists the subdirectory where the file is installed.

o If the CONFIG.SYS file is changed, the system must be restarted.

o If the problem persists, reinstall Communications Manager.


ΓòÉΓòÉΓòÉ 4.2.24. APN0270 ΓòÉΓòÉΓòÉ

APN0270-E This command cannot be processed because of a lack of resources. API
function code (hex) = API(8) Return code (hex) = rc(8) Probe code (hex) =
probe(8) Error type (hex) = errtype(8).

where
API(8)          = API code
rc(8)           = return code
probe(8)        = probe code
errtype(8)      = error type

Originator: APPN Configuration

Explanation: It is possible that several programs that each use a lot of memory
are running at the same time.  Because of this, disk space is not available for
memory swapping.

User Response:

o Reduce the number of active programs.

o Free some hard disk space.

o Delay the use of other memory intensive programs until the configuration
  process is complete.


ΓòÉΓòÉΓòÉ 4.2.25. APN0275 ΓòÉΓòÉΓòÉ

APN0275-W The SNA configuration file NDF_file was not found, although the
binary version of it (a .CF2 file) exists.

where
NDF_file        = APPN configuration file

Originator: APPN Configuration

Explanation: A node definitions file (.NDF) is a text version of the binary
.CF2 file and it is used during configuration.  The .NDF file must either be
restored or replaced to continue the configuration.

User Response:

o Select Restore to reconstruct the .NDF file from the binary file.  This
  option will retain the current configuration.

o Select Replace to create new text and binary files. This option will destroy
  the old binary configuration file and replace it with a new one.

o Select Cancel to return to the previous window without making any changes.


ΓòÉΓòÉΓòÉ 4.2.26. APN0276 ΓòÉΓòÉΓòÉ

APN0276-E Binary SNA configuration file CF2_filename.CF2 could not be read.

where
CF2_filename    = binary configuration file

Originator: APPN Configuration

Explanation: The likely causes are:

o The file is corrupted.

o The file is locked by another process.

User Response:

o Stop the process using the .CF2 file.

o Copy this file from a backup diskette, if one is available.

o Recreate the .CF2 file.  From the OS/2 command prompt, enter CMVERIFY
  configuration_name.  This will recreate the .CF2 from the .NDF file.


ΓòÉΓòÉΓòÉ 4.2.27. APN0277 ΓòÉΓòÉΓòÉ

APN0277-E The Partner LU name that was entered is a duplicate of an existing
entry for the link link_name.  Partner LU names must be unique within a node.
Change the LU name and retry the operation.

where
link_name       = connection link name

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.28. APN0278 ΓòÉΓòÉΓòÉ

APN0278-E The Partner alias that was entered is a duplicate of an existing
entry for the link link_name.  LU aliases must be unique within a node.  Change
the alias and retry the operation.

where
link_name       = connection link name

Originator: APPN Configuration


ΓòÉΓòÉΓòÉ 4.2.29. APN0290 ΓòÉΓòÉΓòÉ

APN0290-E The local PU name for this link has been defined on another link.

Originator: APPN Configuration

Explanation: More than one host link uses the same PU name, and it is the same
as the CP name (default name).  If a host link connects to a network node, then
the PU name must be the CP name to allow CP to CP sessions to be activated.
Since the PU name is the same as the CP name, the configuration will verify
successfully.  Both links can be activated, but only one of the links can have
SSCP-PU sessions at a time.

User Response: To use SSCP-PU sessions simultaneously on the links, change the
PU name on one of the links so that the names do not match. Ensure that any
link with an adjacent node type of network node and CP to CP sessions has the
same PU name as the CP name. It is possible to have one link for dependent
sessions and another parallel link for APPN traffic for both PU and APPN
traffic to multiple hosts.


ΓòÉΓòÉΓòÉ 4.2.30. APN0291 ΓòÉΓòÉΓòÉ

APN0291-E The Node ID is not unique.  Enter a unique name.

Originator: APPN Configuration

User Response: Select OK to return to the window.  Then enter a unique node ID.


ΓòÉΓòÉΓòÉ 4.3. APN0292 through APN0409 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.3.1. APN0292 ΓòÉΓòÉΓòÉ

APN0292-E The Outgoing Call Directory entry and the IDLC destination address
combinations must be unique.

Originator: APPN Configuration

Explanation: The Outgoing Call Directory Entry is associated with the ISDN
connections.

User Response: Select OK to return to the window.  Then enter unique
combinations for the Outgoing Call Directory entry and the IDLC destination
address.


ΓòÉΓòÉΓòÉ 4.3.2. APN0293 ΓòÉΓòÉΓòÉ

APN0293-E This connection has a host LU or a gateway host LU pool associated
with it.  You must delete the associated definition before a successful
deletion of the connection can happen.

Originator: APPN Configuration

Explanation: This connection has either host LUs or gateway host LU pools
associated with it.  Before this connection can be deleted, the associated
definitions must be deleted.  You can delete the associated gateway definitions
from the Gateway configuration windows.

User Response: The associated gateway definitions need to be removed. Use the
Gateway configuration windows to remove the definition.  Host connections may
have both host LU pool and host LU definitions associated, that may prevent
their deletion.  Workstation connections can only have host LU definitions
preventing their proper deletion.


ΓòÉΓòÉΓòÉ 4.3.3. APN0294 ΓòÉΓòÉΓòÉ

APN0294-W This connection has gateway configuration definitions associated with
it.  If you want to continue, the gateway definitions will also be changed.

Originator: APPN Configuration

Explanation: You have selected to change a connection that has associated
gateway configuration definitions.

User Response: If you want to continue and apply the changes that you have made
to the link, select Change.  The associated gateway definitions will
automatically be updated to match the changed connection.  If you are not sure
that you want to apply the changes at this time, select Cancel to return to the
Connection definition window.


ΓòÉΓòÉΓòÉ 4.3.4. APN0295 ΓòÉΓòÉΓòÉ

APN0295-W Host focal point support must not be configured when the NetWare
server is host attached.  Select OK for automatic update.

Originator: APPN Configuration

Explanation: When using Systems Network Architecture (SNA) management support
for NetWare, if the NetWare server is host attached (NW_UPSTREAM), host focal
point support can not be configured in CM/2.

User Response:

o Select OK to automatically remove host focal point support from the
  configuration.

o Select Cancel to return to the previous window.  Then, change the management
  support so that either the local node is host attached or no NetWare
  management support is configured.


ΓòÉΓòÉΓòÉ 4.3.5. APN0296 ΓòÉΓòÉΓòÉ

APN0296-E A value must be specified for either the destination information
field or the adjacent node ID field.

Originator: APPN Configuration

Explanation: Neither the destination information field nor the adjacent node ID
field has been assigned a value. One of these fields needs to be completed. The
destination information field which appears on this window depends on your
selected DLC type.  For example, the LAN destination address field appears for
a LAN DLC type.

User Response: Specify a value for one of the two indicated fields.  Then retry
the operation.


ΓòÉΓòÉΓòÉ 4.3.6. APN0297 ΓòÉΓòÉΓòÉ

APN0297-W This connection has 3270 emulator definitions associated with it.  If
processing continues, the emulator definitions will also be changed.

Originator: APPN Configuration

Explanation: You have selected to change a connection that has associated 3270
emulator definitions.

User Response: To continue and apply the changes to the link, select Change.
The associated 3270 emulator is automatically updated to match the changed
connection.  If you are not sure that you want to apply the changes at this
time, select Cancel to return to the Connection Definition window.


ΓòÉΓòÉΓòÉ 4.3.7. APN0298 ΓòÉΓòÉΓòÉ

APN0298-E There is not enough disk space to update the configuration file. Free
some space and select Retry. WARNING:  If you select Cancel or close the
message window, data will be lost and the file may be unusable.

Originator: APPN Configuration

Explanation: There is insufficient space on the disk to update either the node
definitions file (.NDF), the SNA configuration file (.CF2), or the security
information file (.SEC).

User Response: Leave the message window open and follow these steps:

o Open another OS/2 window.

o Erase unneeded files from the disk to provide more disk space.

o When more space is available, return to the message window and select Retry
  to try the operation again.

o Note:  If you select Cancel or close the message window, erase the corrupted
  configuration files and recreate the configuration.


ΓòÉΓòÉΓòÉ 4.3.8. APN0301 ΓòÉΓòÉΓòÉ

APN0301-E A character that is not valid was entered in this field, or the
entire field has not been completed.

Originator: APPN Configuration

User Response: Select OK to return to the entry window containing the field.
Then press F1 to display the valid characters for this field.


ΓòÉΓòÉΓòÉ 4.3.9. APN0302 ΓòÉΓòÉΓòÉ

APN0302-E The number entered is outside the valid range.

Originator: APPN Configuration

User Response: Select OK to return to the entry window containing the field.
Then press F1 to display the valid ranges for this field.


ΓòÉΓòÉΓòÉ 4.3.10. APN0303 ΓòÉΓòÉΓòÉ

APN0303-E Data must be entered in this field.

Originator: APPN Configuration

User Response: Select OK to return to the entry window containing the field.
Then press F1 to display the valid characters for this field.


ΓòÉΓòÉΓòÉ 4.3.11. APN0304 ΓòÉΓòÉΓòÉ

APN0304-E The entire field must be completed.

Originator: APPN Configuration

User Response: Select OK to return to the entry window containing the field.
Then press F1 to display the valid characters for this field.


ΓòÉΓòÉΓòÉ 4.3.12. APN0306 ΓòÉΓòÉΓòÉ

APN0306-Q Messages were logged to the FFST/2 message log.  Would you like to
invoke the FFST/2 Message Log Formatter to view the FFST/2 message log?

Originator: Configuration Services - Advanced

Explanation:

While reading the configuration information in the node definitions file
(.NDF), messages were logged to the FFST/2 message log.

User Response:

o Select YES to invoke the FFST/2 Message Log Formatter to view the FFST/2
  message log.

o Select NO if you do not want to invoke FFST/2.

Note:  This is equivalent to starting the Message Log Formatter from the FFST/2
folder and opening the first file listed in the files list. By default this
file is C:\OS2\SYSTEM\OS2MLOG.DAT.  However, if you selected a different drive
when you installed OS/2, this file will be on the drive you selected.


ΓòÉΓòÉΓòÉ 4.3.13. APN0307 ΓòÉΓòÉΓòÉ

APN0307-E Number entered is outside the valid range.

Originator: APPN Configuration

Explanation: The number entered for the entry field is outside the allowed
numeric range.

User Response:

o Re-enter a valid number within the range specified.


ΓòÉΓòÉΓòÉ 4.3.14. APN0308 ΓòÉΓòÉΓòÉ

APN0308-E The node definitions file NDF_file could not be locked.

where
NDF_file        = APPN configuration file name

Originator: APPN Configuration

Explanation: The DosOpen call to open and lock the node definitions file (.NDF)
failed.

User Response:

o Identify the application that has locked the node definitions file (.NDF),
  and ensure that the file is no longer locked, then retry the operation.

o If the file is still locked, you may have to shutdown and restart your
  computer to unlock the node definitions file. Otherwise, you can create or
  edit another configuration.


ΓòÉΓòÉΓòÉ 4.3.15. APN0309 ΓòÉΓòÉΓòÉ

APN0309-W Other SNA definitions exist that refer to the changed local LU or
local CP alias.  Changing the alias may affect the other SNA definitions.

Originator: APPN Configuration

Explanation: The alias of the local LU or local CP may be associated with
either the CNOS or the 5250 emulation profile verb. Changing the alias may
affect one of these verbs.

User Response: If you do not want to change the local LU or local CP
definition, select Cancel.  If you want to change the other definitions
independently of the local LU or local CP definition, select Cancel and then
make the changes in the node definitions file (.NDF) or in the associated
emulation profile.


ΓòÉΓòÉΓòÉ 4.3.16. APN0310 ΓòÉΓòÉΓòÉ

APN0310-W A change number of sessions (CNOS) verb exists that references this
local LU definition.  If you delete the LU definition without deleting the CNOS
verb at the same time, an error will occur at verify time.

Originator: APPN Configuration

User Response: If you do not want to delete the local LU definition, select
Cancel.  Or, if you want to change the CNOS verb so that it references a
different local LU definition, select Cancel, and then go to the node
definitions file (.NDF) to make the change. If you want to delete the CNOS verb
and the local LU definition, select Delete.


ΓòÉΓòÉΓòÉ 4.3.17. APN0350 ΓòÉΓòÉΓòÉ

APN0350-E There are not enough compression tokens allocated to allow a session
at the maximum compression level configured.

Originator: APPN Configuration

Explanation: There must be a sufficient number of compression tokens allocated
before a session can be started at the compression level configured.

User Response:

Do one of the following:

o Increase the number of compression tokens

o Decrease the compression level


ΓòÉΓòÉΓòÉ 4.3.18. APN0351 ΓòÉΓòÉΓòÉ

APN0351-W The value of maximum compression tokens is ignored if the value of
maximum compression level is NONE.

Originator: APPN Configuration

Explanation: The number entered for maximum compression tokens has no effect
when the maximum compression level is NONE.

User Response:

Do one of the following:

o Set maximum compression tokens to zero.

o Change the level configured for maximum compression level.


ΓòÉΓòÉΓòÉ 4.3.19. APN0352 ΓòÉΓòÉΓòÉ

APN0352-W The PLU->SLU and SLU->PLU compression level settings will be ignored.

Originator: APPN Configuration

Explanation: A level of compression was chosen for one of the directional
compression settings.  If either SYSTEM or PROHIBITED was specified for
Compression need, compression level settings are ignored.

User Response:

Do one of the following:

o Set both PLU->SLU and SLU->PLU compression levels to NONE.

o Select REQUESTED for Compression need to ensure the specified directional
  compression levels are used.


ΓòÉΓòÉΓòÉ 4.3.20. APN0353 ΓòÉΓòÉΓòÉ

APN0353-W PLU->SLU and SLU->PLU compression levels of NONE causes no
compression to take place.

Originator: APPN Configuration

Explanation: Because the PLU->SLU and SLU->PLU compression levels are set to
NONE, no compression will take place.  This is inconsistent with a Compression
need of REQUESTED.

User Response:

Change one of the following:

o Value supplied for PLU->SLU compression level

o Value supplied for SLU->PLU compression level

o Level configured for Compression need


ΓòÉΓòÉΓòÉ 4.3.21. APN0400 ΓòÉΓòÉΓòÉ

APN0400-E DosAllocSeg failed.  DosAllocSeg return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: A memory allocation error occurred.  The probable cause of return
code 8 is that OS/2 does not have enough free memory to satisfy the request.

User Response: Retry the operation (OS/2 memory shortages are usually
temporary).  If the error recurs, try to free some memory by stopping some
active OS/2 processes or by instructing the processes to free any unused
memory.  Then retry the operation. If the problem continues, note the time,
date and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.3.22. APN0401 ΓòÉΓòÉΓòÉ

APN0401-E DosSubSet failed.  DosSubSet return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: A memory allocation error occurred.  The probable cause of return
code 8 is that OS/2 does not have enough free memory to satisfy the request.

User Response: Retry the operation (OS/2 memory shortages are usually
temporary).  If the error recurs, try to free some memory by stopping some
active OS/2 processes or by instructing the processes to free any unused
memory.  Then retry the operation. If the problem continues, note the time,
date and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.3.23. APN0402 ΓòÉΓòÉΓòÉ

APN0402-E DosSubAlloc failed.  DosSubAlloc return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: A memory allocation error occurred.  The probable cause of return
code 8 is that OS/2 does not have enough free memory do satisfy the request.

User Response: Retry the operation (OS/2 memory shortages are usually
temporary).  If the error recurs, try to free some memory by stopping some
active OS/2 processes or by instructing the processes to free any unused
memory.  Then retry the operation. If the problem continues, note the time,
date and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.3.24. APN0403 ΓòÉΓòÉΓòÉ

APN0403-E Command syntax error detected on line num(5) of the node definitions
file (.NDF).

where
num(5)          = line number

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.3.25. APN0404 ΓòÉΓòÉΓòÉ

APN0404-E Command 'name(32)' on line num(5) of the node definitions file (.NDF)
is specified incorrectly.

where
name(32)        = command name
num(5)          = line number

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.3.26. APN0405 ΓòÉΓòÉΓòÉ

APN0405-W Command 'name(32)' on line num(5) of the node definitions file (.NDF)
is inconsistent.

where
name(32)        = command name
num(5)          = line number

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.3.27. APN0406 ΓòÉΓòÉΓòÉ

APN0406-W DosOpen failed for the security information file (.SEC).  DosOpen
return code = rc(5).  Ignore this message if no SNA information is needed.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.
Probable causes for the return codes are:

o 2  The file does not exist.

o 3  The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110 The file does not exist.

If no SNA security information has been created for this configuration, the
specified file does not exist.

User Response: Ensure that the correct configuration name is specified.  If
not, retry the operation using the correct name. If SNA security information
has not yet been created for this configuration, you can ignore the message.  A
new file will be created for the configuration. If the file is currently being
updated by another OS/2 process, either wait for the other process to complete,
instruct the other process to release the file, or stop the process.  Then
retry the operation. If the return code indicates the file does not exist, the
file might not exist or might be damaged. Create a new file, or restore the
file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.3.28. APN0407 ΓòÉΓòÉΓòÉ

APN0407-E DosRead failed for the Communications Manager configuration file
(.CFG).  DosRead return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while attempting to read the Communications
Manager configuration file.  The DosRead function call failed with the
indicated return code.

User Response: Retry the operation. You may have to restore the configuration
from a backup copy or by using one of the file restoration utilities. If the
problem continues, note the time, date and identification number of this
message, along with any return code.  Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.3.29. APN0408 ΓòÉΓòÉΓòÉ

APN0408-E DosRead failed for the Communications Manager configuration file
(.CFG).  Unexpected end-of-file encountered.

Originator: APPN Configuration

Explanation: An error occurred while attempting to read the Communications
Manager configuration file.  The configuration utility expected more data to be
available, but the DosRead function call indicated that no more data was
available in the file.

User Response: Retry the operation. You may have to restore the configuration
from a backup copy or by using one of the file restoration utilities. If the
problem continues, note the time, date and identification number of this
message, along with any return code.  Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.3.30. APN0409 ΓòÉΓòÉΓòÉ

APN0409-E DosChgFilePtr failed for the Communications Manager configuration
file (.CFG).  DosChgFilePtr return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while attempting to read the Communications
Manager configuration file.  The DosChgFilePtr function call failed with the
indicated return code.

User Response: Retry the operation. You may have to restore the Configuration
from a backup copy or by using one of the file restoration utilities. If the
problem continues, note the time, date and identification number of this
message, along with any return code.  Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.4. APN0410 through APN0458 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.4.1. APN0410 ΓòÉΓòÉΓòÉ

APN0410-E APPC/SNA is not configured in the Communications Manager
configuration file (.CFG).

Originator: APPN Configuration

Explanation: Communications Manager attempted to upgrade SNA information for
the configuration, but SNA profiles were not defined in the configuration.  The
configuration file (.CFG) may be corrupted.  The configuration could not be
upgraded.

User Response: Restore the configuration file from a backup and retry the
operation, or create a new configuration.


ΓòÉΓòÉΓòÉ 4.4.2. APN0411 ΓòÉΓòÉΓòÉ

APN0411-E The version of the Communications Manager configuration file (.CFG)
is no longer supported by this version of the Communications Manager. You must
upgrade the configuration file before proceeding.

Originator: APPN Configuration

Explanation: The configuration file does not reflect a current release of
Communications Manager.  SNA support requires Version 1.2 or greater.

User Response: Upgrade the configuration to Version 1.2 or greater.  If you do
not have the correct version of Communications Manager installed, obtain
Version 1.2 (or greater) and install it on your workstation.


ΓòÉΓòÉΓòÉ 4.4.3. APN0412 ΓòÉΓòÉΓòÉ

APN0412-E The Communications Manager configuration file (.CFG) is not verified.

Originator: APPN Configuration

Explanation: The Communications Manager configuration could not be upgraded to
the current version because it has not been verified.

User Response: Verify the configuration using the Verify option of
Communications Manager, using the same version of Communications Manager that
was used to create the configuration. If the verification was successful or
generated warning messages only, retry the operation. If the verification
failed, you must change the configuration and retry the verification.  After
the configuration is verified, retry the operation. For more details on how to
verify or change the Communications Manager configuration, refer to the
Communications Manager Configuration Guide.


ΓòÉΓòÉΓòÉ 4.4.4. APN0415 ΓòÉΓòÉΓòÉ

APN0415-E DosQPathInfo failed for the configuration file directory.

Originator: APPN Configuration

Explanation: An error occurred while trying to access the directory where the
current configuration file is stored.

User Response: Make sure the correct path and directory are specified for the
configuration file.  Retry the operation.  If the failure still occurs, move
the configuration files to a different directory and retry the operation.


ΓòÉΓòÉΓòÉ 4.4.5. APN0416 ΓòÉΓòÉΓòÉ

APN0416-E Node definitions file name name(260) is not valid.

where
name(260)       = node definitions file name

Originator: APPN Configuration

Explanation: The file name you specified when starting a configuration utility
is not a valid node definitions file name.  The node definitions file can be
specified in several different ways:

o Specify the file name only (no file extension).  The configuration utilities
  will add the correct file extension (.NDF), and will look for the file in the
  current directory.

o Specify the file name and file extension.  The extension must be .NDF for
  node definitions files.  The configuration utilities will look for the file
  in the current directory.

o Specify the directory along with the file name (no file extension).  The
  configuration utilities will create the complete file name by adding the
  correct file extension (.NDF).

o Specify the complete file name, including the directory name.

User Response: Restart the configuration utility, specifying the node
definitions file name in the correct format.


ΓòÉΓòÉΓòÉ 4.4.6. APN0417 ΓòÉΓòÉΓòÉ

APN0417-W DosOpen failed for the node definitions file file name(12).  DosOpen
return code = rc(5).  Ignore this message if no SNA information is needed.

where
file name(12)   = file name
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.
Probable causes for the return codes are:

o 2  The file does not exist.

o 3  The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110 The file does not exist. If no security SNA information has been created
  for this configuration, the specified file does not exist.

User Response: Ensure that the correct configuration name is specified.  If
not, retry the operation using the correct name. If no SNA information has been
created for this configuration, you can ignore the message.  A new file will be
created for the configuration.  If the file is currently being updated by
another OS/2 process, either wait for the other process to complete, instruct
the other process to release the file, or stop the process.  Then retry the
operation. If the return code indicates the file does not exist, the file might
not exist or it might be damaged.  You can create a new file, or restore the
file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.7. APN0418 ΓòÉΓòÉΓòÉ

APN0418-E DosOpen failed for the configuration control file (.CTL).  DosOpen
return code = rc(5).  Ignore this message if no SNA information is needed.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.  The
probable cause for each return code is:

o 2  The file does not exist.

o 3  The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110 The file does not exist.

User Response: Ensure that you specified the correct configuration name.  If
not, retry the operation using the correct name. If the file is currently being
updated by another OS/2 process, either wait for the other process to complete,
instruct the other process to release the file, or stop the process.  Then
retry the operation. If the return code indicates the file does not exist, the
file might not exist or might be damaged.  You can create a new file, or you
can restore the file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.8. APN0419 ΓòÉΓòÉΓòÉ

APN0419-E DosOpen failed for the Communications Manager configuration file
(.CFG).  DosOpen return code = rc(5).  Ignore this message if no SNA
information is needed.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.
Probable causes are:

o Return Code   Probable Cause

   - 2        The file does not exist.

   - 3        The file does not exist.

   - 32       The file is currently being updated by another OS/2 process.

   - 110       The file does not exist.

User Response: Ensure that you specified the correct configuration name.  If
not, retry the operation using the correct name. If the file is currently being
updated by another OS/2 process, either wait for the other process to complete,
instruct the other process to release the file, or stop the process.  Then
retry the operation. If the return code indicates the file does not exist, the
file might not exist or might be damaged.  You can create a new file, or you
can restore the file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.9. APN0420 ΓòÉΓòÉΓòÉ

APN0420-W DosOpen failed for the SNA configuration file (.CF2).  DosOpen return
code = rc(5).  Ignore this message if no SNA information is needed.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.
Probable causes for the return codes are:

o 2  The file does not exist.

o 3  The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110 The file does not exist.

If no SNA information has been created for this configuration, the specified
file does not exist.

User Response: Ensure that the correct configuration name is specified.  If it
is not, retry the operation using the correct name. If no SNA information has
been created for this configuration, ignore the message.  A new file will be
created. If the file is currently being updated by another OS/2 process, either
wait for the other process to complete, instruct the other process to release
the file, or stop the process.  Then retry the operation. If the return code
indicates the file does not exist, the file might not exist or it might be
damaged. Create a new file, or restore the file by using a backup copy or a
file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.10. APN0421 ΓòÉΓòÉΓòÉ

APN0421-E DosOpen failed for the security information file (.SEC).  DosOpen
return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.  The
probable cause for each return code is:

o 2  The file does not exist.

o 3  The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110 The file does not exist.

User Response: Ensure that you specified the correct configuration name.  If
not, retry the operation using the correct name. If the file is currently being
updated by another OS/2 process, either wait for the other process to complete,
instruct the other process to release the file, or stop the process.  Then
retry the operation. If the return code indicates the file does not exist, the
file might not exist or might be damaged.  You can create a new file, or you
can restore the file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.11. APN0422 ΓòÉΓòÉΓòÉ

APN0422-E DosOpen failed for the configuration log file (.LOG).  DosOpen return
code = rc(5).  Ignore this message if no SNA information is needed.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.  The
probable cause for each return code is:

o 2   The file does not exist.

o 3   The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110  The file does not exist.

User Response: Ensure that you specified the correct configuration name.  If
not, retry the operation using the correct name. If the file is currently being
updated by another OS/2 process, either wait for the other process to complete,
instruct the other process to release the file, or stop the process.  Then
retry the operation. If the return code indicates the file does not exist, the
file might not exist or might be damaged.  You can create a new file, or you
can restore the file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.12. APN0423 ΓòÉΓòÉΓòÉ

APN0423-E DosOpen failed for the debug file (.DBG).  DosOpen return code =
rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while trying to open the specified file.
Probable causes are:

o 2  The file does not exist.

o 3  The file does not exist.

o 32  The file is currently being updated by another OS/2 process.

o 110 The file does not exist.

User Response: Ensure that the correct configuration name is specified.  If it
is not, retry the operation using the correct name. If the file is currently
being updated by another OS/2 process, either wait for the other process to
complete, instruct the other process to release the file, or stop the process.
Then retry the operation. If the return code indicates the file does not exist,
the file might not exist or might be damaged. Create a new file, or restore the
file by using a backup copy or a file-restoration utility.


ΓòÉΓòÉΓòÉ 4.4.13. APN0424 ΓòÉΓòÉΓòÉ

APN0424-E Configuration control file name name(260) is not valid.

where
name(260)       = configuration control file name

Originator: APPN Configuration

Explanation: An alternate configuration control file was specified for starting
a configuration utility.  However, the file name is not a configuration control
file name.  The configuration control file can be specified in several
different ways:

o Specify the file name only (no file extension).  The configuration utilities
  will add the correct file extension (.CTL), and will look for the file in the
  current directory.

o Specify the file name and file extension.  The extension must be .CTL for
  configuration control files.  The configuration utilities will look for the
  file in the current directory.

o Specify the directory along with the file name (no file extension). The
  configuration utilities will create the complete file name by adding the
  correct file extension (.CTL).

o Specify the complete file name, including the directory name.

User Response: Restart the configuration utility, specifying the configuration
control file name in the correct format.


ΓòÉΓòÉΓòÉ 4.4.14. APN0425 ΓòÉΓòÉΓòÉ

APN0425-E Communications Manager configuration file name name(260) is not
valid.

where
name(260)       = Communications Manager file name

Originator: APPN Configuration

Explanation: The file name specified when starting a configuration utility is
not a valid configuration file name.  The configuration can be specified in
several different ways:

o Specify the file name only (no file extension).  The configuration utilities
  will add the correct file extension (.CFG), and will look for the file in the
  current directory.

o Specify the file name and file extension.  The extension must be .CFG for
  configuration files. The configuration utilities will look for the file in
  the current directory.

o Specify the directory along with the file name (no file extension). The
  configuration utilities will create the complete file name by adding the
  correct file extension (.CFG).

o Specify the complete file name, including the directory name.

User Response: Restart the configuration utility, specifying the configuration
file name in the correct format.


ΓòÉΓòÉΓòÉ 4.4.15. APN0426 ΓòÉΓòÉΓòÉ

APN0426-E SNA configuration file name name(260) is not valid.

where
name(260)       = SNA configuration file name

Originator: APPN Configuration

Explanation: The file name specified when starting a configuration utility is
not a valid SNA configuration file name.  The configuration file can be
specified in several different ways:

o Specify the file name only (no file extension).  The configuration utilities
  will add the correct file extension (.CF2), and will look for the file in the
  current directory.

o Specify the file name and file extension.  The extension must be .CF2 for SNA
  configuration files.  The configuration utilities will look for the file in
  the current directory.

o Specify the directory along with the file name (no file extension). The
  configuration utilities will create the complete file name by adding the
  correct file extension (.CF2).

o Specify the complete file name, including the directory name.

User Response: Restart the configuration utility, specifying the SNA
configuration file name in the correct format.


ΓòÉΓòÉΓòÉ 4.4.16. APN0427 ΓòÉΓòÉΓòÉ

APN0427-E Security information file name name(260) is not valid.

where
name(260)       = security information file name

Originator: APPN Configuration

Explanation: The file name specified when starting a configuration utility is
not a valid security information file name.

User Response: The security information file can be specified in several
different ways:

o Specify the file name only (no file extension).  The configuration utilities
  will add the correct file extension (.SEC), and will look for the file in the
  current directory.

o Specify the file name and file extension.  The extension must be .SEC for
  security information files. The configuration utilities will look for the
  file in the current directory.

o Specify the directory along with the file name (no file extension). The
  configuration utilities will create the complete file name by adding the
  correct file extension (.SEC).

o Specify the complete file name, including the directory name.

Restart the configuration utility, specifying the security information file
name in the correct format.


ΓòÉΓòÉΓòÉ 4.4.17. APN0428 ΓòÉΓòÉΓòÉ

APN0428-E DosWrite failed for the node definitions file (.NDF).  Incorrect
number of bytes written.

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Assume that
the contents of the file are no longer valid. The most probable cause of the
error is there is not enough storage on the disk to hold the file.

User Response: Free any unused disk space (by moving or erasing unused files)
and retry the operation. If the problem continues, note the time, date and
identification number of this message, along with any return code.  Then
contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.4.18. APN0429 ΓòÉΓòÉΓòÉ

APN0429-E DosWrite failed for the node definitions file (.NDF) end-of-file
character.

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Assume that
the contents of the file are no longer valid. The most probable cause of the
error is there is not enough storage on the disk to hold the file.

User Response: Free any unused disk space (by moving or erasing unused files)
and retry the operation. If the problem continues, note the time, date and
identification number of this message, along with any return code.  Then
contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.4.19. APN0430 ΓòÉΓòÉΓòÉ

APN0430-E DosClose or DosWrite failed for the node definitions file (.NDF).
DosWrite/DosClose return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Assume that
the contents of the file are no longer valid. The most probable cause of the
error is there is not enough storage on the disk to hold the file.

User Response: Free any unused disk space (by moving or erasing unused files)
and retry the operation. If the problem continues, note the time, date and
identification number of this message, along with any return code.  Then
contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.4.20. APN0433 ΓòÉΓòÉΓòÉ

APN0433-E An error occurred while reading the configuration control file
(.CTL).

Originator: APPN Configuration

Explanation: An error occurred while reading the specified file.

User Response: Retry the operation.  If the error recurs, try to correct the
problem indicated by the return code, and retry the operation.  You may have to
restore the file from a backup copy or by using one of the file restoration
utilities. See the detailed description of the message for information about
the file restoration utilities and their possible side effects. If the problem
continues, note the time, date and identification number of this message, along
with any return code.  Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.4.21. APN0434 ΓòÉΓòÉΓòÉ

APN0434-W An empty or missing security information file (.SEC) is okay if no
security information is defined in the SNA configuration.  An empty security
information file will be created.

Originator: APPN Configuration

Explanation: The configuration utility did not find a security information
file.  It assumed that no SNA security information was defined (session level
security, conversation level security, or CPI Communications side information
entries with program security defined).  The configuration utility created a
security information file with no security information in it so this message
will not appear again.  The configuration utility continues processing.

User Response: If the assumption is valid (no SNA security information is
defined for this configuration), and no other errors occurred, then everything
was successful and this message can be ignored. If SNA security information was
defined for this configuration, you must restore the security information file
from a backup or create a new file.


ΓòÉΓòÉΓòÉ 4.4.22. APN0437 ΓòÉΓòÉΓòÉ

APN0437-E Parsing of the node definitions file failed.

Originator: APPN Configuration

Explanation: An error occurred while the node definitions file (.NDF) was being
parsed.  Likely causes are that the file is corrupted, or that the file was
edited and syntax errors were introduced.  This message should be preceded in
the error log by other messages that specifically describe the error.

User Response: Examine the other entries in the log file for more information
about the error.  If the error was introduced by editing the node definitions
file, correct the error.  Otherwise, restore the file from a backup, or use one
of the file restoration utilities. Then retry the operation.


ΓòÉΓòÉΓòÉ 4.4.23. APN0438 ΓòÉΓòÉΓòÉ

APN0438-E An error occurred while creating the IBM-supplied mode and class of
service definitions.

Originator: APPN Configuration

Explanation: An error occurred while trying to create an IBM-supplied
definition.

User Response: Another message will have been displayed immediately before this
message that identifies the problem in greater detail (either APN0400, APN0401
or APN0402).  Refer to the description of that message to find the cause of the
problem and the recommended actions for correcting it.  Then retry the
operation.


ΓòÉΓòÉΓòÉ 4.4.24. APN0441 ΓòÉΓòÉΓòÉ

APN0441-E Parsing of the Communications Manager configuration file failed.

Originator: APPN Configuration

Explanation: An error occurred while the configuration file (.CFG) was being
parsed.  A likely cause is that the file is corrupted.

User Response:

o If you have a backup copy of the .CFG file, restore the file. Then retry the
  operation.

o If the problem persists, restart your system and try the operation again.


ΓòÉΓòÉΓòÉ 4.4.25. APN0444 ΓòÉΓòÉΓòÉ

APN0444-E Parsing of the SNA configuration file failed.

Originator: APPN Configuration

Explanation: An error occurred while the SNA configuration file (.CF2) was
being parsed.  A likely cause is that the file is corrupted. This message
should be preceded in the error log by other, more specific messages describing
the error.

User Response: Examine the other entries in the log file for more information
about the error.  Restore the file from a backup if one exists. Or, if a valid
node definitions file (.NDF) exists, recreate the .CF2 file by running the
verification utility CMVERIFY on the .NDF file.  Then retry the operation.


ΓòÉΓòÉΓòÉ 4.4.26. APN0447 ΓòÉΓòÉΓòÉ

APN0447-E Parsing of the security information file failed.

Originator: APPN Configuration

Explanation: An error occurred while the security information file (.SEC) was
being parsed.  A likely cause is that the file is corrupted. This message
should be preceded in the error log by other, more specific messages describing
the error.

User Response: Examine the other entries in the log file for more information
about the error. Restore the file from a backup, or use one of the file
restoration utilities.  Then retry the operation.


ΓòÉΓòÉΓòÉ 4.4.27. APN0453 ΓòÉΓòÉΓòÉ

APN0453-E Update of the node definitions file failed.

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Likely
causes are that there is not enough storage on the disk to hold the file, or
that the file is locked by another process.

User Response: Free any unused disk space (by moving or erasing unused files),
or end the other process that is using the file, and retry the operation.


ΓòÉΓòÉΓòÉ 4.4.28. APN0456 ΓòÉΓòÉΓòÉ

APN0456-E Update of the SNA configuration file failed.

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Likely
causes are that there is not enough storage on the disk to hold the file, or
that the file is locked by another process.

User Response: Free any unused disk space (by moving or erasing unused files),
or end the other process that is using the file, and retry the operation.


ΓòÉΓòÉΓòÉ 4.4.29. APN0457 ΓòÉΓòÉΓòÉ

APN0457-E The configuration is keylock secured, and the specified keylock value
does not match the keylock values defined in the Communications Manager
configuration file.  The SNA configuration file (.CF2) cannot be updated and
the active configuration cannot be changed.

Originator: APPN Configuration

Explanation: The Communications Manager configuration is keylock secured.  No
updates are allowed to the Communications Manager configuration file (.CFG),
the SNA configuration file (.CF2), or the active configuration.

User Response: To update the SNA configuration file and the active
configuration, do one of the following:

o Open the configuration's keylock and verify the configuration again.

o Verify the configuration again, specifying either the configuration's master
  key or its service key.


ΓòÉΓòÉΓòÉ 4.4.30. APN0458 ΓòÉΓòÉΓòÉ

APN0458-E Communications Manager is not active.  The SNA active configuration
cannot be updated.

Originator: APPN Configuration

Explanation: The active SNA configuration was to be updated with the new
configuration if the configuration verified successfully.  The configuration
utility could not complete this request because Communications Manager support
is not active; therefore, there is no active configuration to update.  The
configuration utility continues processing and tries to update the SNA
configuration file with the new configuration.

User Response: If the SNA configuration file is successfully updated, then
everything is fine.  The next time you start Communications Manager it will
pick up the configuration updates from the SNA configuration file.


ΓòÉΓòÉΓòÉ 4.5. APN0459 through APN0491 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.5.1. APN0459 ΓòÉΓòÉΓòÉ

APN0459-E The SNA communications support (APPC and APPN) is not active. The
active SNA configuration cannot be updated.

Originator: APPN Configuration

Explanation: The active SNA configuration was to be updated with the new
configuration once the configuration verified successfully.  The configuration
utility could not complete the request because the SNA support is not active;
therefore, there is no active configuration to update.  The configuration
utility continues processing and tries to update the SNA configuration file
with the new configuration.

User Response: To use the new configuration, stop Communications Manager and
then restart it; this reactivates the SNA support.  When the SNA support is
reactivated, it will pick up the configuration updates from the SNA
configuration file.


ΓòÉΓòÉΓòÉ 4.5.2. APN0460 ΓòÉΓòÉΓòÉ

APN0460-E The specified configuration file name does not match the
active/current configuration file name.  The active SNA configuration cannot be
updated.

Originator: APPN Configuration

Explanation: The active SNA configuration was to be updated with the new
configuration once the configuration verified successfully.  The configuration
utility could not complete the request because the configuration being verified
is not the active configuration.  Configurations are identified by their file
names. Therefore, an SNA configuration file that is different from the SNA
configuration file is used to start Communications Manager.  The configuration
utility continues processing and tries to update the SNA configuration file
with the new configuration.

User Response: To use the new configuration, stop Communications Manager and
then restart it using the correct file name so the SNA support will be
reactivated.  When SNA support is restarted, it will pick up the configuration
updates from the specified SNA configuration file.


ΓòÉΓòÉΓòÉ 4.5.3. APN0461 ΓòÉΓòÉΓòÉ

APN0461-E DosLoadModule of APPC.DLL failed.  DosLoadModule return code = rc(5).
The SNA active configuration cannot be updated.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: The specified OS/2 function failed.  The active configuration
could not be dynamically updated.

User Response: Retry the operation.  The problem could have been caused by a
temporary lack of OS/2 resources. If the problem continues, note the time,
date, and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.4. APN0462 ΓòÉΓòÉΓòÉ

APN0462-E DosGetProcAddr of the APPC entry point failed.  DosGetProcAddr return
code = rc(5).  The SNA active configuration cannot be updated.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: The specified OS/2 function failed.  The active configuration
could not be dynamically updated.

User Response: Retry the operation.  The problem could have been caused by a
temporary lack of OS/2 resources. If the problem continues, note the time,
date, and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.5. APN0463 ΓòÉΓòÉΓòÉ

APN0463-E DosLoadModule of CPIC.DLL failed.  DosLoadModule return code = rc(5).
The CPI-C side information definitions in the SNA active configuration cannot
be updated.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: The specified OS/2 function failed.  The active configuration
could not be dynamically updated.

User Response: Retry the operation.  The problem could have been caused by a
temporary lack of OS/2 resources. If the problem continues, note the time,
date, and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.6. APN0464 ΓòÉΓòÉΓòÉ

APN0464-E DosGetProcAddr of the CPI-C entry point failed.  DosGetProcAddr
return code = rc(5).  The CPI-C side information definitions in the SNA active
configuration cannot be updated.

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: The specified OS/2 function failed.  The active configuration
could not be dynamically updated.

User Response: Retry the operation.  The problem could have been caused by a
temporary lack of OS/2 resources. If the problem continues, note the time,
date, and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.7. APN0468 ΓòÉΓòÉΓòÉ

APN0468-E DosWrite failed for the security information file (.SEC).  DosWrite
return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Assume that
the contents of the file are no longer valid. The most probable cause of the
error is there is not enough storage on the disk to hold the file.

User Response: Free any unused disk space (by moving or erasing unused files)
and retry the operation. If the problem continues, note the time, date and
identification number of this message, along with any return code.  Then
contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.8. APN0469 ΓòÉΓòÉΓòÉ

APN0469-E DosWrite failed for the node definitions file (.NDF).  DosWrite
return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while updating the specified file.  Assume that
the contents of the file are no longer valid. The most probable cause of the
error is there is not enough storage on the disk to hold the file.

User Response: Free any unused disk space (by moving or erasing unused files)
and retry the operation. If the problem continues, note the time, date and
identification number of this message, along with any return code.  Then
contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.9. APN0470 ΓòÉΓòÉΓòÉ

APN0470-E DosAllocSeg for the keyword table failed.  DosAllocSeg return code =
rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: A memory allocation error occurred.  The probable cause of return
code 8 is that OS/2 does not have enough free memory to satisfy the request.

User Response: Retry the operation (OS/2 memory shortages are usually
temporary).  If the error recurs, try to free some memory by stopping some
active OS/2 processes or by instructing the processes to free any unused
memory.  Then retry the operation. If the problem continues, note the time,
date and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.10. APN0471 ΓòÉΓòÉΓòÉ

APN0471-E DosSubSet for the keyword table failed.  DosSubSet return code =
rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: A memory allocation error occurred.  The probable cause of return
code 8 is that OS/2 does not have enough free memory to satisfy the request.

User Response: Retry the operation (OS/2 memory shortages are usually
temporary).  If the error recurs, try to free some memory by stopping some
active OS/2 processes or by instructing the processes to free any unused
memory.  Then retry the operation. If the problem continues, note the time,
date and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.11. APN0472 ΓòÉΓòÉΓòÉ

APN0472-E The keyword name 'name(255)' in the configuration control file (.CTL)
is too long.  Keyword names cannot be longer than 32 characters.

where
name(255)       = keyword name

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.12. APN0473 ΓòÉΓòÉΓòÉ

APN0473-E The delimiter definition in the configuration control file (.CTL) is
incorrect.  It must define 7 delimiters (each delimiter is a 1-byte character).

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.13. APN0474 ΓòÉΓòÉΓòÉ

APN0474-E The delimiter definition in the configuration control file (.CTL) is
incorrect.  The character 'char(1)' cannot be used as a delimiter.

where
char(1)         = delimiter character

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.14. APN0475 ΓòÉΓòÉΓòÉ

APN0475-E The delimiter definition in the configuration control file (.CTL) is
incorrect.  The character 'char(1)' is used to define more than one delimiter.

where
char(1)         = delimiter character

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.15. APN0476 ΓòÉΓòÉΓòÉ

APN0476-E The keyword name 'name(32)' in the configuration control file (.CTL)
is not valid.  It contains ASCII characters that are not graphical or are
defined as delimiters.

where
name(32)        = keyword name

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.16. APN0477 ΓòÉΓòÉΓòÉ

APN0477-E The keyword name 'name(32)' in the configuration control file (.CTL)
is not valid.  Keyword names cannot start with a digit (0-9).

where
name(32)        = keyword name

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.17. APN0478 ΓòÉΓòÉΓòÉ

APN0478-E The internal ID for the keyword 'name(32)' in the configuration
control file (.CTL) is not valid.

where
name(32)        = keyword name

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.18. APN0479 ΓòÉΓòÉΓòÉ

APN0479-E The configuration control file (.CTL) is not valid.  More than one
keyword is defined using the same internal ID (ID(5)).

where
ID(5)           = internal ID

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.19. APN0480 ΓòÉΓòÉΓòÉ

APN0480-E DosSubAlloc for a keyword entry failed.  DosSubAlloc return code =
rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: A memory allocation error occurred.  The probable cause of return
code 8 is that OS/2 does not have enough free memory to satisfy the request.

User Response: Retry the operation (OS/2 memory shortages are usually
temporary).  If the error recurs, try to free some memory by stopping some
active OS/2 processes or by instructing the processes to free any unused
memory.  Then retry the operation. If the problem continues, note the time,
date and identification number of this message, along with any return code.
Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.20. APN0481 ΓòÉΓòÉΓòÉ

APN0481-E The configuration control file (.CTL) is not valid.  The keyword
'name(32)' is defined more than once.

where
name(32)        = keyword name

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains an incorrect
keyword or delimiter definition.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.21. APN0482 ΓòÉΓòÉΓòÉ

APN0482-E The configuration control file (.CTL) is not valid.  The keyword
associated with the internal ID ID(5) is not defined.

where
ID(5)           = internal ID

Originator: APPN Configuration

Explanation: The configuration control file (.CTL) contains a keyword or
delimiter definition that is not valid.

User Response: Edit the configuration control file (the default is APPNV.CTL),
correct the keyword and/or delimiter definitions, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.22. APN0483 ΓòÉΓòÉΓòÉ

APN0483-E DosRead failed for the SNA configuration file (.CF2).  DosRead return
code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while reading the specified file.

User Response: Retry the operation.  If the error recurs, try to correct the
problem indicated by the return code, and retry the operation.  You may have to
restore the file from a backup copy or by using one of the file restoration
utilities. See the detailed description of the message for information about
the file restoration utilities and their possible side effects. If the problem
continues, note the time, date and identification number of this message, along
with any return code.  Then contact your service coordinator.


ΓòÉΓòÉΓòÉ 4.5.23. APN0484 ΓòÉΓòÉΓòÉ

APN0484-E The required parameter 'name(32)' is not specified.

where
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.5.24. APN0485 ΓòÉΓòÉΓòÉ

APN0485-W The parameter 'name(32)' cannot be specified.  This parameter is not
allowed when the value of the parameter 'name(32)' is 'value(32)'.  The
parameter 'name(32)' is ignored.

where
name(32)        = parameter name
name(32)        = parameter name
value(32)       = parameter value

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.5.25. APN0486 ΓòÉΓòÉΓòÉ

APN0486-E The required subparameter 'name(32)' for parameter 'name(32)' is not
specified.

where
name(32)        = subparameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.5.26. APN0487 ΓòÉΓòÉΓòÉ

APN0487-W The value 'value(32)' is not allowed for the parameter 'name(32)'
when the value of the parameter 'name(32)' is not 'value(32)'.  The value of
the parameter 'name(32)' is set to 'value(32)'.

where
name(32)        = parameter name
value(32)       = parameter value
name(32)        = parameter name
value(32)       = parameter value
value(32)       = parameter value

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.5.27. APN0488 ΓòÉΓòÉΓòÉ

APN0488-E The required parameter 'name(32)' is not specified.  This parameter
is required when the value of the parameter 'name(32)' is 'value(32)'.

where
name(32)        = parameter name
name(32)        = parameter name
value(32)       = parameter value

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.5.28. APN0489 ΓòÉΓòÉΓòÉ

APN0489-E The required parameter 'name(32)' is not specified.  This parameter
is required when the value of the parameter 'name(32)' is not 'value(32)'.

where
name(32)        = parameter name
name(32)        = parameter name
value(32)       = parameter value

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.5.29. APN0490 ΓòÉΓòÉΓòÉ

APN0490-E The parameters 'name(32)' and 'name(32)' cannot be specified on the
same command.

where
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.5.30. APN0491 ΓòÉΓòÉΓòÉ

APN0491-E The parameter 'name(32)' cannot be specified.  This parameter is not
allowed when the value of the parameter 'name(32)' is 'value(32)'.

where
name(32)        = parameter name
name(32)        = parameter name
value(32)       = parameter value

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6. APN0492 through APN0522 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.6.1. APN0492 ΓòÉΓòÉΓòÉ

APN0492-E The parameter 'name(32)' cannot be specified.  This parameter is not
allowed when the value of the parameter 'name(32)' is not 'value(32)'.

where
name(32)        = parameter name
name(32)        = parameter name
value(32)       = parameter value

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.2. APN0493 ΓòÉΓòÉΓòÉ

APN0493-W The value 'value(32)' is not allowed for the parameter 'name(32)'
when the value of the parameter 'name(32)' is 'value(32)'.  The value of the
parameter 'name(32)' is set to 'value(32)'.

where
name(32)        = parameter name
value(32)       = parameter value
name(32)        = parameter name
value(32)       = parameter value
value(32)       = parameter value

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.6.3. APN0494 ΓòÉΓòÉΓòÉ

APN0494-W The logical link 'name(8)' is defined as a limited resource with
CP-CP sessions. If CP-CP sessions are activated using this logical link, the
link is never automatically deactivated because the CP-CP sessions will always
be active.

where
name(8)         = link name

Originator: APPN Configuration

Explanation: The logical link definition specifies that the link is a limited
resource and that CP-CP sessions are to be used. The two settings are
inconsistent as CP-CP sessions will not be automatically deactivated, the
specification of limited resource will be ignored for this link.

User Response: If the link should be defined as a limited resource then CP-CP
sessions should be set to NO.  If CP-CP sessions are required then limited
resources should be set to NO.  Note that if limited resource is set to
USE_ADAPTER_DEFINITION then the link is considered a limited resource if the
associated adapter specifies that unused links should be freed.


ΓòÉΓòÉΓòÉ 4.6.4. APN0496 ΓòÉΓòÉΓòÉ

APN0496-W The value for the parameter 'name(32)' is not valid.  The
IBM-supplied class of service definitions are defined by the SNA communications
support and cannot be defined in the node definitions file (.NDF).  This
definition is ignored.

where
name(32)        = parameter name

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.6.5. APN0497 ΓòÉΓòÉΓòÉ

APN0497-E The combination of values for subparameter 'name(32)' of parameter
'name(32)' is not valid.

where
name(32)        = subparameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.6. APN0498 ΓòÉΓòÉΓòÉ

APN0498-W The value for the parameter 'name(32)' is not valid.  The
IBM-supplied CPSVCMG mode definition is defined by the SNA communications
support and cannot be defined in the node definitions file (.NDF).  This
definition is ignored.

where
name(32)        = parameter name

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.6.7. APN0499 ΓòÉΓòÉΓòÉ

APN0499-E The value of the parameter 'name(32)' must be greater than or equal
to the value of the parameter 'name(32)'.

where
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.8. APN0500 ΓòÉΓòÉΓòÉ

APN0500-E The combination of values for the parameters 'name(32)' and
'name(32)' is not valid when the value of the parameter 'name(32)' is
'name(32)'.

where
name(32)        = parameter name
name(32)        = parameter name
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.9. APN0501 ΓòÉΓòÉΓòÉ

APN0501-E The value for the parameter 'name(32)' is not valid.

where
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.10. APN0502 ΓòÉΓòÉΓòÉ

APN0502-E One of the parameters 'name(32)' or 'name(32)' must be specified.

where
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.11. APN0503 ΓòÉΓòÉΓòÉ

APN0503-E The value for the parameter 'name(32)' is incorrect.  The session
limits for the CPSVCMG mode cannot be changed.

where
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.12. APN0504 ΓòÉΓòÉΓòÉ

APN0504-E The value of the parameter 'name(32)' must be greater than or equal
to the sum of the values for the parameters 'name(32)' and 'name(32)'.

where
name(32)        = parameter name
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.13. APN0505 ΓòÉΓòÉΓòÉ

APN0505-E The required parameter 'name(32)' is not specified.  This parameter
is required when the value of the parameter 'name(32)' is greater than 0.

where
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.14. APN0506 ΓòÉΓòÉΓòÉ

APN0506-W The parameter 'name(32)' cannot be specified.  This parameter is not
allowed when the value of the parameter 'name(32)' is not equal to 0.  The
parameter 'name(32)' is ignored.

where
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.6.15. APN0507 ΓòÉΓòÉΓòÉ

APN0507-W The parameter 'name(32)' cannot be specified.  This parameter is not
allowed when the value of the parameter 'name(32)' is equal to 0.  The
parameter 'name(32)' is ignored.

where
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: A command in the node definitions file (.NDF) contains parameter
values that are inconsistent with other parameter values.  The problem is not
severe enough to terminate processing of the node definitions file.  The
configuration utilities either ignore the parameters or assume correct values
for them.

User Response: Each syntax error generates two messages.  The first message
(APN0405) identifies the line or command in the .NDF file where the error was
found.  The second message identifies the problem and what assumptions the
configuration utilities used to correct it. If the assumptions are valid, and
no other errors occurred, you need not take further action.  If the assumptions
are not valid for your configuration, then edit the command in the .NDF file,
correct the syntax error, and retry the operation.


ΓòÉΓòÉΓòÉ 4.6.16. APN0508 ΓòÉΓòÉΓòÉ

APN0508-E The required parameter 'name(32)' is not specified.  This parameter
is required when the value of the parameter 'name(32)' is equal to 0 and the
value of the parameter 'name(32)' is not 'SNASVCMG'.

where
name(32)        = parameter name
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.17. APN0509 ΓòÉΓòÉΓòÉ

APN0509-E The combination of values for the parameters 'name(32)', 'name(32)',
and 'name(32)' are not valid.  The values of these parameters are restricted to
(2,1,1), (1,0,1), or (0,0,0) respectively, when the value of the parameter
'name(32)' is 'SNASVCMG'.

where
name(32)        = parameter name
name(32)        = parameter name
name(32)        = parameter name
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.18. APN0510 ΓòÉΓòÉΓòÉ

APN0510-E Incorrect value 'name(8)' specified.  User-defined link names cannot
begin with '@'.  The Communications Manager uses '@' to identify
dynamically-created logical links.

where
name(8)         = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.19. APN0511 ΓòÉΓòÉΓòÉ

APN0511-E Incorrect value 'name(8)' specified.  User-defined partner LU aliases
cannot begin with '@'.  The Communications Manager uses '@' to identify
dynamically-created partner LUs.

where
name(8)         = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.20. APN0512 ΓòÉΓòÉΓòÉ

APN0512-E Internal error.  Parsing stack overflow.

Originator: APPN Configuration

Explanation: An internal processing/program error occurred.

User Response: Retry the operation.  If the problem continues, note the time,
date, and identification number of this message.  Then contact your service
coordinator.


ΓòÉΓòÉΓòÉ 4.6.21. APN0513 ΓòÉΓòÉΓòÉ

APN0513-E Unexpected keyword: 'name(32)'.

where
name(32)        = keyword name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.22. APN0514 ΓòÉΓòÉΓòÉ

APN0514-E Unexpected delimiter: 'char(1)'.

where
char(1)         = delimiter character

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.23. APN0515 ΓòÉΓòÉΓòÉ

APN0515-E Parsing of the node definitions file (.NDF) ended immediately because
of a processing error.

Originator: APPN Configuration

Explanation: An unrecoverable error was encountered while parsing the commands
in the node definitions (.NDF) file. This message is preceded by another
message which provides a better description of the error.  The messages to
expect are:

o APN0524

o APN0525

o APN0526

o APN0527

o APN0528

User Response: Read the description of the previous message to determine the
exact cause of the error, and follow the recommended responses.


ΓòÉΓòÉΓòÉ 4.6.24. APN0516 ΓòÉΓòÉΓòÉ

APN0516-E Unexpected end-of-file.  Probable causes are a comment or
configuration command have not been ended in the node definitions file (.NDF).

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.25. APN0517 ΓòÉΓòÉΓòÉ

APN0517-E Unexpected string value: 'name(32)'.

where
name(32)        = parameter name

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.26. APN0518 ΓòÉΓòÉΓòÉ

APN0518-E Unexpected number: num(10).

where
num(10)         = number

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.27. APN0519 ΓòÉΓòÉΓòÉ

APN0519-E Unexpected hex number: X'name(32)'.

where
name(32)        = hex value

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.28. APN0520 ΓòÉΓòÉΓòÉ

APN0520-E Hex number either does not end with a quote (char(1)) or contains hex
digits that are not valid.

where
char(1)         = quote character

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.29. APN0521 ΓòÉΓòÉΓòÉ

APN0521-E Comment not ended and end-of-file encountered.

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.6.30. APN0522 ΓòÉΓòÉΓòÉ

APN0522-E Unexpected/unknown character or unexpected end-of-file.

Originator: APPN Configuration

Explanation: There is a syntax error in the node definitions (.NDF) file.

User Response: Each syntax error generates two messages.  The first message
(APN0403 or APN0404) identifies the line or command in the .NDF file where the
error was found.  The second message identifies the problem.  Edit the
indicated line or command in the .NDF file, correct the syntax error, and retry
the operation.


ΓòÉΓòÉΓòÉ 4.7. APN0523 through APN0552 ΓòÉΓòÉΓòÉ

Messages are divided into subcategories for ease of location in the Contents.
To view a message, press Ctrl+C to return to the Contents and then select an
individual message.

Note:  In the Contents, you can use the + or - keys to locate individual
messages.


ΓòÉΓòÉΓòÉ 4.7.1. APN0523 ΓòÉΓòÉΓòÉ

APN0523-E DosRead failed for the security information file (.SEC).  DosRead
return code = rc(5).

where
rc(5)           = return code

Originator: APPN Configuration

Explanation: An error occurred while reading the specified file.

User Response: Retry the operation.  If the error recurs, try to correct the
problem indicated by the return code, and retry the operation.  You may have to
restore the file from a backup copy or by using one of the file restoration
utilities. See the detailed description of the message for information about
the file restoration utilities and their possible side effects. If the problem
continues, note the time, date and identification number of