Preface

Purpose of This Guide

This document describes the BEA Connect TCP product and gives instructions for configuring and administering Connect TCP.

Who Should Read This Guide

This document is intended for IMS system administrators who will configure and administer the BEA Connect TCP system. In addition, programmers will find useful information for developing client programs and service routines that exchange data with the remote BEA Connect gateways.

How This Manual Is Organized

The BEA Connect TCP for IMS User Guide is organized as follows:

Chapter 1, "Introducing BEA Connect TCP for IMS," provides a description of BEA Connect TCP concepts and processes.
Chapter 2, "Understanding How BEA Connect TCP for IMS Works," describes how to develop applications that exchange data with a remote BEA Connect gateway.
Chapter 3, "Installing BEA Connect TCP for IMS," describes the tasks for installing the BEA Connect TCP software.
Chapter 4, "Configuring BEA Connect TCP for IMS," describes how to create the configuration file.
Chapter 5, "Administering BEA Connect TCP for IMS," describes how to start the BEA Connect TCP application and test connectivity with remote BEA Connect gateways. It also provides information on implementing the BEA Connect TCP system and handling errors.
Chapter 6, "Programming BEA Connect TCP for IMS," describes how to program your application in COBOL, including message formats and field descriptions.
Appendix A, "System Services Used by BEA Connect TCP for IMS," describes various MVS, IMS, and TCP/IP services used by BEA Connect TCP.
Appendix B, "Error and Informational Messages," describes messages and resolutions for the BEA Connect TCP system.
Appendix C, "Example Configuration File," provides sample BEA Connect TCP configurations.
Appendix D, "Sample JCL," provides sample Job Control Language (JCL) required to install and execute the BEA Connect TCP application.
Appendix E, "Sample IMS Client and Server Transactions," provides sample IMS Client and Server transactions for use with the BEA Connect TCP application.
Appendix F, "Error and Reason Codes," describes error and reason codes issued by BEA Connect TCP.
Glossary identifies and defines BEA Connect TCP terminology.

How to Use This Manual

Online Document Considerations

This document, BEA Connect TCP for IMS User Guide, is designed primarily as an online, hypertext guide. If you are reading this as a paper publication, note that to get full use from this guide you should install and access it as an online document via a Web browser that supports HTML 3.0. Netscape Navigator 2.02 or Microsoft Internet Explorer 3.0 or later are recommended. (Information on how to install the online documentation is available in the BEA Connect TCP Release Notes.)

Opening the Manual in a Web Browser

To access the online version of this document, open the following HTML file in a Web browser:

http://(directory path to Connect TCP HTML files)/imsbegin.htm

Note: The online documentation requires a Web browser that supports HTML 3.0. Netscape Navigator 2.02 or Microsoft Internet Explorer 3.0 or later are recommended.

Figure 1 shows the online guide with the clickable navigation bar and table of contents.

Figure 1 Connect TCP for IMS User Guide Displayed in Netscape Web Browser

Printing from a Web Browser

You can print a hardcopy version of this document, one file at a time, from the Web browser. Before you print, make sure that the chapter or appendix you want is displayed and selected in your browser. (To select a file, click anywhere inside the frame you want to print. If your browser offers a Print Preview feature, you can use it to verify which file you are about to print.)

Document Conventions

The following documentation conventions are used throughout this manual:


Item	Convention	Example
Arguments	appear in parentheses and are formatted in a lowercase monospace font. Optional arguments are formatted in italic font. Predefined arguments are formatted in an uppercase font.	(`name`, `0`, `value`) (`ACCTID`, `2`, `5000`)
Environment variables	are formatted in an uppercase font.	ENVFILE=${APPDIR}
Glossary terms	are formatted in italics in the printed copy. Online glossary terms are underlined and in color.	Port is the host name of a Jolt server. Port is the host name of a Jolt server.
Key names	are presented in boldface type.	Press Enter to continue.
Literals	are formatted in a monospace font.	`class extendSample`
Programs and applications	are formatted with initial caps.	Use the Repository Editor and the Class Library.
User input	are formatted in a monospace font.	Type `cd TUXDIR`
Window items	are presented in boldface type. Window items can be window titles, button labels, text edit box names or other parts of the window.	Type your password in the Logon window. Select Export to make the service available to the client.