OS/2 Shareware BBS: 14 Text/14-Text.zip/cmoverv.inf

OS/2 Help File | 1993-10-19 | 107KB | 3,436 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ

Communications Manager provides services that your workstation can use to
communicate with a host computer or another workstation.  You can use
Communications Manager applications to exchange information or use resources
from the host or from other workstations.  These resources include programs,
files, databases, and printers.

Communications Manager allows your workstation to:

o Communicate with host computers or other workstations either directly or
  through any of the following kinds of networks:

   - Local area networks (LANs)

   - Systems Network Architecture-conforming networks

   - Integrated services digital network (ISDN)

   - X.25 networks

o Control the method of data exchange between your workstation and a host
  computer or another workstation that uses different kinds of communications
  protocols or techniques, such as Synchronous Data Link Control (SDLC), X.25,
  or asynchronous communications

o Be configured remotely by any computer running Communications Manager over a
  network

o Emulate, or perform like, a 3270 or 5250 display terminal when communicating
  with a host computer

o Use the services of the Presentation Manager* interface, such as the
  clipboard, online help, and emulator help

o Transfer files to and from a host computer or another workstation

o Use host-directed printing features

o Remap, or change, keyboard definitions for the OS/2 3270/5250 emulator.

*  Trademark of IBM.


ΓòÉΓòÉΓòÉ 2. What's New ΓòÉΓòÉΓòÉ

Communications Manager/2 Version 1.1 contains the following new functions:

o An enhanced OS/2 3270/5250 emulator, including:

   - A Menu Bar to access emulator functions

   - Hide/Show and Popup Menu Bar options on the System Menu

   - New emulator functions, including:

      o New file transfer functions permitting multiple file transfers and host
        selection with pull-down menus.

      o Automatic Font Selection

      o Hotspots for host mouse functions

      o Popup Keypad

      o Numeric Lock Field

o Double-byte character set support for the OS/2 3270/5250 emulator.

o A Communications Manager/2 Distributed Feature that allows you to run
  Communications Manager from a redirected drive.

o The capability to support transactions in full-duplex mode in an LU 6.2
  environment.

o Support for Integrated Data Link Control (IDLC)

o Support for SNA session level data compression

o The capability of connecting to an unlimited number of hosts concurrently

o The capability that all workstations running OS/2 on a LAN segment have
  access to NetView*.

o The capability for downstream Novell** NetWare** users to use Communications
  Manager as a gateway to exchange network management data between themselves
  and NetView* running on the host.

o The capability to issue Communications Manager system management commands
  from the OS/2 command line to obtain and display information about links,
  data-link control, and APPC transactions.

o The capability to route RUNCMDs from an OS/2 service point to an OS/2
  workstation.

o Expanded use of First Failure Support Technology (FFST/2) to perform problem
  determination functions.

o Expanded formatted trace service, to include more APIs, such as SRPI,
  EHLLAPI, LUA, and ACDI.

*  Trademark of IBM.

**  Trademark of Novell, Inc.


ΓòÉΓòÉΓòÉ 2.1. Communications Manager/2 Distributed Feature ΓòÉΓòÉΓòÉ

The CM/2 Distributed Feature has the capability to share a common set of files
among multiple users. This requires only a small amount of Communications
Manager product files to be stored on your workstation.  The rest of the
product files are stored on a file server on the same LAN. The distributed
workstations have many, but not all, of the functions of the single user
workstations.

Following are some of the services the CM/2 Distributed Feature supports:

o 3270 and 5250 emulation over LAN connections
o APPC, CPI Communications, and LUA APIs over LAN connections
o ACDI redirection over LAN connections
o ACDI API over an asynchronous connection

Following are some of the services the Communications Manager/2 Distributed
Feature does not support:

o Synchronous data link control (SDLC)
o Integrated Data Link Control (IDLC)
o Twinaxial data link control (TDLC)
o X.25 DLC
o Gateway
o Network node
o Ability to create and maintain configurations

See the Network Administration and Subsystem Management Guide for more
information on the CM/2 Distributed Feature.

See the Workstation Installation and Configuration Guide for more information
on installing and configuring the CM/2 Distributed Feature.


ΓòÉΓòÉΓòÉ 3. Services and Connections ΓòÉΓòÉΓòÉ

Communications Manager supports a variety of services and connections
including:

Services

o Advanced Peer-to-Peer Networking* (APPN*)

o Advanced program-to-program communications (APPC)

o Asynchronous communications device interface (ACDI)

o Subsystem management

o Systems application architecture* (SAA*) common communications support
  architectures

o Systems network architecture (SNA) gateway

o User Profile Management

o Novell** NetWare** support

o FFST/2* support

Connections

o Local Area Network (LAN) Support Services

o Integrated services digital network (ISDN)

   - IDLC
   - SDLC
   - X.25
   - LAN (IEEE 802.2 and NetBIOS)

o X.25 network

o Coaxial distributed function terminal (DFT)

o Synchronous data link control (SDLC) nonswitched and switched line support

o Twinaxial data link control (TDLC)

*  Trademark of IBM.

** Trademark of Novell, Inc.


ΓòÉΓòÉΓòÉ 3.1. Advanced Peer-to-Peer Networking (APPN)* ΓòÉΓòÉΓòÉ

Communications Manager provides Advanced Peer-to-Peer Networking (APPN)
end-node and network-node support for workstations, allowing them more
flexibility communicating with other systems in the network. Some of the
important capabilities that APPN provides are:

o End-node capability, which allows the local node, such as a workstation, to
  connect as an end node to a serving network node for directory and routing
  services.

o Network-node capability, which provides network services on behalf of
  connected end nodes.

o Connection network services for the LAN, which workstations use to obtain LAN
  destination addresses without having to be configured for them.  This
  capability allows a node to establish a link connection directly to another
  node with no LAN destination address configured.

* Trademark of IBM


ΓòÉΓòÉΓòÉ 3.2. Advanced Program-to-Program Communications (APPC) ΓòÉΓòÉΓòÉ

Communications Manager supports APPC between SNA applications, allowing
workstations to share programs, files, and other data.  Communications Manager
also supplies an APPC API for writing application programs.

APPC supports conversation and session security between communicating programs.
You can manage this security through User Profile Management Services.

Communications Manager also supports data compression for APPC communications.


ΓòÉΓòÉΓòÉ 3.3. Asynchronous Communications Device Interface (ACDI) ΓòÉΓòÉΓòÉ

Communications Manager supports asynchronous communication for applications
written to the ACDI or ACDI Redirection API. This includes:

o Direct asynchronous communications from the workstation

o Redirected asynchronous communications through a LAN server that has the IBM*
  Local Area Network Asynchronous Connection Server (LANACS) installed.

*Trademark of IBM.


ΓòÉΓòÉΓòÉ 3.4. Coaxial Distributed Function Terminal (DFT) ΓòÉΓòÉΓòÉ

Communications Manager supports coaxial DFT, which is the protocol used for
communication through an IBM 3274 or IBM 3174 control unit.

Communications Manager also supports the 3270 credit card adapter.


ΓòÉΓòÉΓòÉ <hidden> 3270 Credit Card Adapter ΓòÉΓòÉΓòÉ

The 3270 emulation credit card adapter is a credit card size adapter that
provides an interface between computer systems and 3270 networks. The 3270
credit card emulates a 3270 session in DFT and is designed for use with
Personal Computer Memory Card International Association (PCMCIA) version 2.0,
type 2 slots.

When you choose to use this option, the 3270 emulation is configured to use a
3270 credit card for communication.  If a 3270 credit card is not installed,
the 3270 emulator looks for a 3270 connection adapter, a 3278/79 emulation
adapter, or an advanced 3278/79 emulation adapter for communication.

Note:  There is no support for LAN over Coaxial (DFT).  The existing DFT
       limitation of 5 sessions remains unchanged.  This support is for OS/2
       V2.1 and higher.


ΓòÉΓòÉΓòÉ 3.5. Integrated Data Link Control (IDLC) ΓòÉΓòÉΓòÉ

IDLC is a full-duplex high-level data link control (HDLC) protocol. It is IBM's
implementation of the CCITT Q.922 standard or Link Access Procedure-Extended
(LAPE).  IDLC can support point-to-point workstation connections over a
full-duplex wide area network (WAN).

In some cases, IDLC refers to Integrated Services Digital Network (ISDN) data
link control.  It has the same function as integrated data link control, but it
is used by ISDN.  The Communications Manager implementation of IDLC supports
not only the ISDN B-channel, but also supports any point-to-point WAN
connection.

IDLC is supported by the AS/400 and the 3174 Communication Controller for an
ISDN connection.


ΓòÉΓòÉΓòÉ 3.6. Integrated Services Digital Network (ISDN) ΓòÉΓòÉΓòÉ

ISDN is a technology for transferring data over a switched digital
telecommunication network.  This ability provides a fast and reliable way for
transferring or sharing information between remotely attached machines.
Because several users can share the same circuits within the switched network,
the network needs a protocol to manage the communication links.

The recommendations of the International Telegraph and Telephone Consultative
Committee (CCITT) define such a protocol for attaching equipment (for example,
a workstation) to an ISDN.  Communication Manager's switched network
environment, along with the IBM ISDN interface coprocessor adapters and the IBM
ISDN Coprocessor Support Program Version 1.2 software, supports this protocol
and its variations specific to certain network implementation worldwide.

Communications Manager supports the basic rate interface to an ISDN. This
interface provides circuit switch or packet mode access on two independent 64
kilobits per second (Kbps) data channels (referred to as B-channels).  It also
provides a 16 Kbps signaling channel (referred to as the D-channel).  The
D-channel is mainly used for signaling but it can also be used for X.25 packet
data communications.

To enable Communications Manager ISDN support, the following software must be
installed and configured in the following order:

o LAPS (NTS/2 level required)

  If you are not using LAN protocols, install using the LAPS /N command. This
  provides PROTMAN.OS2, NETBIND.EXE and PROTOCOL.INI.

o IBM ISDN Coprocessor Support Program Version 1.2

  This provides the software support for the adapter and NETWORK.INI.
  NETWORK.INI provides network-specific information to Communications Manager.

o Communications Manager/2 Version 1.1


ΓòÉΓòÉΓòÉ 3.7. Local Area Network (LAN) Support ΓòÉΓòÉΓòÉ

LAN Adapter and Protocol Support (LAPS) is a prerequisite for Communications
Manager.  IBM Network Transport Services/2 (NTS/2) provides the support for IBM
LAN adapters and a range of certified non-IBM LAN adapters for the following
types of LANs:

o IBM Token-Ring Network

o IBM PC Network

o Ethernet (ETHERAND) Network

o IBM 3174 Peer Communications Network


ΓòÉΓòÉΓòÉ 3.8. NetWare Support ΓòÉΓòÉΓòÉ

Communications Manager provides the ability to use either Communications
Manager or NetWare as a gateway to exchange network management data between
themselves and NetView* running on a host. This requires that you have a
Communications Manager workstation and Novell** NetWare** for SAA* server on a
LAN.  With this configuration, Communications Manager supports SNA Management
Services transport between:

o A Communications Manager workstation and NetView through an intermediary
  NetWare for SAA server

o A NetWare for SAA server and NetView through an intermediary Communications
  Manager workstation

*  Trademark of IBM.

** Trademark of Novell, Inc.


ΓòÉΓòÉΓòÉ 3.9. Subsystem Management ΓòÉΓòÉΓòÉ

Communications Manager provides subsystem management to allow you to display
and control the running status of the links, sessions, and transaction programs
(TPs) operating on your system.  You can fine-tune the operation of your
network by displaying the status of these resources and using subsystem
management functions to alter communication session operations. As you take
these actions, subsystem management continues to monitor the real-time activity
of your sessions and the links on which they are operating.  As a result, you
can immediately see how an action you take on one resource affects the
operation of others.

In the Subsystem Management window you can:

o View the status of the Communications Manager services that are listed in the
  window.

o Viewing the status of Communications Manager services

o Use the menu bar in the window to start or stop many of the listed services.

o Starting and stopping Communications Manager services

o Use the menu bar to display the status of your network resources (links, data
  link controls (DLCs), and sessions). When you open the display windows, you
  can start or stop activity on many of the displayed resources.

o Displaying and controlling sessions and links


ΓòÉΓòÉΓòÉ <hidden> Viewing the Status of Communications Manager Services ΓòÉΓòÉΓòÉ

The Subsystem Management window displays a list of the names of the services
that can be displayed or controlled within subsystem management. The status
field next to the name of a service tells you whether the service is currently
Starting, Started, Stopping, or Stopped within the active configuration.

The fields at the top of the window display the names of the active
configuration (the configuration that is currently running) and the default
configuration (the configuration that Communications Manager uses when you
first start the program on your workstation).


ΓòÉΓòÉΓòÉ <hidden> Starting and Stopping Communications Manager Services ΓòÉΓòÉΓòÉ

You can use the pull-down menu in the Subsystem Management window to start and
stop the following services:

o APPC (advanced program-to-program communication) attach manager

o Communications Manager kernel

o SNA (systems network architecture) subsystem

Note:  Some of these services may not appear in the Subsystem Management window
on your workstation.  The services displayed in the window vary by the type of
workstation configuration you are using.


ΓòÉΓòÉΓòÉ <hidden> Keylock ΓòÉΓòÉΓòÉ

The Communications Manager keylock is a software security function that serves
two purposes:

o Protects confidential information that could be exposed by some
  Communications Manager functions, such as trace and configuration.

o Prevents unauthorized or accidental changes to a configuration.

If you need access to keylocked functions, your system administrator can give
you the password.


ΓòÉΓòÉΓòÉ <hidden> Displaying and Controlling Sessions and Links ΓòÉΓòÉΓòÉ

You can use the Subsystem Management window to display the status of individual
communication sessions and the links on which they operate.

SNA Networks

To display the status of sessions and links on a Systems Network Architecture
(SNA) network, select SNA subsystem; and then select Service from the menu bar.
Select Details from the Service pull-down menu.  The SNA Subsystem window
appears, from which you can choose which resources you want to display or
control.

In many cases, when you open a display window, you can use the pull-down menu
on the window to start, stop, or modify the activity of the individual
resources displayed.

X.25 Networks

