System Definitions

All system definitions are required unless a particular definition is specifically noted to be optional. Remember to add the name selected for the &CICSDEF parameter to the list of groups auto-installed during CICS initialization.

Online Definition

If you prefer online definition, you may define the CICS resources using the CEDA transaction as described below.

CICS Application Program definitions are required for the following programs that make up the data engine component of the Services Builder for CICS 3270 Bridge.

Batch Processing

If you prefer to use a batch process for creating the CICS system definitions on the target system, upload the following JCL text file, CICSDEFS, from the CICS_DATA_ENGINE directory of the product CD, following the change specifications at the beginning of the member, then save and submit the job:

//jobname JOB (account)
//*** CREATE CICS DEFINITIONS FOR
//*** SYNAPTA SERVICES BUILDER 
//***  FOR CICS(R) 3270 BRIDGE
//***************************************************
//* PRIOR TO SUBMITTING, CHANGE THE FOLLOWING:
//***************************************************
//*  JOB CARD: TO MEET YOUR INSTALLATION STANDARDS
//*  GLOBAL CHANGE &CICSLOAD
//*    to the prefix of the LOADLIB containing 
//*     DFHCSDUP
//*  GLOBAL CHANGE &CICSREG
//*    to the prefix to the CSD for the target region
//*  GLOBAL CHANGE &PORT
//*    to the desired TCP port for client access
//*   Note that Attachmate recommends and has 
//*     reserved port 2317
//*  GLOBAL CHANGE &TRAN
//*    to the desired Clean up transaction
//*   Note that Attachmate recommends ATMC as the 
//*    Clean up Transaction ID.
//*   The value must match the value used in the 
//*    configuration macro for the Converter 
//*    (XTR1A001).
//*  GLOBAL CHANGE &SAMPTRAN
//*    to the desired supplied sample application
//*    transaction. For example ATMI (if unused at your
//*    installation).
//*  GLOBAL CHANGE &CICSDEF
//*    to the desired RDO group name.

The CICS Web Interface (CWI) Analyzer allows the data engine to receive HTTP-based input over a defined TCP/IP port on the mainframe by analyzing the specific request and passing it along, or by invoking a registered CWI Converter (such as the Web XML converter) and server application program. CWI Analyzer is also capable of filtering out requests from a client and allowing requests from designated clients to exchange XML information with their associated mainframe components. This IP filtering can allow specific IP addresses, IP addresses containing wildcard range designations, or any IP client access to the specified XML processors on the host.

Customization for the CWI Analyzer module can include specification of:

• A default analyzer in the event the HTTP message received is not defined; the default can be set to NONE if unrecognized HTTP should be treated as an invalid request

• XML messages to process

• Associated Web XML Converter name

• Associated Server Application name

• Optional conversion module to be used for code page translation

• Optional unescaping of XML data stream before control is given to the Web XML Converter

• IP addresses that are authorized to exchange XML with CICS

For details, see Customizing the CWI Analyzer Module.

A set of IP addresses can be specified with or without wildcard specifications, and these specifications can be attached to a specific XML message or an IP pool can be created and referenced for multiple XML messages, with each specifying its own Converter and Server programs.

A CICS Transaction Identification must be created for the server program. The name selected must match the cleanup transaction &CTRAN parameter defined in customization module XTR1S003 during installation. The definition should be as follows:

The TCP/IP Service must be defined to allow connection from the local 3270 Services Builder via a TCP port (in this example, 2317) as follows:

Make sure CICS transactions CWXN and CWBA have the appropriate resource level setting, as follows:

TRANSACTIONS CWXN and CWBA
SECURITY 
RESSec : No No | Yes 
CMdsec : No No | Yes 
Extsec : No No | Yes 
TRANSec : 01 1-64 
RSl : 00 0-24 | Public 
PROGRAMS XTR1A000 XTR1A001 and XTR1A002
RSl : 00 0-24 | Public 

CWXN, CWBA, and ATMC must have Class Maximum Tasks set to the highest number of anticipated concurrent tasks.

CICS terminal MODEL definitions must be defined for 3270 models 2, 3, 4, and 5. These names must match the corresponding &MODnFAC parameter in the customization module XTR1S003. (For details, refer to Installing the Data Engine.) The IBM-supplied terminal definition CBRF, the default name shipped for all model types, can be copied and renamed for the model 2 terminal MODEL. The definitions for models 3, 4, and 5 must have their screen rows/columns changed to 32/80, 43/80, and 27,132 respectively. The following chart reflects these definitions.

Installation Verification

This product includes an optional application, ATMHELLO, that can be used to verify that the product was successfully installed.

* For example, ATM1, if unused at your installation.

	Installation, Overview
	Upgrading, Overview
	Installing in UNIX
	Installation Prompts for Management Components in Windows