Preface

Purpose of This Manual

This document describes the BEA Connect TCP for CICS product and gives instructions for using the tools for building Connect TCP for CICS applications.

BEA Connect TCP for CICS is a gateway connectivity feature that enables OLTP application programs on BEA TUXEDO systems to perform various non-transactional tasks with application programs that reside on CICS.

This guide explains how to configure and administer BEA Connect TCP for CICS and how it fits into the overall BEA TUXEDO configuration. In addition, this guide:

Lists required software products and features
Explains how BEA Connect TCP processes service requests that originate on remote BEA TUXEDO systems
Explains how BEA Connect TCP affects CICS application programs
Provides conceptual and procedural information that will help you configure and administer BEA Connect TCP

Who Should Read This Manual

This document is primarily for CICS system administrators who will configure and administer BEA Connect TCP. In addition, programmers will find useful pointers for developing client programs and service routines that send data through to the remote BEA TUXEDO Connect TPS gateway.

Prerequisites

Programmers who work with BEA Connect TCP should be familiar with CICS applications development.

System administrators who work with Connect TCP should be familiar with the following concepts, tools, and procedures:

TCP/IP networking
IBM CICS Sockets Interface
Defining new resources to CICS
Standard CICS monitoring tools

How This Manual Is Organized

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

Chapter 1, "Introducing BEA Connect TCP for CICS," introduces BEA Connect TCP, explains how BEA Connect TCP fits into the BEA TUXEDO configuration, and lists MVS software requirements.
Chapter 2, "Understanding How BEA Connect TCP for CICS Works," explains how BEA Connect TCP is started, how it processes services requests, and how it is terminated.
Chapter 3, "Installing BEA Connect TCP for CICS," lists the hardware and software requirements, provides installation instructions for BEA Connect TCP for CICS and includes a list of distribution files and members.
Chapter 4, "Configuring BEA Connect TCP for CICS," provides background information that will prepare you to configure BEA Connect TCP.
Chapter 5, "Administering BEA Connect TCP for CICS," explains how to invoke BEA Connect TCP for CICS and describes various commands you can use to administer BEA Connect TCP.
Chapter 6, "Programming BEA Connect TCP for CICS," provides information that helps programmers develop service routines that send data to the remote BEA Connect TCP gateway.
Appendix A, "Error and Informational Messages," provides a detailed list of the messages BEA Connect TCP generates both for the local CICS log and the remote BEA TUXEDO ULOG.

How to Use This Manual

Online Document Considerations

This document, BEA Connect TCP for CICS 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)/cicbegin.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 BEA Connect TCP for CICS 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	Examples
Variable names	Variable names represent information you must supply or output information that can change; they are intended to be replaced by actual names. Variable names are displayed in italics and can include hyphens but not underscores. The following are examples of variable names in text: error-file-name The when-return value...
Function names in text	C function names are displayed in lower case type and can include parentheses and possibly underscores, as follows: routine_name() COBOL function or subprogram names are displayed in uppercase type without underscores or hyphens, as follows: ROUTINENAME()
Symbolic constants for languages (keywords, error codes, and flags)	C symbolic constants are displayed in uppercase type and can include underscores, as follows: CONSTANT_NAME COBOL symbolic constants are displayed in uppercase type and can include hyphens, as follows: CONSTANT-NAME
User input and screen output	For screen displays and other examples of input and output, user input appears as in the first of the following lines; system output appears as in the second through fourth lines: `dir c:\accounting\data` Volume in drive C is WIN_NT_1 Volume Serial Number is 1234-5678 Directory of C:\ACCOUNTING\DATA
Syntax	Code samples can include the following elements: Variable names can include hyphens but not underscores (e.g., error-file-name) Optional items are enclosed in square brackets: [ ]. If you include an optional item, do not code the square brackets. A required element for which alternatives exist is enclosed in braces {}. The alternatives are separated by the pipe (vertical bar) character: \|. You must include only one of the alternatives for that element. Do not code the braces or pipe character. An ellipsis ( ... ) indicates that the preceding element can be repeated as necessary. C synopsis: int tpacall(char svc, char data, long len, long flags) COBOL statement: CALL "TPACALL" USING TPSVCDEF-REC TPTYPE-REC DATA-REC TPSTATUS-REC.
Omitted code	An ellipsis ( ... ) is used in examples to indicate that code that is not pertinent to the discussion is omitted. The ellipsis can be horizontal or vertical.