To display the status of physical links or SNA virtual circuits on an X.25
network, select your choice on this window; and then select Service from the
menu bar.  Select Details from the Service pull-down menu.

When you open a display window, you can use the menu bar on the window to
start, stop, or modify the activity of the individual resources displayed.

Note:  X.25 selections appear only when X.25 physical links and SNA virtual
circuits are defined in your configuration.


ΓòÉΓòÉΓòÉ 3.10. SAA Common Communications Support Architectures ΓòÉΓòÉΓòÉ

Communications Manager implements Systems Network Architecture/Management
Services (SNA/MS). This architecture defines the approach to managing
communications networks. The protocols used offer a vehicle for monitoring
network operations from a central location.


ΓòÉΓòÉΓòÉ 3.11. Synchronous Data Link Control (SDLC) Nonswitched and Switched Line Support ΓòÉΓòÉΓòÉ

Communications Manager supports SDLC nonswitched line support, which is a
communications protocol for managing information transfer over a
telecommunications line that does not require dialing to establish the
connection.

Communications Manager also supports SDLC switched, which does require dialing
to establish the connection.


ΓòÉΓòÉΓòÉ 3.12. Systems Network Architecture (SNA) Gateway ΓòÉΓòÉΓòÉ

Communications Manager allows multiple users on a LAN, an SDLC switched or
leased link, an X.25 network, or ISDN network to access a System/370* (S/370)
architecture host through an SNA gateway. Up to 254 workstations can be
configured on the LAN supported by the SNA gateway.

A gateway permits communication between hosts that support PU 2.0 workstations
and workstations that use different DLC types.  An SNA gateway can do the
following:

o Act as a protocol converter between workstations that use DLCs on their links
  that are different from the DLC that is used on the host link

o Reduce the amount of system definition at the host and workstations

o Allow you to dynamically change network definitions and add workstations

o Reduce host resources by using pooled LUs, and by automatically logging off
  unused sessions

* Trademark of IBM Corporation


ΓòÉΓòÉΓòÉ 3.13. Twinaxial Data Link Control (TDLC) ΓòÉΓòÉΓòÉ

Communications Manager supports twinaxial data link control (TDLC), which is a
communications function that allows workstations attached to a workstation
controller by way of twinaxial cable to use 5250 emulation and APPC.

Note:  5250 emulation for twinaxial connection is for an IBM Applications
System/400* (AS/400*) only.

*  Trademark of IBM.


ΓòÉΓòÉΓòÉ 3.14. User Profile Management (UPM) Services ΓòÉΓòÉΓòÉ

User Profile Management lets you control access to shared resources, such as
file systems and databases. You can use UPM to create, manage, and view
individual and group user IDs as well as to set authority levels.

In Communications Manager, advanced program-to-program communications (APPC)
and 5250 emulation use UPM to control access to remote computers by requiring
users to log on at the UPM logon window.

The User's Guide contains information about administering and using UPM.  In
addition, the online Command Reference contains descriptions and syntax for UPM
commands that you can type from the OS/2 command line.


ΓòÉΓòÉΓòÉ 3.15. X.25 Network Support ΓòÉΓòÉΓòÉ

Communications Manager supports communications over X.25 packet switching data
networks (PSDNs) using either permanent or switched virtual circuits.  SNA
applications can use this connection through the qualified logical link control
(QLLC). The complete data traffic from all the sessions on an SNA link can be
carried over a single virtual circuit.

In addition, an API for non-SNA communications is provided so that a single
X.25 link can carry a mixture of multiple SNA and non-SNA virtual circuits
concurrently. X.25 is supported within SAA common communications protocol.


ΓòÉΓòÉΓòÉ <hidden> Connecting to Multiple Hosts ΓòÉΓòÉΓòÉ

Communications Manager provides the ability to communicate to multiple hosts
(SSCPs) on separate logical links through unique physical unit (PU)
connections.  This can be useful in the following situations:

o LU 6.2 access to public networks (for example, X.25) of hosts that have not
  installed VTAM* 3.2 or later, and that cannot establish cross-domain links

o LU 0, 1, 2, or 3 access to hosts in different domains, where cross-domain
  configuration is not possible

o Direct routes to multiple hosts when this is more efficient than a route
  through cross-domain links

o Multiple links to the same host for gateway configurations that require more
  than 254 dependent host LUs

* Trademark of IBM


ΓòÉΓòÉΓòÉ <hidden> Managing 3270 and 5250 Sessions ΓòÉΓòÉΓòÉ

Communications Manager provides a way for you to view a list of configured
emulator sessions and to start and stop those sessions.


ΓòÉΓòÉΓòÉ 4. Emulation ΓòÉΓòÉΓòÉ

Communications Manager allows your workstation to emulate, or perform like, a
3270 or 5250 host display terminal, and to establish host printer sessions with
a workstation printer. The type of emulation (3270 or 5250) depends on the type
of host computer you are communicating with.  An individual workstation can be
connected to multiple hosts and perform both types of emulation.

These connections, called emulation sessions, allow you to have access to host
computer functions as if you were using a 3270 or 5250 host display terminal.

3270 and 5250 emulation sessions are managed through Presentation Manager
windows.  As a result, you can change the color, size, and location of an
emulator session window on your screen.  You make these changes either during
configuration, or during runtime through the Menu Bar.

The Menu Bar gives you access to a variety of emulator user functions,
including:

o File transfer to and from host systems

o Host graphics capabilities

o Keyboard remapping

o Color customizing of emulator session screens

o Font size customizing

o Pop-up Keypad function

o Hotspots for mouse usage in emulation sessions

o Numeric Lock function

 In addition, the Menu Bar gives you access to a number of OS/2 features such
as Clipboard and print screen functions. Each emulation session appears in its
own window. All printer sessions appear in a print control window.

Depending on the connections configured for your workstation, you can start:

o 5 coaxial terminal or printer 3270 sessions
o 16 active display sessions for 3270 (For OS/2 2.1, the limit of active
  display sessions is increased to 26.)
o 15 terminal or printer 5250 sessions

You can start up to 26 sessions concurrently, combining 3270 and 5250 terminal
emulations and printer sessions.

Communications Manager supports data compression for 3270 and 5250 emulation
session communications.

The types of connections used for your sessions are shown in the 3270/5250
Session Management window.  Your system administrator can tell you about the
configuration of your workstation and about the session types available to you.


ΓòÉΓòÉΓòÉ 4.1. Menu Bar ΓòÉΓòÉΓòÉ

The Menu Bar, at the top of your emulator session window, gives you access to a
variety of emulator user functions.  The Menu Bar selections are File, Edit,
Transfer, Settings, Keyboard, and Help.  Help is provided for each selection
and for each of the choices they contain.

The System Menu, in the upper left corner of the emulator screen, contains a
Hide/Show Menu Bar option, and a Popup Menu Bar option.


ΓòÉΓòÉΓòÉ 4.2. File Transfer ΓòÉΓòÉΓòÉ

You can send files to a host computer or receive files from a host computer
using 3270 terminal emulation.  This is called a file transfer.  IBM host
computers that use VM, TSO, or CICS system software and have the required file
transfer program installed, support file transfer using 3270 terminal
emulation.

File transfer uses an emulator session to transfer a file. You must be logged
on to the emulator session you want to use for the file transfer.  File
transfer has exclusive use of the session and you cannot interact with the host
application while file transfer is running.

You can send or receive files either of two ways:

o Using the Transfer function, accessible through the Menu Bar
o From the OS/2 command prompt

When you transfer files using Send file or Receive file from the Transfer menu
on the Menu Bar, you specify the file transfer options to be used for the
transfer.  You can name and save sets of options so that you can use them for
other file transfer sessions.

You can also transfer multiple files at once by specifying the name of a file
list you have created.  Even during multiple file transfer each individual file
can have its own set of file transfer options.

The 5250 emulator does not support file transfer between the workstation and
the host computer.  However, file transfer is available when you use the PC
Support programs on AS/400.


ΓòÉΓòÉΓòÉ 4.3. Host Graphics ΓòÉΓòÉΓòÉ

You can use the Graphical Data Display Manager (GDDM) host graphics support in
a 3270 emulation session.  GDDM-OS/2 Link file must be installed on your host
to allow you to download the necessary files to your workstation.

To customize Host Graphics, select Host Graphics from the Settings menu on the
Menu Bar.

For more information, refer to the Graphical Data Display Manager publications.


ΓòÉΓòÉΓòÉ 4.4. Keyboard Remapping ΓòÉΓòÉΓòÉ

The Communications Manager keyboard utility enables you to change key
assignments on the keyboard you use in terminal emulation.  You can customize
key operations to match the keyboard layout you are accustomed to using.

A keyboard layout is the physical arrangement of the keyboard.  In that layout,
functions are assigned, or mapped, to keys.  These key assignments are called
the keyboard mapping.  They are contained in a keyboard profile within a
Communications Manager configuration file.

Communications Manager provides default keyboard mappings for workstations that
use terminal emulation.  You can use these defaults or use the keyboard utility
to change them.

There are two ways to start the keyboard utility program:

o From the Keyboard menu on the Menu Bar

o From the 3270/5250 emulation configuration windows in CMSETUP

Using the keyboard utility, you can:

o Move a definition from a source key to a target key

o Copy a definition from a source key to a target key

o Swap the definitions of a source key and a target key

o Print a copy of the keyboard layout

o Locate keys assigned to a specified function

o Display the current keyboard definitions

o Remap a selected key

A browse function enables you to view the current definitions for each key.


ΓòÉΓòÉΓòÉ 4.5. Color Customizing ΓòÉΓòÉΓòÉ

The foreground and background colors of the 3270 and 5250 emulation sessions
are specified during configuration.  You can accept these default colors or
choose your own.

To choose your own, use the Settings option on the Menu Bar and select Color.

As you select new colors the change is immediately made to the current
emulation session window. This lets you view the effect of your color changes
before you save them.


ΓòÉΓòÉΓòÉ 4.6. Font Size ΓòÉΓòÉΓòÉ

You can change the font size by selecting Settings from the Menu Bar, then
selecting font size.  The font size you select remains active until it is
changed.

The Font Size window allows you to perform the following tasks:

o Accept a font size automatically determined by the emulator program

o Select a font size from the list

The fields and buttons specific to this window are:

o Automatic font selection
o Fixed size

Automatic font selection lets the emulator program automatically assign the
font size according to the window size.

Fixed size allows you to change the font for data displayed in the emulator
session window.


ΓòÉΓòÉΓòÉ 4.7. Pop-up Keypad ΓòÉΓòÉΓòÉ

A popup keypad is a small window containing push buttons, or keys, so that you
can use your mouse to perform keyboard operations.  Communications Manager lets
you define two popup keypads, each with eight push buttons.

To display a popup keypad, place your mouse pointer anywhere in the emulator
session window and click once with mouse button 2. The keypad pops up at the
mouse pointer position.

The push buttons have default assignments, but you can customize your keypads
using the Popup Keypad Setup window, which is accessed from the Menu Bar under
Keyboard.

Use the Popup Keypad Setup window to customize the popup keypads in the
following ways:

o Change a key assignment on a popup keypad
o Display the current settings of a popup keypad
o Select the mode of operation for a popup keypad

You can define a popup keypad to be either sticky or a non-sticky.  A sticky
popup keypad will remain displayed on your screen after an action is completed.
A non-sticky popup keypad will disappear after an action is complete.


ΓòÉΓòÉΓòÉ 4.8. Hotspots ΓòÉΓòÉΓòÉ

A hotspot is the area on a host screen that allows you to use your mouse to
execute a host function or host command without pressing a function key or
typing a command.

The Hotspots Setup window allows you to select the function keys and host
commands that can be activated by using a mouse.

You can access the Hotspots Setup window from the Settings menu on the Menu
Bar.


ΓòÉΓòÉΓòÉ 4.9. Numeric Lock ΓòÉΓòÉΓòÉ

The Numeric Lock window allows you to activate a numeric lock field in a host
application that is running on your 3270 emulator session. If you are working
in a host application containing protected fields that only accept certain
numbers and characters, this feature allows you to "turn off" the rest of the
keyboard while your cursor is in the protected field and minimize the chance
for errors.

This feature is only available for 3270 emulator sessions.


ΓòÉΓòÉΓòÉ 4.10. Data Compression ΓòÉΓòÉΓòÉ

Data compression is the process of compressing repeated characters or repeated
data strings to shorten the length of records or blocks, thus reducing transfer
time for communications.

Communications Manager supports SNA session level data compression with the Run
Length Encoding (RLE) and Limpel-Ziv 9-bit (LZ9) compression algorithms.

With Communications Manager you can specify the use of data compression for
communications over 3270 and 5250 emulation sessions, APPC/APPN sessions, and
LUA sessions. To increase the speed of data transfer, EHLAPPI, APPC, and LUA
now support data compression for LU-LU sessions.

Note:  3270 emulation supports only LZ9 for outbound data streams and RLE for
inbound data streams.


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

The Communications Manager OS/2 3270/5250 emulator now has both single-byte
character set (SBCS) and double-byte character set (DBCS) capability, making
Communications Manager fully-enabled for DBCS.


ΓòÉΓòÉΓòÉ 5. Installation and Configuration ΓòÉΓòÉΓòÉ

When you install Communications Manager, you indicate the directory where you
want the base files to be installed. The next step is to install a
configuration.

Many customers require a program called LAN Adapter and Protocol Support (LAPS)
to make use of Communications Manager. You must install and configure LAPS
before you install Communications Manager in the following situations:

o When you are going to upgrade a Communications Manager configuration that was
  established using OS/2 Extended Edition for use with local area network (LAN)
  Transport.

o When you are going to use Communications Manager to establish connections on
  an integrated services digital network (ISDN).

When you establish a configuration definition, you supply information about the
workstation and your network, and you make selections that indicate how you
want a feature or application to work on the workstation.

Features and Applications That You Can Configure

When you configure one or more of the features or applications for use with
Communications Manager, your workstation can perform the following functions:

o 3270 emulation

o 5250 emulation

o ACDI APIs

o ACDI redirection

o APPC APIs

o CPI Communications

o LUA APIs

o X.25 APIs

o Gateway

Communications Manager Configuration Methods

For 3270 and 5250 emulation, Communications Manager offers two configuration
methods:

o Default Configuration

