Configuring and Administering BEA eLink TCP for CICS

 

It is the responsibility of the BEA Tuxedo administrator to set up the configuration file, but close coordination with the BEA Tuxedo application developer and the CICS programmer is necessary.

The following subsections describe the BEA eLink for Mainframe TCP for CICS (hereafter referenced as eLink TCP for CICS) Maintenance System. The BEA eLink TCP for CICS Maintenance System is an online CICS application for use in configuring, maintaining, and administering the eLink TCP for CICS gateway. The following topics explain the Maintenance System:

• Menu Navigation

• The Main Menu

• The Connection Screens

• The Requester Screens

• The Outbound Service Information Screens

• The User Connection ACCOUNT Screens

• The Inbound Service Information Screens

• The Handler Configuration Screens

• Dynamically Configuring eLink TCP for CICS

• Administering the Gateways

To start the administration system, enter the transaction code as defined to CICS in the installation procedure. If the name was not changed during installation, the name of the transaction is BEAM.

 

---

Menu Navigation

You can access any of the following six groups of menus for maintaining connections, requesters, outbound services, the user connection account, inbound services, and Handler configuration. The following table describes how you can use each group of menus.

Menu Type	Use
Connection	To monitor and control configured and active connections
Requester	To configure and maintain remote endpoints
Outbound Service Information	To configure each remote service and specify which Requester to use for each service
User Connection Account	To create and maintain user accounts
Inbound Service Information	To configure services residing locally that are accessed remotely
Handler Configuration	To configure and maintain the local endpoint

 

Each of these topics is discussed in more detail in the following sections.

 

---

The Main Menu

The Main menu (BEAM) gives you access to all the maintenance screens.

BEAPMNU BEA ELINK TCP FOR CICS BEAM M1 SELECTION SCREEN TABLE OPERATION ---------------- ----------- C - CONNECTION 1 - INSERT R - REQUESTER 2 - UPDATE S - OUTBOUND SERVICE INFORMATION 3 - INQUIRE U - USER CONNECTION ACCOUNT 4 - DELETE I - INBOUND SERVICE INFORMATION 5 - BROWSE H - HANDLER CONFIGURATION SELECTION: __ (e.g. R3) ENTER: PROCESS, PF3: EXIT

 

Usage

Use the Main menu to access the screens that make up the maintenance system. To move from the Main menu to a sub-menu, enter the appropriate two-character code. The first character in the code denotes the area in which you want to operate; the second character denotes the operation you want to perform on that area.

The following table lists the codes for the areas of operation.

Table 4-1

Code	Area of Operation
C	Connections
R	Requesters
S	Outbound Service Information
U	User Connection Account
I	Inbound Service Information
H	Handler Configuration

The following table lists the codes for the allowable operations.

Table 4-2

Code	Allowable Operation
1	Insert
2	Update
3	Inquire
4	Delete
5	Browse

Because some operations are not available in all three areas, the following table lists the valid combinations.

.

Enter This Code	To Access This Screen
C2	Update Connection
C3	Inquire Connection
C5	Browse Connection
R1	Insert Requester
R2	Update Requester
R3	Inquire Requester
R4	Delete Requester
R5	Browse Requester
S1	Insert Outbound Service Information
S2	Update Outbound Service Information
S3	Inquire Outbound Service Information
S4	Delete Outbound Service Information
S5	Browse Outbound Service Information
U1	Insert User Connection Account
U2	Update User Connection Account
U3	Inquire User Connection Account
U4	Delete User Connection Account
U5	Browse User Connection Account
I1	Insert Inbound Service Information
I2	Update Inbound Service Information
I3	Inquire Inbound Service information
I4	Delete Inbound Service Information
I5	Browse Inbound Service Information
H2	Update Handler Configuration
H3	Inquire Handler Configuration

 

You can use the maintenance system screens to view and alter a connection, but not to insert (create) or delete a connection. Connections are created and deleted by eLink TCP for CICS in its normal operation.

The maintenance system checks the two-character selection code that you enter and displays the appropriate screen if the code is valid. If the code you enter is not valid, you receive an error message.

 

---

The Connection Screens

The three screens available for maintaining connection instances are labeled Update, Inquiry, and Browse. The respective screens allow you to make an inquiry concerning a specific connection, to browse a list of all connections, or to disable/enable a connection.

A connection instance is an established TCP/IP connection between a remote endpoint and a Requester or a Handler. For the purposes of eLink TCP for CICS, a remote endpoint is an eLink TCP for Tuxedo gateway executing within a remote BEA Tuxedo domain.

PF Keys

The following function keys are available on various connection screens.

Table 4-3 Function Keys

Function Key	Definitions
ENTER	Process the selection code entered
PF3	Transfer to Main Menu
PF5	Transfer to Connections Browse screen
PF7	Display the previous page of records
PF8	Display the next page of records

Note: If you enter data and press PF3 or PF5 before pressing ENTER, the current operation process is aborted and the new screen is displayed.

Update Connection Screen (C2)

Use the UPDATE CONNECTION screen to update a record from the Connection file. When the screen initially displays, the LOGICAL MACHINE NAME and TYPE fields are unprotected. Enter a valid LOGICAL MACHINE NAME (gateway ID) and TYPE and press ENTER. The screen re-displays showing the data from the record you specified and the STATUS field is unprotected. The message RECORD READY FOR UPDATE displays. You can now make changes to the record.

BEAPCON BEA ELINK TCP FOR CICS BEAM C2 UPDATE CONNECTION LOGICAL MACHINE NAME: ________________ TYPE: _ STATUS: MAX MSG SIZE: REQUESTER TASK NUMBER: NUMBER REQUESTS: NUMBER SUCCESS REQS: NUMBER RECONNECTS: NUMBER OPEN SOCKETS: NUMBER SESSIONS ACTIVE: ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
LOGICAL MACHINE NAME	This field name is the gateway ID. Give it a unique name up to 16 characters.Example: (bankmach1) For Requesters, this field name is the LMID associated with the service that the Requester is requesting. For a Handler, this field name is BEAH followed by the task number. The task number of the Handler is given in the BEALOG.
TYPE	The type of connection. Specify I for incoming connections or O for outgoing connections.
STATUS	The status of the connection. Specify E to enable the connection. Specify D for normal shutdown which allows initiated tasks to complete prior to disconnecting. Specify A for immediate shutdown which aborts all initiated tasks and disconnects.
MAX MSG SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. Example: (31000)
REQUESTER TASK NUMBER	The task number of the Requester that is currently associated with the LOGICAL MACHINE NAME. If there is not an active Requester, the task number is for the Requester most recently associated with that LMID. For a Handler, this field is blank; the task number is part of the LMID.
NUMBER REQUESTS	The number of service requests made during this connection.
NUMBER SUCCESS REQS	The number of successful communications.
NUMBER RECONNECTS	The number of successful connections.
NUMBER OPEN SOCKETS	The number of sockets that are currently opened by the Requester.
NUMBER SESSIONS ACTIVE	The number of active sessions on this connection.

 

