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

OS/2 Help File | 1994-02-27 | 777.5 KB | 30,437 lines

ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ

Second Edition, July 1993

This is a major revision of, and obsoletes, SC31-6173-00.

This edition applies to Version 1.1 of IBM Communications Manager/2 and to all
subsequent releases and modifications until otherwise indicated in new editions
or technical newsletters. Make sure you are using the correct edition for the
level of the product.

Order publications through your IBM representative or the IBM branch office
serving your locality.  Publications are not stocked at the address below.

IBM welcomes your comments.  A form for readers' comments may be provided at
the back of this publication, or you may address your comments to the following
address:

International Business Machines Corporation
Department E15
P.O. Box 12195
Research Triangle Park, North Carolina
27709-9990

When you send information to IBM, you grant IBM a nonexclusive right to use or
distribute the information in any way it believes appropriate without incurring
any obligation to you.


ΓòÉΓòÉΓòÉ 2. Notices ΓòÉΓòÉΓòÉ

References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only that IBM product, program, or service may be used.
Any functionally equivalent product, program, or service that does not infringe
any of the intellectual property rights of IBM may be used instead of the IBM
product, program, or service. The evaluation and verification of operation in
conjunction with other products, except those expressly designated by IBM, are
the responsibility of the user.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Commercial Relations
IBM Corporation
Purchase, New York, 10577, U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,
contact:

IBM World Trade Asia Corporation Commercial Relations
IBM Kamiya-cho Building, 4-3-9 Toranomon, Minato-ku
Tokyo, Japan

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement.

This document is not intended for production use and is furnished as is without
any warranty of any kind, and all warranties are hereby disclaimed including
the warranties of merchantability and fitness for a particular purpose.

The following terms, denoted by an asterisk (*) in this publication, are
trademarks of the IBM Corporation in the United States and other countries:

Advanced Peer-to-Peer Networking        Operating System/2
Application System/400                  OS/2
APPN                                    OS/400
AS/400                                  Personal System/2
CICS                                    Presentation Manager
FFST/2                                  PS/2
First Failure Support Technology/2      SAA
IBM                                     Systems Application Architecture
Macro Assembler/2                       System/370
NetView                                 VTAM

The following terms, denoted by an double asterisk (**) in this publication,
are trademarks of other companies:

Intel                                   Intel Corporation
Micro Focus                             Micro Focus Limited
Microsoft                               Microsoft Corporation
Windows                                 Microsoft Corporation


ΓòÉΓòÉΓòÉ 3. 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 supports a single-user and a client-server functional
hierarchy as part of this platform. A Communications Manager server contains
most of the communication capabilities, maintains the communication
connections, and processes Communications Manager client requests.
Communications Manager users can choose from among a variety of remote
connectivity options.

This book provides detailed descriptions of the Advanced Peer-to-Peer
Networking* (APPN*) configuration and subsystem management verbs. These verbs
allow for configuration and management of an APPN node. APPN is IBM's Systems
Network Architecture (SNA) for peer-to-peer, decentralized networks. OS/2
workstations that are running the SNA logical unit (LU) type 6.2 protocol use
Advanced Program-to-Program Communications (APPC) to run application programs.
In a Communications Manager environment, the underlying network to which the
computers are connected uses the capability provided by APPN for communication.

It is assumed that you are using OS/2 Version 1.30.1 with corrective service
diskette (CSD) 5200 (1.30.2) or OS/2 Version 2.0 or higher as your base
operating system. The term OS/2, as it is 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 with CSD 5200 (1.30.2)
or higher or OS/2 Version 2.0, the Communications Manager documentation still
applies.

Note:  You can use the double-byte character set (DBCS) version with OS/2
Version 2.0 or later.

ASCII refers to PC single-byte code in this book.  ASCII should be considered
as JISCII in Japan.

The base operating system for users of DOS systems should be Version 3.0 or
higher.

The term "Windows", as it is used in this book, refers to Microsoft** Windows**
version 3.0 and higher. Refer to Application Programming Guide for general
information about programming considerations for Communications Manager
communications clients.


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

The following conventions are used in this book.


ΓòÉΓòÉΓòÉ 3.1.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 upper-  Γöé
Γöé         Γöé case or lowercase.                                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "Example type" Γöé Example type indicates information that the user is instructed to type at a   Γöé
Γöé         Γöé command prompt or in a window.                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 3.1.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   Γöé
Γöé         Γöé assembly 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).         Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 3.1.3. Syntax Diagrams ΓòÉΓòÉΓòÉ

Throughout this library conceptual diagrams are used to illustrate the
programming syntax. The following list tells you how to interpret the syntax
diagrams:

o Read the syntax diagrams from left to right, from top to bottom, following
  the path of the line.

o Items shown on the main path of the syntax statement are required syntax.

    >>ΓöÇΓöÇKEYWORDΓöÇΓöÇkeyword_nameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

o Items shown on branches below the main path are optional syntax.

    >>ΓöÇΓöÇKEYWORDΓöÇΓöÇkeyword_nameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                  ΓööΓöÇITEM1ΓöÇΓöÿ  ΓööΓöÇITEM2ΓöÇΓöÿ

o Items shown on branches above the main path are default syntax.

                  ΓöîΓöÇITEM1ΓöÇΓöÉ
    >>ΓöÇΓöÇKEYWORDΓöÇΓöÇkeyword_nameΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

o Items appearing in a stack indicate that only one of the items may be
  specified.  When one of the items in a stack appears on the main path, you
  must choose one of the items.

  For example, in the following syntax diagram, you must choose either ITEM1 or
  ITEM2.  ITEM3 and ITEM4 both appear below the main path, so neither of them
  is required.

    >>ΓöÇΓöÇKEYWORDΓöÇΓöÇkeyword_nameΓöÇΓöÇΓö¼ΓöÇITEM1ΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                  ΓööΓöÇITEM2ΓöÇΓöÿ  Γö£ΓöÇITEM3ΓöÇΓöñ
                       ΓööΓöÇITEM4ΓöÇΓöÿ

o A repeat arrow shown above an item or a stack of items indicates that you can
  specify the item multiple times or specify more than one of the items.  A
  character (such as a comma) on the repeat arrow line indicates that the items
  must be separated by that character.

  For example, in the following syntax diagram, you can specify both ITEM1 and
  ITEM2, but you must use a comma to separate the choices in your programming
  syntax.

                  ΓöîΓöÇ,ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                       Γöé
    >>ΓöÇΓöÇKEYWORDΓöÇΓöÇkeyword_nameΓöÇΓöÇΓöÇΓö¼ΓöÇITEM1ΓöÇΓö¼Γö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                  ΓööΓöÇITEM2ΓöÇΓöÿ

o In some cases, when an item has additional items associated with it, an
  additional syntax diagram is shown that represents the full syntax of that
  item.  For example, in the following syntax diagram, additional information
  that can be specified for ITEM1 appears in the "ITEM1" Variables syntax
  diagram.

    >>ΓöÇΓöÇKEYWORDΓöÇΓöÇkeyword_nameΓöÇΓöÇΓöñ ITEM1 Γö£ΓöÇΓöÇITEM2ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
    ITEM1 VARIABLES:
    Γö£ΓöÇΓöÇΓö¼ΓöÇvariable1ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
      Γö£ΓöÇvariable2ΓöÇΓöñ
      ΓööΓöÇvariable3ΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 3.2. 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, displaying, 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.


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

The Information and Planning Guide has a description of the complete
Communications Library. The online Overview contains a complete description of
both the Communications Manager library and related publications.


ΓòÉΓòÉΓòÉ 4. Introduction ΓòÉΓòÉΓòÉ

;p.


ΓòÉΓòÉΓòÉ 4.1. Description ΓòÉΓòÉΓòÉ

This book provides a complete description of the display, subsystem management,
configuration, and management services (MS) verbs you can use to establish and
maintain node definitions in Communications Manager APPC applications. Also
included in this book are descriptions for the return codes associated with
these verbs.


ΓòÉΓòÉΓòÉ 4.2. Overview of the Verbs in This Book ΓòÉΓòÉΓòÉ

The verb interface described in this book allows your programs to perform most
of the configuration, management, subsystem management functions, and node
definition functions associated with a Communications Manager network
environment. This section provides you with an overview for each of these
functions and the associated verbs.


ΓòÉΓòÉΓòÉ 4.2.1. Display Verbs ΓòÉΓòÉΓòÉ

Communications Manager supports a set of subsystem management verbs, providing
display verbs that let you view available SNA information.

Verb      Description
DISPLAY   Returns general configuration information and current operating
          values for your SNA node.
DISPLAY_APPN Returns Advanced Peer-to-Peer Networking* (APPN*) configuration
          information and current operating values for your node.


ΓòÉΓòÉΓòÉ 4.2.2. Subsystem Management Verbs ΓòÉΓòÉΓòÉ

Communications Manager supports a set of subsystem management verbs, providing
an authorized program with a method for managing sessions, links, and the APPC
attach manager.

Verb      Description
ACTIVATE_DLC Activates a specified data link control.
ACTIVATE_LOGICAL_LINKS Activates a specific logical link, or all logical links
          configured as automatically activated.
CNOS      Sets either a positive session limit or resets a session limit to 0
          for a given pair of logical units (LUs) and a given transmission
          service mode.
DEACTIVATE_CONVERSATION_GROUP Deactivates a session identified by a
          conversation group ID.
DEACTIVATE_DLC Deactivates a specified DLC adapter.
DEACTIVATE_LOGICAL_LINK Deactivates a specified SNA logical link.
DEACTIVATE_SESSION Deactivates a session identified by an internal session ID
          or deactivates all the sessions for a given LU pair and a given
          transmission service mode name.
REJECT_INCOMING_CALLS Indicates to the switched network that you no longer want
          to receive incoming calls.
ACCEPT_INCOMING_CALLS Indicates to the switched network that you want to accept
          or "listen" for incoming calls over a switched network.
START_AM  Starts the APPC attach manager.
STOP_AM   Stops the APPC attach manager.


ΓòÉΓòÉΓòÉ 4.2.3. Configuration Verbs ΓòÉΓòÉΓòÉ

Communications Manager supports a set of configuration verbs, providing an
authorized program with a method for configuring resources such as LUs and TPs.

Verb      Description
DEFINE_APPC_ATTACH_ROUTE Defines communications client destination of attaches
          for the specified LU aliases.
DEFINE_CLIENT_DEP_APPC_ACCESS Defines communications client machines access to
          dependent LU 6.2 resources.
DEFINE_CLIENT_INDEP_APPC_ACCESS Defines communications client machine access to
          independent LU 6.2 resources.
DEFINE_CLIENT_LUA_ACCESS Defines communications client machine access to LUA
          resources.
DEFINE_CPIC_SIDE_INFO Creates a side information entry that the OS/2 CPI
          Communications support uses when initialing conversations.
DEFINE_COS Defines or replaces a class-of-service (COS) definition.
DEFINE_DEFAULTS Defines system default values for functions provided by
          Communications Manager.
DEFINE_DEFAULT_SOC Defines or replaces a default sphere of control for an MS
          category.
DEFINE_EXPLICIT_SOC Defines an explicit sphere of control, or adds nodes to an
          existing explicit sphere of control, for an MS category.
DEFINE_GATEWAY_HOST Defines all pool classes for the host.
DEFINE_GATEWAY_WORKSTATION Defines which combination of LUs provided to a
          workstation when it establishes a link.
DEFINE_LOCAL_CP Defines the parameters of the local control point (CP) LU.
DEFINE_LOCAL_LU Defines or replaces a local LU.
DEFINE_LOGICAL_LINK Defines or replaces the characteristics of a link to an
          adjacent node.
DEFINE_LUA Defines a new LUA logical unit (LU) type 0,1,2,3 or replaces an
          existing one.
DEFINE_LUA_POOL Enables you to group multiple LUA LUs together into an LUA
          pool.
DEFINE_LU_LU_PASSWORD Defines or replaces the password to be used for LU-LU
          sessions between the specified local LU (including the local control
          point (CP)) and the remote LU (including an adjacent CP).
DEFINE_MODE Defines or replaces the characteristics of a particular mode,
          including the COS to which it maps.
DEFINE_PARTNER_LU Defines or replaces the parameters of a partner LU for LU-LU
          sessions between a specified local LU (including the local CP) and
          the partner LU (including an adjacent CP).
DEFINE_PARTNER_LU_LOCATION Defines or replaces directory information for a
          partner LU.
DEFINE_REMOTE_FP Defines or replaces a remote focal point for the local entry
          point node, for an MS category.
DEFINE_TP Defines Transaction Program information that the APPC attach manager
          uses when processing incoming attaches from LUs.
DEFINE_USER_ID_PASSWORD Defines the user ID and password used for
          conversation-level security. Incoming attaches containing access
          security information must contain a user ID and, if present in the
          attach, a password.
DELETE_COS Requests deletion of a COS definition.
DELETE_DEFAULT_SOC Deletes (disables) the default sphere of control for an MS
          category.
DELETE_EXPLICIT_SOC Deletes nodes from the sphere of control definition for an
          MS category.
DELETE_LOCAL_LU Requests deletion of a local LU definition.
DELETE_LU_LU_PASSWORD Requests deletion of the LU-LU password used between
          sessions.
DELETE_MODE Requests deletion of the mode definition.
DELETE_PARTNER_LU Requests deletion of a partner LU definition.
DELETE_PARTNER_LU_LOCATION Deletes a partner LU entry from the directory
          database.
DELETE_TP Deletes an APPC Transaction Program definition.
DELETE_USER_ID_PASSWORD Deletes a user ID and password used for
          conversation-level security.
REVOKE_REMOTE_FP Revokes the current remote focal point for an MS category.


ΓòÉΓòÉΓòÉ 4.2.3.1. SNA Configuration Verbs ΓòÉΓòÉΓòÉ

The following verbs can be issued only as commands in a SNA node definitions
file (.NDF). They are issued internally by APPC when Communications Manager is
started.

Verb      Description
DEFINE_APPC_ATTACH_ROUTE Enables routing of LU 6.2 attaches when their
          destination is a communications client.
DEFINE_CLIENT_DEP_APPC_ACCESS Defines the communications client destination of
          attaches for the specified LU aliases.
DEFINE_CLIENT_INDEP_APPC_ACCESS Defines communications client machine access to
          independent LU 6.2 resources.
DEFINE_CLIENT_LUA_ACCESS Defines communicaitons client machine access to LUA
          resources.
DEFINE_CONNECTION_NETWORK Defines a node as a member of a connection network,
          simplifying APPN configuration on local area networks.
DEFINE_CPIC_SIDE_INFO Defines side information parameters used by Common
          Programming Interface (CPI Communications) applications.
DEFINE_DEFAULTS Defines system default values, to simplify an SNA node
          definition.
DEFINE_LOCAL_CP Defines the characteristics of the local control point (CP).
DEFINE_LUA_POOL Enables you to group multiple LUA LUs together into an LUA
          pool.


ΓòÉΓòÉΓòÉ 4.2.4. Management Services Verbs ΓòÉΓòÉΓòÉ

Communications Manager supports a set of management services (MS) verbs,
providing an application program with a method for reporting potential problems
to MS focal points available in an SNA network.

Verb      Description
REGISTER_MS_APPLICATION Registers your OS/2* program in the Communications
          Manager MS application routing list so your node will route requested
          MS data to your program. Your program can register itself as an MS
          entry point application or an MS focal point application.
SEND_MDS_MU Sends MS data to another MS application.
TRANSFER_MS_DATA Sends MS data to a management services focal point, and logs
          it in the First Failure Support Technology/2* (FFST/2*) error log.
UNREGISTER_MS_APPLICATION Removes your program from the Communications Manager
          MS application routing list so MS data is no longer routed to it.


ΓòÉΓòÉΓòÉ 4.2.5. Call Examples ΓòÉΓòÉΓòÉ

In any language that supports the OS/2 program, issuing an APPC verb consists
of a sequence like:

PUSH verb-control-block-selector
PUSH verb-control-block-offset
CALL APPC

o In the IBM* Macro Assembler/2* language, issuing an APPC verb from a program
  looks like this:

    EXTRN APPC:FAR

    @PUSHS VCB
    CALL FAR PTR APPC
  where VCB is a verb control block.

o In the C language, issuing an APPC verb from a program looks like this:

    extern void pascal far APPC(ULONG);    /* procedure prototype */

    APPC ((ULONG)vcbptr);
  where vcbptr is a far pointer to a verb control block.

o In the COBOL language, issuing an APPC verb from a program looks like this:

    CALL "__APPC" USING BY REFERENCE CNOS
  where CNOS is an APPC verb structure. Ensure that the entry point name APPC
  in quotes is preceded by 2 underscore characters. This far pointer consists
  of both the selector and offset portions of the address.


ΓòÉΓòÉΓòÉ 4.2.6. DLL Interface ΓòÉΓòÉΓòÉ

The base operating system provides two types of dynamic linking to the dynamic
link module:

o Load-time linking
o Run-time linking

To link to APPC at load time, you must either include the following IMPORTS
statement in the .DEF file when linking your program, or you must link with the
ACS.LIB library at link time.

For all programs using APPC verbs, the statement is:

IMPORTS APPC.APPC

For all programs using common services verbs, the statement is:

IMPORTS ACSSVC.ACSSVC

For programs issuing the DISPLAY verb requesting X.25 physical link
information, or issuing the X.25 CONNECT_PHYSICAL_LINK or
DISCONNECT_PHYSICAL_LINK verbs, the statement is:

IMPORTS ACSSVC.ACSMGT

The ACS.LIB library contains entry-point linkage information about all
Communications Manager API entry points.

Run-time linking provides the ability to conditionally link to a dynamic link
module. With run-time linking, your application issues DosLoadModule and
DosGetProcAddr to obtain linkage to the APPC entry point.

Refer to OS/2 Technical Library for additional information about run-time
linking.

Note:  Although run-time linking is supported by APPC, the capability to unlink
is not supported. Once an application has performed the run-time link to
APPC.DLL, it should not unlink using DosFreeModule.


ΓòÉΓòÉΓòÉ 4.2.7. Stack Size ΓòÉΓòÉΓòÉ

APPC uses the calling application's stack when executing a verb. The
combination of the base operating system and APPC together uses 2560 bytes. You
need additional stack space for your program's own variables. Therefore, the
recommended stack size is at least 4500 bytes. You can specify stack size on
the STACKSIZE statement in the .DEF file used when the program is linked. An
example of the STACKSIZE statement for a .DEF file follows:

STACKSIZE 4500
Specifying STACKSIZE in the .DEF file overrides any stack size specified in the
source code.


ΓòÉΓòÉΓòÉ 4.2.8. Segment Attributes ΓòÉΓòÉΓòÉ

There are two types of data segments used by APPC programs: VCBs and data
buffers.


ΓòÉΓòÉΓòÉ 4.2.8.1. Programming Note ΓòÉΓòÉΓòÉ

The base operating system optimizes performance by executing some subsystems in
the calling application's address space.  This means that incorrect use of
local descriptor table (LDT) selectors by application programs that have not
been fully or correctly debugged may cause improper operation, or perhaps
system failures. Accordingly, application programs should not perform pointer
arithmetic operations that involve changing the LDT selector field of a
pointer.


ΓòÉΓòÉΓòÉ 4.2.8.2. Verb Control Blocks (VCB) ΓòÉΓòÉΓòÉ

The segment used for the verb control block (VCB) must be a read/write data
segment. Your program can either declare the VCB as a variable in your program,
allocate it (using DosAllocSeg), or suballocate it from a larger segment (using
DosSubAlloc). It must be sufficiently large to contain all the fields for the
verb your program is issuing.

An application program should not change any part of the verb control block
after it has been issued until the verb completes. When APPC finishes the
execution of a verb, it copies a complete, modified VCB back onto the original
block. Therefore, if your program declares a verb control block as a variable,
consider declaring it in static storage rather than on the stack of an internal
procedure.

Fill all reserved and unused fields in each VCB with zeros (X'00'). In fact, it
may be more time efficient to set the entire verb control block to zeros before
your program assigns the values to the parameters. Setting reserved fields to
zeros is particularly important; OS/2 programmers experienced with previous
APPC releases will observe that fields that were reserved in earlier releases
have been used for new functions.

Note:  If the VCB is not read/write, or if it is not at least 10 bytes (that
is, large enough to hold the APPC primary and secondary return codes), APPC
cannot access it, and the base operating system abnormally ends the process.
This termination is recognized as a general protection fault, processor
exceptiontrap D.

APPC returns the INVALID_VERB_SEGMENT primary return code when the VCB is too
short or the incorrect type of segment is used.        .


ΓòÉΓòÉΓòÉ 4.2.8.3. Data Buffers ΓòÉΓòÉΓòÉ

If the verb has an associated data buffer (such as the DISPLAY and DISPLAY_APPN
verbs, among others), the segment containing the data buffer must be an
unnamed, shared segment allocated by calling DosAllocSeg with shared indicator
set to 1. That is, you cannot precompile constant data into a segment and send
it directly from that segment. Your program must first copy the constant data
into a shared data segment allocated as previously described.

Multiple data buffers are allowed in the same segment; however, no data buffer
can span multiple segments. For example, APPC does not support chains of
segments allocated by DosAllocHuge. Also, APPC does not support individual
segments (other than the first segment) allocated by DosAllocHuge.

Multiple verb or data buffers can coexist in the same segment, provided the
preceding segment requirements are met.

APPC returns the INVALID_DATA_SEGMENT primary return code when the data buffer
is too short or the incorrect type of segment is used.


ΓòÉΓòÉΓòÉ 4.2.8.3.1. Reusing Data Segments ΓòÉΓòÉΓòÉ

To improve its performance, APPC registers each new data buffer passed to it
using an internal call to DosGiveSeg. It does not free the data segments for an
APPC program until the program's process ends. For example, a loop containing
the following calls will eventually allocate all available memory segments in
the system.

DO FOREVER
    DosAllocSeg (@DataBuffer)
    DISPLAY_APPN (@DataBuffer)
    DosFreeSeg (@DataBuffer)    /* no memory will be freed */
END
Once allocated, use the same data segments again each time your program issues
a verb with associated data buffers.


ΓòÉΓòÉΓòÉ 4.2.9. Presentation Manager Applications ΓòÉΓòÉΓòÉ

OS/2 Presentation Manager* (PM) applications should be designed to return to PM
as quickly as possible. However, many APPC verbs can be issued in situations
where they do not return immediately from APPC to the calling program. PM is
not able to process any requests until a program returns control to PM. In PM
applications that make APPC calls, your program should use a separate thread
for your APPC conversation verbs to avoid lengthy delays in PM when the APPC
verb does not return.

Programs that issue the following verbs may take an extended amount of time to
execute:

ACTIVATE_LOGICAL_LINKS
DISPLAY


ΓòÉΓòÉΓòÉ 4.2.10. OS/2 Critical Sections and Signals ΓòÉΓòÉΓòÉ

Use OS/2 critical sections with care when your program issues APPC verbs. Do
not issue APPC verbs within an OS/2 critical section (that is, do not issue
DosEnterCritSec and then issue APPC verbs without first successfully completing
DosExitCritSec. Similarly, if one thread of a program establishes a critical
section and another thread is within a call to APPC, APPC is suspended until
the critical section is exited.

During processing of an APPC verb, all signals (except numeric co-processor
signals) are delayed until verb completion or until APPC needs to wait for
incoming data. For example, pressing the Ctrl+Break keys ends a TP if APPC is
waiting for data to arrive while processing a [MC_]RECEIVE_AND_WAIT verb. Also,
a DosKillProcess issued from another process is held until APPC completes a
verb it may be processing or needs to wait for incoming data.


ΓòÉΓòÉΓòÉ 4.2.11. APPC ExitList Processing ΓòÉΓòÉΓòÉ

When the first TP in a process is started (with a TP_STARTED or
RECEIVE_ALLOCATE verb), APPC attaches an OS/2 ExitList routine to the TP
process. An ExitList routine is a procedure that is called when an OS/2 process
ends. The ExitList routine that APPC adds involves no work on the part of the
programmer.

This routine does not prevent a application programmer from specifying
additional ExitList routines (using DosExitList). User-written application
ExitList routines should use an invocation order higher than the invocation
order used by the Communications Manager components (X'90' through X'98').

The APPC ExitList routine does the following processing:

 1. It internally issues a TP_ENDED verb with type(SOFT) for each active TP in
    the process.

 2. It frees any data segments it has registered for the process. Data segments
    are registered whenever a program issues an APPC verb specifying a data
    buffer, such as an [MC_]RECEIVE_AND_WAIT or an [MC_]SEND_DATA verb, if APPC
    has not already registered the segment on a previous verb.

 3. If the program was started by the attach manager and it is a "queued" type
    program, the attach manager is informed so it can restart the program if
    any Attaches are queued for the program's TP.

 4. It releases held signals.

 5. It transfers control to the next installed ExitList routine for the
    process.

For a description of the APPC conversation verbs mentioned in this section,
refer to APPC Programming Guide and Reference.


ΓòÉΓòÉΓòÉ 4.3. Compiling and Linking Your APPC Program ΓòÉΓòÉΓòÉ

Save the source files for all the elements of your TPs. Later releases of
Communications Manager may require that the TPs be recompiled and relinked to
use the new functions in those releases.

You can create a program module (an .EXE file) to run on the base operating
system by linking your compiled source files with the LINK utility program
supplied with the base operating system. For more information on how to create
a .EXE file, refer to the programming language reference manual associated with
the language you are using.

The LINK program uses the compiled source files, a list of library files, and
module definition files that contain information about your program. From these
files, the LINK program builds the .EXE file that runs your TP.

Linking Process outlines the process.

Linking Process


ΓòÉΓòÉΓòÉ 4.3.1. Using Communications Manager High-Level Language Header Files ΓòÉΓòÉΓòÉ

To simplify the coding of APPC verbs, the VCB structure for each verb, along
with appropriate parameter constants, is supplied with Communications Manager.
By default, these files are installed in the Network Administrator Diskette.

When installing or reinstalling the header files, choose the API data
structures option from the Additional Features menu. Communications Manager
High-Level Language (HLL) Header Files lists the header files by language and
type of verb.

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé      Communications Manager High-Level Language (HLL) Header Files              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé        Γöé           Γöé SUBSYSTEM MANAGE-  Γöé CONFIGURATION    Γöé           Γöé
Γöé LANGUAGE   Γöé CONVERSATION VERBS Γöé MENT VERBS     Γöé VERBS        Γöé CONSTANTS      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé C       Γöé appc_c.h      Γöé acsmgtc.h      Γöé appccfg.h      Γöé appcdef.h      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé COBOL     Γöé appc_cbl.cbl    Γöé acsmgt.cbl     Γöé appccfg.cbl     Γöé appc_cbl.cbl    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MASM     Γöé appc_a.inc     Γöé           Γöé           Γöé appc_a.inc     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 4.3.1.1. Setting Environment Variables for Communications Manager Header Files ΓòÉΓòÉΓòÉ

For C and Macro Assembler (MASM), add the Communications Manager header file
subdirectory to your INCLUDE environment variable. By default, the
Communications Manager header files are installed in the Network Administrator
Diskette.

For COBOL, either specify the complete path on the COBOL COPY statement, or
move the necessary COBOL header files into the current directory where you are
compiling.


ΓòÉΓòÉΓòÉ 4.3.1.2. Using the Header Files in C Language Programs ΓòÉΓòÉΓòÉ

The C header files that contain verb structures (APPC_C.H, ACSMGTC.H and
APPCCFG.H) each include the constant file APPCDEF.H, if it has not yet been
included.

Including APPN.H will include all of the C header files. Your program can also
specify single header files by defining macro variables consisting of INCL_
concatenated with the file name (without extension) of the file you want to
include; for example,

#define INCL_APPC_C

If you include OS2.H in your program, you should place the include statement
for OS2.H before any APPC include statements. If you do not, you will get five
instances of the following warning message:

warning C4074: non standard extension used - 'benign typedef redefinition'

This is not a problem; it is just saying that certain typedef statements have
been repeated with the same content.


ΓòÉΓòÉΓòÉ 4.4. Communications Manager Keylock ΓòÉΓòÉΓòÉ

All configuration and subsystem management verbs, with the exception of DISPLAY
and DISPLAY_APPN, must specify the proper key (either the master key or the
service key) if the keylock is on. Otherwise, the key field is ignored. If the
key is used, it is better not to hard-code it into a program, but instead to
obtain it from a passed parameter, from a file, or from operator input. For
more information about the keylock feature, see Workstation Installation and
Configuration Guide.

Generally, your program must first issue the DISPLAY verb in order to get
current information about the SNA system. Values such as link_ids and
session_ids are obtained by using this verb.


ΓòÉΓòÉΓòÉ 4.5. Return Codes ΓòÉΓòÉΓòÉ

The configuration, subsystem management, and management services verbs
described in this book have return codes associated with them that supply
information about the success of verb execution or that provide error
information. These codes are listed in the "Returned Parameters" section for
each verb. Return Codes provides a complete description of the return codes.

Error information is provided in a 2-byte primary code that identifies the
error type and a 4-byte secondary code that provides more detailed error
information.


ΓòÉΓòÉΓòÉ 4.6. How To Read Verb Descriptions ΓòÉΓòÉΓòÉ

The DISPLAY Verb, through Management Services Verbs, of this book contain
descriptive listings of the configuration, subsystem management, and MS verbs.
Each listing begins with a description of the verb and a pointer to the VCB
format for the verb in Verb Control Blocks and Hexadecimal Codes.

 Supplied Parameter Syntax

          Provides a conceptual diagram of the parameters supplied with the
          verb.

          Provides a conceptual diagram of the parameters returned by the verb.

          Conventions Used in This Book tells you how to interpret the syntax
          diagrams.

 Parameters

          Provides a detailed description of the parameters and any associated
          parameter values supplied by the program.

          In some cases, you must supply a variable value for a parameter. This
          is indicated by italicized text following the parameter name in the
          syntax diagrams and parameter descriptions. The following list
          explains the conventions for these values:

          o address indicates that a 4-byte OS/2 memory address must be
            supplied. The address is stored in Intel**, byte-reversed format.

          o id indicates that an arbitrary string of hexadecimal bytes of a
            predetermined length must be supplied.

          o n (number) indicates that an integer that is 1, 2, or 4 bytes must
            be supplied. The integer is stored in Intel, byte-reversed format.

          o name indicates that a character string of a predetermined length,
            which probably corresponds with a configured profile or field name
            must be supplied. The name can be in ASCII or EBCDIC, and is
            usually padded on the right with blanks. (See Character Strings for
            more information.)

          In many cases, predetermined values must be supplied for the
          parameter. These values are shown in the syntax diagrams and
          discussed in the parameter descriptions. They are shown in uppercase
          letters following their associated parameters.

 Return Codes

          Provides a detailed description of the parameters and any associated
          parameter values returned to the program. The description includes a
          table showing the primary and secondary return codes associated with
          the verb, and a page reference for each return code where additional
          information can be found.

 Comments

          Many of the verb descriptions also contain a section titled
          "Additional Information". This section provides additional useful
          information about the verb.


ΓòÉΓòÉΓòÉ 4.7. Character Strings ΓòÉΓòÉΓòÉ

Communications Manager makes use of character strings composed of characters
from one of the following character sets:

          o Character set 01134, which is composed of uppercase letters A-Z and
            numerals 0-9.

          o Character set A, which is composed of uppercase letters A-Z,
            numerals 0-9, and three special characters: @, #, and $. The first
            character of the string must be either an uppercase letter or one
            of the three special characters.

          o Character set AE, which is composed of uppercase letters A-Z,
            lowercase letters a-z, numerals 0-9, and four special characters:
            period (.), @, #, and $.

          o Character set 00640, which is composed of uppercase letters A-Z,
            lowercase letters a-z, numerals 0-9, and 20 special characters.

          o Character set GR, which is composed of uppercase letters A-Z,
            lowercase letters a-z, numerals 0-9, and 162 special characters;
            this range of type GR characters represents the hex values
            X'20'-X'FF'.

          The choice of character set depends on the kind of parameter that
          contains the character string. These character sets, along with the
          hexadecimal (hex) codes from ASCII code page 850 (multilingual) and
          EBCDIC code page 500 (international), and graphic representations of
          each character, are provided in Character Sets 01134, A, AE, 00640,
          and GR. See SNA Formats for more information on character sets.


ΓòÉΓòÉΓòÉ 4.8. Program Considerations ΓòÉΓòÉΓòÉ

Two dynamic link library (DLL) files are shipped with Communications Manager to
handle APPC verbs and common services verbs: APPC.DLL and ACSSVC.DLL,
respectively. Multiple application processes and threads can call these DLLs to
issue verbs.

The language interface for APPC verbs is straightforward. Your program fills in
the fields of a block of memory called a VCB. Next, your program calls the APPC
DLL, passing a pointer to the verb control block. When its operation is
complete, APPC returns, having used and then modified the fields in the VCB.
When it gets return parameters back, your program can read the returned
parameters from the VCB.

The language interface for common services verbs is similar, except that a
different DLL (ACSSVC.DLL) is called.


ΓòÉΓòÉΓòÉ 4.8.1. Procedure Entry Points ΓòÉΓòÉΓòÉ

The entry points available for using APPC are:

          Entry Point    Description
          APPC           This entry point in APPC.DLL is used in any language
                         for control, conversation, subsystem management, and
                         configuration verbs.
          ACSSVC         This entry point in ACSSVC.DLL is used in any language
                         for common services verbs.
          ACSMGT         This entry point in ACSSVC.DLL is used in any language
                         to obtain X.25 Physical Link Information, using the
                         DISPLAY verb, and for the X.25 CONNECT_PHYSICAL_LINK
                         and DISCONNECT_PHYSICAL_LINK verbs.

          The default installed locations for the two required dynamic link
          modules are:

          APPC.DLL       d:\CMLIB\DLL
          ACSSVC.DLL     d:\CMLIB\DLL

          where d is the drive on which Communications Manager is installed.

          Calls to any of these procedure entry points are far calls; that is,
          your program uses a 4-byte pointer in the call.


ΓòÉΓòÉΓòÉ 4.9. Programming Considerations for OS/2, DOS, and Windows Clients ΓòÉΓòÉΓòÉ

This section describes programming considerations for OS/2, DOS, and Windows**
communications client programs in APPC applications that implement
Communications Manager client-server distributed computing.

Note:  Writing transaction programs for the OS/2 , DOS, and Windows clients
client does not differ from that previously described for Communications
Manager, except where noted in this section.


ΓòÉΓòÉΓòÉ 4.10. OS/2 Communications Clients ΓòÉΓòÉΓòÉ

The programming considerations for OS/2 communications clients are described in
the following sections.


ΓòÉΓòÉΓòÉ 4.10.1. Procedure Entry Points ΓòÉΓòÉΓòÉ

 The entry points for APPC on the OS/2 communications client, in any supported
language, are: headi=2.

          Entry Point    Description
          APPC           This entry point in APPC.DLL is for control and
                         conversation verbs and the CNOS subsystem management
                         verb.  Configuration verbs are not supported.
          ACSSVC         This entry point in ACSSVC.DLL is for common services
                         verbs.  For information about common services verbs,
                         see Application Programming Guide.

          For migration, application programs written for OS/2 Extended Edition
          versions 1.2 and 1.3 that require CNOS verb support can call ACSMGT.

          The DLLs are initially installed in hp1.d\CMLIB\DLL, where d is the
          drive where Communications Manager Client Server/2 is installed.


ΓòÉΓòÉΓòÉ 4.10.2. Data Segments ΓòÉΓòÉΓòÉ

Data buffers are not registered by APPC on the OS/2 communications client. Your
program can allocate and free data buffers as needed.


ΓòÉΓòÉΓòÉ 4.10.3. APPC ExitList Processing ΓòÉΓòÉΓòÉ

On the OS/2 communications client, the APPC ExitList routine does the
following:

           1. Internally issues a hp2.TP_ENDEDehp2. verb with type(SOFT) for
              each active TP in the process.

           2. If the program was started by the attach manager, and it is a
              queued type program, the APPC ExitList routine informs the attach
              manager so it can restart the program if any attaches are queued
              for the TP.

           3. Transfers control to the next installed APPC ExitList routine for
              the process.

          Signals are disabled when a verb is received by APPC and reenabled
          when the verb returns.


ΓòÉΓòÉΓòÉ 4.11. DOS Communications Clients ΓòÉΓòÉΓòÉ

The programming considerations for DOS communications clients are described in
the following sections.


ΓòÉΓòÉΓòÉ 4.11.1. Writing Transaction Programs ΓòÉΓòÉΓòÉ

The Communications Manager DOS client provides a Terminate and Stay Resident
(TSR) program, APPC.EXE, that handles APPC verbs. The Communication Manager DOS
client also provides a TSR, ACSSVC.EXE, that handles common services verbs.

The language interface for the APPC TSR and the ACSSVC TSR is the same as that
previously described for Communications Manager. Your program fills in a verb
control block (VCB) and calls the TSR passing it a pointer to the VCB.  A
modified VCB is then returned to the program containing all returned values.


ΓòÉΓòÉΓòÉ 4.11.2. Procedure Entry Points ΓòÉΓòÉΓòÉ

The entry points for APPC on the DOS communications client, in any supported
language, are: headi=2.

          Entry Point    Description
          APPC           This entry point in the APPC TSR is for control and
                         conversation verbs and the CNOS subsystem management
                         verb.  Configuration verbs are not supported.
          ACSSVC         This entry point in the ACSSVC TSR is for common
                         services verbs.  For information about common services
                         verbs, see Application Programming Guide.

          The ACSMGT entry point is not supported.  Transaction programs that
          require CNOS verb support should use the APPC entry point in the APPC
          TSR.

          The TSRs are initially installed in E:\CMLIBD where e indicates the
          drive where Communications Manager Client Server is installed.


ΓòÉΓòÉΓòÉ 4.11.3. TSR Interface ΓòÉΓòÉΓòÉ

For programs that issue APPC verbs and the CNOS verb, you must use the DOS link
utility program to link your program object file to APPC.LIB.

For programs that issue common services verbs, you must use the DOS link
utility program to link your program object file to ACSSVC.LIB.


ΓòÉΓòÉΓòÉ 4.11.4. Data Segments ΓòÉΓòÉΓòÉ

Because of fundamental differences between the DOS and OS/2 programming
environments, APPC program data segments have different characteristics under
DOS.


ΓòÉΓòÉΓòÉ 4.11.5. Verb Control Blocks (VCB) ΓòÉΓòÉΓòÉ

Your program can declare the verb control block (VCB) as a variable or it can
allocate the VCB dynamically using the memory management facilities provided by
DOS.

Replace all fields in the VCB with zeros (X'00') before your program assigns
values to the parameters.  Fields reserved in earlier releases have been used
for new functions.

APPC can not validate that the VCB is the appropriate length.  If the VCB does
not contain at least 10 bytes (enough to hold the APPC primary and secondary
return codes), APPC may overwrite critical data.


ΓòÉΓòÉΓòÉ 4.11.6. Data Buffers ΓòÉΓòÉΓòÉ

Your program can declare data buffers as variables or it can allocate data
buffers dynamically using the memory management facilities provided by DOS.

Note:  APPC can not validate that the data buffer is the appropriate length.
If the data buffer it smaller than is specified in the VCB, APPC may overwrite
critical data. Data buffers are not registered by APPC on the DOS
communications client.  Your program may allocate and free data buffers as
needed.


ΓòÉΓòÉΓòÉ 4.11.7. APPC Exit Processing ΓòÉΓòÉΓòÉ

Although ExitLists are not supported by DOS, APPC does monitor for termination
of the APPC program and performs exit processing.

Note:  On the DOS communications client, the exit processing consists of
internally issuing a TP_ENDED verb with type(SOFT) for each active TP.


ΓòÉΓòÉΓòÉ 4.11.8. Additional Considerations ΓòÉΓòÉΓòÉ

Deadlock can occur when a program communicates with a partner that does not
support multitasking.  Each side might be blocked from sending because a
program is waiting to receive data. Design DOS communications clients carefully
to ensure that deadlock does not occur.


ΓòÉΓòÉΓòÉ 4.12. Windows Communications Clients ΓòÉΓòÉΓòÉ

The programming considerations for DOS communications clients are as follows:


ΓòÉΓòÉΓòÉ 4.12.1. Procedure Entry Points ΓòÉΓòÉΓòÉ

The entry points in APPC.DLL on the Windows communications client, in any
supported language, are: headi=2.

          Entry Point    Description
          APPC           This entry point in APPC.DLL is for control and
                         conversation verbs, and the CNOS subsystem management
                         verb.  Configuration verbs are not supported.
          ACSSVC         This entry point in ACSSVC.DLL is for common services
                         verbs.  For information about common services verbs,
                         see Application Programming Guide.

          The ACSMGT entry point is not supported.  Transaction programs that
          require CNOS verb support should use the APPC entry point in the APPC
          TSR.

          The DLLs are initially installed in e:\CMLIBW where e is the drive
          where Communications Manager Client Server is installed.


ΓòÉΓòÉΓòÉ 4.12.2. DLL Interface ΓòÉΓòÉΓòÉ

The Windows DLL interface is the same as that previously described for
Communications Manager with the following exceptions:

           1. Because the ACSMGT entry point in ACSSVC.DLL is not supported,
              programs may not import this entry point.

           2. Windows programs that use run-time linking to link to DLLs should
              issue the Windows functions LoadLibrary and GetProcAddress.


ΓòÉΓòÉΓòÉ 4.12.3. Data Segments ΓòÉΓòÉΓòÉ

The previous description of data segments for Communications Manager OS/2 APPC
programs applies to data segments for Windows APPC programs with the following
exceptions:

           1. Programs that allocate VCBs dynamically should use the Windows
              GlobalAlloc function with the alloc flag specifying GMEM_SHARE.

           2. When a verb has an associated data buffer, the program should use
              the Windows GlobalAlloc function with the alloc flag specifying
              GMEM_SHARE to allocate the data buffer.


ΓòÉΓòÉΓòÉ 4.12.4. APPC Exit Processing ΓòÉΓòÉΓòÉ

Although ExitLists are not supported by Windows, APPC does monitor for
termination of the APPC program and performs exit processing.

On the Windows communications client, APPC exit processing consists of the
following:

           1. APPC internally issues a TP_ENDED verb with type(SOFT) for each
              active TP in the process.

           2. If the program was started by the attach manager, and it is a
              queued type program, the attach manager is informed so it can
              restart the program if any attaches are queued for the TP.


ΓòÉΓòÉΓòÉ 5. The DISPLAY Verb ΓòÉΓòÉΓòÉ

This chapter contains reference information for the DISPLAY verb. The DISPLAY
verb returns configuration information and current operating values for the
active SNA node. Your program may request all or any combination of information
types. APPC returns the requested information into a data buffer; the types of
information requested and the size and address of the data buffer are supplied
parameters on the verb.

See DISPLAY Verb Control Block for information on the verb control block
format.


ΓòÉΓòÉΓòÉ 5.1. DISPLAY ΓòÉΓòÉΓòÉ

DISPLAY

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDISPLAYΓöÇΓöÇlength_of_initial_sectionnΓöÇΓöÇdisplay_buffer_lengthnΓöÇΓöÇdisplay_buffer_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇnumber_of_information_sectionsnΓöÇΓöÇsna_global_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇlu_6.2_informationΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                  ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇattach_manager_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇtp_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇsession_informationΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇNOΓöÇΓöÇΓöÿ                ΓööΓöÇNOΓöÇΓöÇΓöÿ          ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇlink_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇlu_0_to_3_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇgw_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇNOΓöÇΓöÇΓöÿ           ΓööΓöÇNOΓöÇΓöÇΓöÿ             ΓööΓöÇNOΓöÇΓöÇΓöÿ          ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇX.25_physical_link_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇsystem_defaults_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                      ΓööΓöÇNOΓöÇΓöÇΓöÿ                ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇadapter_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇlu_definition_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                ΓööΓöÇNOΓöÇΓöÇΓöÿ               ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇpartner_lu_definition_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇmode_definition_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                       ΓööΓöÇNOΓöÇΓöÇΓöÿ                ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇlink_definition_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇmanagement_services_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇpu_infoΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                    ΓööΓöÇNOΓöÇΓöÇΓöÿ                  ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇincoming_call_directory_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇNOΓöÇΓöÇΓöÿ                    ΓööΓöÇNOΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöñ Returned Parameters Γö£ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÿ
                    RETURNED PARAMETERS:
                    Γö£ΓöÇΓöÇdisplayed_lengthnΓöÇΓöÇrequired_lengthnΓöÇΓöÇsna_global_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇlu_6.2_information_addressaddressΓöÇΓöÇattach_manager_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇtp_information_addressaddressΓöÇΓöÇsession_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇinformation_addressaddressΓöÇΓöÇlu_0_to_3_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇgw_information_addressaddressΓöÇΓöÇX.25_physical_link_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇsystem_defaults_information_addressaddressΓöÇΓöÇadapter_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇlu_definition_information_addressaddressΓöÇΓöÇpartner_lu_definition_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇmode_definition_information_addressaddressΓöÇΓöÇlink_definition_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇmanagement_services_information_addressaddressΓöÇΓöÇpu_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇincoming_call_directory_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ

 Parameters

          length_of_initial_section
                    Specifies the number of bytes in this verb control block,
                    up to the beginning of the information pointers.

                    For Communications Manager, always specify the integer
                    value 52.

          display_buffer_length
                    Specifies the length (0 to 65535 bytes) of the display data
                    buffer that is to contain the returned information.

          display_buffer_address
                    The address of the buffer that is to contain the requested
                    information.

                    Use a shared, unnamed segment for the data buffer. as
                    directed in OS/2 Technical Library. The data buffer must be
                    entirely within the data segment, so the offset portion of
                    the address plus the length of the data buffer must not
                    exceed the segment size.

          number_of_information_sections
                    Specifies the maximum number of information sections that
                    can be returned by this verb. For Communications Manager,
                    always specify the integer value 18.

          sna_global_information
                    Specifies a request for SNA global information.

          lu_6.2_information
                    Specifies a request for information on all active LUs,
                    their partners, and their modes.

          attach_manager_information
                    Specifies a request for information on the defined
                    transaction programs.

          tp_information
                    Specifies a request for information on the active
                    transaction programs and any active conversations.

          session_information
                    Specifies a request for information on sessions.

          link_information
                    Specifies a request for information on the active SNA
                    logical links.

          lu_0_to_3_information
                    Specifies a request for information on logical units type
                    0, 1, 2, and 3.

          gw_information
                    Specifies a request for information on the SNA gateway.

          X.25_physical_link_information
                    Specifies a request for X.25 physical link information.

          system_defaults_information
                    Specifies a request for information about the default LU,
                    mode names, and default parameters for inbound and outbound
                    implicit partners.

          adapter_information
                    Specifies a request for information about the configured
                    communications adapters.

          lu_definition_information
                    Specifies a request for information about the defined LUs.

          partner_lu_definition_information
                    Specifies a request for information about the defined
                    partner LUs.

          mode_definition_information
                    Specifies a request for information about the defined
                    modes.

          link_definition_information
                    Specifies a request for information about the defined
                    logical links.

          management_services_information
                    Specifies a request for information about management
                    services.

          pu_information
                    Specifies a request for information about the physical
                    units.

          incoming_call_directory_information
                    Specifies a request for incoming call directory
                    information.

 Return Codes

          The OK return code indicates that the DISPLAY verb ran successfully:

          The following returned parameters correspond to the supplied
          parameters. The requested information is returned only when the
          return code indicates OK.

          displayed_length
                    This 4-byte integer is the total number of bytes returned
                    into the display data buffer. The number is less than or
                    equal to the number supplied for the display_buffer_length
                    parameter.

          required_length
                    This 4-byte integer is the total number of bytes needed for
                    displayed data. This number may be larger than the supplied
                    display_buffer_length. It may also be larger than 64KB if
                    the requested information cannot fit within a 64KB segment.
                    In this case, reissue the DISPLAY verb with one information
                    field at a time. The required buffer size can change when
                    reissuing the DISPLAY verb because new sessions, TPs, and
                    other resources could have been started in the meantime.

          sna_global_information_address
                    Indicates the address of the beginning of SNA global
                    information in the data buffer.

          lu_6.2_information_address
                    Indicates the address of the beginning of LU 6.2
                    information in the data buffer.

          attach_manager_information_address
                    Indicates the address of the beginning of the attach
                    manager information in the data buffer.

          tp_information_address
                    Indicates the address of the beginning of TP information in
                    the data buffer.

          session_information_address
                    Indicates the address of the beginning of session
                    information in the data buffer.

          link_information_address
                    Indicates the address of the beginning of link information
                    in the data buffer.

          lu_0_to_3_information_address
                    Indicates the address of the beginning of LU information in
                    the data buffer.

          gw_information_address
                    Indicates the address of the beginning of gateway
                    information in the data buffer.

          X.25_physical_link_information_address
                    Indicates the address of the beginning of X.25 physical
                    link information in the data buffer.

          system_defaults_information_address
                    Indicates the address of the beginning of system default
                    information in the data buffer.

          adapter_information_address
                    Indicates the address of the beginning of adapter
                    information in the data buffer.

          local_lu_definition_information_address
                    Indicates the address of the beginning of local LU
                    definition information information in the data buffer.

          partner_lu_definition_information_address        .
                    Indicates the address of the beginning of partner LU
                    definition information in the data buffer.

          mode_definition_information_address
                    Indicates the address of the beginning of mode definition
                    information in the data buffer.

          link_definition_information_address
                    Indicates the address of the beginning of link definition
                    information in the data buffer.

          management_services_information_address
                    Indicates the address of the beginning of management
                    services information in the data buffer.

          pu_information_address
                    Indicates the address of the beginning of the physical
                    units information in the data buffer.

          incoming_call_directory_information
                    Indicates the address of the beginning of incoming call
                    directory information in the data buffer.

          DISPLAY Verb Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the DISPLAY verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DISPLAY Verb Primary and Secondary Return Codes                     Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DISPLAY_INVALID_CONSTANT    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DISPLAY_INFO_EXCEEDS_LENGTH   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DATA_SEGMENT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé X.25_ERROR       Γöé X25_UNEXPECTED_OS2_ERROR    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_ABEND            Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_INACTIVE          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_TERMINATING         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_INSUFFICIENT_RESOURCE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_DEVICE_DRIVER_ERROR     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_ADAPTER_ACCESS_ERROR    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_ADPTER_ERROR        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_INVALID_LINK_NAME      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_LINK_IN_CONNECT_MODE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_LINK_IN_DISCONNECT_MODE   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_LINK_IN_AUTOCONNECT_MODE  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_LINK_ERROR_LEVEL_1     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_LINK_ERROR_LEVEL_2     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_INVALID_STATE        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_COMMS_SERVICES_ERROR    Γöé Numeric List of Secondary Return Codes Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DISPLAY verb requires a user-supplied buffer for the return of
          system information. If the buffer is not large enough, APPC returns
          the DISPLAY_INFO_EXCEEDS_LENGTH return code, along with the size
          actually needed at the time of the request (in the required_length
          returned parameter). One possible strategy for the use of this verb
          follows:

           1. Allocate a 64KB buffer (you can use a smaller buffer size if you
              have system memory constraints) in the display_buffer_length
              parameter.

           2. If APPC returns the DISPLAY_INFO_EXCEEDS_LENGTH return code, then
              take one of the following steps:

             o If the display_buffer_length value is less than the
               required_length value returned by APPC and the required length
               is less than 64KB, then increase the size of the display buffer
               to equal or greater than the required_length value.

             o If the required_length value is greater than 64KB, you may
               choose to request each information section individually, or you
               can perform the following:

                 a. Process the information sections with complete information,
                    whose total number displayed equals the actual total
                    number.

                 b. Choose a subset of the information sections you requested
                    that contains incomplete information and reissue the verb
                    requesting these information sections.

                 c. Repeat steps a and b as needed.

          Note:  If an individual information section is greater than 64KB,
          then you cannot get all of the requested information from APPC.


ΓòÉΓòÉΓòÉ 5.2. SNA Global Information ΓòÉΓòÉΓòÉ

SNA Global Information

The sna_global_information_address points to the first byte of the returned SNA
global information in the display data buffer.

See SNA_GLOBAL_INFO_SECT for the DISPLAY Verb Control Block for the format of
the returned information.

          SNA Global Information Group Returned Parameters shows returned
          parameters that describe SNA global information for the DISPLAY verb.

                    SNA Global Information
                    versionn
                    releasen
                    net_namename
                    cp_namename
                    alias_cp_namename
                    node_idid
                    node_type{EN | NN}
                    cp_nau_addressaddress
                    product_set_idid
                       machine type number
                       model number
                       plant of manufacture
                       machine sequence number

          SNA Global Information Group Returned Parameters

 Return Codes

          version
                    This 1-byte field indicates the version number. The hex
                    value for this field is X'01'.

          release
                    This 1-byte field indicates the release number of this
                    implementation. The hex value for this field is X'00'.

          net_name
                    The name of the network containing the local control point
                    (CP). This network name is the first part of the
                    fully_qualified_cp_name. This name is also known as the
                    network ID or NETID in other machines.

                    This is a Type A EBCDIC character string. If this name is
                    less than eight characters, APPC pads it on the right with
                    EBCDIC blanks.

          cp_name
                    The name of the local control point (CP). This CP name is
                    the second part of the fully_qualified_cp_name.

                    This is a Type A name EBCDIC character string. If this name
                    is less than 8 characters, APPC pads it on the right with
                    EBCDIC blanks.

          alias_cp_name
                    The 8-byte ASCII name used locally for the control point
                    (CP). The name is not sent outside the local node.

                    This is an ASCII character string. If the name is less than
                    8 bytes, APPC pads it on the right with ASCII blanks.

          node_id
                    This 4-byte hexadecimal string indicates the local node ID
                    used in the exchange ID (XID) exchange. For Communications
                    Manager, the first 3 hexadecimal digits are always X'05D';
                    the remaining 5 hexadecimal digits are the configured
                    node_id.

          node_type
                    Indicates the network capabilities of the node. APPC
                    returns one of the following values:

             EN        Your workstation is configured as an APPN end node.
             NN        Your workstation is configured as an APPN network node.

          cp_nau_address
                    Specifies the destination network address of the control
                    point (CP) for sessions to a subarea node.

          product_set_id
                    This 16-byte field indicates the configured hardware
                    product set ID. This information was configured in the
                    Communications Manager workstation profile.

                    The product_set_id consists of four parts:

              1. Machine type number: 4 bytes
              2. Model number: 3 bytes
              3. Plant of manufacture: 2 bytes
              4. Machine sequence number: 7 bytes

                    These are all Type A name EBCDIC character strings.


ΓòÉΓòÉΓòÉ 5.3. LU 6.2 Information ΓòÉΓòÉΓòÉ

LU 6.2 Information

The lu_6.2_information_address points to the first byte of the returned LU 6.2
information in the display data buffer. It returns information about each local
LU that has an active LU 6.2 session, each partner LU that it is in session
with, and each mode used in an active session between the local LU and partner
LU.

Each local LU 6.2 can have multiple partner LUs; each partner LU can have
multiple modes.

See LU62_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          LU 6.2 Information Group Returned Parameters shows returned
          parameters that describe LU 6.2 information for the DISPLAY verb.

          LU 6.2 Information Group Returned Parameters

                    LU 6.2 Information
                    length_of_lu_6.2_initial_sectionn
                    number_of_lu_6.2n
                    total_number_lu_6.2n

                    Local LU Group (Repeated for each active local LU):
                    length_of_this_lu_6.2_entryn
                    length_of_lu_6.2_info_onlyn
                    lu_namename
                    lu_aliasname
                    number_of_partner_lusn
                    fully_qualified_lu_namename
                    default_lu{YES | NO}
                    lu_local_addressvalue
                    lu_session_limitn
                    max_tpsn
                    lu_type_6.2value
                    pu_namename

                    Partner LU Group (Repeated for each active partner LU):
                    length_of_this_partner_lu_entryn
                    length_of_partner_lu_info_onlyn
                    partner_lu_aliasname
                    number_of_modesn
                    partner_lu_uninterpreted_namename
                    fq_partner_lu_namename
                    partner_lu_session_limitn
                    partner_lu_dlc_namename
                    partner_lu_adapter_numbern
                    partner_lu_destination_address_lengthvalue
                    partner_lu_destination_addressvalue
                    parallel_session_support{SUPPORTED | NOT_SUPPORTED}
                    def_partner_lu_security_capabilities
                    act_partner_lu_security_capabilities
                    implicit_partner

                    Mode Group (Repeated for each active mode):
                    length_of_this_mode_entryn
                    mode_namename
                    max_ru_size_lowern
                    max_ru_size_uppern
                    mode_max_negotiable_session_limitn
                    current_session_limitn
                    min_negotiated_winner_limitn
                    min_negotiated_loser_limitn
                    active_session_countn
                    pending_session_countn
                    auto_activaten
                    active_conwinner_session_countn
                    active_conloser_session_countn
                    session_termination_countn
                    session_termination_source_drain{YES | NO}
                    session_termination_target_drain{YES | NO}
                    pacing_sizevalue
                    implicit_mode{YES | NO }
                    def_compression_need
                    def_plu_slu_compression
                    def_slu_plu_compression

 Return Codes

          Each LU 6.2 can have multiple partners and each partner can have
          multiple modes. Therefore, the partner LU parameters are repeated for
          each partner LU associated with a local LU; the mode parameters are
          repeated for each mode associated with a partner LU.

          length_of_lu_6.2_initial_section
                    Indicates the size of the information prior to the first
                    local LU 6.2 group. It includes the size of this field but
                    not of any previous fields.

          number_of_lu_6.2
                    Indicates the number of local LU 6.2 groups returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_lu_6.2
                    Indicates the total number of local LU 6.2 groups.

                    Local LU Group

                    The following parameters are repeated for each active
                    partner LU. APPC returns a value for each defined LU 6.2.

             length_of_this_lu_6.2_entry
                       Indicates the size of this local LU 6.2 group, including
                       this local LU 6.2 information and its partner LU
                       information and mode information. It includes the size
                       of this field but not of any previous fields.

             length_of_lu_6.2_info_only
                       Indicates the size of the local LU 6.2 information up to
                       the first partner LU group. It includes the size of this
                       field but not of any previous fields.

             lu_name
                       The 8-byte EBCDIC network name of the local LU. This is
                       the name of the LU as it is known throughout the
                       network.

                       This is a type A EBCDIC character string. If the name is
                       less than 8 bytes, it is padded on the right with EBCDIC
                       blanks.

             lu_alias
                       The 8-byte ASCII name used locally for the LU. The name
                       is not sent outside the local node.

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, it must be padded on the right with
                       ASCII blanks.

                       Alternatively, you can select the default local LU by
                       specifying 8 bytes of binary zeros.

                       Note:  This parameter is case sensitive.

                       Ensure that this field is defined with the correct
                       uppercase and

             number_of_partner_lus
                       Indicates the number of partner LU groups for the
                       current LU.

             fully_qualified_lu_name
                       Indicates the fully qualified EBCDIC name of the local
                       LU. The fully qualified name consists of the name of the
                       network to which the local LU belongs, a period (.), and
                       the lu_name as it is known in the network.

                       This name consists of two type-A EBCDIC character
                       strings. If this name is less than 17 characters
                       (including the EBCDIC period), it is padded on the right
                       with EBCDIC blanks.

             default_lu
                       Indicates whether this LU is the default LU. APPC
                       returns one of the following values for this parameter:

                YES
                          Indicates that the LU serves three purposes:

                    1. It is the LU that a TP is associated with if the TP does
                       not specify any LU in the TP_STARTED verb; that is, if
                       the lu_alias field is all zeros. This does not apply to
                       remotely initiated TPs.

                    2. It is the LU to which the CNOS verb applies if that verb
                       does not specify an LU name, that is, if the lu_alias
                       field is all zeros.

                    3. It is the LU to which an incoming session-activation
                       request (BIND) is routed if that request did not specify
                       an LU.

                NO
                          This specifies that the LU is not the default LU.

                       Note:  The name of the default_lu is returned in the
                              systems_defaults_information parameter of the
                              default_local_lu_name field.

             lu_local_address
                       This 1-byte field indicates the local SNA address (NAU
                       address) of the LU. For independent LUs, this field is
                       X'00'.

             lu_session_limit
                       This field is retired and set to 65535.

             max_tps
                       This field is always set to 0, which indicates that
                       there is no limit.

             lu_type_6.2
                       Indicates the type of LU for which the information is
                       being displayed. In this section, the value is always
                       X'06', which means LU 6.2.

             pu_name
                       The 8-character identifier that corresponds to a host
                       system link used for dependent LU sessions.  If multiple
                       PUs exist, this allows multiple host systems to
                       concurrently issue ACTPUs to the same physical
                       workstation.

                       Partner LU Group

                       The following parameters are repeated for each active
                       partner LU.

                length_of_this_partner_lu_entry
                          Indicates the size of this partner LU group,
                          including this partner LU information and the modes
                          defined under it. It includes the size of this field
                          but not of any previous fields.

                length_of_partner_lu_info_only
                          Indicates the size of the partner LU information up
                          to the first mode under this partner LU. It includes
                          the size of this field but not of any previous
                          fields.

                partner_lu_alias
                          The locally known name for the partner LU.

                          This is an 8-byte ASCII character string. If the
                          string is less than 8 bytes, you must pad it on the
                          right with ASCII blanks.

                          Note:  This parameter is case sensitive. Ensure that
                                 this field gets defined with the correct
                                 uppercase and lowercase characters.

                number_of_modes
                          Indicates the number of mode groups.

                partner_lu_uninterpreted_name
                          The EBCDIC name of the partner LU (defined to the
                          SSCP, such as VTAM*). The name is sent as the DLU
                          (destination LU) name on a request for session
                          activation (INIT_SELF) on the subarea connection.
                          This field is valid only for a dependent local LU
                          whose network address (defined in the configuration)
                          is not 0.

                          This is a Type AE EBCDIC character string. If this
                          name is less than 8 characters, it is padded it on
                          the right with EBCDIC blanks.

                fq_partner_lu_name
                          The 17-byte EBCDIC fully qualified network name for
                          the partner LU. The name consists of the partner
                          network ID, an EBCDIC period, and the
                          partner_lu_name. This is the name of the partner LU
                          as it is known throughout the network.

                          This name is two type A EBCDIC character strings
                          concatenated by an EBCDIC period. Each name can have
                          a maximum length of 8 bytes with no embedded blanks.
                          If the network ID is not present, the period is
                          omitted. If the name is less than 17 bytes, it is
                          padded on the right with EBCDIC blanks.

                partner_lu_session_limit
                          This field is retired and set to 65535.

                partner_lu_dlc_name
                          This field is retired and set to blanks.

                partner_lu_adapter_number
                          This field is retired and set to 0.

                partner_lu_destination_address_length
                          This field is retired and set to 0.

                partner_lu_destination_address
                          This field is retired and set to 0.

                parallel_session_support
                          This indicates if parallel sessions are supported
                          between the local LU and the partner LU pair.

                   SUPPORTED
                             Parallel sessions are supported with this partner
                             LU.

                   NOT_SUPPORTED
                             Parallel sessions are not supported with this
                             partner LU.

                def_partner_lu_security_capabilities
                          This 1-byte field indicates the LU-LU verification
                          and conversation security support levels of this
                          partner LU.

                                                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé  BIT  Γöé    Γöé                     Γöé
                                                    Γöé BIT NAME                 Γöé POSI- Γöé VALUE Γöé MEANING                 Γöé
                                                    Γöé                     Γöé  TION Γöé    Γöé                     Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé Reserved                 Γöé  0-4  Γöé 00000 Γöé Reserved                Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   0 Γöé Not supported              Γöé
                                                    Γöé Session level security          Γöé  5  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   1 Γöé Supported                Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   0 Γöé Not supported              Γöé
                                                    Γöé Conversation level security       Γöé  6  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   1 Γöé Supported                Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   0 Γöé Not supported              Γöé
                                                    Γöé Already verified security        Γöé  7  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   1 Γöé Supported                Γöé
                                                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                act_partner_lu_security_capabilities
                          This 1-byte field indicates the active LU-LU
                          verification and conversation security support levels
                          of this partner LU following session activation.

                                                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé  BIT  Γöé    Γöé                     Γöé
                                                    Γöé BIT NAME                 Γöé POSI- Γöé VALUE Γöé MEANING                 Γöé
                                                    Γöé                     Γöé  TION Γöé    Γöé                     Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé Reserved                 Γöé  0-5  Γöé 000000Γöé Reserved                Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   0 Γöé Not supported              Γöé
                                                    Γöé Conversation level security       Γöé  6  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   1 Γöé Supported                Γöé
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   0 Γöé Not supported              Γöé
                                                    Γöé Already verified security        Γöé  7  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                                    Γöé                     Γöé    Γöé   1 Γöé Supported                Γöé
                                                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                implicit_partner
                          Indicates if the entry for this partner LU was
                          created as a result of receiving a session activation
                          request from an unconfigured partner LU.

                          Mode Group

                          The following parameters are repeated for each active
                          mode.

                   length_of_this_mode_entry
                             Indicates the size of this mode group. It includes
                             the size of this field but not of any previous
                             fields.

                   mode_name
                             The 8-byte EBCDIC name for the mode. The mode name
                             is used to designate the network properties for a
                             group of sessions. This is the name of the mode as
                             it is known throughout the network.

                             This is a type A EBCDIC character string. If the
                             name is less than 8 bytes, APPC pads it on the
                             right with EBCDIC blanks.

                   max_ru_size_lower
                             Indicates the lower boundary for the maximum RU
                             size to be used on sessions with this mode name.

                   max_ru_size_upper
                             Indicates the upper boundary for the maximum RU
                             size to be used on sessions with this mode name.

                   mode_max_negotiable_session_limit
                             Indicates the value used to negotiate the maximum
                             number of sessions permissible between the local
                             LU and the partner LU for the designated mode
                             name.

                   current_session_limit
                             Indicates the currently agreed to maximum session
                             limit between the local and the partner LU for the
                             designated mode name.

                   min_negotiated_winner_limit
                             Indicates the minimum number of contention-winner
                             sessions permissible between the local LU and the
                             partner LU for the designated mode name as
                             specified or negotiated in the CNOS verb.

                   min_negotiated_loser_limit
                             Indicates the minimum number of contention-loser
                             sessions permissible between the local LU and the
                             partner LU for the designated mode name as
                             specified or negotiated in the CNOS verb.

                   active_session_count
                             Indicates the number of currently active sessions
                             between the local LU and the partner LU on the
                             designated mode name.

                   pending_session_count
                             Indicates the number of sessions pending (waiting
                             for session activation to complete).

                   auto_activate
                             Indicates the number of contention-winner sessions
                             for the communication subsystem to activate
                             automatically, rather than using session
                             allocation verbs.

                   active_conwinner_session_count
                             Indicates the number of currently active
                             contention-winner sessions between the local LU
                             and the partner LU on the designated mode name.

                   active_conloser_session_count
                             Indicates the number of currently active
                             contention-loser sessions between the local LU and
                             the partner LU on the designated mode name.

                   session_termination_count
                             If a previous CNOS verb caused the mode session
                             limit to be reset to 0, there may have been
                             conversations using or waiting to use those
                             sessions. The session_termination_count indicates
                             how many of those sessions have not yet been
                             deactivated.

                   session_termination_source_drain
                             Indicates if the local LU can drain the queue of
                             Attaches before taking down sessions as a result
                             of a CNOS verb.

                             APPC returns a value of either YES or NO.

                   session_termination_target_drain
                             Indicates if the remote LU can drain the queue of
                             Attaches before taking down sessions as a result
                             of a CNOS verb.

                             APPC returns a value of either YES or NO.

                   pacing_size
                             Indicates the largest permissible size for the
                             received pacing window on sessions with this mode
                             name.

                   implicit_mode
                             Indicates if the entry for this mode was created
                             as a result of receiving a session activation
                             request specifying an unconfigured mode.

                             APPC returns a value of either YES or NO.

                   def_compression_need
                             The compression need defined for the mode.

                   def_plu_slu_compression
                             The requested PLU to SLU compression level for a
                             session established with this mode.

                             The actual compression level activated at session
                             initiation may be different.

                   def_slu_plu_compression
                             The requested SLU to PLU compression level for a
                             session established with this mode.

                             The actual compression level activated at session
                             initiation may be different.


ΓòÉΓòÉΓòÉ 5.4. Attach Manager Information ΓòÉΓòÉΓòÉ

Attach Manager Information

The attach_manager_information_address points to the first byte of the returned
APPC attach manager information in the display data buffer.

See AM_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Attach Manager Information Group Returned Parameters shows returned
          parameters that describe attach manager information for the DISPLAY
          verb.

                    Attach Manager Information
                    length_of_initial_tp_sectionn
                    attach_manager_active{YES | NO}
                    number_of_defined_tpsn
                    total_number_of_defined_tpsn

                    TP Group (Repeated for each configured remotely attachable TP):
                    length_of_this_tp_entryn
                    tp_namename
                    filespecname
                    sync_level_capabilities
                       sync_level_none{SUPPORTED | NOT_SUPPORTED}
                       sync_level_confirm{SUPPORTED | NOT_SUPPORTED}
                    conversation_type{BASIC | MAPPED | EITHER |
                           FDX_BASIC | FDX_MAPPED | FDX_EITHER | ANY_TYPE}
                    incoming_allocate_queue_depth_limitn
                    incoming_allocate_queue_depthn
                    incoming_allocate_timeoutn
                    number_of_receive_allocates_pendingn
                    receive_allocate_timeoutn
                    tp_type{QUEUED_OPERATOR_STARTED | QUEUED_AM_STARTED |
                           NONQUEUED_AM_STARTED |
                           QUEUED_OPERATOR_PRELOADED}
                    program_state{INACTIVE | LOADING | LOADED | RUNNING}
                    conversation_security{YES | NO}
                    process_idn
                    parm_stringvalue
                    program_type{BACKGROUND | FULL_SCREEN |
                                PRESENTATION_MANAGER | VIO_WINDOWABLE}
                    icon_filespecname

          Attach Manager Information Group Returned Parameters

 Return Codes

          length_of_initial_tp_section
                    Indicates the size of the initial section of TP
                    information, up to the first TP group. It includes the size
                    of this field but not of any previous fields.

          attach_manager_active
                    Indicates if the APPC application manager is active or not
                    active. APPC returns either YES or NO.

          number_of_defined_tps
                    Indicates the number of configured remotely attachable
                    transaction programs returned by the DISPLAY verb into your
                    program's buffer.

          total_number_of_defined_tps
                    Indicates the total number of configured remotely
                    attachable transaction programs. This value may be greater
                    than the number_of defined_tps value.

                    TP Group

                    The following parameters are repeated for each configured
                    remotely attachable transaction program.

             length_of_this_tp_entry
                       Indicates the size of this TP group. It includes the
                       size of this field but not of any previous fields.

             tp_name
                       The EBCDIC name of the configured transaction program.

             filespec
                       Indicates the ASCII name of the OS/2 program that
                       contains the transaction program specified in the
                       tp_name field. The name is in the format of a drive,
                       path, file name, a period (.), and a file extension. If
                       this name is less than 64 characters, APPC pads it on
                       the right with ASCII blanks. The name is truncated if it
                       is longer than 64 bytes.

             sync_level_capabilities
                       Indicates the synchronization level or levels that the
                       transaction program supports. The transaction program
                       can support one or both of these sync levels.

                sync_level_none
                          This 1-bit field indicates whether the transaction
                          program supports the synchronization level of NONE. A
                          transaction program that supports NONE does not
                          perform confirmation processing. The transaction
                          program does not issue verbs, and does not recognize
                          any returned parameters, relating to the confirmation
                          function.

                          Note:  APPC returns either SUPPORTED or
                                 NOT_SUPPORTED.

                sync_level_confirm
                          This 1-bit field indicates whether the transaction
                          program supports the synchronization level of
                          CONFIRM. A transaction program that supports CONFIRM
                          can perform confirmation processing. The transaction
                          program can issue verbs, and recognize any returned
                          parameters, relating to the confirmation function.

                          Note:  APPC returns either SUPPORTED or
                                 NOT_SUPPORTED.

             conversation_type
                       Specifies the type (basic or mapped) and style
                       (half-duplex or full-duplex) of conversations that will
                       be used by the TP.  This parameter is verified upon
                       receipt of an incoming attach.  You must specify one of
                       the following values:

                BASIC
                          Indicates that this transaction program supports
                          basic conversations.

                MAPPED
                          Indicates that this transaction program supports
                          mapped conversations.

                EITHER
                          Indicates that this transaction program supports
                          either basic or mapped conversations.

                FDX_BASIC
                          Indicates that this transaction program supports
                          basic conversation verbs for full-duplex operation.

                FDX_MAPPED
                          Indicates that this transaction program supports
                          mapped conversation verbs for full-duplex operation.

                FDX_EITHER
                          Indicates that this transaction program supports
                          either basic or mapped conversation verbs for
                          full-duplex operation.

                ANY_TYPE
                          Indicates that this transaction program supports
                          either basic or mapped conversation verbs, and can
                          accept either a half-duplex or full-duplex
                          conversation, depending upon what arrives on the
                          incoming allocation request.

             incoming_allocate_queue_depth_limit
                       This 2-byte integer indicates the maximum depth of the
                       queue for the incoming attaches. This field is valid
                       only for transaction programs configured as queued; for
                       nonqueued programs, APPC returns 0 for this field.

             incoming_allocate_queue_depth
                       This 2-byte integer indicates the number of Attaches
                       queued to the transaction program at this time. This
                       field is valid only for transaction programs configured
                       as queued; for nonqueued programs, APPC returns 0 for
                       this field.

             incoming_allocate_timeout
                       This 2-byte integer indicates the length of time, in
                       seconds, that an Attach should remain queued awaiting an
                       APPC RECEIVE_ALLOCATE verb or a CPI Communications
                       Accept_Conversation (CMACCP) call. A returned value of
                       -1 (that is, X'FFFF') means incoming Attaches will not
                       be rejected because of a passage of time. This field is
                       valid only for transaction programs configured as
                       queued; for nonqueued programs, APPC returns 0 for this
                       field.

             number_of_receive_allocates_pending
                       This 2-byte integer indicates the number of APPC
                       RECEIVE_ALLOCATE verbs or CPI Communications
                       Accept_Conversation (CMACCP) calls for this transaction
                       program held by the attach manager at this time. This
                       field is valid only for transaction programs configured
                       as queued; for nonqueued programs, APPC returns 0 for
                       this field.

             receive_allocate_timeout
                       Indicates the length of time, in seconds, that an APPC
                       RECEIVE_ALLOCATE verb or a CPI Communications
                       Accept_Conversation (CMACCP) call should remain queued
                       awaiting an incoming attach. A returned value of -1
                       (that is, X'FFFF') means incoming Attaches are not
                       rejected because of a passage of time. This field is
                       valid only for transaction programs configured as
                       queued; for nonqueued programs, APPC returns 0 for this
                       field.

             tp_type
                       Indicates how the TP type was configured for the OS/2
                       program. APPC returns one of the following values:

                QUEUED_OPERATOR_STARTED
                          Indicates that the OS/2 program is started by an
                          operator. Incoming attaches specifying this tp_name
                          are queued by the attach manager until the program
                          requests them by issuing an APPC RECEIVE_ALLOCATE
                          verb or a CPI Communications Accept_Conversation
                          (CMACCP) call. A message is displayed if the program
                          is not started.

                QUEUED_AM_STARTED
                          Indicates that the attach manager starts an OS/2
                          program when the first incoming Attach specifying
                          this tp_name arrives. Subsequent incoming attaches
                          are queued by the attach manager until the program
                          requests them by issuing APPC RECEIVE_ALLOCATE verbs
                          or CPI Communications Accept_Conversation (CMACCP)
                          calls. If the program ends with allocates queued for
                          it or if an incoming attach for this program
                          subsequently arrives after the program ends, the OS/2
                          program is started again by the attach manager.

                NONQUEUED_AM_STARTED
                          Indicates that the attach manager starts a new
                          instance of this OS/2 program for each incoming
                          Attach specifying this tp_name.

                QUEUED_OPERATOR_PRELOADED
                          Indicates that the OS/2 program is started by an
                          operator. Incoming attaches specifying this tp_name
                          are queued by the attach manager until the program
                          requests them by issuing APPC RECEIVE_ALLOCATE verbs
                          or CPI Communications Accept_Conversation (CMACCP)
                          calls. If the program is not started, a message is
                          not displayed.

             program_state
                       Indicates the state of the OS/2 program containing the
                       transaction program, as known by the attach manager.
                       This field is valid only for transaction programs
                       configured as queued; for nonqueued programs, APPC
                       returns a value of 0 for this field. APPC returns one of
                       the following values:

                INACTIVE
                          Indicates that the attach manager is not aware that
                          the OS/2 program is loaded in memory. An
                          operator-started program may be loaded in memory, but
                          the attach manager does not know of its existence
                          until the program issues the first APPC
                          RECEIVE_ALLOCATE verb or CPI Communications
                          Accept_Conversation (CMACCP) call.

                LOADING
                          Indicates that the OS/2 program is in the process of
                          being started.

                LOADED
                          Indicates that the OS/2 program has been started, but
                          the program has not issued the first APPC
                          RECEIVE_ALLOCATE verb or CPI Communications
                          Accept_Conversation (CMACCP) call. This value is
                          valid only for programs that the attach manager
                          starts, not for operator-started programs.

                RUNNING
                          Indicates that the OS/2 program is started (either by
                          an operator or the attach manager) and has issued the
                          first APPC RECEIVE_ALLOCATE verb or CPI
                          Communications Accept_Conversation (CMACCP) call.

             conversation_security
                       Indicates whether conversation-level security
                       information is required on incoming attaches designating
                       this tp_name. Conversation-level security verification
                       is always performed on those requests that include
                       security information.

                       APPC returns one of the following values:

                YES
                          Indicates that conversation-level security
                          information is required. Attaches designating the
                          transaction program must carry a user_id and either a
                          password or an already verified indicator.

                NO
                          Indicates that no security information is required.
                          Attaches designating the transaction program can omit
                          or include security information.

             process_id
                       This is the 2-byte OS/2 process ID for the process that
                       the OS/2 program is running under. The process ID is not
                       known to the attach manager if the DISPLAY verb returns
                       all zeros for this process ID.

                       The attach manager returns a valid (nonzero) process ID
                       if one of the following conditions is true:

                o The tp_type is QUEUED_AM_STARTED and the program_state is
                  LOADED or RUNNING

                o The tp_type is QUEUED_OPERATOR_STARTED and the program_state
                  is RUNNING.

             program_parameter_string
                       Indicates the first 32 bytes of the ASCII parameter
                       string that is passed to the remotely started OS/2
                       program when it is started by the APPC attach manager.
                       If the string is longer it is truncated for migration
                       purposes.

             program_type
                       Specifies the type of screen group that will be
                       associated with this OS/2 program, which has not been
                       defined.

                       APPC returns one of the following values:

                BACKGROUND
                          This specifies that this program will not have a
                          screen group and will run as a detached program.

                FULL_SCREEN
                          This specifies that this program will have a screen
                          group but will not run under the Presentation Manager
                          interface.

                PRESENTATION_MANAGER
                          This specifies that this program will have a screen
                          group and will run under the Presentation Manager
                          interface.

                VIO_WINDOWABLE
                          This specifies that this program will have a screen
                          group and will run under the Presentation Manager
                          interface and also is required to make OS/2 VIO
                          calls.

             icon_filespec
                       Indicates an ASCII string containing the fully qualified
                       drive, path, and filename of an icon definition. If you
                       do not specify a file name, OS/2 provides an icon for
                       windowed applications.


ΓòÉΓòÉΓòÉ 5.5. TP Information ΓòÉΓòÉΓòÉ

TP Information

The tp_information_address points to the first byte of the returned transaction
program information in the display data buffer.

Each active TP in the Active TP Group can have multiple conversations.

See TP_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          TP Information Group Returned Parameters shows returned parameters
          that describe transaction program information for the DISPLAY verb.

                    TP Information
                    length_of_initial_active_tp_sectionn
                    number_of_active_tpsn
                    total_number_of_active_tpsn

                    Active TP Group (Repeated for each active TP):
                    length_of_this_active_tp_entryn
                    length_of_active_tp_info_onlyn
                    number_of_conversationsn
                    tp_idvalue
                    tp_namename
                    user_idname
                    local/remote_initiated{LOCAL | REMOTE}
                    lu_aliasname
                    luw_idstring

                    Conversation Group (Repeated for each active conversation):
                    length_of_this_conversation_entryn
                    conversation_idvalue
                    conversation_correlator_lengthlength
                    conversation_correlator_idid
                    conversation_state{SEND | RECEIVE | CONFIRM |
                                  CONFIRM_SEND | CONFIRM_DEALLOC |
                                  PENDING_POST | SEND_RECEIVE |
                                  SEND_ONLY | RECEIVE_ONLY}
                    session_idid
                    sync_level_support{NONE | CONFIRM}
                    conversation_type{BASIC | MAPPED | EITHER}
                    conversation_group_idid
                    conversation_source{LOCAL_LU | PARTNER_LU}
                    conversation_style{TWO_WAY_ALTERNATE |
                                        TWO_WAY_SIMULTANEOUS}
                    source_send_byte_countn
                    target_send_byte_countn

          TP Information Group Returned Parameters

 Return Codes

          length_of_initial_active_tp_section
                    Indicates the size of this TP section up to the first
                    active TP group. It includes the size of this field but not
                    of any previous fields.

          number_of_active_tps
                    Indicates the number of active TP groups returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_active_tps
                    Indicates the total number of active TP groups.

                    Active TP Group

                    The following parameters are repeated for each active
                    transaction program.

             length_of_this_active_tp_entry
                       Indicates the size of this active TP group, including
                       information for this active TP and its active
                       conversations. It includes the size of this field but
                       not of any previous fields.

             length_of_active_tp_info_only
                       Indicates the size of the information up to the first
                       conversation group. It includes the size of this field
                       but not of any previous fields.

             number_of_conversations
                       Indicates the number of conversation groups.

             tp_id
                       Indicates the internal identifier of the transaction
                       program for which this information is displayed.

             tp_name
                       The EBCDIC name of this active transaction program.

             user_id
                       The EBCDIC user ID that the initiating program provided
                       in the incoming attach.

                       This is a Type AE EBCDIC character string. If this name
                       is less than 10 characters, APPC pads it on the right
                       with EBCDIC blanks.

             local/remote_initiated
                       This 1-byte field indicates if this transaction program
                       was started locally (by the TP_STARTED verb) or remotely
                       (by an incoming attach).

                       APPC returns one of the following values:

                LOCAL     This transaction program was locally started.
                REMOTE    This transaction program was remotely started.

             lu_alias
                       The 8-byte ASCII name used locally for the LU. The name
                       is not sent outside the local node.

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, it must be padded on the right with
                       ASCII blanks.

                       Alternatively, you can select the default local LU by
                       specifying 8 bytes of binary zeros.

                       Note:  This parameter is case sensitive. Ensure that
                       this field is defined with the correct uppercase and
                       lowercase characters.

             luw_id
                       The luw identifier for the transaction in which the TP
                       is participating. The luw_id is created for, or on
                       behalf of, the TP that initiated the transaction, and is
                       carried on all attaches initiated during that
                       transaction.

                       The luw_id consists of the following fields:

                o Length (1 byte):  binary length of the fully qualified LU
                  name
                o The fully qualified LU name

                       Conversation Group

                       The following parameters are repeated for each active
                       conversation associated with this TP.

                length_of_this_conversation_entry
                          Indicates the size of this conversation group. It
                          includes the size of this field but not of any
                          previous fields.

                conversation_id
                          Indicates the 4-byte ID of the conversation for which
                          this information is displayed.

                conversation_correlator_length
                          The length of the conversation correlator. You can
                          specify a value in the range of 0 to 8; 0 indicates
                          that no conversation correlator is defined.

                conversation_correlator_id
                          This is an 8-byte identifier that the source LU
                          assigns to the conversation; the source LU is the one
                          that sent the allocation request. The conversation
                          correlator is included on the allocation request. The
                          conversation correlator uniquely identifies a
                          conversation, from among all conversations, between
                          the local and partner LUs. It may be used, for
                          example, during problem determination associated with
                          a conversation.

                conversation_state
                          Indicates the state of the conversation when the
                          DISPLAY verb was issued. APPC returns one of the
                          following values:

                   SEND
                             The conversation can send data. This value also is
                             returned if the conversation is in Send-Pending
                             state.

                   RECEIVE
                             The conversation can receive data.

                   CONFIRM
                             The conversation has received a confirm indicator.
                             It can issue an [MC_]CONFIRMED or [MC_]SEND_ERROR
                             verb to change state.  It will continue in Receive
                             state if an [MC_]CONFIRMED verb is issued.

                   CONFIRM_SEND
                             The conversation is in Confirm state and changes
                             to Send state when an [MC_]CONFIRMED verb is
                             issued.

                   CONFIRM_DEALLOC
                             The conversation is in Confirm state and becomes
                             inactive when an [MC_]CONFIRMED verb is issued.

                   PENDING_DEALLOCATE
                             The conversation is in Pending-Deallocate state
                             while it waits for (MC_)DEALLOCATE TYPE
                             (sync_level) to complete.

                   PENDING_POST
                             The conversation is in Pending-Post state while it
                             waits for the [MC_]RECEIVE_AND_POST verb to
                             complete its receive function.

                   SEND_RECEIVE
                             The full-duplex conversation can send or receive
                             data.

                   SEND_ONLY
                             The full-duplex conversation can send data, but it
                             does not have permission to receive data, because
                             the partner TP has already deallocated its side of
                             the conversation.

                   RECEIVE_ONLY
                             The full-duplex conversation can receive data, but
                             it does not have permission to send data, because
                             it has already deallocated its side of the
                             conversation.

                session_id
                          Indicates the 8-byte internal identifier of the
                          current session.

                sync_level_support
                          Indicates the sync level support for the
                          conversation. APPC returns one of the following
                          values:

                   NONE
                             Indicates that the transaction program does not
                             perform confirmation processing.  The transaction
                             program does not issue verbs and does not
                             recognize any returned parameters relating to the
                             confirmation function.

                   CONFIRM
                             Indicates that the transaction program can perform
                             confirmation processing. The transaction program
                             can issue verbs and recognize returned parameters
                             relating to confirmation.

                conversation_type
                          This 1-byte field indicates the type of conversation
                          that the transaction program supports.

                          APPC returns one of the following values:

                   BASIC
                             Indicates that this transaction program supports
                             basic conversations.

                   MAPPED
                             Indicates that this transaction program supports
                             mapped conversations.

                   EITHER
                             Indicates that this transaction program supports
                             either basic or mapped conversations.

                conversation_group_id
                          This value uniquely identifies each active session.

                conversation_source
                          Indicates whether the local or partner LU is the
                          source of the conversation, that is, which LU started
                          the conversation by sending the allocation request.

                          APPC returns one of the following values:

                   LOCAL_LU
                             The local LU is the source of the conversation,
                             and the partner LU is the target of the
                             conversation.

                   PARTNER_LU
                             The partner LU is the source of the conversation,
                             and the local LU is the target of the
                             conversation.

                conversation_style
                          This 1-byte field indicates the conversation style in
                          effect for the specified conversation. APPC returns
                          one of the following values:

                   TWO_WAY_ALTERNATE
                             Indicates that information is transferred in both
                             directions, but only in one direction at a time.
                             This style of data transfer is also known as
                             half-duplex conversation.

                   TWO_WAY_SIMULTANEOUS
                             Indicates that information is transferred in both
                             directions at the same time.  This style of data
                             transfer is also known as full-duplex
                             conversation.

                source_send_byte_count
                          Indicates the number of bytes that the source LU has
                          sent on the conversation, up to the time that the
                          DISPLAY verb was issued. The count includes all SNA
                          RU bytes sent, including those in the FMH-5 (Attach),
                          FMH-7 (Error Description), SIGNAL, LUSTAT, and SNA
                          responses; it does not include SNA TH and RH bytes.

                          If the local LU is the target of the conversation,
                          this is the number of bytes the local LU has
                          received.

                target_send_byte_count
                          Indicates the number of bytes that the target LU has
                          sent on the conversation, up to the time that the
                          DISPLAY verb was issued. The count includes all SNA
                          RU bytes sent, including those in the FMH-5 (Attach),
                          FMH-7 (Error Description), SIGNAL, LUSTAT, and SNA
                          responses; it does not include SNA TH and RH bytes.

                          If the local LU is the source of the conversation,
                          this is the number of bytes the local LU has
                          received.


ΓòÉΓòÉΓòÉ 5.6. Session Information ΓòÉΓòÉΓòÉ

Session Information

The session_information_address points to the first byte of the returned end
point session information in the display data buffer.

See SESS_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Session Information Group Returned Parameters shows returned
          parameters that describe session information for the DISPLAY verb.

                    Session Information
                    length_of_initial_session_sectionn
                    number_of_sessionsn
                    total_number_of_sessionsn

                    Session Group (Repeated for each active session):
                    length_of_this_session_entryn
                    session_idvalue
                    conversation_idvalue
                    lu_aliasname
                    partner_lu_aliasname
                    mode_namename
                    send_ru_sizen
                    receive_ru_sizen
                    send_pacing_sizen
                    receive_pacing_sizen
                    link_namename
                    dafn
                    oafn
                    odain
                    type_of_session{SSCP_PU_SESSION | SSCP_LU_SESSION | LU_LU_SESSION}
                    type_of_connection{HOST_CONNECTION | PEER_CONNECTION}
                    fq_pc_idid
                    conversation_group_idid
                    local_fq_lu_namename
                    remote_fq_lu_namename
                    type_of_pacing{FIXED | ADAPTIVE}
                    pri_lu_indicator{LOCAL_LU | PARTNER_LU}
                    pri_lu_send_fmd_piu_countn
                    sec_lu_send_fmd_piu_countn
                    pri_lu_send_non_fmd_piu_countn
                    sec_lu_send_non_fmd_piu_countn
                    pri_lu_send_byte_countn
                    sec_lu_send_byte_countn
                    plu_slu_compression_level
                    plu_slu_compression_percent
                    slu_plu_compression_level
                    slu_plu_compression_percent

          Session Information Group Returned Parameters

 Return Codes

          length_of_initial_session_section
                    Indicates the size of the session information section up to
                    the first session group. It includes the size of this field
                    but not of any previous fields.

          number_of_sessions
                    Indicates the number of session groups returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_sessions
                    Indicates the total number of session groups.

          Session Group

          The following parameters are repeated for each active session.

          length_of_this_session_entry
                    Indicates the size of this session group. It includes the
                    size of this field but not of any previous fields.

          session_id
                    Indicates the 8-byte internal identifier of the session for
                    which this information is displayed.

          conversation_id
                    Indicates the 4-byte ID of the conversation currently using
                    this session.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, APPC pads it on the right with ASCII
                    blanks.

          partner_lu_alias
                    The 8-byte ASCII name used locally for the partner LU. The
                    name is not sent outside of the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, APPC pads it on the right with ASCII
                    blanks.

          mode_name
                    The 8-byte EBCDIC name for the mode. The mode name is used
                    to designate the network properties for a group of
                    sessions. This is the name of the mode as it is known
                    throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, APPC pads it on the right with EBCDIC
                    blanks.

          send_ru_size
                    Indicates the maximum RU size used on this session and this
                    mode_name for sending RUs.

          receive_ru_size
                    Indicates the maximum RU size used on this session and this
                    mode_name for receiving RUs.

          send_pacing_size
                    Indicates the size of the send pacing window on this
                    session.

          receive_pacing_size
                    Indicates the size of the receive pacing window on this
                    session.

          link_name
                    This is the 8-byte EBCDIC name of the local logical link
                    station padded on the right with 4 EBCDIC blanks.

          daf
                    Indicates the Destination address field for this session.
                    This field, together with the OAF and the ODAI, is part of
                    a unique 17-bit identifier APPC constructs internally to
                    keep track of each session using a given link.

          oaf
                    Indicates the Origin address field for this session. If
                    X'00', it indicates that the origin node is serving as a PU
                    2. Otherwise, this field, together with the DAF and ODAI,
                    is part of a unique 17-bit identifier APPC constructs
                    internally to keep track of each session using a given
                    link.

          odai
                    Indicates the Origin destination address indicator field
                    for this session. When bringing up a session, the sender of
                    the BIND sets this field to 0 if the local node contains
                    the primary link station on the link; otherwise, the value
                    1 indicates the BIND sender is the node containing the
                    secondary link station. This field, along with the OAF and
                    the DAF, is part of a unique 17-bit identifier APPC
                    constructs internally to keep track of each session using a
                    given link.

          type_of_session
                    Indicates the type of this session. You must specify one of
                    the following values:

             SSCP_PU_SESSION
                       This session is between a workstation physical unit and
                       a host system services control point. This type of
                       session exists if the local node contains a dependent
                       LU, or if the session has been solicited in order to
                       send alerts to the host.

             SSCP_LU_SESSION
                       This session is between a dependent LU and a host system
                       services control point.

             LU_LU_SESSION
                       This session is between two LUs.

          type_of_connection
                    Indicates whether the session activation protocol follows
                    the rules for an independent LU or a dependent LU.

             HOST_CONNECTION
                       For dependent LU protocols, the workstation LU is
                       defined as dependent at the host, the host LU sends the
                       session activation request (BIND), and each workstation
                       LU can support only one session at a time.

             PEER_CONNECTION
                       For independent LU protocols, an LU can send a BIND, and
                       can have multiple sessions to different partners, or
                       parallel sessions to the same partner LU.

          fq_pc_id
                    Indicates the network-unique fully qualified procedure
                    correlation identifier of the session.

          conversation_group_id
                    Indicates the session to be allocated. This value uniquely
                    identifies each active session.

          local_fq_lu_name
                    Indicates the fully qualified network name of the local LU
                    as it is known throughout the network.

          remote_fq_lu_name
                    Indicates the fully qualified network name of the remote LU
                    as it is known throughout the network.

          type_of_pacing
                    Indicates the type of pacing being used. APPC returns
                    either FIXED or ADAPTIVE.

          pri_lu_indicator
                    Indicates whether the local or partner LU is the primary LU
                    of the session, that is, which LU started the session by
                    sending the BIND request.

                    APPC returns one of the following values:

             LOCAL_LU
                       The local LU is the primary LU of the session, and the
                       partner LU is the secondary LU of the session.

             PARTNER_LU
                       The partner LU is the primary LU of the session, and the
                       local LU is the secondary LU of the session.

          pri_lu_send_fmd_piu_count
                    Indicates the number of FM data PIUs that the primary LU
                    has sent on the session, up to the time that the DISPLAY
                    verb was issued. The count includes only SNA FMD PIUs sent,
                    before segmenting (if any); it does not include non-FMD
                    PIUs, such as SC and DFC PIUs. A segmented PIU is counted
                    as one PIU.

                    If the local LU is the secondary LU of the session, this is
                    the number of FMD PIUs the local LU has received.

          sec_lu_send_fmd_piu_count
                    Indicates the number of FM data PIUs that the secondary LU
                    has sent on the session, up to the time that the DISPLAY
                    verb was issued. The count includes only SNA FMD PIUs sent,
                    before segmenting (if any); it does not include non-FMD
                    PIUs, such as SC and DFC PIUs. A segmented PIU is counted
                    as one PIU.

                    If the local LU is the primary LU of the session, this is
                    the number of FMD PIUs the local LU has received.

          pri_lu_send_non_fmd_piu_count
                    Indicates the number of non-FM data PIUs that the primary
                    LU has sent on the session, up to the time that the DISPLAY
                    verb was issued. The count includes only SNA non-FMD PIUs
                    sent, before segmenting (if any), such as SC and DFC PIUs.
                    A segmented PIU is counted as one PIU.

                    If the local LU is the secondary LU of the session, this is
                    the number of non-FMD PIUs the local LU has received.

          sec_lu_send_non_fmd_piu_count
                    Indicates the number of non-FM data PIUs that the secondary
                    LU has sent on the session, up to the time that the DISPLAY
                    verb was issued. The count includes only SNA non-FMD PIUs
                    sent, before segmenting (if any), such as SC and DFC PIUs.
                    A segmented PIU is counted as one PIU.

                    If the local LU is the primary LU of the session, this is
                    the number of non-FMD PIUs the local LU has received.

          pri_lu_send_byte_count
                    Indicates the number of bytes that the primary LU has sent
                    on the session, up to the time that the DISPLAY verb was
                    issued. The count includes all SNA PIU bytes sent, before
                    segmenting (if any), including those in FMD and non-FMD
                    PIUs. For segmented PIUs, it includes all TH, RH, and RU
                    bytes on the first segment, and the RU bytes on the middle
                    and last segments; it does not include the TH bytes on the
                    middle and last segments.

                    If the local LU is the secondary LU of the session, this is
                    the number of bytes the local LU has received.

          sec_lu_send_byte_count
                    Indicates the number of bytes that the secondary LU has
                    sent on the session, up to the time that the DISPLAY verb
                    was issued. The count includes all SNA PIU bytes sent,
                    before segmenting (if any), including those in FMD and
                    non-FMD PIUs. For segmented PIUs, it includes all TH, RH,
                    and RU bytes on the first segment, and the RU bytes on the
                    middle and last segments; it does not include the TH bytes
                    on the middle and last segments.

                    If the local LU is the primary LU of the session, this is
                    the number of bytes the local LU has received.

          plu_slu_compression_level
                    Specifies the active compression level for PLU to SLU data.

          plu_slu_compression_percent
                    Specifies a value representing the compression impact on
                    PLU to SLU data. (The value equals the total number of
                    compressed bytes divided by the total number of
                    uncompressed bytes, multiplied by 100.)

                    A value of zero (0) indicates that either compression_level
                    is none or that no data has been transferred.

          slu_plu_compression_level
                    Specifies the active compression level for SLU to PLU data.

          slu_plu_compression_percent
                    Specifies a value representing the compression impact on
                    SLU to PLU data. (The value equals the total number of
                    compressed bytes divided by the total number of
                    uncompressed bytes, multiplied by 100.)

                    A value of zero (0) indicates that either compression_level
                    is none or that no data has been transferred.


ΓòÉΓòÉΓòÉ 5.7. Active Link Information ΓòÉΓòÉΓòÉ

Active Link Information

The link_information_address points to the first byte of the returned logical
link information in the display data buffer.

See LINK_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Link Information Group Returned Parameters shows returned parameters
          that describe link information for the DISPLAY verb.

                    Active Link Information
                    length_of_initial_link_sectionn
                    number_of_linksn
                    total_number_of_linksn

                    Link Group (Repeated for each link group):
                    length_of_this_link_entryn
                    link_namename
                    dlc_namename
                    adapter_numbern
                    destination_address_lengthn
                    destination_addressaddress
                    inbound_outbound{INBOUND | OUTBOUND}
                    state{CONALS_PND | XID_PND | CONTACT_PND | CONTACTED |
                          DISC_PND | DISC_RQ}
                    deactivate_logical_link_flag{NOT_IN_PROGRESS | IN_PROGRESS}
                    number_of_sessionsn
                    ru_sizen
                    fq_adj_cp_namename
                    adj_node_type{LEN | EN | NN}
                    cp_cp_session_support{YES | NO}
                    connection_type{HOST | PEER | BOTH}
                    link_station_role{NEGOTIABLE | PRIMARY | SECONDARY}
                    line_type{SWITCHED | NON_SWITCHED}
                    tg_numbern
                    effective_capacityn
                    cost_per_connect_timen
                    cost_per_byten
                    propagation_delay{MINIMUM | LAN | TELEPHONE |
                                  PACKET_SWITCHED_NETWORK | SATELLITE |
                                  MAXIMUM}
                    security{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                           UNDERGROUND_CABLE | SECURE_CONDUIT |
                           GUARDED_CONDUIT | ENCRYPTED |
                           GUARDED_RADIATION}
                    user_defined_1n
                    user_defined_2n
                    user_defined_3n
                    pu_namename
                    subfields_startpointer
                    node_id_sentn
                    node_id_rcvdn
                    link_subfieldsn

          Link Information Group Returned Parameters

 Return Codes

          length_of_initial_link_section
                    Indicates the size of the link information section up to
                    the first link group. It includes the size of this field
                    but not of any previous fields.

          number_of_links
                    Indicates the number of logical links returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_links
                    Indicates the total number of logical links. For X.25, this
                    is the number of SNA X.25 virtual circuits.

                    Link Groups

                    The following parameters are repeated for each link group.

             length_of_this_link_entry
                       Indicates the size of this link group. It includes the
                       size of this field but not of any previous fields. In
                       addition, this parameter includes the length of any
                       link_subfields which may be present for this link.

             link_name
                       The 8-byte EBCDIC name of the local logical link station
                       is padded on the right with 4 EBCDIC blanks. This
                       logical link can be activated by specifying this name on
                       the ACTIVATE_LOGICAL_LINKS verb.

                       Note:  This is a type A EBCDIC character string. If the
                       name is less than 8 bytes, APPC pads it on the right
                       with EBCDIC blanks. Even though you cannot begin with an
                       EBCDIC "@" (X'7C'), the system inserts EBCDIC "@" in the
                       first character position for dynamically defined
                       implicit links.  Therefore, the data returned may
                       contain an EBCDIC "@" in the first character position of
                       this field.

             dlc_name
                       The 8-byte ASCII name of the local data link control
                       (DLC). This is the name used to configure a DLC in the
                       Communications Manager DLC profile.

                o 'ETHERAND'
                o 'IBMPCNET'
                o 'IBMTRNET'
                o 'SDLC   '
                o 'TWINAX  '
                o 'X25DLC  '
                o 'IDLC   '

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, APPC pads it on the right with ASCII
                       blanks.

             adapter_number
                       Indicates the adapter number for this link.

             destination_address_length
                       A 1-byte field that indicates how many leftmost bytes of
                       the 32 bytes in the next field (destination_address) are
                       significant.

             destination_address
                       Indicates the address of the remote link station.

                       For X.25, this field contains a network address if the
                       virtual circuit type is SWITCHED. If the virtual circuit
                       type is PERMANENT, it contains the number of the PVC
                       that is used to communicate with the remote station. The
                       first byte of the destination address distinguishes a
                       permanent from a switched connection. If the first byte
                       is X'FF', the connection is permanent; otherwise, it is
                       switched.

             inbound_outbound
                       Indicates if this link is an inbound or outbound link.

                INBOUND
                          This link was activated as a result of action by the
                          remote node.

                OUTBOUND
                          This link was activated as a result of action by the
                          local node.

             state
                       Indicates the state of the link. The link state is one
                       of the following:

                CONALS_PND
                          The process to bring up the link has begun but XID
                          negotiation has not started.

                XID_PND
                          XID negotiation is in progress.

                CONTACT_PND
                          XID negotiation has been completed but the final
                          response from the DLC has not been received.

                CONTACTED
                          The link is fully functioning.

                DISC_PND
                          A request to disconnect the link has been issued to
                          the DLC.

                DISC_RQ
                          The operator has requested that the link be
                          disconnected.

             deactivate_logical_link_flag
                       Indicates whether a DEACTIVATE_LOGICAL_LINK verb with
                       type(SOFT) to deactivate this link has been issued. The
                       link is deactivated when all sessions on the link are
                       deactivated. APPC returns one of the following values:

                NOT_IN_PROGRESS
                          Link deactivation is not in progress.

                IN_PROGRESS
                          Link deactivation is currently in progress.

             number_of_sessions
                       Indicates the number of sessions that are currently on
                       this link.

             ru_size
                       Indicates the amount of the data transmitted on this
                       link.

             fq_adj_cp_name
                       Specifies the fully qualified name for the control point
                       (CP) in the adjacent node. This name is a 17-byte EBCDIC
                       name consisting of two 8-byte Type A EBCDIC character
                       strings concatenated by an EBCDIC period.

             adjacent_node_type
                       Specifies the APPN node type of the adjacent node. APPC
                       returns one of the following values:

                LEN
                          Specifies that the adjacent node type is a low-entry
                          networking node.

                EN
                          Specifies that the adjacent node type is an APPN end
                          node.

                NN
                          Specifies that the adjacent node type is an APPN
                          network node.

             cp_cp_session_support
                       Specifies whether the link is to support CP-CP sessions.
                       APPC returns either YES or NO.

             connection_type
                       Indicates the type of connection. The valid values are:

                HOST
                          For dependent LU protocols, the workstation LU is
                          defined as dependent at the host, the host LU sends
                          the session activation request (BIND), and each
                          workstation LU can support only one session at a
                          time.

                PEER
                          For independent LU protocols, an LU can send a BIND,
                          and can have multiple sessions to different partners,
                          or parallel sessions to the same partner LU.

                BOTH
                          Both dependent and independent protocols are
                          supported on this link.

             link_station_role
                       Specifies the link station role to be used for this
                       link. You must specify one of the following values:

                NEGOTIABLE
                          Specifies this link will negotiate its role during
                          link activation via XID exchange.

                PRIMARY
                          Specifies this link as the primary link station.

                SECONDARY
                          Specifies this link as the secondary link station.

             line_type
                       Indicates the type of line connection. APPC returns
                       either SWITCHED or NONSWITCHED.

             tg_number
                       Specifies the transmission group number.

             effective_capacity
                       The highest bit transmission rate for the logical link
                       before the link is considered overloaded. You can obtain
                       the effective capacity value by multipying the link
                       speed by a user defined maximum load factor. The value
                       is expressed in bits per second.

             cost_per_connect_time
                       An integer value that expresses the relative value of
                       using this link. The units are user defined, and must be
                       based on the applicable tariffs of the transmission
                       facility being used by the link. The
                       cost_per_connect_time values that are assigned must be
                       proportional and must reflect the relative expense of
                       the link as compared to all other links in the network.
                       A value of 0 means that connections using this link are
                       free.

                       Cost per connect time is network specific and is not
                       intended to be uniform across networks (except where two
                       or more networks coordinate assignment of relative cost
                       values among themselves).

             cost_per_byte
                       An integer value that expresses a relative cost of
                       transmitting a byte over this link. The units are user
                       defined and must be based on the actual cost of
                       transmitting data over the link. A value of 0 means that
                       transmitting a byte of data over the link is free.

                       Cost per byte is network specific and is not intended to
                       be uniform across networks (except where two or more
                       networks coordinate assignment of relative cost values
                       among themselves).

             propagation_delay
                       This value represents the amount of time it takes for a
                       signal to travel the length of the logical link, in
                       microseconds. The following list describes the valid
                       values, with MINIMUM representing the least propagation
                       delay and MAXIMUM representing the longest propagation
                       delay.

                MINIMUM
                          Specifies there is no propagation delay.

                LAN
                          Specifies that propagation delay is less than 480
                          microseconds.

                TELEPHONE
                          Specifies a delay between 480 and 49152 microseconds.

                PACKET_SWITCHED_NETWORK
                          Specifies a delay between 49152 and 245760
                          microseconds.

                SATELLITE
                          Specifies a delay longer than 245760 microseconds.

                MAXIMUM
                          Specifies the maximum delay allowed.

             security
                       This parameter specifies the security value for this
                       link. The following list describes the valid values for
                       these parameters in the order of their effectiveness.

                NONSECURE
                          Specifies that no security exists, such as satellite
                          links or underground lines.

                PUBLIC_SWITCHED_NETWORK
                          Specifies that data transmitted over this adapter
                          will flow through a public switched network.

                UNDERGROUND_CABLE
                          Specifies transmission over a secure underground
                          cable.

                SECURE_CONDUIT
                          Specifies that the line is secure conduit that is not
                          guarded, such as pressurized pipe.

                GUARDED_CONDUIT
                          Specifies that the conduit is protected against
                          physical tapping.

                ENCRYPTED
                          Specifies that the adapter, or the system software
                          that controls the adapter, encrypts the data
                          transmitted over the line.

                GUARDED_RADIATION
                          Specifies that the line is protected against physical
                          and radiation tapping.

             user_defined_1
                       The value of the first user-defined transmission group
                       (TG) characteristic for this TG.

             user_defined_2
                       The value of the second user-defined TG characteristic
                       for this TG.

             user_defined_3
                       The value of the third user-defined TG characteristic
                       for this TG.

             pu_name
                       The 8-character identifier that corresponds to a host
                       system link used for dependent LU sessions.  If multiple
                       PUs exist, this allows multiple host systems to
                       concurrently issue ACTPUs to the same physical
                       workstation.

             subfields_start
                       This pointer contains the address of the location in the
                       buffer where the link_subfields begins.

             node_id_sent
                       Indicates the 8-digit hexadecimal value of the Node
                       Identification field of the DLC XID frame sent to the
                       remote partner.  For a description of the DLC XID frame,
                       see SNA Formats.

             node_id_rcvd
                       Indicates the 8-digit hexadecimal value of the Node
                       Identification field of the DLC XID frame received from
                       the remote parter.  For a description of the DLC XID
                       frame, see SNA Formats.

             link_subfields
                       If the returned value of the subfields_start parameter
                       is non-null, a variable-length list of variable-format
                       subfields will follow the fixed portion of the link
                       information.  These subfields will provide additional
                       details about this logical link, and may include some or
                       all of the following kinds of subfields :

                o Product-specific subfields, which are used to convey
                  protocol-specific information pertaining to a given link.

                o Primitive-specific subfield, which returns information from
                  the Connection Manager component pertaining to a given link.

                o Network-specific subfields, which return information
                  maintained by the switched network traversed by the link.

                o CCITT subfields, which describe switched-link information
                  such as telephone numbers.

                       Additional information concerning the information
                       returned by each subfield may be found in Verb Control
                       Blocks and Hexadecimal Codes.


ΓòÉΓòÉΓòÉ 5.8. LU 0 to 3 Information ΓòÉΓòÉΓòÉ

LU 0 to 3 Information

The lu_0_to_3_information_address points to the first byte of the returned LU
type 0, 1, 2, and 3 information in the display data buffer.

See LU_0_3_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          LU 0 to 3 Information Group Returned Parameters shows returned
          parameters that describe LU types 0, 1, 2, and 3 information for the
          DISPLAY verb.

                    LU 0 to 3 Information
                    length_of_initial_lu_0_to_3_sectionn
                    number_of_lus_0_to_3n

                    LU Group (Repeated for each LU):
                    length_of_this_lu_0_to_3_entryn
                    access_type{3270_EMULATION | LUA}
                    lu_type_0_to_3{LU0 | LU1 | LU2 | LU3}
                    lu_dafn
                    lu_short_namename
                    lu_long_namename
                    lu_sess_idvalue
                    lu_dlc_namename
                    lu_adapter_numbern
                    lu_destination_address_lengthn
                    lu_destination_addressaddress
                    sscp_lu_session_state{ACTIVATED | NOT_ACTIVATED |
                                    ACTIVATING | NOT_ACTIVATING |
                                    DEACTIVATING | NOT_DEACTIVATING |
                                    DETACHING | NOT_DETACHING}
                    lu_lu_session_state{BOUND | NOT_BOUND | BINDING |
                                  NOT_BINDING | UNBINDING | NOT_UNBINDING}
                    link_namename
                    pu_namename
                    partner_lu_namename
                    plu_slu_compression_level
                    slu_plu_compression_level

          LU 0 to 3 Information Group Returned Parameters

 Return Codes

          length_of_initial_lu_0_to_3_section
                    Indicates the size of the LU 0 to 3 section up to the first
                    LU group. It includes the size of this field but not of any
                    previous fields.

          number_of_lus_0_to_3
                    Indicates the number of LU groups.

                    LU Group

                    The following parameters are repeated for each LU.

             length_of_this_lu_0_to_3_entry
                       Indicates the size of this LU group. It includes the
                       size of this field but not of any previous fields.

             access_type
                       This field indicates the source of the LU information.
                       The source can be 3270_EMULATION or LUA.

             lu_type_0_to_3
                       Indicates the type of LU. APPC returns one of the
                       following values:

                o LU0
                o LU1
                o LU2
                o LU3

             lu_daf
                       Indicates the network addressable unit (NAU) of the LU
                       for which this information is displayed.

             lu_short_name
                       Indicates the 1-byte ASCII short name of the LU.

             lu_long_name
                       Indicates the 8-byte ASCII long name of the LU.

             lu_sess_id
                       Indicates the 8-byte internal ID of the LU-LU session.

             lu_dlc_name
                       The ASCII name of the adapter that is used for the
                       partner LU. For X.25, an adapter corresponds to a
                       physical link. Only the following ASCII strings are
                       allowed:

                o 'ETHERAND'
                o 'IBMPCNET'
                o 'IBMTRNET'
                o 'SDLC   '
                o 'TWINAX  '
                o 'X25DLC  '
                o 'IDLC   '

             lu_adapter_number
                       Indicates the adapter number for the host link.

             lu_destination_address_length
                       A 1-byte field that indicates how many leftmost bytes of
                       the 32 bytes in the next field (lu_destination_address)
                       are significant.

             lu_destination_address
                       Indicates the address of the remote link station. For
                       X.25, this field contains a network address if the
                       virtual circuit type is SWITCHED. If the virtual circuit
                       type is PERMANENT, the field contains the number of the
                       PVC that is used to communicate with the remote station.

                       This information is not meaningful for a template entry
                       or for an SDLC adapter.

             sscp_lu_session_state
                       Indicates the state of the SSCP-LU session.  Only one of
                       these bits may be on (have a value of 1).  If none of
                       the bits are on, then the SSCP-LU session is in the
                       DEACTIVATED state.

             lu_lu_session_state
                       Indicates the state of the LU-LU session.  Only one of
                       these bits may be on (have a value of 1).  If none of
                       the bits are on, the LU_LU session is in the NOT_BOUND
                       state.

             link_name
                       The 8-byte EBCDIC name of the local logical link station
                       is padded on the right with 4 EBCDIC blanks. This
                       logical link can be activated by specifying this name on
                       the ACTIVATE_LOGICAL_LINKS verb.

                       Note:  This is a type A EBCDIC character string. If the
                       name is less than 8 bytes, APPC pads it on the right
                       with EBCDIC blanks. Even though you cannot begin with an
                       EBCDIC "@" (X'7C'), the system inserts EBCDIC "@" in the
                       first character position for dynamically defined
                       implicit links.  Therefore, the data returned may
                       contain an EBCDIC "@" in the first character position of
                       this field.

             pu_name
                       The 8-character identifier that correspondes to a host
                       system link used for dependent LU sessions.  This allows
                       multiple host systems to issue ACTPUs to the same
                       physical workstation.

             partner_lu_name
                       Regarding LUA access, this field indicates the partner
                       LU of the associated LU.

             plu_slu_compression_level
                       Specifies the active compression level for PLU to SLU
                       data.

             slu_plu_compression_level
                       Specifies the active compression level for SLU to PLU
                       data.


ΓòÉΓòÉΓòÉ 5.9. SNA Gateway Information ΓòÉΓòÉΓòÉ

SNA Gateway Information

The gateway_information_address points to the first byte of the returned SNA
gateway information in the display data buffer.

See GW_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          SNA Gateway Information Group Returned Parameters shows returned
          parameters that describe SNA gateway information for the DISPLAY
          verb.

          The following LUs are displayed:

          o Dedicated LUs at the workstation (pool class is 0)
          o Pooled LUs assigned to LUs at the workstation (pool class and
            ws_local_address are nonzero)
          o Pooled LUs not assigned to a workstation LU (pool class is nonzero,
            ws_local_address is 0)

          Nondedicated workstation LUs not assigned to a pooled LU are not
          displayed.

                    SNA Gateway Information
                    length_of_initial_gw_sectionn
                    number_of_gw_lusn

                    Workstation Group (Repeated for each gateway LU)
                    length_of_this_gw_entryn
                    ws_lu_namename
                    ws_pool_namename
                    ws_logoff_time_leftsigned_value
                    ws_local_addressvalue
                    host_local_addressvalue
                    ws_lu_type{LU0 | LU1 | LU2 | LU3 | LU6.2 | UNKNOWN}
                    host_lu_namefq_name
                    ws_dlc_namename
                    ws_adapter_numbern
                    ws_destination_address_lengthn
                    ws_destination_addressaddress
                    host_link_namename
                    ws_link_namename
                    ws_lu_status{LU_CP_ACTIVE_ONLINE{YES | NO} |
                              LU_CP_ACTIVE_OFFLINE{YES | NO} |
                              LU_CP_PENDING_INITIATION{YES | NO} |
                              LU_CP_PENDING_TERMINATION{YES | NO} |
                              LU_LU_ACTIVE_{YES | NO} |
                              LU_LU_PENDING_INITIATION{YES | NO} |
                              LU_LU_PENDING_TERMINATION{YES | NO} |
                              WS_LINK_ACTIVE{YES | NO}}

          SNA Gateway Information Group Returned Parameters

 Return Codes

          length_of_initial_gw_section
                    Indicates the size of the gateway LU section up to the
                    first gateway LU. It includes the size of this field but
                    not of any previous fields.

          number_of_gw_lus
                    Indicates the number of active or connected LUs at
                    workstations supported by this gateway.  This number is
                    returned by the DISPLAY verb into your program's buffer.

                    Workstation Group

                    The following parameters are repeated for each gateway LU.

             length_of_this_gw_entry
                       Indicates the size of this gateway LU entry. It includes
                       the size of this field but not of any previous fields.

             ws_lu_name
                       Indicates the 8-byte EBCDIC name of the workstation LU
                       for which this information is returned.

                       This is a Type AE name EBCDIC character string. If this
                       name is less than 8 characters, APPC pads it on the
                       right with EBCDIC blanks.

             ws_pool_name
                       Indicates the pool name for this LU.  This is a string
                       of 8 user-defined characters. A value of blank,
                       indicates a dedicated LU not in any pool class.

             ws_logoff_time_left
                       If a positive (+) value is present, this parameter
                       indicates the time remaining before this LU can be
                       considered for automatic logoff, provided the pool class
                       has been configured properly. If a negative (-) value is
                       present, this parameter represents the number of minutes
                       since the LU became eligible for automatic logoff.

                    Programming Note

             o Automatic logoff applies only to pooled LUs.

             o A pool class does not have to be configured for automatic
               logoff.

             o If a given LU is eligible for automatic logoff, the LU may not
               actually be logged of if no other requests are waiting to
               establish a session with an LU in the pool class.

          ws_local_address
                    Indicates the NAU address of the workstation LU, as
                    configured at the workstation. An address of 0 indicates a
                    pooled LU that has not been assigned.

          host_local_address
                    Indicates the NAU address of the workstation LU as
                    configured at the host.

          ws_lu_type
                    Indicates the type of LU at the workstation. The valid
                    types include:

             o LU0
             o LU1
             o LU2
             o LU3
             o LU6.2
             o UNKNOWN

          host_lu_name
                    Indicates the fully qualified EBCDIC name of the host LU.
                    The fully qualified name consists of the name of the
                    network to which the host LU belongs, a period (.), and the
                    host's lu_name as it is known in the network.

                    The host_lu_name consists of two Type A name EBCDIC
                    character strings. If this name is less than 17 characters
                    (including the EBCDIC period), APPC pads it on the right
                    with EBCDIC blanks.

          ws_dlc_name
                    The ASCII name of the adapter that is used for this gateway
                    connection. For X.25, an adapter corresponds to a physical
                    link. Only the following ASCII strings are allowed:

             o 'ETHERAND'
             o 'IBMPCNET'
             o 'IBMTRNET'
             o 'SDLC   '
             o 'TWINAX  '
             o 'X25DLC  '
             o 'IDLC   '

          ws_adapter_number
                    Indicates the adapter number for the workstation. A
                    returned value of X'FF' indicates unknown. This is
                    applicable only for a pooled LU that has not been assigned.
                    This is indicated by a workstation local address of 0.

          ws_destination_address_length
                    A 1-byte field that indicates how many leftmost bytes of
                    the 1 bytes in the next field (ws_destination_address) are
                    significant.

          ws_destination_address
                    Indicates the address of the remote link station.

                    For X.25, this field contains a network address if the
                    virtual circuit type is SWITCHED. If the virtual circuit
                    type is PERMANENT, the field contains the number of the PVC
                    that is used to communicate with the remote station.

                    Note:  This information is not meaningful for a template
                    entry or for an SDLC adapter.

          host_link_name
                    Indicates the link between the workstation and the host.

          ws_link_name
                    Indicates the link between the workstation and the gateway.

          ws_lu_status
                    Indicates the status of the workstation LU. APPC can return
                    more than one status flag. The different status flags
                    include:

             LU_CP_ACTIVE_ONLINE
                       Indicates if the SSCP-LU session on the workstation is
                       active. APPC returns either YES or NO.

             LU_CP_ACTIVE_OFFLINE
                       Indicates if the SSCP-LU session is established as soon
                       as the workstation link is activated. APPC returns
                       either YES or NO.

             LU_CP_PENDING_INITIATION
                       Indicates if the SSCP-LU session on the workstation is
                       currently being activated. APPC returns either YES or
                       NO.

             LU_CP_PENDING_TERMINATION
                       Indicates if the SSCP-LU session is currently being
                       ended. APPC returns either YES or NO.

             LU_LU_ACTIVE
                       Indicates if the LU-LU session is active. APPC returns
                       either YES or NO.

             LU_LU_PENDING_INITIATION
                       Indicates if the LU-LU session is currently being
                       activated. APPC returns either YES or NO.

             LU_LU_PENDING_TERMINATION
                       Indicates if the LU-LU session is currently being ended.
                       APPC returns either YES or NO.

             WS_LINK_ACTIVE
                       Indicates if the link to the workstation is active. APPC
                       returns either YES or NO.


ΓòÉΓòÉΓòÉ 5.10. X.25 Physical Link Information ΓòÉΓòÉΓòÉ

X.25 Physical Link Information

The x.25_physical_link_information_address points to the first byte of the
returned X.25 physical link information in the display data buffer.

See X25_PHYSICAL_LINK_INFO_SECT for the DISPLAY Verb Control Block for the
format of the returned information.

          X.25 Physical Link Information Group Returned Parameters shows
          returned parameters that describe X.25 physical link information for
          the DISPLAY verb.

                    X.25 Physical Link Information
                    length_of_initial_x.25_physical_link_sectionn
                    number_of_x.25_physical_linksn
                    number_of_x.25_physical_link_entriesn

                    X.25 Link Group (Repeated for each X.25 link group):
                    length_of_this_x.25_physical_link_entryn
                    link_namename
                    link_commentsname
                    adapter_slot_numbern
                    link_type{LEASED_LINE | VX32}
                    link_modevalue{DISCONNECT | CONNECT | AUTO_CONNECT}
                    link_state{CONNECTING | CONNECTED | ERROR_LEVEL_1 |
                            ERROR_LEVEL_2 | DISCONNECTING | DISCONNECTED |
                            ADAPTER_ERROR | ADAPTER_ACCESS_ERROR |
                            INCOMING_WAIT}
                    link_direction{INCOMING | OUTGOING | 2-WAY}
                    number_of_active_pvcsn
                    total_number_of_pvcsn
                    number_of_active_svcsn
                    number_of_incoming_svcsn
                    number_of_2_way_svcsn
                    number_of_outgoing_svcsn


          X.25 Physical Link Information Group Returned Parameters

 Return Codes

          length_of_initial_x.25_physical_link_section
                    Indicates the size of the X.25 physical link section up to
                    the first X.25 physical link group. It includes the size of
                    this field but not of any previous fields.

          number_of_x.25_physical_links
                    Indicates the total number of X.25 physical links
                    configured.

          number_of_x.25_physical_link_entries
                    Indicates the total number of X.25 physical links for which
                    information is returned. This number can be smaller than
                    the number of links configured if the DISPLAY verb buffer
                    is not large enough.

                    X.25 Link Group

                    The following parameters are repeated for each X.25 link
                    group.

             length_of_this_x.25_physical_link_entry
                       Indicates the size of this X.25 link group. It includes
                       the size of this field but not of any previous fields.

             link_name
                       This field contains an alphanumeric link profile name
                       that determines the link on which the call is made. A
                       link profile with this name must have been set up during
                       configuration. This field is not used when the calling
                       address is a directory name.

             link_comments
                       Indicates the comments (up to 60 bytes) configured with
                       this X.25 physical link.

             adapter_slot_number
                       Indicates the adapter slot number for this physical
                       link.

             link_type
                       Specifies the type of link.

                LEASED_LINE
                          Indicates the use of nonswitched links.

                VX32
                          Indicates the use of a Transpac VX32 modem, which
                          implements a variant of the X.32 protocol.

             link_mode
                       Indicates the mode of the physical link.

                DISCONNECT
                          The API disconnects the link.

                CONNECT
                          The API attempts to connect the link.

                AUTO_CONNECT
                          The API attempts to connect the link whenever an
                          application requires the link to make a call, receive
                          a call, or allocate a PVC on the link.

             link_state
                       Indicates the status of the physical link.

                CONNECTING
                          The link is being established.

                CONNECTED
                          The link is established.

                ERROR_LEVEL_1
                          An error has been detected at the physical level.

                ERROR_LEVEL_2
                          An error has been detected at the frame level.

                DISCONNECTING
                          The link is being terminated.

                DISCONNECTED
                          There is no established link connection.

                ADAPTER_ERROR
                          An error has been detected on the adapter for this
                          link.

                ADAPTER_ACCESS_ERROR
                          The adapter for this link is not installed or cannot
                          be accessed.

                INCOMING_WAIT
                          A VX32 type of link is ready to receive an incoming
                          call.

             link_direction
                       Indicates the current direction of calls that the link
                       will support. This parameter is meaningful only if the
                       link_state parameter is CONNECTED.

                INCOMING
                          Calls can only be received.

                OUTGOING
                          Calls can only be sent.

                2-WAY
                          Calls can be sent or received.

             number_of_active_pvcs
                       Indicates the number of active permanent virtual
                       circuits.

             total_number_of_pvcs
                       Indicates the number of permanent virtual circuits
                       configured.

             number_of_active_svcs
                       Indicates the number of active switched virtual
                       circuits.

             number_of_incoming_svcs
                       Indicates the number of switched virtual circuits
                       configured as incoming SVCs.

             number_of_2_way_svcs
                       Indicates the number of switched virtual circuits
                       configured as two-way SVCs.

             number_of_outgoing_svcs
                       Indicates the number of switched virtual circuits
                       configured as outgoing SVCs.


ΓòÉΓòÉΓòÉ 5.11. System Default Information ΓòÉΓòÉΓòÉ

System Default Information

The system_defaults_information_address returns information about the default
LU and mode names and information about the default parameters for inbound and
outbound implicit partners.

See SYS_DEF_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          System Default Information Group Returned Parameters shows returned
          parameters that describe system default information for the DISPLAY
          verb.

                    System Default Information
                    default_mode_namename
                    default_local_lu_namename
                    implicit_partner_lu_support{YES | NO}
                    maximum_held_alertsn
                    default_tp_conversation_security_rqd{YES | NO}
                    maximum_mc_ll_send_sizen
                    directory_for_inbound_attachesname
                    default_tp_operation{QUEUED_OPERATOR_STARTED |
                                       QUEUED_OPERATOR_PRELOADED |
                                       QUEUED_AM_STARTED |
                                       NONQUEUED_AM_STARTED}
                    default_tp_program_type{BACKGROUND | FULL_SCREEN |
                                       PRESENTATION_MANAGER |
                                       VIO_WINDOWABLE}

          System Default Information Group Returned Parameters

 Return Codes

          default_mode_name
                    Indicates the mode name whose parameters are used when an
                    undefined mode name is either sent or received.

                    All binary zeros indicates that no default mode name is
                    defined.

          default_local_lu_name
                    Indicates the LU name of the local LU. The default LU is
                    used when all binary zeros is specified for the lu_alias
                    parameter on the TP_STARTED, CNOS,
                    DEACTIVATE_CONVERSATION_GROUP, or DEACTIVATE_SESSION verb.

                    Note:  To get the lu_alias of the default_lu, you can get
                    the LU Definition Information and use the
                    default_local_lu_name as a key into the returned LU
                    Definitions to determine which defined LU is the
                    default_lu.

          implicit_partner_lu_support
                    Indicates whether inbound implicit partner LU support is
                    enabled. APPC returns one of the following values:

             YES       Indicates BINDs are accepted from undefined partners.
             NO        Indicates that BINDs are accepted only if the partner is
                       defined.

          maximum_held_alerts
                    Specifies the number of alerts that will be held by
                    Communications Manager if there is not an active link to a
                    focal point.

          default_tp_conversation_security_rqd
                    Specifies whether or not conversation security will be used
                    for default TPs. APPC returns one of the following values:

             YES       Specifies that the incoming attach must contain a valid
                       user_id and password.

             NO        Specifies that the incoming attach does not have to
                       contain security information.

          maximum_mc_ll_send_size
                    Indicates the maximum size of a logical record to be used
                    on a mapped conversation for sending data to either the
                    inbound or outbound implicit remote LU. The size is the
                    number of bytes in the logical record, as indicated in the
                    LL field of the record.

          directory_for_inbound_attaches
                    Specifies the name of an OS/2 directory to be used by the
                    attach manager when no DEFINE_TP verb has been issued for
                    the TP name specified on the incoming attach. An asterisk
                    (*) indicates that the current path is used to find the TP.

          default_tp_operation
                    Specifies how an OS/2 program is to be started, when it is
                    started due to an incoming attach.

                    APPC returns one of the following values:

             QUEUED_OPERATOR_STARTED
                       This indicates that one version of the program will be
                       run at a time. If the Attach arrives and the program has
                       not been started yet, Communications Manager will issue
                       a message to the operator to start the specified
                       program. Subsequent Attaches that arrive while the
                       program is active will be queued.

             QUEUED_OPERATOR_PRELOADED
                       This indicates that one version of the program will be
                       run at a time. If the Attach arrives and the program has
                       not been started yet, no message appears. Subsequent
                       Attaches that arrive while the program is active will be
                       queued.

             QUEUED_AM_STARTED
                       This indicates that one version of the program will be
                       run at a time and will be started by the APPC attach
                       manager. Subsequent Attaches that arrive while the
                       program is active will be queued.

             NONQUEUED_AM_STARTED
                       This indicates that multiple copies of the program will
                       be run at a time and will be started by the APPC attach
                       manager.

          default_tp_program_type
                    Specifies the type of screen group that will be associated
                    with this OS/2 program, which has not been defined.

                    APPC returns one of the following values:

             BACKGROUND
                       This specifies that this program will not have a screen
                       group and will run as a detached program.

             FULL_SCREEN
                       This specifies that this program will have a screen
                       group but will not run under the Presentation Manager
                       interface.

             PRESENTATION_MANAGER
                       This specifies that this program will have a screen
                       group and will run under the Presentation Manager
                       interface.

             VIO_WINDOWABLE
                       This specifies that this program will have a screen
                       group and will run under the Presentation Manager
                       interface and is also required to make OS/2 VIO calls.


ΓòÉΓòÉΓòÉ 5.12. Adapter Information ΓòÉΓòÉΓòÉ

Adapter Information

The adapter_information_address returns information about the characteristics
of the communications adapters configured.

See ADAPTER_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Adapter Information Group Returned Parameters shows returned
          parameters that describe adapter information for the DISPLAY verb.

                    Adapter Information
                    length_of_initial_sectionn
                    number_of_adaptersn
                    total_number_of_adaptersn

                    Adapter Group (Repeated for each adapter group):
                    length_of_adapter_datan
                    dlc_namename
                    adapter_numbern
                    link_station_role{NEGOTIABLE | PRIMARY | SECONDARY}
                    effective_capacityn
                    cost_per_connect_timen
                    cost_per_byten
                    propagation_delay{MINIMUM | LAN | TELEPHONE |
                                  PACKET_SWITCHED_NETWORK | SATELLITE |
                                  MAXIMUM}
                    security{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                           UNDERGROUND_CABLE | SECURE_CONDUIT |
                           GUARDED_CONDUIT | ENCRYPTED |
                           GUARDED_RADIATION}
                    user_defined_1n
                    user_defined_2n
                    user_defined_3n
                    line_type{SWITCHED | NONSWITCHED}
                    limited_resource{YES | NO}
                    limited_resource_timeoutn
                    abm_support{YES | NO}
                    max_btu_sizen
                    receive_windown
                    send_windown
                    max_ls_usedn
                    adapter_active{YES | NO}
                    adapter_max_activation_attemptsn
                    adapter_type{NON-DIALED | AUTO-DIALED}

          Adapter Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Specifies the length in bytes from the beginning of the
                    adapter information to the beginning of the first adapter
                    data entry.

          number_of_adapters
                    Specifies the number of defined adapter groups returned by
                    the DISPLAY verb into your program's buffer.

          total_number_of_adapters
                    Specifies the total number of defined adapters.

                    Adapter Group

                    The following parameters are repeated for each adapter
                    group.

             length_of_adapter_data
                       Specifies the length in bytes from the beginning of this
                       adapter data entry to the beginning of the next.

             dlc_name
                       The 8-byte ASCII name of the local data link control
                       (DLC). This is the name used to configure a DLC in the
                       Communications Manager DLC profile.

                o 'ETHERAND'
                o 'IBMPCNET'
                o 'IBMTRNET'
                o 'SDLC   '
                o 'TWINAX  '
                o 'X25DLC  '
                o 'IDLC   '

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, APPC pads it on the right with ASCII
                       blanks.

             adapter_number
                       Specifies a particular communications adapter number.

             link_station_role
                       Specifies the link station role to be used for this
                       link. You must specify one of the following values:

                NEGOTIABLE
                          Specifies this link will negotiate its role during
                          link activation via XID exchange.

                PRIMARY
                          Specifies this link as the primary link station.

                SECONDARY
                          Specifies this link as the secondary link station.

             effective_capacity
                       The highest bit transmission rate for the logical link
                       before the link is considered overloaded. You can obtain
                       the effective capacity value by multiplying the link
                       speed by a user defined maximum load factor. The value
                       is expressed in bits per second.

             cost_per_connect_time
                       An integer value in the range of 0 to 255 that expresses
                       the relative cost of using this link. The units are user
                       defined. The cost per connect time values must be
                       proportional to applicable tariffs of the transmission
                       facility being used by the link and must reflect the
                       relative expense of the link as compared to all other
                       links in the network. A value of 0 means that
                       connections using this link are free.

                       Cost per connect time is network specific and is not
                       intended to be uniform across networks (except where two
                       or more networks coordinate assignment of relative cost
                       values among themselves).

             cost_per_byte
                       An integer value in the range 0 to 255 that expresses a
                       relative cost of transmitting a byte over this link. The
                       units are user defined. Cost per byte value should be
                       proportional to the actual cost of transmitting data
                       over the link. A value of 0 means that transmitting a
                       byte of data over the link is free.

                       Cost per byte is network specific and is not intended to
                       be uniform across networks (except where two or more
                       networks coordinate assignment of relative cost values
                       among themselves).

             propagation_delay
                       This value represents the amount of time it takes for a
                       signal to travel the length of the logical link, in
                       microseconds. The following list describes the valid
                       values, with MINIMUM representing the least propagation
                       delay and MAXIMUM representing the longest propagation
                       delay.

                MINIMUM
                          Specifies there is no propagation delay.

                LAN
                          Specifies that propagation delay is less than 480
                          microseconds.

                TELEPHONE
                          Specifies a delay between 480 and 49152 microseconds.

                PACKET_SWITCHED_NETWORK
                          Specifies a delay between 49152 and 245760
                          microseconds.

                SATELLITE
                          Specifies a delay longer than 245760 microseconds.

                MAXIMUM
                          Specifies the maximum delay allowed.

             security
                       This parameter specifies the security value for this
                       adapter. The following list describes the valid values
                       for these parameters in the order of their
                       effectiveness.

                NONSECURE
                          Specifies that no security exists, such as satellite
                          links or underground lines.

                PUBLIC_SWITCHED_NETWORK
                          Specifies that data transmitted over this adapter
                          will flow through a public switched network.

                UNDERGROUND_CABLE
                          Specifies transmission over a secure underground
                          cable.

                SECURE_CONDUIT
                          Specifies that the line is secure conduit that is not
                          guarded, such as pressurized pipe.

                GUARDED_CONDUIT
                          Specifies that the conduit is protected against
                          physical tapping.

                ENCRYPTED
                          Specifies that the adapter, or the system software
                          that controls the adapter, encrypts the data
                          transmitted over the line.

                GUARDED_RADIATION
                          Specifies that the line is protected against physical
                          and radiation tapping.

             user_defined_1
                       The value of the first user-defined transmission group
                       (TG) characteristic for this TG.

             user_defined_2
                       The value of the second user-defined TG characteristic
                       for this TG.

             user_defined_3
                       The value of the third user-defined TG characteristic
                       for this TG.

             line_type
                       Specifies the type of link connection. APPC returns
                       either SWITCHED or NONSWITCHED.

             limited_resource
                       Specifies whether the link stations on this adapter are
                       considered a limited resource, due to the cost of
                       maintaining an active link, the link station capacity of
                       the adapter, or some other reason. APPC returns either
                       YES or NO.

             limited_resource_timeout
                       If this adapter is a limited resource, specifies the
                       length of time that elapses before a link on this
                       adapter is deactivated due to no line traffic.

             abm_support
                       Specifies whether asynchronous balanced mode (ABM)
                       protocols are supported. APPC returns one of the
                       following values:

                YES       Asynchronous balanced mode (ABM) protocols are
                          supported.
                NO        Normal response mode (NRM) protocols are supported.

             max_btu_size
                       Specifies the maximum BTU size that link stations on
                       this adapter can receive.

             receive_window
                       Specifies the maximum number of I-frames that can be
                       received by a link station on this adapter before an
                       acknowledgement is sent.

             send_window
                       Specifies the maximum number of I-frames that can be
                       sent by a link station on this adapter before an
                       acknowledgment is received.

             max_ls_used
                       Specifies the maximum number of link stations on this
                       adapter that can be active at one time.

             adapter_active
                       Indicates whether or not the adapter has been
                       initialized and is operational.

             adapter_max_activation_attemptsn
                       Indicates the adapter default value for the maximum
                       number of activation attempts per link.  A value of 0
                       means that there is no limit.

             adapter_type
                       Indicates the type of adapter represented by this
                       entity. Auto_dialed adapters are those which are used by
                       Connection Manager to place automatically-dialed calls
                       across a switched network. Non_dialed adapters are those
                       which are not used by Connection Manager to place
                       automatically-dialed calls.


ΓòÉΓòÉΓòÉ 5.13. LU 6.2 Definition Information ΓòÉΓòÉΓòÉ

LU 6.2 Definition Information

The lu_6.2_information_address returns information about the configured LUs.

See LU62_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          LU 6.2 Definition Information Group Returned Parameters shows
          returned parameters that describe LU 6.2 definition information for
          the DISPLAY verb.

                    LU 6.2 Definition Information
                    length_of_initial_sectionn
                    number_of_lusn
                    total_number_of_lusn

                    LU Group (Repeated for each LU group):
                    length_of_lu_datan
                    lu_namename
                    lu_alias_namename
                    lu_nau_addressaddress
                    pu_namename

          LU 6.2 Definition Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Specifies the length in bytes from the beginning of LU
                    definition info to the beginning of the first LU data
                    entry.

          number_of_lus
                    Specifies the number of defined LU groups returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_lus
                    Specifies the total number of LUs defined to the system.

                    LU Group

                    The following parameters are repeated for each LU 6.2
                    group.

             length_of_lu_data
                       Specifies the length in bytes from the beginning of this
                       LU data entry to the beginning of the next.

             lu_name
                       The 8-byte EBCDIC network name of the local LU. This is
                       the name of the LU as it is known throughout the
                       network.

                       This is a type A EBCDIC character string. If the name is
                       less than 8 bytes, it is padded on the right with EBCDIC
                       blanks.

             lu_alias
                       The 8-byte ASCII name used locally for the LU. The name
                       is not sent outside the local node.

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, APPC pads it on the right with ASCII
                       blanks.

             lu_nau_address
                       Specifies the destination network address of the LU for
                       sessions to a subarea node.  The value is 0 for
                       independent LUs.

             pu_name
                       The 8-character identifier that corresponds to a host
                       system link used for dependent LU sessions. This allows
                       multiple host systems to issue ACTPUs to the same
                       physical workstation.


ΓòÉΓòÉΓòÉ 5.14. Partner LU Definition Information ΓòÉΓòÉΓòÉ

Partner LU Definition Information

The partner_lu_definition_information_address returns information about the
configured and implicit partners.

See PLU_DEF_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Partner LU Definition Information Group Returned Parameters shows
          returned parameters that describe partner LU definition information
          for the DISPLAY verb.

                    LU 6.2 Definition Information
                    length_of_initial_sectionn
                    number_of_partner_lusn
                    total_number_of_partner_lusn

                    Partner LU Group (Repeated for each partner LU group):
                    length_of_partner_lu_datan
                    fq_partner_lu_namename
                    partner_lu_aliasname
                    uninterpreted_partner_lu_namename
                    parallel_session_support{YES | NO}
                    maximum_mc_ll_send_sizen
                    session_level_security{YES | NO}
                    conv_security_verification{YES | NO}
                    number_of_alternate_aliasesn

                    Alternate Alias Group (Repeated for each alternate alias group):
                    alternate_partner_lu_alias_namename

          Partner LU Definition Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Specifies the length in bytes from the beginning of partner
                    LU definition information to the beginning of the first
                    partner LU definition data entry.

          number_of_partner_lus
                    Specifies the number of defined partner LUs returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_partner_lus
                    Specifies the total number of partner LUs defined to the
                    system.

                    Partner LU Group

                    The following parameters are repeated for each partner LU
                    group.

             length_of_partner_lu_data
                       Specifies the length in bytes from the beginning of this
                       partner LU data entry to the beginning of the next.

             fq_partner_lu_name
                       The 17-byte EBCDIC fully qualified network name for the
                       partner LU. The name consists of the partner network ID,
                       an EBCDIC period, and the partner_lu_name. This is the
                       name of the partner LU as it is known throughout the
                       network.

                       This name is two type A EBCDIC character strings
                       concatenated by an EBCDIC period. Each name can have a
                       maximum length of 8 bytes with no embedded blanks. If
                       the network ID is not present, the period is omitted. If
                       the name is less than 17 bytes, it is padded on the
                       right with EBCDIC blanks.

             partner_lu_alias
                       The 8-byte ASCII name used locally for the partner LU.
                       The name is not sent outside of the local node.

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, APPC pads it on the right with ASCII
                       blanks.

             uninterpreted_partner_lu_name
                       Specifies the uninterpreted name for the partner LU.

             parallel_session_support
                       Specifies if the partner LU supports more than one
                       session. APPC returns one of the following values:

                YES       Specifies that parallel sessions are supported.
                NO        Specifies that parallel sessions are not supported.

             maximum_mc_ll_send_size
                       Specifies the maximum size of a logical record to be
                       used on a mapped conversation for sending data to the
                       partner LU.

             session_level_security
                       Specifies the type of security information that a local
                       LU will accept on BIND requests it receives from the
                       partner LU. APPC returns one of the following values:

                YES       Specifies that the BIND request may carry a password
                          that will be verified upon receipt.

                NO        Specifies that the BIND request may carry a password
                          but no session level security verification will be
                          done.

             conv_security_verification
                       Specifies the type of security information that a local
                       LU will accept on allocation requests it receives from
                       the partner LU. APPC returns one of the following
                       values:

                YES       Specifies that the allocation request may include a
                          user ID and the indication that the user ID has
                          already been verified.

                NO        Specifies that allocation requests may include a user
                          ID together with a password, but not the already
                          verified indication.

             number_of_alternate_aliases
                       Specifies the number of alternate aliases defined to the
                       system.

                       Alternate Alias Group

                       The following parameter is repeated for each alternate
                       alias group.

                alternate_partner_lu_alias_name
                          The 8-byte ASCII name used as an alias for the
                          partner LU. The name is not sent outside of the local
                          node. If the name is less than 8 bytes, APPC pads it
                          on the right with ASCII blanks.


ΓòÉΓòÉΓòÉ 5.15. Mode Definition Information ΓòÉΓòÉΓòÉ

Mode Definition Information

The mode_definition_information_address returns information about the
configured and implicit modes.

See MODE_DEF_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Mode Definition Information Group Returned Parameters shows returned
          parameters that describe mode definition information for the DISPLAY
          verb.

                    Mode Definition Information
                    length_of_initial_sectionn
                    number_of_modesn
                    total_number_of_modesn

                    Mode Definition Group (Repeated for each mode definition group):
                    length_of_mode_datan
                    cos_namename
                    mode_namename
                    compression_need
                    max_ru_size_upper_boundn
                    receive_pacing_windown
                    default_ru_size{YES | NO}
                    max_negotiable_session_limitn
                    max_session_limitn
                    min_conwinners_sourcen
                    plu_slu_compression_level
                    slu_plu_compression_level

          Mode Definition Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Specifies the length in bytes from the beginning of mode
                    definition information to the beginning of the first mode
                    data entry.

          number_of_modes
                    Specifies the number of defined mode groups returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_modes
                    Specifies the total number of modes defined to the system.

                    Mode Definition Group

                    The following parameters are repeated for each mode
                    definition group.

             length_of_mode_data
                       Specifies the length in bytes from the beginning of this
                       mode data entry to the beginning of the next.

             cos_name
                       The 8-byte EBCDIC name for the class of service. This is
                       the name of the COS as it is known throughout the
                       network.

                       This is a type A EBCDIC character string. If the name is
                       less than 8 bytes, APPC pads it on the right with EBCDIC
                       blanks.

             mode_name
                       The 8-byte EBCDIC name for the mode. The mode name is
                       used to designate the network properties for a group of
                       sessions. This is the name of the mode as it is known
                       throughout the network.

                       This is a type A EBCDIC character string. If the name is
                       less than 8 bytes, APPC pads it on the right with EBCDIC
                       blanks.

             compression_need
                       Specifies the level of compression desired.

             max_ru_size_upper_bound
                       Specifies the upper bound for the maximum size RU that
                       can be sent and received on the session.

             receive_pacing_window
                       Specifies the session pacing window for the sessions
                       when fixed pacing is used.

             default_ru_size
                       Specifies whether the upper bound for the maximum RU
                       will be calculated by APPC. APPC returns one of the
                       following values:

                YES       The upper bound will be set to the link size.
                NO        The max_ru_size_upper_bound value is used.

             max_negotiable_session_limit
                       Specifies the maximum session limit that a local LU can
                       use during its CNOS processing, as the target LU, for
                       the mode name.

             max_session_limit
                       Specifies the session limit that a local LU is to use
                       during its CNOS processing, as the source LU, for the
                       mode name.

             min_conwinners_source
                       Specifies the minimum contention winner value that a
                       local LU is to use during its CNOS processing, as a
                       source LU, for the mode name.

             plu_slu_compression_level
                       The requested PLU to SLU compression level for a session
                       established with this mode.

             slu_plu_compression_level
                       The requested SLU to PLU compression level for a session
                       established with this mode.


ΓòÉΓòÉΓòÉ 5.16. Link Definition Information ΓòÉΓòÉΓòÉ

Link Definition Information

The link_definition_information_address returns information about the
configured links.

See LINK_DEF_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Link Definition Information Group Returned Parameters shows returned
          parameters that describe link definition information for the DISPLAY
          verb.

                    Link Definition Information
                    length_of_initial_sectionn
                    number_of_linksn
                    total_number_of_linksn

                    Link Definition Group (Repeated for each link definition group):
                    length_of_link_datan
                    link_namename
                    fq_adj_cp_namename
                    adj_node_type{LEARN | LEN | NN}
                    preferred_nn_server{YES | NO}
                    dlc_namename
                    use_puname_as_cpname{YES | NO}
                    max_activation_attempts{NO_LIMIT | value}
                    adapter_numbern
                    destination_address_lengthn
                    destination_addressaddress
                    cp_cp_session_support{YES | NO}
                    activate_at_startup{YES | NO}
                    limited_resource{YES | NO | USE_ADAPTER_DEFINITION}
                    link_station_role{NEGOTIABLE | PRIMARY | SECONDARY |
                                USE_ADAPTER_DEFINITION}
                    cost_per_connect_timen
                    cost_per_byten
                    solicit_sscp_session{YES | NO}
                    bind_support{YES | NO}
                    line_type{SWITCHED | NONSWITCHED}
                    effective_capacityn
                    security{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                           UNDERGROUND_CABLE | SECURE_CONDUIT |
                           GUARDED_CONDUIT | ENCRYPTED |
                           GUARDED_RADIATION}
                    propagation_delay{MINIMUM | LAN | TELEPHONE |
                               PACKET_SWITCHED_NETWORK |
                               SATELLITE | MAXIMUM}
                    user_defined_1n
                    user_defined_2n
                    user_defined_3n
                    pu_namename
                    pu_node_idn

          Link Definition Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Specifies the length in bytes from the beginning of link
                    definition information to the beginning of the first link
                    data entry.

          number_of_links
                    Specifies the number of link definitions returned by the
                    DISPLAY verb into your program's buffer.

          total_number_of_links
                    Specifies the total number of links defined to the system.

                    Link Definition Group

                    The following parameters are repeated for each link
                    definition group.

             length_of_link_data
                       Specifies the length in bytes from the beginning of this
                       link data entry to the beginning of the next.

             link_name
                       The 8-byte EBCDIC name of the local logical link station
                       is padded on the right with 4 EBCDIC blanks.  This
                       logical link can be activated by specifying this name on
                       the ACTIVATE_LOGICAL_LINKS verb.

                       Note:  This is a Type A EBCDIC character string.  If the
                       name is less than 8 bytes, APPC pads it on the right
                       with EBCDIC blanks.  In addition, the string cannot
                       begin with an EBCDIC "@" (X'7C').

             fq_adj_cp_name
                       Specifies the fully qualified network name for the
                       control point (CP) in the adjacent node.

             adj_node_type
                       Specifies the APPN node type of the adjacent node. APPC
                       returns one of the following values:

                LEARN
                          Specifies that the adjacent node type (EN, NN, or
                          LEN) is not known, and is to be learned when a link
                          (TG) to the adjacent node is established.

                LEN
                          Specifies that the adjacent node is a low-entry
                          networking node.

                NN
                          Specifies that the adjacent node is a network node.

             preferred_nn_server
                       Specifies that the adjacent node type is a network node
                       and should be the first node to which CP-CP sessions are
                       established. APPC returns either YES or NO.

             dlc_name
                       The 8-byte ASCII name of the local data link control
                       (DLC). This is the name used to configure a DLC in the
                       Communications Manager DLC profile.

                o 'ETHERAND'
                o 'IBMPCNET'
                o 'IBMTRNET'
                o 'SDLC   '
                o 'TWINAX  '
                o 'X25DLC  '
                o 'IDLC   '

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, APPC pads it on the right with ASCII
                       blanks.

             use_puname_as_cpname
                       Transmit the PU name in the CP name field on an XID3
                       exchange.

             max_activation_attempts
                       Specifies the default value for the maximum number of
                       activation attempts per link.  A value of 0 indicates
                       that there is no limit.

                       An ACTIVATE_LINK command always attempts to activate the
                       link even if the number of activation attempts has been
                       reached.

             adapter_number
                       Specifies the adapter used for this link station to
                       communicate with the adjacent node.

             destination_address_length
                       Specifies the length of the destination address.

             destination_address
                       Specifies the destination address to be used by the
                       local node to address the link station on the adjacent
                       node.

             cp_cp_session_support
                       Specifies whether the link is to support CP-CP sessions.
                       APPC returns one of the following values:

                YES
                          Specifies that CP-CP sessions are supported on this
                          link. CP-CP sessions are activated on this link only
                          when the adjacent node supports CP-CP sessions and,
                          for an APPN end node, when the adjacent node is an NN
                          and the EN does not have a NN server when this link
                          is activated.

                NO
                          Specifies that CP-CP sessions are not supported on
                          this link. This is useful for NNs in order to define
                          a link over which it will support intermediate
                          sessions but not directory searches.

             activate_at_startup
                       Specifies whether the link is to be automatically
                       activated when a subsequent ACTIVATE_LOGICAL_LINKS verb
                       is issued. See the description of the link_name_select
                       parameter on page ACTIVATE_LOGICAL_LINKS for more
                       information. APPC returns either YES or NO.

             limited_resource
                       Specifies whether this link is to remain active when
                       there are no sessions using the link. APPC returns one
                       of the following values:

                YES
                          Specifies that this link to the adjacent control
                          point is subject to limited resource control, and
                          will be brought down when the link is no longer being
                          used.

                NO
                          Specifies that this link is to remain active, even if
                          the adapter was specified as a limited resource. This
                          is useful, for example, in a token-ring environment
                          when a user wants a link to a LAN server or host to
                          remain active but has defined the token-ring adapter
                          as a limited resource.

                USE_ADAPTER_DEFINITION
                          Specifies that the limited resource value defined for
                          the adapter is to be used.

             link_station_role
                       Specifies the link station role to be used for this
                       link. You must specify one of the following values:

                NEGOTIABLE
                          Specifies this link will negotiate its role during
                          link activation via XID exchange.

                PRIMARY
                          Specifies this link as the primary link station.

                SECONDARY
                          Specifies this link as the secondary link station.

                USE_ADAPTER_DEFINITION
                          Specifies that the link station role defined for the
                          adapter is to be used.

             cost_per_connect_time
                       An integer value in the range of 0 to 255 that expresses
                       the relative cost of using this link. The units are user
                       defined. The cost per connect time values must be
                       proportional to applicable tariffs of the transmission
                       facility being used by the link and must reflect the
                       relative expense of the link as compared to all other
                       links in the network. A value of 0 means that
                       connections using this link are free.

                       Cost per connect time is network specific and is not
                       intended to be uniform across networks (except where two
                       or more networks coordinate assignment of relative cost
                       values among themselves).

             cost_per_byte
                       An integer value in the range 0 to 255 that expresses a
                       relative cost of transmitting a byte over this link. The
                       units are user defined. Cost per byte value should be
                       proportional to the actual cost of transmitting data
                       over the link. A value of 0 means that transmitting a
                       byte of data over the link is free.

                       Cost per byte is network specific and is not intended to
                       be uniform across networks (except where two or more
                       networks coordinate assignment of relative cost values
                       among themselves).

             solicit_sscp_session
                       Specifies whether an SSCP session is requested for this
                       link. APPC returns either YES or NO.

             bind_support
                       Indicates whether this node accepts incoming BIND
                       requests. Communication Manager always sets this to YES.

             line_type
                       Indicates the type of line connection. APPC returns
                       either SWITCHED or NONSWITCHED.

             effective_capacity
                       The highest bit transmission rate for the logical link
                       before the link is considered overloaded. You can obtain
                       the effective capacity value by multiplying the link
                       speed by a user defined maximum load factor. The value
                       is expressed in bits per second.

             security
                       This parameter specifies the security value for this
                       link. The following list describes the valid values for
                       these parameters in the order of their effectiveness.

                NONSECURE
                          Specifies that no security exists, such as satellite
                          links or underground lines.

                PUBLIC_SWITCHED_NETWORK
                          Specifies that data transmitted over this adapter
                          will flow through a public switched network.

                UNDERGROUND_CABLE
                          Specifies transmission over a secure underground
                          cable.

                SECURE_CONDUIT
                          Specifies that the line is secure conduit that is not
                          guarded, such as pressurized pipe.

                GUARDED_CONDUIT
                          Specifies that the conduit is protected against
                          physical tapping.

                ENCRYPTED
                          Specifies that the adapter, or the system software
                          that controls the adapter, encrypts the data
                          transmitted over the line.

                GUARDED_RADIATION
                          Specifies that the line is protected against physical
                          and radiation tapping.

             propagation_delay
                       This value represents the amount of time it takes for a
                       signal to travel the length of the logical link, in
                       microseconds. The following list describes the valid
                       values, with MINIMUM representing the least propagation
                       delay and MAXIMUM representing the longest propagation
                       delay.

                MINIMUM
                          Specifies there is no propagation delay.

                LAN
                          Specifies that propagation delay is less than 480
                          microseconds.

                TELEPHONE
                          Specifies a delay between 480 and 49152 microseconds.

                PACKET_SWITCHED_NETWORK
                          Specifies a delay between 49152 and 245760
                          microseconds.

                SATELLITE
                          Specifies a delay longer than 245760 microseconds.

                MAXIMUM
                          Specifies the maximum delay allowed.

             user_defined_1
                       The value of the first user-defined TG characteristic
                       for this link.

             user_defined_2
                       The value of the second user-defined TG characteristic
                       for this link.

             user_defined_3
                       The value of the third user-defined TG characteristic
                       for this link.

             pu_name
                       The 8-character identifier that corresponds to a host
                       system link used for dependent LU sessions. This allows
                       multiple host systems to issue ACTPUs to the same
                       physical workstation.

             pu_node_id
                       The hexadecimal representation of the Node
                       Identification field of the XID.  This requests the node
                       identification that is sent (node_id_sent) to the remote
                       partner when the link is activated.


ΓòÉΓòÉΓòÉ 5.17. Management Services Information ΓòÉΓòÉΓòÉ

Management Services Information

The management_services_information_address returns information about
management services.

See MS_INFO_SECT for the DISPLAY Verb Control Block for the format of the
returned information.

          Management Services Information Group Parameters shows returned
          parameters that describe management services (MS) information for the
          DISPLAY verb.

                    Management Services Information
                    length_of_initial_ms_sectionn
                    count_of_held_alertsn
                    number_of_ms_fps_displayedn
                    total_number_of_ms_fpsn
                    number_of_ms_appls_displayedn
                    total_number_of_ms_applsn
                    number_of_ms_act_trans_displayedn
                    total_number_of_ms_act_transn
                    number_of_local_ms_fps_displayedn
                    total_number_of_local_ms_fpsn

                    MS Focal Point Group (repeated for each MS focal point):
                    length_of_ms_fp_dataname
                    fp_ms_categoryname
                    fp_appl_namename
                    fp_fq_cp_namename
                    backup_fp_appl_namename
                    backup_fp_fq_cp_namename
                    retry_responsibility{FP_RETRY | EP_RETRY}
                    fp_type{EXPLICIT_PRIMARY | IMPLICIT_PRIMARY | BACKUP |
                                              DEFAULT_PRIMARY | DEFAULT_BACKUP | DOMAIN |
                                              HOST | NO_FP}
    fp_status{NOT_ACTIVE | ACTIVE | PENDING | LOCAL_ACTIVE |
                                                  NEVER_ACTIVE}
    fp_routing{DEFAULT | DIRECT}
    primary_fp_fq_cp_namename
    number_of_backup_fpsn

    Registered MS Application Group (repeated for each MS application):
    length_of_ms_appl_datan
    ms_appl_namename
    ms_categoryname
    queue_namename

  Management Services Information Group Parameters

    MS Active Transaction Group (repeated for each MS active transaction):
    length_of_ms_act_trans_datan
    origin_fq_cp_namename
    origin_ms_appl_namename
    dest_fq_cp_namename
    dest_ms_appl_namename
    agent_unit_of_workname/value

    Local MS Focal Point Group (repeated for each local MS FP):
    length_of_all_ms_local_fp_datan
    length_of_ms_local_fp_data_onlyn
    local_fp_ms_categoryname
    local_fp_appl_namename
    local_fp_appl_status{APPL_UNREGISTERED | APPL_REGISTERED |
                                                                                          APPL_REGISTERED_UNAVAILABLE}
          default_soc{NO | YES}
          default_backup_fp_fq_cp_namename
          default_backup_fp_indication{REPLACE | KEEP}
          number_of_soc_nodesn

          MS SOC Node Group
          (repeated for each MS SOC node for each local MS focal point):
          length_of_ms_soc_node_datan
          soc_node_fq_cp_namename
          explicit_backup_fp_fq_cp_namename
          explicit_backup_fp_indication{REPLACE | KEEP}
          soc_node_status{REVOKED | INACTIVE_EXPLICIT | INACTIVE_DEFAULT |
                                                                        INACTIVE_IMPLICIT | ADD_PENDING | ACTIVE_SOC |
                                                                        DELETE_ADD_PENDING | DELETE_PENDING}
        soc_fp_rank{EXPLICIT_PRIMARY | IMPLICIT_PRIMARY |
                                                              BACKUP | DEFAULT_PRIMARY}

   Management Services Information Group Returned Parameters

 Return Codes

          length_of_initial_ms_section
                    Indicates the length of the initial MS information section,
                    including this parameter, up to the first MS focal point
                    group. The length does not include any previous information
                    sections.

          count_of_held_alerts
                    Indicates the number of MS alerts being held that will be
                    sent to the MS alert focal point (FP) when one becomes
                    available.  The held Alerts are sent to either an MDS-level
                    FP, a migration-level FP, such as a migration-level
                    AS/400*, or an NMVT-level (host) FP, depending on which one
                    becomes available. If an MDS-level FP becomes available,
                    all held alerts are sent on an LU 6.2 session using the
                    MDS-MU GDS format.  If a migration-level FP becomes
                    available, all held alerts are sent on an LU 6.2 session
                    using the CP-MSU GDS format.  if a host FP becomes
                    available, all held alerts are sent on the SSCP-PU session
                    using the NMVT RU format.

                    The local CP holds alerts that originate at the local node.
                    It also holds alerts that originate at attached
                    workstations when the following two conditions are met:

             o The local node is an SNA Gateway node serving the workstations.

             o The workstations send alerts (in NMVT RU format) on the SSCP-PU
               session to the local gateway node.

          number_of_ms_fps_displayed
                    Indicates the number of MS focal points (MS FPs) for which
                    the information listed under MS Focal Point Group is
                    returned. This is the number of times the information group
                    is repeated.

          total_number_of_ms_fps
                    Indicates the total number of MS FPs for which APPC has
                    information. This number is the same as the number returned
                    with the number_of_ms_fps_displayed parameter, except when
                    APPC has more information about MS FPs than it can place in
                    the supplied buffer, in which case this number is larger.

          number_of_ms_appls_displayed
                    Indicates the number of registered MS applications for
                    which the information listed under Registered MS
                    Application Group is returned. This is the number of times
                    the information group is repeated.

          total_number_of_ms_appls
                    Indicates the total number of registered MS applications
                    for which APPC has information. This number is the same as
                    the number returned with the number_of_ms_appls_displayed
                    parameter, except when APPC has more information about
                    registered MS applications than it can place in the
                    supplied buffer, in which case this number is larger.

          number_of_ms_act_trans_displayed
                    Indicates the number of MS active transactions for which
                    the information listed under MS Active Transaction Group is
                    returned. This is the number of times the information group
                    is repeated.

          total_number_of_ms_act_trans
                    Indicates the total number of MS active transactions for
                    which APPC has information. This number is the same as the
                    number returned with the number_of_ms_act_trans_displayed
                    parameter, except when APPC has more information about MS
                    active transactions than it can place in the supplied
                    buffer, in which case this number is larger.

          number_of_local_ms_fps_displayed
                    Indicates the number of local MS focal points for which the
                    information listed under Local MS Focal Point Group is
                    returned. This is the number of times the information group
                    is repeated.

          total_number_of_local_ms_fps
                    Indicates the number of local MS focal points for which
                    APPC has information.  This number is the same as the
                    number returned with the number_of_local_ms_fps_displayed
                    parameter, except when APPC has more information about
                    local MS focal points than it can place in the supplied
                    buffer, in which case this number is larger.

                    MS Focal Point Group

                    The following parameters are repeated for each local and
                    remote MS FP.

             length_of_ms_fp_data
                       Indicates the length of the MS FP group information,
                       including this parameter.

             fp_ms_category
                       Indicates the MS category of the focal point. All the
                       information within this group refers to the FP for this
                       MS category.

             fp_appl_name
                       Indicates the MS application name of the current
                       (active) focal point. If the local node has no FP, the
                       MS category name is returned with this parameter.

             fp_fq_cp_name
                       Indicates the control point (CP) name of the node at
                       which the current (active) MS FP is located.

                       If the FP is located at a type 5 host system and it
                       supports receipt of MDS-MUs, this parameter indicates
                       the LU name for the FP.  If the type 5 host system does
                       not support receipt of MDS-MUs, this parameter indicates
                       the EBCDIC host_fp_link_name, as configured by the
                       DEFINE_LOCAL_CP verb.  If a host_fp_link_name is not
                       configured, this parameter indicates all zeros (X'00'),
                       which means an implicit host link is being used.

                       If the local node has no FP, a value of all EBCDIC space
                       characters (X'40') is returned.

             backup_fp_appl_name
                       Indicates the MS application name of the backup FP, if
                       one is known. If no backup FP is known, a value of all
                       EBCDIC space characters (X'40') is returned. This
                       parameter is meaningful only if the number_of_backup_fps
                       parameter indicates a number greater than 0.

             backup_fp_fq_cp_name
                       Indicates the control point (CP) name of the node at
                       which the backup MS FP is located, if one is known. If
                       the backup FP is located at a type 5 host system that
                       supports receipt of MDS-MUs, this parameter indicates
                       the LU name for the FP.  If this backup FP is currently
                       the active FP, this parameter and the fp_fq_cp_name
                       parameter return the same name.  If no backup FP is
                       known, a value of all EBCDIC space characters (X'40') is
                       returned.  This parameter is meaningful only if the
                       number_of_backup_fps parameter indicates a number
                       greater than 0.

                       The local node may have multiple backup FPs defined to
                       it, as indicated with the number_of_backup_fps
                       parameter.  If it does, this backup FP is the first one
                       in the list of backup FPs.

             retry_responsibility
                       Indicates which end of the FP-EP relationship (either
                       the FP or EP node) has retry responsibility, in terms of
                       initially establishing the relationship, and
                       subsequently reestablishing the relationship after it is
                       broken.

                FP_RETRY
                          The remote FP is responsible for reestablishing the
                          FP-EP relationship.

                EP_RETRY
                          The local EP is responsible for reestablishing the
                          FP-EP relationship.

             fp_type
                       Indicates the type of the current MS focal point for the
                       local MS entry point node. The FP type depends on how
                       the FP-EP relationship was established, and on whether
                       the local node is configured as an NN, EN, or LEN node
                       (an EN without CP-CP session support). The type can be
                       one of the following:

                EXPLICIT_PRIMARY
                          The current FP type is explicit primary. The FP-EP
                          relationship was initiated by the FP as a result of
                          the FP operator including the local node in the FP's
                          sphere of control (SOC). The local node may be an NN,
                          EN, or LEN node.

                IMPLICIT_PRIMARY
                          The current FP type is implicit primary. The FP-EP
                          relationship was initiated by the local EP node as a
                          result of the DEFINE_REMOTE_FP verb. The local node
                          may be an NN, EN, or LEN node.

                BACKUP
                          The current FP type is backup. The FP-EP relationship
                          was initiated by the local EP node as a result of
                          switching to the backup FP after the primary FP
                          became unavailable. The local node may be an NN, EN,
                          or LEN node.

                DEFAULT_PRIMARY
                          The current FP type is default primary. The FP-EP
                          relationship was initiated by the FP based on the the
                          APPN topology database of the FP node. The local node
                          is an NN.

                DEFAULT_BACKUP
                          The current FP type is default backup. The FP-EP
                          relationship was initiated by the EP as a result of
                          switching to the default backup FP after the default
                          primary FP became unavailable. The local node is an
                          NN.

                DOMAIN
                          The current FP type is domain. The FP-EP relationship
                          was initiated by the EN's serving NN as a result of
                          the NN acquiring an explicit primary, implicit
                          primary, backup, default primary, or host FP. The
                          local node is an EN.

                HOST
                          The current FP type is host. The FP-EP relationship
                          was initiated by the local EP node as a result of the
                          user configuring YES for host FP support, and the
                          local node has, or can have, an SSCP-PU session to
                          the host node at which the FP is located. The local
                          node may be an NN, EN, or LEN node.

                NO_FP
                          Currently, the local node has no FP. Either it has
                          never acquired one, or it lost contact with the one
                          it had. If it never had one, this MS focal point
                          group is shown because one or more MS applications
                          have registered themselves and requested to be
                          notified when the FP becomes available.

             fp_status
                       Indicates the status of the MS FP. The status can be one
                       of the following:

                NEVER_ACTIVE
                          The FP has never been acquired, but one or more
                          registered MS applications have requested FP
                          information.

                NOT_ACTIVE
                          The FP has been acquired, but has since become
                          unavailable.

                ACTIVE
                          The remote FP has been acquired and is available.

                PENDING
                          A request has been sent to a remote primary or backup
                          FP to acquire that FP, and its reply has not yet been
                          received.

                LOCAL_ACTIVE
                          The local FP has registered and is available.

             fp_routing
                       Indicates the routing used to send unsolicited MDS-MU
                       requests to the MS focal point when the local node is an
                       EN. (Requests from an NN are always sent directly to the
                       FP, on an SNASVCMG-mode session.) The routing can be one
                       of the following:

                DEFAULT
                          Unsolicited MS requests destined for the FP are sent
                          from the EN to its serving NN, on a CPSVCMG-mode
                          session, for forwarding to the FP.

                DIRECT
                          Unsolicited MS requests destined for the FP are sent
                          directly to the FP, on an SNASVCMG-mode session.

                       When a program registers an MS application name, it can
                       request FP information. When APPC acquires the FP, it
                       passes the program the FP information, which includes
                       the type of routing to use to send unsolicited MS
                       requests to the FP. The program then indicates the type
                       of routing when it issues the SEND_MDS_MU verb.

             primary_fp_fq_cp_name
                       Indicates the CP name of the node at which the primary
                       MS focal point is located.

                       If the primary FP is located at a type 5 host system
                       that supports receipt of MDS-MUs, this parameter
                       indicates the LU name for the FP. If the primary FP is
                       currently the active FP, this parameter and the
                       fp_fq_cp_name parameter return the same name.

             number_of_backup_fps
                       Indicates the number of backup FPs defined to the local
                       node. The number may be 0 to 8. See also the description
                       of the DEFINE_REMOTE_FP verb.

                    Registered MS Application Group

                    The following parameters are repeated for each registered
                    MS application name. This information represents the
                    parameters a program specifies. A program registers an MS
                    application name by means of the REGISTER_MS_APPLICATION
                    verb.

             length_of_ms_appl_data
                       Indicates the length of the registered MS application
                       group information, including this parameter.

             ms_appl_name
                       Indicates the registered MS application name. This is
                       the name a program uses to receive MDS_MUs destined for
                       this MS application name.

             ms_category
                       Indicates the MS category associated with an MS FP, when
                       the program desires information about the FP. If the
                       program desires no FP information, all binary zeros are
                       returned.

             queue_name
                       Indicates the OS/2 queue name that APPC uses to notify
                       the MS application program that an MDS_MU is being
                       passed to the program. MDS_MUs are passed to the program
                       using a segment the program allocates. The program
                       specifies the queue name and segment selector when it
                       registers the MS application name. (The segment selector
                       is not returned with this MS information.)

                    MS Active Transaction Group

                    The following parameters are repeated for each MS active
                    transaction. An active transaction is an MS request/reply
                    transaction where the MS request has been sent or received
                    but the final reply has not. Each MS transaction is
                    uniquely identified by an Agent_Unit_of_Work correlator.

             length_of_ms_act_trans_data
                       Indicates the length of the MS active transaction group
                       information, including this parameter.

             origin_fq_cp_name
                       Indicates the control point (CP) name of the node at
                       which the MS application that originated the transaction
                       is located, unless the originating MS application is
                       located at a type 5 host system and it supports receipt
                       of MDS_MUs, in which case this parameter indicates the
                       LU name for the origin of the MS transaction.

                       If the type 5 host system does not support receipt of
                       MDS_MUs, this parameter indicates the EBCDIC
                       host_fp_link_name, as configured by the DEFINE_LOCAL_CP
                       verb, or all zeros (X'00') if the host_fp_link_name
                       parameter was not specified.

             origin_ms_appl_name
                       Indicates the name of the MS application that originated
                       the MS transaction.

             dest_fq_cp_name
                       Indicates the control point (CP) name of the node at
                       which the destination MS application for the MS
                       transaction is located, unless the destination MS
                       application is located at a type 5 host system and it
                       supports receipt of MDS_MUs, in which case this
                       parameter indicates the LU name for the destination of
                       the MS transaction.

             dest_ms_appl_name
                       Indicates the name of the destination MS application for
                       the MS transaction.

             agent_unit_of_work
                       Indicates the Agent_Unit_of_Work correlator for the MS
                       transaction. The correlator consists of three fields:

                o The control point (CP) name for the Requester_Location_Name
                o The MS application name for the Requestor_Agent
                o The sequence number, date and time for the Seqno_DTM

          Local MS Focal Point Group

          The following parameters are repeated for each MS category for which
          the local node is the focal point. Associated with each MS category
          is a sphere of control that the local node manages.

          length_of_all_ms_local_fp_datan
                    Indicates the length in bytes from the beginning of this
                    local MS FP entry to the beginning of the next.

          length_of_ms_local_fp_data_onlyn
                    Indicates the length in bytes from the beginning of this
                    local MS FP entry to the beginning of the first MS SOC node
                    entry for this local MS FP entry.

          local_fp_ms_categoryname
                    Indicates the MS category of this local focal point. All
                    the information within this group refers to the local FP
                    for this MS category.

          local_fp_appl_namename
                    Indicates the MS application name of the local focal point.

          local_fp_status
                    Indicates the status of the local focal point. The status
                    can be one of the following:

             UNREGISTERED
                       No local focal point application is registered for the
                       MS category. The value of the local_fp_appl_name
                       parameter is not meaningful.

             REGISTERED
                       A local focal point application is registered for the MS
                       category. The value returned with the local_fp_appl_name
                       parameter is the name of the local FP.

             REGISTERED_UNAVAILABLE
                       A local focal point application is registered for the MS
                       category, but APPC is currently unable to open the queue
                       or write to the shared data segment that the application
                       registered. For example, the segment may be full,
                       because the application is still processing previously
                       received data and has not yet freed enough suballocated
                       space for APPC to use for received MDS-MUs.

          default_soc
                    Indicates whether a default sphere of control is defined to
                    be used with the MS category. The SOC for the MS category
                    may also include SOC nodes where the local FP is the
                    explicit, implicit, or backup FP, as well as the primary
                    default FP.

             NO
                       No default SOC is used.

             YES
                       A default SOC is used.

          default_backup_fp_fq_cp_namename
                    Indicates the CP name of the node at which the default
                    backup MS focal point is located. A null value (all binary
                    0's) indicates the default SOC nodes have no default backup
                    FP. This parameter is meaningful only when the
                    default_backup_fp_indication parameter indicates REPLACE.

                    If a default backup FP is defined and it is located at a
                    type 5 host system that supports receipt of MDS-MUs, this
                    parameter indicates the LU name for the FP.

          default_backup_fp_indication
                    Indicates whether the default SOC nodes have a default
                    backup FP:

             KEEP
                       Indicates the SOC nodes keep their current backup FP, if
                       any.

             REPLACE
                       Indicates the SOC nodes replace their current backup FP,
                       if any, with the one specified on the
                       default_backup_fp_fq_cp_name parameter.

          number_of_soc_nodesn
                    Indicates the number of MS SOC nodes for which information
                    is returned.

                    MS SOC Node Group

                    The following parameters are repeated for each MS SOC node
                    in the local node's SOC table, for this local FP entry.

             length_of_ms_soc_node_datan
                       Indicates the length in bytes from the beginning of this
                       SOC node entry to the beginning of the next.

             soc_node_fq_cp_namename
                       Indicates the CP name of the SOC node.

             explicit_backup_fp_fq_cp_namename
                       Indicates the CP name of the node at which the explicit
                       backup MS focal point is located. A null value (all
                       binary 0's) indicates the SOC node has no explicit
                       backup FP. This parameter is meaningful only when the
                       explicit_backup_fp_indication parameter indicates
                       REPLACE.

                       If an explicit backup FP is defined and it is located at
                       a type 5 host system that supports receipt of MDS-MUs,
                       this parameter indicates the LU name for the FP.

             explicit_backup_fp_indication
                       Indicates whether the SOC node has an explicit backup
                       FP:

                KEEP
                          Indicates the SOC node keeps its current backup FP,
                          if any.

                REPLACE
                          Indicates the SOC node replaces its current backup
                          FP, if any, with the one specified on the
                          explicit_backup_fp_fq_cp_name parameter.

             soc_node_status
                       Indicates the status of the SOC node, in terms of its
                       FP-EP relationship with the local FP node.

                REVOKED
                          Indicates the SOC node has revoked the local FP. The
                          local FP node does not try to reacquire SOC nodes
                          that have a status of REVOKED. You can remove this
                          SOC node entry using the DELETE_EXPLICIT_SOC verb. If
                          needed, you can reacquire the SOC node using the
                          DEFINE_EXPLICIT_SOC verb.

                INACTIVE_EXPLICIT
                          Indicates the SOC node is inactive, and the
                          soc_fp_rank is EXPLICIT_PRIMARY. This SOC node status
                          occurs when the local MS FP application is not yet
                          registered or when the SOC node is not yet available.
                          You can remove this SOC node entry using the
                          DELETE_EXPLICIT_SOC verb.

                INACTIVE_DEFAULT
                          Indicates the SOC node is inactive, and the
                          soc_fp_rank is DEFAULT_PRIMARY. This SOC node status
                          occurs when the local MS FP application is not yet
                          registered, when the SOC node is not yet available,
                          or when the FP-EP relationship is broken. You can
                          remove this SOC node entry using the
                          DELETE_EXPLICIT_SOC or DELETE_DEFAULT_SOC verb.

                INACTIVE_IMPLICIT
                          Indicates the SOC node is inactive, and the
                          soc_fp_rank is either EXPLICIT_PRIMARY,
                          IMPLICIT_PRIMARY, or BACKUP. This SOC node status
                          occurs when the FP_EP relationship is broken. You can
                          remove this SOC node entry using the
                          DELETE_EXPLICIT_SOC verb.

                ADD_PENDING
                          Indicates the SOC node is pending active, and the
                          soc_fp_rank is either EXPLICIT_PRIMARY or
                          DEFAULT_PRIMARY. This SOC node status occurs when the
                          local FP node has sent a request to the SOC node to
                          acquire it and the local node has not yet received
                          the response.

                ACTIVE_SOC
                          Indicates the SOC node is active; that is, the local
                          FP node has an active FP-EP relationship with the SOC
                          (EP) node. An active FP-EP relationship exists from
                          the time it is established until the EP revokes the
                          local FP, or until the relationship is broken. A
                          FP-EP relationship is broken when an error message is
                          received that indicates an attempt by the local FP
                          node to send MS data to the EP node failed; or when
                          an unrecoverable session outage occurs while an MS
                          transaction is active between the FP and EP nodes,
                          such that no sessions for MDS exist between the FP
                          and EP nodes.

                DELETE_ADD_PENDING
                          Indicates the SOC node is pending delete after being
                          pending active; that is, the SOC node was in
                          ADD_PENDING status when the DELETE_DEFAULT_SOC or
                          DELETE_DEFAULT_SOC verb was issued to delete the SOC
                          node from the local FP node's SOC table. This is
                          normally a short, interim status. This SOC node entry
                          is removed if the SOC node rejects the local node's
                          attempt to acquire the SOC node; the status changes
                          to DELETE_PENDING if the SOC node accepts the request
                          to acquire the SOC node.

                DELETE_PENDING
                          Indicates the SOC node is pending delete; however,
                          the FP-EP relationship is still active. This SOC node
                          status occurs when the DELETE_DEFAULT_SOC or
                          DELETE_DEFAULT_SOC verb is issued to delete the SOC
                          node from the local FP node's SOC table. This SOC
                          node entry is removed when the FP-EP relationship is
                          broken and the soc_fp_rank is DEFAULT_PRIMARY; or
                          when the SOC node revokes the local FP and the
                          soc_fp_rank is IMPLICIT_PRIMARY, BACKUP, or
                          DEFAULT_PRIMARY.

             soc_fp_rank
                       Indicates the rank of the local FP in terms of its FP-EP
                       relationship with this SOC node.

                EXPLICIT_PRIMARY
                          The local FP is the explicit primary FP for this SOC
                          node. This SOC node entry was added to the SOC table
                          by means of the DEFINE_EXPLICIT_SOC verb. The SOC
                          node may be a NN, EN, or LEN node.

                IMPLICIT_PRIMARY
                          The local FP is the implicit primary FP for this SOC
                          node. This SOC node entry was added to the SOC table
                          as a result of the SOC node requesting that the local
                          node be its primary FP. For example, the
                          DEFINE_REMOTE_FP verb may have been issued at the SOC
                          node. The SOC node may be a NN, EN, or LEN node.

                BACKUP
                          The local FP is the backup FP for this SOC node. This
                          SOC node entry was added to the SOC table as a result
                          of the SOC node requesting that the local node be its
                          backup FP. This occurs when the SOC node switches to
                          a backup FP after its primary FP becomes unavailable.
                          The SOC node may be a NN, EN, or LEN node. (Note that
                          the local FP node cannot determine whether it is the
                          primary backup or default backup, as the MS
                          Capabilities request from the SOC node does not make
                          this distinction.)

                DEFAULT_PRIMARY
                          The local FP is the default primary FP for this SOC
                          node. This SOC node entry was added to the SOC table
                          by means of the DEFINE_DEFAULT_SOC verb in
                          combination with the APPN topology database of the
                          local node. The SOC node is a NN.


ΓòÉΓòÉΓòÉ 5.18. PU Information ΓòÉΓòÉΓòÉ

PU Information

The pu_info indicates a request for information about the PUs.

          PU Information Group Parameters shows returned parameters that
          describe PU information for the DISPLAY verb.

                    PU Information
                    pu_init_sect_lenn
                    number_pu_displn
                    number_pu_definedn
                    PU Group (Repeated for each PU)
                    pu_entry_lenn
                    pu_namename
                    pu_node_idid
                    pu_link_namename
                    num_lusn
                    fq_adj_cp_namefq_name
                    pu_status{ INACTIVE |
                            PENDING_ACTIVE |
                            ACTIVE |
                            PENDING_INACTIVE
                            LOCAL CP }
                    dlc_namename
                    PU LU Group (Repeated for each LU)
                    pu_lu_entry_lenn
                    lu_namename
                    lu_type{ LU0 | LU1 | LU2 | LU3 | LU6.2 | GW LU0 | GW LU1 | GW LU3
                           GW LU6.2 | GW | CS | CS LU6.2 }
                    lu_status{ INACTIVE | ACTIVE }
                    link_namename
                    dlc_namename

          PU Information Group Parameters

 Return Codes

          pu_init_sect_len
                    Indicates the total size of the PU information section.

          num_pu_displ
                    Indicates the number of PUs returned by the DISPLAY verb.

          num_pu_defined
                    Indicates the number of PUs known to the system.  Normally,
                    this value will match num_pu_displ.  In cases where the
                    information will not fit into the program-supplied buffer,
                    there may be more PUs known to the system than can be
                    returned by the DISPLAY verb.

          PU Group

          The following parameters are returned for each PU.

          pu_entry_len
                    Indicates the size of this PU entry, including the PU_LU
                    entries associated with it.

          pu_name
                    Indicates the 8-byte EBCDIC name of the PU (Physical Unit).

          pu_node_id
                    Indicates the 8-digit hexadecimal Node Identification field
                    that will be sent by this PU in an XID frame.

          pu_link_name
                    Indicates the name of the SNA link associated with this PU.

          num_lu
                    Indicates how many LUs are associated with this PU.

          fq_adj_cp_name
                    Indicates the fully-qualified name of the SSCP which is
                    participating in an SSCP-PU session with this PU.

          pu_status
                    Indicates the status of the PU by one of the following
                    values:

             INACTIVE             The link associated with the PU is not
                                  active.
             PENDING ACTIVE       The link is active, but the PU has not yet
                                  received an ACTPU from the host.
             ACTIVE               The link is active, and the PU has received
                                  an ACTPU.
             PENDING INACTIVE     The link is active, and the PU is waiting for
                                  a DACTPU from the host. A Request_Discontact
                                  has been sent to the host.
             LOCAL CP             The PU is acting as a local control point,
                                  and has no host link defined.

          dlc_name
                    Indicates the name of the DLC used by the link to the host.

          PU_LU Group

          This section is repeated for each LU associated with the PU.

          pu_lu_entry_len
                    Indicates the length of this PU_LU information entry.

          lu_name
                    Indicates the 8-byte EBCDIC name of this LU.

          lu_type
                    Indicates the type of this LU. The abbreviation "GW"
                    indicates the LU is controlled by an SNA Gateway. The
                    abbreviation "CS" indicates the LU is controlled by the SNA
                    Client-Server facility.

          lu_status
                    Indicates the status of the LU.  An ACTIVE LU has an LU-LU
                    session; an INACTIVE one does not.

          link_name
                    Indicates the name of the SNA link associated with this LU.
                    This name will be the same as the PU link name except for
                    LUs controlled by the SNA Gateway.  In this case, this link
                    name will be for the downstream, or workstation, side of
                    the connection.

          dlc_name
                    Indicates the name of the DLC used by the LU link.


ΓòÉΓòÉΓòÉ 5.19. Incoming Call Directory Information ΓòÉΓòÉΓòÉ

Incoming Call Directory Information

The Incoming_Call_Directory_Information specifies a request for incoming call
directory information.

          Incoming Call Directory Information Group Parameters shows returned
          parameters that describe incoming call directory information for the
          Display verb.

                    Incoming Call Directory Information
                    icde_section_lenn
                    num_icd_entries_displn
                    tot_num_icd_entriesn
                    Incoming Call Directory Entry Group (Repeated for each ICD
                    Entry)
                    icde_overlay_lenn
                    icd_entry_namename
                    icd_entry_acc_calls{ YES | NO }

          Incoming Call Directory Information Group Parameters

 Return Codes

          icde_section_len
                    Indicates the total size of the Incoming Call Directory
                    (ICD) entry information section.

          num_icd_entries_displ
                    Indicates the number of ICD entries returned by the Display
                    verb.

          tot_num_icd_entries
                    Indicates the total number of ICD entries known to the SNA
                    subsystem.  In cases where the information will not fit
                    into the program-supplied buffer, there may be more ICD
                    entries known to the SNA subsystem than can be returned by
                    the Display verb.  Also, there may be ICD entries defined
                    to Connection Manager which are not referenced by SNA link
                    definitions.  Information about such ICD entries will not
                    be returned by the Display verb.

                    ICD Entry Group

                    This information is repeated for each ICD entry.

             icde_overlay_len
                       Indicates the length of this ICD entry overlay.

             icd_entry_name
                       Indicates the the 1-15-character ASCII name of the
                       Incoming Call Directory Entry, as defined to Connection
                       Manager.

             icd_entry_acc_calls
                       Indicates whether or not the specified ICD entry is
                       accepting incoming calls.


ΓòÉΓòÉΓòÉ 6. The DISPLAY_APPN Verb ΓòÉΓòÉΓòÉ

This chapter contains reference information for the DISPLAY_APPN verb and
includes the following information sections:

The entry point for DISPLAY_APPN is APPC in APPC.DLL.


ΓòÉΓòÉΓòÉ 6.1. DISPLAY_APPN ΓòÉΓòÉΓòÉ

DISPLAY_APPN

The DISPLAY_APPN verb returns information about APPN resources.

See DISPLAY_APPN Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDISPLAY_APPNΓöÇΓöÇlength_of_initial_sectionnΓöÇΓöÇdisplay_buffer_lengthnΓöÇΓöÇdisplay_buffer_addressnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇnumber_of_information_sectionsnΓöÇΓöÇnode_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇdirectory_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                               ΓööΓöÇNOΓöÇΓöÇΓöÿ             ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇtopology_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇintermed_sess_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇcos_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                 ΓööΓöÇNOΓöÇΓöÇΓöÿ               ΓööΓöÇNOΓöÇΓöÇΓöÿ          ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇcn_informationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                              ΓööΓöÇNOΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöñ Returned Parameters Γö£ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÿ
                    RETURNED PARAMETERS:
                    Γö£ΓöÇΓöÇdisplayed_lengthΓöÇΓöÇrequired_lengthΓöÇΓöÇnode_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇdirectory_information_addressaddressΓöÇΓöÇtopology_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇintermed_information_addressaddressΓöÇΓöÇcos_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇcn_information_addressaddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ

 Parameters

          length_of_initial_section
                    Specifies the number of bytes in this verb control block,
                    up to the beginning of the information addresses.

                    For Communications Manager, always specify the integer
                    value 40.

          display_buffer_length
                    Specifies the length (0 to 65535 bytes) of the buffer that
                    is to contain the returned information.

          display_buffer_address
                    Specifies the address of the buffer that is to contain the
                    requested information. This address can be within the verb
                    buffer (that is, the returned information can be at the end
                    of the verb.)

                    Use a shared, unnamed segment for the data buffer.

          number_of_information_sections
                    Specifies the maximum number of information sections that
                    can be returned by this verb.

                    For Communications Manager, always specify the value 6.

          node_info
                    Specify YES if information about this node's APPN
                    capabilities is requested or NO if it is not.

          directory_information
                    Specify YES if information about this node's APPN directory
                    is requested or NO if it is not.

          topology_information
                    Specify YES if information about this node's APPN topology
                    is requested or NO if it is not.

          intermed_sess_information
                    Specify YES if information about intermediate sessions
                    handled by this node is requested or NO if it is not.

          cos_information
                    Specify YES if information about the class of service
                    definitions is requested or NO if it is not.

          cn_information
                    Specify YES if information about the connection network
                    definitions is requested or NO if it is not.

 Return Codes

          The OK return code indicates that the DISPLAY_APPN verb ran
          successfully.

          The following returned parameters correspond to the supplied
          parameters. The requested information is returned only when the
          return code indicates OK.

          displayed_length
                    This 4-byte integer is the total number of bytes returned
                    into the display data buffer. The number is less than or
                    equal to the number supplied for the buffer_length
                    parameter.

          required_length
                    This 4-byte integer is the total number of bytes needed for
                    displayed data. This number may be larger than the supplied
                    buffer_length. It may also be larger than 64 KB if the
                    requested information cannot fit within a 64 KB segment. In
                    this case, reissue the DISPLAY_APPN verb with one
                    information field at a time. The required buffer size can
                    change when reissuing the DISPLAY_APPN verb because new
                    sessions, and other resources could have been started in
                    the meantime.

          node_info_address
                    Indicates the address of the beginning of the node
                    information in the display data buffer.

          directory_info_address
                    Indicates the address of the beginning of the directory
                    information in the display data buffer.

          topology_info_address
                    Indicates the address of the beginning of the topology
                    information in the display data buffer.

          intermed_sess_info_address
                    Indicates the address of the beginning of the intermediate
                    session information in the display data buffer.

          cos_info_address
                    Indicates the address of the beginning of the class of
                    service information in the display data buffer.

          cn_info_address
                    Indicates the address of the beginning of the connection
                    network information in the display data buffer.

          DISPLAY_APPN Verb Primary and Secondary Return Codes. shows the
          primary and secondary error return codes associated with the
          DISPLAY_APPN verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DISPLAY_APPN Verb Primary and Secondary Return Codes.                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DISPLAY_INVALID_CONSTANT    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DISPLAY_INFO_EXCEEDS_LENGTH   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DATA_SEGMENT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 6.2. Node Information ΓòÉΓòÉΓòÉ

Node Information

The node_information_address returns information about the APPN capabilities of
this node.

See NODE_INFO_SECT for the DISPLAY_APPN Verb Control Block for the format of
the returned information.

          Node Information Group Returned Parameters shows returned parameters
          that describe node information for the DISPLAY_APPN verb.

                    Node Information
                    route_addition_resistancen
                    max_cache_dir_entriesn
                    current_number_cache_entriesn
                    dir_disk_dump_intervaln
                    max_compression_tokens
                    tokens_remaining
                    max_compression_level

          Node Information Group Returned Parameters

 Return Codes

          route_addition_resistance
                    Indicates the desirability of using this node for
                    intermediate session traffic. This value is set to 128 for
                    Communications Manager. Nodes that are perceived as being
                    more desirable for intermediate routing are assigned a
                    lower route addition resistance and nodes that are less
                    desirable are assigned a higher route addition resistance.

          max_cache_dir_entries
                    Indicates the maximum number of resources that can be
                    cached in the directory. Each time a node supporting
                    directory services locates a resource it did not know about
                    previously, an entry for that resource and its location is
                    dynamically added to the directory. This value is set to
                    255 for Communications Manager.

          current_number_cache_entries
                    Indicates the current number of entries in the directory
                    cache.

          dir_disk_dump_interval
                    Indicates how often the directory is to be saved on
                    permanent storage (fixed disk). This value is set to 20 for
                    Communications Manager.

          max_compression_tokens
                    Indicates the maximum time and memory dedicated for data
                    compression.  The value in this field is resource capacity.

          tokens_remaining
                    Indicates the amount of tokens available to establish
                    session compression.

          max_compression_level
                    Indicates the maximum compression level configured for
                    Communications Manager.


ΓòÉΓòÉΓòÉ 6.3. Directory Information ΓòÉΓòÉΓòÉ

Directory Information

The directory_information_address returns the information contained in the
local node's directory. The directory consists of all of the LUs for which the
local node knows the owning control point (CP).

See DIRECTORY_INFO_SECT for the DISPLAY_APPN Verb Control Block for the format
of the returned information.

          Directory Information Group Returned Parameters shows returned
          parameters that describe directory information for the DISPLAY_APPN
          verb.

                    Directory Information
                    length_of_initial_sectionn
                    number_of_directory_entriesn
                    number_of_nnsn
                    total_number_of_nnsn
                    number_of_unassociated_nnsn
                    total_number_of_unassociated_nnsn

                    Network Node and Unassociated End Node Groups
                    (Repeated for each network node and unassociated end nodes):
                    length_of_all_nn_datan
                    length_of_nn_data_onlyn
                    serving_nn_fq_cp_namename
                    number_of_lusn

                    LU Groups (Repeated for each LU in the NNCP domain):
                    length_of_lu_datan
                    fq_lu_namen
                    owning_fq_cp_namename
                    lu_entry_type{HOME | REGISTER | CACHE}
                    wildcard_entry{YES | NO}

          Directory Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Indicates the length in bytes from the beginning of
                    directory information to the beginning of the first network
                    node (NN) entry.

          number_of_directory_entries
                    Indicates the total number of directory entries.

          number_of_nns
                    Indicates the number of NNs for which information is
                    returned.

          total_number_of_nns
                    Indicates the total number of NNs in the directory
                    database.

                    This parameter also indicates the number of unassociated
                    end nodes (EN) for which information is returned. An
                    unassociated NN is an NN whose serving network node is
                    unknown to the APPN directory database. For example, if the
                    local node is an NN, it will be displayed as an
                    unassociated EN.

          number_of_unassociated_nns
                    Indicates the total number of ENs in the directory database
                    that do not have a known network node server.

          total_number_of_unassociated_nns
                    Indicates the total number of unassociated ENs.

                    Network Node and Unassociated End Node Groups

                    The following parameters are repeated for each network node
                    and for each unassociated NN displayed.

             length_of_all_nn_data
                       Indicates the length in bytes from the beginning of this
                       network node or unassociated NN entry to the next.

             length_of_nn_data_only
                       Indicates the length in bytes from the beginning of this
                       field to the beginning of the first LU entry for this
                       network node or unassociated NN.

             serving_nn_fq_cp_name
                       Indicates the fully qualified control point (CP) name of
                       the network node serving the node at which the LU is
                       located. For unassociated NN entries, the NN fully
                       qualified CP name is returned.

             number_of_lus
                       Indicates the number of LUs for which information is
                       returned.

                       LU Groups

                       The following parameters are repeated for each LU in the
                       NNCP domain.

                length_of_lu_data
                          Indicates the length in bytes from the beginning of
                          this field to the beginning of the next LU entry.

                fq_lu_name
                          Indicates the fully qualified network name of an LU
                          in the domain of the serving NN.

                owning_fq_cp_name
                          Indicates the fully qualified CP name of the node at
                          which the LU is located. This name will be the same
                          as the serving NN name when the LU is located at a
                          network node or an unassociated NN. It will also be
                          the same as the fully qualified LU name when this is
                          the control point LU for the node.

                lu_entry_type
                          Indicates the type of directory entry. APPC returns
                          one of the following values:

                   HOME
                             Indicates that the LU is in the domain of the
                             local NNCP and the LU information has been
                             configured at the local node.

                   REGISTER
                             Indicates that the LU is at an NN that is in the
                             domain of the local network node. Registered
                             entries are added by receipt of a Register request
                             received from the ENCP; they are deleted by
                             receipt of a Delete request or the deactivation of
                             the CP-CP sessions between the NNCP and the ENCP.

                   CACHE
                             Indicates that the NNCP has previously performed a
                             search for this LU and has saved, or "cached", the
                             location information, or that the location of the
                             LU was configured at the local NN. The latter
                             applies only to LUs outside the domain of the
                             local NN. The LU may be located in the domain of
                             another NN or the local NN.

                             The location of an LU in the domain of the local
                             network node is cached as a result of a search
                             when the LU is located at a served NN that does
                             not register its LUs but can be searched. Cached
                             entries are deleted by:

                      o An operator
                      o A "least recently used" algorithm when the directory
                        becomes full
                      o The deactivation of the CP-CP sessions between the NNCP
                        and the ENCP in its domain

                wildcard_entry
                          Indicates if the directory entry is a wildcard entry.

                          APPC returns either YES or NO. If YES is returned and
                          the fq_lu_name is all EBCDIC blanks, this is a full
                          wildcard entry. If YES is returned and there are
                          non-blank characters in the fq_lu_name, this is a
                          partial wildcard entry.


ΓòÉΓòÉΓòÉ 6.4. Topology Information ΓòÉΓòÉΓòÉ

Topology Information

The topology_information_address returns information about the network
topology; that is, all NNs and transmission groups between the NNs, and
transmission groups from the local node to ENs and LEN nodes.

Note:  The information returned by TOPOLOGY_INFO is only meaningful when the
local node is a network node. Only active and "activate on demand" links are
displayed.

See TOPOLOGY_INFO_SECT for the DISPLAY_APPN Verb Control Block for the format
of the returned information.

          Topology Information Group Returned Parameters shows returned
          parameters that describe topology information for the DISPLAY_APPN
          verb.

          Topology Information Group Returned Parameters

                    Topology Information
                    length_of_initial_sectionn
                    number_of_nnsn
                    total_number_of_nnsn

                    Network Node Groups(Repeated for each network node group):
                    length_of_all_nn_datan
                    length_of_nn_data_onlyn
                    fq_nncp_namename
                    nncp_route_addition_resistancen
                    nncp_congested{YES | NO}
                    nncp_quiescing{YES | NO}
                    nncp_isr_depleted{YES | NO}
                    number_of_tgsn

                    Transmission Groups
                    (Repeated for each transmission group for each NNCP):
                    length_of_tg_datan
                    destination_fq_cp_namename
                    tg_numbern
                    node_type{REAL | VIRTUAL}
                    cost_per_connect_timen
                    cost_per_byten
                    security{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                           UNDERGROUND_CABLE | SECURE_CONDUIT |
                           GUARDED_CONDUIT | ENCRYPTED |
                           GUARDED_RADIATION}
                    propagation_delay{MINIMUM | LAN | TELEPHONE |
                                 PACKET_SWITCHED_NETWORK | SATELLITE |
                                 MAXIMUM}
                    quiescing{YES | NO}
                    effective_capacityn
                    user_defined_1n
                    user_defined_2n
                    user_defined_3n
                    operational{YES | NO}
                    network_topology{YES | NO}

 Return Codes

          length_of_initial_section
                    Indicates the length in bytes from the beginning of
                    topology information to the beginning of the first network
                    node entry.

          number_of_nns
                    Indicates the number of NNs for which information is
                    returned.

          total_number_of_nns
                    Indicates the total number of NNs in the APPN topology
                    database.

                    Network Node Groups

                    The following parameters are repeated for each displayed
                    network node.

             length_of_all_nn_data
                       Indicates the length in bytes from the beginning of this
                       NN entry to the beginning of the next.

             length_of_nn_data_only
                       Indicates the length in bytes from the beginning of this
                       field to the beginning of the first transmission group
                       (TG) entry for this NN.

             fq_nncp_name
                       Indicates the network name of the NN control point.

             nncp_route_addition_resistance
                       Indicates a value corresponding to the desirability of
                       using this node for intermediate session traffic. This
                       parameter takes on integer values from 0-255 and is used
                       in route computation. Nodes that are perceived as being
                       more desirable for intermediate routing should be
                       assigned a lower route addition resistance and nodes
                       that are less desirable should be assigned a higher
                       route addition resistance.

             nncp_congested
                       Indicates if the NN is congested. APPC returns either
                       YES or NO.

             nncp_quiescing
                       Indicates if the NN control point is being taken down.
                       APPC returns either YES or NO.

             nncp_isr_depleted
                       Indicates whether the NN control point intermediate
                       session routing resources are depleted. APPC returns
                       either YES or NO.

             number_of_tgs
                       Indicates the number of transmission groups originating
                       at the NN control point for which information is
                       returned.

                       Transmission Groups

                       The following parameters are repeated for each TG in
                       this NN.

                length_of_tg_data
                          Indicates the length in bytes from the beginning of
                          this TG entry to the beginning of the next TG entry,
                          or the next NN entry if this is the last TG.

                destination_fq_cp_name
                          Indicates the fully qualified control point (CP) name
                          of the node that is the endpoint for this TG; that
                          is, the node adjacent to the node at which this TG
                          originates.

                tg_number
                          Indicates the number associated with the TG.

                node_type
                          Indicates the type of node that is identified by the
                          destination_fq_cp_name. APPC returns one of the
                          following values:

                   REAL
                             Indicates that the connection is to another
                             computer.

                   VIRTUAL
                             Indicates that the connection is through a
                             connection network.

                cost_per_connect_time
                          An integer value in the range of 0 to 255 that
                          expresses the relative cost of using this link. The
                          units are user defined. The cost per connect time
                          values must be proportional to applicable tariffs of
                          the transmission facility being used by the link and
                          must reflect the relative expense of the link as
                          compared to all other links in the network. A value
                          of 0 means that connections using this link are free.

                          Cost per connect time is network specific and is not
                          intended to be uniform across networks (except where
                          two or more networks coordinate assignment of
                          relative cost values among themselves).

                cost_per_byte
                          An integer value in the range 0 to 255 that expresses
                          a relative cost of transmitting a byte over this
                          link. The units are user defined. Cost per byte value
                          should be proportional to the actual cost of
                          transmitting data over the link. A value of 0 means
                          that transmitting a byte of data over the link is
                          free.

                          Cost per byte is network specific and is not intended
                          to be uniform across networks (except where two or
                          more networks coordinate assignment of relative cost
                          values among themselves).

                security
                          This parameter specifies the security value for this
                          link. The following list describes the valid values
                          for these parameters in the order of their
                          effectiveness.

                   NONSECURE
                             Specifies that no security exists, such as
                             satellite links or underground lines.

                   PUBLIC_SWITCHED_NETWORK
                             Specifies that data transmitted over this adapter
                             will flow through a public switched network.

                   UNDERGROUND_CABLE
                             Specifies transmission over a secure underground
                             cable.

                   SECURE_CONDUIT
                             Specifies that the line is secure conduit that is
                             not guarded, such as pressurized pipe.

                   GUARDED_CONDUIT
                             Specifies that the conduit is protected against
                             physical tapping.

                   ENCRYPTED
                             Specifies that the adapter, or the system software
                             that controls the adapter, encrypts the data
                             transmitted over the line.

                   GUARDED_RADIATION
                             Specifies that the line is protected against
                             physical and radiation tapping.

                propagation_delay
                          This value represents the amount of time it takes for
                          a signal to travel the length of the logical link, in
                          microseconds. The following list describes the valid
                          values, with MINIMUM representing the least
                          propagation delay and MAXIMUM representing the
                          longest propagation delay.

                   MINIMUM
                             Specifies there is no propagation delay.

                   LAN
                             Specifies that propagation delay is less than 480
                             microseconds.

                   TELEPHONE
                             Specifies a delay between 480 and 49152
                             microseconds.

                   PACKET_SWITCHED_NETWORK
                             Specifies a delay between 49152 and 245760
                             microseconds.

                   SATELLITE
                             Specifies a delay longer than 245760 microseconds.

                   MAXIMUM
                             Specifies the maximum delay allowed.

                quiescing
                          Indicates if the TG is being taken down. APPC returns
                          one of the following values:

                   YES
                             Indicates that the TG is being taken down.

                   NO
                             Indicates that the TG is not being taken down.

                effective_capacity
                          Indicates the actual bits per second rate (line
                          speed) for this link station. This value is derived
                          from the link bandwidth and maximum load factor. See
                          the descriptions of effective_capacity_min and
                          effective_capacity_max for the DEFINE_COS verb on
                          topic DEFINE_COS for more information on this
                          representation.

                user_defined_1
                          The value of the first user-defined TG characteristic
                          for this TG.

                user_defined_2
                          The value of the second user-defined TG
                          characteristic for this TG.

                user_defined_3
                          The value of the third user-defined TG characteristic
                          for this TG.

                operational
                          Indicates if the TG is in an operational state. APPC
                          returns either YES or NO.

                network_topology
                          Indicates whether the TG is part of the network
                          topology known to all NNs, or if it is only in this
                          network node's local topology. APPC returns one of
                          the following values:

                   YES
                             Indicates that the TG is part of the network
                             topology.

                   NO
                             Indicates that the TG is only in this network
                             node's local topology.


ΓòÉΓòÉΓòÉ 6.5. Intermediate Session Information ΓòÉΓòÉΓòÉ

Intermediate Session Information

The intermediate_session_information_address returns information about the
intermediate sessions at this node. Intermediate sessions are composed of two
session stages, which connect this node to the previous and next node on the
session route.

See ISR_INFO_SECT for the DISPLAY_APPN Verb Control Block for the format of the
returned information.

          Intermediate Session Information Group Returned Parameters shows
          returned parameters that describe intermediate session information
          for the DISPLAY_APPN verb.

                    Intermediate Session Information
                    length_of_initial_sectionn
                    number_of_int_sessionsn
                    total_number_of_int_sessionsn

                    Intermediate Session Groups
                    (Repeated for each intermediate session group):
                    length_of_int_session_datan
                    pri_stage_fq_adj_cp_namename
                    sec_stage_fq_adj_cp_namename
                    pri_stage_link_namename
                    sec_stage_link_namename
                    fq_pcidid
                    fq_pri_lu_namename
                    fq_sec_lu_namename
                    pri_lu_send_fmd_piu_countn
                    sec_lu_send_fmd_piu_countn
                    pri_lu_send_non_fmd_piu_countn
                    sec_lu_send_non_fmd_piu_countn
                    pri_lu_send_byte_countn
                    sec_lu_send_byte_countn

          Intermediate Session Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Indicates the length in bytes from the beginning of
                    intermediate session information to the beginning of the
                    first intermediate session entry.

          number_of_int_sessions
                    Indicates the number of active intermediate sessions for
                    which information is returned.

          total_number_of_int_sessions
                    Indicates the total number of active intermediate sessions.

                    Intermediate Session Groups

                    The following parameters are repeated for each intermediate
                    session group.

             length_of_int_session_data
                       Indicates the length in bytes from the beginning of this
                       intermediate session entry to the beginning of the next.

             pri_stage_fq_adj_cp_name
                       Indicates the fully qualified control point (CP) name of
                       the adjacent node from which the BIND was received for
                       this session.

             sec_stage_fq_adj_cp_name
                       Indicates the fully qualified CP name of the adjacent
                       node to which the BIND was sent for this session.

             pri_stage_link_name
                       Indicates the link name in EBCDIC over which the BIND
                       was received for this session.

             sec_stage_link_name
                       Indicates the link name in EBCDIC over which the BIND
                       was sent for this session.

             fq_pcid
                       Indicates the network-unique fully qualified procedure
                       correlation identifier for this session. The fq_pcid
                       consists of a procedure identifier and the fully
                       qualified CP name of the origin CP for the session.

             fq_pri_lu_name
                       Indicates the fully qualified LU name of the primary LU
                       for the session.

             fq_sec_lu_name
                       Indicates the fully qualified LU name of the secondary
                       LU for the session.

             pri_lu_send_fmd_piu_count
                       Indicates the number of FM data PIUs that the primary LU
                       has sent on the session, up to the time that the DISPLAY
                       verb was issued. The count includes only SNA FMD PIUs
                       sent, before segmenting (if any); it does not include
                       non-FMD PIUs, such as SC and DFC PIUs. A segmented PIU
                       is counted as one PIU.

             sec_lu_send_fmd_piu_count
                       Indicates the number of FM data PIUs that the secondary
                       LU has sent on the session, up to the time that the
                       DISPLAY verb was issued. The count includes only SNA FMD
                       PIUs sent, before segmenting (if any); it does not
                       include non-FMD PIUs, such as SC and DFC PIUs. A
                       segmented PIU is counted as one PIU.

             pri_lu_send_non_fmd_piu_count
                       Indicates the number of non-FM data PIUs that the
                       primary LU has sent on the session, up to the time that
                       the DISPLAY verb was issued. The count includes only SNA
                       non-FMD PIUs sent, before segmenting (if any), such as
                       SC and DFC PIUs. A segmented PIU is counted as one PIU.

             sec_lu_send_non_fmd_piu_count
                       Indicates the number of non-FM data PIUs that the
                       secondary LU has sent on the session, up to the time
                       that the DISPLAY verb was issued. The count includes
                       only SNA non-FMD PIUs sent, before segmenting (if any),
                       such as SC and DFC PIUs. A segmented PIU is counted as
                       one PIU.

             pri_lu_send_byte_count
                       Indicates the number of bytes that the primary LU has
                       sent on the session, up to the time that the DISPLAY
                       verb was issued. The count includes all SNA PIU bytes
                       sent, before segmenting (if any), including those in FMD
                       and non-FMD PIUs. For segmented PIUs, it includes all
                       TH, RH, and RU bytes on the first segment, and the RU
                       bytes on the middle and last segments; it does not
                       include the TH bytes on the middle and last segments.

             sec_lu_send_byte_count
                       Indicates the number of bytes that the secondary LU has
                       sent on the session, up to the time that the DISPLAY
                       verb was issued. The count includes all SNA PIU bytes
                       sent, before segmenting (if any), including those in FMD
                       and non-FMD PIUs. For segmented PIUs, it includes all
                       TH, RH, and RU bytes on the first segment, and the RU
                       bytes on the middle and last segments; it does not
                       include the TH bytes on the middle and last segments.


ΓòÉΓòÉΓòÉ 6.6. Class of Service Information ΓòÉΓòÉΓòÉ

Class of Service Information

The cos_information_address returns the class of service (COS) definitions.

See COS_INFO_SECT for the DISPLAY_APPN Verb Control Block for the format of the
returned information.

          Class of Service Information Group Returned Parameters shows returned
          parameters that describe COS information for the DISPLAY_APPN verb.

          Class of Service Information Group Returned Parameters

                    Class of Service Information
                    length_of_initial_sectionn
                    number_of_cosn
                    total_number_of_cosn

                    Class of Service Groups (Repeated for each class of service group):
                    length_of_all_cos_datan
                    length_of_all_cos_data_onlyn
                    cos_namename
                    transmission_priority{NETWORK | HIGH | MEDIUM | LOW}
                    number_of_node_rowsn
                    number_of_tg_rowsn

                    COS Node Row Groups (Repeated for each node row):
                    length_of_node_row_datan
                    node_row_weightn
                    route_addition_res_minn
                    route_addition_res_maxn
                    congestion_min{YES | NO}
                    congestion_max{YES | NO}

                    COS TG Row Groups (Repeated for each TG row):
                    length_of_tg_row_datan
                    tg_row_weightn
                    effective_capacity_minn
                    effective_capacity_maxn
                    cost_per_connect_time_minn
                    cost_per_connect_time_maxn
                    cost_per_byte_minn
                    cost_per_byte_maxn
                    security_min{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                              UNDERGROUND_CABLE | SECURE_CONDUIT |
                              GUARDED_CONDUIT | ENCRYPTED |
                              GUARDED_RADIATION}
                    security_max{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                              UNDERGROUND_CABLE | SECURE_CONDUIT |
                              GUARDED_CONDUIT | ENCRYPTED |
                              GUARDED_RADIATION}
                    propagation_delay_min{MINIMUM | LAN | TELEPHONE |
                                     PACKET_SWITCHED_NETWORK | SATELLITE |
                                     MAXIMUM}
                    propagation_delay_max{MINIMUM | LAN | TELEPHONE |
                                     PACKET_SWITCHED_NETWORK | SATELLITE |
                                     MAXIMUM}
                    user_defined_1_minn
                    user_defined_1_maxn
                    user_defined_2_minn
                    user_defined_2_maxn
                    user_defined_3_minn
                    user_defined_3_maxn

 Return Codes

          length_of_initial_section
                    Indicates the length in bytes from the beginning of COS
                    information to the beginning of the first COS entry.

          number_of_cos
                    Indicates the number of defined classes of service
                    information returned.

          total_number_of_cos
                    Indicates the number of defined classes of service.

                    Class of Service Groups

                    The following parameters are repeated for each class of
                    service.

             length_of_all_cos_data
                       Indicates the length in bytes from the beginning of this
                       COS data entry to the beginning of the next.

             length_of_cos_data_only
                       Indicates the length in bytes from the beginning of this
                       COS data entry to the beginning of the node row
                       information for this COS data entry.

             cos_name
                       The 8-byte EBCDIC name for the class of service. This is
                       the name of the COS as it is known throughout the
                       network.

                       This is a type A EBCDIC character string. If the name is
                       less than 8 bytes, APPC pads it on the right with EBCDIC
                       blanks.

             transmission_priority
                       Indicates the transmission priority for this class of
                       service. APPC returns a value of either NETWORK, HIGH,
                       MEDIUM, or LOW.

             number_of_node_rows
                       Indicates the number of node descriptions, or rows, and
                       associated weights defined for this class of service.
                       The maximum number is 8. Each node row contains a range
                       of values for route addition resistance and congestion
                       and a weight to be associated with nodes that are within
                       these ranges. The node weights are used in route
                       calculation.

             number_of_tg_rows
                       Indicates the number of transmission group descriptions,
                       or rows, and associated weights defined for this class
                       of service. Each TG row contains a range of values for
                       line speed, cost per connect time, cost per byte,
                       security, propagation delay and up to three user-defined
                       TG characteristics and a weight to be associated with
                       TGs that are within these ranges. The TG weights are
                       used in route calculation.

                    COS Node Row Groups

                    The following parameters are repeated for each node row in
                    this class of service.

             length_of_node_row_data
                       Indicates the length in bytes from the beginning of this
                       node row entry to the beginning of the next node row
                       entry or to the beginning of the first TG row entry.

             node_row_weight
                       Indicates the weight to be associated with nodes that
                       fit the criteria specified by this node row.

             route_addition_res_min

             route_addition_res_max
                       The minimum and maximum route addition resistance values
                       for this row.

             congestion_min

             congestion_max
                       These parameters specify whether low or high congestion
                       will be tolerated. If both parameters are set to NO,
                       only low congestion will be tolerated for this node row.
                       Similarly, if both parameters are set to YES, only nodes
                       that are highly congested will fit this node row
                       description. If congestion_min specifies NO and
                       congestion_max specifies YES, all nodes fall within the
                       congestion range and congestion is not a criteria for
                       this row.

                    COS TG Row Groups

                    The following parameters are repeated for each TG row in
                    this class of service.

             length_of_tg_row_data
                       Indicates the length in bytes from the beginning of this
                       TG row entry to the beginning of the next TG row entry
                       or to the beginning of the next COS data entry.

             tg_row_weight
                       Indicates the weight to be associated with TGs that fit
                       the criteria specified by this TG row.

             effective_capacity_min

             effective_capacity_max
                       The minimum and maximum line speed values for this row.
                       Values are represented as floating point numbers where
                       the first 5 bits are the exponent and the last 3 bits
                       are the mantissa. See the description of
                       effective_capacity_min and effective_capacity_max for
                       the DEFINE_COS verb on topic DEFINE_COS for more
                       information on this representation.

             cost_per_connect_time_min

             cost_per_connect_time_max
                       The minimum and maximum cost per connect time values for
                       this row. Valid values are integer values in the range
                       0-255, where 0 represents the lowest cost per connect
                       time and 255 represents the highest cost per connect
                       time.

             cost_per_byte_min

             cost_per_byte_max
                       The minimum and maximum cost per byte values for this
                       row. Valid values are integer values in the range 0-255,
                       where 0 represents the lowest cost per byte and 255
                       represents the highest cost per byte.

             security_min

             security_max
                       These parameters specify the minimum and maximum
                       security values for this row. The following list
                       describes the valid values for these parameters in the
                       order of their effectiveness.

                NONSECURE
                          Specifies that no security exists, such as satellite
                          links or underground lines.

                PUBLIC_SWITCHED_NETWORK
                          Specifies that data transmitted over this adapter
                          will flow through a public switched network.

                UNDERGROUND_CABLE
                          Specifies transmission over a secure underground
                          cable.

                SECURE_CONDUIT
                          Specifies that the line is secure conduit that is not
                          guarded, such as pressurized pipe.

                GUARDED_CONDUIT
                          Specifies that the conduit is protected against
                          physical tapping.

                ENCRYPTED
                          Specifies that the adapter, or the system software
                          that controls the adapter, encrypts the data
                          transmitted over the line.

                GUARDED_RADIATION
                          Specifies that the line is protected against physical
                          and radiation tapping.

             propagation_delay_min

             propagation_delay_max
                       These parameters specify the minimum and maximum
                       propagation delay values for this TG row. This value
                       represents the amount of time it takes for a signal to
                       travel the length of the logical link, in microseconds.
                       The following list describes the valid values, with
                       MINIMUM representing the least propagation delay and
                       MAXIMUM representing the longest propagation delay.

                MINIMUM
                          Specifies there is no propagation delay.

                LAN
                          Specifies that propagation delay is less than 480
                          microseconds.

                TELEPHONE
                          Specifies a delay between 480 and 49152 microseconds.

                PACKET_SWITCHED_NETWORK
                          Specifies a delay between 49152 and 245760
                          microseconds.

                SATELLITE
                          Specifies a delay longer than 245760 microseconds.

                MAXIMUM
                          Specifies the maximum delay allowed.

             user_defined_1_min

             user_defined_1_max
                       The minimum and maximum values of the first user-defined
                       TG characteristic for this TG row.

             user_defined_2_min

             user_defined_2_max
                       The minimum and maximum values of the second
                       user-defined TG characteristic for this TG row.

             user_defined_3_min

             user_defined_3_max
                       The minimum and maximum values of the third user-defined
                       TG characteristic for this TG row.


ΓòÉΓòÉΓòÉ 6.7. Connection Network Information ΓòÉΓòÉΓòÉ

Connection Network Information

The connection_network_information_address returns the connection network
definitions.

See CN_INFO_SECT for the DISPLAY_APPN Verb Control Block for the format of the
returned information.

          Connection Network Information Group Returned Parameters shows
          returned parameters that describe connection network information for
          the DISPLAY_APPN verb.

                    Connection Network Information
                    length_of_initial_sectionn
                    number_of_cnsn
                    total_number_of_cnsn

                    CN Groups (Repeated for each connection network group):
                    length_of_all_cn_datan
                    length_of_cn_data_onlyn
                    cn_namename
                    cost_per_connect_timen
                    cost_per_byten
                    security{NONSECURE | PUBLIC_SWITCHED_NETWORK |
                            UNDERGROUND_CABLE | SECURE_CONDUIT |
                            GUARDED_CONDUIT | ENCRYPTED |
                            GUARDED_RADIATION}
                    propagation_delay{MINIMUM | LAN | TELEPHONE |
                                   PACKET_SWITCHED_NETWORK | SATELLITE |
                                   MAXIMUM}
                    effective_capacityn
                    user_defined_1n
                    user_defined_2n
                    user_defined_3n
                    number_of_adapters_for_cnn

                    Adapter Groups (Repeated for each adapter for each CN):
                    length_of_adapter_datan
                    dlc_namename
                    adapter_numbern

          Connection Network Information Group Returned Parameters

 Return Codes

          length_of_initial_section
                    Indicates the length in bytes from the beginning of the CN
                    information to the beginning of the first CN data entry.

          number_of_cns
                    Indicates the number of defined connection networks
                    information returned in buffer.

          total_number_of cns
                    Indicates the total number of defined connection networks.

                    CN Groups

                    The following parameters are repeated for each connection
                    network.

             length_of_all_cn_data
                       Indicates the length in bytes from the beginning of this
                       CN data entry to the next.

             length_of_cn_data_only
                       Indicates the length in bytes from the beginning of this
                       CN data entry to the beginning of the first adapter data
                       entry for this CN data entry.

             cn_name
                       Indicates the network name of the connection network.

             cost_per_connect_time
                       An integer value in the range of 0 to 255 that expresses
                       the relative cost of using this link. The units are user
                       defined. The cost per connect time values must be
                       proportional to applicable tariffs of the transmission
                       facility being used by the link and must reflect the
                       relative expense of the link as compared to all other
                       links in the network. A value of 0 means that
                       connections using this link are free.

                       Cost per connect time is network specific and is not
                       intended to be uniform across networks (except where two
                       or more networks coordinate assignment of relative cost
                       values among themselves).

             cost_per_byte
                       An integer value in the range 0 to 255 that expresses a
                       relative cost of transmitting a byte over this link. The
                       units are user defined. Cost per byte value should be
                       proportional to the actual cost of transmitting data
                       over the link. A value of 0 means that transmitting a
                       byte of data over the link is free.

                       Cost per byte is network specific and is not intended to
                       be uniform across networks (except where two or more
                       networks coordinate assignment of relative cost values
                       among themselves).

             security
                       This parameter specifies the security value for this
                       link. The following list describes the valid values for
                       these parameters in the order of their effectiveness.

                NONSECURE
                          Specifies that no security exists, such as satellite
                          links or underground lines.

                PUBLIC_SWITCHED_NETWORK
                          Specifies that data transmitted over this adapter
                          will flow through a public switched network.

                UNDERGROUND_CABLE
                          Specifies transmission over a secure underground
                          cable.

                SECURE_CONDUIT
                          Specifies that the line is secure conduit that is not
                          guarded, such as pressurized pipe.

                GUARDED_CONDUIT
                          Specifies that the conduit is protected against
                          physical tapping.

                ENCRYPTED
                          Specifies that the adapter, or the system software
                          that controls the adapter, encrypts the data
                          transmitted over the line.

                GUARDED_RADIATION
                          Specifies that the line is protected against physical
                          and radiation tapping.

             propagation_delay
                       This value represents the amount of time it takes for a
                       signal to travel the length of the logical link, in
                       microseconds. The following list describes the valid
                       values, with MINIMUM representing the least propagation
                       delay and MAXIMUM representing the longest propagation
                       delay.

                MINIMUM
                          Specifies there is no propagation delay.

                LAN
                          Specifies that propagation delay is less than 480
                          microseconds.

                TELEPHONE
                          Specifies a delay between 480 and 49152 microseconds.

                PACKET_SWITCHED_NETWORK
                          Specifies a delay between 49152 and 245760
                          microseconds.

                SATELLITE
                          Specifies a delay longer than 245760 microseconds.

                MAXIMUM
                          Specifies the maximum delay allowed.

             effective_capacity
                       The highest bit transmission rate for the logical link
                       before the link is considered overloaded. You can obtain
                       the effective capacity value by multiplying the link
                       speed by a user defined maximum load factor. The value
                       is expressed in bits per second.

             user_defined_1
                       The value of the first user-defined TG characteristic
                       for this TG.

             user_defined_2
                       The value of the second user-defined TG characteristic
                       for this TG.

             user_defined_3
                       The value of the third user-defined TG characteristic
                       for this TG.

             number_of_adapters_for_cn
                       Indicates the number of adapters defined for the
                       connection network.

                       Adapter Groups

                       The following parameters are repeated for each adapter
                       for this CN.

                length_of_adapter_data
                          Indicates the length in bytes from the beginning of
                          this adapter data entry to the beginning of the next.

                dlc_name
                          The 8-byte ASCII name of the local data link control
                          (DLC). This is the name used to configure a DLC in
                          the Communications Manager DLC profile.

                   o 'ETHERAND'
                   o 'IBMPCNET'
                   o 'IBMTRNET'
                   o 'SDLC   '
                   o 'TWINAX  '
                   o 'X25DLC  '
                   o 'IDLC   '

                          This is an 8-byte ASCII character string. If the name
                          is less than 8 bytes, APPC pads it on the right with
                          ASCII blanks.

                adapter_number
                          Indicates the adapter number.


ΓòÉΓòÉΓòÉ 7. Subsystem Management Verbs ΓòÉΓòÉΓòÉ

This chapter contains an alphabetical reference of the subsystem management
verbs. Subsystem management verbs include:

The entry point for subsystem management verbs is APPC in APPC.DLL.


ΓòÉΓòÉΓòÉ 7.1. ACCEPT_INCOMING_CALLS ΓòÉΓòÉΓòÉ

ACCEPT_INCOMING_CALLS

Instructs Communications Manager to accept incoming calls corresponding to the
specified Incoming Call Directory Entry (ICDE), and route them to the
application named in the ICDE.

See ACCEPT_INCOMING_CALLS for information on the verb control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇACCEPT_INCOMING_CALLSΓöÇΓöÇkey nameΓöÇΓöÇICDE_Name nameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key, if the keylock
                    feature has been secured.

                    This is an 8-byte ASCII character string.  If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.  Refer to the User's Guide for details of the
                    keylock feature.

          ICDE_Name
                    Specifies the name of the ICDE for which calls are to be
                    accepted.

                    ICDE names are configured via Connection Manager
                    configuration utilities, and govern connection manager's
                    response to an incoming call.

                    When an incoming call is received, the characteristics of
                    the call are matched against the characteristics of all
                    ICDE entries configured to connection manager.  When an
                    ICDE is found which matches the characteristics of the
                    incoming call, connection manager examines the entry to
                    determine whether to route the incoming call notification
                    to an application program, or to reject the call.  This
                    verb sets the given ICDE to cause connection manager to
                    accept and route the incoming call notification.

 Return Codes

          The OK return code indicates that the ACCEPT_INCOMING_CALLS verb ran
          successfully.

          When the verb returns with primary return code OK, the ICDE may not
          yet have been set to accept incoming calls.  Use the Display verb or
          subsystem management to determine when the ICDE is ready to accept
          calls.

          ACCEPT_INCOMING_CALLS Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          ACCEPT_INCOMING_CALLS verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      ACCEPT_INCOMING_CALLS Primary and Secondary Return Codes                 Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé BAD_ICD_ENTRY_NAME       Γöé Numeric List of Secondary Return Codes Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.2. ACTIVATE_DLC ΓòÉΓòÉΓòÉ

ACTIVATE_DLC

This verb activates the specified adapter.

See ACTIVATE_DLC Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇACTIVATE_DLCΓöÇΓöÇkeyΓöÇΓöÇnameΓöÇΓöÇdlc_nameΓöÇΓöÇnameΓöÇΓöÇadapter_numberΓöÇΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          dlc_name
                    The 8-byte ASCII name of the local data link control (DLC).
                    This is the name used to configure a DLC in the
                    Communications Manager DLC profile. The valid names are:

             o 'ETHERAND'
             o 'IBMPCNET'
             o 'IBMTRNET'
             o 'SDLC   '
             o 'TWINAX  '
             o 'X25DLC  '
             o 'IDLC   '

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

          adapter_number
                    Specifies the adapter number to be activated. This must be
                    the same number as that configured for the adapter in a
                    Communications Manager DLC profile.

 Return Codes

          The OK return code indicates that the ACTIVATE_DLC verb ran
          successfully.

          ACTIVATE_DLC Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the ACTIVATE_DLC verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      ACTIVATE_DLC Primary and Secondary Return Codes                     Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_DLC           Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_ADAPTER         Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DUPLICATE_DLC          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DLC_FAILURE           Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.3. ACTIVATE_LOGICAL_LINKS ΓòÉΓòÉΓòÉ

ACTIVATE_LOGICAL_LINKS

This verb requests activation of the specified SNA logical link, or all of the
logical links configured as activate_at_startup (YES). When the verb returns
with primary return code OK, all of the links may not yet be activated. Use the
DISPLAY verb or subsystem management to determine which links have been
activated.

See ACTIVATE_LOGICAL_LINKS Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇACTIVATE_LOGICAL_LINKSΓöÇΓöÇkeynameΓöÇΓöÇnumber_of_linksΓöÇΓöÇΓö¼ΓöÇACTIVATE_ONEΓöÇΓöÇlink_namenameΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                               ΓööΓöÇACTIVATE_ALLΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          number_of_links
                    Specifies whether a specific logical link is to be
                    activated, or all of the logical links defined as
                    activate_at_startup (YES).

                    You must specify one of the following values:

             ACTIVATE_ONE
                       The logical link designated with the link_name parameter
                       is to be activated.

                link_name
                          The 8-byte EBCDIC name of the local logical link
                          station. This logical link can be activated by
                          specifying this name on the ACTIVATE_LOGICAL_LINKS
                          verb.

                          This a type A EBCDIC character string. If the name is
                          less than 8 bytes, it must be padded on the right
                          with EBCDIC blanks. In addition, the string cannot
                          begin with an EBCDIC "@" (X'7C').

             ACTIVATE_ALL
                       All logical links defined as activate_at_startup (YES),
                       if any, are to be activated. In this case, the link_name
                       parameter is not used.

                       If a preferred NN server is configured, Communications
                       Manager attempts to activate the link to it first. The
                       ACTIVATE_LOGICAL_LINKS verb will wait up to 40 seconds
                       for this link to become active before activating the
                       other links.

                       ACTIVATE_ALL is not supported in the node definitions
                       file. Its function is generated when APPC is started, if
                       any links were defined as activate_at_startup (YES).

 Return Codes

          The OK return code indicates that the ACTIVATE_LOGICAL_LINKS verb ran
          successfully.

          When the verb returns with a primary return code of OK, all of the
          links may not yet be activated. Use the DISPLAY verb or subsystem
          management to determine which links have been activated.

          ACTIVATE_LOGICAL_LINKS Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          ACTIVATE_LOGICAL_LINKS verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      ACTIVATE_LOGICAL_LINKS Primary and Secondary Return Codes                Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé OK           Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé NN_SERVER_FAILURE        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé NN_SERVER_TIMEOUT        Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_NUM_LINKS_SPECIFIED   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé ADAPTER_NOT_OPEN        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LINK_NAME_SPECIFIED   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé NO_LINKS_DEFD_AS_AUTO_ACTIVE  Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.4. CNOS (Change Number of Sessions) ΓòÉΓòÉΓòÉ

CNOS (Change Number of Sessions)

This verb establishes APPC LU 6.2 session limits. Use this verb to change the
maximum number of sessions allowed between a pair of LUs from 0 to a positive
number, or from a positive number to 0. One or more of the contention-winner
sessions can be automatically activated.

See CNOS Verb Control Block for information on the verb control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇCNOSΓöÇΓöÇkeynameΓöÇΓöÇlu_aliasnameΓöÇΓöÇpartner_lu_aliasΓöÇΓöÇΓö¼ΓöÇnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                              ΓööΓöÇ0ΓöÇΓöÇfully_qualified_partner_lu_namenameΓöÇΓöÿ
                    >ΓöÇΓöÇmode_name_selectΓöÇΓöÇΓö¼ΓöÇALLΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇset_negotiableΓöÇΓöÇΓö¼ΓöÇNOΓöÇΓöÇΓö¼ΓöÇΓöÇplu_mode_session_limitnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                               ΓööΓöÇONEΓöÇΓöÇmode_namenameΓöÇΓöÿ          ΓööΓöÇYESΓöÇΓöÿ
                    >ΓöÇΓöÇmin_conwinners_sourcenΓöÇΓöÇmin_conwinners_targetnΓöÇΓöÇauto_activatenΓöÇΓöÇresponsibleΓöÇΓöÇΓö¼ΓöÇSOURCEΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                            ΓööΓöÇTARGETΓöÇΓöÿ
                    >ΓöÇΓöÇdrain_sourceΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇdrain_targetΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇNOΓöÇΓöÇΓöÿ         ΓööΓöÇNOΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

                    Alternatively, you can select the default local LU by
                    specifying 8 bytes of binary zeros.

                    Note:  This parameter is case sensitive. Ensure that this
                    field is defined with the correct uppercase and lowercase
                    characters.

          partner_lu_alias
                    The locally known name for the partner LU.

                    This is an 8-byte ASCII character string. If the string is
                    less than 8 bytes, you must pad it on the right with ASCII
                    blanks.

                    Note:  This parameter is case sensitive. Ensure that this
                    field gets defined with the correct uppercase and lowercase
                    characters.

          fully_qualified_partner_lu_name
                    The fully qualified name for the partner LU.

                    This name is two Type A EBCDIC strings.  The name consists
                    of the name of the SNA network (the NETID) of the partner
                    LU (if any), a period, and the lu_name as it is known in
                    the network of the partner LU.  If no NETID is present, the
                    period is omitted. If the string is less than 17 bytes, you
                    must pad it on the right with EBCDIC blanks.  Except for
                    any EBCDIC blank padding, this string must exactly match
                    the fully qualified name of the local LU defined at the
                    node where that LU is located.

                    Note:

              1. The fully_qualified_partner_lu_name must be used when no
                 partner_lu_alias name is defined at the local node and the
                 partner LU is located at a different node. For example, it
                 must be used to start a conversion to an implicit remote LU.

              2. The fully_qualified_partner_lu_name is typically the name of
                 an LU located at a different node. However, the fully
                 qualified name can be an LU defined at the local node,
                 including the LU on which the TP was started.

          mode_name_select
                    Specifies the modes for which your program is setting or
                    resetting the session limits and contention-winner
                    polarities. This is either all the modes or a single mode
                    used between a pair of LUs.

                    You must specify one of the following values:

             ALL
                       Changes the session limits and polarities for all mode
                       names that apply to the partner (except for the
                       SNA-defined mode names, SNASVCMG and CPSVCMG). Use the
                       ALL setting only when resetting session limits to 0.

             ONE
                       Changes the session limits and polarities for the
                       specified mode name.

                mode_name
                          Specifies the EBCDIC mode name to be used in this
                          CNOS request.

                          You can specify the SNA-defined mode name SNASVCMG.
                          Use this mode only in a CNOS transaction when the
                          source LU and the target LU use parallel user
                          sessions. However, when resetting the session limits
                          to 0 for the SNASVCMG mode, the session limits of all
                          other modes between the two LUs must be reset first.

                          This is a Type A EBCDIC character string.

                          A mode name consisting of all blanks is supported.
                          The SNA-defined mode name CPSVCMG is not allowed.

          set_negotiable
                    Specifies whether APPC is to change the current setting for
                    the maximum negotiable session limit.

                    You must specify one of the following values:

             YES
                       The plu_mode_session_limit value specified in the CNOS
                       verb overrides the current setting for the maximum
                       negotiable session limit.

                       A normal CNOS negotiation still takes place. If the CNOS
                       verb contains no parameter errors, the new specified
                       value on the plu_mode_session_limit replaces the current
                       maximum negotiable session limit, even if the partner LU
                       (in the parallel-session case) negotiates the suggested
                       values down.

             NO
                       The plu_mode_session_limit is still used for normal CNOS
                       verb negotiation, but the maximum negotiable limit is
                       not changed.

          plu_mode_session_limit
                    For single-session connections, the value of this parameter
                    must be 0 or 1.

                    For parallel-session connections, this parameter specifies
                    the maximum number of parallel sessions allowed between the
                    source LU and target LU for the group of sessions under the
                    specified mode name.

                    If the mode session limit is currently greater than 0, the
                    value of this parameter must be 0. That is, the CNOS verb
                    can raise the limit above 0, but the next CNOS verb must
                    set the value to 0; a single CNOS verb cannot change the
                    mode session limit from one nonzero number to another.

                    When raising the mode session limit above 0 for a
                    parallel-session connection, the target LU can negotiate
                    this parameter to a value greater than 0 and less than the
                    specified session limit. The specified session limit, or
                    the negotiated session limit if it is negotiated, becomes
                    the new mode session limit and is returned in this field.

                    The value specified for this parameter must be greater than
                    or equal to the sum of the values specified on the CNOS
                    min_conwinners_source and min_conwinners_target parameters.

                    For the SNASVCMG mode name, the specified mode session
                    limit must be 0, 1, or 2. The specified limit depends on
                    whether your program is preparing the SNASVCMG mode for
                    more CNOS commands (1 or 2) or shutting down the mode (0).

                    Your program should not reset the SNASVCMG session limit to
                    0 until all other mode session limits between the two LUs
                    are reset to 0 and the count of active sessions for all
                    modes (except SNASVCMG) for the partner LU is 0.

                    The mode session limit should be large enough to
                    accommodate all active conversations on the mode for all
                    transaction programs.

          min_conwinners_source
                    Specifies the minimum number of sessions of which the
                    source LU is guaranteed to be the contention winner. The
                    specified number must be 0 or greater. The specified number
                    or the negotiated number becomes the new minimum number of
                    contention-winner sessions for the source LU. The sum of
                    this number and the target LUs minimum number of
                    contention-winner sessions cannot exceed the mode session
                    limit.

                    When the specified number is greater than half of the new
                    session limit (rounded up), the target LU can negotiate
                    this parameter down to half of the new mode session limit;
                    APPC returns the new value to the calling program in this
                    parameter. When the specified number is less than or equal
                    to half of the new mode session limit, the target LU cannot
                    negotiate this parameter.

                    For single-session connections, this parameter specifies
                    the desired contention-winner polarity of the session for
                    the source LU.

                    For the SNASVCMG mode name with a mode session limit of 2,
                    the specified minimum number of contention-winner sessions
                    for the source LU must be 1. For the SNASVCMG mode name
                    with a mode session limit of 1, the specified minimum
                    number of contention-winner sessions for the source LU must
                    be 0.

                    APPC uses this parameter only when the mode session limit
                    is set to a nonzero value.

          min_conwinners_target
                    Specifies the minimum number of sessions of which the
                    target LU is guaranteed to be the contention winner. The
                    specified number must be 0 or greater. The specified
                    number, or the negotiated number if it is negotiated,
                    becomes the new minimum number of contention-winner
                    sessions for the target LU. The sum of this number and the
                    source LUs minimum number of contention-winner sessions
                    cannot exceed the mode session limit.

                    The target LU can negotiate this parameter to a number less
                    than or equal to the new mode session limit minus the new
                    minimum number of contention-winner sessions for the source
                    LU; APPC returns the new value to the calling program in
                    this parameter.

                    For single-session connections, this parameter specifies
                    the desired contention-winner polarity for the target LU.

                    For the SNASVCMG mode name (with a mode session limit of 2
                    or 1), the specified minimum number of contention-winner
                    sessions for the target LU must be 1.

                    APPC uses this parameter only when the mode session limit
                    is set to a nonzero value.

          auto_activate
                    Specifies the number of the local LUs contention-winner
                    sessions for APPC to activate automatically.

                    APPC uses this parameter only when the mode session limit
                    is set to a nonzero value. If the value is greater than the
                    min_conwinners_source value (after any negotiation in the
                    parallel-session connection case), APPC uses the new
                    minimum number of contention winners for the source LU as
                    the auto-activation limit.

                    Warning: This parameter may conflict with the limited
                    resource definition of a logical link. Auto-activation by
                    either peer partner may reestablish sessions and link s,
                    possibly resulting in a thrashing situation. Therefore, you
                    should avoid specifying auto-activation between peer nodes
                    using adapters with limited resources or using a logical
                    link defined as a limited resource. (Refer to the Free
                    unused link field in the Communications Manager Data Link
                    Control (DLC) profile configuration in Workstation
                    Installation and Configuration Guide.)

          responsible
                    Specifies which LU is responsible for deactivating the
                    sessions as a result of resetting the session limit for
                    parallel-session connections. This parameter does not apply
                    to single-session connections or the SNASVCMG sessions. The
                    target LU may negotiate this value.

                    You must specify one of the following values:

             SOURCE
                       Specifies that the source LU is responsible. The target
                       LU cannot negotiate this specification.

             TARGET
                       Specifies that the target LU is responsible. The target
                       LU can negotiate this specification to SOURCE in which
                       case the source LU becomes responsible.

                    Whether an LU deactivates a session immediately after the
                    current conversation or after all queued conversations are
                    complete depends on the drain_source and drain_target
                    parameters.

             o If an LU is to drain its waiting (outbound) allocation requests,
               it continues to allocate conversations to active sessions. The
               responsible LU deactivates a session only when the conversation
               allocated to the session is deallocated and no request is
               waiting for allocation to any session with the specified mode
               name between the two LUs. The allocation of a waiting request
               takes precedence over the deactivation of a session.

             o If an LU is not to drain its waiting (outbound) allocation
               requests, the responsible LU deactivates a session as soon as
               the conversation allocated to the session is deallocated. If no
               conversation is allocated to the session, the responsible LU
               deactivates the session immediately.

                    However, this verb does not force deallocation of active
                    conversations.

                    The responsible and mode_name_select parameters are
                    interrelated as follows:

             o APPC ignores the responsible parameter for mode names for which
               the session limit is currently 0 if this CNOS verb specifies
               mode_name_select(ALL).

             o If the CNOS verb specifies mode_name_select(ONE) with a mode
               session limit of 0 and the current session limit for that mode
               name is already 0, the responsible parameter must specify the
               same LU (SOURCE or TARGET) that is currently responsible for
               deactivating sessions. APPC uses this parameter only when the
               CNOS verb specifies a mode session limit of 0.

          drain_source
                    Specifies whether the source LU can service its waiting
                    (outbound) allocation requests. For parallel-session
                    connections, the target LU cannot negotiate this parameter.
                    This parameter does not apply to the SNASVCMG sessions.

                    You must specify one of the following values:

             YES
                       Specifies that the source LU can drain its waiting
                       (outbound) allocation requests. The source LU continues
                       to allocate conversations to the sessions until no
                       requests are waiting for allocation, at which time
                       draining is ended. APPC rejects all ALLOCATE requests
                       issued at the source LU after draining ends.

             NO
                       Specifies that the source LU cannot drain its waiting
                       (outbound) allocation requests. APPC rejects all
                       requests currently waiting for allocation, or
                       subsequently issued requests at the source LU, and
                       returns a primary return code of ALLOCATION_ERROR to the
                       transaction programs.

                    For parallel-session connections, the drain_source and
                    mode_name_select parameters are interrelated as follows:

             o If the CNOS verb specifies mode_name_select(ALL) and
               drain_source (YES), APPC ignores the drain_source parameter for
               those mode names for which the session limit is currently 0.

             o If the CNOS verb specifies mode_name_select(ALL) and
               drain_source(NO), APPC accepts the drain_source parameter for
               all mode names. APPC ends draining for any mode currently
               draining its requests.

             o If the CNOS verb specifies mode_name_select(ONE), and
               drain_source (YES) is currently in effect, drain_source(NO)
               directs APPC to end the draining at the source LU for requests
               for the specified mode_name.

             o If the CNOS verb specifies mode_name_select(ONE) and
               drain_source(NO) is currently in effect, your program must
               specify drain_source(NO) again.

          drain_target
                    Specifies whether the target LU can service its waiting
                    (outbound) allocation requests. This parameter does not
                    apply to the SNASVCMG sessions.

                    For a parallel-session connection, the partner LU may
                    negotiate this value; APPC returns the new value to the
                    calling program in this parameter.

                    You must specify one of the following values:

             YES
                       Specifies that the target LU can service its waiting
                       (outbound) allocation requests. The target LU continues
                       to allocate conversations to the sessions until no
                       requests are waiting for allocation, at which time its
                       draining is ended. ALLOCATE requests issued at the
                       target LU after draining ends are rejected.

                       For parallel-session connections, the target LU can
                       negotiate this specification to NO, in which case the
                       target LU does not drain its waiting (outbound)
                       allocation requests.

             NO
                       Specifies that the target LU cannot drain its waiting
                       (outbound) allocation requests. Requests currently
                       waiting for allocation or issued later at the target LU
                       will be rejected. The target LU cannot negotiate this
                       specification for parallel-session connections.

                    For parallel-session connections, this parameter and the
                    mode_name_select parameter are interrelated as follows:

             o If the CNOS verb specifies mode_name_select(ALL) and
               drain_target (YES), APPC ignores the drain_target parameter for
               the mode names for which the session limit is currently 0.

             o If the CNOS verb specifies mode_name_select(ALL) and
               drain_target(NO), APPC accepts the drain_target parameter for
               all mode names, regardless of the current session limit. Any
               draining of waiting (outbound) allocation requests at the target
               LU is ended.

             o If the CNOS verb specifies mode_name_select(ONE) and
               drain_target (YES) is currently in effect, drain_target(NO) ends
               the target LUs draining.

             o If the CNOS verb specifies mode_name_select(ONE) and
               drain_target (YES) and drain_target(NO) is currently in effect,
               the target LU can either accept the drain_target (YES) parameter
               or negotiate the parameter to NO. After the target LU accepts
               the drain_target (YES) parameter, it can drain any remaining
               waiting (outbound) allocation requests.

               Note:  CNOS issued by subsystem management always uses
                      drain_source if the drain_sourcevalue is YES and the
                      responsible value is SOURCE.


 Return Codes

          The OK return code indicates that the CNOS verb ran successfully.

          The following secondary return codes indicate whether APPC accepts
          the parameters as specified in the CNOS verb or as negotiated by the
          partner LU.

          CNOS_ACCEPTED APPC accepts the session limits and responsibility as
                    specified.
          CNOS_NEGOTIATED APPC accepts the session limits and responsibility as
                    negotiated by the partner LU. Values that can be negotiated
                    are: plu_mode_session_limit, min_conwinners_source,
                    min_conwinners_target, responsible, and drain_target.

          CNOS Primary and Secondary Return Codes. shows the primary and
          secondary error return codes associated with the CNOS verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      CNOS Primary and Secondary Return Codes.                         Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé ALLOCATION_ERROR    Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé ALLOCATION_FAILURE_NO_RETRY   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé ALLOCATION_FAILURE_RETRY    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé CNOS_LOCAL_RACE_REJECT Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé CNOS_PARTNER_LU_REJECT Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé CNOS_MODE_CLOSED        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CNOS_MODE_NAME_REJECT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CNOS_COMMAND_RACE_REJECT    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé ALL_MODE_MUST_RESET       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé AUTOACT_EXCEEDS_SESSLIM     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé BAD_LU_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé BAD_PARTNER_LU_ALIAS      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé BAD_SNASVCMG_LIMITS       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CHANGE_SRC_DRAINS        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CNOS_IMPLICIT_PARALLEL     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CPSVCMG_MODE_NOT_ALLOWED    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé EXCEEDS_MAX_ALLOWED       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé MIN_GT_TOTAL          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé MODE_CLOSED           Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé RESET_SNA_DRAINS        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé SINGLE_NOT_SRC_RESP       Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé CANT_RAISE_LIMITS        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LU_DETACHED           Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé SNASVCMG_RESET_NOT_ALLOWED   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          If a CNOS verb is not issued to set the mode session limit before a
          program issues its first APPC [MC_]ALLOCATE verb,
          [MC_]SEND_CONVERSATION verb, or CPI Communications CMALLC call for a
          given partner LU and mode, APPC will internally generate one using
          the values from the mode definition.

          When setting the limits for a parallel-session connection, the two
          LUs negotiate the mode session limits, drain settings, and
          responsibility values. APPC updates these parameters in the CNOS
          command to reflect the settings agreed to by both LUs during
          negotiation. Use subsystem management or your program can issue the
          DISPLAY verb to obtain the negotiated values for the mode session
          limit.

          No CNOS negotiation occurs when setting the limits for a single
          session (that is, the two LUs do not negotiate drain settings or
          responsibility values). Therefore, coordinate the mode definition
          parameter settings between partner LUs using a single-session
          connection by defining a single session mode at each node.

          As part of setting up the initial limits, the CNOS verb also sets the
          guaranteed (that is, the minimum) number of contention-winner and
          contention-loser sessions and sets the automatic activation count for
          the source LUs contention-winner sessions. The action of the CNOS
          verb normally affects only the group of sessions with the specified
          mode name between the source LU and the target LU. Alternatively, one
          CNOS verb can reset the session limits of all modes for a partner LU.

          APPC enforces the new mode session limit and the contention-winner
          polarities until one side or the other changes them by issuing a
          subsequent CNOS verb. The CNOS transaction is invisible at the target
          LUs API, regardless of which LU is the target. The results of the
          CNOS transaction can be obtained using subsystem management or the
          DISPLAY verb.


ΓòÉΓòÉΓòÉ 7.4.1. Setting a Session Limit to 0 ΓòÉΓòÉΓòÉ

After the CNOS verb raises the session limit above 0, it can reset the limit to
0 only.  It cannot set the session limit to a value that is not 0, and it
cannot redistribute the number of sessions allocated as the contention winners
and losers. Therefore, your program cannot change the mode session limits if
the two LUs have already set the limits to a nonzero value, regardless of which
LU initiated the CNOS transaction.

APPC may activate one or more LU-LU sessions with the specified mode name as a
result of initializing the session limit.  APPC deactivates all LU-LU sessions
for the specified mode name (or for all mode names for a partner LU) as a
result of resetting the session limit to 0.  APPC deactivates each session as
it becomes free and does not interrupt active conversations.

A separate value, the maximum negotiable session limit, is used in CNOS
negotiations. If the set_negotiable parameter value is YES, the mode session
limit value given in this CNOS verb also sets the maximum negotiable session
limit.


ΓòÉΓòÉΓòÉ 7.5. DEACTIVATE_CONVERSATION_GROUP ΓòÉΓòÉΓòÉ

DEACTIVATE_CONVERSATION_GROUP

This verb deactivates the specified LU 6.2 session identified by the
conversation group ID. DEACTIVATE_CONVERSATION_GROUP is an alternative to the
DEACTIVATE_SESSION verb.

See DEACTIVATE_CONV_GROUP Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEACTIVATE_CONVERSATION_GROUPΓöÇΓöÇkeyΓöÇΓöÇnameΓöÇΓöÇlu_aliasΓöÇΓöÇΓö¼ΓöÇnameΓöÇΓö¼ΓöÇΓöÇconversation_group_idΓöÇΓöÇidΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                ΓööΓöÇ 0ΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇtypeΓöÇΓöÇΓö¼ΓöÇCLEANUPΓöÇΓöÇsense_dataΓöÇΓöÇvalueΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                         ΓööΓöÇNORMALΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

                    Alternatively, you can select the default local LU by
                    specifying 8 bytes of binary zeros.

                    Note:  This parameter is case sensitive. Ensure that this
                           field is defined with the correct uppercase and
                           lowercase characters.

          conversation_group_id
                    Specifies the conversation group ID of the LU-LU session to
                    be deactivated.

                    The conversation group ID is a returned parameter on the
                    [MC_]ALLOCATE, [MC_]SEND_CONVERSATION, [MC_]GET_ATTRIBUTES,
                    or RECEIVE_ALLOCATE verb. Your program can get a list of
                    all current conversation group IDs by issuing the DISPLAY
                    verb, requesting Session Information.

          type
                    Specifies the type of deactivation that APPC should
                    perform. You must specify one of the following values:

             CLEANUP
                       Specifies that APPC should perform cleanup deactivation.
                       This type of deactivation terminates the session
                       immediately without waiting for a response from the
                       partner LU. The sense_data parameter is used when
                       CLEANUP is specified.

             NORMAL
                       Specifies that APPC should perform normal deactivation.
                       This type of deactivation terminates the session after
                       all conversations using the session are ended. The
                       sense_data parameter is not used when NORMAL is
                       specified.

          sense_data
                    Supplies the sense data for the CLEANUP type of
                    deactivation. The sense data is part of the deactivation
                    (UNBIND) request. This parameter is not used for NORMAL
                    deactivation and is ignored.

 Return Codes

          The OK return code indicates that the DEACTIVATE_CONVERSATION_GROUP
          verb ran successfully.

          DEACTIVATE_CONVERSATION_GROUP Primary and Secondary Return Codes
          shows the primary and secondary error return codes associated with
          the DEACTIVATE_CONVERSATION_GROUP verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEACTIVATE_CONVERSATION_GROUP Primary and Secondary Return Codes             Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé BAD_LU_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CPSVCMG_MODE_NOT_ALLOWED    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEACT_CG_INVALID_CGID      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEACT_CG_INVALID_TYPE      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.6. DEACTIVATE_DLC ΓòÉΓòÉΓòÉ

DEACTIVATE_DLC

This verb deactivates the specified adapter. All active links using that
adapter are deactivated with type(HARD).

See DEACTIVATE_DLC Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEACTIVATE_DLCΓöÇΓöÇkeynameΓöÇΓöÇdlc_namenameΓöÇΓöÇadapter_numbernΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          dlc_name
                    The 8-byte ASCII name of the local data link control (DLC).
                    This is the name used to configure a DLC in the
                    Communications Manager DLC profile. The valid names are:

             o 'ETHERAND'
             o 'IBMPCNET'
             o 'IBMTRNET'
             o 'SDLC   '
             o 'TWINAX  '
             o 'X25DLC  '
             o 'IDLC   '

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

          adapter_number
                    Specifies the adapter number to be deactivated. This must
                    be the same number as that configured for the adapter in a
                    Communications Manager DLC profile.

 Return Codes

          The OK return code indicates that the DEACTIVATE_DLC verb ran
          successfully.

          DEACTIVATE_DLC Primary and Secondary Return Codes shows the primary
          and secondary error return codes associated with the DEACTIVATE_DLC
          verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEACTIVATE_DLC Primary and Secondary Return Codes                    Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_ADAPTER         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DLC           Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEACT_DLC_ADAPTER_NOT_OPEN   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.7. DEACTIVATE_LOGICAL_LINK ΓòÉΓòÉΓòÉ

DEACTIVATE_LOGICAL_LINK

This verb deactivates the specified SNA logical link.

See DEACTIVATE_LOGICAL_LINK Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEACTIVATE_LOGICAL_LINKΓöÇΓöÇkeynameΓöÇΓöÇlink_namenameΓöÇΓöÇtypeΓöÇΓöÇΓö¼ΓöÇHARDΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                                  ΓööΓöÇSOFTΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          link_name
                    The 8-byte name of the link to be deactivated. Your program
                    can get the link name by issuing the DISPLAY verb,
                    requesting Link Information.

          type
                    The type of deactivation for the specified SNA logical
                    link.

                    You must specify one of the following values:

             HARD
                       The link is to be deactivated immediately regardless of
                       whether sessions are active on that link.

             SOFT
                       APPC is to deactivate the link when all sessions on the
                       specified link have ended. This includes all LU-LU,
                       SSCP-LU, and SSCP-PU sessions on the link. If this verb
                       has already been issued at least once, APPC will return
                       the STATE_CHECK primary return_code with the
                       LINK_DEACT_IN_PROGRESS secondary return_code.

 Return Codes

          The OK return code indicates that the DEACTIVATE_LOGICAL_LINK verb
          ran successfully.

          Note:  This verb does not wait for the link to be deactivated. APPC
                 returns immediately to the calling program with an OK
                 return_code if it sees that the link is able to be
                 deactivated.

          DEACTIVATE_LOGICAL_LINK Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEACTIVATE_LOGICAL_LINK verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEACTIVATE_LOGICAL_LINK Primary and Secondary Return Codes               Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_LINK_ID         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé UNRECOGNIZED_DEACT_TYPE     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEACT_LINK_UNSUCCESSFUL     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LINK_DEACT_IN_PROGRESS     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.8. DEACTIVATE_SESSION ΓòÉΓòÉΓòÉ

DEACTIVATE_SESSION

This verb deactivates the specified LU 6.2 session or all of the LU 6.2
sessions on a specified mode. This verb differs from the
DEACTIVATE_CONVERSATION_GROUP verb in that it deactivates a session via the
session_id instead of the conversation_group_id.

See DEACTIVATE_SESSION Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEACTIVATE_SESSIONΓöÇΓöÇkeynameΓöÇΓöÇsession_ididΓöÇΓöÇlu_aliasnameΓöÇΓöÇpartner_lu_aliasΓöÇΓöÇnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇmode_namenameΓöÇΓöÇtypeΓöÇΓöÇΓö¼ΓöÇCLEANUPΓöÇΓöÇsense_datavalueΓöÇΓö¼ΓöÇΓöÇfully_qualified_partner_lu_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                ΓööΓöÇNORMALΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          session_id
                    Specifies the 8-byte internal identifier of the LU-LU
                    session to be deactivated if a particular session is to be
                    deactivated. By setting this session_id parameter to all
                    binary zeros, a program can deactivate all active sessions
                    for the specified LU, partner LU, and mode. Your program
                    can get the session ID by issuing the DISPLAY verb,
                    requesting Session Information.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

                    Alternatively, you can select the default local LU by
                    specifying 8 bytes of binary zeros.

                    Note:  This parameter is case sensitive. Ensure that this
                           field is defined with the correct uppercase and
                           lowercase characters.

          partner_lu_alias
                    The locally known name for the partner LU.

                    This is an 8-byte ASCII character string. If the string is
                    less than 8 bytes, you must pad it on the right with ASCII
                    blanks.

                    Note:  This parameter is case sensitive. Ensure that this
                           field gets defined with the correct uppercase and
                           lowercase characters.

                    You can use the fully_qualified_partner_lu_name parameter
                    to specify the partner LU instead of the partner_lu_alias.
                    To do this, specify all binary zeros for the
                    partner_lu_alias parameter.

                    Note:  The partner_lu_alias is typically the name of an LU
                           located at a different node. However, the alias name
                           may be that of an LU defined at the local node,
                           including the LU specified in lu_alias.

          mode_name
                    The 8-byte EBCDIC name for the mode. The mode name is used
                    to designate the network properties for a group of
                    sessions. This is the name of the mode as it is known
                    throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

                    You cannot deactivate the CPSVCMG mode.

          type
                    The type of deactivation that APPC should perform.

                    You must specify one of the following values:

             CLEANUP
                       Specifies that APPC should perform cleanup deactivation.
                       This type of deactivation terminates the session
                       immediately without waiting for a response from the
                       partner LU. The sense_data parameter is used when
                       CLEANUP is specified.

             NORMAL
                       Specifies that APPC should perform normal deactivation.
                       This type of deactivation terminates the session after
                       all conversations using the session are ended. The
                       sense_data parameter is not used when NORMAL is
                       specified.

          sense_data
                    Supplies the sense data for the CLEANUP type of
                    deactivation. The sense data is carried on the deactivation
                    (UNBIND) request. This parameter is not used for NORMAL
                    deactivation and is ignored.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

 Return Codes

          The OK return code indicates that the DEACTIVATE_SESSION verb ran
          successfully.

          DEACTIVATE_SESSION Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEACTIVATE_SESSION verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEACTIVATE_SESSION Primary and Secondary Return Codes                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé BAD_LU_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CPSVCMG_MODE_NOT_ALLOWED    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MODE          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_PARTNER_LU_NAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_SESSION_ID       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_TYPE          Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.9. REJECT_INCOMING_CALLS ΓòÉΓòÉΓòÉ

REJECT_INCOMING_CALLS

Instructs connection manager to reject incoming calls corresponding to the
specified Incoming Call Directory (ICD) entry, instead of routing them to the
application named in the ICD entry.

See REJECT_INCOMING_CALLS Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇREJECT_INCOMING_CALLSΓöÇΓöÇkey nameΓöÇΓöÇICD_Entry_Name nameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key, if the keylock
                    feature has been secured.

                    This is an 8-byte ASCII character string.  If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.  Refer to the User's Guide for details of the
                    keylock feature.

          ICD_Entry_Name
                    Specifies the name of the ICD entry for which calls are to
                    be accepted.

                    ICD entry names are configured via Connection Manager
                    configuration utilities, and govern connection manager's
                    response to an incoming call.

                    When an incoming call is received, the characteristics of
                    the call are matched against the characteristics of all ICD
                    entries configured to connection manager.  When an ICD
                    entry is found which matches the characteristics of the
                    incoming call, connection manager examines the entry to
                    determine whether to route the incoming call notification
                    to an application program, or to reject the call.  This
                    verb sets the given ICD entry to cause connection manager
                    to reject the incoming call notification, without routing
                    it to the application program.

 Return Codes

          The OK return code indicates that the REJECT_INCOMING_CALLS verb ran
          successfully.

          When the verb returns with primary return code OK, the ICD entry may
          not yet have been set to reject incoming calls.  Use the Display verb
          or subsystem management to determine when the ICD entry is ready to
          reject calls.

          REJECT_INCOMING_CALLS Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          REJECT_INCOMING_CALLS verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      REJECT_INCOMING_CALLS Primary and Secondary Return Codes                Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé BAD_ICD_NAME          Γöé Numeric List of Secondary Return Codes Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.10. START_AM ΓòÉΓòÉΓòÉ

START_AM

This verb starts the APPC attach manager. Programs must have the attach manager
started for APPC to accept APPC RECEIVE_ALLOCATE verbs or CPI Communications
Accept_Conversation (CMACCP) calls, and to process incoming attaches.

See START_AM Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇSTART_AMΓöÇΓöÇkeynameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

 Return Codes

          The OK return code indicates that the START_AM verb ran successfully.

          START_AM Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the START_AM verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      START_AM Primary and Secondary Return Codes                       Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé ATTACH_MGR_ALREADY_ACTIVE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.11. STOP_AM ΓòÉΓòÉΓòÉ

STOP_AM

This verb stops the APPC attach manager. All queued Attaches are rejected and
all held APPC RECEIVE_ALLOCATE verbs or CPI Communications Accept_Conversation
(CMACCP) calls are returned to the program that issued them. Any future
incoming attaches, RECEIVE_ALLOCATE verbs, or CMACCP calls are rejected until
the attach manager is restarted.

See STOP_AM Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇSTOP_AMΓöÇΓöÇkeynameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

 Return Codes

          The OK return code indicates that the STOP_AM verb ran successfully.

          STOP_AM Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the STOP_AM verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      STOP_AM Primary and Secondary Return Codes                       Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé ATTACH_MGR_ALREADY_INACTIVE   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8. Configuration Verbs ΓòÉΓòÉΓòÉ

This chapter contains an alphabetical reference of the configuration verbs. The
DEFINE verbs may be defined in the .NDF file or issued by application programs.
All the configuration verbs except the .NDF-only verbs can be issued by
application programs. The configuration verbs include:


ΓòÉΓòÉΓòÉ 8.1. SNA Node Configuration Verbs ΓòÉΓòÉΓòÉ

In addition to the configuration verbs listed above, this chapter also
describes SNA node definition configuration verbs that you can use only for
defining configurations within your node definitions file (.NDF). These verbs
include:

 o DEFINE_APPC_ATTACH_ROUTE
 o DEFINE_CLIENT_DEP_APPC_ACCESS 
 o DEFINE_CLIENT_INDEP_APPC_ACCESS 
 o DEFINE_CLIENT_LUA_ACCESS 
 o DEFINE_CONNECTION_NETWORK
 o DEFINE_CPIC_SIDE_INFO
 o DEFINE_DEFAULTS
 o DEFINE_LOCAL_CP
 o DEFINE_LUA_POOL

 For more information on the format of configuration verbs as they are used in
 the .NDF file, view the CMVERIFY.TXT file located in the subdirectory, \CMLIB.


ΓòÉΓòÉΓòÉ 8.2. DEFINE_COS ΓòÉΓòÉΓòÉ

DEFINE_COS

This verb defines a new class of service (COS) definition or replaces an
existing one. If the COS name is already defined, and there is no active mode
that refers to the COS name, the definition is replaced. If the COS name is not
already defined, the new definition is added. In either case, the definition
becomes active immediately. If an active mode exists that refers to the COS
name, the verb is rejected.

The COS definitions should be consistent across all network nodes in the APPN
network. Otherwise, different network nodes may choose inconsistent routes
using the same selection criteria.

You can remove user-defined DEFINE_COS definitions with the DELETE_COS verb.
The seven IBM-supplied COS definitions cannot be deleted.

See DEFINE_COS Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_COSΓöÇΓöÇkeynameΓöÇΓöÇcos_namenameΓöÇΓöÇtransmission_priorityΓöÇΓöÇΓö¼ΓöÇNETWORKΓöÇΓö¼ΓöÇΓöÇnumber_of_node_rowsnΓöÇΓöÇΓöÇΓöÇ>
                                                   Γö£ΓöÇHIGHΓöÇΓöÇΓöÇΓöÇΓöñ
                                                   Γö£ΓöÇMEDIUMΓöÇΓöÇΓöñ
                                                   ΓööΓöÇLOWΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

          Specify for each node row:

                    >>ΓöÇΓöÇnode_row_weightnΓöÇΓöÇroute_addition_res_minnΓöÇΓöÇroute_addition_res_maxnΓöÇΓöÇcongestion_minΓöÇΓöÇΓö¼ΓöÇNOΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ>
                                                                ΓööΓöÇYESΓöÇΓöÿ
                    >ΓöÇΓöÇcongestion_maxΓöÇΓöÇΓö¼ΓöÇNOΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                              ΓööΓöÇYESΓöÇΓöÿ

                    >ΓöÇΓöÇnumber_of_tg_rowsnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

          Specify for each tg row:

                    >>ΓöÇΓöÇtg_row_weightnΓöÇΓöÇeffective_capacity_minnΓöÇΓöÇeffective_capacity_maxnΓöÇΓöÇcost_per_connect_time_minnΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇcost_per_connect_time_maxnΓöÇΓöÇcost_per_byte_minnΓöÇΓöÇcost_per_byte_maxnΓöÇΓöÇsecurity_minΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇNONSECUREΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇsecurity_maxΓöÇΓöÇΓö¼ΓöÇNONSECUREΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      Γö£ΓöÇPUBLIC_SWITCHED_NETWORKΓöÇΓöñ         Γö£ΓöÇPUBLIC_SWITCHED_NETWORKΓöÇΓöñ
                      Γö£ΓöÇUNDERGROUND_CABLEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ         Γö£ΓöÇUNDERGROUND_CABLEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      Γö£ΓöÇSECURE_CONDUITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ         Γö£ΓöÇSECURE_CONDUITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      Γö£ΓöÇGUARDED_CONDUITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ         Γö£ΓöÇGUARDED_CONDUITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      Γö£ΓöÇENCRYPTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ         Γö£ΓöÇENCRYPTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      ΓööΓöÇGUARDED_RADIATIONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ         ΓööΓöÇGUARDED_RADIATIONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇpropagation_delay_minΓöÇΓöÇΓö¼ΓöÇMINIMUMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇpropagation_delay_maxΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                 Γö£ΓöÇLANΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                 Γö£ΓöÇTELEPHONEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                 Γö£ΓöÇPACKET_SWITCHED_NETWORKΓöÇΓöñ
                                 Γö£ΓöÇSATELLITEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                 ΓööΓöÇMAXIMUMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇMINIMUMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇuser_defined_1_minnΓöÇΓöÇuser_defined_1_maxnΓöÇΓöÇuser_defined_2_minnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      Γö£ΓöÇLANΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      Γö£ΓöÇTELEPHONEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      Γö£ΓöÇPACKET_SWITCHED_NETWORKΓöÇΓöñ
                      Γö£ΓöÇSATELLITEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      ΓööΓöÇMAXIMUMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇuser_defined_2_maxnΓöÇΓöÇuser_defined_3_minnΓöÇΓöÇuser_defined_3_maxnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          cos_name
                    The 8-byte EBCDIC name for the COS. This is the name of the
                    COS as it is known throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

          transmission_priority
                    Specifies the transmission priority for this COS. You must
                    specify one of the following values:

             o NETWORK
             o HIGH
             o MEDIUM
             o LOW

          number_of_node_rows
                    Specifies the number of node descriptions, or rows, and
                    associated weights defined for this COS. You can specify a
                    value in the range of 1-8.

                    Each node row contains a range of values for route addition
                    resistance and congestion and a weight to be associated
                    with nodes that are within these ranges. The node weights
                    are used in route calculation.

                    Node Row Group

                    You must specify a value for each of the following
                    parameters for each number_of_node_rows definition:

             node_row_weight
                       Specifies the weight to be associated with nodes that
                       fit the criteria specified by this node row. You can
                       specify a value in the range of 0-255.

             route_addition_res_min

             route_addition_res_max
                       These parameters specify the minimum and maximum route
                       addition resistance values for this row. You can specify
                       a value in the range of 0-255 for each parameter.

             congestion_min

             congestion_max
                       These parameters specify whether congestion is
                       tolerated. You must specify one of the following values
                       for each parameter:

                YES
                          If both parameters are set to YES, only nodes that
                          are highly congested will fit this node row
                          description.

                NO
                          If both parameters are set to NO, only NO congestion
                          is tolerated for this node row.

                       If congestion_min specifies NO and congestion_max
                       specifies YES, then all nodes fall within the
                       congestions range and congestion is not a criteria for
                       this row.

          number_of_tg_rows
                    Specifies the number of transmission group (TG)
                    descriptions, or rows, and associated weights defined for
                    this COS. Each TG row contains a range of values for
                    effective capacity, cost per connect time, cost per byte,
                    security, propagation delay and up to 3 user-defined TG
                    characteristics and a weight to be associated with TGs that
                    are within these ranges. The TG weights are used in route
                    calculation.

          TG Row Group

          You must specify a value for each of the following parameters for
          each number_of_tg_rows definition.

          tg_row_weight
                    Specifies the weight to be associated with TGs that fit the
                    criteria specified by this TG row. You can specify a value
                    in the range of 0-255.

          effective_capacity_min

          effective_capacity_max
                    These parameters specify the minimum and maximum actual
                    bits per second rate (line speed) for this TG row. (The
                    effective capacity is derived from the link bandwidth and
                    maximum load factor.) These values are encoded as 1-byte
                    floating point numbers. This value is encoded as a 1-byte
                    floating point number. The encoding is represented by the
                    formula 0.1 mmm * 2**eeeee, where the bit representation of
                    the byte is b'eeeeemmm'. Each unit of effective capacity is
                    equal to 300 bits per second.

          cost_per_connect_time_min

          cost_per_connect_time_max
                    These parameters specify the minimum and maximum cost per
                    connect time values for this row. Valid values are integer
                    values in the range 0-255, where 0 represents the lowest
                    cost per connect time and 255 represents the highest cost
                    per connect time.

          cost_per_byte_min

          cost_per_byte_max
                    The minimum and maximum cost per byte values for this row.
                    Valid values are integer values in the range 0-255, where 0
                    represents the lowest cost per byte and 255 represents the
                    highest cost per byte.

          security_min

          security_max
                    These parameters specify the minimum and maximum security
                    values for this row. The following list describes the valid
                    values for these parameters in the order of their
                    effectiveness.

             NONSECURE
                       Specifies that no security exists, such as satellite
                       links or underground lines.

             PUBLIC_SWITCHED_NETWORK
                       Specifies that data transmitted over this adapter will
                       flow through a public switched network.

             UNDERGROUND_CABLE
                       Specifies transmission over a secure underground cable.

             SECURE_CONDUIT
                       Specifies that the line is secure conduit that is not
                       guarded, such as pressurized pipe.

             GUARDED_CONDUIT
                       Specifies that the conduit is protected against physical
                       tapping.

             ENCRYPTED
                       Specifies that the adapter, or the system software that
                       controls the adapter, encrypts the data transmitted over
                       the line.

             GUARDED_RADIATION
                       Specifies that the line is protected against physical
                       and radiation tapping.

          propagation_delay_min

          propagation_delay_max
                    These parameters specify the minimum and maximum
                    propagation delay values for this TG row. This value
                    represents the amount of time it takes for a signal to
                    travel the length of the logical link, in microseconds. The
                    following list describes the valid values, with MINIMUM
                    representing the least propagation delay and MAXIMUM
                    representing the longest propagation delay.

             MINIMUM
                       Specifies there is no propagation delay.

             LAN
                       Specifies that propagation delay is less than 480
                       microseconds.

             TELEPHONE
                       Specifies a delay between 480 and 49152 microseconds.

             PACKET_SWITCHED_NETWORK
                       Specifies a delay between 49152 and 245760 microseconds.

             SATELLITE
                       Specifies a delay longer than 245760 microseconds.

             MAXIMUM
                       Specifies the maximum delay allowed.

          user_defined_1_min

          user_defined_1_max
                    These parameters specify the minimum and maximum values of
                    the first user-defined TG characteristic for this TG row.
                    You can specify a value in the range of 0-255 for each
                    parameter.

          user_defined_2_min

          user_defined_2_max
                    These parameters specify the minimum and maximum values of
                    the second user-defined TG characteristic for this TG row.
                    You can specify a value in the range of 0-255 for each
                    parameter.

          user_defined_3_min

          user_defined_3_max
                    These parameters specify the minimum and maximum values of
                    the third user-defined TG characteristic for this TG row.
                    You can specify a value in the range of 0-255 for each
                    parameter.

 Return Codes

          The OK return code indicates that the DEFINE_COS ran successfully:

          DEFINE_COS Primary and Secondary Return Codes shows the primary and
          secondary return codes associated with the DEFINE_COS verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_COS Primary and Secondary Return Codes                      Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEF_COS_INVALID_SECURITY    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_CONGESTION       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_COS_NAME        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_NUMBER_OF_NODE_ROWS   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_NUMBER_OF_TG_ROWS    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_PROPAGATION_DELAY    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé MAX_VALUE_LESS_THAN_MIN     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé NODE_ROW_WGT_LESS_THAN_LAST   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé TG_ROW_WGT_LESS_THAN_LAST    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé SNA_DEFD_COS_CANT_BE_CHANGED  Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_COS verb is used to provide additional COS definitions
          that are not supplied with Communications Manager. The following COS
          definitions are supplied with Communications Manager:

          o #BATCH
          o #BATCHSC
          o #CONNECT
          o #INTER
          o #INTERSC
          o CPSVCMG
          o SNASVCMG

          Refer to Workstation Installation and Configuration Guide for the
          parameter values for these COS definitions.


ΓòÉΓòÉΓòÉ 8.3. DEFINE_DEFAULT_SOC ΓòÉΓòÉΓòÉ

DEFINE_DEFAULT_SOC

This verb defines a default sphere of control (SOC) for a specified MS
category. You use the DEFINE_DEFAULT_SOC verb to enable the local APPN network
node (NN) to be the default focal point (FP) for the MS category. The SOC nodes
are the NNs represented in the local NN's topology database (TDB). All NNs in
the TDB become part of the SOC, except those that have a higher ranking FP. A
default SOC represents a particular ranking for the FP. You can also specify a
backup FP node for the MS category, where the backup FP node is not the local
NN. The new definition takes effect immediately. The local control point (CP)
begins establishing the FP-EP relationship with the SOC nodes either when this
verb completes, or when a FP application that manages the MS category registers
itself locally, whichever occurs last.

This verb should not be used to define the local node as a backup FP.

You can remove a DEFINE_DEFAULT_SOC definition with the DELETE_DEFAULT_SOC
verb.

See DEFINE_DEFAULT_SOC Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_DEFAULT_SOCΓöÇΓöÇkeynameΓöÇΓöÇms_categorynameΓöÇΓöÇbackup_fp_indicatorΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇKEEPΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇREPLACEΓöÇΓöÇbackup_fp_fq_cp_namenameΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          ms_category
                    The name of the MS category for the SOC. Specify either a
                    4-byte SNA-defined name or a 1-8-byte Type A EBCDIC name,
                    left justified and filled on the right with EBCDIC space
                    (X'40') characters.

          backup_fp_indicator
                    The indicator of whether the default SOC nodes are to have
                    a default backup FP.

             KEEP
                       Indicates the SOC nodes are to keep their current backup
                       FP, if any.

             REPLACE
                       Indicates the SOC nodes are to replace their current
                       backup FP, if any, with the one specified on the
                       backup_fp_fq_cp_name parameter.

                backup_fp_fq_cp_name
                          The CP name of the node at which the backup FP is
                          located. The name must be network qualified, left
                          justified, and filled on the right with EBCDIC space
                          (X'40') characters. If the backup FP is located at a
                          type 5 host system that supports receipt of MDS-MUs,
                          this parameter indicates the LU name for the FP.

                          This parameter is meaningful only if the
                          backup_fp_indicator parameter specifies REPLACE;
                          otherwise, this parameter is ignored. You may set
                          this parameter to a null value (all binary zeros) to
                          indicate the EPs are to have no backup FP.

 Return Codes

          The OK return code indicates that the DEFINE_DEFAULT_SOC verb ran
          successfully:

          DEFINE_DEFAULT_SOC Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_DEFAULT_SOC verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_DEFAULT_SOC Primary and Secondary Return Codes                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEFAULT_SOC_DISALLOWED_ON_EN  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DEFAULT_BACKUP_FP_INDICΓöéTNumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DEFAULT_BACKUP_FP_CP_NAΓöéENumeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_DEFAULT_SOC verb is used to define a SOC of EP nodes based
          on the network node (NN) information in the local node's topology
          database. Only NNs in the topology database can be EPs of the default
          SOC. The NNs send their served end nodes (ENs) an MS capabilities
          (X'E1' subvector), which establishes a domain FP-EP relationship for
          the ENs.

          The definition of a SOC and the registration of a focal point (FP)
          application must both occur on the same NN before the NN can
          establish an FP-EP relationship with the EP nodes in the SOC; an
          FP-EP relationship is established by exchanging MS capabilities
          messages between the FP and EP nodes.

          If an FP application is already registered for the MS category when
          the DEFINE_DEFAULT_SOC verb is issued, the local node establishes an
          FP-EP relationship with each NN in the topology database, except for
          network nodes that have an active explicit or implicit FP (see next
          paragraph). Conversely, if an FP application is not registered for
          the MS category when the DEFINE_DEFAULT_SOC verb is issued, the local
          node waits until the FP application is registered before it
          establishes an FP-EP relationship with the NNs.

          An EP node maintains a ranking of FP nodes that establish an FP-EP
          relationship with the EP node. When an EP node has an active FP-EP
          relationship, that FP can can be replaced by another FP of equal or
          higher rank. Each time an FP is replaced by another FP, a new FP-EP
          relationship is established. The ranking is as follows, listed in
          order from highest to lowest rank:

          Primary         A primary FP can be either explicitly or implicitly
                          defined for NNs and ENs.
          Backup          A backup FP can be either explicitly or implicitly
                          defined for NNs and ENs.
          Default Primary Only NNs can have a default primary FP.
          Default Backup  Only NNs can have a default backup FP.
          Domain          Only ENs can have a domain FP.
          Host            Only subarea-adjacent NNs or ENs can have a host FP.

          The DEFINE_EXPLICIT_SOC verb may be issued to define a SOC for
          explicitly specified nodes, concurrent with the default definition.
          If an explicitly specified node is a NN in the topology database, the
          explicit definition is used instead of the default definition.

          The EP node may define an implicit FP for the EP node. If the EP node
          implicitly defines the local node as its FP, the implicit definition
          is used instead of the default definition.

          If a NN in the topology database is, or becomes, unavailable such
          that the FP-EP relationship is broken or not established, the local
          FP node tries to establish or reestablish it as updates to the
          topology database occur. The default FP node always has retry
          responsibility.

          The local FP node is automatically in the SOC of the local FP.
          However, if the local FP is a nested FP, the local node is in the SOC
          of the higher FP node insofar as the local FP is concerned; local EP
          applications remain in the SOC of the local FP.


ΓòÉΓòÉΓòÉ 8.4. DEFINE_EXPLICIT_SOC ΓòÉΓòÉΓòÉ

DEFINE_EXPLICIT_SOC

This verb defines an explicit sphere of control (SOC) for a specified MS
category, or adds nodes to the explicit SOC. You use the DEFINE_EXPLICIT_SOC
verb to enable the local APPN network node (NN) to be the explicit primary
focal point (FP) for the MS category. The SOC nodes are explicitly specified on
this verb, and only those nodes are added to the explicit SOC. An explicit SOC
represents a ranking for the FP. You can also specify an explicit backup FP
node for the MS category, where the backup FP node is not the local NN. The new
definition takes effect immediately. The local control point (CP) begins
establishing the FP-EP relationship with the SOC nodes either when this verb
completes, or when an FP application that manages the MS category registers
itself locally, whichever occurs last.

This verb should not be used to define the local node as a backup FP.

You can remove a DEFINE_EXPLICIT_SOC definition with the DELETE_EXPLICIT_SOC
verb.

See DEFINE_EXPLICIT_SOC Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_EXPLICIT_SOCΓöÇΓöÇkeynameΓöÇΓöÇms_categorynameΓöÇΓöÇbackup_fp_indicatorΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇKEEPΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇnumber_of_soc_nodesnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇREPLACEΓöÇΓöÇbackup_fp_fq_cp_namenameΓöÇΓöÿ

          Specify for each number_of_soc_nodes:

                    >ΓöÇΓöÇsoc_node_cp_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          ms_category
                    The name of the MS category for the SOC. Specify either a
                    4-byte SNA-defined name or a 1- to 8-byte Type A EBCDIC
                    name, left justified and filled on the right with EBCDIC
                    space (X'40') characters.

          backup_fp_indicator
                    The indicator of whether the explicit SOC nodes are to have
                    a backup FP:

             KEEP
                       Indicates the SOC nodes are to keep their current backup
                       FP, if any.

             REPLACE
                       Indicates the SOC nodes are to replace their current
                       backup FP, if any, with the one specified on the
                       backup_fp_fq_cp_name parameter.

                backup_fp_fq_cp_name
                          The CP name of the node at which the backup FP is
                          located. The name must be network qualified, left
                          justified, and filled on the right with EBCDIC space
                          (X'40') characters. If the backup FP is located at a
                          type 5 host system that supports receipt of MDS-MUs,
                          this parameter specifies the LU name for the FP.

                          This parameter is meaningful only if the
                          backup_fp_indicator parameter specifies REPLACE;
                          otherwise, this parameter is ignored. You may set
                          this parameter to a null value (all binary zeros) to
                          indicate the EPs are to have no backup FP.

          number_of_soc_nodes
                    The number of SOC node CP names following this parameter.
                    The number must be greater than or equal to 1.

          soc_node_cp_name
                    The CP names of the explicit SOC nodes. Each name must be
                    network qualified, left justified, and filled on the right
                    with EBCDIC space (X'40') characters. The number of names
                    must be equal to the value on the number_of_soc_nodes
                    parameter.

 Return Codes

          The OK return code indicates that the DEFINE_EXPLICIT_SOC verb ran
          successfully.

          DEFINE_EXPLICIT_SOC Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_EXPLICIT_SOC verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_EXPLICIT_SOC Primary and Secondary Return Codes                 Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé EXPLICIT_SOC_DISALLOWED_ON_EN  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_EXPLICIT_BACKUP_FP_INDIΓöéANumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_EXPLICIT_BACKUP_FP_CP_NΓöéMNumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_NUMBER_OF_SOC_NODES   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_SOC_NODE_CP_NAME    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé SOC_NODE_CP_NAME_IS_LOCAL_CP  Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_EXPLICIT_SOC verb is used to define a SOC based on
          explicit specification of the SOC nodes. The SOC nodes may be either
          NNs or ENs.

          The definition of an SOC and the registration of a FP application
          must both occur on the same NN before the NN can establish an FP-EP
          relationship with the EP nodes in the SOC; an FP-EP relationship is
          established by exchanging MS capabilities messages between the FP and
          EP nodes.

          If an FP application is already registered for the MS category when
          the DEFINE_EXPLICIT_SOC verb is issued, the local node establishes an
          FP-EP relationship with each node specified on the verb. Conversely,
          if an FP application is not registered for the MS category when the
          DEFINE_EXPLICIT_SOC verb is issued, the local node waits until the FP
          application is registered before it establishes an FP-EP relationship
          with the specified nodes.

          An EP node maintains a ranking of FP nodes that establish an FP-EP
          relationship with the EP node. When an EP node has an active FP-EP
          relationship, that FP can can be replaced by another FP of equal or
          higher rank. Each time an FP is replaced by another FP, a new FP-EP
          relationship is established. The ranking is as follows, listed in
          order from highest to lowest rank:

          Primary         A primary FP can be either explicitly or implicitly
                          defined for NNs and ENs.
          Backup          A backup FP can be either explicitly or implicitly
                          defined for NNs and ENs.
          Default Primary Only NNs can have a default primary FP.
          Default Backup  Only NNs can have a default backup FP.
          Domain          Only ENs can have a domain FP.
          Host            Only subarea-adjacent NNs or ENs can have a host FP.

          If a specified SOC (EP) node is unavailable such that the FP-EP
          relationship is not established, the local node tries to establish
          it, as updates to the topology database occur, and at periodic
          intervals when the SOC node type (NN or EN) is not known to the local
          FP node.

          When the FP-EP relationship is established, the EP node is given
          retry responsibility should the FP-EP relationship be broken.

          The local FP node is not allowed to be defined in its own explicit
          SOC; it is automatically in the SOC of the local FP. However, if the
          local FP is a nested FP, the local node is in the SOC of the higher
          FP node insofar as the local FP is concerned; local EP applications
          remain in the SOC of the local FP.


ΓòÉΓòÉΓòÉ 8.5. DEFINE_GATEWAY_HOST ΓòÉΓòÉΓòÉ

DEFINE_GATEWAY_HOST

This verb defines all pool classes for the host with link name host_link_name.

See DEFINE_GATEWAY_HOST Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                                                  ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                                              Γöé
                    >>ΓöÇΓöÇDEFINE_GATEWAY_HOSTΓöÇΓöÇkeyΓöÇΓöÇnameΓöÇΓöÇhost_link_nameΓöÇΓöÇnameΓöÇΓöÇΓöÇΓöÇlu_poolΓöÇΓöÇΓöñ Definition Γö£ΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ@ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇdescriptionΓöÇΓöÇtextΓöÇΓöÿ
                    DEFINITION:
                              ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                            Γöé
                    Γö£ΓöÇΓöÇpool_nameΓöÇΓöÇnameΓöÇΓöÇΓöÇΓöÇnau_rangeΓöÇΓöÇbegin_and_endΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                             ΓööΓöÇauto_logoff_timerΓöÇΓöÇnumber_of_minutesΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          host_link_name
                    The name of the host link, specified in a
                    DEFINE_LOGICAL_LINK command. This is a type A EBCDIC
                    character string. If the name is less than 8 bytes, it must
                    be padded on the right with EBCDIC blanks.

          lu_pool
                    The name, NAU ranges, and auto-logoff specification for
                    this pool.

             pool_name
                       The name of the pool to be defined. The name can be 1-8
                       characters long, and include any printable ASCII
                       character. Each pool name must be different from other
                       pool names on the same host, but two different hosts can
                       have a pool with the same name. The case of the
                       alphabetic characters is significant, so that "Pool1" is
                       a different name from "POOL1".

             nau_range
                       The beginning and ending of a range of NAU addresses to
                       be included in this pool.  The range value can be from 1
                       to 254. If there is only one address in the range, it
                       must be specified as both the beginning and ending
                       value. There can be up to 254 NAU ranges specified for a
                       pool.

             auto_logoff_timer
                       The number of minutes that a member of this pool can be
                       inactive before it is logged off.  The value can range
                       from 0 to 999, 0 indicating that members of this pool
                       will never be logged off due to inactivity. If this
                       field is omitted, the specified default value of 0 is
                       specified.

          description
                    A description of this pool.  The string is free format and
                    can be up to 64 characters long.

 Return Codes

          The OK return code indicates that the DEFINE_GATEWAY_HOST verb ran
          successfully.

          DEFINE_GATEWAY_HOST Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_GATEWAY_HOST verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_GATEWAY_HOST Primary and Secondary Return Codes                 Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEF_GW_BAD_HOST_LINKNAME    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_DUP_HSNAU        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_INV_NAME         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_INV_LCL_HOST_ADR     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_HOST_INV_TIMER      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.6. DEFINE_GATEWAY_WORKSTATION ΓòÉΓòÉΓòÉ

DEFINE_GATEWAY_WORKSTATION

This verb defines which combination of LUs will be given to a workstation when
it establishes a link to this gateway.

See DEFINE_GATEWAY_WORKSTATION Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                                                           ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                                                   Γöé
                    >>ΓöÇΓöÇDEFINE_GATEWAY_WORKSTATIONΓöÇΓöÇkeyΓöÇΓöÇnameΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöñ Definition Γö£ΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                          Γö£ΓöÇworkstation_link_nameΓöÇΓöÇnameΓöÇΓöñ
                                          ΓööΓöÇdlc_nameΓöÇΓöÇnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ@ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇdescriptionΓöÇΓöÇtextΓöÇΓöÿ
                    DEFINITION:
                    Γö£ΓöÇΓöÇworkstation_luΓöÇΓöÇΓöñ Specification Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    SPECIFICATION:
                    Γö£ΓöÇΓöÇworkstation_lu_nameΓöÇΓöÇnameΓöÇΓöÇhost_link_nameΓöÇΓöÇnameΓöÇΓöÇnau_address_at_workstationΓöÇΓöÇnumberΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇnau_address_at_hostΓöÇΓöÇnumberΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      ΓööΓöÇpool_nameΓöÇΓöÇnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          workstation_link_name
                    The name of the link to the workstation, specified in a
                    DEFINE_LOGICAL_LINK command. This is a Type A EBCDIC
                    character sting.  If the name is less than 8 bytes, it must
                    be padded on the right with EBCDIC blanks. This field is
                    required unless the verb is being used to specify an
                    implicit workstation definition.

          dlc_name
                    This field is only used when defining an implicit
                    workstation definition. It specifies the DLC that this
                    definition will be used for.  This allows the gateway to
                    give one set of LUs to a workstation that creates an
                    implicit link over one protocol, and a different set of LUs
                    for workstations that create implicit links over a
                    different protocol. If both this field and the
                    workstation_link_name are omitted, then the verb defines an
                    implicit workstation definition for all DLCs that do not
                    have an implicit definition defined.

                    The following differences exist when configuring an
                    implicit workstation.

              1. workstation_lu_name is not required and will be ignored.

              2. All workstation_lu definitions must use pool_name rather than
                 nau_address_at_host.

                    The following DLC names are supported:

             SDLC           SDLC
             IDLC           IDLC
             IBMTRNET       IBM Token-Ring Network
             ETHERAND       ETHERAND Network
             IBMPCNET       IBM PC Network
             X25DLC         X.25

          workstation_lu
                    The specification of a logical session between the
                    workstation and a host.

             workstation_lu_name
                       The name of the logical session. This is a Type A EBCDIC
                       character string. If the name is less than 8 bytes, it
                       must be padded on the right with EBCDIC blanks. Each LU
                       name must be different from all other LU names in the
                       configuration.

             host_link_name
                       The name of the host for this session, specified in a
                       DEFINE_LOGICAL_LINK command. This is a Type A EBCDIC
                       character string.  If the name is less than 8 bytes, it
                       must be padded on the right with EBCDIC blanks.

             nau_address_at_workstation
                       The NAU address which the workstation will be using for
                       this session.  The number value can be from 1 to 254,
                       inclusive.

             nau_address_at_host
                       The NAU address which the host will be using for this
                       session. If this field is specified, this will be a
                       dedicated session, and only this workstation will be
                       allowed to use this host NAU address. The number value
                       can be from 1 to 254, inclusive.

             pool_name
                       The name of the host pool class from which the host NAU
                       address will be allocated. The name can be 1-8
                       characters long, and included any printable ASCII
                       character.  If this field is specified, this will be a
                       pooled session, and the NAU address will be shared with
                       other workstation LUs.

          description
                    A description of this workstation configuration. The string
                    is free format and can be up to 64 characters long.

 Return Codes

          The OK return code indicates that the DEFINE_GATEWAY_WORKSTATION verb
          ran successfully.

          DEFINE_GATEWAY_WORKSTATION Primary and Secondary Return Codes shows
          the primary and secondary error return codes associated with the
          DEFINE_GATEWAY_WORKSTATION

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_GATEWAY_WORKSTATION Primary and Secondary Return Codes              Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEF_GW_BAD_HOST_LINKNAME    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_BAD_WKS_LINKNAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_DUP_HSNAU        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_INV_NAME         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_INV_LCL_HOST_ADR     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_WKS_DUP_WSNAU      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_WKS_DUP_LUNAME      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_GW_WKS_INV_POOL_CLASS    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.7. DEFINE_LOCAL_LU ΓòÉΓòÉΓòÉ

DEFINE_LOCAL_LU

This verb defines a new local logical unit (LU) type 6.2 or replaces an an
existing one. If a local LU name is already defined, the definition is
replaced; otherwise, the new definition is added. The definition becomes active
when the local LU is used. This verb allows you to establish sessions with any
other local LU within the same network.

You can remove an independent local LU definition with the DELETE_LOCAL_LU
verb.

See DEFINE_LOCAL_LU Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_LOCAL_LUΓöÇΓöÇkeynameΓöÇΓöÇlu_namenameΓöÇΓöÇlu_aliasnameΓöÇΓöÇnau_addressnΓöÇΓöÇhost_link_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_name
                    The 8-byte EBCDIC network name of the local LU. This is the
                    name of the LU as it is known throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

                    Note:  We recommend that you avoid using the three special
                    characters  $, #, and @.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

                    Alternatively, you can select the default local LU by
                    specifying 8 bytes of binary zeros.

                    Note:  This parameter is case sensitive. Ensure that this
                    field is defined with the correct uppercase and lowercase
                    characters.

          nau_address
                    Specifies the network addressable unit (NAU) address of the
                    LU.

                    You can specify a value in the range of 0-254, where:

             0         Specifies that the NAU address is not used, and the LU
                       is an independent LU. Sessions among APPN end nodes and
                       network nodes must use independent LUs. An LU type 6.2
                       is the only type of SNA LU that supports independent
                       sessions. An independent session does not depend on an
                       SSCP (that is, the LU can send a BIND directly without
                       the help of an SSCP).
             1-254     Specifies the NAU address of the LU, and that the LU is
                       a dependent LU for sessions to a subarea node. If your
                       network contains a subarea that does not support an
                       independent session from a peripheral node, you will be
                       restricted to a single dependent session between your
                       APPC LU and that subarea. In this case, the LU will need
                       to be assigned a unique NAU address.

                       An LUs NAU address is the address used by a subarea node
                       for an LUs dependent session. A dependent session is a
                       session that depends on an SSCP to initiate it (that is,
                       an optional INIT_SELF request flows on the LU to SSCP
                       session, the SSCP sends a CINIT request to a subarea LU,
                       and the subarea LU sends the BIND).

                       On a given link, every LU that uses a dependent session
                       must be assigned a unique NAU address. Every LU defined
                       for an LUA session, every LU defined for a 3270 session,
                       and every LU defined for a 3270 gateway session uses a
                       dependent session and must be assigned a unique NAU
                       address.

          host_link_name
                    The 8-byte EBCDIC name of the local link station.  This
                    logical link can be activated by specifying this name on
                    the ACTIVATE_LOGICAL_LINKS verb.

                    Note:  The host link name is ignored if nau_address equals
                    0 is specified.  Otherwise, this parameter is optional. If
                    a nau address is specified, the LU definition is assigned
                    to the CP-PU.

                    This is a Type A EBCDIC character string.  If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCIDIC blanks.  In addition, the string cannot begin with
                    an EBCIDIC "@" (X'7C').

 Return Codes

          The OK return code indicates that the DEFINE_LOCAL_LU verb ran
          successfully:

          DEFINE_LOCAL_LU Primary and Secondary Return Codes shows the primary
          and secondary error return codes associated with the DEFINE_LOCAL_LU
          verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_LOCAL_LU Primary and Secondary Return Codes                   Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LU_NAME         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LU_NAU_ADDRESS     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEL_LOCAL_DEPENDENT_LU     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DUPLICATE_LU_ALIAS       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LOCAL_LU_NAME_EQ_PLU_NAME    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LU_NAME_SAME_AS_CP_NAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LU_NAU_ADDRESS_ALREADY_DEFD   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé HOST_LINK_NAME_NOT_DEFINED   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.8. DEFINE_LOGICAL_LINK ΓòÉΓòÉΓòÉ

DEFINE_LOGICAL_LINK

The DEFINE_LOGICAL_LINK verb defines the characteristics of a link to an
adjacent network node, end node, or low-entry networking (LEN) node. The verb
is used to add a new definition or replace an existing one. If the link is
already defined, the definition is replaced; otherwise, the new definition is
added. The link name is unique in this node and is used in conjunction with the
destination address to determine whether the link is already defined. An
existing link name can be associated with a new destination address if the link
is inactive. The definition becomes active when the link goes from the inactive
state to the active state.

Note:  A logical link definition cannot be deleted.

          See DEFINE_LOGICAL_LINK Verb Control Block for information on the
          verb control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_LOGICAL_LINKΓöÇΓöÇkeynameΓöÇΓöÇlink_namenameΓöÇΓöÇfq_adjacent_cp_namenameΓöÇΓöÇadjacent_node_typeΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇLEARNΓöÇΓö¼ΓöÇΓöÇdlc_namenameΓöÇΓöÇuse_puname_as_cpnameΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇmaximum_activation_attemptsΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      Γö£ΓöÇLENΓöÇΓöÇΓöÇΓöñ                    ΓööΓöÇNOΓöÇΓöÇΓöÿ
                      ΓööΓöÇNNΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇNO_LIMITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇnode_id_sentidΓöÇΓöÇadapter_numbernΓöÇΓöÇdestination_address_lengthnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ
                    >ΓöÇΓöÇdestination_addressaddressΓöÇΓöÇx25_dir_entrynameΓöÇΓöÇpref_nn_serverΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                     ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇcp_cp_session_supportΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇactivate_at_startupΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇlimited_resourceΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                 ΓööΓöÇNOΓöÇΓöÇΓöÿ            ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇlink_station_roleΓöÇΓöÇΓö¼ΓöÇPRIMARYΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      Γö£ΓöÇNOΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ           Γö£ΓöÇSECONDARYΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ           Γö£ΓöÇNEGOTIABLEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                             ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ
                    >ΓöÇΓöÇeffective_capacityΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇcost_per_connect_lineΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇcost_per_byteΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ         ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ

  >>ΓöÇΓöÇsecurityΓöÇΓöÇΓö¼ΓöÇNONSECUREΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇpropagation_delayΓöÇΓöÇΓö¼ΓöÇMINIMUMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
         Γö£ΓöÇPUBLIC_SWITCHED_NETWORKΓöÇΓöñ           Γö£ΓöÇLANΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
         Γö£ΓöÇUNDERGROUND_CABLEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ           Γö£ΓöÇTELEPHONEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
         Γö£ΓöÇSECURE_CONDUITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ           Γö£ΓöÇPKT_SWITCHED_NETΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
         Γö£ΓöÇGUARDED_CONDUITΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ           Γö£ΓöÇSATELLITEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
         Γö£ΓöÇENCRYPTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ           Γö£ΓöÇMAXIMUMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
         Γö£ΓöÇGUARDED_RADIATIONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ           ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ
         ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÇΓöÿ
  >ΓöÇΓöÇuser_defined_1ΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇuser_defined_2ΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
            ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ          ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ
  >ΓöÇΓöÇuser_defined_3ΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇpu_namenameΓöÇΓöÇadj_cp_node_ididΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
            ΓööΓöÇUSE_ADAPTER_DEFINITIONΓöÇΓöÿ
  >ΓöÇΓöÇsolicit_sscp_sessionΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇoutgoing_call_directory_entry_namenameΓöÇΓöÇinit_selfΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
               ΓööΓöÇNOΓöÇΓöÇΓöÿ                           ΓööΓöÇNOΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          link_name
                    The 8-byte EBCDIC name of the local logical link station.
                    This logical link can be activated by specifying this name
                    on the ACTIVATE_LOGICAL_LINKS verb.

                    This a type A EBCDIC character string. If the name is less
                    than 8 bytes, it must be padded on the right with EBCDIC
                    blanks. In addition, the string cannot begin with an EBCDIC
                    "@" (X'7C').

          fq_adjacent_cp_name
                    Specifies the fully qualified name for the control point
                    (CP) in the adjacent node. This name is a 17-byte EBCDIC
                    name consisting of two 8-byte Type A EBCDIC character
                    strings concatenated by an EBCDIC period.

                    There are several reasons to use this parameter:

             o When the partner LU is located in a low entry networking (LEN)
               node

             o When the adjacent node does not include its CP name on the XIDs
               it exchanges

             o When using a link defined as activate_at_startup(NO), specifying
               a fq_adjacent_cp_name, and using a DEFINE_PARTNER_LU_LOCATION
               verb to tell APPC which link to activate to reach the partner LU
               being defined. APPC matches this parameter and the
               fq_owning_cp_name on the DEFINE_PARTNER_LU_LOCATION verb to
               determine which link to activate.

                    Otherwise, this parameter can be omitted. To omit this
                    parameter, specify all EBCDIC blank (X'40') characters. If
                    this parameter is omitted, the CP name of the adjacent node
                    will be obtained from its XID.

                    If you specify this parameter and the adjacent node (other
                    than a LEN node) sends its fully qualified CP name on an
                    XID exchange, the two names must be the same. All NNs and
                    ENs include their CP name, but some low-entry networking
                    (LEN) nodes do not.

                    If the adjacent node's CP name does not contain a network
                    ID, insert your local network ID in the first portion of
                    this parameter.

          adjacent_node_type
                    Specifies the APPN node type of the adjacent node. You must
                    specify one of the following values:

             LEARN
                       Specifies that the adjacent node type (EN, NN, or LEN)
                       is not known, and is to be learned when a link to the
                       adjacent node is established.

                       If your local node is a NN and you are defining a link
                       to another NN, ensure that the NETIDs of both nodes are
                       identical. Communications Manager cannot activate a link
                       to another network node if the link is defined as
                       adjacent_node_type(LEARN) and the remote node has a
                       different SNA network ID (NETID).

             LEN
                       Specifies that the adjacent node is treated as a low
                       entry networking (LEN) node. You should specify
                       cp_cp_session_support(NO) when using this parameter.

                       With an adjacent_node_type(LEN), CP name checking will
                       be bypassed and you can use any CP name value to make
                       the association between the DEFINE_PARTNER_LU_LOCATION
                       and the DEFINE_LOGICAL_LINK verbs.

                       This is the only value that will allow establishing a
                       link between two network nodes that have different
                       NETIDs. CP-CP sessions are not possible between two APPN
                       network nodes that have different NETIDs.

             NN
                       Specifies that the adjacent node is an APPN network node
                       and can be used as an NN server if the preferred server
                       is unavailable.

                       If your local node is a NN and you are defining a link
                       to another NN, ensure that the NETIDs of both nodes are
                       identical. Communications Manager cannot activate a link
                       to another network node if the link is defined as
                       adjacent_node_type(NN) and the remote node has a
                       different SNA network ID (NETID).

          dlc_name
                    The 8-byte ASCII name of the local data link control (DLC).
                    This is the name used to configure a DLC in the
                    Communications Manager DLC profile. The valid names are:

             o 'ETHERAND'
             o 'IBMPCNET'
             o 'IBMTRNET'
             o 'SDLC   '
             o 'TWINAX  '
             o 'X25DLC  '
             o 'IDLC   '

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

          use_puname_as_cpname
                    Transmit the PU name in the CP name field on an XID3
                    exchange.

          max_activation_attempts
                    Specifies the default value for the maximum number of
                    activation attempts per link.  A value of 0 indicates that
                    there is no limit.

                    An ACTIVATE_LINK command always attempts to activate the
                    link even if the number of activation attempts has been
                    reached.

          node_id_sent
                    Indicates the 8-digit hexadecimal Node Identification field
                    of the XID frame that will be sent to the adjacent node.

          adapter_number
                    Specifies the adapter used for this link station to
                    communicate with the adjacent node. This must be the same
                    number as that configured for an adapter.

                    You can specify a maximum value of 255.

          destination_address_length
                    Specifies the length, in bytes, of the destination address.
                    You can specify a maximum value of 16. The value varies
                    depending on the type of DLC. For example:

             o For SDLC, X.25, and Twinax, this parameter must be set to 0.

             o For local area networks, this is the MAC address of the adapter
               in the adjacent node.

          destination_address
                    Specifies the destination address to be used by the local
                    node to address the link station on the adjacent node.

                    If your program specifies a destination_address_length of
                    6, APPC uses the default destination service access point
                    (SAP) value of X'04'. Otherwise, if your program specifies
                    a destination_address_length of 7, include the destination
                    SAP at the end of the destination_address.

          x25_dir_entry
                    Specifies an X.25 directory entry configured in your
                    Communications Manager X.25 directory profile. This
                    parameter is required if you are changing the link
                    definition between two X.25 adapters. This parameter is
                    ignored if the dlc_name is not X25DLC.

          preferred_nn_server
                    Specifies that this is the link to the APPN network node
                    that you would prefer to have as your NN server.

             YES
                       Specifies that the adjacent node is to be your NN
                       server. If you have specified activate_at_startup(YES),
                       Communications Manager attempts to activate this link
                       before other defined links in your node definition.

                       You must specify cp_cp_session_support(YES),
                       adjacent_node_type(LEARN or NN), and be defined as an
                       APPN end node on the DEFINE_LOCAL_CP command.

             NO
                       If the link to the preferred NN is unable to be
                       activated, this link may still serve as the link to the
                       NN server for your node.

          cp_cp_session_support
                    Specifies whether the link is to support CP-CP sessions.
                    You must specify one of the following values:

             YES
                       Specifies that CP-CP sessions are supported on this
                       link. CP-CP sessions are activated on this link only
                       when the adjacent node supports CP-CP sessions, and:

                o The adjacent node is an NN, or

                o The local node is an EN and does not have a NN server when
                  this link is activated.

             NO
                       Specifies that CP-CP sessions are not supported on this
                       link. This is useful for APPN network nodes to define a
                       link over which it will support intermediate sessions
                       but not directory searches.

          activate_at_startup
                    Specifies whether the link is to be automatically activated
                    when a subsequent ACTIVATE_LOGICAL_LINKS verb is issued.
                    See the description of the number_of_links parameter on
                    topic ACTIVATE_LOGICAL_LINKS for more information.

                    You must specify one of the following values:

             YES
                       Specifies that APPC should attempt to activate this link
                       when Communications Manager is started or when an
                       ACTIVATE_LOGICAL_LINKS verb with
                       number_of_links(ACTIVATE_ALL) is specified.

             NO
                       Specifies that this link will only be activated:

                o When an ACTIVATE_LOGICAL_LINKS verb with
                  number_of_links(ACTIVATE_ONE) and with this link_name is
                  specified.

                o When specifying an fq_adjacent_cp_name and using a
                  DEFINE_PARTNER_LU_LOCATION verb to tell APPC which link to
                  activate to reach the partner LU being defined. APPC matches
                  this parameter and the fq_owning_cp_name on the
                  DEFINE_PARTNER_LU_LOCATION verb to determine which link to
                  activate.

                o When the link is activated by a remote machine.

          limited_resource
                    Specifies whether this link is to remain active when there
                    are no sessions using the link.

                    You must specify one of the following values:

             YES
                       Specifies that this link to the adjacent node is subject
                       to limited resource control, and will be brought down
                       when the link is no longer being used.

                       Note:  Once a link is activated, it must be used at
                       least once before limited resource control deactivates
                       the link.

             NO
                       Specifies that this link is to remain active, even if
                       the adapter was specified as a limited resource. This is
                       useful, for example, in the token-ring environment when
                       the user wants a link to a LAN server or host to remain
                       active but has defined the token-ring adapter as a
                       limited resource.

             USE_ADAPTER_DEFINITION
                       Specifies that the limited resource value defined for
                       the adapter is to be used. The adapter definition is set
                       to YES if Free unused link(Yes) was configured in the
                       Communications Manager Data Link Control (DLC) profile.

          link_station_role
                    Specifies the link station role to be used for this link.
                    You must specify one of the following values:

             PRIMARY
                       Specifies this link as the primary link station.

             SECONDARY
                       Specifies this link as the secondary link station.

             NEGOTIABLE
                       Specifies this link will negotiate its role during link
                       activation via XID exchange.

             USE_ADAPTER_DEFINITION
                       Specifies that the link station role defined for the
                       adapter is to be used.

          effective_capacity
                    Specifies the actual bit rate for this link. The effective
                    capacity is derived from the link bandwidth and maximum
                    load factor.

             USE_ADAPTER_DEFINITION
                       Specifies that the effective capacity associated with
                       the adapter is to be used.

          cost_per_connect_time
                    An integer value in the range of 0 to 255 that expresses
                    the relative cost of using this link. The units are user
                    defined. The cost per connect time values must be
                    proportional to applicable tariffs of the transmission
                    facility being used by the link and must reflect the
                    relative expense of the link as compared to all other links
                    in the network. A value of 0 means that connections using
                    this link are free.

                    Cost per connect time is network specific and is not
                    intended to be uniform across networks (except where two or
                    more networks coordinate assignment of relative cost values
                    among themselves).

          cost_per_byte
                    An integer value in the range 0 to 255 that expresses a
                    relative cost of transmitting a byte over this link. The
                    units are user defined. Cost per byte value should be
                    proportional to the actual cost of transmitting data over
                    the link. A value of 0 means that transmitting a byte of
                    data over the link is free.

                    Cost per byte is network specific and is not intended to be
                    uniform across networks (except where two or more networks
                    coordinate assignment of relative cost values among
                    themselves).

          security
                    Specifies the security value for this link. The following
                    list describes the valid values for this parameter in the
                    order of their effectiveness:

             NONSECURE
                       Specifies that no security exists, such as satellite
                       links or underground lines.

             PUBLIC_SWITCHED_NETWORK
                       Specifies that data transmitted over this adapter will
                       flow through a public switched network.

             UNDERGROUND_CABLE
                       Specifies transmission over a secure underground cable.

             SECURE_CONDUIT
                       Specifies that the line is secure conduit that is not
                       guarded, such as pressurized pipe.

             GUARDED_CONDUIT
                       Specifies that the conduit is protected against physical
                       tapping.

             ENCRYPTED
                       Specifies that the adapter or the system software that
                       controls the adapter encrypts the data transmitted over
                       the line.

             GUARDED_RADIATION
                       Specifies that the line is protected against physical
                       and radiation tapping.

             USE_ADAPTER_DEFINITION
                       Specifies that the security value defined for the
                       adapter is to be used.

          propagation_delay
                    Specifies the amount of time it takes for a byte to travel
                    through this logical link. Specify one of the following
                    values:

             MINIMUM
                       Specifies there is no propagation delay.

             LAN
                       Specifies a delay less than 480 microseconds.

             TELEPHONE
                       Specifies a delay between 480 microseconds and 49152
                       microseconds.

             PACKET_SWITCHED_NETWORK
                       Specifies a delay between 49152 microseconds and 245760
                       microseconds.

             SATELLITE
                       Specifies a delay over 245760 microseconds.

             MAXIMUM
                       Specifies the maximum delay allowed.

             USE_ADAPTER_DEFINITION
                       Specifies that the propagation delay defined for the
                       adapter is to be used.

          user_defined_1
                    Specifies the relative value for a network-unique
                    transmission group characteristic. You can specify a value
                    in the range of 0-255.

             USE_ADAPTER_DEFINITION
                       Specifies that the user_defined_1 value defined for the
                       adapter is to be used.

          user_defined_2
                    Specifies the relative value for a network-unique
                    transmission group characteristic. You can specify a value
                    in the range of 0-255.

             USE_ADAPTER_DEFINITION
                       Specifies that the user_defined_2 value defined for the
                       adapter is to be used.

          user_defined_3
                    Specifies the relative value for a network-unique
                    transmission group characteristic. You can specify a value
                    in the range of 0-255.

             USE_ADAPTER_DEFINITION
                       Specifies that the user_defined_3 value defined for the
                       adapter is to be used.

          pu_name
                    Indicates the 8-byte character identifier that corresponds
                    to a host system link used for dependent LU sessions.  This
                    allows multiple host systems to issue ACTPUs to the same
                    physical workstation.

          adj_cp_node_id
                    Indicates the 8-digit hexadecimal Node Identification field
                    which is expected to be in an XID frame received from the
                    adjacent node.

          solicit_sscp_session
                    Specifies whether your node requests sessions with the SSCP
                    over this link. Only one link in a node can solicit SSCP
                    sessions at a time. If this link is to a host focal point,
                    APPC sets this value to YES.

             YES
                       Requests a host to initiate sessions between the SSCP
                       and your PU (control point) and any dependent LUs in
                       your node.

             NO
                       No sessions with the SSCP are requested on this link.

          outgoing_call_directory_entry_name
                    Identifies the name of the outgoing call directory entry
                    being used for a particular call over a switched network.
                    The call directory entry contains an entry name (remote
                    party name), the network number associated with the remote
                    party, and other criteria which can be sent as part of the
                    outgoing call setup message to the switched network.

                    This parameter can contain an ASCII character string of up
                    to 15 characters long.

          init_self
                    Indicates whether or not this node is to be used as a
                    gateway to support workstations. Specify YES if this link
                    will be used by SNA Gateway and support INIT_SELF.  Specify
                    NO to reset the SNA Gateway or choose not to support
                    INIT_SELF.

 Return Codes

          The OK return code indicates that the DEFINE_LOGICAL_LINK verb ran
          successfully.

          DEFINE_LOGICAL_LINK Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_LOGICAL_LINK verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_LOGICAL_LINK Primary and Secondary Return Codes                 Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_OCDT_ENTRY_NAMEΓöé                 Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_PU_NAME     Γöé                 Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé BAD_PARMS_LEN          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_LINK_BAD_NODE_TYPE     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_LINK_INVALID_SECURITY    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_LINK_PU_FOCAL_PT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_AUTO_ACTIVATE      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_BYTE_COST        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_CP_CP_SUPPORT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_CP_NAME         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DEST_ADDR_LEN      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_EFFECTIVE_CAPACITY   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LIMITED_RESOURCE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LINK_NAME        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LS_ROLE         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_PREF_NN_SERVER     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_SOLICIT_SSCP      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_TIME_COST        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_USER_DEF_1       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_USER_DEF_2       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_USER_DEF_3       Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé ADAPTER_NOT_DEFD        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CHANGED_PU_WITH_DEPENDENT_LUs  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEST_ADDR_EQUALS_OWN_ADDR    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DLC_NOT_DEFD          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DUPLICATE_LINK_NAME       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LINK_IS_ACTIVE         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LOCAL_CP_NAME          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé NEW_LINK_NAME_EXISTING_DA    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé PU_PREVIOUSLY_DEFINED      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé X25_DIRENTRY_NOT_FOUND     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_LOGICAL_LINK verb is correlated for outbound links by
          using the following specifications:

          o link_name (if the ACTIVATE_LOGICAL_LINKS verb is used)
          o fq_adjacent_cp_name (information supplied by directory services
            when determining locations)

          For inbound links, correlation may be done by one of the following:

          o destination_address (if one is supplied from the LAN DLC)
          o fq_adjacent_cp_name (if one is supplied in the XID from the
            adjacent node)
          o adj_cp_node_id

          The DEFINE_LOGICAL_LINK verb is used to provide link definitions for
          the following reasons:

          o Define adjacent or serving network nodes. This allows the link to
            be established at startup time using the ACTIVATE_LOGICAL_LINKS
            verb.

          o Links for which the fq_adjacent_cp_name, or node_id should be
            verified during XID negotiation. If this value is specified and not
            the same as what is learned during XID negotiation, then the link
            activation will fail.

          o Links that have different characteristics than those specified by
            the adapter (link_station_role, cost, and so forth).


ΓòÉΓòÉΓòÉ 8.9. DEFINE_LUA ΓòÉΓòÉΓòÉ

DEFINE_LUA

This verb defines a new LUA logical unit (LU) type 0, 1, 2, 3 or replaces an
existing one. If an LU name is already defined, the NAU address or
host_link_name may be changed; otherwise, the new definition is added. The
definition becomes active when the local LU is used. This verb allows you to
establish sessions with any other local LU within the same network.

See DEFINE_LUA Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_LUAΓöÇΓöÇkeynameΓöÇΓöÇlu_namenameΓöÇΓöÇnau_addressnΓöÇΓöÇhost_link_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_name
                    The 8-byte ASCII network name of the LUA local LU. The name
                    is not sent outside the local node.

                    This is an 8-byte Type A ASCII character string. If the
                    name is less than 8 bytes, it must be padded on the right
                    with ASCII blanks.

                    Note:  We recommend that you avoid using the $, #, and @
                    special characters.

          nau_address
                    Specifies the network addressable unit (NAU) address of the
                    LU.

                    You can specify a value in the range of 1-254, where:

             1-254     Specifies the NAU address of the LU, and that the LU is
                       a dependent (secondary) LU for sessions to a subarea
                       node. If your network contains a subarea that does not
                       support an independent session from a peripheral node
                       (that is, it does not use the recent VTAM and NCP
                       releases), you will be restricted to a single dependent
                       session between your LU and that subarea.

                       An LUs NAU address is the address used by a subarea node
                       for an LUs dependent session. A dependent session is a
                       session that depends on an SSCP to initiate it (that is,
                       an optional INIT_SELF request flows on the LU to SSCP
                       session, the SSCP sends a CINIT request to a subarea LU,
                       and the subarea LU sends the BIND).

                       On a given link, every LU that uses a dependent session
                       must be assigned a unique NAU address. Every LU defined
                       for an LUA session, every LU defined for a 3270 session,
                       and every LU defined for a 3270 gateway session uses a
                       dependent session and must be assigned a unique NAU
                       address.

          host_link_name
                    Indicates the 8-byte EBCDIC name of the local logical link
                    station. This logical link can be activated by specifying
                    this name on the ACTIVATE_LOGICAL_LINKS verb.

                    This is a Type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.  In addition, the string cannot begin with
                    an EBCDIC "@" (X'7C').

 Return Codes

          The OK return code indicates that the DEFINE_LUA verb ran
          successfully.

          DEFINE_LUA Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the DEFINE_LUA verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_LUA Primary and Secondary Return Codes                      Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé BAD_LU_NAME           Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_NAU_ADDRESS       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé RESERVED_FIELD_NOT_ZERO     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé VERB_LENGTH_INVALID       Γöé                     Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DUPLICATE_LU_NAME        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé NON_UNIQUE_NAU_ADDRESS     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_LINK_NAME        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé NAU_REDEFINITION        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LINK_NAME_REDEFINITION     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LU_TYPE_REDEFINITION      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          Using host_link_name, make sure you create a unique NAU address
          between the 3270 SNA gateway and the LUA LU.


ΓòÉΓòÉΓòÉ 8.10. DEFINE_LU_LU_PASSWORD ΓòÉΓòÉΓòÉ

DEFINE_LU_LU_PASSWORD

This verb defines or replaces the password to be used for LU-LU sessions
between the specified local LU (including the local control point) and the
partner LU (including an adjacent control point). This verb is used to add a
new definition or replace an existing definition.

You can remove a DEFINE_LU_LU_PASSWORD with the DELETE_LU_LU_PASSWORD verb.

See DEFINE_LU_LU_PASSWORD Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_LU_LU_PASSWORDΓöÇΓöÇkeynameΓöÇΓöÇlu_aliasnameΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇpasswordstringΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

                    Alternatively, you can select the default local LU by
                    specifying 8 bytes of binary zeros.

                    Note:  This parameter is case sensitive. Ensure that this
                    field is defined with the correct uppercase and lowercase
                    characters.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

          password
                    Specifies the LU-LU password to be used for session-level
                    security verification between a local LU and the partner
                    LU. This is an 8-byte hexadecimal string. Any characters
                    are allowed.

 Return Codes

          The OK return code indicates that the DEFINE_LU_LU_PASSWORD verb ran
          successfully.

          DEFINE_LU_LU_PASSWORD Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_LU_LU_PASSWORD verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_LU_LU_PASSWORD Primary and Secondary Return Codes                Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_FQPLU_NAME       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé BAD_LU_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEF_LU_LU_PW_SESS_ACTIVE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERR   Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.11. DEFINE_MODE ΓòÉΓòÉΓòÉ

DEFINE_MODE

This verb defines the characteristics of a particular mode, including the class
of service to which it maps. You can use the DEFINE_MODE verb to add a new
definition or to replace an existing one. The definition becomes active when
the mode goes from the inactive state to the active state. An explicit CNOS
verb may be used to override some of the mode parameters when establishing a
session.

You can remove a DEFINE_MODE definition with the DELETE_MODE verb.

See DEFINE_MODE Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_MODEΓöÇΓöÇkeynameΓöÇΓöÇmode_namenameΓöÇΓöÇcos_namenameΓöÇΓöÇdefault_ru_sizeΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇNOΓöÇΓöÇmax_ru_size_upper_boundnΓöÇΓö¼ΓöÇΓöÇreceive_pacing_windownΓöÇΓöÇmax_negotiable_session_limitnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇYESΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇplu_mode_session_limitnΓöÇΓöÇcompression_needΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇPROHIBITEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇmin_cowinners_sourcenΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      Γö£ΓöÇSYSTEMΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                      Γöé       ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
                      Γöé                           Γöé Γöé
                      ΓööΓöÇREQUESTEDΓöÇΓöÇΓöÇΓö¼ΓöÇplu_slu_compression_levelΓöÇΓöÇΓö¼ΓöÇNONEΓöÇΓö¼ΓöÇΓö¼Γö┤ΓöÇΓöÿ
                             Γöé               Γö£ΓöÇRLEΓöÇΓöÇΓöñ Γöé
                             Γöé               ΓööΓöÇLZ9ΓöÇΓöÇΓöÿ Γöé
                             ΓööΓöÇslu_plu_compression_levelΓöÇΓöÇΓö¼ΓöÇNONEΓöÇΓö¼ΓöÇΓöÿ
                                           Γö£ΓöÇRLEΓöÇΓöÇΓöñ
                                           ΓööΓöÇLZ9ΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          mode_name
                    The 8-byte EBCDIC name for the mode. The mode name is used
                    to designate the network properties for a group of
                    sessions. This is the name of the mode as it is known
                    throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

          cos_name
                    The 8-byte EBCDIC name for the COS. This is the name of the
                    COS as it is known throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

          default_ru_size
                    Specifies whether a default lower and upper bound for the
                    maximum request/response unit (RU) size is to be used for
                    sessions having this mode name. You must specify one of the
                    following values:

             YES
                       Specifies that the lower bound on the maximum RU size
                       will be 256 and the upper bound on the maximum RU size
                       will be the largest RU that the link can handle without
                       causing segmentation. In this case, the
                       max_ru_size_upper_bound parameter is ignored.

             NO
                       Specifies that the value supplied in the
                       max_ru_size_upper_bound parameter is to be used for the
                       upper bound maximum RU size.

          max_ru_size_upper_bound
                    Specifies that the upper bound for the maximum size RU that
                    can be sent and received on the session. The actual value
                    for the maximum size RU, which is negotiated between the
                    local and partner LUs during session activation, will not
                    be greater than the value on this parameter. You can
                    specify a value in the range of 256-16384.

          receive_pacing_window
                    Specifies the session pacing window for the sessions. For
                    fixed session pacing, this value is used to determine the
                    receive pacing window for the sessions. For adaptive
                    session pacing, this value is used as the initial window
                    size for the first pacing request. You can specify a value
                    in the range of 0-63.

          max_negotiable_session_limit
                    Specifies the maximum session limit that a local LU can use
                    during its CNOS processing as the target LU for the mode
                    name.

                    You can specify a value in the range of 0-32767. The value
                    for this parameter must be 2 for the SNASVCMG mode.

          plu_mode_session_limit
                    Specifies the session limit that a local LU is to use
                    during its CNOS processing as the source LU for the mode
                    name. The value must be less than or equal to the
                    max_negotiable_session_limit.

                    You can specify a value in the range of 0-32767. It may be
                    2, 1, or 0 for the SNASVCMG mode.

          min_conwinners_source
                    Specifies the minimum number of contention winner sessions
                    that a local LU is to use during its CNOS processing as a
                    source LU for the mode name. If the CNOS verb specifies a
                    different value, the value in the CNOS verb takes
                    precedence.

                    You can specify a value in the range of 0-32767. It may be
                    1 for the SNASVCMG mode when the value for
                    max_negotiable_session_limit is 2 ; otherwise, it must be 0
                    for the SNASVCMG mode.

          COMPRESSION_NEED
                    Allows the user to specify one of the following parameters:

             PROHIBITED
                       This keyword prohibits compression in either direction
                       regardless of available system resources.
             SYSTEM
                       Communications Manager uses MAX_COMP_LEVEL from the
                       DEFINE_LOCAL_CP verb to check resource availability and
                       line speed for determining compression needs, regardless
                       of the directional compression level settings on
                       PLU_SLU_COMPRESSION and SLU_PLU_COMPRESSION.
             REQUESTED
                       This keyword causes Communication Manager to attempt the
                       compression level defined for PLU to SLU
                       (PLU_SLU_COMPRESSION) and SLU to PLU
                       (SLU_PLU_COMPRESSION) directions.  The maximum level of
                       compression will be used.

          PLU_SLU_COMPRESSION_LEVEL
                    Allows the user to specify the desired compression level
                    for PLU to SLU data.  The information in this field is
                    required. One of the following parameters must be
                    specified:

             NONE
                       This setting prohibits compression in the PLU to SLU
                       direction for this mode.  This is the default parameter
                       for PLU_SLU_COMPRESSION.
             RLE
                       This setting causes the maximum level of compression in
                       the PLU to SLU direction to be RLE.
             LZ9
                       This setting causes the maximum level of compression in
                       the PLU to SLU direction to be LZ9.

          SLU_PLU_COMPRESSION_LEVEL
                    Allows the user to specify the desired compression level
                    for SLU to PLU data.  The information in this field is
                    required. One of the following parameters must be
                    specified:

             NONE
                       This setting prohibits compression in the SLU to PLU
                       direction for this mode.  This is the default parameter
                       for SLU_PLU_COMPRESSION.
             RLE
                       This setting causes the maximum level of compression in
                       the SLU to PLU direction to be RLE.
             LZ9
                       This setting causes the maximum level of compression in
                       the SLU to PLU direction to be LZ9.

 Return Codes

          The OK return code indicates that the DEFINE_MODE verb ran
          successfully.

          DEFINE_MODE Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the DEFINE_MODE verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_MODE Primary and Secondary Return Codes                     Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé CPSVCMG_ALREADY_DEFD      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_CNOS_SLIM        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_COS_SNASVCMG_MODE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DEFAULT_RU_SIZE     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MAX_NEGOT_SESS_LIM   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MAX_RU_SIZE_UPPER    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MIN_CONWINNERS     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MODE_NAME        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MODE_SESSION_LIMIT   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_RECV_PACING_WINDOW   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_RU_SIZES        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_SNASVCMG_MODE_LIMITS  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé MODE_SESS_LIM_EXCEEDS_NEG    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_MODE_BAD_COMPRESSION_NEED  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DEF_MODE_BAD_DIR_COMPRESSION  Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé COS_NOT_DEFD          Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_MODE verb is used to provide additional mode definitions
          which are not supplied with Communications Manager. The following
          mode definitions are supplied with Communications Manager:

          o X'4040404040404040' (all EBCDIC blanks)
          o #BATCH
          o #BATCHC
          o #BATCHCS
          o #BATCHSC
          o #INTER
          o #INTERC
          o #INTERCS
          o #INTERSC
          o CPSVCMG
          o SNASVCMG

          The characteristics of these modes, except for CPSVCMG, can be
          changed using the DEFINE_MODE verb. The mode definition for CPSVCMG
          can neither be changed nor deleted.

          If session initiation is requested for a mode for which there is not
          a mode definition, there must be an default mode name defined for the
          node. In this case, the default mode parameters will be used. If
          there is not an default mode name specified, the session will fail to
          activate. A default mode name is configured using the DEFINE_DEFAULTS
          command in your node definitions file. For more information, see
          DEFINE_DEFAULTS.


ΓòÉΓòÉΓòÉ 8.12. DEFINE_PARTNER_LU ΓòÉΓòÉΓòÉ

DEFINE_PARTNER_LU

This verb defines the parameters of a partner LU for LU-LU sessions between any
local LU (including the local control point) and the partner LU (including an
adjacent control point). You can use the DEFINE_PARTNER_LU verb to add a new
definition or to replace an existing one. The new definition becomes active
when the partner LU goes from the inactive state to the active state.

This verb should not be used to define partner LUs located in the local node.

You can remove a DEFINE_PARTNER_LU definition with the DELETE_PARTNER_LU verb.

See DEFINE_PARTNER_LU Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_PARTNER_LUΓöÇΓöÇkeynameΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇpartner_lu_aliasnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇpartner_lu_uninterpreted_namenameΓöÇΓöÇparallel_session_supportΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇmax_mc_11_send_sizenΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                    ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇconv_security_verificationΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇnum_alt_aliasesnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                    ΓööΓöÇNOΓöÇΓöÇΓöÿ

          Specify for each num alt alias:

                    >>ΓöÇΓöÇalternate_partner_lu_alias.nameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

          partner_lu_alias
                    The locally known name for the partner LU.

                    This is an 8-byte ASCII character string. If the string is
                    less than 8 bytes, you must pad it on the right with ASCII
                    blanks.

                    Note:  This parameter is case sensitive. Ensure that this
                    field gets defined with the correct uppercase and lowercase
                    characters.

          partner_lu_uninterpreted_name
                    Specifies the uninterpreted name for the partner LU. This
                    is the name a local LU uses to initiate a session with the
                    partner LU in a subarea node when the local LU is defined
                    as a dependent LU for such sessions.

                    Note:  The local LU is a dependent LU when its network
                    addressable unit (NAU) address is a value other than 0. See
                    DEFINE_LOCAL_CP and DEFINE_LOCAL_LU for more details. The
                    local LU sends this name in the INIT_SELF request that it
                    sends to its SSCP (VTAM).

                    You can specify the same name as the network name of the
                    partner LU, or a different name. When specifying a
                    different name, or when the partner LU is located in
                    another network across an SNA gateway, this name must also
                    be defined in the interpret table at the local LUs SSCP.
                    Otherwise, when the name is the same as the network name
                    and the partner LU is in the same network as the SSCP, the
                    name need not be defined in the SSCP's interpret table.

                    You must specify all binary zeros when no uninterpreted
                    name is to be defined for the partner LU. The uninterpreted
                    name is not needed when the local LU is an independent LU
                    for its sessions with subarea LUs.

          parallel_session_support
                    Specifies whether the partner LU supports more than one
                    concurrent session to a local LU. You must specify one of
                    the following values:

             YES
                       Specifies that parallel sessions are supported when the
                       partner LU is an independent LU.

             NO
                       Specifies that parallel sessions are not supported.

          max_mc_ll_send_size
                    Specifies the maximum size of a logical record to be used
                    on a mapped conversation for sending data to the partner
                    LU. The size is the number of bytes in the logical record,
                    as indicated in the LL field of the record.

                    You should specify 0 when the largest size logical record
                    (32767 bytes) is to be used.

          conv_security_verification
                    Specifies the type of security information that a local LU
                    will accept on incoming attaches it receives from the
                    partner LU. You must specify one of the following values:

             YES
                       Specifies that an incoming attach may include a user ID
                       and the indication that the user ID has already been
                       verified.

             NO
                       Specifies that incoming attaches may include a user ID
                       together with a password, but not the already verified
                       indication.

          num_alt_aliases
                    Specifies the number of alternate partner LU aliases. The
                    value specified for this parameter determines how many
                    different aliases this partner LU can be known by. Specify
                    a value from 0 to 8. For values greater than 0, specify an
                    8-byte alternate partner LU alias for each.

             alternate_partner_lu_alias
                       Specify each alternate partner LU alias. Each alternate
                       partner LU alias is 8 bytes in length, padded on the
                       right with ASCII blanks.

 Return Codes

          The OK return code indicates that the DEFINE_PARTNER_LU verb ran
          successfully.

          DEFINE_PARTNER_LU Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_PARTNER_LU verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_PARTNER_LU Primary and Secondary Return Codes                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEF_PLU_INVALID_FQ_NAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_CONV_SECURITY_VERIF   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MAX_MC_LL_SEND_SIZE   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_PARALLEL_SESS_SUPP   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_UNINT_PLU_NAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DUPLICATE_PARTNER_LU_ALIAS   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé PLU_NAME_EQ_LOCAL_LU_NAME    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé UNINT_PLU_NAME_DEFD       Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_PARTNER_LU verb is used to provide partner LU definitions
          for the following reasons:

          o The implicit partner LU capability is disabled.
          o The implicit partner LU capability is enabled but the implicit
            parameter specifications do not apply to this partner LU.

          The parameter specifications for implicit partner LUs are:

          fq_partner_lu_name(FQ_LU_NAME from BIND)
          partner_lu_alias(@I00000n)
          partner_lu_uninterpreted_name(0)
          parallel_session_support(YES)
          max_mc_ll_send_size(value from the DEFINE_DEFAULTS verb)
          conv_security_verification(NO)


ΓòÉΓòÉΓòÉ 8.13. DEFINE_PARTNER_LU_LOCATION ΓòÉΓòÉΓòÉ

DEFINE_PARTNER_LU_LOCATION

This verb defines APPN directory information for a partner LU. Use the
DEFINE_PARTNER_LU_LOCATION verb to add a new definition or to replace an
existing one. The definition becomes active immediately.

There are several reasons to issue this verb:

          o When the partner LU is located in a low-entry networking (LEN)
            node.

          o When using a link defined as activate_at_startup(NO) and specifying
            a fq_adjacent_cp_name, use this verb to tell APPC which link to
            activate to reach the partner LU being defined. APPC uses the
            fq_owning_cp_name on this verb to determine which link to activate.

          o When the adjacent node does not include its control point (CP) name
            on the XID it sends.

          o When you want to predefine the location of an LU to your network
            node (for performance).

          You can remove a DEFINE_PARTNER_LU_LOCATION definition with the
          DELETE_PARTNER_LU_LOCATION verb.

          See DEFINE_PARTNER_LU_LOCATION Verb Control Block for information on
          the verb control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_PARTNER_LU_LOCATIONΓöÇΓöÇkeynameΓöÇΓöÇwildcard_entryΓöÇΓöÇΓö¼ΓöÇFULLΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                 Γö£ΓöÇPARTIALΓöÇΓöñ
                                                 ΓööΓöÇNOΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇfq_owning_cp_namenameΓöÇΓöÇlocal_node_nn_serverΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                            ΓööΓöÇNOΓöÇΓöÇfq_serving_nn_cp_namenameΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          wildcard_entry
                    Specifies whether this APPN directory entry is to be a
                    wildcard entry.

                    You must specify one of the following values:

             FULL
                       Specifies that this is a wildcard entry. The fully
                       qualified partner LU name is ignored and causes the node
                       to always return a "found" reply to a directory search.
                       This capability is used only when defining adjacent LEN
                       nodes.

             PARTIAL
                       Specifies that this is a partial wildcard entry. The
                       fully qualified partner LU name is specified as a
                       partial name on this entry and causes the node to return
                       a "found" reply to a directory search when the partial
                       name matches the first (left-hand) part of the LU name
                       being searched.

                       The partial LU name must not be defined on any other
                       node in the APPN network.

             NO
                       Specifies that this is not a wildcard entry. The partner
                       LU name must be specified.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

                    This parameter is ignored if wildcard_entry(FULL) was
                    specified.

                    If this is a partial wildcard entry, the partner LU name
                    will be a partial name, such as NET1.CICS. This NN will
                    reply to a directory search, for example, NET1.CICSV1R8,
                    with a "found" message indicating the LU is explicitly
                    defined on this node.

          fq_owning_cp_name
                    Specifies the fully qualified CP name of the node at which
                    the partner LU is located. This name must be specified, and
                    it cannot be the name of the local CP. This name should
                    match the fq_adjacent_cp_name parameter of the
                    corresponding DEFINE_LOGICAL_LINK verb if this is a partner
                    LU on a LEN-level link.

                    The location of an LU on the local node is defined when the
                    DEFINE_LOCAL_LU verb is issued.

          local_node_nn_server
                    Specifies whether the local node (which must be a network
                    node) serves as the NN server for the partner LU being
                    defined. You must specify one of the following values:

             YES
                       Specifies that the local node acts as a NN server to the
                       adjacent LEN node.

             NO
                       Specifies that the partner LU is served by the NN
                       specified in the fq_serving_nn_cp_name parameter. This
                    parameter applies only if the local node is an APPN NN.

          fq_serving_nn_cp_name
                    Specifies the fully qualified CP name of the NN serving the
                    EN or LEN node at which the partner LU is located. This
                    allows the APPN NN to search more efficiently through the
                    network, since it can direct search requests to other NNs
                    instead of doing a general broadcast.

 Return Codes

          The OK return code indicates that the DEFINE_PARTNER_LU_LOCATION verb
          ran successfully.

          DEFINE_PARTNER_LU_LOCATION Primary and Secondary Return Codes shows
          the primary and secondary error return codes associated with the
          DEFINE_PARTNER_LU_LOCATION verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_PARTNER_LU_LOCATION Primary and Secondary Return Codes              Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé BAD_LOCAL_NODE_NN_SERVER    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé CACHE_NOT_ALLOWED_EN      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_FQ_OWNING_CP_NAME    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_FQPLU_NAME       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_FQ_SERVING_NNCP_NAME  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_WILDCARD_ENTRY     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé FQ_OWNING_CP_NAME_EQ_LCL    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé FQPLU_NAME_EQ_LCL        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé FQ_SERVING_NNCP_NAME_EQ_LCL   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The following example shows a DEFINE_PARTNER_LU_LOCATION definition
          on a local APPN end node connected to a low-entry networking (LEN)
          node:

                    DEFINE_PARTNER_LU_LOCATION
                         wildcard entry(FULL)
                         fq_partner_lu_name(X'404040...')
                         fq_owning_cp_name(APPN.LEN1);

          If the EN plans to activate sessions to the LEN node, there must be a
          DEFINE_LOGICAL_LINK verb with fp_cp_name(APPN.LEN1). If the LEN node
          establishes the link first to the EN, the EN may omit the
          DEFINE_LOGICAL_LINK verb ONLY if the adjacent LEN nodes sends its
          fq_cp_name during XID negotiation (which is one of the features
          provided by APPC in OS/2).

          There are four reasons why you may need to use
          DEFINE_PARTNER_LU_LOCATION:

          o Preload an APPN NN directory database.

            You can use the DEFINE_PARTNER_LU_LOCATION verb to improve your
            network performance by preloading an APPN NN directory database,
            thereby reducing network broadcast searches. If an APPN EN linked
            to a NN server requests a session with a partner LU that is unknown
            to the server, the server sends a broadcast search to all of the
            NNs that it has CP-CP sessions with. In turn, other APPN NNs
            propagates this request throughout the network. If the result of
            the search is a positive reply, the requesting NN server caches the
            LU so that the next search request does not require a network
            broadcast. Preloading the directory saves having to broadcast each
            time you receive a request for a session with an unknown LU.

          o Communicate without the aid of an network node server.

            In an environment in which you do not have an NN server, you must
            define the location of the partner LUs you want to communicate
            with. Either your node or the node in which your partner LU resides
            must define and activate a link between the two nodes. The CP name
            defined on the DEFINE_PARTNER_LU_LOCATION verb must match the CP
            name of the node where your partner LU is defined.

          o Communicate to a partner LU on a node that does not have CP-CP
            sessions (for example, an LEN node).

            You must use DEFINE_PARTNER_LU_LOCATION if you will be
            communicating to LUs which are defined on LEN nodes.

          o Communicate to a partner LU that requires a route through a host
            system.

            If you are communicating to a partner LU that requires a route
            through a host system, you must define the partner LU to be at the
            host node. This applies for VTAM Version 3 Release 2 or later and
            NCP Version 4 Release 3 or later.


ΓòÉΓòÉΓòÉ 8.14. DEFINE_REMOTE_FP ΓòÉΓòÉΓòÉ

DEFINE_REMOTE_FP

This verb defines a remote focal point (FP) for the local entry point (EP)
node. You use the DEFINE_REMOTE_FP verb to enable the local APPN node (NN or
EN) to have a primary implicit FP for the MS category. The local EP node
becomes implicitly defined in the FP node's sphere of control (SOC). An
implicit SOC represents a ranking for the FP. See "Additional Information" for
more information about FP ranking. You can also specify up to 8 remote backup
FPs for the MS category. The new definition takes effect immediately. The local
control point (CP) establishes the FP-EP relationship with the remote FP node
when this verb completes.

This verb should not be used to define the local node as a FP.

You can remove a DEFINE_REMOTE_FP definition with the REVOKE_REMOTE_FP verb.

See DEFINE_REMOTE_FP Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_REMOTE_FPΓöÇΓöÇkeynameΓöÇΓöÇms_categorynameΓöÇΓöÇprimary_fp_fq_cp_namenameΓöÇΓöÇnumber_of_backup_fpsΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇnΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇ0ΓöÇΓöÿ

          Specify for each number_of_backup_fps:

                    >ΓöÇΓöÇΓö¼ΓöÇbackup_fp_fq_cp_namenameΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    The name of the master or service key configured with the
                    Communications Manager keylock feature.

          ms_category
                    The name of the MS category for the focal point. Specify
                    either a 4-byte SNA-defined name or a 1-8-byte type A
                    EBCDIC name, left justified and filled on the right with
                    EBCDIC space (X'40') characters.

          primary_fp_fq_cp_name
                    The network qualified CP name of the node at which the
                    primary FP is located. If the primary FP is located at a
                    type 5 host system that supports receipt of MDS-MUs, this
                    parameter indicates the LU name for the FP.

          number_of_backup_fps
                    The number of backup FP CP names following this parameter.

             0
                       No backup FPs are specified.

             n
                       The number of backup FPs specified. The number may be 0
                       to 8.

                backup_fp_fq_cp_name
                          The CP names of the backup FP nodes, with one entry
                          for each CP name. Each name must be network
                          qualified, left justified, and filled on the right
                          with EBCDIC space (X'40') characters. If any backup
                          FP is located at a type 5 host system that supports
                          receipt of MDS-MUs, this parameter indicates the LU
                          name for that FP.

                          The number of entries must be equal to the value on
                          the number_of_backup_fps parameter.

 Return Codes

          The OK return code indicates that the DEFINE_REMOTE_FP verb ran
          successfully.

          DEFINE_REMOTE_FP Primary and Secondary Return Codes shows the primary
          and secondary error return codes associated with the DEFINE_REMOTE_FP
          verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_REMOTE_FP Primary and Secondary Return Codes                   Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_REMOTE_PRIMARY_FP_CP_NAΓöéENumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé REMOTE_PRIMARY_FP_NAME_IS_LOCALΓöéCNumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_NUMBER_OF_REMOTE_BACKUPΓöéFNumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_REMOTE_BACKUP_FP_CP_NAMΓöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé REMOTE_BACKUP_FP_NAME_IS_LOCAL_ΓöéPNumeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_REMOTE_FP verb is used to define a remote FP for the local
          EP node, which may be a NN or EN.

          The local EP node establishes a FP-EP relationship that uses direct
          routing with the FP node.

          An EP node maintains a ranking of FP nodes that establish a FP-EP
          relationship with the EP node. When an EP node has an active FP-EP
          relationship, that FP can can be replaced by another FP of equal or
          higher rank. Each time a FP is replaced by another FP, a new FP-EP
          relationship is established. The ranking is as follows, listed in
          order from highest to lowest rank:

          Primary             A primary FP can be either explicitly or
                              implicitly defined for NNs and ENs.
          Backup              A backup FP can be either explicitly or
                              implicitly defined for NNs and ENs.
          Default Primary     Only NNs can have a default primary FP.
          Default Backup      Only NNs can have a default backup FP.
          Domain              Only ENs can have a domain FP.
          Host                Only subarea-adjacent NNs or ENs can have a host
                              FP.

          If the FP is, or becomes, unavailable such that the FP-EP
          relationship is broken or is not established, the local EP node tries
          to reestablish it. TGs become active in the topology database and as
          links to adjacent nodes become active, and at periodic intervals. The
          EP for a defined implicit FP always has retry responsibility.

          If the defined remote FP node is, in fact, not a FP node for the MS
          category, it rejects the EP's MS capabilities request. This event is
          logged in the FFST/2 error log, and the local EP node does not try to
          reestablish the FP-EP relationship. However, if backup FPs are
          specified, the EP node tries to acquire a backup FP.


ΓòÉΓòÉΓòÉ 8.15. DEFINE_TP ΓòÉΓòÉΓòÉ

DEFINE_TP

This verb defines transaction program (TP) information that the APPC attach
manager uses when processing incoming attaches from partner LUs. You can use
the DEFINE_TP verb to add a new definition or replace an existing one. If the
TP is already defined but is not currently active, the definition is replaced.
If the TP is already defined and it is currently active or being started, the
verb is rejected.

You can remove a DEFINE_TP definition with the DELETE_TP verb.

See DEFINE_TP Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_TPΓöÇΓöÇkeynameΓöÇΓöÇtp_namenameΓöÇΓöÇfilespecnameΓöÇΓöÇicon_filespecnameΓöÇΓöÇparm_stringstringΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇconversation_typeΓöÇΓöÇΓö¼ΓöÇBASICΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇpip_allowedΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇconv_security_rqdΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                               Γö£ΓöÇMAPPEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ        ΓööΓöÇNOΓöÇΓöÇΓöÿ           ΓööΓöÇNOΓöÇΓöÇΓöÿ
                               Γö£ΓöÇEITHERΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                               Γö£ΓöÇFDX_BASICΓöÇΓöÇΓöñ
                               Γö£ΓöÇFDX_MAPPEDΓöÇΓöñ
                               Γö£ΓöÇFDX_EITHERΓöÇΓöñ
                               ΓööΓöÇANY_TYPEΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇsync_levelΓöÇΓöÇΓö¼ΓöÇNONEΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇtp_operationΓöÇΓöÇΓö¼ΓöÇQUEUED_OPERATOR_STARTEDΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇprogram_typeΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                            Γö£ΓöÇCONFIRMΓöÇΓöñ         Γö£ΓöÇQUEUED_OPERATOR_PRELOADEDΓöÇΓöñ
                            ΓööΓöÇEITHERΓöÇΓöÇΓöÿ         Γö£ΓöÇQUEUED_AM_STARTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                         ΓööΓöÇNONQUEUED_AM_STARTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇBACKGROUNDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇqueue_depth_limitnΓöÇΓöÇincoming_allocate_timeoutΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      Γö£ΓöÇFULL_SCREENΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ                         ΓööΓöÇHOLD_FOREVERΓöÇΓöÿ
                      Γö£ΓöÇPRESENTATION_MANAGERΓöÇΓöñ
                      ΓööΓöÇVIO_WINDOWABLEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇreceive_allocate_timeoutΓöÇΓöÇΓö¼ΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                   ΓööΓöÇHOLD_FOREVERΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          tp_name
                    Specifies the name of the TP as specified on the incoming
                    attach. This name must match the tp_name sent by the
                    partner LU. If the partner LU is running the Communications
                    Manager, the tp_name was specified on either an APPC
                    program's [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb, or
                    a CPI Communications program's Allocate (CMALLC) call.

                    This is a 64-byte type AE name EBCDIC character string.

                    If the tp_name identifies a SNA service program, the first
                    character of the tp_name must be a hexadecimal digit
                    between X'00' and X'3F', excluding X'0E' and X'0F',
                    followed (optionally) by a 1- to 3-character EBCDIC string.

          filespec
                    The full name of an executable OS/2 program that starts the
                    TP. The filespec should include the drive, path, file name,
                    and extension. If you do not specify a file extension, the
                    default is .EXE. If you do not want a file extension, end
                    the file name with a period (.).

          icon_filespec
                    The name of an OS/2 icon file to be associated with this
                    OS/2 program when it is remotely started. The icon_filespec
                    should include the drive, path, file name, and extension.

          parm_string
                    The input parameters that are required by this OS/2 program
                    when it is remotely started.

          conversation_type
                    Specifies the type (basic or mapped) and style (half-duplex
                    or full-duplex) of conversations that will be used by the
                    TP. This parameter is verified upon receipt of an incoming
                    attach. You must specify one of the following values:

             BASIC
                       Specifies that only basic conversations will be used.

             MAPPED
                       Specifies that only mapped conversations will be used.

             EITHER
                       Specifies that this TP will support both types of
                       conversations.

             FDX_BASIC
                       Specifies that only basic conversation verbs for
                       full-duplex conversations will be used.

             FDX_MAPPED
                       Specifies that only mapped conversation verbs for
                       full-duplex conversations will be used.

             FDX_EITHER
                       Specifies that this TP will support either basic or
                       mapped conversation verbs for full-duplex conversations,
                       depending on what arrives on the incoming allocation
                       request.

             ANY_TYPE
                       Specifies that this TP will support either basic or
                       mapped conversation verbs and can support either
                       half-duplex or full-duplex conversations, depending on
                       what arrives on the incoming allocation request.

          pip_allowed
                    Specifies whether or not PIP data is allowed to be
                    received.

             YES
                       Informs the RECEIVE_ALLOCATE verb to allow PIP data to
                       flow on the next Receive and Wait (Fill-LL).

             NO
                       Informs the RECEIVE_ALLOCATE verb to reject the PIP data
                       as originally designed.

          conv_security_rqd
                    Specifies whether or not conversation security will be
                    required. You must specify one of the following values:

             YES
                       Specifies that the incoming attach must contain a valid
                       user ID and either a password or an already verified
                       indication.

             NO
                       Specifies that the incoming attach does not have to
                       contain security information.

          sync_level
                    Specifies the conversation sync level that the TP will use.
                    You must specify one of the following values:

             NONE
                       Specifies that the incoming attach must indicate
                       sync_level(NONE).

             CONFIRM
                       Specifies that the incoming attach must indicate
                       sync_level(CONFIRM).

             EITHER
                       Specifies that the TP will use the sync level specified
                       by the incoming attach.

          tp_operation
                    Specifies how this OS/2 program will be started.  If the
                    filespec specified on this verb is used in other TP
                    definitions on this workstation, all occurrences must be
                    defined with the same tp_operation. You must specify one of
                    the following values:

             QUEUED_OPERATOR_STARTED
                       Specifies that one version of the program will be run at
                       a time. If an incoming attach arrives and the program
                       has not been started yet, APPC will issue a message to
                       the operator to start the specified program. Subsequent
                       attaches that arrive while the program is active will be
                       queued.

             QUEUED_OPERATOR_PRELOADED
                       Specifies that one version of the program will be run at
                       a time. If an incoming attach arrives and the program
                       has not been started yet, the Attach will be rejected.
                       The APPC attach manager determines that a TP has started
                       upon reception of an APPC RECEIVE_ALLOCATE verb or a CPI
                       Communications program Accept_Conversation (CMACCP)
                       call. No message is sent to the operator. Subsequent
                       attaches that arrive while the program is active are
                       queued.

             QUEUED_AM_STARTED
                       Specifies that one version of the program will be run at
                       a time and will be started by the APPC attach manager.
                       Subsequent attaches that arrive while the program is
                       active will be queued.

             NONQUEUED_AM_STARTED
                       Specifies that multiple copies of the program will be
                       run at a time and will be started by the APPC attach
                       manager.

          program_type
                    Specifies the type of screen group that will be associated
                    with the OS/2 program being defined. You must specify one
                    of the following values:

             BACKGROUND
                       Specifies that the APPC attach manager starts the
                       program in a detached OS/2 background process. The
                       program runs in a null (nonselectable) display session,
                       so the program cannot write to the screen or read from
                       the keyboard. If your program is completely debugged and
                       requires no interactive user input, this option provides
                       the fastest performance.

             FULL_SCREEN
                       Specifies that this program will have a screen group,
                       but will not run under the OS/2 Presentation Manager
                       interface.

             PRESENTATION_MANAGER
                       Specifies that this program will have a screen group and
                       will run under the OS/2 Presentation Manager interface.

             VIO_WINDOWABLE
                       Specifies that this program will have a screen group and
                       will run under the OS/2 Presentation Manager interface
                       and is also required to make OS/2 VIO calls.

          queue_depth_limit
                    This value specifies the number of incoming attaches that
                    will be queued before being rejected. This parameter is
                    meaningful only with tp_operation(QUEUED_AM_STARTED),
                    tp_operation(QUEUED_OPERATOR_STARTED), or
                    tp_operation(QUEUED_OPERATOR_PRELOADED).

          incoming_allocate_timeout
                    This parameter specifies the number of seconds incoming
                    attaches will be queued waiting for an APPC program to
                    issue a RECEIVE_ALLOCATE verb or for a CPI Communications
                    program to issue an Accept_Conversation (CMACCP) call. This
                    parameter is meaningful only with
                    tp_operation(QUEUED_AM_STARTED),
                    tp_operation(QUEUED_OPERATOR_PRELOADED), or
                    tp_operation(QUEUED_OPERATOR_STARTED).

                    You can specify a maximum value of 32767, or you can
                    specify HOLD_FOREVER, which means that the incoming attach
                    will never time out.

          receive_allocate_timeout
                    This number specifies the number of seconds an APPC
                    program's RECEIVE_ALLOCATE verb or a CPI Communications
                    program's Accept_Conversation (CMACCP) call will wait for
                    an incoming attach to arrive.

                    You can specify a maximum value of 32767, or you can
                    specify HOLD_FOREVER, which means that the RECEIVE_ALLOCATE
                    verb or CMACCP call will never time out.

 Return Codes

          The OK return code indicates that the DEFINE_TP verb ran
          successfully.

          DEFINE_TP Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the DEFINE_TP verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_TP Primary and Secondary Return Codes                      Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_CONV_SECURITY_RQD    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_CONVERSATION_TYPE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_QUEUE_ALLOC_TIMEOUT   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_PROGRAM_TYPE      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_QUEUE_DEPTH       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_TP_RECEIVE_TIMEOUT   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_SYNC_LEVEL       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_SYNC_LEVEL_FOR_FDX   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_TP_NAME         Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_TP_OPERATION      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INCONSISTENT_TP_OPERATION    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé TP_ALREADY_ACTIVE        Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DEFINE_TP verb provides a definition for TPs for which defaults
          do not apply.


ΓòÉΓòÉΓòÉ 8.16. DEFINE_USER_ID_PASSWORD ΓòÉΓòÉΓòÉ

DEFINE_USER_ID_PASSWORD

This verb defines or replaces a user ID and passwords used for
conversation-level security. Incoming attaches requiring security verification
must contain a user ID and password. You can use the DEFINE_USER_ID_PASSWORD
verb to define a new user ID and password or to replace an existing password.

You can remove a DEFINE_USER_ID_PASSWORD definition with the
DELETE_USER_ID_PASSWORD verb.

See DEFINE_USER_ID_PASSWORD Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_USER_ID_PASSWORDΓöÇΓöÇkeynameΓöÇΓöÇuser_idnameΓöÇΓöÇpasswordnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          user_id
                    Specifies a valid user ID for incoming attaches. If not
                    specifying User Profile Management (UPM), this is a 10-byte
                    type AE name EBCDIC character string.

                    To use UPM to validate incoming attaches, the configuration
                    must contain at least a user ID of EBCDIC asterisk (X'5C').
                    To do this, specify an EBCDIC asterisk (X'5C') for the
                    user_id parameter and leave the password parameter blank
                    (it is ignored).

          password
                    Specifies a valid password for incoming attaches.

                    This is a 10-byte type AE name EBCDIC character string. If
                    an EBCDIC asterisk was specified for the user_id parameter,
                    indicating UPM, the password parameter value is ignored.

 Return Codes

          The OK return code indicates that the DEFINE_USER_ID_PASSWORD verb
          ran successfully.

          DEFINE_USER_ID_PASSWORD Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DEFINE_USER_ID_PASSWORD verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DEFINE_USER_ID_PASSWORD Primary and Secondary Return Codes               Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_PASSWORD        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_USER_ID         Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          On a workstation running TPs that can be remotely started by requests
          from another machine, you must determine which user IDs and passwords
          are valid for incoming attaches. If an incoming attach arrives with a
          user ID and a password, the user ID and the password are looked up in
          one of two lists: APPC's local list of valid user IDs and passwords
          or a list maintained by UPM.

          When an incoming attach arrives with a user ID and password, the APPC
          attach manager searches for a valid user ID and password combination
          among its conversation security entries. If a valid user ID and
          password combination is not found, the APPC attach manager sends the
          user ID and password combination to UPM for validation.


ΓòÉΓòÉΓòÉ 8.17. DELETE_COS ΓòÉΓòÉΓòÉ

DELETE_COS

This verb deletes a class of service (COS) definition. When all modes referring
to the COS are deleted, the COS definition is deleted.

See DELETE_COS Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_COSΓöÇΓöÇkeynameΓöÇΓöÇcos_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          cos_name
                    The 8-byte EBCDIC name for the COS. This is the name of the
                    COS as it is known throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

 Return Codes

          The OK return code indicates that the DELETE_COS verb ran
          successfully.

          DELETE_COS Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the DELETE_COS verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_COS Primary and Secondary Return Codes                      Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé COS_NAME_NOT_DEFD        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé SNA_DEFD_COS_CANT_BE_CHANGED  Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The following COS names that are supplied with Communications Manager
          cannot be deleted:

          o #BATCH
          o #BATCHSC
          o #CONNECT
          o #INTER
          o #INTERSC
          o CPSVCMG
          o SNASVCMG


ΓòÉΓòÉΓòÉ 8.18. DELETE_DEFAULT_SOC ΓòÉΓòÉΓòÉ

DELETE_DEFAULT_SOC

This verb deletes a default sphere of control (SOC) for a specified MS
category. You use the DELETE_DEFAULT_SOC verb to disable the local APPN network
node (NN) as the default primary focal point (FP) for the MS category. However,
no MS capabilities messages are exchanged because of issuing this verb, and EP
nodes can still use the local node as a default FP, but it will no longer retry
establishing FP-EP relationships.

See DELETE_DEFAULT_SOC Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_DEFAULT_SOCΓöÇΓöÇkeynameΓöÇΓöÇms_categorynameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    The name of the master or service key configured with the
                    Communications Manager keylock feature.

          ms_category
                    The name of the MS category for the SOC. Specify either a
                    4-byte SNA-defined name or a 1- to 8-byte Type A EBCDIC
                    name, left justified and filled on the right with EBCDIC
                    space (X'40') characters.

 Return Codes

          The OK return code indicates that the DELETE_DEFAULT_SOC verb ran
          successfully.

          DELETE_DEFAULT_SOC Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DELETE_DEFAULT_SOC verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_DEFAULT_SOC Primary and Secondary Return Codes                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé NO_SOC_DEFINED_FOR_MS_CATEGORY Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé SOC_FOR_MS_CATEGORY_NOT_DEFAULTΓöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DELETE_DEFAULT_SOC verb is used to stop the local node from
          establishing any new FP-EP relationships or retrying broken ones.

          The default SOC nodes are marked pending inactive in the list of SOC
          nodes maintained internally in memory. Each is removed from the list
          when an MS capabilities messages (X'62') is received that revokes or
          rejects the FP-EP relationship, or when the FP-EP relationship
          becomes broken.


ΓòÉΓòÉΓòÉ 8.19. DELETE_EXPLICIT_SOC ΓòÉΓòÉΓòÉ

DELETE_EXPLICIT_SOC

This verb deletes node entries from the sphere of control (SOC) for a specified
MS category. You use the DELETE_EXPLICIT_SOC verb to disable the local APPN
network node (NN) as the FP node for the specified SOC nodes, no matter how the
local FP node acquired the SOC nodes.

No MS capabilities messages are exchanged because of issuing this verb, and the
specified SOC EP nodes can still use the local node as an FP. The local node
will no longer retry establishing FP-EP relationships if it was a default SOC
FP for the EP nodes. However, explicit and implicit SOC EP nodes can continue
to retry when the FP-EP relationship is broken, and the local FP node accepts
the EP's retry request.

See DELETE_EXPLICIT_SOC Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_EXPLICIT_SOCΓöÇΓöÇkeynameΓöÇΓöÇms_categorynameΓöÇΓöÇnumber_of_soc_nodesΓöÇΓöÇΓö¼ΓöÇnΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                        ΓööΓöÇ0ΓöÇΓöÿ

          Specify for each number_of_backup_fps:

                    >ΓöÇΓöÇΓö¼ΓöÇbackup_fp_fq_cp_namenameΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    The name of the master or service key configured with the
                    Communications Manager keylock feature.

          ms_category
                    The name of the MS category for the SOC. Specify either a
                    4-byte SNA-defined name or a 1- to 8-byte Type A EBCDIC
                    name, left justified and filled on the right with EBCDIC
                    space (X'40') characters.

          number_of_soc_nodes
                    The number of SOC node CP names following this parameter. A
                    value of 0 may be specified, indicating that all SOC node
                    entries in the local FP node's SOC are to be deleted.

          soc_node_cp_name
                    The CP names of the explicit SOC nodes, with one entry for
                    each CP name. Each name must be network qualified, left
                    justified and filled on the right with EBCDIC space (X'40')
                    characters. The number of entries must be equal to the
                    value on the number_of_soc_nodes parameter.

 Return Codes

          The OK return code indicates that the DELETE_EXPLICIT_SOC verb ran
          successfully.

          DELETE_EXPLICIT_SOC Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DELETE_EXPLICIT_SOC verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_EXPLICIT_SOC Primary and Secondary Return Codes                 Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé NO_SOC_EXISTS_FOR_MS_CATEGORY  Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DELETE_EXPLICIT_SOC verb is used to stop the local node from
          establishing any new FP-EP relationships, or retrying broken ones,
          with the specified SOC nodes. It can be used to delete specific SOC
          node entries, no matter how the local FP node acquired the SOC nodes.
          The local node may be the primary or backup FP, and the SOC nodes may
          have been acquired by local definition, using the DEFINE_DEFAULT_SOC
          or DEFINE_IMPLICIT_SOC verb; or by remote implicit definition, using
          the DEFINE_REMOTE_FP verb on the EP node (or an equivalent EP
          function).

          The SOC node is marked pending inactive in the list of SOC nodes
          maintained internally in memory. Each is removed from the list when
          an MS capabilities messages (X'62') is received that revokes or
          rejects the FP-EP relationship, or when the FP-EP relationship
          becomes broken. SOC node entries that are already inactive are
          immediately removed from the SOC.


ΓòÉΓòÉΓòÉ 8.20. DELETE_LOCAL_LU ΓòÉΓòÉΓòÉ

DELETE_LOCAL_LU

This verb requests deletion of the local LU definition. If the local LU is
currently active, the local LU is deleted when all sessions are taken down.
Neither the control point (CP) LU nor any dependent LUs can be deleted.

See DELETE_LOCAL_LU Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_name
                    The 8-byte EBCDIC network name of the local LU. This is the
                    name of the LU as it is known throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

 Return Codes

          The OK return code indicates that the DELETE_LOCAL_LU verb ran
          successfully.

          DELETE_LOCAL_LU Primary and Secondary Return Codes shows the primary
          and secondary return codes associated with the DELETE_LOCAL_LU verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_LOCAL_LU Primary and Secondary Return Codes                   Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEL_LOCAL_DEPENDENT_LU     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LU_NAME_NOT_DEFD        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé LU_NAME_SAME_AS_CP_NAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DELETE_LOCAL_LU verb causes a CNOS (reset) verb to be issued for
          all modes on all the partner LUs for this LU. When all the sessions
          using this LU are deactivated and all the TPs using this LU are
          ended, APPC deletes the active LU control block.


ΓòÉΓòÉΓòÉ 8.21. DELETE_LU_LU_PASSWORD ΓòÉΓòÉΓòÉ

DELETE_LU_LU_PASSWORD

This verb deletes an LU-LU password used for sessions. When all sessions
between the local LU and the partner LU are inactive, the definition is
deleted.

See DELETE_LU_LU_PASSWORD Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_LU_LU_PASSWORDΓöÇΓöÇkeynameΓöÇΓöÇlu_aliasnameΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          lu_alias
                    The 8-byte ASCII name used locally for the LU. The name is
                    not sent outside the local node.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks.

                    Alternatively, you can select the default local LU by
                    specifying 8 bytes of binary zeros.

                    Note:  This parameter is case sensitive. Ensure that this
                    field is defined with the correct uppercase and lowercase
                    characters.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

 Return Codes

          The OK return code indicates that the DELETE_LU_LU_PASSWORD verb ran
          successfully.

          DELETE_LU_LU_PASSWORD Primary and Secondary Return Codes shows the
          primary and secondary return codes associated with the
          DELETE_LU_LU_PASSWORD verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_LU_LU_PASSWORD Primary and Secondary Return Codes                Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé BAD_LU_ALIAS          Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_FQPLU_NAME       Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEF_LU_LU_PW_SESS_ACTIVE    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          If an LU-LU password is not defined for the specified lu_alias and
          fq_partner_lu_name parameters, a primary return code of
          PARAMETER_CHECK and a secondary return code of INVALID_FQPLU_NAME are
          returned.


ΓòÉΓòÉΓòÉ 8.22. DELETE_MODE ΓòÉΓòÉΓòÉ

DELETE_MODE

This verb requests deletion of the mode definition. A DELETE_MODE verb may also
request deletion of the active modes created due to the implicit mode
capability. When the mode is inactive for all active partner LUs, the mode is
deleted.

See DELETE_MODE Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_MODEΓöÇΓöÇkeynameΓöÇΓöÇmode_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          mode_name
                    The 8-byte EBCDIC name for the mode. The mode name is used
                    to designate the network properties for a group of
                    sessions. This is the name of the mode as it is known
                    throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

 Return Codes

          The OK return code indicates that the DELETE_MODE verb ran
          successfully.

          DELETE_MODE Primary and Secondary Return Codes shows the primary and
          secondary return codes associated with the DELETE_MODE verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_MODE Primary and Secondary Return Codes                     Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé CP_OR_SNA_SVCMG_UNDELETABLE   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé DEL_MODE_DEFAULT_SPCD      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé MODE_NAME_NOT_DEFD       Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DELETE_MODE verb causes a CNOS (reset) verb to be issued for the
          specified mode on all the partner LUs that the mode is active. When
          all the sessions for the active mode control blocks are deactivated,
          the mode will be deleted.

          The architected modes, CPSVCMG and SNASVCMG, cannot be deleted.


ΓòÉΓòÉΓòÉ 8.23. DELETE_PARTNER_LU ΓòÉΓòÉΓòÉ

DELETE_PARTNER_LU

This verb requests deletion of a partner LU definition. A DELETE_PARTNER_LU
verb may also request deletion of the active partner LUs created due to the
implicit partner LU capability. When the partner LU is inactive for all active
local LUs (including the local control point (CP)), the partner LU is deleted.

See DELETE_PARTNER_LU Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_PARTNER_LUΓöÇΓöÇkeynameΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

 Return Codes

          The OK return code indicates that the DELETE_PARTNER_LU verb ran
          successfully.

          DELETE_PARTNER_LU Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DELETE_PARTNER_LU verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_PARTNER_LU Primary and Secondary Return Codes                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé CPSVCMG_SESSION_ACTIVE     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé FQPLU_NAME_NOT_DEFD       Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The DELETE_PARTNER_LU verb causes a CNOS (reset) verb to be issued
          for all the modes on all the specified partner LU. When all the
          sessions for the partner LU are deactivated, the partner LU will be
          deleted.


ΓòÉΓòÉΓòÉ 8.24. DELETE_PARTNER_LU_LOCATION ΓòÉΓòÉΓòÉ

DELETE_PARTNER_LU_LOCATION

This verb deletes the partner LU entry from the APPN directory database.

See DELETE_PARTNER_LU_LOCATION Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_PARTNER_LU_LOCATIONΓöÇΓöÇkeynameΓöÇΓöÇwildcard_entryΓöÇΓöÇΓö¼ΓöÇFULLΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                                 Γö£ΓöÇPARTIALΓöÇΓöñ
                                                 ΓööΓöÇNOΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          wildcard_entry
                    Specifies whether this APPN directory entry is to be a
                    wildcard entry.

                    You must specify one of the following values:

             FULL
                       Specifies that this is a wildcard entry. The fully
                       qualified partner LU name is ignored and causes the node
                       to always return a "found" reply to a directory search.
                       This capability is used only when defining adjacent LEN
                       nodes.

             PARTIAL
                       Specifies that this is a partial wildcard entry. The
                       fully qualified partner LU name is specified as a
                       partial name on this entry and causes the node to return
                       a "found" reply to a directory search when the partial
                       name matches the first (left-hand) part of the LU name
                       being searched.

                       The partial LU name must not be defined on any other
                       node in the APPN network.

             NO
                       Specifies that this is not a wildcard entry. The partner
                       LU name must be specified.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

 Return Codes

          The OK return code indicates that the DELETE_PARTNER_LU_LOCATION verb
          ran successfully.

          DELETE_PARTNER_LU_LOCATION Primary and Secondary Return Codes shows
          the primary and secondary error return codes associated with the
          DELETE_PARTNER_LU_LOCATION verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_PARTNER_LU_LOCATION Primary and Secondary Return Codes              Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_WILDCARD_ENTRY     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_FQLU_NAME        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé PLU_LOCATION_NOT_DEFD      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.25. DELETE_TP ΓòÉΓòÉΓòÉ

DELETE_TP

This verb deletes an APPC transaction program definition. Any attaches, APPC
RECEIVE_ALLOCATE verbs, or CPI Communications Accept_Conversation (CMACCP)
calls queued for the deleted TP will be rejected. For nonqueued TPs, the TP
definition is deleted immediately. For queued TPs, the TP definition is deleted
when the active instance terminates.

See DELETE_TP Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_TPΓöÇΓöÇkeynameΓöÇΓöÇtp_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          tp_name
                    Specifies the name of the transaction program as specified
                    on the DEFINE_TP verb. This is a 64-byte Type AE name
                    EBCDIC character string.

 Return Codes

          The OK return code indicates that the DELETE_TP verb ran
          successfully.

          DELETE_TP Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the DELETE_TP verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_TP Primary and Secondary Return Codes                      Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé TP_NAME_NOT_RECOGNIZED     Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.26. DELETE_USER_ID_PASSWORD ΓòÉΓòÉΓòÉ

DELETE_USER_ID_PASSWORD

This verb requests deletion of user ID and password.

See DELETE_USER_ID_PASSWORD Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDELETE_USER_ID_PASSWORDΓöÇΓöÇkeynameΓöÇΓöÇuser_idnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          user_id
                    Specifies a valid user ID. If you do not specify User
                    Profile Management (UPM), this is a 10-byte Type AE name
                    EBCDIC character string. If you delete the association
                    between APPC conversation security and UPM, specify an
                    EBCDIC asterisk (X'5C').

 Return Codes

          The OK return code indicates that the DELETE_USER_ID_PASSWORD verb
          ran successfully.

          DELETE_USER_ID_PASSWORD Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          DELETE_USER_ID_PASSWORD verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      DELETE_USER_ID_PASSWORD Primary and Secondary Return Codes               Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé USERID_NOT_DEFD         Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 8.27. REVOKE_REMOTE_FP ΓòÉΓòÉΓòÉ

REVOKE_REMOTE_FP

This verb revokes the current remote focal point (FP) if its rank is other than
a domain or host FP. You use the REVOKE_REMOTE_FP verb to remove the EP from
the FP's sphere of control (SOC). If a domain or host FP is known to the local
EP node, it becomes the current FP after this verb completes. Otherwise, the EP
is left without an FP for the MS category.

You can reacquire the revoked FP (or acquire a different FP) using the
DEFINE_REMOTE_FP verb.

See REVOKE_REMOTE_FP Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇREVOKE_REMOTE_FPΓöÇΓöÇkeynameΓöÇΓöÇms_categorynameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          key
                    Specifies either the master or service key if the keylock
                    feature has been activated.

                    This is an 8-byte ASCII character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    ASCII blanks. Refer to User's Guide for details of the
                    keylock feature.

          ms_category
                    The name of the MS category for the FP.

 Return Codes

          The OK return code indicates that the REVOKE_REMOTE_FP verb ran
          successfully.

          REVOKE_REMOTE_FP Primary and Secondary Return Codes shows the primary
          and secondary error return codes associated with the REVOKE_REMOTE_FP
          verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      REVOKE_REMOTE_FP Primary and Secondary Return Codes                   Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_KEY       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé MS_CATEGORY_DOES_NOT_EXIST   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          The REVOKE_REMOTE_FP verb is used to revoke the current remote FP
          (other than a domain or host FP). The FP can be either a primary,
          default, or backup.

          The EP node stores the revoke safely on the fixed disk so that, if
          the EP has retry responsibility and the remote FP definition remains
          unchanged, the EP will not try to reestablish the FP-EP relationship
          following the restarting of Communications Manager.


ΓòÉΓòÉΓòÉ 8.28. SNA Node Definition Verbs ΓòÉΓòÉΓòÉ

The following SNA Node Definition verbs can be used for defining configurations
within your node definitions file (.NDF).

          o DEFINE_APPC_ATTACH_ROUTE
          o DEFINE_CLIENT_DEP_APPC_ACCESS
          o DEFINE_CLIENT_INDEP_APPC_ACCESS
          o DEFINE_CLIENT_LUA_ACCESS
          o DEFINE_CONNECTION_NETWORK
          o DEFINE_CPIC_SIDE_INFO
          o DEFINE_DEFAULTS
          o DEFINE_LOCAL_CP
          o DEFINE_LUA_POOL


ΓòÉΓòÉΓòÉ 8.29. DEFINE_APPC_ATTACH_ROUTE (NDF Only) ΓòÉΓòÉΓòÉ

DEFINE_APPC_ATTACH_ROUTE (NDF Only)

This verb enables routing of LU 6.2 attaches (refered to simply as an attach)
when their destination is a communications client.  If an attach is received
for one of the specified LUs, the attach manager routes the attach to the
specified communications client for processing.

Note:  This verb is necessary only for the routing of attaches for client
dependent LUs.  If an attach is received for a client independent LU, the
DEFINE_CLIENT_INDEP_APPC_ACCESS verb provides the destination communications
client.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_APPC_ATTACH_ROUTEΓöÇΓöÇmachine_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇlu_aliasΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                                     ΓööΓöÇdescriptionΓöÇΓöÇ(ΓöÇΓöÇtextΓöÇΓöÇ)ΓöÇΓöÿ

 Parameters

          machine_name
                    Specifies the machine name of the destination client for
                    routing incoming attaches.

                    The client machine name is defined according to the client
                    platform being used. The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_MACHINE_NAME environment variable if the client machine
               is using User Provided Names on the DOS client.

             o The CS_MACHINE_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    This is a 1- to 15-byte ASCII character string that
                    consists of uppercase letters (A-Z), digits (0-9), and the
                    special characters $, #, and @. The character string cannot
                    start with a digit.

          lu_alias
                    Specifies those dependent 6.2 LUs at the communications
                    server for which attaches are to be routed. If an attach is
                    received for any of the specified LUs, the attach manager
                    will route it to the specified communications client for
                    processing. Dependent LUs are identified by LU alias, which
                    is defined in the LU_ALIAS field of the DEFINE_LOCAL_LU
                    verb. Each LU alias is a 1- to 8-byte ASCII character
                    string.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can begin in the first position of the
                    character string. Up to 255 client LU aliases can be
                    specified.

          description
                    A description of this communications client attach route.
                    The string is free format and can be up to 64 ASCII
                    characters long.


ΓòÉΓòÉΓòÉ 8.30. DEFINE_CLIENT_DEP_APPC_ACCESS (NDF only) ΓòÉΓòÉΓòÉ

DEFINE_CLIENT_DEP_APPC_ACCESS (NDF only)

This verb defines the access that communications clients and their users have
to dependent APPC resources at the communications server. In order to access
these dependent APPC resources, an authorized user must be logged on to one of
the specified client machines. These dependent APPC resources consist of one or
more dependent 6.2 LUs defined at the communications server.

Note:  You can use the DEFINE_CLIENT_DEP_APPC_ACCESS verb to add a new
definition or replace an existing one.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_CLIENT_DEP_APPC_ACCESSΓöÇΓöÇdep_appc_acc_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇmachine_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇuser_or_group_idΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇlu_aliasΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                          ΓööΓöÇdescriptionΓöÇΓöÇ(ΓöÇΓöÇtextΓöÇΓöÇ)ΓöÇΓöÿ

 Parameters

          dep_appc_acc_name
                    The unique name of the communications client dependent APPC
                    access to be defined. This is a 1- to 8-byte ASCII
                    character string.

          machine_name
                    Specifies those client machines that are authorized to
                    access the specified dependent APPC resources at the
                    communications server. Authorized client machines are
                    identified by their machine names.

                    A client machine name is defined according to the client
                    platform being used.  The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_MACHINE_NAME environment variable if the client machine
               is using User Provided Names on the DOS client.

             o The CS_MACHINE_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    Each client machine is a 1- to 15-byte ASCII character
                    string that consists of uppercase letters (A-Z), digits
                    (0-9), and the special characters $, #, and @. The
                    character string cannot start with a digit.

                    Each can contain the wildcard characters "?"  and "*". The
                    wildcard characters can be in the first position of the
                    character string. Up to 255 client machine names can be
                    specified.

          user_or_group_id
                    Specifies those users that are authorized to access the
                    specified dependent APPC resources at the communications
                    server. In order to access these resources, an authorized
                    user must be logged on to one of the specified client
                    machines. Authorized users are identified by a User ID, or
                    authorized groups of users are identified by a Group ID.

                    A user_or_group_id is defined according to the client
                    platform being used. The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_USER_NAME environment variable if the client machine is
               using User Provided Names on the DOS client.

             o The CS_USER_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    Each ID is a 1- to 20-byte ASCII character string that
                    consists of uppercase letters (A-Z), digits (0-9), and the
                    special characters $, #, and @. The character string cannot
                    start with a digit. Up to 255 LAN Server User or Group IDs
                    or user provided names may be specified.

          lu_alias
                    Specifies those dependent 6.2 LUs at the communications
                    server that the specified client machines and their
                    specified users have access to. Dependent LUs are
                    identified by LU alias, which is defined in the LU_ALIAS
                    field of the DEFINE_LOCAL_LU verb.

                    Each LU alias is a 1- to 8-byte ASCII character string.

                    Each may contain the wildcard characters "?" and "*". The
                    wildcard characters may begin in the first position of the
                    character string. Up to 255 client LU aliases may be
                    specified.

          description
                    A description of this communications client dependent APPC
                    access. The string is free format and can be up to 64 ASCII
                    characters long.


ΓòÉΓòÉΓòÉ 8.31. DEFINE_CLIENT_INDEP_APPC_ACCESS (NDF only) ΓòÉΓòÉΓòÉ

DEFINE_CLIENT_INDEP_APPC_ACCESS (NDF only)

This verb defines the access that a communications client and its users have to
an independent 6.2 LU at the communications server. In order to access these
independent APPC resources, an authorized user must be logged on to the client
machine.

This independent 6.2 LU is dynamically defined at the communications server
when the client machine is started. If a client has been configured for
independent APPC access at multiple communications servers, the client will
choose one server in each network on which to define an independent LU.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_CLIENT_INDEP_APPC_ACCESSΓöÇΓöÇind_appc_acc_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇmachine_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇuser_or_group_idΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇlu_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇlu_aliasΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                 ΓööΓöÇdefaultΓöÇΓöÇ(ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇ)ΓöÇΓöÿ
                                                        ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇpreferredΓöÇΓöÇ(ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇ)ΓöÇΓöÿ  ΓööΓöÇdescriptionΓöÇΓöÇ(ΓöÇΓöÇtextΓöÇΓöÇ)ΓöÇΓöÿ
                              ΓööΓöÇNOΓöÇΓöÇΓöÿ

 Parameters

          ind_appc_acc_name
                    The unique name of the communications client independent
                    APPC access to be defined. This is a 1- to 8-byte ASCII
                    character string.

          machine_name
                    Specifies the machine name of the communications client
                    that has independent APPC access to the communications
                    server. When the client machine is started, a server in
                    each network is chosen on which it has independent APPC
                    access to define an independent LU.

                    The client machine name is defined according to the client
                    platform being used. The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_MACHINE_NAME environment variable if the client machine
               is using User Provided Names on the DOS client.

             o The CS_MACHINE_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    This is a 1- to 15-byte ASCII character string that
                    consists of uppercase letters (A-Z), digits (0-9), and the
                    special characters $, #, and @. The character string cannot
                    start with a digit.

          user_or_group_id
                    Specifies those users that are authorized to access the
                    specified independent APPC resources at the communications
                    server. In order to access these resources, an authorized
                    user must be logged on to the specified client machine.
                    Authorized users are identified by a User ID, or authorized
                    groups of users are identified by a Group ID.

                    A user_or_group_id is defined according to the client
                    platform being used. The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_USER_NAME environment variable if the client machine is
               using User Provided Names on the DOS client.

             o The CS_USER_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    Each ID is a 1- to 20-byte ASCII character string that
                    consists of uppercase letters (A-Z), digits (0-9), and the
                    special characters $, #, and @. The character string cannot
                    start with a digit.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can be in the first position of the
                    character string. Up to 255 LAN Server User or Group IDs or
                    user provided names can be specified.

          lu_name
                    Specifies the name of the LU that is defined when the
                    client machine is started. The LU name is also installed as
                    an LU alias when the LU is defined. This LU alias must be
                    specified when remotely starting a transaction program (TP)
                    on the specified client from any TP using an LU on this
                    server workstation (any TP running on the server
                    workstation or any TP running on a client and using an LU
                    on the server workstation).

                    The LU name is a 1- to 8-byte ASCII character string. The
                    ASCII character string must consist of uppercase letters
                    (A-Z), digits (0-9), and the special characters $, #, and
                    @. The character string cannot start with a digit.

          lu_alias
                    Specifies a list of LU aliases that may be used by
                    transaction programs on the communications client to access
                    the independent LU at the server.

                    Each LU alias is a 1- to 8-byte ASCII character string.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can be in the first position of the
                    character string. Up to 255 client LU aliases can be
                    specified.

          default
                    Specifies whether or not the independent LU is a default
                    LU. If YES is specified, application programs on the
                    communications client may specify the default LU when
                    starting a transaction program (TP). If NO is specified,
                    application programs that attempt to start a TP on the
                    default LU will not be given access to the LU.

          preferred
                    Specifies whether or not this communications server is
                    preferred for independent APPC access. If the
                    communications client is configured for independent APPC
                    access on multiple servers, one is chosen. A preferred
                    server is selected if one is available. If not, a
                    non-preferred server is selected. If a non-preferred server
                    is selected, and a preferred server becomes available, the
                    independent LU is redefined on the preferred server when
                    the LU is not in use.

          description
                    A description of this communications client independent
                    APPC access. The string is free format and can be up to 64
                    ASCII characters long.


ΓòÉΓòÉΓòÉ 8.32. DEFINE_CLIENT_LUA_ACCESS (NDF-only) ΓòÉΓòÉΓòÉ

DEFINE_CLIENT_LUA_ACCESS (NDF-only)

This verb defines the access that communications clients and their users have
to LUA resources at the communications server. In order to access these
dependent LUA resources, an authorized user must be logged on to one of the
specified client machines.

These LUA resources consist of one or more LUA LUs and one or more LUA pools
defined at the communications server. You can use the DEFINE_CLIENT_LUA_ACCESS
verb to add a new definition or replace an existing one.

 Supplied Parameter Syntax

                                                           ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                                                                 Γöé
                    >>ΓöÇΓöÇDEFINE_CLIENT_LUA_ACCESSΓöÇΓöÇlua_acc_nameΓöÇΓöÇmachine_nameΓöÇΓöÇuser_or_group_idΓöÇΓöÇΓöÇΓö¼ΓöÇlu_nameΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                                           ΓööΓöÇpool_nameΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      ΓööΓöÇdescriptionΓöÇΓöÇtextΓöÇΓöÿ

 Parameters

          lua_acc_name
                    The unique name of the communications client LUA access to
                    be defined.

                    This is a 1- to 8-byte ASCII character string which
                    consists of uppercase letters(A-Z), digits (0-9), and the
                    special characters $, #, and @.  The character string
                    cannot begin with a digit.

          machine_name
                    Specifies those client machines that are authorized to
                    access the specified LUA resources at the communications
                    server. Authorized client machines are identified by their
                    machine names.

                    A client machine name is defined according to the client
                    platform being used. The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_MACHINE_NAME environment variable if the client machine
               is using User Provided Names on the DOS client.

             o The CS_MACHINE_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    This is a 1- to 15-byte ASCII character string that
                    consists of uppercase letters (A-Z), digits (0-9), and the
                    special characters $, #, and @. The character string cannot
                    start with a digit.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can begin in the first position of the
                    character string. Up to 255 machine names may be specified.

          user_or_group_id
                    Specifies those users that are authorized to access the
                    specified LUA resources at the communications server. In
                    order to access these resources, an authorized user must be
                    logged on to one of the specified client machines.
                    Authorized users are identified by a User ID, or authorized
                    groups of users are identified by a Group ID.

                    A user_or_group_id is defined according to the client
                    platform being used. The different ways are:

             o A LAN Management software package if the client machine is using
               LAN Requester Provided Names. This option is available for all
               client platforms.

             o The Communications Client Connection Information window if the
               client machine is using User Provided Names on the OS/2 client.

             o The CS_USER_NAME environment variable if the client machine is
               using User Provided Names on the DOS client.

             o The CS_USER_NAME profile entry in the CMCS section of the
               WIN.INI if the client machine is using User Provided Names on
               the Windows client.

                    Each ID is a 1- to 20-byte ASCII character string that
                    consists of uppercase letters (A-Z), digits (0-9), and the
                    special characters $, #, and @. The character string cannot
                    start with a digit.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can begin in the first position of the
                    character string. Up to 255 LAN Server User or Group IDs or
                    user provided names may be specified.

          lu_name
                    Specifies those LUA LUs at the communications server that
                    the specified client machines and their specified users
                    have access to. LUA LUs are identified by LU name, which is
                    defined in the lu_name field of the DEFINE_LUA verb.

                    Each LU name is a 1- to 8-byte ASCII character string. The
                    ASCII character string must consist of uppercase letters
                    (A-Z), digits (0-9), and the special characters $, #, and
                    @. The character string cannot start with a digit.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can begin in the first position of the
                    character string. Up to 255 client LU names can be
                    specified.

                    Note:  Either lu_name, pool_name, or both must be
                    specified.

          pool_name
                    Specifies those LUA pools at the communications server that
                    the specified client machines and their specified users
                    have access to. LUA pools are identified by LUA pool name,
                    which is defined in the pool_name field of the
                    DEFINE_LUA_POOL verb.

                    This is a 1- to 8-byte ASCII character string.

                    Each pool name is a 1- to 8-byte ASCII character string.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can be in the first position of the
                    character string. Up to 255 client pool names can be
                    specified.

                    Each pool name must be unique within this definition file.
                    Pools may span multiple communications servers by
                    specifying the same pool name on each communications server
                    that you want in the spanned pool.

                    Note:  Either lu_name, pool_name, or both must be
                    specified.

          description
                    A description of this communications client LUA access. The
                    string is free format and can be up to 64 ASCII characters
                    long.


ΓòÉΓòÉΓòÉ 8.33. DEFINE_CONNECTION_NETWORK (NDF Only) ΓòÉΓòÉΓòÉ

DEFINE_CONNECTION_NETWORK (NDF Only)

This verb defines a connection network that the local control point (CP) can
access, and the adapters use to connect to the connection network. The
connection network applies only to LAN connections. Up to five adapters of any
type may be used to access a single connection network. The adapters are
identified by DLC name and adapter number.

This verb is used to add a new definition. If the connection network name is
not already defined, the new definition is added. If the connection network
name is already defined or a specified adapter is active, the verb is rejected.

A connection network definition cannot be deleted.

This verb can only be executed as a command in a SNA node definitions file. For
a template of this command, refer to file CMVERIFY.TXT located in the \CMLIB
directory.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_CONNECTION_NETWORKΓöÇΓöÇfq_cn_namenameΓöÇΓöÇadapter_infoΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

          Specify for each adapter_info

                    >>ΓöÇΓöÇadapter_numbernΓöÇΓöÇdlc_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

 Parameters

          fq_cn_name
                    Specifies the 17-byte fully qualified network name for the
                    connection network. CP-CP sessions must be maintained by
                    the APPN end nodes in order to achieve this connectivity.

                    Choose the connection name with the same care with which
                    you would name the CP of an individual machine. The NETID
                    portion should match the NETID of other machines in the
                    same SNA network. The connection network name portion must
                    be unique among the LU names in the SNA network. The same
                    fq_cn_name must be defined on all of the machines that will
                    participate in the connection network.

          adapter_info
                    Specifies the list of DLC names and adapter numbers in this
                    workstation participating in the connection network. You
                    can specify up to five adapters.  Only LAN adapters may be
                    specified.

             adapter_number
                       Specifies the adapter number to use. This must be the
                       same number as that configured for an adapter.

             dlc_name
                       The 8-byte ASCII name of the local data link control
                       (DLC). This is the name used to configure a DLC in the
                       Communications Manager DLC profile. The valid names are:

                o 'ETHERAND'
                o 'IBMPCNET'
                o 'IBMTRNET'
                o 'SDLC   '
                o 'TWINAX  '
                o 'X25DLC  '
                o 'IDLC   '

                       This is an 8-byte ASCII character string. If the name is
                       less than 8 bytes, it must be padded on the right with
                       ASCII blanks.

 Comments

          The DEFINE_CONNECTION_NETWORK verb is used to provide a definition
          which will allow any-to-any connectivity over the specified adapters.
          The fq_cn_name must be identical on all of the machines that will
          participate in the connection network. CP-CP sessions must be
          maintained by the APPN end nodes in order to achieve this
          connectivity.


ΓòÉΓòÉΓòÉ 8.34. DEFINE_CPIC_SIDE_INFO (NDF Only) ΓòÉΓòÉΓòÉ

DEFINE_CPIC_SIDE_INFO (NDF Only)

The DEFINE_CPIC_SIDE_INFO verb creates a side information entry that the OS/2
CPI Communications support will use when initiating CPI Communications
conversations. This side information contains the information necessary to
locate and establish a conversation between the local CPI Communications
transaction program (TP) and a partner TP. The partner TP can be either a CPI
Communications TP or a LU 6.2 TP. This information is only used when the local
CPI Communications TP is initiating the conversation.

This verb can only be executed as a command in SNA node definitions file. For a
template of this command, refer to file CMVERIFY.TXT installed in \CMLIB.

Note:  DEFINE_CPIC_SIDE_INFO and DELETE_CPIC_SIDE_INFO functions can be
initiated through CXMSSI and CXMDSI respectively.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_CPIC_SIDE_INFOΓöÇΓöÇsymbolic_destination_namenameΓöÇΓöÇpartner_lu_aliasnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇfq_partner_lu_namenameΓöÇΓöÇmode_namenameΓöÇΓöÇtp_namenameΓöÇΓöÇsna_service_tpΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                                        ΓööΓöÇNOΓöÇΓöÇΓöÿ

 Parameters

          symbolic_destination_name
                    Specifies the symbolic destination name used by CPI
                    Communications applications to identify this definition. It
                    is a 1-8 byte name from ASCII character set 01134.

          partner_lu_alias
                    The locally known name for the partner LU.

                    This is an 8-byte ASCII character string. If the string is
                    less than 8 bytes, you must pad it on the right with ASCII
                    blanks.

                    Note:  This parameter is case sensitive. Ensure that this
                    field gets defined with the correct uppercase and lowercase
                    characters.

          fq_partner_lu_name
                    The 17-byte EBCDIC fully qualified network name for the
                    partner LU. The name consists of the partner network ID, an
                    EBCDIC period, and the partner_lu_name. This is the name of
                    the partner LU as it is known throughout the network.

                    This name is two type A EBCDIC character strings
                    concatenated by an EBCDIC period. Each name can have a
                    maximum length of 8 bytes with no embedded blanks. If the
                    network ID is not present, the period is omitted.

                    The partner_lu_alias and fq_partner_lu_name are mutually
                    exclusive: you can specify one of the other, but not both.

          mode_name
                    The 8-byte EBCDIC name for the mode. The mode name is used
                    to designate the network properties for a group of
                    sessions. This is the name of the mode as it is known
                    throughout the network.

                    This is a type A EBCDIC character string. If the name is
                    less than 8 bytes, it must be padded on the right with
                    EBCDIC blanks.

          tp_name
                    Specifies the name of the partner TP to be used when a CPI
                    Communications application initiates a conversation
                    specifying this side information entry. To specify an SNA
                    service TP, the first byte of the tp_name must be a
                    hexadecimal digit between X'01' and X'3F', excluding X'0E'
                    and X'0F'.

          sna_service_tp
                    Specifies whether the tp_name identifies a SNA service TP.
                    You must specify one of the following values:

             YES
                       Specifies that the TP identified by this parameter is an
                       SNA service TP. The first character of the tp_name must
                       be a hexadecimal digit between X'01' and X'3F',
                       excluding X'0E' and X'0F'. The remaining characters can
                       be any ASCII character in character set 00640.

             NO
                       Specifies that the TP identified by this parameter is
                       not an SNA service TP. The characters can be any ASCII
                       character set 00640 (including the first character).


ΓòÉΓòÉΓòÉ 8.35. DEFINE_DEFAULTS (NDF Only) ΓòÉΓòÉΓòÉ

DEFINE_DEFAULTS (NDF Only)

The DEFINE_DEFAULTS verb defines system default values for functions provided
by Communications Manager. The verb is used to create a new definition. The
default parameter definitions become active when Communications Manager is
started.

This verb can only be executed as a command in a SNA node definitions file. For
a template of this command, refer to file CMVERIFY.TXT located in the \CMLIB
directory.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_DEFAULTSΓöÇΓöÇdefault_mode_namenamedefault_local_lu_aliasΓöÇΓöÇinplicit_inbound_plu_supportΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇmax_mc_ll_send_sizeΓöÇΓöÇnΓöÇΓöÇdirectory_for_inbound_attachesΓöÇΓöÇstringΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇdefault_tp_operationΓöÇΓöÇΓö¼ΓöÇQUEUED_OPERATOR_STARTEDΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇdefault_tp_program_typeΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                 Γö£ΓöÇQUEUED_OPERATOR_PRELOADEDΓöÇΓöñ
                                 Γö£ΓöÇQUEUED_AM_STARTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                 ΓööΓöÇNONQUEUED_AM_STARTEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇBACKGROUNDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇdefault_tp_conv_security_rqdΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇSNA B channelsΓöÇΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                      Γö£ΓöÇFULL_SCREENΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ                 ΓööΓöÇNOΓöÇΓöÇΓöÿ
                      Γö£ΓöÇPRESENTATION MANAGERΓöÇΓöñ
                      ΓööΓöÇVIO_WINDOWABLEΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇmax_held_alertsΓöÇΓöÇnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

 Parameters

          default_mode_name
                    Specifies the mode name to be used under the following
                    conditions:

             o When an incoming BIND request contains a mode name not defined
               at the local node. The parameters defined for this mode are used
               for the inbound implicit mode capability.

             o When an APPC program issues an [MC_]ALLOCATE,
               [MC_]SEND_CONVERSATION, or CNOS verb, or when a CPI
               Communications program issues an Allocate (CMALLC) call,
               specifying a mode name not defined at the local node. The
               parameters defined for this mode are used for the outbound
               implicit mode capability.

                    This is a Type A character string. If this parameter is not
                    specified, no mode serves as the default.

                    Note:  The null (or all blank) mode name is a valid mode
                    name.

          default_local_lu_alias
                    Specifies the alias of the local LU that is to serve as the
                    default LU. This local LU alias must have been previously
                    defined.

                    Note:  This verb does not define a default LU for your
                    client. You specify a default LU for your client in the
                    DEFINE_CLIENT_INDEP_APPC verb.  For more information, see
                    DEFINE_CLIENT_INDEP_APPC_ACCESS.

                    The default LU is used when all binary zeros is specified
                    for the lu_alias on the TP_STARTED verb. If this parameter
                    is not specified, the local CP LU is used as the default
                    LU.

          implicit_inbound_plu_support
                    Specifies whether or not inbound implicit partner LU
                    support is enabled. You must specify one of the following
                    values:

             YES
                       Specifies that inbound implicit partner LU support is
                       enabled, which provides the capability to accept an
                       incoming BIND request that contains a partner LU name
                       that is not defined at the local node.

             NO
                       Specifies that inbound implicit partner LU support is
                       disabled, which means that an incoming bind that
                       specifies a partner LU that is not defined at the local
                       node will be rejected.

          max_mc_ll_send_size
                    Specifies the maximum size of a logical record to be used
                    on a mapped conversation for sending data to either the
                    inbound or outbound implicit partner LU. The size is the
                    number of bytes in the logical record, as indicated in the
                    LL field of the record. Specify 0 for a value of 32767.

          directory_for_inbound_attaches
                    Specifies the name of an OS/2 directory to be used by the
                    APPC attach manager when no DEFINE_TP verb has been issued
                    for the TP name received on an incoming attach. In this
                    case, the attach manager will attempt to start a program
                    whose file name is the same as the incoming TP name. If
                    found, the program is loaded based on the parameters below.
                    If not found, the attach is rejected.

                    Specify an asterisk (X'2A') to indicate that the OS/2 PATH
                    environment variable should be used when starting an
                    undefined transaction program.

                    Note:  This directory does not apply for client TPs.  To
                    specify a directory for client TPs, you need to do so on
                    the DEFINE_TP verb.  For more information, see DEFINE_TP.

                    When an OS/2 program is started by the APPC attach manager
                    because it found a matching name in the
                    directory_for_inbound_attaches, the attach manager uses the
                    following TP definition information for starting the
                    program:

             parm_string(null)
             conversation_type(EITHER)
             sync_level(EITHER)
             queue_depth_limit(255)
             incoming_allocate_timeout(HOLD_FOREVER)
             receive_allocate_timeout(HOLD_FOREVER)

          default_tp_operation
                    Specifies how a TP that has not been defined should be
                    loaded.

                    Note:  This does not apply for client TPs. You need to do
                    so on the DEFINE_TP verb.  For more information, see
                    DEFINE_TP. You must specify one of the following values:

             QUEUED_OPERATOR_STARTED
                       Specifies that one version of the program will be run at
                       a time. If an incoming attach arrives and the program
                       has not been started yet, APPC will issue a message to
                       the operator to start the specified program. Subsequent
                       attaches that arrive while the program is active will be
                       queued.

             QUEUED_OPERATOR_PRELOADED
                       Specifies that one version of the program will be run at
                       a time. If an incoming attach arrives and the program
                       has not been started yet, the attach will be queued
                       awaiting an APPC RECEIVE_ALLOCATE verb or a CPI
                       Communications program Accept_Conversation (CMACCP)
                       call. No message will be sent to the operator.
                       Subsequent attaches that arrive while the program is
                       active will be queued.

             QUEUED_AM_STARTED
                       Specifies that one version of the program will be run at
                       a time and will be started by the APPC attach manager.
                       Subsequent attaches that arrive while the program is
                       active will be queued.

             NONQUEUED_AM_STARTED
                       Specifies that multiple copies of the program will be
                       run at a time and will be started by the APPC attach
                       manager.

          default_tp_program_type
                    Specifies the type of screen group that will be associated
                    with a TP which has not been defined. You must specify one
                    of the following values:

             BACKGROUND
                       Specifies that the APPC attach manager starts the
                       program in a DETACHed OS/2 background process. The
                       program runs in a null (nonselectable) display session,
                       so the program cannot write to the screen or read from
                       the keyboard. If your program is completely debugged and
                       requires no interactive user input, this option provides
                       the fastest performance.

             FULL_SCREEN
                       Specifies that this program will have a screen group,
                       but will not run under the OS/2 Presentation Manager
                       interface.

             PRESENTATION_MANAGER
                       Specifies that this program will have a screen group and
                       will run under the OS/2 Presentation Manager interface.

             VIO_WINDOWABLE
                       Specifies that this program will have a screen group and
                       will run under the OS/2 Presentation Manager interface
                       and is also required to make OS/2 VIO calls.

          default_tp_conv_security_rqd
                    Specifies whether or not conversation security will be used
                    for default TPs. You must specify one of the following
                    values:

             YES
                       Specifies that the incoming attach must contain a valid
                       user ID and password.

             NO
                       Specifies that the incoming attach does not have to
                       contain security information.

          SNA B channels
                    Indicates the number of ISDN B channels available to APPC.

          max_held_alerts
                    Specifies the number of alerts that will be held by
                    Communications Manager if there is not an active link to a
                    focal point. When this number is exceeded, the oldest alert
                    will be discarded. You can specify a maximum value of 255.

                    Held alerts are lost whenever Communications Manager is
                    stopped in any way. They are not saved through a restarting
                    of the system.

 Comments

          The node definitions file does not require that all the parameters be
          supplied for the DEFINE_DEFAULTS verb. The following list shows the
          default values taken by each parameter, if it is not explicitly
          supplied:

          default_mode_name(X'4040404040404040')
          default_local_lu_alias(the local CP becomes the default LU)
          implicit_inbound_plu_support(YES)
          max_held_alerts(10)
          default_tp_conv_security(NO)
          max_mc_ll_send_size(32767)
          directory_for_inbound_attaches(no default directory)
          default_tp_operation(NONQUEUED_AM_STARTED)
          default_tp_program_type(BACKGROUND)


ΓòÉΓòÉΓòÉ 8.36. DEFINE_LOCAL_CP (NDF Only) ΓòÉΓòÉΓòÉ

DEFINE_LOCAL_CP (NDF Only)

This verb defines the parameters of the local control point (CP) LU. The local
CP must be defined before any other resources can be defined. This verb does
not replace an existing definition. An existing definition can be replaced only
by deactivating the local CP and then issuing this verb to redefine the local
CP.

A local CP definition cannot be deleted.

This verb can be executed as a command only in an SNA node definitions file.
For a template of this command, refer to file CMVERIFY.TXT installed in \CMLIB.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_LOCAL_CPΓöÇΓöÇnode_typeΓöÇΓöÇΓö¼ΓöÇNNΓöÇΓö¼ΓöÇΓöÇnode_ididΓöÇΓöÇfq_cp_namenameΓöÇΓöÇcp_aliasnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                    ΓööΓöÇENΓöÇΓöÿ
                    >ΓöÇΓöÇnau_addressaddressΓöÇΓöÇhost_fp_supportΓöÇΓöÇΓö¼ΓöÇYESΓöÇΓö¼ΓöÇΓöÇhost_fp_link_nameΓöÇΓöÇnameΓöÇΓöÇMAX_COMP_LEVELΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                        ΓööΓöÇNOΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇΓö¼ΓöÇNONEΓöÇΓö¼ΓöÇΓöÇMAX_COMP_TOKENSΓöÇΓöÇnumberΓöÇΓöÇNW_FP_SUPPORTΓöÇΓöÇΓö¼ΓöÇ0ΓöÇΓö¼ΓöÇΓöÇNW_SERVER_NAMEΓöÇΓöÇnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                      Γö£ΓöÇRLEΓöÇΓöÇΓöñ                      Γö£ΓöÇ1ΓöÇΓöñ
                      ΓööΓöÇLZ9ΓöÇΓöÇΓöÿ                      ΓööΓöÇ2ΓöÇΓöÿ

 Parameters

          node_type
                    Specifies the network capabilities of the node.

             NN
                       Specifies that the node provides APPN network node
                       capability.

                       The network node capability provided by Communications
                       Manager includes intermediate session routing, route
                       selection services, and APPN directory services for end
                       nodes and low-entry networking (LEN) nodes that it
                       serves, and for local users.

             EN
                       Specifies that the node provides APPN end node
                       capability.

                       The end node capability provided by Communications
                       Manager includes the registration of resources with its
                       APPN network node server and origin and destination end
                       node directory services for locating resources. The node
                       obtains APPN directory and route selection services from
                       its network node server, and it may have one or more
                       connections into the APPN network at a time.

          node_id
                    Specifies a unique node identifier for the local node. This
                    value is sent by Communications Manager in its XID
                    exchanges, and it is included in alert information. A
                    unique node ID value is required for links to an NCP or
                    VTAM.

                    When sending this complete node ID, Communications Manager
                    sends 4 bytes, consisting of 8 hexadecimal digits. The
                    first 3 digits, called the block number, are X'05D' for
                    Communications Manager. You specify the remaining 5
                    hexadecimal digits, called the ID number.

          fq_cp_name
                    Specifies the fully qualified control point name for the
                    node. It is made up of a 1-8 byte network ID concatenated
                    with a period and the 1-8 byte name of the CP. This forms
                    the fully qualified name by which the CP is known
                    throughout the network.

          cp_alias
                    Specifies the alias name by which transaction programs
                    within the node can designate the control point as the
                    local LU on the TP_STARTED, RECEIVE_ALLOCATE, and CNOS
                    verbs.

                    Note:  This parameter is case sensitive. Make sure that
                    this field gets defined with the correct uppercase and
                    lowercase spelling.

          nau_address
                    Specifies the destination network address of the CP LU for
                    sessions to a subarea node.

             INDEPENDENT_LU
                       Specifies that the network addressable unit (NAU)
                       address is not used, and the CP is to function as an
                       independent LU.

             1-254
                       Specifies the NAU address of the CP, and that the CP is
                       to function as a dependent LU for sessions to a subarea
                       node.

                       On a given link, every LU, including the CP LU, that
                       uses a dependent session must be assigned a unique NAU
                       address. Every LU defined for an LUA session, every LU
                       defined for a 3270 session, and every LU defined for a
                       3270 gateway session uses a dependent session and must
                       be assigned a unique NAU address.

          host_fp_support
                    Specifies whether the host provides management services
                    focal point support. You must specify a value of either YES
                    or NO.

          host_fp_link_name
                    Specifies the 8-character name of the link that defines the
                    link to the host. This parameter is used when
                    host_fp_support(YES) is specified. This link must be
                    defined on a DEFINE_LOGICAL_LINK verb.

                    This is a Type A name, which is a character string
                    consisting of one or more of the following:

             o Uppercase letters A through Z
             o Numbers 0 through 9
             o Three special characters: $, #, and @

                    The first character of this name must be an uppercase
                    letter or a special character. If this name is less than 8
                    characters, it must be padded on the right with blanks.

                    If the host_fp_support is set to YES and no
                    host_fp_link_name is specified, the link with the active
                    SSCP-PU session will be used if one exists.

                    Note:  This link, if one exists, will not be activated by
                    Communications Manager if it is a switched link and user
                    data sessions do not exist. In this case, a
                    host_fp_link_name should be specified.

                    We recommend you avoid using the $, #, and @ special
                    characters.

          MAX_COMP_LEVEL
                    Specifies the maximum compression level desired for
                    Communications Manager.  This parameter overrides all other
                    compression settings for determining the maximum level of
                    compression. This field contains one of the following
                    keywords for compression level:

             NONE      This setting does not allow compression for data
                       originating or terminating at Communications Manager.
                       This is the default setting.
             RLE       This setting causes the maximum level of compression to
                       be RLE.
             LZ9       This setting causes the maximum level of compression to
                       be LZ9.

          MAX_COMP_TOKENS
                    Specifies the maximum time and memory dedicated for data
                    compression execution.  The value in this field is used to
                    determine whether or not compression resources have been
                    exhausted. The parameter supplied with this keyword can
                    range from 0 to 3800. A value of 0 for this field can be
                    used to default the number of tokens to the amount needed
                    for one session at the MAX_COMP_LEVEL specified.

                    For a more detailed description of tokens, see Workstation
                    Installation and Configuration Guide.

          NW_FP_SUPPORT
                    The default value is none, in which case, neither
                    NW_FP_SUPPORT nor NW_SERVER_NAME are present.  When it is
                    present, the possible parameters for Communications Manager
                    upstream and NetWare upstream are:

             0         None
             1         Communications Manager upstream (NW_DOWNSTREAM)
             2         NetWare upstream (NW_UPSTREAM)

          NW_SERVER_NAME
                    The default value is blank which causes the NW_SERVER_NAME
                    to be absent from the NDF file. This keyword can only be
                    present if the NW_FP_SUPPORT keyword is also present.  The
                    parameter is an optional 2-128 byte ASCII string.  The
                    string is the name of the NetWare server with which a
                    connection is to be established.


ΓòÉΓòÉΓòÉ 8.37. DEFINE_LUA_POOL (NDF Only) ΓòÉΓòÉΓòÉ

DEFINE_LUA_POOL (NDF Only)

This verb enables you to group multiple LUA LUs together into an LUA pool. A
communications client requesting access to an LU in an LUA pool is given the
first available LU in the pool.

LUA pools can span multiple communications servers. This provides a method of
load balancing among server workstations. When a communications client requests
access to an LU in an LUA pool that spans multiple communications servers, a
server is randomly chosen to provide the LU. You can use the DEFINE_LUA_POOL
verb to add a new definition or replace an existing one.

Each pool name must be unique within this definition file. Pools may span
multiple communications servers by specifying the same pool name on each
communications server that you want in the spanned pool.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇDEFINE_LUA_POOLΓöÇΓöÇpool_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇlu_nameΓöÇΓöÇ(ΓöÇΓöÇ)ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                               ΓööΓöÇdescriptionΓöÇΓöÇ(ΓöÇΓöÇtextΓöÇΓöÇ)ΓöÇΓöÿ

 Parameters

          pool_name
                    Specifies the name of the LUA pool. The pool name may be
                    used in the DEFINE_CLIENT_LUA_ACCESS verb to authorize
                    communications clients and their users for access to the
                    LUA pool.

                    Note:  This same pool name may be used on multiple
                    communications servers when defining an LUA pool that spans
                    servers.

                    This a 1- to 8-byte ASCII character string.

          lu_name
                    Specifies those LUA LUs at this communications server that
                    comprise the LUA pool. LUA LUs are identified by LU name,
                    which is defined in the lu_name field of the DEFINE_LUA
                    verb.

                    Each LU name is a 1- to 8-byte ASCII character string. The
                    ASCII character string must consist of uppercase letters
                    (A-Z), digits (0-9), and the special characters $, #, and
                    @. The character string cannot start with a digit.

                    Each can contain the wildcard characters "?" and "*". The
                    wildcard characters can begin in the first position of the
                    character string. Up to 255 client LU names can be
                    specified.

          description
                    A description of this LUA pool. The string is free format
                    and can be up to 64 ASCII characters long.


ΓòÉΓòÉΓòÉ 9. Management Services Verbs ΓòÉΓòÉΓòÉ

The entry point for the following MS verbs is APPC in APPC.DLL:

 o REGISTER_MS_APPLICATION
 o SEND_MDS_MU
 o UNREGISTER_MS_APPLICATION

 The entry point for the TRANSFER_MS_DATA verb is ACSSVC in ACSSVC.DLL.

 The DOS client entry point for the TRANSFER_MS_DATA verb is ACSSVT TSR.

 Also included at the beginning of this chapter is a description of the
 programming support Communications Manager provides for receiving NMVT request
 units.

   This is the only verb available on the communications client.


ΓòÉΓòÉΓòÉ 9.1. NMVT Receive Support ΓòÉΓòÉΓòÉ

NMVT Receive Support

Communications Manager provides the capability for an NMVT-level application to
register itself in order to receive NMVT RUs. It does so, not by issuing a
verb, but by creating a named OS/2 queue and allocating a named shared segment.

The name of the queue must be "\QUEUES\ACS\SNA\NMVTxxxx" and the name of the
segment must be "\SHARMEM\ACS\SNA\NMVTxxxx", where "xxxx" is 4 characters that
represent the kind of MS major vector the NMVT application wants to receive.
The characters express either a single NMVT major vector key, such as "8090"
for the Request Product Set ID MS major vector, or the characters "SPCI" for
the four Common Operations Services MS major vectors (X'8061' through
X'8064.').

The program must allocate a named shared segment, using DosAllocSeg and
specifying the sharing indicator, to use DosGetShrSeg to acquire access to the
segment. Communications Manager suballocates space from the segment into which
it copies the NMVT RU. Therefore, the program must use DosSubSet to initialize
the segment for suballocation. Communications Manager copies the NMVT into the
suballocated space with the beginning of the NMVT RU (byte 0 of the NMVT RU) at
the beginning of the suballocated space. It is the program's responsibility to
free the suballocated space, using DosSubFree.

The program must create the named queue, using DosCreateQueue and specifying
FIFO queuing. Communications Manager informs the NMVT-level program that it has
copied an NMVT into the segment by issuing the OS/2 function call
DosWriteQueue, specifying on the call a pointer to the suballocated space and
the length of the suballocated space; the length is at least equal to the
length of the NMVT RU, and it may be slightly greater. Storage is suballocated
to contain the data. The amount of storage may be larger than the actual data
passed. Therefore, the length of the suballocated space may be larger than the
RU length contained in the buffer. The amount of RU (NMVT data) actually
contained in the buffer is determined by examining the MS major vector
information within the RU.


ΓòÉΓòÉΓòÉ 9.2. REGISTER_MS_APPLICATION ΓòÉΓòÉΓòÉ

REGISTER_MS_APPLICATION

An MS application program (referred to simply as a program) uses this verb to
register an MS application name with Communications Manager. Once the MS
application name is registered, Communications Manager routes MS data destined
for that MS application name to the program by means of the specified OS/2
queue and data segment. An entry point (EP) program may also request that
Communications Manager pass information to it pertaining to the focal point
(FP) for a specified MS category. This FP information includes the destination
routing information that the program uses to send unsolicited MS requests to
the FP. It also informs the program of status changes to the FP; that is, when
the FP becomes available or unavailable, or when a change to a different FP
occurs for that MS category.

See REGISTER_MS_APPLICATION Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇREGISTER_MS_APPLICATIONΓöÇΓöÇms_application_namenameΓöÇΓöÇms_categorynameΓöÇΓöÇqueue_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                    >ΓöÇΓöÇsegment_selectornΓöÇΓöÇms_fp_applicationΓöÇΓöÇΓö¼ΓöÇNOΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                                         ΓööΓöÇYESΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          ms_application_name
                    Specifies an MS application name. This is the name that is
                    carried in the MDS Routing Information (X'1311') GDS
                    variable within the Multiple Domain Support Message Unit
                    (X'1310') GDS variable, or MDS_MU. Communications Manager
                    uses the MS application name to route MDS_MUs to the
                    program.

          ms_category
                    Specifies an MS category, when the program desires
                    information pertaining to the FP for an MS category. The MS
                    category may be any category that the SNA MS architecture
                    allows, including a user-defined category. Communications
                    Manager passes the FP information to the program by means
                    of an FP notification message. The FP notification message
                    is an MDS_MU containing an MS capabilities (X'80F0') MS
                    major vector with a Focal Point Notification (X'E1') MS
                    subvector and a Focal Point Identification (X'21') MS
                    subvector. Communications Manager passes the MDS_MU to the
                    program using the OS/2 queue and segment specified on this
                    verb, just as it passes other MDS_MUs to the program. After
                    the MS application name is registered, Communications
                    Manager passes the program the FP notification message as
                    soon as the FP becomes available, or immediately following
                    the completion of this verb if the FP is already available.

                    Specify a value of all binary zeros for the MS category
                    name if the program does not need FP information.

                    If YES is specified for the ms_fp_application parameter,
                    the ms_category parameter is required. The MS category name
                    must be the same as the MS application name. The value
                    specified for the ms_category must be the same as the value
                    specified for the ms_application_name parameter. If a
                    remote (higher) FP application is, or becomes, available,
                    Communications Manager passes the local FP application an
                    FP notification message pertaining to the remote (higher)
                    FP. The local FP application is then a nested FP for the MS
                    category.

          queue_name
                    Specifies the name of an OS/2 queue that the program
                    created. Communications Manager uses this queue to notify
                    the program when it has placed an MDS_MU in the specified
                    segment.

          segment_selector
                    Specifies the selector of a sharable, suballocatable data
                    segment in which Communications Manager can place MDS_MUs
                    that it passes to the program. Communications Manager
                    suballocates the segment and places the MDS_MU in the
                    suballocated space. The program is responsible for
                    releasing the suballocated space.

          ms_fp_application
                    Specifies whether the MS application is an FP application.

             NO
                       The MS application is not an FP application.

             YES
                       The MS application is an FP application. The ms_category
                       parameter must also be specified.

 Return Codes

          The OK return code indicates that the REGISTER_MS_APPLICATION verb
          ran successfully.

          REGISTER_MS_APPLICATION Primary and Secondary Return Codes shows the
          primary and secondary error return codes associated with the
          REGISTER_MS_APPLICATION verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      REGISTER_MS_APPLICATION Primary and Secondary Return Codes               Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé MS_APPL_NAME_ALREADY_REGD    Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé QUEUE_NOT_CREATED        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DATA_SEGMENT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MS_FP_APPL       Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MS_CATEGORY_FOR_FP_APPLΓöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          o An MS application name can be registered only once. That is, once
            an MS application name is registered, it cannot be registered
            again, by the same program or a different one, until it is
            unregistered.

          o Prior to issuing the REGISTER_MS_APPLICATION verb, the program must
            create the OS/2 queue that Communications Manager uses to notify
            the program of MDS_MUs it has placed in the segment. The program
            creates the OS/2 queue using the OS/2 function call DosCreateQueue.

            Specify FIFO queuing, and the queue name that the program will use
            on the REGISTER_MS_APPLICATION verb.

          o A program can issue the REGISTER_MS_APPLICATION verb multiple
            times, each time specifying a different MS application name, and
            either the same queue name as on a previous registration, or a
            different queue name. Thus, the program may register multiple
            queues to receive notification for different categories of MS data
            on different queues, or it may register the same queue to receive
            notification for all categories of MS data on one queue.

          o Before closing the queue, the program should unregister the MS
            application name. See UNREGISTER_MS_APPLICATION for more
            information.

          o Prior to issuing the REGISTER_MS_APPLICATION verb, the program must
            allocate the segment it will use to receive MDS_MUs, and then
            specify the selector portion of the segment address on the
            segment_selector parameter. It allocates the segment using the OS/2
            function call DosAllocSeg.

            Specify the sharing indicator so that the segment is shareable with
            DosGiveSeg. This allows Communications Manager to give segment
            addressability to the main task process. Communications Manager
            copies incoming MDS_MUs into the segment while running on the main
            task process.

          o Communications Manager suballocates the specified segment.
            Therefore, the program must initialize the segment for
            suballocation prior to issuing the REGISTER_MS_APPLICATION verb. It
            initializes the segment using DosSubSet.

          o The same segment can be specified on more than one
            REGISTER_MS_APPLICATION verb by the same program (but for different
            MS application names). This allows a program that handles multiple
            categories of MS data to use the same segment for receiving all the
            MDS_MUs across the different categories.

          o Before freeing the segment, the program should unregister the MS
            application name. See UNREGISTER_MS_APPLICATION for more
            information.

          o Multiple programs may share (register) the same segment for
            receiving MDS_MUs. Communications Manager keeps a count of the
            different programs (OS/2 processes) that register the same segment,
            and maintains addressability to the segment as long as at least one
            program using the segment has an MS application name registered.
            Thus, each program may subsequently unregister its MS application
            name (and free the segment) without affecting the use of the
            segment by the other programs.

          o The segment should be large enough to hold all the MDS_MUs that
            could be queued up in the segment waiting for the program to
            process them and free the suballocated segment space. If an MDS_MU
            arrives and insufficient space is available in the segment to hold
            the MDS_MU, Communications Manager sends an MS error message back
            to the originator of the MDS_MU, indicating the MDS_MU could not be
            delivered to the named MS application. If this could happen for the
            category of MS data that the program handles, it should copy the
            MDS_MUs from the shared segment to a private segment and free the
            suballocated space of the shared segment before processing the
            MDS_MUs.

          o If the program specifies an MS category; that is, a nonzero value,
            on the ms_category parameter, and the MSFP for that category is
            already available, Communications Manager passes an FP notification
            message to the program after it posts the REGISTER_MS_APPLICATION
            verb complete. Subsequently, Communications Manager will pass the
            program an FP notification message each time the FP's availability
            status changes or a switch occurs to a different FP for that MS
            category. If the FP is not available when the program registers the
            MS application name, Communications Manager does not pass it an FP
            notification message until the FP becomes available.

            The FP notification message is an MDS_MU containing an MS
            capabilities (X'80F0') MS major vector within a CP-MSU. The MS
            capabilities message contains a Focal Point Notification (X'E1') MS
            subvector and a Focal Point Identification (X'21') MS subvector.
            The Focal Point Notification subvector is two bytes long,
            consisting simply of a length byte and the subvector key (X'E1').

            The Focal Point Identification subvector has the following format,
            in terms of the MS subfields it contains:

             Focal Point Identification (X'21') subvector

                - MS Category (X'01') subfield
                - Focal Point Identification Flags (X'02') subfield
                - Focal Point NETID (X'10') subfield
                - Focal Point NAU Name (X'11') subfield
                - Focal Point Application ID (X'12') subfield

          The MS Category subfield contains the MS category with which this FP
          notification message is associated. The FP NETID, NAU Name, and
          Application ID subfields contain the network ID, CP or LU name, and
          MS application name of the FP for the MS category. The program can
          use this information to build the Destination Location Name (X'82')
          MS subvector in the MDS Routing Information (X'1311') GDS variable of
          unsolicited MDS_MUs it sends to the FP. See "Additional Information"
          for the SEND_MDS_MU verb on topic SEND_MDS_MU for information about
          the format of an MDS_MU.

          The FP Identification Flags subfield includes an indication of
          whether the program should specify default or direct routing on the
          SEND_MDS_MU verbs it issues to send unsolicited MDS_MUs to the FP.
          This routing indicator is bit 15 of the 2-byte Flags field in the
          subfield. Bit 15 of the Flags field is reserved for product use. Its
          definition for Communications Manager is as follows:

                Bit 15    Meaning
                0         Default routing is to be used.
                1         Direct routing is to be used.

          See the description of the mds_mu_routing parameter of the
          SEND_MDS_MU verb on topic SEND_MDS_MU for details about the effect of
          selecting default or direct routing when sending MDS_MUs.

          o When an active MSFP becomes unavailable, Communications Manager
            passes an FP notification message to each program that registered
            an MS application name with the MS category associated with the FP.
            The Focal Point Identification subvector in the FP notification
            message contains empty subfields; that is, all EBCDIC space (X'40')
            characters for the network ID, NAU name, and application ID of the
            FP.

          o Communications Manager supports conversion of incoming NMVTs to
            MDS_MUs. This can occur when the origin node is a type 5 host node
            and the MS data is received from that node over an SSCP-PU session.
            If an NMVT-level program that can receive the NMVT is not running,
            Communications Manager determines whether an MS application name is
            registered that corresponds to the MS major vector key in the NMVT.
            If one is registered, Communications Manager builds an MDS_MU with
            a CP-MSU containing the major vector from the NMVT, and passes the
            MDS_MU to the program that registered the MS application name. This
            capability is intended to allow programs to receive MS data without
            regard to the type of session, CP-CP, LU-LU, or SSCP-PU, on which
            the MS data is received. See Conversion Between MS Data Formats for
            more details about conversion of MS data from one format to
            another.

          o Communications Manager includes two internal MS applications that
            user-written programs cannot register. The internal Communications
            Manager MS application names are:

             EP_ALERT (X'23F0F3F1')
             MS_CAPABILITIES (X'23F0F1F1')

          o The REGISTER_MS_APPLICATION verb is also used to register an MSFP
            application. When both a FP application is registered and a sphere
            of control (SOC) is defined for the MS category, the local node
            sends MS capabilities requests (with X'61' subvector) to establish
            a FP-EP relationship with the EP nodes in the SOC. Unsolicited MS
            requests from the EP nodes in the SOC, for the MS category, are
            routed to the FP application.

          o A FP application may be a nested FP. That is, the network may have
            a higher FP, where the local node is in the SOC of the higher FP.
            The nested FP application may forward MS requests it receives to
            the higher FP, using the SEND_MDS_MU verb.


ΓòÉΓòÉΓòÉ 9.3. SEND_MDS_MU ΓòÉΓòÉΓòÉ

SEND_MDS_MU

An MS application program (referred to simply as a program) uses this verb to
send a Multiple Domain Support Message Unit (X'1310') GDS variable, abbreviated
MDS_MU, to another MS application program and, optionally, to log the MDS_MU in
the FFST/2 error log. The receiving program may be in a remote node or the
local node. It may be a focal point (FP) or entry point program.

The program must supply a complete MDS_MU, containing an MDS Routing
Information (X'1311') GDS variable; an Agent Unit of Work (X'1549') GDS
variable; and an application GDS variable such as a Control Point Management
Services Unit (X'1212') GDS variable, abbreviated CP-MSU, or an SNA Condition
Report (X'1532') GDS variable. The MDS_MU may be an unsolicited request, the
request part of a request/reply, or a reply to a request. The program may also
request that the Date/Time (X'01') MS common subvector or Product Set ID
(X'10') MS common subvector be added to the MS major vector when the
application GDS variable is a CP-MSU.

Communications Manager sends the MDS_MU to the destination specified in the
Destination Location Name (X'82') MS subvector of the MDS Routing Information
GDS variable.

See SEND_MDS_MU Verb Control Block for information on the verb control block
format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇSEND_MDS_MUΓöÇΓöÇproduct_set_id_subvectorΓöÇΓöÇΓö¼ΓöÇADDΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇtime_stamp_subvectorΓöÇΓöÇΓö¼ΓöÇADDΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                          ΓööΓöÇNO_ADDΓöÇΓöÿ             ΓööΓöÇNO_ADDΓöÇΓöÿ
                    >ΓöÇΓöÇmds_mu_routingΓöÇΓöÇΓö¼ΓöÇDEFAULTΓöÇΓö¼ΓöÇΓöÇlocal_loggingΓöÇΓöÇΓö¼ΓöÇLOGΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇoriginator_idnameΓöÇΓöÇdata_lengthnΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                              ΓööΓöÇDIRECTΓöÇΓöÇΓöÿ         ΓööΓöÇNO_LOGΓöÇΓöÿ
                    >ΓöÇΓöÇdata_addraddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          product_set_id_subvector
                    Specifies whether to add the Product Set ID (X'10') MS
                    common subvector to the data the program supplies. The
                    Product Set ID subvector contains the product
                    identification configured for the Communications Manager.
                    You must specify one of the following values:

             ADD
                       Communications Manager adds the Product Set ID subvector
                       to the first (or only) MS major vector in the CP-MSU.
                       ADD should be specified only if the data does not
                       already contain a Product Set ID subvector.

             NO_ADD
                       Communications Manager does not add the Product Set ID
                       subvector.

                    Communications Manager does not automatically add the
                    Product Set ID MS subvector to any MS major vector.
                    Therefore, it is the responsibility of the program to set
                    the product_set_id_subvector parameter appropriately, in
                    accordance with the SNA MS architecture definition for the
                    MS major vector it is supplying.

          time_stamp_subvector
                    Specifies whether to add the Date/Time (X'01') MS common
                    subvector to the data the program supplies. You must
                    specify one of the following values:

             ADD
                       Communications Manager adds the Date/Time subvector to
                       the first (or only) MS major vector in the CP-MSU.

             NO_ADD
                       Communications Manager does not add the Date/Time
                       subvector.

                    Communications Manager does not automatically add the
                    Date/Time MS subvector to any MS major vector. Therefore,
                    it is the responsibility of the program to set the
                    time_stamp_subvector parameter appropriately, in accordance
                    with the SNA MS architecture definition for the MS major
                    vector it is supplying.

          mds_mu_routing
                    Specifies whether Communications Manager is to use default
                    or direct routing to send the MS data to the destination
                    program if the destination program supports the MDS- or
                    migration-level MS architecture; if the destination program
                    supports only the NMVT-level MS architecture, this
                    parameter is not used. The selection of routing applies
                    only when the origin or destination node is an APPN end
                    node (EN). You must specify one of the following values:

             DEFAULT
                       Communications Manager uses default routing. Default
                       routing causes Communications Manager to send the MS
                       data on an LU-LU session if the session already exists
                       to the destination node. Otherwise, Communications
                       Manager sends the MS data on a CP-CP session between an
                       EN and its serving NN (if the origin node is an EN) or
                       between a NN and its served EN (if the destination is an
                       EN). Between two NNs, Communications Manager sends the
                       MS data on an LU-LU session. A CP-CP session uses the
                       CPSVCMG mode name, and an LU-LU session uses the
                       SNASVCMG mode name.

             DIRECT
                       Communications Manager uses direct routing. Direct
                       routing causes Communications Manager to send the MS
                       data on a direct LU-LU session between the origin and
                       destination nodes. See the "Additional Information"
                       under the description of the REGISTER_MS_APPLICATION
                       verb for details about how Communications Manager
                       informs a program of what kind of routing it should use
                       to send unsolicited MS data to a FP node.

          local_logging
                    Specifies whether Communications Manager is to log the
                    MDS_MU in the FFST/2 error log. You must specify one of the
                    following values:

             LOG
                       Communications Manager logs the MDS_MU in the FFST/2
                       error log.

             NO_LOG
                       Communications Manager does not log the MDS_MU in the
                       FFST/2 error log.

          originator_id
                    Specifies the name of the component that issued the
                    SEND_MDS_MU verb. Communications Manager includes this
                    parameter when it logs the data in the FFST/2 error log.
                    However, it does not include the parameter in the MDS_MU
                    sent on the SNA session.

          data_length
                    Specifies the length of the data buffer containing the
                    supplied MDS_MU.

          data_addr
                    Specifies the address of the data buffer containing the
                    supplied MDS_MU. The data buffer must fit completely within
                    a single data segment.

 Return Codes

          The OK return code indicates that the SEND_MDS_MU verb ran
          successfully.

          SEND_MDS_MU Primary and Secondary Return Codes shows the primary and
          secondary error return codes associated with the SEND_MDS_MU verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      SEND_MDS_MU Primary and Secondary Return Codes                     Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_DATA_SEGMENT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_ORIGIN_CP_NAME     Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_FORMAT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_CPMSU_FORMAT   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_FORMAT_PARSE_ERRΓöéRNumeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_LENGTH_FORMAT  Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_NMVT_FORMAT   Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_ROUT_INFO_FORMATΓöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_MDS_MU_UOW_FORMAT    Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé SSCP_PU_SESSION_NOT_ACTIVE   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          o The format of an MDS_MU, in terms of the GDS variables and MS major
            vectors, subvectors, and subfields it contains, is as follows:

             MDS_MU (X'1310') GDS variable

                - MDS Routing Information (X'1311') GDS variable

                   o Origin Location Name (X'81') subvector

                      - NETID (X'01') subfield
                      - NAU Name (X'02') subfield
                      - Application ID (X'03') subfield

                   o Destination Location Name (X'82') subvector

                      - NETID (X'01') subfield
                      - NAU Name (X'02') subfield
                      - Application ID (X'03') subfield

                   o Flags (X'90') subvector

                - Agent_Unit_of_Work (X'1549') GDS variable

                   o Requestor Location Name (X'01') subvector

                      - NETID (X'01') subfield
                      - NAU Name (X'02') subfield

                   o Requestor Agent (X'04') subvector
                   o Sequence Number/Date-Time (X'02') subvector

                - CP-MSU (X'1212') GDS variable with an MS major vector, or
                  SNA Condition Report (X'1532') GDS variable

          Refer to Systems Network Architecture Network Product Formats for a
          detailed definition of the format of an MDS_MU GDS variable.

          o The program uses the SEND_MDS_MU verb to send an MDS request,
            reply, or error message.  An MDS request or reply can consist of
            one or more MDS_MU's.  The first MDS_MU of an MDS request must have
            a new (unique) agent unit of work value. All subsequent MDS_MUs of
            an MDS reply must have the same agent unit of work value; and all
            MDS_MUs of an MDS reply must have the same agent unit of work value
            as the originating MDS request.  Additionally, an MDS error message
            pertaining to an MDS request or reply must have the same agent unit
            of work value as the request or reply.  The same agent unit of work
            value means that the value must be identical in all the related
            MDS_MUs, including blank padding (if any) in the Register Location
            Name (X'01') and Requestor Agent (X'04') subvectors.

          o The program may request that Communications Manager fill in the
            origin NETID and NAU name of the MDS Routing Information (X'1311')
            GDS variable with the NETID and CP name of the local node. To do
            so, the program must supply 8 EBCDIC space (X'40') characters in
            each of the NETID (X'01') and NAU Name (X'02') subfields of the
            Origin Location Name (X'81') subvector.

            The program may also request that Communications Manager fill in
            the requestor location name of the Agent_Unit_of_Work (X'1549') GDS
            variable with the NETID and CP name of the local node; the program
            should request this only when it is the originator of the MS
            transaction. To do so, the program must supply eight EBCDIC space
            characters in each of the NETID (X'01') and NAU Name (X'02')
            subfields of the Requestor Location Name (X'01') subvector.

          o If an error occurs during the sending of the MDS_MU to the
            destination MS application, the error is reported back to the
            origin MS application by means of an MDS_MU error message.
            Therefore, in order for the program to receive this error
            notification, it must register its origin MS application name
            before issuing this SEND_MDS_MU verb.

          o Contrast this verb with TRANSFER_MS_DATA, which an entry point
            program uses to send an alert to an alert FP, as well as send an
            NMVT to a type 5 host node over an SSCP-PU session.

          o The destination program may be located at an APPN node that
            supports receipt of CP-MSUs, but not MDS_MUs. In this case,
            Communications Manager sends only the CP-MSU part of the MDS_MU.

          o The destination program may be located at a type 5 host node that
            supports receipt of MDS_MUs.

          o Communications Manager supports conversion of outgoing MDS_MUs to
            NMVTs. This can occur when the destination node is a type 5 host
            node and the MS data is sent to that node over an SSCP-PU session.
            In this case, Communications Manager builds an NMVT containing the
            MS major vector supplied in the CP-MSU (within the MDS_MU), and
            sends the NMVT on the SSCP-PU session. This capability is intended
            to allow programs to send MS data without regard to what type of
            session, CP-CP, LU-LU or SSCP-PU, is used to transmit the MS data
            to the destination. Refer to Workstation Installation and
            Configuration Guide for more details about conversion of MS data
            from one format to another.

            When the SSCP-PU session is not active, Communications Manager will
            attempt to activate the link to the subarea, and thereby cause the
            SSCP to activate the SSCP-PU session. The link to the type 5 host
            node is the one that is identified by link name as the host link
            during configuration. Communications Manager returns an error
            return code on the SEND_MDS_MU verb indicating the SSCP-PU session
            is not active. The program may then reissue this verb and attempt
            to resend the MDS_MU; however, the program should avoid a sustained
            loop of this retry logic, in the event that the SSCP-PU session
            cannot be activated.

          o The program issuing this verb may be an MSFP program. An FP program
            uses this verb to forward MS requests it receives from MS entry
            points to a remote (higher) FP. In this regard, the local FP
            program is acting as a nested FP. For example, the program may be
            an alert FP program. It uses the SEND_MDS_MU verb to send alerts it
            receives from EP nodes in its sphere of control, and alerts that
            originate at the local node, to the higher FP.

          o The SEND_MDS_MU verb may be used to request APPN topology data or
            APPC accounting data from the local CP. For details of this
            capability, refer to Workstation Installation and Configuration
            Guide.


ΓòÉΓòÉΓòÉ 9.4. TRANSFER_MS_DATA ΓòÉΓòÉΓòÉ

TRANSFER_MS_DATA

This verb sends the supplied management services (MS) data, a CP-CP session, an
LU-LU session, or an 802.2 transport, depending on the type of MS data. The MS
data may be a complete NMVT, Alert subvectors, or user-defined type 2.1 node.
If the MS data is user defined, the data is logged in the FFST/2 error log;
however, the data is not sent outside the local node. When the MS data is an
NMVT, it may contain any MS major vector that SNA permits in an NMVT sent from
a type 2.1 node.

The verb also provides options to request that Communications Manager add the
Product Set ID (X'10') MS subvector, that it log the MS data in the FFST/2
error log, and that it send the data.

See TRANSFER_MS_DATA Verb Control Block for information on the verb control
block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇTRANSFER_MS_DATAΓöÇΓöÇdata_typeΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇNMVTΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Subvector Options Γö£ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
                                     Γöé ΓööΓöÇAlert_SUBVECTORSΓöÇΓöÿ             Γöé
                                     ΓööΓöÇUSER_DEFINEDΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
                    >ΓöÇΓöÇtime_stamp_subvectorΓöÇΓöÇΓö¼ΓöÇADDΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇlocal_loggingΓöÇΓöÇΓö¼ΓöÇLOGΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇoriginator_idnameΓöÇΓöÇdata_lengthnΓöÇΓöÇΓöÇΓöÇ>
                                 ΓööΓöÇNO_ADDΓöÇΓöÿ         ΓööΓöÇNO_LOGΓöÇΓöÿ
                    >ΓöÇΓöÇdata_addraddressΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                    SUBVECTOR OPTIONS:
                    Γö£ΓöÇΓöÇproduct_set_id_subvectorΓöÇΓöÇΓö¼ΓöÇADDΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇsend_on_sessionΓöÇΓöÇΓö¼ΓöÇSENDΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                                   ΓööΓöÇNO_ADDΓöÇΓöÿ          ΓööΓöÇNO_SENDΓöÇΓöÿ

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          data_type
                    The types of MS data the application may supply are as
                    follows:

             NMVT
                       The data contains a complete NMVT request unit,
                       including NMVT bytes 0-7, one or more MS major vectors
                       or part of an MS major vector, and the appropriate MS
                       subvectors for each major vector. If the NMVT contains
                       an alert major vector, Communications Manager logs the
                       Alert in its NMVT format. If the NMVT is to be sent to
                       an MDS- or migration-level FP, Communications Manager
                       converts the NMVT Alert to an MDS-MU or CP-MSU,
                       respectively, before sending it.

             Alert_SUBVECTORS
                       The data contains MS subvectors in the SNA-defined
                       format for an Alert MS major vector. The data does not
                       contain NMVT bytes 0-7 nor the Alert MS major vector
                       header (length and key). Communications Manager adds
                       these in front of the supplied MS subvectors to form the
                       complete NMVT before logging the alert. Communications
                       Manager sets the NMVT flags to indicate the following:

                o The NMVT is unsolicited.
                o The NMVT is the only one for this procedure related
                  identifier (PRID).
                o The NMVT includes the SNA Address List (X'04') MS common
                  subvector, if it is present; otherwise, the NMVT does not
                  include this subvector.

                       Subsequently, if the alert is to be sent to an MDS- or
                       migration-level FP, Communications Manager converts the
                       NMVT Alert to an MDS_MU or CP-MSU, respectively, before
                       sending it.

                       Note:  Alert data is initially routed by FFST/2. FFST/2
                       may be configured to not route alerts (log only), using
                       the 802.2 interface to on-LAN collectors such as IBM LAN
                       Network Manager, or to route alerts through SNA.  If
                       configured to route alerts through SNA to an Alert FP,
                       Communications Manager sends the data on either an
                       SSCP-PU session, a CP-CP session, or an LU-LU session,
                       depending on which type of session Communications
                       Manager uses to transmit alerts to the Alert FP.  If no
                       SNA session is active, Communications Manager inserts
                       the alert on an internal held-Alert queue to await the
                       activation of the session, and initiates activation of
                       the session. An OK return code is indicated on
                       completion of the verb, even if the session is not
                       active, because the alert will be sent when the session
                       becomes active.

             USER_DEFINED
                       The data contains a complete NMVT request unit including
                       NMVT bytes 0-7 and one or more MS major vectors. The MS
                       major vectors (length, key, and included MS subvectors)
                       are user-defined; that is, Communications Manager does
                       not examine them for validity. Communications Manager
                       logs the data but does not send it on any session.

                    For detailed formats of the NMVT RU and MS major vectors
                    and subvectors, refer to Systems Network Architecture
                    Network Product Formats.

          product_set_id_subvector
                    Specifies whether to add the Product Set ID (X'10') MS
                    common subvector to the data the program supplies. This
                    Product Set ID subvector identifies the sender of the MS
                    data. This parameter is ignored if the data_type parameter
                    specifies USER_DEFINED.

             ADD
                       Communications Manager adds the Product Set ID subvector
                       to the first (or only) MS major vector or to the alert
                       subvectors. If the program supplies an Alert MS major
                       vector (or Alert subvectors) containing a Product Set ID
                       subvector, Communications Manager adds the
                       Communications Manager's Product Set ID subvector
                       immediately preceding the existing one. ADD should be
                       specified only if the data does not already contain a
                       Product Set ID subvector, or if it contains a Product
                       Set ID subvector that identifies the origin of an alert
                       where the origin is not the Communications Manager
                       control point.

             NO_ADD
                       Communications Manager does not add the Product Set ID
                       subvector.

                    Communications Manager does not automatically add the
                    Product Set ID MS subvector to any MS major vector.
                    Therefore, it is the responsibility of the program issuing
                    the TRANSFER_MS_DATA verb to set the
                    product_set_id_subvector parameter appropriately, in
                    accordance with the SNA MS architecture definition for the
                    MS major vector (or alert subvectors) it is supplying.

          send_on_session
                    Specifies whether Communications Manager is to send the
                    data on an SNA session. This parameter only applies to
                    non-Alert NMVT data types. User-defined data is never sent
                    on any session.  Alert data is always sent according to
                    FFST/2 Alert routing configuration, together with the
                    availability of SNA Alert transports. You must specify one
                    of the following values:

             NO_SEND
                       Communications Manager does not send the data on any
                       session.

             SEND
                       Communications Manager sends the non-Alert data on the
                       SSCP-PU session if the session is active and either the
                       data is a request, such as the Send Message to Operator
                       (X'006F') MS major vector, or it is a reply to a request
                       received on the SSCP-PU session. If the SSCP-PU session
                       is not active, an error return code is indicated on
                       completion of the verb; in addition, if the logical link
                       to the host system is over a LAN DLC such as the IBM
                       Token-Ring Network, Communications Manager will initiate
                       activation of the session by activating the logical
                       link, causing activation of the SSCP-PU session. In this
                       situation, the program may choose to reissue the verb a
                       short time later, allowing sufficient time for the
                       SSCP-PU session to come up.

                       If the data contains a reply to a request received on a
                       CP-CP session or LU-LU session, Communications Manager
                       sends the data back to the requestor on the same
                       session. An OK return code is indicated on completion of
                       the verb, even if the session is not active. For more
                       details, see "Additional Information" on
                       TRANSFER_MS_DATA.

          time_stamp_subvector
                    Specifies whether to add the Date/Time (X'01') MS common
                    subvector to the data the program supplies. Alert data
                    always gets the Date/Time subvector appended at the end of
                    the first (or only) MS major vector or the end of the alert
                    subvectors, if not already present.

             ADD
                       Communications Manager adds the Date/Time subvector at
                       the end of the first (or only) MS major vector.

             NO_ADD
                       Communications Manager does not add the Date/Time
                       subvector.

                    Communications Manager does not automatically add the
                    Date/Time MS subvector to any MS major vector except
                    alerts. Therefore, it is the responsibility of the program
                    issuing the TRANSFER_MS_DATA verb to set the
                    time_stamp_subvector parameter appropriately, in accordance
                    with the SNA MS architecture definition for the MS major
                    vector it is supplying.

          local_logging
                    Specifies whether Communications Manager is to log the
                    supplied data in the FFST/2 error log. This parameter is
                    used mainly to log non-Alert NMVT data types. User-defined
                    data and alert data are always logged. You must specify one
                    of the following values:

             LOG
                       The data is logged in the FFST/2 error log.

             NO_LOG
                       The data is not logged in the FFST/2 error log.

          originator_id
                    Specifies the name of the component that issued the
                    TRANSFER_MS_DATA verb. Communications Manager includes this
                    parameter when it logs the data in the FFST/2 error log.
                    However, it does not include the parameter in the MS data
                    sent on the SNA session.

          data_length
                    Specifies the length of the data buffer containing the
                    supplied MS data. When the data_type is NMVT or
                    Alert_SUBVECTORS, the data the program supplies, plus NMVT
                    bytes 0-7 and the MS subvectors and subfields
                    Communications Manager may add, must fit in one RU of no
                    greater length than the maximum RU size allowed for the
                    logical link to the host, either 256 or 512. The maximum RU
                    size is specified during configuration of the data link
                    control. (Refer to Workstation Installation and
                    Configuration Guide for information on configuration.) For
                    the data type of USER_DEFINED, the data, plus the Date/Time
                    MS subvector that Communications Manager adds (if any),
                    must be no greater than 512 bytes.

          data_addr
                    Specifies the address of the data buffer containing the
                    supplied MS data. The data buffer must fit completely
                    within a single data segment.

 Return Codes

          The OK return code indicates that the TRANSFER_MS_DATA verb ran
          successfully.

          TRANSFER_MS_DATA Primary and Secondary Return Codes shows the primary
          and secondary error return codes associated with the TRANSFER_MS_DATA
          verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      TRANSFER_MS_DATA Primary and Secondary Return Codes                   Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé INVALID_DATA_TYPE        Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé INVALID_DATA_SEGMENT      Γöé Numeric List of Secondary Return Codes Γöé
                    Γöé             Γöé DATA_EXCEEDS_RU_SIZE      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STATE_CHECK       Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé SSCP_PU_SESSION_NOT_ACTIVE   Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATIONS_MANAGER_ΓöéOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          o Contrast this verb with the SEND_MDS_MU verb. An MS focal point
            (FP) program uses SEND_MDS_MU to send MS data such as alerts to a
            higher (remote) FP program. An MS entry point (EP) program uses
            SEND_MDS_MU to send MS data other than alerts to a destination MS
            application. See the description of the SEND_MDS_MU verb on topic
            SEND_MDS_MU for more details.

          o This TRANSFER_MS_DATA verb is used by EP programs to send MS data
            to a local or remote FP program. The FP node typically has an
            operator that can use this information to manage the network to
            which the local node is connected.

            Specifically, an EP program uses this verb to send:

             - An Alert (X'0000') MS major vector,
             - A Common Operations Services request or reply:

                o A Reply to Execute Command (X'0061') MS major vector,
                o A Reply to Analyze Status (X'0062') MS major vector,
                o A Reply to Query Resource Data (X'0063') MS major vector,
                o A Reply to Test Resource (X'0063') MS major vector, or
                o A Send Message to Operator (X'006F') MS major vector,

             - A Query Product ID (QPI) reply:

                o A Reply Product Set ID (X'0090') MS major vector, or

             - Any other MS major vector allowed in an NMVT sent to a type 5
               host system over the SSCP-PU session.

          o In order to send an NMVT on the SSCP-PU session to the host system,
            the host must activate the session. Activation of an SSCP-PU
            session is requested by specifying YES for the solicit_sscp_session
            parameter of the host link definition.

          o In order to send an NMVT Alert to the host, in addition to defining
            the host link to solicit an SSCP-PU session, the host FP point
            support must be configured.  In order to configure the host FP
            point support correctly, both of the following must be configured:

              1. FFST/2 must be configured to route alerts through SNA by
                 specifying EPWROUT or EPWROUT 1 when initializing the FFST/2
                 Alert router.

              2. Communications Manager must be configured such that the local
                 CP definition specifies YES for the HOST_FP_SUPPORT parameter.

          o If the MS data is sent to a host system on the SSCP-PU session, and
            the local node has a direct SSCP-PU session to the host system, the
            NMVT can contain a single MS major vector, multiple MS major
            vectors, or, if chaining NMVTs for a given procedure related
            identifier (PRID), a portion of an MS major vector. If, however,
            the local node has an indirect SSCP-PU session through an OS/2 SNA
            gateway to the host system, the NMVT must contain a single MS major
            vector, because the SNA gateway supports pass-through of only a
            single MS major vector at a time.

          o Solicited replies, that is, data that contains a reply to a request
            received, is always returned on the same SNA session used for the
            request.  The program issuing the TRANSFER_MS_DATA verb is not
            affected by which format (NMVT, CP-MSU, or MDS-MU) Communications
            Manager uses to send the reply.

          o If the MS data contains a Send Message to Operator MS major vector,
            this data is sent to the current FP for Common Operator Services.
            Again, the program issuing the TRANSFER_MS_DATA verb is not
            affected by the type of SNA session used or the format required to
            send data over this session.  All other non-Alert unsolicited MS
            data is only routed over an SSCP-PU session.

          o An alert notifies a network operator at the Alert FP that a system
            resource is unavailable (or will soon become unavailable) to end
            users. Alerts provide the primary means for a program to
            communicate problem determination information to a network
            operator.

          o Using the TRANSFER_MS_DATA verb, the program supplies an alert in
            either the NMVT form or alert subvector form. An alert supplied in
            NMVT form includes NMVT bytes 0-7 (the NMVT NS header, PRID field,
            and flags) and the Alert MS major vector and its included MS
            subvectors. An alert supplied in alert subvector form does not
            include the leading NMVT bytes 0-7 nor the MS major vector length
            and key fields. When the alert is supplied in subvector form,
            Communications Manager inserts NMVT bytes 0-7 and the Alert MS
            major vector length field and key (X'0000').

            Alert data is initially routed by FFST/2; FFST/2 alert routing is
            configured on a parameter passed when invoking EPWROUT as follows:

             EPWROUT         Defaults to SNA routing
             EPWROUT 0       No routing occurs (log only)
             EPWROUT 1       Specifies SNA routing
             EPWROUT 2       Specifies 802.2 routing

            Note:  If FFST/2 is configured for SNA routing, alert data is sent
            to the current FP for alerts.  The FP may be an NMVT-level host FP,
            a migration-level FP, or an MDS-level FP. The program issuing the
            TRANSFER_MS_DATA verb is not affected by the type of SNA session
            used, or the format required to send data over this session.

          o When the SNA session on which the alert is to be sent is not
            active, the Alert is inserted on an internal "held alert queue".
            When the session is subsequently activated, the alerts on the
            held-alert queue are removed and sent on the session, starting with
            the oldest alert on the queue. The size of the held alert queue is
            a configuration option. If more alerts are generated than the queue
            can hold, the oldest alerts are removed and discarded as the new
            alerts are inserted on the queue.

          o A program can also use the TRANSFER_MS_DATA verb to log
            user-defined data. The data is supplied in NMVT format with a
            user-defined MS major vector, but the data is not sent on any
            session.

          o In most instances, SNA links are automatically brought up as
            needed. (The exception is when the local node's link station role
            for the logical link is strictly secondary.) Activation of a host
            link causes the host system or SNA gateway to activate the SSCP-PU
            session.

            However, if the local node's link station role for the link is
            strictly secondary, and the SSCP-PU session is not active, no
            attempt is made to activate the link. If the link is up for other
            reasons, such as for an LU 6.2 session, or a 3270 emulation
            session, then the host will have already activated the SSCP-PU
            session. But if the link is not being used for other reasons, the
            system administrator at the host node must define the configuration
            appropriately to cause the link and SSCP-PU session to come up when
            Communications Manager is started.

          o FastService also provides interfaces and tools to log errors and
            messages from various customer application programs.

          o For all communications clients, this verb is sent to the server and
            processed.  If there is no server available, the
            SERVER_RESOURCE_NOT_FOUND or SERVER_RESOURCES_LOST return code is
            issued.


ΓòÉΓòÉΓòÉ 9.5. UNREGISTER_MS_APPLICATION ΓòÉΓòÉΓòÉ

UNREGISTER_MS_APPLICATION

An MS application program (referred to simply as a program) uses this verb to
unregister an MS application name. Communications Manager removes the specified
MS application name from its internal MS application program routing list, and
stops sending MDS MUs to the program.

See UNREGISTER_MS_APPLICATION Verb Control Block for information on the verb
control block format.

 Supplied Parameter Syntax

                    >>ΓöÇΓöÇUNREGISTER_MS_APPLICATIONΓöÇΓöÇms_application_namenameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><

                    >>ΓöÇΓöÇreturn_codeΓöÇΓöÇΓö¼ΓöÇOKΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
                             ΓööΓöÇerror codesΓöÇΓöÿ

 Parameters

          ms_application_name
                    Specifies the MS application name that the program
                    registered on a previous REGISTER_MS_APPLICATION verb.

 Return Codes

          The OK return code indicates that the UNREGISTER_MS_APPLICATION verb
          ran successfully.

          UNREGISTER_MS_APPLICATION Primary and Secondary Return Codes shows
          the primary and secondary error return codes associated with the
          UNREGISTER_MS_APPLICATION verb.

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöé      UNREGISTER_MS_APPLICATION Primary and Secondary Return Codes              Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PRIMARY RETURN CODES  Γöé SECONDARY RETURN CODES     Γöé TOPIC                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé PARAMETER_CHECK     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γöé             Γöé MS_APPL_NAME_NOT_REGD      Γöé Numeric List of Secondary Return Codes Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéABENDED             Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé COMMUNICATION_SUBSYSTEMΓöéNOT_LOADED            Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé INVALID_VERB_SEGMENT  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé STACK_TOO_SMALL     Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé UNEXPECTED_DOS_ERROR  Γöé                 Γöé Numeric List of Primary Return Codes  Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 Comments

          o Issue this verb before closing the OS/2 queue and freeing the
            segment.

          o If the program has registered an MS application name, but it ends
            without issuing this verb, Communications Manager performs this
            function as part of its exit processing for the program.

          o If the program registers an MS application name and then ends (that
            is, the OS/2 process for the program ends) without unregistering
            the MS application name, Communications Manager unregisters the MS
            application name on behalf of the program. However, before the
            program ends, it is a good practice for the program to unregister
            all MS application names it has registered.

          o If the program does not finish an active MS transaction before it
            ends, the transaction remains active; that is, Communications
            Manager does not end the transaction. Therefore, the program should
            finish all of its MS transactions before it unregisters the MS
            application name and ends.


ΓòÉΓòÉΓòÉ 10. Return Codes ΓòÉΓòÉΓòÉ

The APPN verbs report various types of information to the programs that issue
the verbs. The information always includes a primary and a secondary return
code that indicates the status of verb execution. A verb that returns a primary
return code of OK executed successfully. Other primary and secondary return
codes provide error information that can help determine and correct problems in
the program code.

This appendix describes the primary and secondary return codes that
Communications Manager provides for all the APPN and system management verbs.
The return codes are listed in the numeric order of their hexadecimal return
code values. Each return code description explains the condition that causes a
return code and recommends a response to take when the return code indicates an
error condition.


ΓòÉΓòÉΓòÉ 10.1. Overview of Return Codes ΓòÉΓòÉΓòÉ

Return codes can help to accomplish the following tasks:

 o Control program flow and execution

 o Provide information to programmers and program testers during program
   development and testing

 o Provide information and guidance to end users of programs

 Programmers can use return codes in transaction programs (TPs) in the
 following ways:

 o A TP should know the state of its conversations and know what input arrives
   from the partner. Return codes can report conversation states.

 o Return codes can report the occurrence and causes of errors. Programmers and
   testers can use that information to accurately report errors and provide
   fixes.

 o The information reported about the occurrence and causes of errors can be
   used to provide appropriate error diagnostics and recovery.


ΓòÉΓòÉΓòÉ 10.2. Using Return Codes Effectively ΓòÉΓòÉΓòÉ

Each return code identifies a unique condition that can occur in a program. For
each verb, establish the following four categories for handling return codes.
Treat the return codes differently by group.

 Group 1: Normal program operation The program should proceed to the next line
           of operation. This should be the condition you expect the program to
           return most of the time.

           Return codes for normal program operation include:

                      0000 OK
                      0009 DEALLOC_NORMAL

 Group 2: Recoverable by the program The program should handle the condition
           because it might occur occasionally. The program should recover
           appropriately and continue.

           The following return codes are recoverable by programs. Many apply
           only to specific verbs.

                      0005 DEALLOC_ABEND
                      0006 DEALLOC_ABEND_PROG
                      0007 DEALLOC_ABEND_SVC
                      0008 DEALLOC_ABEND_TIMER
                      000C PROG_ERROR_NO_TRUNC
                      000D PROG_ERROR_TRUNC
                      000E PROG_ERROR_PURGING
                      0011 SVC_ERROR_NO_TRUNC
                      0012 SVC_ERROR_TRUNC
                      0013 SVC_ERROR_PURGING
                      0017 CNOS_LOCAL_RACE_REJECT
                      0014 UNSUCCESSFUL
                      0018 CNOS_PARTNER_LU_REJECT
                      0021 CANCELLED
                      0040 OPERATION_INCOMPLETE
                      0041 OPERATION_NOT_ACCEPTED
                      0042 CONVERSATION_ENDED
                      0043 ERROR_INDICATION
                      0045 BUFFER_PROVIDED_TOO_SMALL
                      F002 TP_BUSY
                      F013 KEYLOCK_SECURED

           Note:  Although a program can easily recover from a TP_BUSY return
           code, you should not design the transactions in such a way that it
           is an expected condition.
 Group 3: Human intervention A program might need human intervention to run
           successfully.

           The following conditions are the only ones that an end user should
           see. Each return code should provide appropriate information for end
           users. Such information should provide useful directions that an end
           user can follow to correct the condition.

           Examples of this type of return code include:

                      0003 ALLOCATION_ERROR
                      000F CONV_FAILURE_RETRY
                      0010 CONV_FAILURE_NO_RETRY
                      0044 EXP_DATA_NOT_SUPPORTED_BY_LU
                      0046 USER_CONTROL_DATA_NOT_SUPPORTED
                      F003 COMM_SUBSYSTEM_ABENDED
                      F004 COMM_SUBSYSTEM_NOT_LOADED
                      F011 UNEXPECTED_DOS_ERROR
                      F012 COMMUNICATIONS_MANAGER_NOT_LOADED
                      F020 INVALID_KEY
                      F021 X25_ERROR
                      F022 DUMP_STORAGE_ERROR
                      F027 MPTN_MODULE_NOT_LOADED
                      F028 MPTN_NAME_FOUND
                      F029 MPTN_NAME_NOT_FOUND

 Group 4: Unexpected errors End users of an application should be insulated
           from unexpected errors. Recovery from unexpected errors requires at
           least a fix to a program.

           When unexpected errors occur in production, the program should
           produce a detailed log entry for the problem. The log entry (either
           a message log, an error log, or both) should contain enough
           information to allow someone to determine if an error is a code
           defect or a user error. The program should tell the user that the
           program has a defect if the error condition did not result from user
           error. The program should provide sufficient information in the log
           entry to perform problem determination.

           After the program creates a log entry, the program should terminate.
           The conversation in error should also terminate by an attempt to
           issue the [MC_]DEALLOCATE with type(ABEND). This occurs
           automatically if you issue a TP_ENDED verb. If no other threads are
           active, the entire program should terminate.

           Unexpected errors include:

                      0001 PARAMETER_CHECK
                      0002 STATE_CHECK
                      0019 CONVERSATION_TYPE_MIXED
                      0023 CONVERSATION_STYLE_MIXED
                      F008 INVALID_VERB_SEGMENT
                      F015 STACK_TOO_SMALL
                      FFFF INVALID_VERB

           Note:  Some of the STATE_CHECK secondary return codes, such as
           ATTACH_MGR_ALREADY_ACTIVE, indicate recoverable situations, but most
           indicate unexpected errors.


ΓòÉΓòÉΓòÉ 10.3. Primary Return Codes ΓòÉΓòÉΓòÉ

This section contains two lists of APPN primary return codes. The first list is
an alphabetic list. The second list, which begins on page Numeric List of
Primary Return Codes, is a numerical listing. This second list provides
explanations of the return codes and appropriate responses to conditions that
cause these return codes.


ΓòÉΓòÉΓòÉ 10.3.1. Alphabetic List of Primary Return Codes ΓòÉΓòÉΓòÉ

ALLOCATION_ERROR                       0003
BUFFER_PROVIDED_TOO_SMALL              0045
CANCELLED                              0021
CNOS_LOCAL_RACE_REJECT                 0017
CNOS_PARTNER_LU_REJECT                 0018
COMMUNICATION_SUBSYSTEM_ABENDED        F003
COMMUNICATION_SUBSYSTEM_NOT_LOADED     F004
COMMUNICATIONS_MANAGER_NOT_LOADED      F012
CONVERSATION_ENDED                     0042
CONVERSATION_TYPE_MIXED                0019
CONVERSATION_STYLE_MIXED               0023
CONV_FAILURE_NO_RETRY                  0010
CONV_FAILURE_RETRY                     000F
DEALLOC_ABEND                          0005
DEALLOC_ABEND_PROG                     0006
DEALLOC_ABEND_SVC                      0007
DEALLOC_ABEND_TIMER                    0008
DEALLOC_NORMAL                         0009
DUMP_STORAGE_ERROR                     F022
ERROR_INDICATION                       0043
EXP_DATA_NOT_SUPPORTED_BY_LU           0044
INVALID_KEY                            F020
INVALID_VERB                           FFFF
INVALID_VERB_SEGMENT                   F008
KEYLOCK_SECURED                        F013
MPTN_MODULE_NOT_LOADED                 F027
MPTN_NAME_FOUND                        F028
MPTN_NAME_NOT_FOUND                    F029
OK                                     0000
OPERATION_INCOMPLETE                   0040
OPERATION_NOT_ACCEPTED                 0041
PARAMETER_CHECK                        0001
PROG_ERROR_NO_TRUNC                    000C
PROG_ERROR_PURGING                     000E
PROG_ERROR_TRUNC                       000D
SERVER_RESOURCES_LOST                      F026
SERVER_RESOURCE_NOT_FOUND                   F024
STACK_TOO_SMALL                        F015
STATE_CHECK                            0002
SVC_ERROR_NO_TRUNC                     0011
SVC_ERROR_PURGING                      0013
SVC_ERROR_TRUNC                        0012
TP_BUSY                                F002
UNEXPECTED_DOS_ERROR                   F011
UNSUCCESSFUL                           0014
USER_CONTROL_DATA_NOT_SUPPORTED        0046
X25_ERROR                              F021


ΓòÉΓòÉΓòÉ 10.3.2. Numeric List of Primary Return Codes ΓòÉΓòÉΓòÉ

 0000      OK

           Explanation: The verb was executed successfully.

           Programmer Response: No action is required.

 0001      PARAMETER_CHECK

           Explanation: The local program issued a verb that specified a
           parameter with an invalid parameter value. The specific error
           conditions vary with each verb. The secondary return code associated
           with PARAMETER_CHECK indicates the parameter that is in error.

           This error does not indicate a mismatch between the Communications
           Manager configuration and the configuration at the remote location.
           A mismatch between the remote configuration and the local
           configuration would cause an ALLOCATION_ERROR primary return code in
           the program and BIND failures in the local error log.

           Programmer Response: Correct the invalid parameter as indicated by
           the secondary return code.

           A PARAMETER_CHECK indicates a major defect in a program. When a
           program receives this primary return code, the best recovery
           technique is to terminate the program. APPC ExitList processing
           cleans up any active conversations.

           This return code recurs until the local program is changed.

 0002      STATE_CHECK

           Explanation: APPC returns STATE_CHECK for conversation verbs,
           subsystem management verbs, and node definition verbs. This primary
           return code has different meanings that depend on the type of verb
           that was issued.

           For conversation verbs, the local TP issued a verb on a conversation
           that was in a state in which the verb is not allowed.

           A program that is on the error path indicated by this return code
           can use the DISPLAY verb, requesting conversation information, to
           find the current state of this conversation.

           For subsystem management and node definition verbs, STATE_CHECK
           indicates that APPC was not in the correct state to do what the verb
           requests. For example, if the program issues a STOP_AM verb, and the
           attach manager is not active, the program gets a STATE_CHECK with a
           secondary return code of ATTACH_MGR_ALREADY_INACTIVE.

           Programmer Response: Take the action described in the secondary
           return code.

           For conversation verbs, make the local program aware of its current
           state, using information returned by APPC, and issue the verb only
           in a valid state.

           For management verbs, the action that the program is requesting
           might have taken place. So, in some cases, no action is required.

 0003      ALLOCATION_ERROR

           Explanation: APPC could not allocate a conversation with the remote
           TP.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this primary return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK primary return
           code. Take the action described in the secondary return code.

 0005      DEALLOC_ABEND

           Explanation: The source of the error notification is either the
           remote TP or the partner LU. The remote TP can cause this return
           code by issuing an MC_DEALLOCATE verb that specifies the type(ABEND)
           parameter. Alternatively, the partner LU can issue an MC_DEALLOCATE
           verb because of a remote TP ABEND condition.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK return code.
           Check the TP for errors.

 0006      DEALLOC_ABEND_PROG

           Explanation: The remote TP or the partner LU issued a DEALLOCATE
           verb that specified type(ABEND_PROG). If the conversation for the
           remote TP is in the Receive or Pending Post state when the
           DEALLOCATE verb is issued, information sent by the local TP but not
           yet received by the remote TP is not sent to the local TP.

           APPC reports this return code on a verb the program issues in the
           Send, Receive, Pending Post, Send-Receive, or Receive-Only state
           when the remote TP or partner LU deallocates the conversation.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK return code.
           Check the TP for errors.

 0007      DEALLOC_ABEND_SVC

           Explanation: The remote TP or the partner LU issued a DEALLOCATE
           verb that specified type(ABEND_SVC). If the conversation for the
           remote TP is in the Receive or Pending Post state when the
           DEALLOCATE verb is issued, information sent by the local program but
           not yet received by the remote program is purged.

           APPC reports this return code on a verb the program issues in the
           Send, Receive, Pending Post, Send-Receive, or Receive-Only state
           when the remote TP or partner LU deallocates the conversation.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK return code.
           Check the TP for errors.

 0008      DEALLOC_ABEND_TIMER

           Explanation: The remote TP issued a DEALLOCATE verb that specified
           type(ABEND_TIMER). If the conversation for the remote TP is in the
           Receive or Pending Post state when DEALLOCATE is issued, information
           sent by the local TP, but not yet received by the remote TP, is
           purged.

           APPC reports this return code on a verb the TP issues in Send,
           Receive, Pending Post, Send-Receive, or Receive-Only state when the
           remote TP or partner LU deallocates the conversation.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK return code.
           Check the TP for errors.

 0009      DEALLOC_NORMAL

           Explanation: The remote TP issued a DEALLOCATE verb that specified
           type(FLUSH) or type(SYNC_LEVEL) with the synchronization level of
           the conversation specified as NONE.

           APPC reports this return code to the local TP on a subsequent verb
           it issues in the Receive, Pending Post, Send-Receive, or
           Receive-Only state.

           If the conversation style is two-way alternate (half-duplex); or, if
           the conversation style is two-way simultaneous (full-duplex) and the
           conversation state is Receive-Only, the conversation has ended and
           is in the Reset state. A conversation ID (conv_id) was supplied as a
           parameter by the verb that received this return code. That conv_id
           is no longer valid.

           If the conversation style is two-way simultaneous and the
           conversation state is Send-Receive, the conversation state changes
           to Send-Only and APPC does not permit the TP to issue Receive verbs.
           APPC will reject Receive verbs with a STATE_CHECK return code. The
           TP may continue to issue Send verbs until it is ready to end the
           conversation by issuing an [MC_]DEALLOCATE verb.

           Programmer Response: No action is required. This return code does
           not indicate an error.  If the resulting conversation state is
           Reset, APPC has deallocated and cleaned up the conversation.  If the
           program issues any more verbs for this conversation, APPC will
           return the PARAMETER_CHECK return code.

 000C      PROG_ERROR_NO_TRUNC

           Explanation: The remote TP issued a SEND_ERROR verb that specified
           type(PROG) and the conversation for the remote TP was in the Send,
           Send-Receive, or Send-Only state. The SEND_ERROR verb did not
           truncate a logical record. No truncation occurs when a program
           issues a SEND_ERROR verb before it sends any logical records or
           after it sends a complete logical record.

           APPC reports this return code on a RECEIVE verb and the conversation
           remains in the Receive, Send-Receive, or Receive-Only state
           (depending upon the conversation style).

           Programmer Response: Correct the reported error.

 000D      PROG_ERROR_TRUNC

           Explanation: The remote TP issued a SEND_ERROR verb that specified
           the type(PROG) parameter, the conversation for the remote TP was in
           the Send, Send-Receive, or Send-Only state, and the SEND_ERROR verb
           truncated a logical record. Truncation occurs when a program starts
           to send a logical record and then issues a SEND_ERROR verb before it
           sends the complete logical record. APPC reports this return code on
           a receive verb the local TP issues after receiving the truncated
           logical record.

           Programmer Response: Correct the reported error and resend the
           truncated record.

 000E      PROG_ERROR_PURGING

           Explanation: The remote TP issued a SEND_ERROR verb, specifying
           type(PROG) while in Receive, Pending Post, or Confirm state. If the
           remote TP issues a SEND_ERROR verb when it is in the Receive or
           Pending Post state, information sent to but not yet received by the
           remote TP is purged.

           APPC typically reports this return code on a verb the local TP
           issues after it sends information to the remote TP. However, APPC
           can also report this return code on a verb the program issues before
           it sends any information, depending on the verb and when the verb is
           issued. The conversation is in the Receive state.

           Programmer Response: The program should correct the reported error
           and prepare to resend data that might have been lost.

 000F      CONV_FAILURE_RETRY

           Explanation: A temporary failure prematurely ended the conversation.

           Examples of temporary failure conditions follow:

    o The remote machine powered off or restarted during the conversation.

    o The remote machine stopped or unloaded its APPC communications subsystem
      during the conversation.

    o The remote machine deactivated its DLC during the conversation.

    o The local or partner LU deactivated the session in the middle of a
      conversation.

    o The local LU was notified of a session outage occurring in the network.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK return code.

 0010      CONV_FAILURE_NO_RETRY

           Explanation: A permanent failure prematurely ended the conversation.
           Operator intervention is required to correct the problem. This
           return code indicates that the link between the two LUs probably
           failed.

           Examples of permanent failure conditions follow:

    o The local and partner LUs have been disconnected from each other. The
      link or session abruptly terminated.

    o The remote TP at the partner was deactivated while it was running.

    o The remote machine might have violated internal SNA protocols.

           The conversation has ended and is in the Reset state. A conversation
           ID (conv_id) was supplied as a parameter by the verb that received
           this return code. That conv_id is no longer valid.

           Programmer Response: APPC has deallocated and cleaned up the
           conversation. If the program issues any more verbs for this
           conversation, APPC will return the PARAMETER_CHECK return code,
           since the conv_id parameter is no longer valid.

 0011      SVC_ERROR_NO_TRUNC

           Explanation: The remote TP or partner LU issued a SEND_ERROR verb,
           specifying the type(SVC) parameter, the conversation for the remote
           TP was in the Send, Send-Receive, or Send-Only state, and the
           SEND_ERROR verb did not truncate a logical record. No truncation
           occurs when a program issues the verb before it sends any logical
           records or after it sends a complete logical record. APPC reports
           this return code on a Receive verb and the conversation remains in
           the Receive, Send-Receive, or Receive-Only state (depending upon the
           conversation style).

           Programmer Response: Correct the reported error.

 0012      SVC_ERROR_TRUNC

           Explanation: The remote TP or partner LU issued a SEND_ERROR verb,
           specifying type(SVC) while the conversation for the remote TP was in
           the Send, Send-Receive, or Send-Only state, and the SEND_ERROR verb
           truncated a logical record. Truncation occurs if a TP begins sending
           a logical record and the TP or partner LU issues a SEND_ERROR verb
           before a complete logical record is sent. APPC reports this return
           code on a receive verb that the local TP issues after receiving the
           truncated logical record.

           Programmer Response: Correct the reported error and resend the
           truncated record.

 0013      SVC_ERROR_PURGING

           Explanation: The remote TP or partner LU issued a SEND_ERROR verb,
           specifying type(SVC) in Receive, Pending Post, or Confirm state. If
           the remote TP issues a SEND_ERROR verb when it is in the Receive or
           Pending Post state, information sent to, but not yet received by,
           the remote TP is purged.

           APPC typically reports this return code on a verb the local TP
           issues after sending information to the remote TP. However, APPC can
           also report this return code on a verb that the program issues
           before it sends any information, depending on the verb and when the
           verb is issued.

           Programmer Response: The program should check the error and prepare
           to resend data that might have been purged.

 0014      UNSUCCESSFUL

           Explanation: This return code has different meanings, depending on
           whether the verb issued was [MC_]ALLOCATE, [MC_]SEND_CONVERSATION,
           [MC_]RECEIVE_EXPEDITED_DATA, [MC_]RECEIVE_IMMEDIATE, or
           [MC_]TEST_RTS.

    o For [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verbs with
      return_control(IMMEDIATE), APPC could not allocate a contention winner
      session when requested to do so.

    o For an [MC_]RECEIVE_EXPEDITED_DATA verb, there is no expedited data
      available to receive.

    o For an [MC_]RECEIVE_IMMEDIATE verb, there is nothing to receive.

    o For an [MC_]TEST_RTS verb, no REQUEST_TO_SEND indicator was received.

           Programmer Response: No explicit action is required. Retry the verb
           as appropriate.

 0017      CNOS_LOCAL_RACE_REJECT

           Explanation: APPC is currently processing a CNOS verb issued by a
           local LU.

           Programmer Response: Retry the CNOS verb after a short delay.

 0018      CNOS_PARTNER_LU_REJECT

           Explanation: The partner LU rejected a CNOS request from the local
           LU, as indicated by the secondary return code.

           Programmer Response: Take the action described in the secondary
           return code.

 0019      CONVERSATION_TYPE_MIXED

           Explanation: The TP issued both basic and mapped conversation verbs
           on the same conversation.

           Programmer Response: Change the TP so that it issues only
           conversation verbs of the type specified on the [MC_]ALLOCATE verb
           or received on the RECEIVE_ALLOCATE verb.

           This return code recurs until the local program is changed.

 0021      CANCELLED

           Explanation: The Receive function of an [MC_]RECEIVE_AND_POST verb
           was canceled because one of the following verbs was issued:

    o DEALLOCATE with a type of ABEND_PROG, ABEND_SVC, or ABEND_TIMER
    o [MC_]DEALLOCATE with type(ABEND)
    o [MC_]SEND_ERROR
    o TP_ENDED

           Programmer Response: No action is required.

 0023      CONVERSATION_STYLE_MIXED

           Explanation: One of the following errors occurred:

    o The TP issued full duplex conversation verbs; that is, specified a value
      of full duplex in the verb extension code of the verb control block for a
      half duplex conversation.  APPC rejected the verb to prevent a deadlock
      from occurring.
    o The TP issued half duplex conversation verbs for a full duplex
      conversation.  APPC rejected the verb to prevent a deadlock from
      occurring.

           Programmer Response: Change the TP so that it issues only
           conversation verbs of the style specified on the [MC_]ALLOCATE verb
           or received on the RECEIVE_ALLOCATE verb.

           This return code recurs until the local program is changed.

 0040      OPERATION_INCOMPLETE

           Explanation: APPC has not finished processing the nonblocking verb.

           Programmer Response: The program should wait or test for the
           completion of the verb semaphore using an OS/2 function call such as
           DosSemWait or DosMuxSemWait.  If the program has registered
           nonblocking verb completion queues with APPC through the
           REGISTER_NB_QUEUES verb, then it should issue an OS/2 DosReadQueue
           call to be notified when the nonblocking verb completes.

           Do not check the returned parameters, or reuse the semaphore, until
           the verb has been posted.

 0041      OPERATION_NOT_ACCEPTED

           Explanation: APPC rejected the verb; that is, it did not execute the
           verb. The following are some possible reasons for rejection:

    o APPC is currently processing an [MC_]DEALLOCATE specifying type(ABEND).

    o APPC cannot accept any additional queued nonblocking verbs until
      previously queued verbs have completed.

    o APPC has detected a potential deadlock situation with a blocking verb,
      and has rejected the verb to prevent deadlock.

           Programmer Response: The requested verb did not execute.  If the
           program has other nonblocking verbs outstanding, it should wait for
           those verbs to complete, and then issue the rejected verb again.

 0042      CONVERSATION_ENDED

           Explanation: APPC is ending the conversation and the verb has not
           completed. APPC may be ending the conversation normally or it may be
           processing an [MC_]DEALLOCATE specifying type(ABEND).  In either
           case, APPC must post all outstanding expedited data verbs.  For
           example, if there is an outstanding [MC_]RECEIVE_EXPEDITED_DATA verb
           when APPC ends the conversation, APPC posts the verb complete with
           the CONVERSATION_ENDED return code.  No conversation state change
           occurs.

           Programmer Response: The requested verb did not complete execution,
           but no explicit action is required.  The TP should not issue any
           additional verbs for this conversation.

 0043      ERROR_INDICATION

           Explanation: APPC did not execute the full-duplex Send verb because
           a terminating error is pending.  The secondary return code
           associated with ERROR_INDICATION indicates the nature of the
           terminating error.

           If the conversation is in the Send-Receive state, no conversation
           state change occurs, and the actual error is reported to a Receive
           verb.  If the conversation is in the Send-Only state; that is, it
           has already received a DEALLOCATE_NORMAL return code, receipt of the
           ERROR_INDICATION return code ends the conversation and places it in
           the Reset state.

           Examples of terminating errors follow:

    o The remote TP or partner LU issued an [MC_]DEALLOCATE verb specifying
      type(ABEND).

    o The partner LU detected an attach error, and APPC could not allocate a
      conversation with the remote TP.

    o A temporary or permanent failure condition occurred, such as a session
      outage in the network or a violation of internal SNA protocols.

           Programmer Response: The requested verb did not execute, but no
           explicit action is required.  The TP should stop issuing Send verbs
           for this full-duplex conversation.

 0044      EXP_DATA_NOT_SUPPORTED_BY_LU

           Explanation: APPC could not execute the expedited data verb, because
           the partner LU does not support full-duplex conversations and
           expedited data.

           Programmer Response: Do not use expedited data verbs
           ([MC_]SEND_EXPEDITED_DATA and [MC_]RECEIVE_EXPEDITED_DATA) when
           communicating with this partner LU.

 0045      BUFFER_PROVIDED_TOO_SMALL

           Explanation: APPC could not return expedited data, because the size
           of the data buffer as specified by the value for the max_length
           parameter on the [MC_]RECEIVE_EXPEDITED_DATA verb is less than the
           amount of expedited data that APPC has available to receive.

           Programmer Response: The size of the expedited data available to
           receive is returned in the data_length parameter.  Increase the size
           of the data buffer to a value equal to or greater than the  value
           returned in the data_length parameter, and issue the
           [MC_]RECEIVE_EXPEDITED_DATA verb again. This return code recurs
           until the local program is changed.

 0046      USER_CONTROL_DATA_NOT_SUPPORTED

           Explanation: Your program issued an MC_SEND_DATA verb specifying
           user_control_data(YES).  The partner LU does not support user
           control data.  This return code is reported on a subsequent verb.
           Information sent by the MC_SEND_DATA verb has been purged by the
           partner LU.

           Programmer Response: Do not use user control data when communicating
           with this partner LU. This return code recurs until the local
           transaction program is changed.

           You should design your transaction programs (TPs) as a pair.  If
           your TP sends user control data, ensure that the partner LU supports
           user control data, and that the partner TP checks for the
           appropriate what_received values.

 F002      TP_BUSY

           Explanation: APPC did not execute the verb for a TP because APPC was
           processing another verb for that TP on another thread. APPC can
           process only one verb from a given TP at a time. This return code
           can occur if more than one thread of a TP issues verbs using the
           same tp_id.

           Programmer Response: The requested verb did not execute, but no
           explicit action is required. The program can issue the verb again.

 F003      COMM_SUBSYSTEM_ABENDED

           Explanation: A verb was not executed because Communications Manager
           abnormally ended.

           The reason for an abnormal end of APPC is logged in the OS/2 system
           error log. Error log types 0004 and FFFF indicate an abnormal end.

           Programmer Response: Correct the condition that caused the abnormal
           end and restart Communications Manager.

 F004      COMM_SUBSYSTEM_NOT_LOADED

           Explanation: APPC could not execute the verb because Communications
           Manager has not started APPC. Either Communications Manager has not
           been started or has not been configured correctly for the
           application.

           If this return code is encountered, it will probably be on the first
           API verb issued by a program. Your program should explicitly check
           for this return code on the first API verb it issues.

           Programmer Response: Issue a CmkKernelReg command to load
           Communications Manager.

 F008      INVALID_VERB_SEGMENT

           Explanation: APPC could not process the verb for one of the
           following reasons:

    o APPC could not process the verb because the verb is truncated at the end
      of the data segment that contains the verb. That is, the verb control
      block is larger than the number of bytes between the start of the verb
      and the end of the segment.

    o The TP issued this verb as a nonblocking verb and APPC was unable to gain
      shared access to the segment containing the verb control block.

           Programmer Response:

    o Check the 4-byte verb control block pointer that was passed to APPC; the
      pointer might not point to the beginning of the verb control block.

    o Ensure that the program uses a read-write data segment large enough to
      contain the entire verb structure.

    o If the verb is nonblocking, ensure that the entire verb control block
      resides in an shared, unnamed segment

           This return code recurs until the local program is changed.

 F011      UNEXPECTED_DOS_ERROR

           Explanation: If an unexpected OS/2 return code is encountered when
           APPC internally makes an OS/2 function call, the verb is posted with
           primary return code UNEXPECTED_DOS_ERROR.

           The secondary return code contains the unexpected OS/2 return code.
           An occurrence of this error might cause APPC to abnormally end; look
           at the OS/2 system error log for more information. This return code
           usually indicates that all the OS/2 resources of some type have been
           consumed; for example, there is no more hard disk space available
           for swapping.

           The hexadecimal representation of the return code is stored in the
           secondary return code in Intel byte-swapped order. The following
           explains the format of the secondary return code:

     " An invalid queue handle error is unexpectedly returned to APPC by the
     base operating system. This return code has a decimal value of 337, which
     is X'151'. Thus, the secondary return code returned to the program by APPC
     is 51010000. "

 Programmer Response: Look at the secondary return code to find the OS/2 return
 code.

 F012      COMMUNICATIONS_MANAGER_NOT_LOADED

           Explanation: APPC could not execute the verb because Communications
           Manager has not been started.

           Programmer Response: The program should explicitly check for this
           return code on the first common services verb it issues. When this
           return code is returned to the program, issue a CmkKernelReg command
           to start Communications Manager.

 F013      KEYLOCK_SECURED

           Explanation: The trace request was rejected because the keylock was
           on and no key name or an invalid key name was specified in the key
           parameter. This return code is maintained for migration purposes
           only. It is not used for verbs that contain the key supplied
           parameter.

           Programmer Response: Ensure that the program supplied a valid master
           or service key. If appropriate, accept this key as a command line
           input parameter.

 F015      STACK_TOO_SMALL

           Explanation: APPC requires a minimum stack size of 3.5 kilobytes
           (3500 bytes) when a verb is issued. APPC runs on the stack of the
           program that calls it. When the verb was issued, APPC found the
           stack size to be too small.

           Programmer Response:

           Relink the program as required, enlarging the stack, and retry the
           program.

 F020      INVALID_KEY

           Explanation: The supplied key was incorrect.

           User Response: Find the current master or service key, and issue the
           verb again with a valid key. This assumes that the key is a
           parameter on the program.

 F021      X25_ERROR

           Explanation: While using the DISPLAY verb to find X.25 physical link
           information, X.25 encountered an error. The secondary return code
           contains the unexpected X.25 return code.

           The hexadecimal representation of the X.25 return code is stored in
           the CSPI secondary return code in Intel byte-swapped order. The
           format of the secondary return code is shown in the following
           example:

     " An X.25 inactive error is unexpectedly returned to CSPI on the DISPLAY
     verb. This return code has a decimal value of 102, which is X'66'. Thus,
     the secondary return code returned to your program by CSPI is 66000000. "

 Programmer Response: Look at the secondary return code to find the OS/2 return
 code.

 F022      DUMP_STORAGE_ERROR

           Explanation: An internal error occurred while dumping components 1
           through 5, 9 through 11, 17, or 18. The error code is contained in
           the leftmost two bytes of the secondary return code. The dump data
           might be incomplete.

           Programmer Response: When this return code is returned to the
           program, you should inform the user retry the program. If the
           problem persists, report the error code to your service
           representative.

 F024      SERVER_RESOURCE_NOT_FOUND

           Explanation: No communication server was found which could provide
           the requested function, or no server was found which would provide
           this service to this machine and/or user name.

           Programmer Response: One of the following may resolve this problem:

     1. Verify that the communications server is active.
     2. Ensure that the connectivity to the server is active.
     3. Check the access definitions at the server for this client and user id.

 F026      SERVER_RESOURCES_LOST

           Explanation: The communications server which was providing the
           function was lost due to a connection failure.

           Programmer Response:

     1. Verify that the communications server is active.
     2. Check the connectivity to the server.

 F027      MPTN_MODULE_NOT_LOADED

           Explanation: This code is returned by the PLU_TAB_OP verb when it is
           called and MPTN (AnyNet) is not loaded.

           Programmer Response: None.

 F028      MPTN_NAME_FOUND

           Explanation: This code is returned by the PLU_TAB_OP verb on an add
           or lookup option when the given name is found in the preference
           table or the default value of the preference table is returned.

           Programmer Response: None.  The name is already in the table.

 F029      MPTN_NAME_NOT_FOUND

           Explanation: This code is returned by the PLU_TAB_OP verb on an add,
           remove, or lookup option when the given name is not found in the
           preference table.

           Programmer Response: None.  The name is added to the table.

 FFFF      INVALID_VERB

           Explanation: APPC did not recognize the supplied verb operation code
           and did not execute the verb.

           Either the local program specified an incorrect verb operation code
           or it called the incorrect entry point. For example, this return
           code can occur when the common services entry point (ACSSVC) is
           called with an APPC verb.

           Programmer Response: Correct the verb operation code or the entry
           point being called.

           This return code recurs until the local program is changed.


ΓòÉΓòÉΓòÉ 10.4. Secondary Return Codes ΓòÉΓòÉΓòÉ

This section contains two lists of the APPN and APPC verb secondary return
codes. The first list is an alphabetic list. The second list, which begins on
page Numeric List of Secondary Return Codes, is a numerical listing of the
secondary return codes. This second list provides explanations of the return
codes and appropriate responses to take when you encounter these return codes.


ΓòÉΓòÉΓòÉ 10.4.1. Alphabetic List of Secondary Return Codes ΓòÉΓòÉΓòÉ

ACTIVATE_SAP_FAILURE                        00000287
ADAPTER_NOT_DEFD                            000001D5
ADAPTER_NOT_OPEN                            000002B3
ALLOCATION_ERROR_PENDING                    00030000
ALLOCATE_NOT_PENDING                        00000509
ALLOCATION_FAILURE_NO_RETRY                 00000004
ALLOCATION_FAILURE_RETRY                    00000005
ALL_MODE_MUST_RESET                         00000153
ATTACH_MGR_ALREADY_ACTIVE                   0000050A
ATTACH_MGR_ALREADY_INACTIVE                 00000508
AUTOACT_EXCEEDS_SESSLIM                     00000152
BAD_COMPRESSION_LEVEL                       000002CA
BAD_COMPRESSION_NEED                        00000227
BAD_COMPRESSION_TOKENS                      000002CB
BAD_CONV_ID                                 00000002
BAD_CONV_STYLE                              00000022
BAD_CONV_TYPE                               00000011
BAD_DIR_COMPRESSION                         00000228
BAD_ERROR_DIRECTION                         00000105
BAD_LL                                      000000F1
BAD_LOCAL_NODE_NN_SERVER                    000002D7
BAD_LU_ALIAS                                00000003
BAD_LU_NAME                                 000002E4
BAD_PARTNER_LU_ALIAS                        0000015B
BAD_RETURN_CONTROL                          00000014
BAD_RETURN_STATUS_WITH_DATA                 000000D7
BAD_SECURITY                                00000013
BAD_SNASVCMG_LIMITS                         00000154
BAD_SYNC_LEVEL                              00000012
BAD_TP_ID                                   00000001
BAD_TYPE                                    00000250
CACHE_NOT_ALLOWED_EN                        000002DF
CANT_ALLOCATE_SHARED_SEGMENT                00000705
CANT_RAISE_LIMITS                           00000151
CHANGE_SRC_DRAINS                           0000015D
CNOS_ACCEPTED                               00000000
CNOS_COMMAND_RACE_REJECT                    0000015F
CNOS_IMPLICIT_PARALLEL                      00000150
CNOS_MODE_CLOSED                            00000156
CNOS_MODE_NAME_REJECT                       00000157
CNOS_NEGOTIATED                             00000007
CONFIRMED_BAD_STATE                         00000041
CONFIRM_BAD_STATE                           00000032
CONFIRM_INVALID_FOR_FDX                     00000034
CONFIRMED_INVALID_FOR_FDX                   00000042
CONFIRM_NOT_LL_BDY                          00000033
CONFIRM_ON_SYNC_LEVEL_NONE                  00000031
CONV_FAILURE_NO_RETRY_PENDING               00100000
CONV_FAILURE_RETRY_PENDING                  000F0000
CONVERSATION_TYPE_MISMATCH                  10086034
COS_NAME_NOT_DEFD                           00000810
COS_NOT_DEFD                                0000021B
CPSVCMG_ALREADY_DEFD                        00000221
CPSVCMG_MODE_NOT_ALLOWED                    00000519
CPSVCMG_SESSION_ACTIVE                      000001FF
CP_OR_SNA_SVCMG_UNDELETABLE                 000001F3
DATA_EXCEEDS_RU_SIZE                        00000302
DEACT_CG_INVALID_CGID                       0000026C
DEACT_CG_INVALID_TYPE                       0000026B
DEACT_DLC_ADAPTER_NOT_OPEN                  00000200
DEACT_LINK_UNSUCCESSFUL                     00000517
DEALLOC_ABEND_PENDING                       00050000
DEALLOC_ABEND_PROG_PENDING                  00060000
DEALLOC_ABEND_SVC_PENDING                   00070000
DEALLOC_ABEND_TIMER_PENDING                 00080000
DEALLOC_BAD_TYPE                            00000051
DEALLOC_CONFIRM_BAD_STATE                   00000053
DEALLOC_FLUSH_BAD_STATE                     00000052
DEALLOC_LOG_LL_WRONG                        00000057
DEALLOC_NOT_LL_BDY                          00000055
DEF_COS_INVALID_SECURITY                    00000807
DEF_GW_BAD_HOST_LINKNAME                    00000202
DEF_GW_DUP_HSNAU                            00000203
DEF_GW_HOST_INV_TIMER                       00000208
DEF_GW_INV_NAU_ADR                          00000207
DEF_GW_INV_NAME                             00000209
DEF_GW_WKS_BAD_WKS_LINKNAME                 0000020B
DEF_GW_WKS_DUP_LUNAME                       00000205
DEF_GW_WKS_DUP_WSNAU                        00000204
DEF_GW_WKS_INV_DLC_NAME                     0000020A
DEF_GW_WKS_INV_POOL_CLASS                   00000206
DEF_LINK_BAD_NODE_TYPE                      000001CB
DEF_LINK_INVALID_SECURITY                   00000822
DEF_LU_LU_PW_SESS_ACTIVE                    00000852
DEF_PLU_INVALID_FQ_NAME                     00000274
DEFAULT_SOC_DISALLOWED_ON_EN                00000860
DEL_LOCAL_DEPENDENT_LU                      00000223
DEL_MODE_DEFAULT_SPCD                       000001F4
DEST_ADDR_EQUALS_OWN_ADDR                   000001DF
DISPLAY_INFO_EXCEEDS_LEN                    000001B4
DISPLAY_INVALID_CONSTANT                    000001B5
DLC_FAILURE                                 00000283
DLC_NOT_DEFD                                000001C6
DUPLICATE_LU_NAME                           000002E0
DUPLICATE_DLC                               00000286
DUPLICATE_LINK_NAME                         000001C0
DUPLICATE_LU_ALIAS                          00000211
DUPLICATE_PARTNER_LU_ALIAS                  00000277
EXCEEDS_MAX_ALLOWED                         0000015C
EXPD_BAD_RETURN_CONTROL                     00000126
EXPLICIT_SOC_DISALLOWED_ON_EN               00000863
FDX_NOT_SUPPORTED_BY_LU                     00000023
FLUSH_NOT_SEND_STATE                        00000061
FQPLU_NAME_EQ_LCL                           000002D8
FQPLU_NAME_NOT_DEFD                         000001F8
FQ_OWNING_CP_NAME_EQ_LCL                    000002DE
FQ_SERVING_NNCP_NAME_EQ_LCL                 000002D9
HOST_LINK_NAME                              000001FB
HOST_LINK_NAME_NOT_DEFINED                  00000269
INCONSISTENT_TP_OPERATION                   000002A7
INVALID_ADAPTER                             00000516
INVALID_ALIAS                               0000020F
INVALID_AUTO_ACTIVATE                       000001CD
INVALID_BYTE_COST                           000001D1
INVALID_CNOS_SLIM                           00000217
INVALID_CN_NAME                             00000821
INVALID_CONGESTION                          00000806
INVALID_CONVERSATION_TYPE                   000002A1
INVALID_CONV_SECURITY_RQD                   000002A2
INVALID_CONV_SECURITY_VERIF                 00000276
INVALID_COS_NAME                            00000801
INVALID_COS_SNASVCMG_MODE                   0000021C
INVALID_CP_CP_SUPPORT                       000001CC
INVALID_CP_NAME                             000001CA
INVALID_CP_NAU_ADDRESS                      000002C5
INVALID_DATA_SEGMENT                        00000006
INVALID_DATA_TYPE                           00000303
INVALID_DEFAULT_BACKUP_FP_CP_NAME           00000862
INVALID_DEFAULT_BACKUP_FP_INDICATOR         00000861
INVALID_DEST_ADDR_LEN                       000001D3
INVALID_DIRECTION                           00000401
INVALID_DIR_FOR_ATTACHES                    00000267
INVALID_DLC                                 00000510
INVALID_EFFECTIVE_CAPACITY                  00000824
INVALID_EXPLICIT_BACKUP_FP_CP_NAME          00000862
INVALID_EXPLICIT_BACKUP_FP_INDICATOR        00000864
INVALID_FIRST_CHARACTER                     00000404
INVALID_FQLU_NAME                           000001FD
INVALID_FQPLU_NAME                          000002DA
INVALID_FP_SUPPORT                          00000225
INVALID_FQ_CP_NAME                          000002C3
INVALID_FQ_OWNING_CP_NAME                   000002DB
INVALID_FQ_SERVING_NNCP_NAME                000002DD
INVALID_HOST_LINK_NAME                      00000226
INVALID_IMPLICIT_PLU_SUPP                   00000262
INVALID_LIMITED_RESOURCE                    000001CE
INVALID_LINK_NAME                           0000050F
INVALID_LINK_NAME                           000002E3
INVALID_LINK_NAME                           000001C1
INVALID_LINK_NAME_SPECIFIED                 000002B0
INVALID_LS_ROLE                             000001D2
INVALID_LU_NAME                             00000210
INVALID_LU_NAU_ADDRESS                      0000020E
INVALID_MAX_MC_LL_SEND_SIZE                 00000275
INVALID_MAX_NEGOT_SESS_LIM                  00000214
INVALID_MAX_RU_SIZE_UPPER                   00000219
INVALID_MAX_TIMES_CONSIDERED                00000224
INVALID_MDS_MU_CPMSU_FORMAT                 00000850
INVALID_MDS_MU_FORMAT_PARSE_ERROR           00000851
INVALID_MDS_MU_LENGTH_FORMAT                00000849
INVALID_MDS_MU_FORMAT                       00000846
INVALID_MDS_MU_NMVT_FORMAT                  00000853
INVALID_MDS_MU_ROUT_INFO_FORMAT             00000845
INVALID_MDS_MU_UOW_FORMAT                   00000848
INVALID_MIN_CONWINNERS                      0000021E
INVALID_MODE                                00000515
INVALID_MODE_NAME                           00000215
INVALID_MODE_SESSION_LIMIT                  00000218
INVALID_NODE_TYPE                           000002C4
INVALID_MS_CATEGORY_FOR_FP_APPL             00000843
INVALID_MS_FP_APPL                          00000842
INVALID_NAU_ADDRESS                         000002E2
INVALID_NUMBER_OF_ADAPTERS                  00000828
INVALID_NUMBER_OF_NODE_ROWS                 00000802
INVALID_NUMBER_OF_REMOTE_BACKUP_FPS         0000086E
INVALID_NUMBER_OF_SOC_NODES                 00000866
INVALID_NUMBER_OF_TG_ROWS                   00000809
INVALID_NUM_LINKS_SPECIFIED                 000002B2
INVALID_ORIGIN_CP_NAME                      00000847
INVALID_OUTGOING_CALL_DIRECTORY_ENTRY_NAME  000001DD
INVALID_PARALLEL_SESS_SUPP                  0000027A
INVALID_PARTNER_LU_NAME                     00000514
INVALID_PASSWORD                            00000291
INVALID_PREF_NN_SERVER                      000001DB
INVALID_PROCESS                             00000525
INVALID_PROGRAM_TYPE                        000002A5
INVALID_PROPAGATION_DELAY                   00000823
INVALID_PU_NAME                             000001D4
INVALID_QUEUE_ALLOC_TIMEOUT                 000002AC
INVALID_QUEUE_DEPTH                         000002AB
INVALID_RECV_PACING_WINDOW                  00000216
INVALID_REMOTE_BACKUP_FP_CP_NAME            0000086F
INVALID_REMOTE_PRIMARY_FP_CP_NAME           0000086C
INVALID_RESERVED_FIELD                      000001D0
INVALID_RU_SIZES                            00000213
INVALID_SEMAPHORE_HANDLE                    000000D6
INVALID_SESSION_ID                          00000512
INVALID_SNASVCMG_MODE_LIMITS                0000021A
INVALID_SOC_NODE_CP_NAME                    00000867
INVALID_SOLICIT_SSCP                        000001CF
INVALID_SYNC_LEVEL                          000002A3
INVALID_TIME_COST                           000001D6
INVALID_TP_NAME                             000002A0
INVALID_TP_OPERATION                        000002A4
INVALID_TP_RECEIVE_TIMEOUT                  000002AD
INVALID_TYPE                                00000511
INVALID_UNINT_PLU_NAME                      0000027C
INVALID_USER_DEF_1                          000001C3
INVALID_USER_DEF_2                          000001C4
INVALID_USER_DEF_3                          000001C5
INVALID_USER_ID                             00000290
INVALID_WILDCARD_ENTRY                      000002DC
INVALID_X25_ADAPTER_NAME                    0D000000
INVALID_X25_LINK_NAME                       03000000
LINK_IS_ACTIVE                              000001DA
LINK_DEACT_IN_PROGRESS                      0000050D
LINK_NAME_REDEFINITION                      000002E6
LINK_NOT_DEFD                               000001FA
LOCAL_CP_ALREADY_DEFD                       00000201
LOCAL_CP_NAME                               000001D7
LOCAL_LU_NAME_EQ_PLU_NAME                   0000020D
LU_DETACHED                                 0000015E
LU_NAME_NOT_DEFD                            000001F9
LU_NAME_SAME_AS_CP_NAME                     000001F7
LU_NAU_ADDRESS_ALREADY_DEFD                 00000212
LU_TYPE_REDEFINITION                        000002E7
MAX_VALUE_LESS_THAN_MIN                     00000803
MIN_GT_TOTAL                                00000155
MODE_CLOSED                                 00000156
MODE_NAME_NOT_DEFD                          000001F5
MODE_SESS_LIM_EXCEEDS_NEG                   00000220
MS_APPL_NAME_ALREADY_REGD                   00000840
MS_APPL_NAME_NOT_REGD                       00000844
MS_CATEGORY_DOES_NOT_EXIST                  00000871
NEW_LINK_NAME_EXISTING_DA                   000001D9
NAU_REDEFINITION                            000002E5
NN_SERVER_FAILURE                           000002B5
NN_SERVER_TIMEOUT                           000002B4
NODE_ROW_WGT_LESS_THAN_LAST                 00000804
NON_UNIQUE_NAU_ADDRESS                      000002E1
NO_CP_DEFD                                  00000008
NO_LINKS_DEFD_AS_AUTO_ACTIVE                000002B1
NO_USE_OF_SNASVCMG                          00000017
NO_USE_OF_SNASVCMG_CPSVCMG                  00000017
NO_SOC_DEFINED_FOR_MS_CATEGORY              00000869
NO_SOC_EXISTS_FOR_MS_CATEGORY               0000086B
OK                                          00000000
PIP_LEN_INCORRECT                           00000016
PIP_NOT_ALLOWED                             10086031
PIP_NOT_SPECIFIED_CORRECTLY                 10086032
PLU_LOCATION_NOT_DEFD                       000001FE
PLU_NAME_EQ_LOCAL_LU_NAME                   00000279
P_TO_R_INVALID_FOR_FDX                      000000A5
P_TO_R_INVALID_TYPE                         000000A1
P_TO_R_NOT_LL_BDY                           000000A2
P_TO_R_NOT_SEND_STATE                       000000A3
QUEUE_NOT_CREATED                           00000841
RCV_AND_POST_BAD_FILL                       000000D5
RCV_AND_POST_BAD_STATE                      000000D1
RCV_AND_POST_NOT_LL_BDY                     000000D2
RCV_AND_WAIT_BAD_FILL                       000000B5
RCV_AND_WAIT_BAD_STATE                      000000B1
RCV_AND_WAIT_NOT_LL_BDY                     000000B2
RCV_IMMD_BAD_FILL                           000000C4
RCV_IMMD_BAD_STATE                          000000C1
RECEIVE_EXPD_INVALID_LENGTH                 00000125
REMOTE_BACKUP_FP_NAME_IS_FOCAL_CP           00000870
REMOTE_PRIMARY_FP_NAME_IS_FOCAL_CP          0000086D
RESERVED_FIELD_NOT_ZERO                     000002E8
RESET_SNA_DRAINS                            00000159
R_T_S_BAD_STATE                             000000E1
R_T_S_INVALID_FOR_FDX                       000000E2
SAME_LINK_NAME_DIFF_DA                      000001D8
SECURITY_NOT_VALID                          080F6051
SEND_DATA_BAD_USER_CONTROL_DATA             000000F8
SEND_DATA_CONFIRM_ON_SYNC_NONE              000000F5
SEND_DATA_INVALID_TYPE                      000000F4
SEND_DATA_NOT_LL_BDY                        000000F6
SEND_DATA_NOT_SEND_STATE                    000000F2
SEND_ERROR_BAD_STATE                        00000104
SEND_ERROR_BAD_TYPE                         00000103
SEND_ERROR_LOG_LL_WRONG                     00000102
SEND_EXPD_INVALID_LENGTH                    00000124
SEND_TYPE_INVALID_FOR_FDX                   000000F7
SINGLE_NOT_SRC_RESP                         0000015A
SNASVCMG_RESET_NOT_ALLOWED                  00000167
SNA_DEFD_COS_CANT_BE_CHANGED                0000080A
SNA_DEFD_COS_CANT_BE_DELETED                00000811
SOC_FOR_MS_CATEGORY_NOT_DEFAULT             0000086A
SOC_NODE_CMP_NAME_IS_LOCAL_CP               00000868
SSCP_PU_SESSION_NOT_ACTIVE                  00000301
SYNC_LEVEL_NOT_SUPPORTED                    10086041
TABLE_ERROR                                 00000405
TEST_INVALID_FOR_FDX                        00000123
TG_ROW_WGT_LESS_THAN_LAST                   00000805
TP_ALREADY_ACTIVE                           000002A8
TP_NAME_NOT_RECOGNIZED                      10086021
TRANS_PGM_NOT_AVAIL_NO_RETRY                084C0000
TRANS_PGM_NOT_AVAIL_RETRY                   084B6031
UNDEFINED_TP_NAME                           00000506
UNINT_PLU_NAME_DEFD                         00000278
UNKNOWN_ERROR_TYPE_PENDING                  00110000
UNKNOWN_PARTNER_MODE                        00000018
UNRECOGNIZED_DEACT_TYPE                     0000050E
USERID_NOT_DEFD                             00000292
VERB_LENGTH_INVALID                         000002E9
X25_ABEND                                   63000000
X25_ADAPTER_ACCESS_ERROR                    71000000
X25_ADAPTER_ERROR                           72000000
X25_COMMS_SERVICES_ERROR                    E5030000
X25_DEVICE_DRIVER_ERROR                     6F000000
X25_DIRENTRY_NOT_FOUND                      000001DC
X25_INACTIVE                                66000000
X25_INSUFFICIENT_RESOURCE                   6C000000
X25_INVALID_LINK_NAME                       73000000
X25_INVALID_STATE                           E4030000
X25_LINK_IN_AUTOCONNECT_MODE                78000000
X25_LINK_IN_CONNECT_MODE                    76000000
X25_LINK_IN_DISCONNECT_MODE                 77000000
X25_LINK__ERROR_LEVEL_1                     7A000000
X25_LINK__ERROR_LEVEL_2                     7B000000
X25_TERMINATING                             69000000
X25_UNEXPECTED_OS2_ERROR                    62000000


ΓòÉΓòÉΓòÉ 10.4.2. Numeric List of Secondary Return Codes ΓòÉΓòÉΓòÉ

 00000000  OK

           Explanation: Examine the primary return code. Most primary return
           codes have a secondary return code of 00000000, even when the
           primary return code indicates an error.

           If the primary return code is OK, APPC executed the verb
           successfully.

           Programmer Response: No action is required.

 00000000  CNOS_ACCEPTED

           Explanation: APPC accepts the session limits and responsibility as
           specified.

           Programmer Response: No action is required.

 00000001  BAD_TP_ID

           Explanation: APPC does not recognize the specified tp_id parameter.
           Either the wrong tp_id was supplied on the verb, the TP has already
           terminated, or the verb was not issued in the OS/2 process where the
           tp_id was originally obtained. Some possible causes for this error
           are:

    o The program never issued a TP_STARTED or RECEIVE_ALLOCATE verb.
    o The program issued a TP_STARTED or RECEIVE_ALLOCATE verb, but APPC
      replied with a return code other than OK on that verb.
    o The tp_id returned by the TP_STARTED or RECEIVE_ALLOCATE verb was not
      copied correctly into the verb control block for the current verb.
    o The program issued a successful TP_ENDED verb that invalidates the tp_id.

           Programmer Response: If the TP has not ended, issue the verb again
           with the correct tp_id.

 00000002  BAD_CONV_ID

           Explanation: APPC does not recognize the specified conv_id
           parameter. Some possible causes for this error are:

    o The program never issued an [MC_]ALLOCATE verb.
    o The program issued a [MC_]ALLOCATE verb, but APPC replied with a return
      code other than OK on that verb.
    o An earlier conversation verb, issued for this conversation, received a
      return code other than OK, and ended the conversation.
    o The conv_id returned by the [MC_]ALLOCATE or RECEIVE_ALLOCATE verb was
      not copied correctly into the verb control block for the current verb.
    o The program issued a successful [MC_]DEALLOCATE verb that invalidates the
      conv_id.

           Programmer Response: If the conversation has not ended, issue the
           verb again with the correct conv_id.

 00000003  BAD_LU_ALIAS

           Explanation: APPC cannot find the specified lu_alias among those
           defined.

           This return code recurs until either the local program or the local
           configuration is changed.

 00000004  ALLOCATION_FAILURE_NO_RETRY

           Explanation: APPC returns this return code when it has determined
           that it is impossible to allocate a conversation without human
           intervention. For example, APPC can tell when there is no adapter in
           the local workstation.

           If there is any possibility that a conversation might be
           established, APPC responds with the ALLOCATION_FAILURE_RETRY return
           code (00000005). For example, APPC cannot detect whether there is an
           adapter in the remote workstation, so APPC keeps trying to establish
           a conversation by simply retrying the [MC_]ALLOCATE or
           [MC_]SEND_CONVERSATION verb.

           The retry is justified because typically in production operation the
           problem is caused by a transient link failure, which is recoverable.
           The situation is different in a test environment when the
           conversation is being established for the first time. In the test
           environment, either return code is likely.

           The TP should not try to allocate the conversation again until the
           condition is corrected.

           Note:  This return code implies that something is wrong at the local
           workstation, but the implication is not always true. Experience
           suggests that for these problems, both machines, and the connection
           between them, are not configured correctly.

 00000005  ALLOCATION_FAILURE_RETRY

           Explanation: APPC returns this return code when it determines that
           it cannot allocate a conversation, but might be able to allocate a
           conversation without human intervention. For example, APPC cannot
           detect whether there is an adapter in the remote workstation, so
           APPC keeps trying to establish a conversation by simply retrying the
           [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb.

           APPC probably had difficulty activating a link or a session. The TP
           might try again to allocate the conversation. To avoid congesting
           the network with attempted allocation requests, the TP should pause
           or wait for a keystroke before retrying the allocation, and limit
           the number of retries.

           This return code implies that something is wrong at the remote
           location or with the connection between the two machines, but this
           implication is not always true.

           Note:  Even though the return code is ALLOCATION_FAILURE_RETRY, the
                  allocation request might never succeed, especially if the
                  partner is never activated or has been configured
                  incorrectly.

 00000006  INVALID_DATA_SEGMENT

           Explanation: APPC could not process the verb for one of the
           following reasons:

    o The segment that contains the data buffer is too small for the specified
      data length.

    o The segment is not a shared, unnamed segment. The data length might be
      too large, or the address of the data buffer might be wrong.

    o The OS/2 RAM semaphore specified for the wait_object parameter on a
      nonblocking verb is not in a shared, unnamed segment.

           Programmer Response:

    o Ensure that the data segment is a shared, unnamed segment. Determine the
      size and starting address of the data segment. Ensure that the data
      length and data address parameters specified in the verb control block
      correspond to the actual size and location of the desired segment.

    o If the verb is nonblocking, ensure that the OS/2 RAM semaphore is in the
      same shared, unnamed segment as the verb control block.

 00000007  CNOS_NEGOTIATED

           Explanation: APPC accepts the session limits and responsibility as
           negotiated by the partner LU.

           When the local LU tried to set up sessions with the partner LU, the
           partner LU did not agree to what was configured. Fortunately, the
           LUs reached an agreement for splitting up the sessions. This process
           is called "negotiation".

           The mode session limit field configures the maximum number of
           sessions that this mode will use. When the special SNASVCMG sessions
           come up, the local and partner LUs negotiate how many sessions
           between the two LUs will occur. The number of sessions might be
           fewer than you configured.

           The LUs also negotiate who will be the contention winner for each
           session. The CNOS verb defines the minimum number of contention
           winner sessions. The contention winner is the LU who gets the first
           chance at the session. Although you define a value for the
           contention winners, the partner might negotiate it lower than you
           configured. If this occurs, APPC sends a message to the message log.

           Programmer Response: No action is required.

 00000008  NO_CP_DEFD

           Explanation: No local node name (CP name) is active in the local
           machine. In Communications Manager, APPC requires a CP to be defined
           and active in each machine before it will process any APPC verbs.

           Programmer Response: APPC verbs in the program will not be
           successful until a CP is defined and active in the local machine.
           The program should terminate and inform the user of this condition.

 00000011  BAD_CONV_TYPE

           Explanation: APPC does not recognize the specified conversation_type
           parameter. The specified value must be either BASIC_CONVERSATION
           (X'00') or MAPPED_CONVERSATION (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000012  BAD_SYNC_LEVEL

           Explanation: APPC does not recognize the specified sync_level
           parameter. The specified value must be either NONE (X'00') or
           CONFIRM (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000013  BAD_SECURITY

           Explanation: APPC does not recognize the specified security
           parameter. The specified value must be NONE (X'00'), SAME (X'01'),
           or PGM (X'02').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000014  BAD_RETURN_CONTROL

           Explanation: APPC does not recognize the specified return_control
           parameter. The specified value must be WHEN_SESSION_ALLOCATED
           (X'00'), IMMEDIATE (X'01'), WHEN_SESSION_FREE (X'02'),
           WHEN_CONWINNER_ALLOC (X'03'), or WHEN_CONV_GROUP_ALLOC (X'04').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000016  PIP_LEN_INCORRECT

           Explanation: The pip_data_length is longer than 32767 bytes.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a value less than or equal to
           32767.

           This return code recurs until the local program is changed.

 00000017  NO_USE_OF_SNASVCMG_CPSVCMG

           Explanation: APPC does not accept SNASVCMG or CPSVCMG as the value
           for the mode_name parameter.

           Programmer Response: Examine the mode_name in the verb control
           block. SNASVCMG and CPSVCMG are not valid values.

           This return code recurs until the local program is changed.

 00000018  UNKNOWN_PARTNER_MODE

           Explanation: APPC does not recognize the specified partner_lu_alias.
           This return code can also occur if a default_mode_name parameter is
           specified on the DEFINE_DEFAULTS verb and the mode name specified
           there has never been defined.

           This return code can also occur if the program starts as
           Communications Manager is starting. APPC is active and is in the
           process of executing the verbs in the node definitions file (.NDF).
           APPC has not yet executed the verb that defines the partner LU or
           mode used by the program.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a configured partner_lu_alias.

           The most probable cause is a partner LU alias that was been spelled
           incorrectly in the program or in the configuration. The name used in
           the program must match the name specified in the .NDF. If the names
           contain less than eight characters, the program must pad them with
           blanks.

           Ensure that the program uses the correct character sets for these
           names. The partner_lu_alias parameter should be in ASCII.

           If partner_lu_alias is spelled correctly and padded correctly, the
           program might not have moved the parameter into the [MC_]ALLOCATE or
           [MC_]SEND_CONVERSATION verb control block correctly, or it might
           have overwritten the parameter after it moved.

           This return code recurs until either the local program or the local
           configuration is changed.

 00000022  BAD_CONV_STYLE

           Explanation: APPC does not recognize the specified
           conversation_style parameter. The specified value must be either
           TWO_WAY_ALTERNATE (X'00') or TWO_WAY_SIMULTANEOUS (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000023  FDX_NOT_SUPPORTED_BY_LU

           Explanation: The local program specified a full-duplex conversation
           (conversation_style) and the partner LU does not support full-duplex
           conversations.  A session with the partner LU has been established,
           but the program may allocate only half-duplex conversations with
           this partner LU.  APPC reports this return code on an [MC_]ALLOCATE
           verb.

           Programmer Response: Do not allocate full-duplex conversations when
           communicating with this partner LU.

 00000031  CONFIRM_ON_SYNC_LEVEL_NONE

           Explanation: APPC does not allow a TP to issue a [MC_]CONFIRM verb
           if the synchronization level of this conversation was allocated as
           NONE.

           Programmer Response: Either change the [MC_]ALLOCATE verb to specify
           a sync_level other than NONE or prevent the program from issuing the
           [MC_]CONFIRM verb.

           This return code recurs until the local program is changed.

 00000032  CONFIRM_BAD_STATE

           Explanation: The conversation is not in the Send state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information and the state tables in APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can use subsystem management or issue a DISPLAY common services
           verb, requesting active transaction programs information, to find
           the current conversation state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 00000033  CONFIRM_NOT_LL_BDY

           Explanation: The conversation is in the Send state and the TP
           started, but did not finish, sending a logical record.

           Programmer Response: The TP should send a complete logical record
           before the TP issues a CONFIRM verb.

           This return code recurs until the local program is changed.

 00000034  CONFIRM_INVALID_FOR_FDX

           Explanation: The TP issued a [MC_]CONFIRM verb when the conversation
           style is TWO_WAY_SIMULTANEOUS. Alternatively, the TP may have issued
           a [MC_]ALLOCATE verb with a value of CONFIRM specified for the
           sync_level parameter and a value of TWO_WAY_SIMULTANEOUS for
           conversation_style.

           Programmer Response:

    o Do not issue an [MC_]CONFIRM verb when the conversation style is
      TWO_WAY_SIMULTANEOUS.

    o Either change the [MC_]ALLOCATE verb to specify a sync_level of NONE, or
      specify a conversation_style of TWO_WAY_ALTERNATE.

           This return code recurs until the local program is changed.

 00000041  CONFIRMED_BAD_STATE

           Explanation: The conversation is not in the Confirm state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can use subsystem management or issue a DISPLAY common services
           verb, requesting active transaction programs information, to find
           the current conversation state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 00000042  CONFIRMED_INVALID_FOR_FDX

           Explanation: The TP issued a [MC_]CONFIRMED verb when the
           conversation style is TWO_WAY_SIMULTANEOUS.

           Programmer Response: Do not issue an [MC_]CONFIRMED verb when the
           conversation style is TWO_WAY_SIMULTANEOUS.

           This return code recurs until the local program is changed.

 00000051  DEALLOC_BAD_TYPE

           Explanation: APPC does not recognize the specified type parameter.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000052  DEALLOC_FLUSH_BAD_STATE

           Explanation: One of the following errors occurred:

    o The TP specified type(SYNC_LEVEL) for a conversation that has a
      synchronization level of NONE and is not in the Send, Send-Receive, or
      Send-Only states.

    o The TP might have specified type(FLUSH) when the conversation was not in
      the Send, Send-Receive, or Send-Only states. The verb was not executed
           and the conversation was not deallocated.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can use subsystem management or issue the DISPLAY common services
           verb, requesting active transaction programs information, to find
           the current conversation state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 00000053  DEALLOC_CONFIRM_BAD_STATE

           Explanation: The TP specified type(SYNC_LEVEL) for a conversation
           that has a synchronization level of CONFIRM when the conversation
           was not in the Send state. The conversation was not deallocated.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information and the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can use subsystem management or issue the DISPLAY common services
           verb, requesting active transaction programs information, to find
           the current conversation state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 00000055  DEALLOC_NOT_LL_BDY

           Explanation: The conversation is in the Send state and type was
           specified as SYNC_LEVEL or FLUSH. The TP started, but did not
           finish, sending a logical record.

           Programmer Response: The TP should send a complete logical record
           the TP before it issues a DEALLOCATE verb.

           This return code recurs until the local program is changed.

 00000057  DEALLOC_LOG_LL_WRONG

           Explanation: The LL field of the log data does not match the
           specified log_data_length.

           Programmer Response: Examine the verb control block and the data
           buffer being issued for this verb. Ensure that the log_data_length
           parameter matches the LL fields at the beginning of the data buffer.
           Note that the log_data_length is in byte-reversed (Intel) format,
           but the LL field is not.

           This return code recurs until the local program is changed.

 00000061  FLUSH_NOT_SEND_STATE

           Explanation: The conversation is not in the Send, Send-Receive, or
           Send-Only state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can issue the DISPLAY common services verb, requesting active
           transaction programs information, to find the current conversation
           state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000A1  P_TO_R_INVALID_TYPE

           Explanation: APPC does not recognize the specified type parameter.
           The specified value must be either SYNC_LEVEL (X'00') or FLUSH
           (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 000000A2  P_TO_R_NOT_LL_BDY

           Explanation: The conversation is in the Send state and the TP
           started, but did not finish, sending a logical record.

           Programmer Response: The TP should send a complete logical record
           before it issues a PREPARE_TO_RECEIVE verb.

           This return code recurs until the local program is changed.

 000000A3  P_TO_R_NOT_SEND_STATE

           Explanation: The conversation is not in the Send state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can issue the DISPLAY common services verb, requesting active
           transaction programs information, to find the current conversation
           state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000A5  P_TO_R_INVALID_FOR_FDX

           Explanation: The TP issued a [MC_]PREPARE_TO_RECEIVE verb when the
           conversation style is TWO_WAY_SIMULTANEOUS.

           Programmer Response: Do not issue an [MC_]PREPARE_TO_RECEIVE verb
           when the conversation style is TWO_WAY_SIMULTANEOUS.

           This return code recurs until the local program is changed.

 000000B1  RCV_AND_WAIT_BAD_STATE

           Explanation: The conversation is not in the Receive, Send,
           Send-Receive, or Receive-Only state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can issue the DISPLAY common services verb, requesting active
           transaction programs information, to find the current conversation
           state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000B2  RCV_AND_WAIT_NOT_LL_BDY

           Explanation: The conversation is in the Send state and the TP
           started, but did not finish, sending a logical record.

           Programmer Response: The TP should send a complete logical record
           before the TP issues a RECEIVE_AND_WAIT verb.

           This return code recurs until the local program is changed.

 000000B5  RCV_AND_WAIT_BAD_FILL

           Explanation: The TP specified an invalid value for the fill
           parameter. The specified value must be either BUFFER (X'00') or LL
           (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 000000C1  RCV_IMMD_BAD_STATE

           Explanation: The conversation is not in the Receive, Send-Receive,
           or Receive-Only state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can use subsystem management or issue the DISPLAY common services
           verb, requesting active transaction programs information, to find
           the current conversation state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000C4  RCV_IMMD_BAD_FILL

           Explanation: The TP specified an invalid value for the fill
           parameter. The specified value must be either BUFFER (X'00') or LL
           (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 000000D1  RCV_AND_POST_BAD_STATE

           Explanation: The conversation is not in the Receive or Send state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can issue the DISPLAY common services verb, requesting active
           transaction programs information, to find the current conversation
           state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000D2  RCV_AND_POST_NOT_LL_BDY

           Explanation: The conversation is in the Send state and the TP
           started, but did not finish, sending a logical record.

           Programmer Response: The TP should send a complete logical record
           before the TP issues a RECEIVE_AND_POST verb.

           This return code recurs until the local program is changed.

 000000D5  RCV_AND_POST_BAD_FILL

           Explanation: The TP specified an invalid value for the fill
           parameter. The specified value must be either BUFFER (X'00') or LL
           (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 000000D6  INVALID_SEMAPHORE_HANDLE

           Explanation: APPC cannot use the specified semaphore. The handle for
           a system semaphore must be obtained when the semaphore is created or
           opened. The handle for a RAM semaphore must be a valid address of a
           4-byte memory location.

           Programmer Response: Fix the program to supply a valid semaphore
           handle.

           This return code recurs until the local program is changed.

 000000D7  BAD_RETURN_STATUS_WITH_DATA

           Explanation: APPC does not recognize the specified
           return_status_with_data parameter. The specified value must be
           either NO (X'00') or YES (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 000000E1  R_T_S_BAD_STATE

           Explanation: The conversation is in the wrong state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can use subsystem management or issue the DISPLAY common services
           verb, requesting active transaction programs information, to find
           the current conversation state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000E2  R_T_S_INVALID_FOR_FDX

           Explanation: The TP issued a [MC_]REQUEST_TO_SEND verb when the
           conversation style is TWO_WAY_SIMULTANEOUS.

           Programmer Response: Do not issue an [MC_]REQUEST_TO_SEND verb when
           the conversation style is TWO_WAY_SIMULTANEOUS.

           This return code recurs until the local program is changed.

 000000F1  BAD_LL

           Explanation: The data buffer contains an invalid logical record
           length (LL) value of X'0000', X'0001', X'8000', or X'8001'.

           Programmer Response: Examine the data buffer used for this verb.
           Ensure that any LL field in the data buffer contain valid values.

           This return code recurs until the local program is changed.

 000000F2  SEND_DATA_NOT_SEND_STATE

           Explanation: The conversation is not in the Send, Send-Receive, or
           Send-Only state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes and the
           what_received values returned by the Receive verbs. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can issue the DISPLAY common services verb, requesting active
           transaction programs information, to find the current conversation
           state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 000000F4  SEND_DATA_INVALID_TYPE

           Explanation: APPC does not recognize the specified type parameter.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 000000F5  SEND_DATA_CONFIRM_SYNC_NONE

           Explanation: APPC does not permit a TP to issue a [MC_]SEND_DATA
           verb with type(CONFIRM) if the synchronization level of the
           conversation is allocated as NONE.

           Programmer Response: Either change the [MC_]ALLOCATE verb to specify
           a sync_level other than NONE, or prevent the program from issuing
           the [MC_]SEND_DATA verb with type(CONFIRM).

           This return code recurs until the local program is changed.

 000000F6  SEND_DATA_NOT_LL_BDY

           Explanation: The conversation is in the Send state and the TP
           started, but did not finish, sending a logical record. This can
           occur when type was specified as CONFIRM, DEALLOCATE_FLUSH,
           DEALLOCATE_SYNC_LEVEL, PREPARE_TO_RECEIVE_FLUSH, or
           PREPARE_TO_RECEIVE_SYNC_LEVEL.

           Programmer Response: The TP should send a complete logical record
           before it issues a SEND_DATA verb.

           This return code recurs until the local program is changed.

 000000F7  SEND_TYPE_INVALID_FOR_FDX

           Explanation: APPC does not permit a TP to specify the following
           values for the type parameter when the conversation style is two-way
           simultaneous:

    o CONFIRM (X'02')
    o PREPARE_TO_RECEIVE_FLUSH (X'03')
    o PREPARE_TO_RECEIVE_SYNC_LEVEL (X'04')

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a type value that is valid for
           two-way simultaneous conversations.

           This return code recurs until the local program is changed.

 000000F8  SEND_DATA_BAD_USER_CONTROL_DATA

           Explanation: APPC does not recognize the specified user_control_data
           parameter.  The specified value must be either NO (X'00') or YES
           (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000102  SEND_ERROR_LOG_LL_WRONG

           Explanation: The LL field of the log data does not match the
           specified log_data_length.

           Programmer Response: Examine the verb control block and the data
           buffer being issued for this verb. Ensure that the log_data_length
           parameter matches the LL fields at the beginning of the data buffer.
           Note that the log_data_length is in byte-reversed (Intel) format,
           whereas the LL field is not.

           This return code recurs until the local program is changed.

 00000103  SEND_ERROR_BAD_TYPE

           Explanation: APPC does not recognize the specified type parameter.
           The specified value must be either PROG (X'00') or SVC (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000104  SEND_ERROR_BAD_STATE

           Explanation: The conversation is not in the Send-Receive or
           Send-Only state.

           Programmer Response: The TP did not correctly handle the state
           information that APPC returned.

           The program should examine the APPC return codes. Use this
           information with the state tables in the APPC Programming Guide and
           Reference to find the current state.

           When the program is on the error path indicated by this return code,
           it can issue the DISPLAY common services verb, requesting active
           transaction programs information, to find the current conversation
           state.

           Fix the local program so it uses information returned by APPC to
           know its current state.

 00000105  BAD_ERROR_DIRECTION

           Explanation: APPC does not recognize the specified error_direction
           parameter. The specified value must be either RECEIVE (X'00') or
           SEND (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000123  TEST_INVALID_FOR_FDX

           Explanation: The TP issued a [MC_]TEST_RTS verb when the
           conversation style is TWO_WAY_SIMULTANEOUS.

           Programmer Response: Do not issue an [MC_]TEST_RTS verb when the
           conversation style is TWO_WAY_SIMULTANEOUS.

           This return code recurs until the local program is changed.

 00000124  SEND_EXPD_INVALID_LENGTH

           Explanation: The value specified for the data_length parameter of
           the [MC_]SEND_EXPEDITED_DATA verb is not within the valid range of 1
           to 86.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000125  RECEIVE_EXPD_INVALID_LENGTH

           Explanation: The value specified for the max_length parameter of the
           [MC_]RECEIVE_EXPEDITED_DATA verb is not within the valid range of 0
           to 86.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000126  EXPD_BAD_RETURN_CONTROL

           Explanation: APPC does not recognize the specified return_control
           parameter for the [MC_]RECEIVE_EXPEDITED_DATA verb. The specified
           value must be either WHEN_EXPEDITED_DATA_RECEIVED (X'00') or
           IMMEDIATE (X'01').

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for this parameter.

           This return code recurs until the local program is changed.

 00000150  CNOS_IMPLICIT_PARALLEL

           Explanation: APPC does not permit a program to change the session
           limit for a mode other than the SNASVCMG mode for the implicit
           partner template when the template specifies parallel sessions. (The
           term template is used because many of the actual values are yet to
           be filled in.) Before the session activation request that identifies
           the implicit partner arrives, CNOS negotiation is impossible. A TP
           can change session limits for implicit partners after they have been
           established.

           Programmer Response: Fix the local program so that it does not issue
           a CNOS verb for modes other than the SNASVCMG mode, when the partner
           LU is an implicit partner LU template. Implicit partner LUs are
           those configured with a partner LU name that starts with an asterisk
           (*).

           This return code recurs until the local program is changed.

 00000151  CANT_RAISE_LIMITS

           Explanation: APPC does not permit session limits to be set to a
           nonzero value unless the limits are currently 0.

           Programmer Response: Use subsystem management or issue the DISPLAY
           common services verb to find the current session limits. If the
           limits are already the value desired by the local program, no action
           is required. If they are not acceptable, the session limits must
           first be lowered to 0, then raised to the desired nonzero value.

 00000152  AUTOACT_EXCEEDS_SESSLIM

           Explanation: On the CNOS verb, the value for the auto_activate
           parameter is greater than the value for the
           partner_lu_mode_session_limit parameter.

           Programmer Response: Fix the local program so that when it issues a
           CNOS verb, it does not try to auto-activate more sessions than its
           limit.

           This return code recurs until the local program is changed.

 00000153  ALL_MODE_MUST_RESET

           Explanation: APPC does not permit a nonzero session limit when the
           mode_name_select parameter indicates ALL.

           Programmer Response: Examine the verb control block being used for
           this verb. Fix the local program so that it does not specify a
           nonzero value, or change the mode_name_select parameter to a value
           other than ALL.

           This return code recurs until the local program is changed.

 00000154  BAD_SNASVCMG_LIMITS

           Explanation: The program specified invalid settings for the
           partner_lu_mode_session_limit, min_conwinners_source, or
           min_conwinners_target parameters when mode_name(SNASVCMG) was
           supplied.

           The three groups of valid settings are as follows:

       partner_lu_mode_session_limit(2)
       min_conwinners_source(1)
       min_conwinners_target(1)

       partner_lu_mode_session_limit(1)
       min_conwinners_source(0)
       min_conwinners_target(1)

       partner_lu_mode_session_limit(0)
       min_conwinners_source(0)
       min_conwinners_target(0)

           Programmer Response: Examine the verb control block being used for
           this verb. Fix the local program to specify a valid combination of
           these three parameters when the SNASVCMG mode is specified.

           This return code recurs until the local program is changed.

 00000155  MIN_GT_TOTAL

           Explanation: The sum of min_conwinners_source and
           min_conwinners_target specifies a number greater than
           partner_lu_mode_session_limit.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program so that it the sum of the
           min_conwinners_source and the min_conwinners_target is less than or
           equal to  the partner_lu_mode_session_limit.

           This return code recurs until the local program is changed.

 00000156  CNOS_MODE_CLOSED

           Explanation: The local LU cannot negotiate a nonzero session limit
           because the local maximum session limit at the partner LU is 0.

           The primary return code corresponding to this secondary return code
           is CNOS_PARTNER_LU_REJECT.

           Programmer Response: The local program cannot take any action until
           the partner LU raises its session limit above 0.

 00000156  MODE_CLOSED

           Explanation: The CNOS verb must specify a mode session limit of 0
           because the local maximum negotiable session limit is currently 0
           for the specified mode and set_negotiable(YES) was specified.

           The primary return code corresponding to this secondary return code
           is PARAMETER_CHECK.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify 0 for the mode session limit.

 00000157  CNOS_MODE_NAME_REJECT

           Explanation: The partner LU does not recognize the specified mode
           name.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a mode name that has been defined
           at the remote location.

           This return code recurs until either the local program or the remote
           configuration is changed.

 00000159  RESET_SNA_DRAINS

           Explanation: The SNASVCMG mode does not support the drain parameter
           values.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for the drain
           parameter when the mode_name specifies SNASVCMG.

           This return code recurs until the local program is changed.

 0000015A  SINGLE_NOT_SRC_RESP

           Explanation: For a single-session CNOS verb (that is, the partner LU
           session limit is 1), APPC permits only the local (source) LU to be
           responsible for deactivating sessions.

           Programmer Response: Set the responsible parameter to indicate the
           source LU.

           This return code recurs until the local program is changed.

 0000015B  BAD_PARTNER_LU_ALIAS

           Explanation: APPC did not recognize the supplied partner_lu_alias.

           Programmer Response: Examine the local node definitions file (.NDF),
           use subsystem management, or issue the DISPLAY common services verb,
           requesting partner LU information, to find which partner LUs are
           defined at the local machine. Specify a defined partner LU and issue
           the verb again.

           This return code recurs until either the local program or the local
           configuration is changed.

 0000015C  EXCEEDS_MAX_ALLOWED

           Explanation: The program issued a CNOS verb that specified a
           partner_lu_mode_session_limit number and set_negotiable(NO). The
           number specified for the partner_lu_mode_session_limit parameter
           exceeds the current maximum negotiable session limit.

           One way to set the maximum negotiable session limit is by using the
           DEFINE_MODE verb. Another way is to issue a CNOS verb, specifying a
           new partner_lu_mode_session_limit number and set_negotiable(YES).

           Programmer Response: Use subsystem management or issue the DISPLAY
           common service verb to find the local maximum negotiable session
           limit. Fix the local program to specify a session limit less than
           that value.

 0000015D  CHANGE_SRC_DRAINS

           Explanation: APPC does not permit mode_name_select(ONE) and
           drain_source(YES) when drain_source(NO) is currently in effect for
           the specified mode.

           Programmer Response: No action is required.

 0000015E  LU_DETACHED

           Explanation: A command to stop Communications Manager reset the
           definition of the local LU before the CNOS verb tried to specify
           that LU.

           Programmer Response: No action is required. Since APPC is being
           stopped, all sessions are terminated.

 0000015F  CNOS_COMMAND_RACE_REJECT

           Explanation: The local LU is currently processing a CNOS verb issued
           by the partner LU.

           Programmer Response: Retry the CNOS verb after a short delay.

 00000167  SNASVCMG_RESET_NOT_ALLOWED

           Explanation: The local program attempted to issue the CNOS verb for
           the mode named SNASVCMG that specified a mode session limit of 0.
           This mode cannot be explicitly reset using this verb.

           Programmer Response: Correct the program so that it does not issue a
           CNOS for the SNASVCMG mode.

           This return code recurs until the local program is changed.

 000001B4  DISPLAY_INFO_EXCEEDS_LEN

           Explanation: The returned DISPLAY information did not fit in the
           buffer, so APPC stopped processing the verb. As much information as
           possible was returned. If a particular type of information cannot be
           returned into the display data buffer because it will not fit, no
           information of that type is returned and its returned information
           address contains X'FFFFFFFF'.

           Programmer Response: If the program cannot increase the size of the
           segment containing the display data buffer, issue the DISPLAY verb
           repeatedly, requesting fewer information fields each time.

 000001B5  DISPLAY_INVALID_CONSTANT

           Explanation: The value supplied for the parameter num_sections or
           init_sect_len is invalid.

           Programmer Response: Fix your local program to specify a valid value
           for this field.

    For the DISPLAY verb: For Extended Services Communications Manager, use the
              values num_sections(16) and init_sect_len(50). To write programs
              that are compatible with OS/2 Extended Edition versions 1.2 and
              1.3, use the values num_sections(9) and init_sect_len(44).
    For the DISPLAY_APPN verb: For Extended Services Communications Manager,
              use the values num_sections(6) and init_sect_len(40).

 000001C0  DUPLICATE_LINK_NAME

           Explanation: The program issued a DEFINE_LOGICAL_LINK verb that
           specified a link_name for a link that was already defined. An
           existing link cannot be redefined with a different DLC name or
           adapter number.

           Programmer Response: Use subsystem management or issue the DISPLAY
           common services verb to find the current DLC name and adapter number
           that corresponds to the link. Either deactivate and delete the link
           first, to redefine it, or correct the program to specify the correct
           DLC name and adapter number.

 000001C1  INVALID_LINK_NAME

           Explanation: APPC does not recognize the specified link_name
           parameter value. The specified value must be an 8-byte Type A EBCDIC
           name. If the name contains less than 8 bytes, it must be padded with
           EBCDIC blanks. Implicit link names start with an EBCDIC '@', so any
           specified link name must not start with an EBCDIC '@'.

           Note:  For SNA compability, avoid using the three special characters
                  ($, #, and @) in Type A names.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program or configuration to specify a valid value for
           this parameter.

           This return code recurs until the local program or configuration is
           changed.

 000001C3  INVALID_USER_DEF_1

           Explanation: APPC does not recognize the specified
           user_defined_1_min or user_defined_1_max parameter value. These
           parameters specify the minimum and maximum values of the first
           user-defined transmission group (TG) characteristic for this TG row.
           The specified value must be an integer in the range 0 through 255.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for these parameters.

           This return code recurs until the local program is changed.

 000001C4  INVALID_USER_DEF_2

           Explanation: APPC does not recognize the specified
           user_defined_2_min or user_defined_2_max parameter value. These
           parameters specify the minimum and maximum values of the second
           user-defined transmission group (TG) characteristic for this TG row.
           The specified value must be an integer in the range 0 through 255.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for these parameters.

           This return code recurs until the local program is changed.

 000001C5  INVALID_USER_DEF_3

           Explanation: APPC does not recognize the specified
           user_defined_3_min or user_defined_3_max parameter value. These
           parameters specify the minimum and maximum values of the third
           user-defined transmission group (TG) characteristic for this TG row.
           The specified value must be an integer in the range 0 through 255.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program to specify a valid value for these parameters.

           This return code recurs until the local program is changed.

 000001C6  DLC_NOT_DEFD

           Explanation: The adapter specified for the connection network does
           not have a corresponding data link control (DLC) profile in the
           configuration file (.CFG).

           Programmer Response: Ensure that the specified DLC name is one that
           has been configured and verified in the corresponding Communications
           Manager configuration file (.CFG).

 000001C8  PU_PREVIOUSLY_DEFINED

           Explanation: You have a link name already defined  with this pu_name
           on a different DEFINE_LOGICAL_LINK verb.  You cannot have two links
           with the same pu_name specified.

           Programmer Response: Make sure the pu_name is entered correctly.  If
           you want to change the link name, change the configuration file, by
           adding the new name, then stop APPC and restart.  If you want to
           change the pu_name, redefine and issuse the DEFINE_LINK verb.

 000001C9  CHANGED_PU_WITH_DEPENDENT_LUs

           Explanation: You attempted to redefine a pu_name that has already
           has defined dependent LUs (Gateway, LUA, or 6.2) assigned to this
           link.  This return code error occurs on the DEFINE_LOGICAL_LINK
           verb.

           Programmer Response: Change the configuration file by adding the new
           pu_name, then stop APPC and restart to enable the new configuration.

 000001CA  INVALID_CP_NAME

           Explanation: The program issued a DEFINE_LOGICAL_LINK verb.

           APPC does not recognize the specified
           fully_qualified_adjacent_cp_name parameter value. The specified
           value must be a 1- to 8-byte network ID, concatenated with an EBCDIC
           period and the 1- to 8-byte name of the control point (CP). The
           network ID (also known as SNA network name or NETID) and the control
           point name must be Type A EBCDIC strings. If this fully qualified
           name contains less than 17 bytes, pad it with EBCDIC blanks.

           The local machine is an APPN network node. The program specified
           adjacent_node_type(NN), and the NETID portion of the
           fully_qualified_adjacent_cp_name parameter does not match the NETID
           of the local node. In general, in network node to network node link
           definitions, both network nodes must have the same NETID.

           Programmer Response: Examine the verb control block for the verb.
           Fix the local program or configuration to specify a valid value for
           this parameter.

           This return code recurs until the local program or configuration is
           changed