o Advanced Configuration

When you configure features and applications other than emulation,
Communications Manager automatically uses the advanced configuration method.

After your configuration is created, you can use Keylock to lock or unlock a
configuration.


ΓòÉΓòÉΓòÉ 5.1. Install a Configuration ΓòÉΓòÉΓòÉ

The setup process consists of creating or changing a configuration for your own
workstation or someone else's workstation.

A configuration is a description of the devices, optional features, and
communications settings on your workstation. Communications Manager uses the
information stored in your configuration to establish and manage your network
communications.

o You can use Communications Manager to create your configuration, and then
  install it.

o You can install a configuration created for you by someone else. You must use
  this option if you are running the Communications Manager/2 Distributed
  Feature.

o You can install a configuration created for your workstation with an earlier
  version of Communications Manager.

If you are creating a new configuration, Communications Manager will guide you
through the setup process.  When you finish creating your configuration, you
have the option to install it or to save it to install at a later time.

If you are installing an existing configuration, Communications Manager will
guide you through the installation process. Configurations created with an
earlier version of Communications Manager are automatically upgraded.


ΓòÉΓòÉΓòÉ 5.2. 3270 Emulation ΓòÉΓòÉΓòÉ

Your workstation functions as a 3270 terminal when communicating with an IBM
System/370* host computer. You can configure 3270 emulation for all workstation
connection types except asynchronous.

* Trademark of IBM


ΓòÉΓòÉΓòÉ 5.3. 5250 Emulation ΓòÉΓòÉΓòÉ

Your workstation functions as a 5250 terminal when communicating with an IBM
Applications System/400* or an IBM System/36* host computer. You can configure
5250 emulation for all workstation connection types except asynchronous and
DFT.

*  Trademark of IBM


ΓòÉΓòÉΓòÉ 5.4. ACDI APIs ΓòÉΓòÉΓòÉ

Your workstation with an asynchronous connection uses custom applications that
interact with the functions of the asynchronous communications device interface
(ACDI) provided by Communications Manager.  For example, the Softerm** Custom
Plus ASCII Emulator uses the ACDI API to connect to various networks, such as
the IBM Information network.

**  Trademark of Softronics, Inc.


ΓòÉΓòÉΓòÉ 5.5. ACDI Redirection ΓòÉΓòÉΓòÉ

Asynchronous communications device interface (ACDI) redirection is a
Communications Manager function that allows you to reassign the serial
communication ports on your workstation to asynchronous devices, such as
modems, at a Local Area Network Asynchronous Connection Server (LANACS)
gateway.  By reassigning ports, you can direct data to different destinations,
without changing your hardware configuration.

Your Communications Manager workstation that is connected to a PC Network,
Ethernet (ETHERAND), token ring, or other LAN network, communicates with
asynchronous terminals and other devices by redirecting your serial port to a
LANACS server. You can configure ACDI redirection for all LAN workstation
connection types.


ΓòÉΓòÉΓòÉ 5.6. APPC APIs ΓòÉΓòÉΓòÉ

Your workstation uses the advanced program-to-program communications (APPC)
protocol to communicate with other network stations and to share programs with
those stations. You can configure APPC APIs for all workstation connection
types except asynchronous and coaxial (DFT).


ΓòÉΓòÉΓòÉ 5.7. CPI Communications ΓòÉΓòÉΓòÉ

Your workstation uses the common programming interface communications (CPI-C)
protocols and conventions to communicate with other network stations.  CPI-C is
the application program interface (API) provided with advanced peer-to-peer
networking (APPN).  You can configure CPI-C for all workstation connection
types except asynchronous and DFT.


ΓòÉΓòÉΓòÉ 5.8. LUA APIs ΓòÉΓòÉΓòÉ

Your workstation uses custom applications that interface with and use the
functions of logical unit (LU) programming. You can configure LUA APIs for all
workstation connection types except asynchronous and coaxial (DFT).


ΓòÉΓòÉΓòÉ 5.9. X.25 APIs ΓòÉΓòÉΓòÉ

Your workstation uses custom applications that use the functions of the X.25
network protocol.


ΓòÉΓòÉΓòÉ 5.10. Default Configuration ΓòÉΓòÉΓòÉ

This is the standard method that you use to configure 3270 or 5250 emulation on
the following workstation connection types:

o Ethernet (ETHERAND) network

o PC Network

o SDLC (synchronous data link control)

o Token ring or other LAN types

o Twinaxial.

With default configuration, Communications Manager relies on a set of assumed
defaults to set up the configuration definitions.  You have to supply only the
information that is unique to your workstation and your network, such as the
destination address and the local node name.

You can set up your workstation quickly for emulation, without having to make a
lot of decisions, by using the assumed defaults.


ΓòÉΓòÉΓòÉ 5.11. Advanced Configuration ΓòÉΓòÉΓòÉ

When you use this method, you complete a set of profiles in which you select
and supply information to make the emulation perform efficiently for your
communication needs.

When you want to tailor Communications Manager emulation operations to the
special needs of your workstation or your network, advanced configuration is
the best method.

Note:  Communications Manager automatically uses the advanced configuration
method if you select several features or applications in one configuration.


ΓòÉΓòÉΓòÉ 5.12. Gateway ΓòÉΓòÉΓòÉ

This choice displays a list of the profiles you use to configure the
workstation as a gateway. A gateway is a workstation that translates addresses
between the network host computer and the workstations on your network.


ΓòÉΓòÉΓòÉ 6. Application Programming Interfaces ΓòÉΓòÉΓòÉ

Communications Manager provides a number of application program interfaces
(APIs) to address the communication needs for connections to both IBM and
non-IBM computers. All of the APIs are accessible from both full-screen and
windowed applications.

o Emulator High-Level Language Application Programming Interface (EHLLAPI)

o Server-Requester programming interface (SRPI)

o Conventional LU application (LUA)

o Advanced program-to-program communications (APPC)

o SAA common programming interface (CPI) for communications

o System management

o Asynchronous communications device interface (ACDI) and ACDI Redirection APIs

o X.25

o Communications Manager Kernel

o Common services

o Service Point Application Router/Remote Operations Service (SPAR/ROPS)

o ISDN Connection Manager Interface (CMI)

o Generalized Call Control Interface (GCCI)

o IBM Realtime Interface CoProcessor Device Driver Programming Interface


ΓòÉΓòÉΓòÉ 6.1. Communications Manager Kernel ΓòÉΓòÉΓòÉ

The Communications Manager kernel is the main component of Communications
Manager.  The kernel stops and starts other Communications Manager components
and provides services that the components need.  The kernel provides
Communications Manager status reporting services.

The kernel API allows application programs to use kernel services.  The kernel
API calls perform the following tasks:

o Loading and unloading the kernel

o Activating and deactivating service requests

o Querying Communications Manager status

o Retrieving an active directory name from the Communications Manager
  environment.


ΓòÉΓòÉΓòÉ <hidden> Asynchrous Communications Device Interface (ACDI) and ACDI Redir. APIs ΓòÉΓòÉΓòÉ

Communications Manager provides a programming interface for asynchronous
communications and provides ACDI functions that do the following:

o Provide device independence and support a variety of asynchronous
  communications devices and connection types such as:

   - Switched and non-switched lines

   - Modems (auto-dial, auto-answer, manual dial, manual answer)

   - Direct connections

o Support asynchronous communications device command sets:

   - Attention command set (an IBM-supplied and user-edited device command set
     that supports Hayes** Smartmodem** and compatibles)

   - CCITT V.25bis command set (an IBM-supplied and user-edited device command
     set that supports V.25bis)

   - No command set (a user-supplied device command set that supports circuits
     that adhere to CCITT V.24)

o Support traditional asynchronous communication protocols such as:

   - Flow control

   - Break processing

o Support two dissimilar external devices attached through an A/B switch

o Provide ports for resource management:

   - Three asynchronous ports for computers with MicroChannel* buses (COM1,
     COM2, COM3)

   - Two asynchronous ports for computers with AT type buses (COM1, COM2)

o Provide communications and system management (C & SM) support

o Provide flexible input and output interfaces for data transfers

o Manage application buffers for transmitted and received data

o Provide asynchronous port sharing where auto-answer and auto-dial are
  allocated to the same port

o Assist country requirements for connecting computers to telephone networks.

Communications Manager enables users to access a range of computers, including
IBM and non-IBM host computer systems. In addition, several connections can be
active concurrently, giving users rapid access to information from any point in
a network.

The Asynchronous Communications Device Interface (ACDI) can be redirected to an
IBM Local Area Network Asynchronous Connection Server (LANACS) Version 2.0.
LANACS is an IBM DOS product that provides asynchronous connection server
capability to a LAN.  The server that runs the LANACS program provides
asynchronous resource (serial ports, asynchronous connection equipment, and
telephone lines) that can be shared by workstations on a LAN.  An Operating
System/2* (OS/2*) workstation on the LAN can use serial ports on the
asynchronous connection server as if the serial ports were located at the
workstation.

ACDI is the programming interface that provides support for those who want to
use the serial ports for asynchronous communications in a multitasking
environment.  ACDI interacts with the serial ports through the base operating
system and ensures that interrupts are handled and data is buffered for
applications as required.

*  Trademark of IBM.

** Trademark of Hayes Microcomputer Products, Inc.


ΓòÉΓòÉΓòÉ 6.2. Advanced Program-To-Program Communications (APPC) ΓòÉΓòÉΓòÉ

Communications Manager provides advanced peer-to-peer networking (APPN) end
node and network node support for workstations, allowing them to communicate
more flexibly with other systems in the network.

Communications Manager provides advanced program-to-program communications
(APPC) to support communications between distributed processing programs,
called transaction programs (TPs).  APPN extends this capability to a
networking environment.  The TPs can be located at any node in the network that
provides APPC.

Communications Manager improves APPC throughput in performance-critical local
area network (LAN) environments. If you plan to install Communications Manager
on a LAN, LAN adapter and protocol support (LAPS) is required.

The level of LAPS shipped with Network Transport Services/2 (NTS/2) Version 1.0
or LAN Server Version 3.0 is recommended; however, Communications Manager also
supports the levels of LAPS available with LAN Server Version 2.0 and Extended
Services for OS/2. Communications Manager supports the following protocols for
APPC:

o IBM Token-Ring Network

o 3174 Peer Communications (LAN over coaxial support)

o Token-Ring Bus Master

o Synchronous Data Link Control (SDLC)

o IBM PC Network*

o Twinaxial

o Ethernet (ETHERAND)

o X.25


ΓòÉΓòÉΓòÉ 6.3. System Management ΓòÉΓòÉΓòÉ

System management allows a system administrator to control and obtain status
information about the SNA communication resources maintained by Communications
Manager. It allows activation and deactivation of sessions and data link
controls.

System management provides verbs that perform display, subsystem management,
configuration, management services, and node definition functions. The
following list provides a brief description of the system management verbs:

o Display verbs

  Display verbs allow you to display general configuration information and
  current operating values for SNA node.

o Subsystem management verbs

  The subsystem management verbs provide programs with a method for managing
  sessions, links, and the APPC attach manager.

o Configuration verbs

  Configuration verbs allow authorized programs to configure resources such as
  LUs and TPs.

o Management services verbs

  Management services verbs provide programs with a method of reporting
  potential problems to management services focal points.


ΓòÉΓòÉΓòÉ 6.4. ISDN Connection Manager Interface (CMI) ΓòÉΓòÉΓòÉ

Connection manager interface (CMI) is an interface that allows user
applications to communicate with connection manager for the purpose of
establishing connections (outgoing and incoming) across a switched network to
remotely attached host computers and other workstations.

Communications Manager provides a virtual media access control (MAC) driver for
each supported protocol stack so that the application at the CMI can
dynamically determine which protocol and logical adapter to use when the call
instance (from the time you call, to the time you hang up) becomes active.
This allows the actual data channels to be independent from protocols and
logical adapter numbers.

CMI provides support for the following protocols:

o Integrated data link control (IDLC)

o Synchronous data link control (SDLC)

o X.25

o LAN

   - IEEE 802.2
   - NetBIOS

CMI provides automatic dialing and automatic answering capability for
applications written to the X.25 interface and to the APPC interfaces (LUA,
EHLLAPI, CPI Communications, and LU 6.2).

Note that the 3270 and 5250 emulation features provided by Communications
Manager are considered to be APPC applications.  SNA manages call control for
IDLC and SDLC.  X.25 call control is managed by the X.25 feature.
Communications Manager does not provide automatic dialing and automatic
answering capability for the LAN interfaces (IEEE 802.2, NetBIOS, Named Pipes
API, and Remote Procedure Call {RPC} API).  Applications written to these
interfaces can be modified to use CMI if they require automatic dialing and
automatic answering capability or can use the Communications Manager dial
utilities to establish the physical connection by sidestream dialing.

*  Trademark of IBM.


ΓòÉΓòÉΓòÉ 6.5. Common Services ΓòÉΓòÉΓòÉ

The common services programming interface verbs are available to all
application programs that use the Communications Manager APIs.

The common services verbs perform the following tasks:

o Enable and disable X.25 physical links

o Provide American National Standard Code for Information Interchange (ASCII)
  to extended binary-coded decimal interchange code (EBCDIC), EBCDIC to ASCII,
  and user-defined conversions on data streams

o Format data in the trace storage buffer and copy the data to a specified file

o Provide dumping for user-selected components and provide specification of the
  file to which dump data is written

o Trace API verbs and data

o Display configuration information and operating values for active SNA nodes

o Produce the translation table for specified code pages so user programs can
  perform table lookup on characters to convert character strings

o Record messages in the FFST/2 message log

o Send message and error logs to a user-supplied queue

o Send network management services messages to a network management services
  control point.


ΓòÉΓòÉΓòÉ 6.6. Conventional LU Application (LUA) ΓòÉΓòÉΓòÉ

LUA shares a physical unit with the 3270 emulator, the gateway function, and
the advanced program-to-program communications APPC API.  LUA extends the
capabilities of Communications Manager by supplying two APIs:

o Request-unit interface, a basic interface

o Session-level interface, a higher-level interface.

LUA provides secondary support only for BIND LU types 0, 1, 2, or 3. The type
of SNA BIND profiles that are supported for LU-LU sessions depends on the
access method used.