Inquire Connection Screen (C3)

Use this screen to inquire about a record from the Connection file. When the screen is initially displayed, the LOGICAL MACHINE NAME and TYPE fields are unprotected. Enter a valid LOGICAL MACHINE NAME (gateway ID) and TYPE and press ENTER. The screen is re-displayed with the data from the record you specified and the LOGICAL MACHINE NAME and TYPE fields are unprotected.

BEAPCON BEA ELINK TCP FOR CICS BEAM C3 INQUIRE CONNECTION LOGICAL MACHINE NAME: ________________ TYPE: _ STATUS: MAX MSG SIZE: REQUESTER TASK NUMBER: NUMBER REQUESTS: NUMBER SUCCESS REQS: NUMBER RECONNECTS: NUMBER OPEN SOCKETS: NUMBER SESSIONS ACTIVE: ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
LOGICAL MACHINE NAME	This name is the gateway ID. Specify a unique name up to 16 characters. Example: (bankmach1) For Requesters, this name is the LMID associated with the service that the Requester is requesting. For a Handler, this name is BEAH followed by the task number. The task number of the Handler is given in the BEALOG.
TYPE	The type of connection. I represents incoming connections or O represents outgoing connections.
STATUS	The status of the connection. E means the connection is enabled. D means the connection is designated for a normal shutdown, which allows initiated tasks to complete prior to disconnecting. A means the connection shuts down immediately, aborts all initiated tasks, and disconnects.
MAX MSG SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. Example: (31000)
REQUESTER TASK NUMBER	The task number of the Requester that is currently associated with the LOGICAL MACHINE NAME. If there is not an active Requester, the task number is for the Requester most recently associated with that LMID. For a Handler, this field is blank; the task number is part of the LMID.
NUMBER REQUESTS	The number of service requests made during this connection.
NUMBER SUCCESS REQS	The number of successful communications.
NUMBER RECONNECTS	The number of successful connections.
NUMBER OPEN SOCKETS	The number of sockets that are currently opened by the Requester.
NUMBER SESSIONS ACTIVE	The number of active sessions on this connection.

 

Browse Connection Screen (C5)

Use this screen to browse records in the Connection file and to select individual records for further processing. If you access this screen from the Main menu, the first record on file is displayed at the top of the screen. If you access this screen from the Connection Update screen or the Inquire screen, the list starts with the key received from that screen.

To select a record for processing enter a valid selection code in the SEL CDE field. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used and all others are ignored. After the selection code is validated and processed, the screen for that process is displayed, and the record key appears in the LOGICAL MACHINE NAME field.

BEAPCON BEA ELINK TCP FOR CICS BEAM C5 BROWSE CONNECTION SEL LOGICAL MACHINE STA MAXMSG NUMBER NUMBER NUMBER SOCK SESS ACT CDE NAME TUS SIZE REQS SUCREQ RECONS ETS IONS IVE TYPE --- ---------------- --- ------ ------ ------ ------ ---- ---- --- ---- _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ _ ________________ _ _____ _____ _____ _____ __ __ _ _ * SELCDE = (2: UPD, 3: INQ) ENTER: PROCESS, PF3: MENU, PF7: PREV, PF8: NEXT BEG/END OF FILE

 

 

---

The Requester Screens

A Requester is responsible for collecting request information to be sent to the remote BEA Tuxedo domain. The Requester establishes network connectivity, transmits data to BEA Tuxedo, and receives data from BEA Tuxedo. Each Requester is responsible for one and only one remote endpoint (or one TCP/IP address/port combination). You can configure multiple Requesters to point to the same endpoint, but each Requester can have only one endpoint.

On the following maintenance screens, each instance of the Requester is given a logical machine ID (LMID). You can give a Requester any unique LMID that is meaningful to you. Every service name is associated with one LMID. This method allows the Requester to know which remote machine is responsible for a particular service.

PF Keys

The following table lists function keys available on various requester screens.

Table 4-4 Function Keys

Function Key	Function
ENTER	Process the selection code entered
PF3	Transfer to Main menu
PF5	Transfer to Requester Browse screen
PF7	Display the previous page of records
PF8	Display the next page of records

Note: If you enter data and press PF3 or PF5 before pressing ENTER, the operation process is aborted and the appropriate screen is displayed.

Insert Requester Screen (R1)

Use this screen to configure a new Requester by inserting a new record into the Requester file.

When the screen is first displayed, all the fields are unprotected. Type the required data, then press ENTER. After the data is validated and processed, the screen is re-displayed and all the fields are unprotected.

BEAPREQ BEA ELINK TCP FOR CICS BEAM R1 INSERT REQUESTER LMID: ________________ MULTIPLEX_CNT: __ DNS: ________________________________________________________________ HOST ADDRESS: _______________ PORT NUMBER: _____ MIN TIME (MILLISEC): _____ SECURITY(Y/N): _ MAX TIME (MILLISEC): _____ ACCOUNT ID: ________ DELTA TIME (MILLISEC): _____ PASSWORD: IDLE TIME (SECONDS): _____ REQ IDLE TIME (SECONDS): _____ MAX QUEUE SIZE: _____ LATENCY TIME (SECONDS): __ MAX MSG SIZE: _____ MAX CONNS: __ RETRY LIMIT: _____ IBM TCP(Y/N): _ LMID TYPE: _ QUEUE NAME 1: ________ START TRAN-ID: ____ QUEUE NAME 2: ________ CICS DATA: ___ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
LMID	This name is the logical machine name or gateway ID. Give it a unique name up to 16 characters. Example: (bankmach1)
DNS	The host name that the domain name service recognizes.
HOST ADDRESS	The TCP/IP dot address. Example: (199.99.99.99)
PORT NUMBER	The TCP port. Check with the TCP/IP administrator for available ports. Example: (1234)
SECURITY	The status of connection-level security. Y specifies that security is on and N denotes that security is off. Note: For additional security information, refer to the Configuring the eLink TCP Security section.
ACCOUNT ID	An eight-character ID. This ID must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN2)
MAX QUEUE SIZE	Specifies the size of the local queue where requests are stored for servicing. A typical setting is 200.
MAX MSG SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. Example: (4096)
RETRY LIMIT	If the connection fails, this number determines how many attempts the system makes to reestablish the connection before marking the connection disabled. Example: (5).
LMID TYPE	The type of gateway the remote system is running (C for CICS, I for IMS, T for Tuxedo, L for InterLink)
START TRANID	The ID of the transaction to be started if the remote system type is CICS.
CICS DATA	A string to be passed to the IBM TCP/IP Listener for use with the eLink TCP for CICS gateway. The default is " ".
MULTIPLEX CNT	The number of concurrent requests for each connection.
MIN TIME	The minimum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: The recommended value for running with Interlink CPT is 400. For information about recommended configuration values and system behavior, refer to the BEA eLink TCP Release Notes.
MAX TIME	The maximum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: If you are running Interlink CPT, this value is rounded up to the nearest second. The recommended value for running with Interlink CPT is less than or equal to 3000. For information about recommended configuration values and system behavior, refer to the BEA eLink TCP Release Notes.
DELTA TIME	The time increase (in milliseconds) from MIN TIME to MAX TIME. Note: The recommended value for running with Interlink CPT is greater than 50. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
IDLE TIME	The amount of time in seconds that a connection is idle before it is closed. IDLE TIME should be a smaller amount of time than REQ IDLE TIME. A typical setting is 30 seconds.
REQ IDLE TIME	The amount of time in seconds that a Requester is idle before it terminates. A typical setting is 120 seconds.
LATENCY TIME	Network time and system processing time added to give a true system wait time (in seconds).
MAX CONNS	The maximum number of connections the Requester opens. The maximum value is 50 for IBM TCP/IP. The maximum value is 1 for InterLink.
IBM TCP	The TCP/IP stack being used. Specify Y if the IBM TCP/IP stack is being used or N if the Interlink stack is being used.
QUEUE NAME 1	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.
QUEUE NAME 2	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.

 