The services that LUA provides to application programs include only those
supporting data communications. LUA does not provide any device emulation
facilities. However, LUA does provide a unique subset of presentation services
(PS) functions.

LUA communications-connectivity requirements include the following IBM host
systems:

o AS/400
o S/36
o S/38
o S/370

*  Trademark of IBM.

LUA permits host attachment by the following:

o Synchronous data link control (SDLC)
o Token-ring network
o X.25
o IBM PC network protocol (using a gateway)
o Ethernet (ETHERAND) network protocol (using a gateway)
o 3174 Peer Communications
o Token-ring bus master
o Integrated services digital network (ISDN)

   - SDLC
   - X.25
   - IDLC


ΓòÉΓòÉΓòÉ 6.7. Emulator High-Level Language Application Programming Interface (EHLLAPI) ΓòÉΓòÉΓòÉ

The Emulator High-Level Language API (EHLLAPI) is an application programming
interface that allows workstation programs to interact with a host using 3270
or 5250 emulation.

An EHLLAPI application program acts as a programmed operator (a program that
performs and monitors activities in a workstation that are usually done by a
human).  An EHLLAPI application program can perform some or all of the
following functions:

o Automate repetitive tasks

o Mask complete applications from the user

o Consolidate several complicated tasks into one simple task

o Simplify existing host applications

o Monitor response time and availability

o Monitor events that are diverse in nature

o Automate console operations

In addition, EHLLAPI facilitates communication from workstation application
programs to host application programs using the 3270 data stream structured
fields.  This allows for the generation of programs such as the file transfer
applications used to transfer files between host and workstation environments.


ΓòÉΓòÉΓòÉ 6.8. Generalized Call Control Interface (GCCI) ΓòÉΓòÉΓòÉ

GCCI provides an interface to a port connection manager (PCM) so that the
connection manager can manage the PCM resources and coordinate the
establishment and disconnection of physical connections.  Each port on the
network has its own PCM that is responsible for controlling access to the
switched network.


ΓòÉΓòÉΓòÉ 6.9. IBM Realtime Interface CoProcessor Device Driver Programming Interface ΓòÉΓòÉΓòÉ

The IBM Realtime Interface Co-Processor device driver is used by the base
operating system to support the Realtime Interface Co-Processor family of
communication adapters, including the following adapters:

o Realtime Interface Co-Processor 2 Port

o Multiport

o Multiport Model 2

o Multiport/2

o PortMaster

o X.25

The device driver programming interface is available with Communications
Manager for users who want to provide their own programming support for the
co-processor adapter.  The main functions of the device driver are to:

o Handle interrupts from the co-processor adapter

o Determine which task on which co-processor adapter interrupted the system
  unit, and signal the appropriate system unit processes

o Read the parameter file and configure the co-processor adapter accordingly

o Provide a programming interface to the co-processor adapter through the
  generic input/output control (IOCtl) interface or through a set of dynamic
  link libraries (DLL)


ΓòÉΓòÉΓòÉ 6.10. SAA Common Programming Interface (CPI) for Communications ΓòÉΓòÉΓòÉ

The Systems Application Architecture (SAA) Common Programming Interface for
Communications (CPI Communications) provides an alternative method of
program-to-program communications that uses SNA LU 6.2 facilities.

SAA describes a set of software interfaces, conventions, and protocols that
provide a framework for designing and developing portable applications.
Applications that follow SAA guidelines are easily integrated and will run on
any hardware and software platform that provides an SAA environment.

Both advanced program-to-program communications (APPC) and CPI Communications
support transaction programs (TPs) that use Communications Manager APPC
support. CPI Communications TPs, however, call SAA CPI Communications functions
rather than issue APPC verbs.

The CPI Communications functions and APPC verbs provide similar services.
However, CPI Communications provides an API that is portable across multiple
SAA platforms.

CPI Communications provides calls for applications that require
program-to-program communication. It makes use of SNA LU 6.2 facilities that
include:

o Starting a partner TP on a remote system

o Sending or receiving data with a partner TP

o Notifying a partner TP that an error has been detected

o Synchronizing partner TPs


ΓòÉΓòÉΓòÉ 6.11. Server-Requester Programming Interface (SRPI) ΓòÉΓòÉΓòÉ

The SRPI is a high-level API that allows programmers to write SRPI requester
programs that request servers to perform tasks.  The SRPI API also supports
ECF.

ECF is a set of programs for interconnecting IBM workstations and IBM
System/370 host computers operating in the MVS/XA or VM/SP environment.

IBM ECF simplifies the way different systems use services over a connection.
ECF provides a single interface that allows application programmers to write
workstation and host applications that run on a variety of communication
connections.

SRPI has the following characteristics:

o An interface for application programs in a workstation to request services,
  data, or both from a host.  The requesting program is referred to as the SRPI
  requester.

o An interface for programs in a host to reply to requests for services, data,
  or both from workstations.  The program that services the request is referred
  to as the server.

The SRPI requester and server programs operate in pairs, with the SRPI
requester in the workstation and the server in the host computer.

The SRPI router is a Communications Manager facility that uses information
defined in the SRPI server profiles to route send requests to server programs
using the appropriate 3270 sessions.


ΓòÉΓòÉΓòÉ 6.12. Service Point Application Router/Remote Operations Service (SPAR/ROPS) ΓòÉΓòÉΓòÉ

A network management API allows you to initiate the processing of host NetView
program commands from OS/2 programs.

Communications Manager lets you initiate workstation commands from the host
NetView program. The standard output of the commands is returned to the host
NetView program.

Two Communications Manager components provide this network management
capability:  Service Point Application Router (SPA Router) and Remote
Operations Service (ROP Service). SPA Router and ROP Service provide the
following features:

o Support for multiple LANs and multiple physical units (PUs)

o Administration of wide area networks

o System administration functions

o Administration of different domains

SPA Router is an OS/2 program that receives commands from the host NetView
program and sends them to the specified application programs.  SPA Router can
receive commands for multiple OS/2 applications concurrently.

ROP Service processes, on the workstation, commands that the host NetView
program sends through SPA Router.  ROP Services can process any OS/2 command
that has a command line interface and that does not require operator input.


ΓòÉΓòÉΓòÉ 6.13. X.25 ΓòÉΓòÉΓòÉ

The X.25 API enables non-SNA application programs to communicate with
workstations, IBM hosts, and non-IBM hosts, using X.25 networks.

X.25 packet switching data networks (PSDNs) are wide area networks (WANs) that
usually connect workstations and computers over large geographical distances.
An X.25 network subscriber can make calls to other subscribers and can have
many calls in operation at the same time. Most public X.25 networks are
interconnected, enabling world-wide international calling. Many corporations
have their own private networks, while some are connected to public networks.

Data is transmitted over an X.25 network in discrete, independent units called
packets. Packets are sent over virtual circuits set up through the X.25
network. Because virtual circuits are duplex, packets can be flowing in both
directions at the same time.

The placing of data in packets and the use of virtual circuits instead of real
circuits enables a PSDN to dynamically and optimally manage its real resources.
Packets from different virtual circuits can be multiplexed on the same
communication line by the PSDN. However, to a network subscriber, a virtual
circuit appears to be a dedicated line. A workstation may only need one
physical link to communicate with many other workstations and computers because
the link can carry many virtual circuits concurrently.

This optimal use of resources can result in communications equipment savings
which can, in turn, result in cheaper communications costs for the X.25 network
subscriber.


ΓòÉΓòÉΓòÉ 7. Problem Diagnosis ΓòÉΓòÉΓòÉ

Communications Manager provides the following information to assist in problem
diagnosis:

o Messages
o Errors
o Alerts
o Traces
o Dumps

Communications Manager provides the following problem diagnosis facilities to
display and interpret problem diagnosis information:

o FFST/2
o Problem Determination Aids
o Common Services Application Programming Interface


ΓòÉΓòÉΓòÉ 7.1. Messages ΓòÉΓòÉΓòÉ

Messages are displayed during Communications Manager sessions.  The appearance
of a message does not always mean an error occurred.  For example, a message
may tell you that an operation is in progress or complete.

Online help is available for Communications Manager messages. In addition,
detailed descriptions of all Communications Manager messages, their causes, and
actions you should take are available in the Message Reference.  You can access
this reference online by selecting it from the Communications Manager/2 folder.

Communications Manager message types and the actions you should take to respond
to them are:

o Information message
o Warning message
o Action message
o File transfer message (TRANS prefix)
o OIA message
o Device driver message

Messages and message helps are logged and displayed in the following ways:

o Pop-up Window
o Message Console
o Message Log Formatter


ΓòÉΓòÉΓòÉ <hidden> Information Message ΓòÉΓòÉΓòÉ

An information message appears if a situation occurs and there is no action you
must take in response to the situation.


ΓòÉΓòÉΓòÉ <hidden> Warning Message ΓòÉΓòÉΓòÉ

A warning message appears if a situation exists that you should be made aware
of. Some warning messages include corrective actions you can take if you decide
to modify the situation.


ΓòÉΓòÉΓòÉ <hidden> Action Message ΓòÉΓòÉΓòÉ

An action message appears if a situation arises in which you must take some
explicit action to correct the situation, or choose an alternative action.
Correct the situation by taking the action provided with the message.  If
instructions are not provided, select Help to view an explanation of the
situation and the corrective action you can take for it.


ΓòÉΓòÉΓòÉ <hidden> File Transfer Message (TRANS prefix) ΓòÉΓòÉΓòÉ

A file transfer message appears during file transfer with a 3270 host to report
the current status of the transfer.


ΓòÉΓòÉΓòÉ <hidden> OIA Message ΓòÉΓòÉΓòÉ

OIA messages appear on the operator information area (OIA) line at the bottom
of the 3270 or 5250 session window. This area provides information about
sessions and presentation space printing, including status and error messages.
Host application programs also use this line to display messages that explain
keystroke errors (although some programs may use a different line).

You can use the online help information provided during a session to determine
the causes and actions for those messages:

o If your host computer is an AS/400, the host automatically displays help
  information when you make a keystroke error.

o If your host computer is an IBM System/36* (S/36*), press the Help key to
  display help information about an error code.

o Select OIA message from the menu bar for additional OIA message information.

Press the Error Reset key to return to the OIA display for 5250 sessions.

*  Trademark of IBM.


ΓòÉΓòÉΓòÉ <hidden> Device Driver Message ΓòÉΓòÉΓòÉ

Device driver messages appear during startup of the workstation.


ΓòÉΓòÉΓòÉ 7.2. Errors ΓòÉΓòÉΓòÉ

Errors are unexpected results that occur during a Communications Manager
operation which require more detailed information than can be provided in a
message.  Errors are logged in the system error log.


ΓòÉΓòÉΓòÉ 7.3. Alerts ΓòÉΓòÉΓòÉ

Alerts are information units sent to a management services focal point in a
network to identify problems or impending problems. Alerts are logged in
EPWALERT.DMP, which you can view by using the FFST/2 dump formatter.

See the Problem Determination Guide for more information about alerts.


ΓòÉΓòÉΓòÉ 7.4. Traces ΓòÉΓòÉΓòÉ

Traces are records of data that provide a history of events that occurred
during communications.  Select Problem determination aids in the Communications
Manager/2 folder to obtain trace information.

See the Problem Determination Guide for more information about traces.


ΓòÉΓòÉΓòÉ 7.5. Dumps ΓòÉΓòÉΓòÉ

Dumps are copies of data stored in a portion of memory being used by
Communications Manager components. Select Problem determination aids in the
Communications Manager/2 folder to obtain dump information.

See the Problem Determination Guide for more information about dumps.


ΓòÉΓòÉΓòÉ <hidden> Pop-Up Window ΓòÉΓòÉΓòÉ

Usually the first indication of a problem is when a message appears in a pop-up
window to let you know that a situation has occurred which may require your
attention.  In most cases, help is available from this window.


ΓòÉΓòÉΓòÉ <hidden> Message Console ΓòÉΓòÉΓòÉ

The message console is a window that you can activate to view messages as they
are logged.  This service provides a similar function to the message log;
however, no help is provided for the messages and the window's contents are
erased when closed.

For Communications Manager, use the message log formatter as the focal point
for problem diagnosis and use the message console for configuring FFST/2.


ΓòÉΓòÉΓòÉ <hidden> Message Log Formatter ΓòÉΓòÉΓòÉ

The message log formatter provides access to the Communications Manager
messages that are stored in the default FFST/2 message log (OS2MLOG.DAT) and in
other message logs defined by Communications Manager.

When you receive a message, view the message in the message log formatter.
Read the entire message and the message help and perform the actions indicated.
If the message instructs you to look in the system error log or the FFST/2 dump
formatter, note the time of the message and the problem ID to help you access
the appropriate entries in the system error log and the dump formatter.


ΓòÉΓòÉΓòÉ <hidden> FFST/2 ΓòÉΓòÉΓòÉ

First Failure Support Technology/2* (FFST/2*) is a software problem diagnosis
tool for OS/2 system software and applications.  It is designed to facilitate
the capture of problem diagnosis information when a problem occurs.

The following FFST/2 facilities are in the FFST/2 folder:

o Start FFST/2
o Stop FFST/2
o Message Console
o System Error Log
o Dump Formatter
o Message Log Formatter

Unless you are an advanced user, your primary use of FFST/2 will be the system
error log and the message log formatter choices. Refer to the Problem
Determination Guide for a complete description of the tasks you can perform
with FFST/2.

*  Trademark of IBM.


ΓòÉΓòÉΓòÉ <hidden> Start FFST/2 ΓòÉΓòÉΓòÉ

Select the Start FFST/2 icon in the FFST/2 folder to start the FFST/2 process.
Add RUN=EPW to CONFIG.SYS file to start this process at system startup.


ΓòÉΓòÉΓòÉ <hidden> Stop FFST/2 ΓòÉΓòÉΓòÉ

Select the Stop FFST/2 icon in the FFST/2 folder to stop the FFST/2 process.

Note:  This is not recommended because problem diagnosis information may not be
processed.  However, in many cases, Communications Manager will restart FFST/2
if a problem occurs.


ΓòÉΓòÉΓòÉ <hidden> System Error Log ΓòÉΓòÉΓòÉ