Update Requester Screen (R2)

Use this screen to update a record from the Requester file. The fields are the same as the ones on the Requester Insert screen, but on this screen you can change the values.

When the screen is first displayed, the LMID field is unprotected. Enter a logical machine name and press ENTER. The screen is re-displayed showing the data from the requested record. The HOST ADDRESS, PORT NUMBER, ACCOUNT ID, PASSWORD, MAX MSG SIZE, and CONNECT RETRY LIMIT fields are unprotected. The following message is displayed: RECORD READY FOR UPDATE.

After the changes you entered are validated and processed, the screen is re-displayed and the LMID field is unprotected.

BEAPREQ BEA ELINK TCP FOR CICS BEAM R2 UPDATE REQUESTER LMID: ________________ MULTIPLEX_CNT: __ DNS: ________________________________________________________________ HOST ADDRESS: _______________ PORT NUMBER: _____ MIN TIME (MILLISEC): _____ SECURITY(Y/N): _ MAX TIME (MILLISEC): _____ ACCOUNT ID: ________ DELTA TIME (MILLISEC): _____ PASSWORD: IDLE TIME (SECONDS): _____ REQ IDLE TIME (SECONDS): _____ MAX QUEUE SIZE: _____ LATENCY TIME (SECONDS): __ MAX MSG SIZE: _____ MAX CONNS: __ RETRY LIMIT: _____ IBM TCP(Y/N): _ LMID TYPE: _ QUEUE NAME 1: ________ START TRAN-ID: ____ QUEUE NAME 2: ________ CICS DATA: ___ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
LMID	This name is the logical machine name or gateway ID. Give it a unique name up to 16 characters. Example: (bankmach1)
DNS	The host name that the Domain Name Service recognizes.
HOST ADDRESS	The TCP/IP dot address. Example: (199.99.99.99)
PORT NUMBER	The TCP port. Check with the TCP/IP administrator for available ports. Example: (1234)
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off. Note: For additional security information, refer to Configuring the eLink TCP Security.
ACCOUNT ID	An eight-character ID for connection security. This ID must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password for connection security. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)
MAX QUEUE SIZE	Specifies the size of the local queue where requests are stored for servicing. A typical setting is 200.
MAX MSG SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. Example: (4096)
RETRY LIMIT	If the connection fails, this number determines how many attempts the system makes to reestablish the connection before marking the connection disabled. Example: (5)
LMID TYPE	The type of gateway the remote system is running (C for CICS, I for IMS, T for Tuxedo, L for InterLink)
START TRANID	The ID of the transaction to be started if the remote system type is CICS.
CICS DATA	A string to be passed to the IBM TCP/IP Listener for use with the eLink TCP for CICS gateway. The default is " ".
MULTIPLEX CNT	The number of concurrent requests for each connection.
MIN TIME	The minimum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: The recommended value for running with Interlink CPT is 400. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
MAX TIME	The maximum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: If you are running Interlink CPT, this value is rounded up to the nearest second. The recommended value for running with Interlink CPT is less than or equal to 3000. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
DELTA TIME	The time increase (in milliseconds) from MIN TIME to MAX TIME. Note: The recommended value for running with Interlink CPT is greater than 50. For information about recommended configuration values and system behavior, refer to the BEA eLink TCP Release Notes.
IDLE TIME	The amount of time in seconds that a connection is idle before it is closed. IDLE TIME should be a smaller amount of time than REQ IDLE TIME. A typical setting is 30 seconds.
REQ IDLE TIME	The amount of time in seconds that a Requester is idle before it terminates. A typical setting is 120 seconds.
LATENCY TIME	Network time and system processing time added to give a true system wait time (in seconds).
MAX CONNS	The maximum number of connections the Requester opens. The maximum value is 50 for IBM TCP/IP. The maximum value is 1 for InterLink.
IBM TCP	The TCP/IP stack being used. Specify Y if the IBM TCP/IP stack is being used or N if the Interlink stack is being used.
QUEUE NAME 1	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.
QUEUE NAME 2	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.

 

Inquire Requester Screen (R3)

Use this screen to make an inquiry about a record from the Requester file. The screen is initially displayed with the LOGICAL MACHINE NAME field unprotected. Enter the logical machine name and press ENTER. The screen is re-displayed with the data from the requested record and the LOGICAL MACHINE NAME field is unprotected.