The system error log is an OS/2 facility that contains information about the
problem and the environment in which the problem occurred. Messages logged to
the message log formatter often describe how to extract information from the
system error log; therefore, always check the message log formatter before
checking the system error log.

Note:  If you are using OS/2 Version 2.0 or higher, you must install the OS/2
Serviceability and Diagnostic Aids to enable Communications Manager system
error logging.


ΓòÉΓòÉΓòÉ <hidden> Dump Formatter ΓòÉΓòÉΓòÉ

The dump formatter is a customized dump facility that can contain detailed
information about a failure and the environment in which it occurred.
Communications Manager uses this facility to supply and format detailed
information about alerts.


ΓòÉΓòÉΓòÉ <hidden> Problem Determination Aids ΓòÉΓòÉΓòÉ

Problem Determination Aids is a problem diagnosis facility in Communications
Manager that provides trace and dump services.

Use trace services to trace application programming interfaces (APIs) and data
transmitted on communication links.

Use dump services to make copies (or a dump) of the data stored in portions of
memory used by Communications Manager for analysis by IBM.

Problem Determination Aids is installed as additional function.


ΓòÉΓòÉΓòÉ 8. Hints and Tips ΓòÉΓòÉΓòÉ

You can use these hints and tips when using Communications Manager. Refer also
to the README file for more hints and tips.

Select one of the following for more information:

o Installation

o CMSETUP Options

o Virtual device driver support

o Sample Programs

o Configuration

o Configuration, Installation, and Distribution (CID)

o Gateway and multiple PU support

o Command Enhancements

o ACDI Redirection Upgrade Restriction


ΓòÉΓòÉΓòÉ 8.1. Installation ΓòÉΓòÉΓòÉ

For additional installation information, read the README file on the
installation diskettes (or in the redirected installation directory).  This
file contains any last-minute documentation updates.

For more hints and tips about installation, select one of the following:

o LAPS installation

o Upgrade from a previous version


ΓòÉΓòÉΓòÉ 8.1.1. LAPS Installation ΓòÉΓòÉΓòÉ

LAN Adapter and Protocol Support (LAPS) is a component that allows you to
configure and make changes to your network adapters and protocols for the
purpose of enhancing network performance.

Communications Manager installation verifies that LAPS is installed, but it
does not verify that LAPS is properly configured.

If one of the following products has been installed on your workstation, an
acceptable version of LAPS may already be available; however, only NTS/2
provides the level of LAPS support necessary for using ISDN.

o IBM Extended Services for OS/2

o IBM TCP/IP for OS/2

o IBM LAN Server (or LAN Requester)

o IBM Network Transport Services/2


ΓòÉΓòÉΓòÉ 8.1.2. Upgrade from a Previous Version ΓòÉΓòÉΓòÉ

If you are migrating from a previous version of Communications Manager, and you
are planning to install on a different drive:

o Remove the previous version using the REINST command. If this is not done,
  the files from the previous version remain on the drive although they are not
  usable.

o Remove any Communications Manager-dependent products such as GDDM-OS/2 Link.
  The HGREMOVE command erases the GDDM-OS/2 Link files.

o Remove any references to the former product from the LIBPATH, PATH and DPATH
  statements in your CONFIG.SYS file.

o Back up data files, such as the configuration files. They can be migrated and
  used by this release of Communications Manager/2.

Note:  It is advisable to back up your CONFIG.SYS before modifying it.


ΓòÉΓòÉΓòÉ 8.2. CMSETUP Options ΓòÉΓòÉΓòÉ

CMSETUP and CMREDIR provide the following options from the menu bar. Select any
option for additional information.

o Install additional functions...

o Remove additional features...

o Reinstall...

o Remove Communications Manager...

o Remove communications features...

o View system information...

o View audit trail...

o Recreate folders...


ΓòÉΓòÉΓòÉ 8.2.1. Install Additional Functions ΓòÉΓòÉΓòÉ

Install additional functions... allows you to add a variety of functions and
online documents.

As you select the items you want to install, the required disk space and the
space you have available display in the Install Additional Functions window.

For information on these functions, refer to the Workstation Installation and
Configuration Guide


ΓòÉΓòÉΓòÉ 8.2.2. Remove additional functions ΓòÉΓòÉΓòÉ

Remove additional features... allows you to remove any of the functions or
online documents that were previously installed.  You can select the functions
or online documents to remove from a displayed list.


ΓòÉΓòÉΓòÉ 8.2.3. Reinstall ΓòÉΓòÉΓòÉ

Reinstall reinstalls the base Communications Manager/2 product and any
components necessary for the selected functions.  This option is used when
Communications Manager/2 files have been erased or damaged.


ΓòÉΓòÉΓòÉ 8.2.4. Remove Communications Manager/2 ΓòÉΓòÉΓòÉ

Remove Communications Manager/2... removes the product from your workstation.
First failure support technology (FFST) and user profile management (UPM) are
not removed.  The \CMLIB directory remains on the target drive with any other
files that you have added, such as configuration files for the Graphical Data
Display Manager-OS2 (GDDM-OS2) Link files.

As a final step in the removal process, the \CMLIB\CM.LOG which contains the
audit trail is reset to indicate that the product has been removed.  All prior
installation history is erased.


ΓòÉΓòÉΓòÉ 8.2.5. Remove Communications Features ΓòÉΓòÉΓòÉ

Remove communications features... removes all files associated with
configuration files other than your default configuration.  Features are major
components of Communications Manage/2 such as 3270 emulation, 5250 emulation,
or the gateway.

Choosing this options also allows you to remove any statements in CONFIG.SYS
that are specific to removed configurations.  The actual configuration files
remain untouched and can be reloaded at any time by selecting Installation in
the Communications Manager Setup window.

Warning: All of the new network graphic images are held in the \CMLIB\*.MET
files.  In general, it is not advisable to remove Communications Manager
configurations by doing an ERASE\CMLIB\cfgname.* as this could destroy files
not related to your configuration.  This is particularly true now as many of
the MET files have relatively common names such as 5250X25.MET.  If you happen
to have a 5250X25.CFG and you erase it with the above command, then you would
lose the 5250 over X.25 image also.  It is safer to use a file utility, such as
the OS/2 File Manager, to identify each file to be erased.


ΓòÉΓòÉΓòÉ 8.2.6. View System Information ΓòÉΓòÉΓòÉ

View system information... displays the:

o Communications Manager version number
o Workstation type
o Default configuration
o Configuration path


ΓòÉΓòÉΓòÉ 8.2.7. View Audit Trail ΓòÉΓòÉΓòÉ

View audit trail... displays a record of every Communications Manager feature
that is installed.  The audit trail is a specific Communications Manager file
called \CMLIB\CM.LOG.  Error messages are also logged here during the initial
installation steps before FFST/2 is available.


ΓòÉΓòÉΓòÉ 8.2.8. Recreate folders ΓòÉΓòÉΓòÉ

Recreate folders... allows you to recreate a folder and objects in the folder.
This is useful if you have accidentally deleted the objects.


ΓòÉΓòÉΓòÉ 8.3. Virtual Device Driver Support ΓòÉΓòÉΓòÉ

When you use OS/2 Version 2.0 or later and Communications Manager/2, support is
available for virtual device drivers.  This allows a DOS program to
simultaneously use a device driver with an OS/2 program.  This support is
currently available for the following interfaces:

o Emulator high level language application programming interface (EHLLAPI)

o 802.2

o Local area network basic input/output system (NetBIOS)

The support for the virtual 802.2 and NetBIOS interfaces is supplied by IBM
network transport services/2 (NTS/2).

Communications Manager provides the virtual EHLLAPI interface. Installation
consists of typing VHAPINST from a windowed or fullscreen OS/2 session.


ΓòÉΓòÉΓòÉ 8.4. Sample Programs ΓòÉΓòÉΓòÉ

The sample programs are provided on the API Support Diskette which is
distributed with the Application Programming Guide. This publication is ordered
separately.

The sample programs are provided as a tool to aid in the development of
programs that use Communications Manager application programming interfaces
(APIs).

The sample programs are installed by decompressing the ZIP files. Refer to the
README.DOC file on the API Support Diskette for additional information.


ΓòÉΓòÉΓòÉ 8.5. Configuration ΓòÉΓòÉΓòÉ

There are three methods to create or change a Communications Manager
configuration.  For more information on any of these methods, select one of the
items below.

o Using interactive configuration (CMSETUP)
o Using CID Response Files
o Editing the .NDF file

Note:  IBM Extended Services for OS/2 Programmable Configuration has been
replaced by CID.

Select an item below for additional configuration information.

o Using the configuration program
o Verifying configuration files
o Copying configuration profiles
o Other configuration concerns


ΓòÉΓòÉΓòÉ 8.5.1. Gateway and Multiple PU Support ΓòÉΓòÉΓòÉ

Some benefits of a gateway are:

o Reducing the host PU definitions

o Eliminating communications links

o Reducing the host system load due to less PU polling.

o Allowing for protocol conversion between the host and the dependent
  workstations

Communications Manager/2 has made a number of changes in the gateway support:

o Gateway configuration is easier and less error-prone due to the OS/2
  Presentation Manager configuration interface (CMSETUP).

o Downstream workstations can now be defined using models.

o Several host systems can now be defined with multiple PU support.

o The SNA gateway supports up to 254 concurrently active workstations (logical
  units) per host on the LAN.  Communications Manager/2 supports up to five
  concurrent physical host connections.

o Host and workstation definitions can now be done directly in the .NDF file.

o Host and workstation definitions can be changed dynamically.

For information on gateway restrictions, refer to the Restrictions chapter of
this Overview, and the README file.

Select one of the following items for additional gateway information.

o The CMGWSESS Utility
o Suggestions


ΓòÉΓòÉΓòÉ 8.5.2. The CMGWSESS Utility ΓòÉΓòÉΓòÉ

The CMGWSESS utility is available for downstream dependent workstations on a
gateway.  CMGWSESS is executed on the dependent workstation and it displays
information concerning all sessions with the gateway node.

All of the information returned by CMGWSESS is available on the gateway
machine.  It could be useful for the user on the dependent workstation,
however, if the gateway machine is not physically accessible.  It allows the
user to get information concerning the LUs and host system which might be
helpful to identify network problems.

CMGWSESS relies upon the ability to initiate an LU 6.2 conversation with the
(Remote Display Server) program on the gateway machine. The LU 6.2 sessions in
fact show up in the data produced by CMGWSESS.  This implies that the gateway
machine must be appropriately customized for accepting an APPC conversation.


ΓòÉΓòÉΓòÉ 8.5.3. Suggestions ΓòÉΓòÉΓòÉ

Gateway host LU pool selection

You assign a name when you create a new pool.  It is advisable to include an
indication of the host name within the eight character pool identification.
This is recommended because of the gateway session information displayed within
the subsystem management application.


ΓòÉΓòÉΓòÉ 8.5.4. Using Interactive Configuration (CMSETUP) ΓòÉΓòÉΓòÉ

You can create or change a Communications Manager configuration using
interactive configuration, which is the CMSETUP command.  Information is
entered using a series of Presentation Manager windows.  When you complete a
configuration, an automatic verification step examines the configuration files
you created and if no conflicts exist, creates the required configuration
files.  If there are conflicts, errors are saved in a log file.  You can then
choose to correct the errors in the configuration.

Most workstation configuration can be created using CMSETUP; however, a few
verbs and some parameters of other verbs are not supported by CMSETUP.  Refer
to Network Administration and Subsystem Management Guide for a list of these
verbs and parameters.


ΓòÉΓòÉΓòÉ 8.5.5. Using CID Response Files ΓòÉΓòÉΓòÉ

You can create or change a Communications Manager configuration using the
Configuration, Installation, and Distribution (CID) response files. You can use
the response files to configure almost all of the Communications Manager
configuration parameters.  The CMRECORD utility creates a response file from a
configuration.  The model configuration can be a configuration that you want to
upgrade or a configuration that was created with CMSETUP.  You can
automatically create a configuration on a workstation with CMSETUP using the
response files.

Creating configurations with CID is generally the responsibility of the network
administrator.


ΓòÉΓòÉΓòÉ 8.5.6. Editing the .NDF File ΓòÉΓòÉΓòÉ

The node definitions file (.NDF) allows you to change your node configuration
using a text editor.  This is useful when you want to:

o Make a quick change to a verb parameter

o Duplicate an .NDF file quickly

o View the configuration verbs

o Specify configuration verbs and parameters not supported by CMSETUP

  Note:  Only experienced Communications Manager users should modify the .NDF
  file.


ΓòÉΓòÉΓòÉ 8.5.7. Using the Configuration Program ΓòÉΓòÉΓòÉ

There are three ways to use the Communications Manager configuration windows.
Select one of the following items for more information about using these
windows.

o Default configuration
o Advanced configuration
o Communications Manager configuration list


ΓòÉΓòÉΓòÉ 8.5.8. Default Configuration ΓòÉΓòÉΓòÉ

Default configuration is limited to configuring the following frequently-used
scenarios:

o 3270 emulation with LAN, SDLC or coaxial connection
o 5250 emulation with LAN, SDLC or twinaxial connection

When you use default configuration, you are required to enter the minimum
number of parameters in each window; Communications Manager supplies defaults
for all other values.


ΓòÉΓòÉΓòÉ 8.5.9. Advanced Configuration ΓòÉΓòÉΓòÉ

Advanced configuration allows you to configure using all of the Communications
Manager configuration windows.  If you use advanced configuration, you will
have access to virtually all of the Communications Manager configuration
parameters.


ΓòÉΓòÉΓòÉ 8.5.10. Communications Manager Configuration List ΓòÉΓòÉΓòÉ

The Communications Manager configuration list is a list of all Communications
Manager profiles and features.  If you are familiar with the configuration
process, you can use this list to save time; however, Communications Manager
does not direct you to the menus that are necessary for your particular
scenario.


ΓòÉΓòÉΓòÉ 8.5.11. Verifying Configuration Files ΓòÉΓòÉΓòÉ

When you close the Configuration Definition window, a configuration
verification is performed.  The Options choice on the menu bar provides an
option to turn automatic verification off; however, if the configuration is not
verified, Communications Manager will not be able to use it at a later time.

Bypassing automatic verification could be useful if, for example, you find that
you do not have all of the necessary information to configure all the required
profiles at that time.  When the information is available, you can restart the
configuration program, make the appropriate modifications, and then perform the
verification.


ΓòÉΓòÉΓòÉ 8.5.12. Copying Configuration Profiles ΓòÉΓòÉΓòÉ

Communications Manager/2 does not provide a facility to copy profiles
selectively from one configuration to another. Instead, you can generate CID
response files and combine their feature definitions.


ΓòÉΓòÉΓòÉ 8.5.13. Other Configuration Concerns ΓòÉΓòÉΓòÉ

Be careful when specifying the LU local/NAU address for terminal emulators.
Communications Manager in Extended Services and Extended Edition ensured a
unique address for this field; this is no longer the case because of enhanced
multiple PU support.

Because you can now have multiple host links, you can also have multiples of
the same NAU address.  Communications Manager does not reject multiples of the
same NAU address, even for the same host link, and only one emulator session
can be active for one NAU address for any host.


ΓòÉΓòÉΓòÉ 8.6. Configuration, Installation, and Distribution (CID) ΓòÉΓòÉΓòÉ

Configuration, Installation, and Distribution (CID) allows several forms of
user involvement in the CID process.  They are:

Attended installation
   Someone with product knowledge is present and can respond to various prompts
   during installation and configuration.

Lightly attended installation
   Someone is present, but is only required to start the installation, insert
   diskettes, and respond to simple prompts.

Unattended installation
   No user involvement is required.
For more information on CID, refer to the Response File Reference online
document.

Select an item below for more CID information.

o Model configuration
o User response files
o Functions not provided by CID
o General comments


ΓòÉΓòÉΓòÉ 8.6.1. Model Configuration ΓòÉΓòÉΓòÉ

To create a Communications Manager model configuration on the file server, do
one of the following:

o Copy a configuration from one of the distributed workstations

o Create a new configuration on the file server

If you are creating the configuration on the file server, then proceed with
configuration of a 3270 emulation session over a token-ring network.  Use
exactly the same setups as if you were on the distributed workstation, except
for the following:

o Select a suitable name for the configuration; for example:

          MYMODEL or MOD3270

o When prompted by CMSETUP with the pop-up window, "Will this configuration be
  used for this workstation?", select NO.  This causes CMSETUP to skip the
  steps related to installing components, using this configuration, on the file
  server.

o During the configuration, when you are required to provide values such as
  LOCAL_CP_NAME, enter the values for one.


ΓòÉΓòÉΓòÉ 8.6.2. User Response Files ΓòÉΓòÉΓòÉ

The following methods can be used to create user response files:

o Edit the sample new installation response file provided with Communications
  Manager.  You can find this sample on the Network Administrator Diskette.

o Use the Communications Manager CMRECORD function to convert a configuration
  into a response file, then edit the result to customize the file.

o Use an editor to create a response file from scratch. This is not
  recommended, as the other options create files with records in the correct
  syntax, which saves time and increases the probability of the file being
  error free.


ΓòÉΓòÉΓòÉ 8.6.3. General Comments ΓòÉΓòÉΓòÉ

Use of a model configuration versus response file only

Network administrators can provide almost all configuration information in
either a response file, a configuration file set or a mixture of both.

For example, a network administrator may wish to consider using only response
files to define configuration information.  This is possible except for the
following function, which cannot be specified in a response file:

o Keyboard remapping

Note:  The Keyboard remapping must be configured on an individual workstation
by copying onto the workstation the appropriate configuration files.

o Creating keyboard definitions in a response file requires care.

  A keyboard record in a configuration file is not directly linked to a COUNTRY
  profile.  Therefore, CMRECORD cannot automatically create correct values for
  the AT_KEYBOARD, ENHANCED_KEYBOARD, and 106_ENHANCED_KEYBOARD (DBCS only)
  records.

  To overcome this, CMRECORD outputs the keyboard records without any COUNTRY
  fields.  The response file processor (CMSETUP /R) considers COUNTRY to be an
  optional field. When CMSETUP /R is processing a response file, if the COUNTRY
  field is not specified, CMSETUP /R will examine the NAME filed and take the
  following action:

   - If the NAME is a known name, for example ACSCENUS, then Communications
     Manager will use the appropriate model keyboard.

   - If the NAME is a user-defined name (for example, MYKEYBD), then
     Communications Manager will determine what keyboard is defined to OS/2 via
     CONFIG.SYS and use the appropriate country's model keyboard to create the
     keyboard record.


ΓòÉΓòÉΓòÉ 8.6.4. Functions not provided by CID ΓòÉΓòÉΓòÉ

The following functions are not provided by CID:

o Keywords which install by feature, without configuration

  It is not possible to specify just a record keyboard in a response file, with
  no field values and have the CID process install that feature.  At a minimum,
  a NAME field keyword must be specified on any record keyword

o Keywords to add, remove or change keylock passwords

  Keylock password is provided on the CMSETUP /R command via the /KL parameter

o Updating multiple configurations in a single job

  Only one configuration can be updated per CID installation. Multiple CID
  installations with CMUPDATETYPE=4 (no installation) can be used to update
  multiple configurations on a workstation


ΓòÉΓòÉΓòÉ 8.7. Command Enhancements ΓòÉΓòÉΓòÉ

Several commands are available from an OS/2 window or full screen session.  In
general, you do not need to use line commands for Communications Manager.
Virtually all of the Communications Manager functions are now accessible from
OS/2 Presentation Manager windows.  There are times, however, when it can be
useful to perform a function under program control.

For more information, refer to the Command Reference.


ΓòÉΓòÉΓòÉ 8.8. ACDI Redirection Upgrade Restriction ΓòÉΓòÉΓòÉ

If you upgrade an existing configuration that includes Asynchronous
Communications Device Interface (ACDI) redirection from OS/2 EE 1.30.2 or
Extended Services, your ACDI redirection configuration will not be upgraded.
Everything else in your existing configuration is upgraded, including the ACDI
APIs.  To include ACDI redirection, you will need to modify your upgraded
configuration.


ΓòÉΓòÉΓòÉ 9. Productivity Aids (Applets) ΓòÉΓòÉΓòÉ

A variety of productivity aids are included with Communications Manager. You
should be aware, however, that these programs are not a formal part of
Communications Manager and are not supported by IBM.

A complete list of these productivity aids is contained on disk 1 of the
Productivity Aids diskettes.  For information on accessing these productivity
aids, refer to the online README file.


ΓòÉΓòÉΓòÉ 10. Restrictions ΓòÉΓòÉΓòÉ

The following restrictions apply to this release of Communications Manager.
Refer to the README file for the latest updates.

Gateway Restrictions

o Single focal point

  Although Communications Manager can maintain multiple SSCP-PU sessions, only
  one host system can be used as an active focal point for sending alerts.
  This link is specified with the HOST_FP_LINK_NAME parameter of the
  DEFINE_LOCAL_CP record in the .NDF file.  The link for the focal point must
  be using the implicit PU with the same name as the local CP.

o Single host entry point

  A Communications Manager node only accepts network management requests
  (NMVTs) from a PU 2 host that are addressed to the PU with the same name as
  the CP.

o One PU per host/adapter/address

  The Communications Manager node can only have one link to another partner
  over a given source adapter/target address pair.  The only way to define an
  additional PU is to define an additional link.  Therefore, it is not possible
  to have multiple PUs to the same host unless a different local adapter or
  remote address is specified.

  Note:  In addition to the obvious solution of using multiple adapters,
  another possibility is to define a different target SAP address.  VTAM allows
  you to specify a source SAPADDR parameter on the PU definition if you are
  connected by an ICA.  You can configure the local SAP in the LAN DLC Adapter
  profile and the target SAP in the SNA Connections Link Profile.


ΓòÉΓòÉΓòÉ 11. Bibliography ΓòÉΓòÉΓòÉ

The bibliography for Communications Manager/2 describes both online and printed
sources of information that can be useful when planning for or using
Communications Manager.

o Publications Ordering Information

o Communications Manager/2 Product Package Publications

o Communications Manager/2 Administrator's Package Publications

o Communications Manager/2 Programming Publications

o Related Local Area Network Publications

o Integrated Services Digital Network Publications

o SNA Session Level Data Confidentiality Publications

o OS/2 Publications

o Related IBM AS/400 Host Publications

o Related 3270 Host Communications Publications

o Related Realtime Interface Co-Processor Publications

o Related X.25 Packet-Switching Data Networks Publications

o Systems Application Architecture (SAA) Publications


ΓòÉΓòÉΓòÉ 11.1. Publications Ordering Information ΓòÉΓòÉΓòÉ

Part numbers and order numbers for IBM publications are presented in the
following way:

o If only one part number or order number follows a publication title, that
  part number or order number is the worldwide part number; for example:

   IBM LAN Asynchronous Connection Server Function and Connectivity Guidelines
   (GA27-3917)

o If a publication has a U.S. version different from the worldwide English
  version, two part numbers or order numbers are given in the following
  example:

   IBM X.25 Interface Co-Processor/2: Technical Reference (16F1879 (U.S.);
   07F3180).

o If a publication has both a part number and an order number, the numbers are
  given as in the following example:

   IBM Local Area Network Technical Reference (25F7688, P/N SC30-3383-03).

Note:  Four publications have order numbers listed and can be ordered
separately.  These books are at the Communications Manager/2 Version 1.0 level
and have not been updated for this release.

To order Communications Manager/2 or OS/2 publications, use the toll-free
number: 800-426-7282. The publication part number (P/N) is required when
ordering through this phone number. Contact your IBM authorized dealer or your
IBM marketing representative for information about ordering any of the
publications listed in this bibliography.


ΓòÉΓòÉΓòÉ 11.2. Communications Manager/2 Basic Product Package Books ΓòÉΓòÉΓòÉ

The following list encompasses all of the hardcopy and online publications in
the Communications Manager library.  The words "IBM Communications Manager/2"
are actually part of the title of each book; however, in this list, those words
are omitted.

o Workstation Installation and Configuration Guide, SC31-7169-01

o Quick Installation, SX75-0085-01

o User's Guide, SC31-7068-01

o Command Reference (online)

o Overview (online)

o Glossary (online)

o Response File Reference (online)

o Service Point Application Router and Remote Operations Service Guide (online)

o Message Reference (online)

o Problem Determination Guide (online)

The following publication is available as a separately orderable publication.

o Information and Planning Guide, SC31-7007-01


ΓòÉΓòÉΓòÉ 11.3. Communications Manager/2 Administrator's Package Books ΓòÉΓòÉΓòÉ

The following list encompasses all of the books in the Communications Manager/2
Administrator's Package.  The words "IBM Communications Manager/2" are actually
part of the title of each book; however, in this list, those words are omitted.

The following books provide advanced planning and installation information for
Communications Manager:

o Network Administration and Subsystem Management Guide, SC31-6168-01

o Scenarios, SC31-6174-01

o Host Connection Reference, SC31-6170-01

o Host Print Guide, SC31-7145-00


ΓòÉΓòÉΓòÉ 11.4. Communications Manager/2 Programming Books ΓòÉΓòÉΓòÉ

The following list encompasses all the programming books in the Communications
Manager library.  The words "IBM Communications Manager/2" are actually part of
the title of each book; however, in this list, those words are omitted.

These publications are provided in BOOK and LISTPS format on the Communications
Manager/2 Version 1.1 CD-ROM.

The following books provide Communications Manager application programming
interface (API) programming information for creating and maintaining
Communications Manager programs:

o Application Programming Guide

o ACDI Programming Reference, SC31-6161

o APPC Programming Guide and Reference

o Conventional LU Application Programming Reference

o ECF Server-Requester Programming Interface (SRPI) Reference, SC31-6165

o EHLLAPI Programming Reference

o ISDN Connection Management Interface (CMI) Programming Reference

o ISDN Port Connection Manager (PCM) Programming Reference

o Realtime Interface Co-Processor Device Driver Programming Reference,
  SC31-6164

o System Management Programming Reference

o X.25 Programming Reference, SC31-6167


ΓòÉΓòÉΓòÉ <hidden> Quick Installation, SX75-0085-01 ΓòÉΓòÉΓòÉ

Quick Installation, SX75-0085-01; P/N 79G0460

This card provides you with a very brief set of instructions on how to start
the installation of Communications Manager.  It is intended primarily for those
who want to accept most or all of the preselected choices during installation.
Quick Installation provides only limited instructions to get you started.  If
you want more detailed information about installing Communications Manager,
refer to Workstation Installation and Configuration Guide.


ΓòÉΓòÉΓòÉ <hidden> * @R2c ΓòÉΓòÉΓòÉ

  width=50% height=100%.User's Guide, SC31-6108-01

User's Guide, SC31-6108-01; P/N 79G0456

This book provides information necessary to accomplish basic communication
tasks using Communications Manager. For example, this volume contains
information and procedures for starting and stopping Communications Manager,
using the clipboard to mark and copy data from one application to another,
using 3270 and 5250 emulation, transferring files, and changing the current
keyboard layout.


ΓòÉΓòÉΓòÉ <hidden> Host Print Guide, SC31-7145 ΓòÉΓòÉΓòÉ

Host Print Guide, SC31-7145; P/N 79G0453

This book describes how to use the functions in Communications Manager Host
Print for both AS/400 and 3270 printing.  It tells how to configure for
printing ,meet special printing needs, and solve printing problems.


ΓòÉΓòÉΓòÉ <hidden> Problem Determination Guide ΓòÉΓòÉΓòÉ

Problem Determination Guide

This book provides online documentation for problem determination procedures
using FFST/2, trace and dump services, diagnostic tools, sense data, and OS/2
request codes.


ΓòÉΓòÉΓòÉ <hidden> Command Reference ΓòÉΓòÉΓòÉ

Command Reference

This online document lists the Communications Manager commands and their syntax
diagrams.  It also describes Communications Manager device drivers.


ΓòÉΓòÉΓòÉ <hidden> Glossary ΓòÉΓòÉΓòÉ

Glossary

This online book defines technical terms and acronyms that are used throughout
the Communications Manager program and publications.


ΓòÉΓòÉΓòÉ <hidden> Information and Planning Guide, SC31-7007-01 ΓòÉΓòÉΓòÉ

Information and Planning Guide, SC31-7007-01; P/N 79G0459