BEAPREQ BEA ELINK TCP FOR CICS BEAM R3 INQUIRE REQUESTER LMID: ________________ MULTIPLEX_CNT: __ DNS: ________________________________________________________________ HOST ADDRESS: _______________ PORT NUMBER: _____ MIN TIME (MILLISEC): _____ SECURITY(Y/N): _ MAX TIME (MILLISEC): _____ ACCOUNT ID: ________ DELTA TIME (MILLISEC): _____ PASSWORD: IDLE TIME (SECONDS): _____ REQ IDLE TIME (SECONDS): _____ MAX QUEUE SIZE: _____ LATENCY TIME (SECONDS): __ MAX MSG SIZE: _____ MAX CONNS: __ RETRY LIMIT: _____ IBM TCP(Y/N): _ LMID TYPE: _ QUEUE NAME 1: ________ START TRAN-ID: ____ QUEUE NAME 2: ________ CICS DATA: ___ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
LMID	This name is the logical machine name or gateway ID. This name is a unique name up to 16 characters. Example: (bankmach1)
DNS	The host name that the domain Name Service recognizes.
HOST ADDRESS	The TCP/IP dot address. Example: (199.99.99.99)
PORT NUMBER	The TCP/IP port. Check with the TCP/IP administrator for available ports. Example: (1234)
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off. Note: For additional security information, refer to the Configuring the eLink TCP Security section.
ACCOUNT ID	An eight-character ID. This ID must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as the password used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)
MAX QUEUE SIZE	Specifies the size of the local queue where requests are stored for servicing. A typical setting is 200.
MAX MSG SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. Example: (4096)
RETRY LIMIT	If the connection fails, this number determines how many attempts the system makes to reestablish the connection before marking the connection disabled. Example: (5).
LMID TYPE	The type of gateway the remote system is running (C for CICS, I for IMS, T for Tuxedo, L for InterLink)
START TRANID	The ID of the transaction to be started if the remote system type is CICS.
CICS DATA	A string to be passed to the IBM TCP/IP Listener for use with the eLink TCP for CICS gateway. The default is " ".
MULTIPLEX CNT	The number of concurrent requests for each connection.
MIN TIME	The minimum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: The recommended value for running with Interlink CPT is 400. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
MAX TIME	The maximum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: If you are running Interlink CPT, this value is rounded up to the nearest second. The recommended value for running with Interlink CPT is less than or equal to 3000. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
DELTA TIME	The time increase (in milliseconds) from MIN TIME to MAX TIME. Note: The recommended value for running with Interlink CPT is greater than 50. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
IDLE TIME	The amount of time in seconds that a connection is idle before it is closed. IDLE TIME should be a smaller amount of time than REQ IDLE TIME. A typical setting is 30 seconds.
REQ IDLE TIME	The amount of time in seconds that a Requester is idle before it terminates. A typical setting is 120 seconds.
LATENCY TIME	Network time and system processing time added to give a true system wait time (in seconds).
MAX CONNS	The maximum number of connections the Requester opens. The maximum value is 50 for IBM TCP/IP. The maximum value is 1 for InterLink.
IBM TCP	The TCP/IP stack being used. Specify Y if the IBM TCP/IP stack is being used or N if the Interlink stack is being used.
QUEUE NAME 1	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.
QUEUE NAME 2	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.

 

Delete Requester Screen (R4)

Use this screen to delete a record from the Requester file.

Warning: Deleting a Requester record can have serious ramifications. Think carefully before performing this operation. If there are any Service records that point to this GWID, any client calls to those services are rejected because BEA eLink does not know to which remote machine the request should go.

The screen is initially displayed with the LOGICAL MACHINE NAME field unprotected. Enter the logical machine name and press ENTER. The screen is then re-displayed with the data from the requested record and the LOGICAL MACHINE NAME field is protected. The following message is displayed: TO CONFIRM DELETE, PRESS ENTER AGAIN.

BEAPREQ BEA ELINK TCP FOR CICS BEAM R4 DELETE REQUESTER LMID: ________________ MULTIPLEX_CNT: __ DNS: ________________________________________________________________ HOST ADDRESS: _______________ PORT NUMBER: _____ MIN TIME (MILLISEC): _____ SECURITY(Y/N): _ MAX TIME (MILLISEC): _____ ACCOUNT ID: ________ DELTA TIME (MILLISEC): _____ PASSWORD: IDLE TIME (SECONDS): _____ REQ IDLE TIME (SECONDS): _____ MAX QUEUE SIZE: _____ LATENCY TIME (SECONDS): __ MAX MSG SIZE: _____ MAX CONNS: __ RETRY LIMIT: _____ IBM TCP(Y/N): _ LMID TYPE: _ QUEUE NAME 1: ________ START TRAN-ID: ____ QUEUE NAME 2: ________ CICS DATA: ___ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
LMID	This name is the logical machine name or gateway ID. This name is a unique name up to 16 characters. Example: (bankmach1)
DNS	The host name that the domain Name Service recognizes.
HOST ADDRESS	The TCP/IP dot address. Example: (199.99.99.99)
PORT NUMBER	The TCP/IP port. Check with the TCP/IP administrator for available ports. Example: (1234)
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off. Note: For additional security information, refer to the Configuring the eLink TCP Security section.
ACCOUNT ID	An eight-character ID. This name must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)
MAX QUEUE SIZE	Specifies the size of the local queue where requests are stored for servicing. A typical setting is 200.
MAX MSG SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. Example: (4096)
RETRY LIMIT	If the connection fails, this number determines how many attempts the system makes to reestablish the connection before marking the connection disabled. Example: (5).
LMID TYPE	The type of gateway the remote system is running (C for CICS, I for IMS, T for Tuxedo, L for InterLink)
START TRANID	The ID of the transaction to be started if the remote system type is CICS.
CICS DATA	A string to be passed to the IBM TCP/IP Listener for use with the eLink TCP for CICS gateway. The default is " ".
MULTIPLEX CNT	The number of concurrent requests for each connection.
MIN TIME	The minimum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: The recommended value for running with Interlink CPT is 400. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
MAX TIME	The maximum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: If you are running Interlink CPT, this value is rounded up to the nearest second. The recommended value for running with Interlink CPT is less than or equal to 3000. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
DELTA TIME	The time increase (in milliseconds) from MIN TIME to MAX TIME. Note: The recommended value for running with Interlink CPT is greater than 50. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
IDLE TIME	The amount of time in seconds that a connection is idle before it is closed. IDLE TIME should be a smaller amount of time than REQ IDLE TIME. A typical setting is 30 seconds.
REQ IDLE TIME	The amount of time in seconds that a Requester is idle before it terminates. A typical setting is 120 seconds.
LATENCY TIME	Network time and system processing time added to give a true system wait time (in seconds).
MAX CONNS	The maximum number of connections the Requester opens. The maximum value is 50 for IBM TCP/IP. The maximum value is 1 for InterLink.
IBM TCP	The TCP/IP stack being used. Specify Y if the IBM TCP/IP stack is being used or N if the Interlink stack is being used.
QUEUE NAME 1	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.
QUEUE NAME 2	The unique name of a TS Q that is used for communications between the Pre-requester and the Requester.

 

Browse Requester Screen (R5)

Use this screen to browse a list of the records in the Requester file. Additionally, you can select a record for further processing by entering a valid selection code in the first column of that record's row.

If you access this screen from the Main menu, the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the key received from that screen determines which records are displayed.