This book provides an overview of Communications Manager, including
descriptions of new and enhanced functions and productivity aids, information
on the administration and use of Communications Manager, and system
requirements.  This book also provides technical advice on performance and
coexistence considerations, planning new installations, and migrating from
previous releases.


ΓòÉΓòÉΓòÉ <hidden> Overview ΓòÉΓòÉΓòÉ

Overview

This online document provides a comprehensive view of Communications Manager.
It includes a description of configuration, services, emulator functions,
application programming interfaces, and a complete bibliography of
Communications Manager documentation and related publications.


ΓòÉΓòÉΓòÉ <hidden> Network Administration and Subsystem Management Guide, ΓòÉΓòÉΓòÉ

Network Administration and Subsystem Management Guide, SC31-6168-01; P/N
79G0452

This book provides an overview of Communications Manager functions and the
steps required to create the Communications Manager configurations for the
workstations you support.  This book also contains configuration worksheets.


ΓòÉΓòÉΓòÉ <hidden> Response File Reference ΓòÉΓòÉΓòÉ

Response File Reference

This online document contains information on how to create response files and
use them to configure Communications Manager remotely.  It also lists all of
the response file keywords and explains how to upgrade Extended Services
response files to Communications Manager response files.


ΓòÉΓòÉΓòÉ <hidden> Scenarios, SC31-6174-01 ΓòÉΓòÉΓòÉ

Scenarios, SC31-6174-01; P/N 79G0458

This book contains sample scenarios with steps to install and configure several
different kinds of networks with attached workstations.


ΓòÉΓòÉΓòÉ <hidden> Workstation Installation and Configuration Guide, SC31-7169 ΓòÉΓòÉΓòÉ

Workstation Installation and Configuration Guide, SC31-7169; P/N 79G0296

This book provides the basic information to install Communications Manager and
to configure it for various connections and features. This book also contains
information about using a response file for installation and about changing a
configuration.  Some advanced user tasks, such as how to use the keylock
function to protect configuration files, are described here.


ΓòÉΓòÉΓòÉ <hidden> Host Connection Reference, SC31-6170-01 ΓòÉΓòÉΓòÉ

Host Connection Reference, SC31-6170-01; P/N 79G0457

This book contains parameter matching and sample system generations for OS/2
connections to S/370 and Application System/400* (AS/400*) hosts.

* Trademark of IBM


ΓòÉΓòÉΓòÉ <hidden> Service Point Application Router and Remote Operations Service Guide, SC31-7006 ΓòÉΓòÉΓòÉ

Service Point Application Router and Remote Operations Service Guide

This is an online book that contains guidance and reference information for
using two Communications Manager functions, Service Point Application Router
and Remote Operations Service, to handle network management commands directed
to a workstation by a NetView operator or application program.


ΓòÉΓòÉΓòÉ <hidden> Message Reference, ΓòÉΓòÉΓòÉ

Message Reference

This online book contains the text, explanations, and suggested actions for all
Communications Manager messages.  This document is also available online.


ΓòÉΓòÉΓòÉ <hidden> Application Programming Guide ΓòÉΓòÉΓòÉ

Application Programming Guide

This book describes application program development for Communications Manager.
It is the starting point for writing application programs that use any of the
Communications Manager application programming interfaces (APIs) and contains
information common to all of the APIs. The Communications Manager/2 Sample
Programs diskette, which contains sample programs, API data structures, and
header files, is provided with this book.


ΓòÉΓòÉΓòÉ <hidden> ACDI Programming Reference, SC31-6161 ΓòÉΓòÉΓòÉ

ACDI Programming Reference, SC31-6161

This book introduces and defines the procedures for using the Asynchronous
Communications Device Interface (ACDI). This book serves as a reference for
programmers who want to use the asynchronous programming functions to create
their own application programs using C and Macro Assembler languages.


ΓòÉΓòÉΓòÉ <hidden> APPC Programming Guide and Reference ΓòÉΓòÉΓòÉ

APPC Programming Guide and Reference

This book provides information necessary to create application programs in the
C, COBOL, or Macro Assembler programming languages that use the advanced
program-to-program communications (APPC) programming interface functions.


ΓòÉΓòÉΓòÉ <hidden> Conventional LU Application Programming Reference ΓòÉΓòÉΓòÉ

Conventional LU Application Programming Reference

This book provides information necessary to create application programs in the
C, COBOL, or Macro Assembler programming languages that use the IBM OS/2
Conventional LU Application (LUA) programming interface.


ΓòÉΓòÉΓòÉ <hidden> ECF Server-Requester Programming Interface (SRPI) Reference, SC31-6165 ΓòÉΓòÉΓòÉ

ECF Server-Requester Programming Interface (SRPI) Reference, SC31-6165

This book provides programmers with the information necessary to create
requester application programs that use the Server-Requester Programming
Interface (SRPI) functions in Communications Manager.


ΓòÉΓòÉΓòÉ <hidden> EHLLAPI Programming Reference ΓòÉΓòÉΓòÉ

EHLLAPI Programming Reference

This book defines the Emulator High-Level Language Application Programming
Interface (EHLLAPI). Applications written to this programming interface can
access and control the 3270 and 5250 host presentation spaces.


ΓòÉΓòÉΓòÉ <hidden> ISDN Connection Management Interface (CMI) Programming Reference ΓòÉΓòÉΓòÉ

ISDN Connection Management Interface (CMI) Programming Reference

This book describes how to use the integrated services digital network (ISDN)
connection manager interface (CMI) to make a connection for user applications
through a switched network.


ΓòÉΓòÉΓòÉ <hidden> ISDN Port Connection Manager (PCM) Programming Reference ΓòÉΓòÉΓòÉ

ISDN Port Connection Manager (PCM) Programming Reference

This book describes how to develop and implement a call control module (a port
connection manager) for use in Communications Manager's switched network
environment.


ΓòÉΓòÉΓòÉ <hidden> Realtime Interface Co-Processor Device Driver Programming Reference, SC31-6164 ΓòÉΓòÉΓòÉ

Realtime Interface Co-Processor Device Driver Programming Reference, SC31-6164

This book provides information for writing programs that support the Realtime
Interface Co-Processor adapters. The dynamic link libraries, the application
loader, and the device driver interface are discussed.


ΓòÉΓòÉΓòÉ <hidden> System Management Programming Reference ΓòÉΓòÉΓòÉ

System Management Programming Reference

This book provides detailed descriptions of the Advanced Peer-to-Peer
Networking (APPN)* configuration and subsystem management verbs.  These verbs
allow configuration and management of APPN nodes.

* Trademark of IBM


ΓòÉΓòÉΓòÉ <hidden> X.25 Programming Reference, SC31-6167 ΓòÉΓòÉΓòÉ

X.25 Programming Reference, SC31-6167

This book provides the information necessary to create application programs in
the C, COBOL, or Macro Assembler programming languages that use the X.25 API.


ΓòÉΓòÉΓòÉ 11.5. Related Local Area Network Publications ΓòÉΓòÉΓòÉ

The following LAN publications can aid administrators in installing,
configuring, and using LAN servers, requesters, and hardware:

o IBM Local Area Network Technical Reference (25F7688, SC30-3383-03) provides
  information for using IBM LAN adapters and software interfaces in IBM
  Personal System/2* (PS/2*) and IBM Personal Computer AT* workstations. It is
  intended for programmers who plan to use IBM LANs and for those who need
  information about the correct adapters required for setting up an IBM LAN.

o IBM LAN Asynchronous Connection Server Function and Connectivity Guidelines
  (GA27-3917) provides guidelines for configuring a LAN asynchronous connection
  server.

o IBM Local Area Network Asynchronous Connection Server (SC30-3509-01) provides
  information for network administrators who are planning and installing a LAN
  asynchronous connection server. This book is provided with the LAN
  asynchronous connection server product and cannot be purchased separately.

o The LAN Server Version 2.0 product is described in the IBM Operating System/2
  Local Area Network Server Version 2.0 Network Administrator Reference:

   - Volume 1:  Planning and Installation (04G1032)
   - Volume 2:  Performance Tuning (04G1033)
   - Volume 3:  Network Administrator Tasks (04G1034)

o IBM Token-Ring Network Introduction and Planning Guide (GA27-3677-03).

o IBM Token-Ring Network Problem Determination Guide (SX27-3710-04).

o IBM PC Network Hardware Maintenance and Service Manual (S68X-2240-03).

o IBM 3174 Establishment Controller Peer Communication User's Guide
  (GA27-3887-02).

o IBM NETBIOS Application Development Guide (S68X-2270).

o IEEE 802.2 Local Area Networks Standard, 802.2 Logical Link Control,
  ANSI/IEEE Standard, October, 1985.

o IEEE 802.2 Local Area Networks Standard, 802.3 Carrier Sense Multiple Access,
  ANSI/IEEE Standard, October, 1985.

o Microsoft/3Com LAN Manager Network Driver Interface Specification, Version
  2.01, Microsoft Corporation, 3Com Corporation.

o The Ethernet:  A Local Area Network, Data Link Layer and Physical Layer
  Specifications, Digital, Intel, XEROX, Version 2.0, November 1982, Digital
  Equipment Corporation, Intel Corporation, Xerox Corporation.

* Trademark of IBM


ΓòÉΓòÉΓòÉ 11.6. Integrated Services Digital Network Publications ΓòÉΓòÉΓòÉ

These publications provide information about ISDN architecture and interfaces.

o IBM Lower-Layer Services Architecture:  ISDN Port Connection Manager
  Architecture Reference (SC31-6829) defines the interface to the LSA port
  connection manager function for ISDN call control.

o IBM Integrated Services Digital Networks Circuit-Switching Signaling Control
  Architecture Reference (SC31-6827) describes the format and sequence of
  messages on the D channel that control the switched connection and use of the
  B channel.

o IBM Integrated Services Digital Networks Data Link Control Architecture
  Reference (SC31-6826) contains information about ISDN data link control,
  representing IBM's interpretation of CCITT Recommendations Q.921 and Q.922.

o International Telegraph and Telephone Consultative Committee (CCITT), Support
  of Packet Mode Terminal Equipment by ISDN.


ΓòÉΓòÉΓòÉ 11.7. SNA Session Level Data Confidentiality Publications ΓòÉΓòÉΓòÉ

SNA session level data confidentiality is part of the IBM Transaction Security
System (TSS).  You can use TSS with Communications Manager to encrypt data when
it is transferred between a host and a workstation. Work Station Security
Services (WSSS) is the workstation portion of TSS. WSSS provides the file
CSUESAPI.DLL, which is used by Communications Manager/2 during file transfer of
encrypted data. Refer to these IBM publications for more information about TSS
and WSSS.

o Transaction Security System: General Information Manual and Planning Guide
  (GA34-2137). This publication describes the hardware and software products in
  TSS. It also describes ways in which you can use these products to:

   - Provide data confidentiality in an SNA network environment
   - Determine data integrity
   - Store sensitive data on portable media
   - Process financial PINs
   - Use public-key functions

  This manual also provides planning and site preparation information for TSS.

o Transaction Security System: Programming Reference:  Volume 1, Access Control
  and DES Cryptography (SC31-2934). This book provides guidance and reference
  information for the Transaction Security System security application program
  interface (API). The book is intended for system analysts who are responsible
  for designing programs that use the TSS hardware and software. Application
  programmers who are responsible for writing application programs that use the
  security API should also use this book.

o Workstation Security Services Installation and Operating Guide (SA34-2141).
  This publication item is a kit that includes a manual, tabs, binder, and
  diskette holders. The manual tells how to install the 4754 and 4755
  cryptographic adapters. It also tells how to install and use the various Work
  Station Security Services utilities, including the hardware initialization
  utility and the software configuration utility. Additional information is
  provided about DOS support, OS/2 support, and problem determination
  procedures.


ΓòÉΓòÉΓòÉ 11.8. OS/2 Publications ΓòÉΓòÉΓòÉ

If your operating system is OS/2, you can use the publications in the following
sections. If your operating system is manufactured by someone other than IBM,
you can use the documentation supplied with your base operating system.

o OS/2 2.0 Publications

o Other OS/2 Publications

o Procedures Language 2/REXX Publications

o General Information


ΓòÉΓòÉΓòÉ <hidden> OS/2 2.0 Publications ΓòÉΓòÉΓòÉ

If your operating system is IBM OS/2 2.0, you can use the following related
publications:

o IBM OS/2 Technical Library (10G3356)

o IBM OS/2 2.0 Command Reference (S10G-6313)

o IBM Application Design Guide (10G6260)

o IBM Programming Guide, Volume 1 (10G6261)

o IBM Programming Guide, Volume 2 (10G6494)

o IBM Programming Guide, Volume 3 (10G6495)

o IBM Control Program Programming Reference (10G6263)

o IBM Presentation Manager Programming Reference, Volume 1 (10G6264)

o IBM Presentation Manager Programming Reference, Volume 2 (10G6265)

o IBM Presentation Manager Programming Reference, Volume 3 (10G6272)

o IBM Information Presentation Facility Guide and Reference (10G6262)

o IBM System Object Model Guide and Reference (10G6309)

o IBM Physical Device Driver Reference (10G6266)

o IBM Virtual Device Driver Reference (10G6310)

o IBM Presentation Driver Reference (10G6267)


ΓòÉΓòÉΓòÉ <hidden> Other OS/2 Publications ΓòÉΓòÉΓòÉ

If your operating system is IBM OS/2 Version 1.30.2, you can use the following
related publications:

o IBM Operating System/2 Standard Edition Getting Started

o IBM Operating System/2 Standard Edition Using Advanced Features

o OS/2 Programming Tools and Information Version 1.3 (6024929) (referred to as
  Programming Tools and Information) contains books which describe programming
  concepts for developing applications for OS/2 Standard Edition. Code examples
  and procedures are described to show the application developer how to use an
  API for developing source code. An installation card is included to guide the
  application developer in installing the toolkit. The following books are
  included:

   - Programming Overview (S91F9258)

   - Programming Guide (S91F9259)

   - Control Program Programming Reference (S91F9260)

   - Presentation Manager Programming Reference, Vol. 1 (S91F9261)

   - Presentation Manager Programming Reference, Vol. 2 (S91F9262)

   - I/O Subsystems and Device Support, Vol. 1: Device Drivers (S91F9263)

   - Building Programs (S91F9264)

   - Presentation Manager C/2 Bindings Reference (S91F9265)

   - I/O Subsystems and Device Support, Vol. 2: Driver Interfaces (S91F9266)

   - FORTRAN/2 Bindings Reference (S91F9267)

   - COBOL/2 Binding Reference (S91F9268)

   - Presentation Manager Macro Assembler/2 Bindings Reference (S91F9269)

   - Dialog Manager and Dialog Tag Summary Reference (S91F9270 )

   - Dialog Tag Language Guide and Reference (S91F9271)

   - Procedures Language/2 REXX Programming Reference (S91F9272)

   - Dialog Manager Guide and Reference (S91F9273)

   - Master Index (S12F9826)