To choose a record, enter a valid selection code in the SEL CDE field next to that record. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used and the others are ignored.

After the entry in the SEL CDE field is validated and processed, the screen for that process is displayed and the record key appears in the LOGICAL MACHINE NAME field.

BEAPREQ BEA ELINK TCP FOR CICS BEAM R5 BROWSE REQUESTER SEL LOGICAL MACHINE HOST PORT MAXM CONN LMID START CDE NAME ADDRESS NUM SIZE R-LIM TYPE TRNID --- ---------------- --------------- ----- ----- ----- ---- ----- _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ _ ________________ _______________ _____ _____ _____ _ ____ * SELCDE = (1: INS, 2: UPD, 3: INQ, 4: DEL) ENTER: PROCESS, PF3: MENU, PF7: PREV, PF8: NEXT RECORD NOT FOUND

 

 

---

The Outbound Service Information Screens

A service is a name associated with some component of work. That component of work might be a banking transaction, an airline flight reservation, or an order for a dozen widgets. In BEA Tuxedo, a client program that needs work done makes a "service request." A process called a server performs the work described in the service request on behalf of the client, then returns the results of its efforts back to the client. In MVS this process would be referred to as a call to a "black box."

In a CICS application that uses eLink TCP for CICS, a service name is passed in the data area in an EXEC CICS LINK command and the results are returned in that same area. The service screens use the terms "service name" and "remote service name." The service name (such as, CIC01XXYYZZ) is what the service is known as to your CICS environment and the remote service name (such as, WITHDRAWL) is what the service is known as to BEA Tuxedo. For simplicity, you can make both names the same, but if naming conventions differ, you can use different names.

PF Keys

The following table lists function keys available on various outbound service screens.

Table 4-5 Function Keys

Function Key	Function
ENTER	Process the selection code entered
PF3	Transfer to Main menu
PF5	Transfer to Browse screen
PF7	Display the previous page of records
PF8	Display the next page of records

Note: If you enter data and press PF3 or PF5 before pressing ENTER, the operation process is aborted and the appropriate screen is displayed.

Insert Outbound Service Information Screen (S1)

Use this screen to insert a record into the service name file. The screen is first displayed with all fields unprotected. Enter the required data in the appropriate fields and press ENTER. After the data is validated and processed, the screen is re-displayed and all the fields are unprotected.