ΓòÉΓòÉΓòÉ <hidden> Procedures Language 2/REXX Publications ΓòÉΓòÉΓòÉ

The following Procedures Language 2/REXX publications are available:

o OS/2 2.0 Procedures Language 2/REXX Reference (S10G-6268)

o OS/2 2.0 Procedures Language 2/REXX User's Guide (S10G-6269)


ΓòÉΓòÉΓòÉ <hidden> General Information ΓòÉΓòÉΓòÉ

The following information sources can help you understand the products
available from IBM:

o Catalog of IBM Education (G320-1244-38, U.S. only; GN21-4412)

o Software Directory (GB21-9949-28, U.S. only; GN20-3025)


ΓòÉΓòÉΓòÉ 11.9. Related IBM AS/400 Host Publications ΓòÉΓòÉΓòÉ

The following information lists the related publications for Communications
Manager communications with an AS/400 host.

o AS/400 Publications

o 5250 Emulation Publications

o PC Support/400 Publications


ΓòÉΓòÉΓòÉ <hidden> AS/400 Publications ΓòÉΓòÉΓòÉ

For information about the IBM AS/400 host library, refer to AS/400 Publications
Guide (GC41-9678).


ΓòÉΓòÉΓòÉ <hidden> 5250 Emulation Publications ΓòÉΓòÉΓòÉ

The following publications can help users understand 5250 emulation with
Communications Manager/2:

o IBM 5250 Information Display System Planning and Site Preparation Guide
  (GA21-9337-08)

o IBM 5251 Display Station Models 1 and 11 5252 Dual Display Station Operator's
  Guide (GA21-9248-03)

o IBM 5251 Display Station Models 2 and 12 Operator's Guide (GA21-9323-02)

o IBM 5291 Display Station Operator's Guide (GA21-9409-02)

o IBM 5292 Color Display Station Models 1 and 2 Operator's Guide (GA21-9416-01)


ΓòÉΓòÉΓòÉ <hidden> PC Support/400 Publications ΓòÉΓòÉΓòÉ

The following publications can help you learn how to use PC Support/400 to
communicate with an IBM AS/400 host:

o AS/400 PC Support/400: OS/2 Installation and Administration Guide Version 2.2
  (SC41-0007)

o AS/400 PC Support/400:  OS/2 Installation and Administration (PS/55) Guide
  Version 2.2 (SC41-0009)

o AS/400 PC Support/400: DOS and OS/2 Technical Reference Version 2.2
  (SC41-8091)

o AS/400 PC Support/400:  Application Program Interface Reference Version 2.2
  (SC41-8254)

o AS/400 PC Support/400:  OS/2 User's Guide Version 2.2 (SC41-8200)

o AS/400 PC Support/400:  OS/2 User's Guide (PS/55) Version 2.2 (SC41-2415)


ΓòÉΓòÉΓòÉ 11.10. Related 3270 Host Communications Publications ΓòÉΓòÉΓòÉ

The following publications can be helpful to communications programmers:

o IBM APPC for the Personal Computer Programming Guide (SC40-0100; P/N 75X1084)

o IBM Programmer's Guide to the SRPI for the PC and the 3270-PC (SC23-0959-01)

o IBM 3270 PC High Level Language Application Program Interface Programmer's
  Guide (available only with the IBM 3270 PC HLLAPI program product, 75X1087)

The following host references can aid a communications system administrator who
is consulting with host personnel during configuration:

o VTAM Installation and Resource Definition Version 3 (SC23-0111-05)

o ACF/VTAM Version 3 Customization (SC23-0112-03) (a component of SBOF-1584 and
  SBOF-1583)

o Enhanced Connectivity Facilities TSO/E Servers-Requesters CMS
  Servers-Requesters Introduction Version 1 (GC23-0957-04)

o Network Program Products Planning (SC27-0658-02)

o Network Program Product Samples (SC30-3352-07)

o Synchronous Data Link Control General Information (GA27-3093-03)

o Systems Network Architecture Guide to SNA Publications (GC30-3438)

o Systems Network Architecture Concepts and Products (GC30-3072-04)

o Systems Network Architecture Network Product Formats (LY43-0081-01)

o Systems Network Architecture Format and Protocol Reference:  Architecture
  Logic for LU Type 6.2 (SC30-3269-03)

o Systems Network Architecture:  Sessions between Logical Units (GC20-1868-02)

o Systems Network Architecture Technical Overview (GC30-3073-03)

o System Control Statements VSE/AF (SC33-6198-02)

o 3270 Information Display System 3274 Control Unit Description and
  Programmer's Guide (GA23-0061-02)

o MVS Host Publications

o VM Host Publications

o Graphical Data Display Manager Publications


ΓòÉΓòÉΓòÉ <hidden> MVS Host Publications ΓòÉΓòÉΓòÉ

The following publications can be used for communicating with an MVS host:

o CICS/DOS/VS Version 1 Installation and Operations Guide (SC33-0070-06)

o CICS/DOS/VS Version 1 Release 7 Release Guide (GC33-0130-02)

o TSO/E Version 2 Guide to the Server-Requester Programming Interface
  (SC28-1877-03)

o ECF/TSO/E Servers and CMS Servers Installation Planning and Programmer's
  Guide (SK2T-0004)

o ECF Installation, Planning, and Administration Guide (SH20-9677-02)


ΓòÉΓòÉΓòÉ <hidden> VM Host Publications ΓòÉΓòÉΓòÉ

The following publications can be used for communicating with a VM host:

o IBM Programmers Guide to the Server-Requester Programming Interface for VM/SP
  (SC24-5291-02)

o VM/SNA NPP Samples (SC30-3309) (a component of SBOF-1584)

o VM/SP Planning Guide and Reference (SC19-6201-06)


ΓòÉΓòÉΓòÉ <hidden> Graphical Data Display Manager Publications ΓòÉΓòÉΓòÉ

Communications system administrators and users of the 3270 host graphics
program Graphical Data Display Manager (GDDM*) can use the following
publications for additional information:

o GDDM Version 2 Release Guide (GC33-0320-02)

o GDDM Version 2 Library Guide and Master Index (GC33-0595-01)

o Introducing GDDM (GBOF-0058). This package contains:

   - GDDM Version 2 General Information (GC33-0319-02)

   - GDDM If you make business presentations... (GC33-0455)

   - GDDM If you're an engineer... (GC33-0456)

o GDDM Version 2.2 Application Programming Guide GDDM/MVS, GDDM/VM, GDDM/VSE,
  GDDM-IMD, GDDM-PGF (SC33-0337)

o GDDM Version 2 Base Programming Reference Volume 1 and 2 (SC33-0332-02)

o GDDM Version 2 Base Programming Reference Summary (SX33-6053-01)

o GDDM-PGF Programming Reference (SC33-0333)

o GDDM-PGF Interactive Chart Utility (SC33-0328)

o GDDM Better Charts Poster (GC33-0529)

o GDDM-PGF Vector Symbol Editor (SC33-0330)

o GDDM-PGF Version 2 Programming Reference Summary (SX33-6054)

o GDDM Version 2 Installation and System Management for MVS (GC33-0321-04)

o GDDM Version 2 Installation and System Management for VSE (GC33-0322-03)

o GDDM Version 2 Installation and System Management for VM (GC33-0323-03)

o GDDM Version 2 Performance Guide (SC33-0324)

o GDDM Version 2 Messages (SC33-0325-03)

o GDDM Version 2 Diagnosis and Problem Determination Guide (SC33-0326-03)

o GDDM Version 2 Guide for Users (SC33-0327-02)

o GDDM Image Symbol Editor (SC33-0329)

o GDDM Interactive Map Definition (SC33-0338)

o GDDM-GKS Programming Guide and Reference (SC33-0334)

o GDDM Image View Utility (SC33-0479)

o GDDM-PCLK Reference Summary (SX33-6067-01)

o GDDM 2.2 Typefaces and Shading Patterns (ST33-0554)

o GDDM Version 2 Licensed Program Specifications (GC33-0423-06)

* Trademark of IBM


ΓòÉΓòÉΓòÉ 11.11. Related Realtime Interface Co-Processor Publications ΓòÉΓòÉΓòÉ

The library for the IBM Realtime Interface Co-Processor, the IBM Realtime
Interface Co-Processor Multiport, and the IBM Realtime Interface Co-Processor
Multiport/2 consists of the following publications:

o Realtime Interface Co-Processor Technical Reference (SC28-8006)

o Realtime Interface Co-Processor Technical Reference Supplement (S15F-8872)

o Realtime Interface Co-Processor Firmware Technical Reference (S33F-5336)

o Realtime Interface Co-Processor Portmaster Technical Reference (S33F-5337)

o Realtime Interface Co-Processor Portmaster Technical Reference Supplement
  (SC28-8271)

o Realtime Interface Co-Processor Multiport Model 2 Technical Reference
  (S57F-0632)

o Realtime Interface Co-Processor Multiport Model 2 Technical Reference
  Supplement (SC28-8273)

o OS/2 Extended Edition Version 1 Realtime Interface Co-Processor Multiport/2
  (S01F-0300)

o Realtime Interface Co-Processor:  Developer's Kit (S16F-2020).  The
  publication with this product provides tips and techniques for system
  programmers who are creating applications for the IBM Realtime Interface
  Co-Processor Multiport/2 and the IBM X.25 Interface Co-Processor/2 in the
  OS/2 program.  It describes an assortment of productivity aids, including
  samples and debugging tools.

o Realtime Interface Co-Processor:  C Language Support (SC28-8014).  The
  publication with this product documents C high-level interfaces for the IBM
  Realtime Interface Co-Processor Multiport/2 and the IBM X.25 Interface
  Co-Processor/2.

o Realtime Interface Co-Processor AIX Support for RISC/6000 User's Guide
  (SC28-9596)

o Realtime Interface Co-Processor and Realtime Interface Co-Processor Multiport
  Hardware Maintenance Library (SC28-8005)

o Realtime Interface Co-Processor Multiport/2 Hardware Maintenance Library for
  6 Port Synchronous Card (S15F-8855)


ΓòÉΓòÉΓòÉ 11.12. Related X.25 Packet-Switching Data Networks Publications ΓòÉΓòÉΓòÉ

The definitive X.25 reference is the CCITT (International Telegraph and
Telephone Consultative Committee) Recommendation X.25:

o Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating
  Equipment (DCE) for Terminals Operating in the Packet Mode on Public Data
  Networks, Volume VIII, Fascicle VIII.2, Rec. X.25, Geneva (November 1980)

o Data Communications Networks Interfaces, Volume VIII, Fascicle VIII.3, Rec.
  X.20-X.32, Malaga-Torremolinos (October 1984)

IBM publications for X.25 are:

o X.25 1984-1988 Interface for Attaching SNA Nodes to Packet-Switched Data
  Networks General Information Network (GA27-3761)

o X.25 1984-1988 Interface for Attaching SNA Nodes to Packet-Switched Data
  Networks Architecture Reference (SC30-3409-01)

o X.25 Interface for Attaching SNA Nodes to Packet-Switched Data Networks
  General Information (GA27-3345-02)

o Tuning Considerations for SNA X.25 DTE's (GG24-1746)

In addition to the literature in the preceding list, you can refer to other
published material about packet switching and X.25.  For example, network
providers may publish introductory material or booklets of network-specific
information.

The following publications describe the X.25 Network Control Program Packet
Switching Interface (NPSI), which offers SNA users the ability to use
communications facilities that support the CCITT X.25 (1980 and 1984)
recommendations:

o X.25 NCP Packet Switching Interface General Information Version 3.4
  (GC30-3469-04)

o X.25 NCP Packet Switching Interface Planning and Installation Version 5.4
  (SC30-3470-05)

o X.25 Network Control Program (NCP) Packet Switching Interface Host
  Programming Version 3.4 (SC30-3502-03)

The following publications may be needed for reference:

o X.25 Interface Co-Processor/2 Technical Reference (S16F-1879, U.S.; 07F3180)

o X.25 Interface Co-Processor/2 Hardware Maintenance Library (S16F-1874, U.S.;
  07F3190; 07F3193, France; 07F3196, Germany)


ΓòÉΓòÉΓòÉ 11.13. Systems Applications Architecture (SAA) Publications ΓòÉΓòÉΓòÉ

The following publications describe the requirements for SAA and its
advantages:

o Systems Application Architecture Common Communications Support Primer
  (GC24-3483)

o Systems Application Architecture Common Programming Interface Query Reference
  (SC26-4349-03)

o SAA: Common Programming Interface C Reference (SC26-4353)

o SAA: Common Programming Interface C Reference (SC26-4354-02)

o Systems Application Architecture Common Programming Interface Application
  Generator Reference (SC26-4355-03)

o Systems Application Architecture Common Programming Interface Dialog
  Reference (SC26-4356-02)

o Systems Application Architecture Common Programming Interface FORTRAN
  Reference (SC26-4357-02)

o Systems Application Architecture (SAA) Common Programming Interface (CPI)
  Procedures Language Reference (SC26-4358-03)

o Systems Application Architecture Common Programming Interface Presentation
  Reference (SC26-4359-02)

o SAA Writing Applications:  A Design Guide (SC26-4362)

o SAA:  Common Programming Interface Communications Reference (SC26-4399)

o Systems Application Architecture:  Common User Access Guide to User Interface
  Design (SC34-4289)

o Systems Application Architecture:  Common User Access Advanced Interface
  Design Reference (SC34-4290)

o IBM Systems Application Architecture:  Common Communications Support Summary
  (GC31-6810)

o SAA Applications:  A Value Guide  (G320-9803)