BEAPSVC BEA ELINK TCP FOR CICS BEAM S1 INSERT OUTBOUND SERVICE INFORMATION SERVICE NAME: ________________ LOGICAL MACHINE NAME: ________________ REMOTE SERVICE NAME: ________________ SERVICE TIMEOUT(SEC): _____ SECURITY(Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
SERVICE NAME	The service name as it is known to the CICS programmer.
LOGICAL MACHINE NAME	This name is a symbolic name as it was defined on the Requester Insert screen. It denotes the remote machine on which this service should be processed.
REMOTE SERVICE NAME	The name as it is known in the remote BEA Tuxedo domain.
SERVICE TIMEOUT	The number of seconds to wait for timing out this service request.
SECURITY	The status of request-level security. Y specifies that security is on and N denotes that security is off.

 

Update Outbound Service Information Screen (S2)

Use this screen to update a record from the service name file. When the screen is first displayed, the SERVICE NAME field is unprotected. Enter the service name and press ENTER. The screen is then re-displayed with the data from the requested record and the LOGICAL MACHINE NAME, REMOTE SERVICE NAME, SERVICE TIMEOUT(SEC), and SECURITY fields are unprotected. The following message is displayed: RECORD READY FOR UPDATE.

After the changes are validated and processed, the screen is re-displayed and the SERVICE NAME field is unprotected.

BEAPSVC BEA ELINK TCP FOR CICS BEAM S2 UPDATE OUTBOUND SERVICE INFORMATION SERVICE NAME: ________________ LOGICAL MACHINE NAME: ________________ REMOTE SERVICE NAME: ________________ SERVICE TIMEOUT(SEC): _____ SECURITY(Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
SERVICE NAME	The service name as it is known to the CICS programmer.
LOGICAL MACHINE NAME	This name is a symbolic name as it was defined on the Update Outbound Service Information screen. It denotes the remote machine on which this service should be processed.
REMOTE SERVICE NAME	The name as it is known in the remote BEA Tuxedo domain.
SERVICE TIMEOUT	The number of seconds to wait for timing out this service request.
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off.

 

Inquire Outbound Service Information Screen (S3)

Use this screen to make an inquiry about a record from the SERVICE NAME file. The screen is initially displayed with the SERVICE NAME field unprotected. Enter the service name and press ENTER. The screen is re-displayed with the data from the requested record and the SERVICE NAME field is unprotected.

BEAPSVC BEA ELINK TCP FOR CICS BEAM S3 INQUIRE OUTBOUND SERVICE INFORMATION SERVICE NAME: ________________ LOGICAL MACHINE NAME: ________________ REMOTE SERVICE NAME: ________________ SERVICE TIMEOUT(SEC): _____ SECURITY(Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
SERVICE NAME	The service name as it is known to the CICS programmer.
LOGICAL MACHINE NAME	This name is a symbolic name as it was defined on the Inquire Outbound Service Information screen. It denotes the remote machine on which this service should be processed.
REMOTE SERVICE NAME	The name as it is known in the remote BEA Tuxedo domain.
SERVICE TIMEOUT	The number of seconds to wait for timing out this service request.
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off.

 

Delete Outbound Service Information Screen (S4)

Use this screen to delete records from the service name file. The screen is initially displayed with the SERVICE NAME field unprotected. Type the service name and press ENTER. The screen is re-displayed with the data from the record requested and all the fields protected.

The following message is displayed: TO CONFIRM DELETE, PRESS ENTER: AGAIN. After you press enter to confirm the deletion, the screen is re-displayed and the SERVICE NAME field is unprotected.

BEAPSVC BEA ELINK TCP FOR CICS BEAM S4 DELETE OUTBOUND SERVICE INFORMATION SERVICE NAME: ________________ LOGICAL MACHINE NAME: ________________ REMOTE SERVICE NAME: ________________ SERVICE TIMEOUT(SEC): _____ SECURITY(Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
SERVICE NAME	The service name as it is known to the CICS programmer.
LOGICAL MACHINE NAME	This name is a symbolic name as it was defined on the Delete Outbound Service Information screen. It denotes the remote machine on which this service should be processed.
REMOTE SERVICE NAME	The name as it is known in the remote BEA Tuxedo domain.
SERVICE TIMEOUT	The number of seconds to wait for timing out this service request.
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off.

 

Browse Outbound Service Information Screen (S5)

Use this screen to browse the records in the service name file. If you access this screen from the Main menu the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the list starts with the record key received from that screen.

To select a record for processing, enter a valid selection code. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used, and the others are ignored. After the selection code is validated and processed, the screen for that process is displayed and the record key appears in the SERVICE NAME field.

BEAPSVC BEA ELINK TCP FOR CICS BEAM S5 BROWSE SERVICE NAME SEL SERVICE LOGICAL MACHINE REMOTE SERVICE SERVICE CDE NAME NAME NAME TIMEOUT SEC --- ---------------- ---------------- ---------------- ------- --- _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ _ ________________ ________________ ________________ _____ _ * SELCDE = (1 -INS, 2 -UPD, 3 -INQ, 4 -DEL) ENTER: PROCESS, PF3: MENU, PF7: PREV, PF8: NEXT RECORD NOT FOUND

 

 

---

The User Connection ACCOUNT Screens

A Handler is responsible for receiving service requests from the remote BEA Tuxedo domain. The User Connection ACCOUNT screens allow for dynamic manipulation of accounts allowed to connect with a Handler when a Handler is configured with security enabled.

PF Keys

The following table lists function keys available on various user account screens.

Table 4-6 Function Keys

Function Key	Function
ENTER	Process the selection code entered
PF3	Transfer to Main menu
PF5	Transfer to Browse screen
PF7	Display the previous page of records
PF8	Display the next page of records

Note: If you enter data and press PF3 or PF5 before pressing ENTER, the operation process is aborted and the appropriate screen is displayed.

Insert User Connection ACCOUNT Screen (U1)

Use this screen to add a new Connection ACCOUNT by inserting a new record into the user file.

When the screen is first displayed, all the fields are unprotected. Type the required data as described in the table below, then press ENTER. After the data is validated and processed, the screen is re-displayed and all the fields are unprotected.

BEAPUSR BEA ELINK TCP FOR CICS BEAM U1 INSERT USER CONNECTION ACCOUNT ACCOUNT: ________ PASSWORD: ________ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
ACCOUNT	An eight-character ID. This name must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)

 

Update User Connection ACCOUNT Screen (U2)

Use this screen to update a record on the account file. When the screen is first displayed, the ACCOUNT field is unprotected. Enter the account ID, and press ENTER. The screen is then re-displayed with the data from the requested record and the PASSWORD field is unprotected. The following message is displayed: RECORD READY FOR UPDATE.

After the changes are validated and processed, the screen is re-displayed and the ACCOUNT field is unprotected.

BEAPUSR BEA ELINK TCP FOR CICS BEAM U2 UPDATE USER CONNECTION ACCOUNT ACCOUNT: ________ PASSWORD: ________ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
ACCOUNT	An eight-character ID. This name must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)

 

Inquire User Connection ACCOUNT Screen (U3)

Use this screen to make an inquiry about a record from the account file. The screen is initially displayed with the ACCOUNT field unprotected. Enter the ACCOUNT and press ENTER. The screen is re-displayed with the data from the requested record and the ACCOUNT field is unprotected.

BEAPUSR BEA ELINK TCP FOR CICS BEAM U3 INQUIRE USER CONNECTION ACCOUNT ACCOUNT: ________ PASSWORD: ________ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
ACCOUNT	An eight-character ID. This name must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)

 

Delete User Connection ACCOUNT Screen (U4)

Use this screen to delete a record from the account file. The screen is initially displayed with the ACCOUNT field unprotected. Type the service name and press ENTER. The screen is re-displayed with the data from the record requested and all the fields protected.

The following message is displayed: TO CONFIRM DELETE, PRESS ENTER: AGAIN. After you press enter to confirm the deletion, the screen is re-displayed and the ACCOUNT field is unprotected.

BEAPUSR BEA ELINK TCP FOR CICS BEAM U4 DELETE USER CONNECTION ACCOUNT ACCOUNT: ________ PASSWORD: ________ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
ACCOUNT	An eight-character ID. This name must be the same ID that is used on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the PASSWORD field. Example: (CICS001A)
PASSWORD	An eight-character password. This password must be the same as on the BEA Tuxedo-side configuration. Coordinate with the BEA Tuxedo Administrator. Required if there is an entry in the ACCOUNT ID field. Example: (LETMEIN1)

 

The Browse User Connection ACCOUNT Screen (U5)

Use this screen to browse the records in the account file. If you access this screen from the Main menu the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the list starts with the record key received from that screen.

To select a record for processing, enter a valid selection code. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used, and the others are ignored.

BEAPUSR BEA ELINK TCP FOR CICS BEAM U5 BROWSE USER CONNECTION ACCOUNTS SEL CDE ACCOUNT ----- ---------- _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ * SELCDE = (1: INS, 2: UPD, 3: INQ, 4: DEL) ENTER: PROCESS, PF3: MENU, PF7: PREV, PF8: NEXT BEG/END OF FILE

 

 

---

The Inbound Service Information Screens

A service is a name associated with some component of work. That component of work can be a banking transaction, an airline flight reservation, or an order for a dozen widgets. In BEA Tuxedo, a client program that needs work done makes a service request. A server performs the work described in the service request on behalf of the client, then returns the results of its efforts back to the client. In MVS this would be referred to as a call to a "black box."

The service screens use the terms LOCAL SERVICE NAME and REMOTE SERVICE NAME. The LOCAL SERVICE NAME (such as, CIC01XXYYZZ) is what the service is known as to your CICS environment and the REMOTE SERVICE NAME (such as, WITHDRAWL) is what the service is known as to BEA Tuxedo. For simplicity, you can make both names the same; however, different names can be used. Changes to the inbound service file are only picked up when the Handler is restarted.

PF Keys

The following table lists function keys available on various inbound service screens.

Table 4-7 Function Keys

Function Key	Function
ENTER	Process the data entered
PF3	Transfer to Main menu
PF5	Transfer to Browse screen
PF7	Display the previous page of records
PF8	Display the next page of records

Note: If you enter data and press PF3 or PF5 before pressing ENTER, the operation process is aborted and the appropriate screen is displayed.

Insert Inbound Service Information Screen (I1)

Use this screen to insert a record into the service name file. The screen is first displayed with all fields unprotected. Enter the required data in the following fields and press ENTER. After the data is validated and processed, the screen is re-displayed and all the fields are unprotected.

BEAPISN BEA ELINK TCP FOR CICS BEAM I1 INSERT INBOUND SERVICE INFORMATION REMOTE SERVICE NAME: ________________ LOCAL SERVICE NAME: ________________ TRANSACTION NAME: ____ MAX MESSAGE SIZE: _____ SECURITY (Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
REMOTE SERVICE NAME	The service name as it is known in the remote BEA Tuxedo domain.
LOCAL SERVICE NAME	The service name as it is known to the CICS programmer.
TRANSACTION NAME	The name of the CICS transaction that is started to process this service request. This transaction is usually the transaction for the Application Handler program which is BEAA by default. For information about programming services without a reply, refer to the Programming BEA eLink TCP for CICS section. Note: Services sending requests using a tpacall with the TPNOREPLY flag set must have a unique TRANSACTION NAME associated with it. Do not use the TRANSACTION NAME for the Application Handler program or an error message results.
MAX MESSAGE SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. This size is the size of the actual data; eLink TCP manages additional message size through its internal headers.
SECURITY	The status of security. Y enables security for the specified service and N disables security for the specified service.

 

Update Inbound Service Information Screen (I2)

Use this screen to update a record in the inbound service name file. The screen is first displayed with the REMOTE SERVICE NAME field unprotected. Enter the remote service name and press ENTER. The screen is re-displayed with the data from the requested record and the LOCAL SERVICE NAME, TRANSACTION NAME, MAX MESSAGE SIZE, and SECURITY fields unprotected. The following message displays: RECORD READY FOR UPDATE.

After the changes are validated and processed, the screen is re-displayed and the REMOTE SERVICE NAME field is unprotected.

BEAPISN BEA ELINK TCP FOR CICS BEAM I2 UPDATE INBOUND SERVICE INFORMATION REMOTE SERVICE NAME: ________________ LOCAL SERVICE NAME: ________________ TRANSACTION NAME: ____ MAX MESSAGE SIZE: _____ SECURITY (Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
REMOTE SERVICE NAME	The service name as it is known in the remote BEA Tuxedo domain.
LOCAL SERVICE NAME	The service name as it is known to the CICS programmer.
TRANSACTION NAME	The name of the CICS transaction that is started to process this service request. This transaction is usually the transaction for the Application Handler program which is BEAA by default. For information about programming services without a reply, refer to the Programming BEA eLink TCP for CICS section. Note: Services sending requests using a tpacall with the TPNOREPLY flag set must have a unique TRANSACTION NAME associated with it. Do not use the TRANSACTION NAME for the Application Handler program or an error message results.
MAX MESSAGE SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. This is the size of the actual data; eLink TCP manages additional message size through its internal headers.
SECURITY	The status of security. Y enables security for the specified service and N disables security for the specified service.

 

Inquire Inbound Service Information Screen (I3)

Use this screen to inquire about a record in the inbound service name file. The screen is first displayed with the REMOTE SERVICE NAME field unprotected. Enter the remote service name and press ENTER. The screen is re-displayed with the data from the requested record and the REMOTE SERVICE NAME field unprotected.

BEAPISN BEA ELINK TCP FOR CICS BEAM I3 INQUIRE INBOUND SERVICE INFORMATION REMOTE SERVICE NAME: ________________ LOCAL SERVICE NAME: ________________ TRANSACTION NAME: ____ MAX MESSAGE SIZE: _____ SECURITY (Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
REMOTE SERVICE NAME	The service name as it is known in the remote BEA Tuxedo domain.
LOCAL SERVICE NAME	The service name as it is known to the CICS programmer.
TRANSACTION NAME	The name of the CICS transaction that is started to process this service request. This transaction is usually the transaction for the Application Handler program which is BEAA by default. For information about programming services without a reply, refer to the Programming BEA eLink TCP for CICS section. Note: Services sending requests using a tpacall with the TPNOREPLY flag set must have a unique TRANSACTION NAME associated with it. Do not use the TRANSACTION NAME for the Application Handler program or an error message results.
MAX MESSAGE SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. This is the size of the actual data; eLink TCP manages additional message size through its internal headers.
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off.

 

Delete Inbound Service Information Screen (I4)

Use this screen to delete a record in the inbound service name file. The screen is first displayed with the REMOTE SERVICE NAME field unprotected. Enter the remote service name and press ENTER. The screen is re-displayed with the data from the record requested and all fields protected. The following message displays: TO CONFIRM DELETE, PRESS ENTER AGAIN. After you press ENTER to confirm the deletion, the screen is re-displayed and the REMOTE SERVICE NAME field is unprotected.

BEAPISN BEA ELINK TCP FOR CICS BEAM I4 DELETE INBOUND SERVICE INFORMATION REMOTE SERVICE NAME: ________________ LOCAL SERVICE NAME: ________________ TRANSACTION NAME: ____ MAX MESSAGE SIZE: _____ SECURITY (Y/N): _ ENTER: PROCESS, PF3: MENU, PF5: BROWSE

 

Fields

Field Name	Description
REMOTE SERVICE NAME	The service name as it is known in the remote BEA Tuxedo domain.
LOCAL SERVICE NAME	The service name as it is known to the CICS programmer.
TRANSACTION NAME	The name of the CICS transaction that is started to process this service request. This service request is usually the transaction for the Application Handler program. For information about programming services without a reply, refer to the Programming BEA eLink TCP for CICS section. Warning: Services sending requests using a tpacall with the TPNOREPLY flag set must have a unique TRANSACTION NAME associated with it. Do not use the TRANSACTION NAME for the Application Handler program or an error message results.
MAX MESSAGE SIZE	The largest message allowed to be sent across this connection. The maximum is 32000. This is the size of the actual data; eLink TCP manages additional message size through its internal headers.
SECURITY	The status of security. Y specifies that security is on and N denotes that security is off.

 

The Browse Inbound Service Screen (I5)

Use this screen to browse the records in the inbound service name file. If you access this screen from the Main menu, the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the list starts with the record key received from that screen.

To select a record for processing, enter a valid selection code. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used, and the others are ignored. After the selection code is validated and processed, the screen for that process is displayed and the record key appears in the REMOTE SERVICE NAME field.

BEAPISN BEA ELINK TCP FOR CICS BEAM I5 BROWSE INBOUND SERVICE SEL REMOTE SERVICE LOCAL SERVICE TRAN MAXM CDE NAME NAME NAME SIZE SEC --- ---------------- ---------------- ---- ----- --- _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ _ ________________ ________________ ____ _____ _ * SELCDE = (1 -INS, 2 -UPD, 3 -INQ, 4 -DEL) ENTER: PROCESS, PF3: MENU, PF7: PREV, PF8: NEXT RECORD NOT FOUND

 

 

---

The Handler Configuration Screens

A Handler is responsible for receiving service requests from the remote BEA Tuxedo domain. The Handler Configuration screens allow for dynamic manipulation of the configuration used by all Handler programs in the system.

Note: To apply changes that have been made to the Handler Configuration file, you must restart the Handler.

PF Keys

The following table lists the function keys available on various user account screens.

Table 4-8 Function Keys

Function Key	Function
ENTER	Process the data entered
PF3	Transfer to Main menu

Note: If you enter data and press PF3 before pressing ENTER, the operation process is aborted and the appropriate screen is displayed.

Update Handler Configuration Screen (H2)

Use this screen to update the configuration record on the user file. If a record does not exist, one is inserted into the user file. When the screen first displays, all fields are unprotected. After the changes are validated and processed, the screen is re-displayed.

BEAPUSR BEA ELINK TCP FOR CICS BEAM H2 UPDATE HANDLER CONFIGURATION SECURITY: Y MULTIPLEX COUNT: 99 MIN TIME (MILLISECS): 20 MAX TIME (MILLISECS): 30 DELTA TIME (MILLISECS): 5 IDLE TIME (SECONDS): 0 ENTER: PROCESS, PF3: MENU UPDATE COMPLETED

 

Fields

Field Name	Description
SECURITY	The status of gateway security. Y denotes that security is activated and N denotes that security is not activated. If this field is set to N, the ACCOUNT and PASSWORD fields are not verified prior to establishing a connection.
MULTIPLEX CNT	The number of concurrent incoming service requests for each Handler.
MIN TIME	The minimum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: The recommended value for running with Interlink CPT is 400. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
MAX TIME	The maximum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: If you are running Interlink CPT, this value is rounded up to the nearest second. The recommended value for running with Interlink CPT is less than or equal to 3000. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
DELTA TIME	The time increase (in milliseconds) from MIN TIME to MAX TIME. Note: The recommended value for running with Interlink CPT is greater than 50. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
IDLE TIME	The amount of time in seconds a Handler is idle before it terminates.

 

Inquire Handler Configuration Screen (H3)

Use this screen to make an inquiry about the configuration record from the user file. The screen is displayed with the data from the requested record and all fields are protected.

BEAPUSR BEA ELINK TCP FOR CICS BEAM H3 INQUIRE HANDLER CONFIGURATION SECURITY: Y MULTIPLEX COUNT: 99 MIN TIME (MILLISECS): 20 MAX TIME (MILLISECS): 30 DELTA TIME (MILLISECS): 5 IDLE TIME (SECONDS): 0 ENTER: PROCESS, PF3: MENU

 

Fields

Field Name	Description
SECURITY	The status of gateway security. Y denotes that security is activated and N denotes that security is not activated. If this field is set to N, the ACCOUNT and PASSWORD fields are not verified prior to establishing a connection.
MULTIPLEX CNT	The number of concurrent incoming service requests for each Handler.
MIN TIME	The minimum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: The recommended value for running with Interlink CPT is 400. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
MAX TIME	The maximum length of time (in milliseconds) for a socket read to wait for data to be processed. Note: If you are running Interlink CPT, this value is rounded up to the nearest second. The recommended value for running with Interlink CPT is less than or equal to 3000. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
DELTA TIME	The time increase (in milliseconds) from MIN TIME to MAX TIME. Note: The recommended value for running with Interlink CPT is greater than 50. For information about recommended configuration values and system behavior, refer to the Configuring eLink TCP for CICS with Interlink CPT section.
IDLE TIME	The amount of time in seconds a program is idle before it terminates.

 

 

---

Dynamically Configuring eLink TCP for CICS

Dynamic configuration means that new configuration information affects currently running Handlers or Requesters without shutting them down. The new configuration information also affects Handlers and Requesters that are started after the information is entered. You can make the following changes to the eLink TCP for CICS gateway configuration dynamically:

• Modifying Outbound Services

• Modifying User Connection Accounts

• Modifying Connections

• Deleting Requester LMIDs

All other configuration tasks are not dynamic, including Inbound Service Information and Handler Configuration. To process configuration information in these cases, the corresponding Requesters and Handlers must be shut down.

Modifying Outbound Services

You can dynamically configure outbound services by inserting a new record into the service name file, modifying an existing record in the service name file, or deleting a record in the service name file. Use the appropriate maintenance screens to accomplish the necessary task, S1 to insert, S2 to update, or S4 to delete. For field definitions, refer to the The Outbound Service Information Screens section.

Modifying User Connection Accounts

You can dynamically configure User Connection Accounts and enable accounts to connect to Handlers by inserting a new account into the user account file, modifying an existing user account, or deleting a user account. Use the appropriate maintenance screens to accomplish the necessary task, U1 to insert, U2 to update, or U4 to delete. For field definitions, refer to the The User Connection ACCOUNT Screens section.

Note: Changes to the User Connection Accounts do not affect Handlers that are currently connected, but only Handlers that connect after the change is made.

Modifying Connections

You can dynamically configure the status of a connection. Using the Update Connection screen (C2), you can enable, disable, or abort the connection for a given LMID. Dynamically configuring the status of a connection has an immediate effect on the corresponding Requesters. For field definitions, refer to the The Connection Screens section.

Note: Because the data in the Update Connection screen is transient, setting the LMID status to disable does not persist after the CICS region is shut down and then restarted. The Requester file, however, is persistent.

Deleting Requester LMIDs

Each instance of the Requester is given a logical machine name (LMID). You can give a Requester any unique LMID that is meaningful to you. Every service name is associated with one or more LMIDs. This method allows the Requester to identify which remote machine is responsible for a particular service. You can dynamically delete an LMID using the Update Requester screen (R2). This dynamic change only affect Pre-requesters immediately.

Note: Requesters that are currently running do not read the information in the requester file and are not affected by this dynamic change.

 

---

Configuring eLink TCP for CICS with Interlink CPT

The BEA eLink for Mainframe TCP product may exhibit the following behavior when using the CPT API in CICS applications. If messages are arriving on the network, request processing is not impacted by timeouts. If no messages are arriving on the network, a timeout is set using the MIN TIME, MAX TIME, and DELTA TIME configuration parameters. The Interlink CPT product supports timeouts in one second intervals only, so all timeouts are rounded to the nearest second. This behavior has the following effects:

• If the timeout is less than half a second (500 milliseconds), the affected task will hard-loop looking for network activity or responses to prior inbound requests. During this time, other CICS tasks in the region will not run.

• If the timeout is greater than half a second and the network is idle, non-network activity (such as responses to prior inbound requests or operator commands) will not be recognized until the timeout expires or a new request arrives on the network.

Recommended Configuration

A recommended configuration of the eLink TCP for CICS system using the Requester and Handler Configuration screens follows. Results may vary depending on your environment.

• Set MIN TIME to 400 milliseconds

• Set MAX TIME to a value less than or equal to 3000 milliseconds

• Set DELTA TIME to a value greater than 50

 

---

Administering the Gateways

BEA Tuxedo has a set of tmadmin and dmadmin commands for the administration of the eLink TCP gateways. For detailed information about these commands, refer to the BEA Tuxedo documentation.