In this section: |
Configuring the adapter consists of specifying connection and authentication information for each of the connections you want to establish. In addition, for if you are using the TCP 62 or LU 6.2 communication protocols, you must configure a Listener node.
How to: Reference: |
This procedure is required if you are using TCP 62 or LU 6.2 as your communications protocol.
Note that you can complete this step either before or after you declare connection attributes.
Note: This step is required if you are using TCP 62 or LU 6.2 on Windows or UNIX.
For descriptions of these parameters, see Communications Parameters for CICS Transactions for TCP 62 or LU 6.2.
Tip: You can also obtain details about each entry by clicking the ? icon to the left of any parameter field on the communications configuration pane to access the Web Console Help.
This chart describes the parameters required to configure communications. To complete the configuration, click Save and Restart Listener.
Keyword |
Description |
---|---|
NODE |
8-character string Defines a logical name of a node block, which must be unique in the file. The logical name can be a maximum of eight characters, must begin with a letter, and can include any characters, except semicolon and equal sign. A node block contains keyword-value pairs, which are enclosed in a BEGIN-END statement. |
PARTNER_LU_NAME |
string Defines the APPLID of the target CICS region. |
LOCAL_LU_NAME |
string Defines the LU name to be used. This value is taken from an LU entry in the major node. The value is also specified in the CICS connection/sessions definition. |
MODE_NAME |
string Defines the DLOGMODE parameter value. |
CODEPAGE |
string Defines the code page that the CICS region is using. |
COMMUNICATION |
Select one of the following options:
Important: Your selection in this field determines what additional configuration information that is required. |
Additional required information for TCP/IP (This option displays additional parameters required for TCP 62.) | |
VTAM_NETWORK_ID |
string Defines the VTAM network ID. This value is taken from the AnyNET listener major node under parameter NETID. |
CONNECT_LIMIT |
number of seconds Defines the maximum time, in seconds, that the client waits for a connection response from the AnyNET environment. Provide a value greater than 0. (Do not enter a value of -1.) |
PROXY |
string Defines the name of the supplied proxy (user-written) program, which converts the Full Function Server calling syntax to the syntax that is valid for the CICS program to be executed. This parameter is optional, and should be left blank for normal operations. Use it only at the direction of your local support personnel. |
MIRROR |
string Defines the IBM-supplied mirror transaction CPMI that the Adapter for CICS Transactions calls by default. If this transaction cannot be used, you can create another transaction name to point to the IBM-supplied mirror program DFHMIRS. Enter the alternate name in the MIRROR field. |
NATPROG |
string Identifies the NATURAL program to be executed. Note: This option does not apply to the Adapter for CICS Transactions. |
HOST |
string Defines the host that a client is connecting to or an IP address that a listener is listening on. |
SERVER_ID |
string Defines the machine name where the server is configured with the CICS AGENT NODE (Listener). |
ANYNET_PORT |
positive integer number Defines the port number that the AnyNET product is using. The default AnyNET port is 397, but any number can be used. For UNIX installations, a port number above 1000 is recommended. |
Additional required information for LU6.2 | |
PROXY |
string Defines the name of the supplied proxy (user-written) program, which converts the Full Function Server calling syntax to the syntax that is valid for the CICS program to be executed. This parameter is optional, and should be left blank for normal operations. Use it only at the direction of your local support personnel. |
SIDE_INFO |
string SIDE_INFO is a table with definitions for all partners to the currently active CICS system. CICS implements the side information table by means of the PARTNER resource. Partner resources are defined by the CEDA DEFINE command. To become known to an active CICS system, a defined partner resource must be installed using the CEDA INSTALL command. |
HOST |
string Defines the DNS name of the host LPAR of the target CICS region. You can also code the four part IP address. |
NODE = CICSTLU6 BEGIN PROTOCOL = CICS CLASS = CICSCLIENT TARGET = CICS PARTNER_LU_NAME = EDBGM010 LOCAL_LU_NAME = T29DPB41 MODE_NAME = PARALLEL HOST = IBIMVS CODEPAGE = 037 COMMUNICATION = LU62 END
NODE = LST_CICS BEGIN PROTOCOL = CICS PORT = 8139 CLASS = AGENT END NODE = SPGCSRV BEGIN PROTOCOL = CICS PORT = 8139 CLASS = AGENT TARGET = INTERNAL HOST = IBIMVS CODEPAGE = 037 ANYNET_PORT = 397 END NODE = CICSCLNT
BEGIN PROTOCOL = CICS CLASS = CLIENT TARGET = CICS INTEGER = HOBF FLOAT = IBM PARTNER_LU_NAME = EDBGM010 LOCAL_LU_NAME = T29DPB04 MODE_NAME = PARALLEL HOST = SPGCSRV CODEPAGE = 037 COMMUNICATION = TCP VTAM_NETWORK_ID = USIBINET CONNECT_LIMIT = 60 MIRROR = CPMI ATTACH_SECURITY = VERIFY SECURITY = C2B591CC2A92650028E8A570F3BE36F3 END
In order to connect to CICS Transactions, the adapter requires connection and authentication information. You supply this information using the SET CONNECTION_ATTRIBUTES command. You can:
You can declare connections to more than one data source by including multiple SET CONNECTION_ATTRIBUTES commands. The actual connection to CICS Transactions takes place when the first query that references that connection is issued. If you issue multiple SET CONNECTION_ATTRIBUTES commands:
For detailed instructions about declaring connection attributes for your operating system, see Configuring the Adapter on Microsoft Windows and UNIX or Configuring the Adapter on z/OS.
How to:
Reference: |
Configuring the adapter consists of specifying connection and authentication information for each of the connections you want to establish. In addition, if you are using the TCP 62 or LU 6.2 communications protocol, you must configure a Listener node as described in How to Configure a Listener. For TCP/IP, you only need to declare connection attributes.
You can configure the adapter from either the Web Console or the Data Management Console.
or
From the Data Management Console, expand the Adapters folder.
The Adapters folder opens.
The Add Adapter to Configuration pane opens.
For TCP/IP, the configuration parameters for the adapter are displayed.
For TCP 62 and LU 6.2, you are prompted to either Configure CICST listener or to click Next to display the configuration parameters for the adapter. You can complete these tasks in either order, but both must be done to use the adapter.
Once you have configured the Listener, return to the Add CICS Transaction to Configuration pane, where the Listener node is now available for selection.
The CICS Transaction adapter is under the Procedures group folder.
The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.
Select one of the following: TCP/IP, TCP 62, LU 6.2. Subsequent options vary slightly depending on this selection.
Note: For TCP 62 and LU 6.2, you must configure a Listener either before or after you declare connection attributes.
This selection is reflected in the Communication field on the second configuration pane.
Is a logical name used to identify a specific set of connection attributes.
For TCP 62 or LU 6.2, a drop-down list of nodes is displayed if the Listener has already been configured. Select a node from the list.
For TCP/IP, enter the name of the host machine.
For TCP 62 or LU 6.2, enter the application ID of the CICS Transactions region.
Enter the name of the mirror transaction.
For TCP/IP, enter the port number.
There are two methods by which a user can be authenticated when connecting to the Adapter for CICS Transactions:
Is the user name by which you are known to the adapter. This field is only displayed when the security mode of the server is non-trusted.
Is the password associated with the user name. This field is only displayed when the security mode of the server is non-trusted.
Select a profile from the drop-down list to indicate the level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default.
If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down list and enter a name in the Profile Name input box. (The extension is added automatically.)
Explicit. The user ID and password are explicitly stated in SET CONNECTION_ATTRIBUTES commands. You can include these commands in the server global profile, edasprof.prf, for all users.
ENGINE CICSTRAN SET CONNECTION_ATTRIBUTES [connection] [node_name]/userid,password: "parameters_list"
Password passthru. The user ID and password are explicitly specified for each connection and passed to CICS Transactions, at connection time, for authentication.
ENGINE CICSTRAN SET CONNECTION_ATTRIBUTES [connection] [node_name] /: "parameters_list"
where:
Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.
Is a logical name used to identify this particular set of connection attributes. In the Access File, it becomes the CONNECTION=connection_name value. See Access File Attributes.
Is a name of the NODE definition in the ODIN configuration file.
Is the primary authorization ID by which you are known to the Adapter for CICS Transactions.
Is the password associated with the primary authorization ID.
The following parameters are supported (some required; some optional):
application_ID is the application ID of the CICS region. This parameter is optional.
mirror_name is the name of the mirror transaction. This value overwrites the MIRROR value provided when the Listener is configured. This parameter is optional.
communication is the communication protocol being used. The options are: TCP/IP, TCP 6.2 (AnyNET), LU 6.2.
How to: Reference: |
Configuring the adapter consists of specifying connection and authentication information for each of the connections you want to establish.
You can configure the adapter from either the Web Console or the Data Management Console.
or
From the Data Management Console, expand the Adapters folder.
The Adapters folder opens.
The Add Adapter to Configuration pane opens.
The configuration parameters for the adapter are displayed.
The CICS Transaction adapter in under the Procedures group folder.
The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.
Select one of the following: TCP/IP or EXCI. Subsequent options vary slightly depending on this selection.
This selection is reflected in the Communication field on the second configuration pane.
Is a logical name used to identify a specific set of connection attributes.
For TCP/IP, enter the name of the host machine.
For EXCI, enter the application ID of the CICS region.
For TCP/IP, enter the port number.
Is the name of the mirror transaction. The default value is EXCI.
This value overwrites the value provided in the Listener mode.
For EXCI, Trusted security is supported under the following conditions: the server must be running with security OPSYS and IRC (Inter Region Communications) must be active in the CICS region. The adapter then connects to the CICS region using the credentials of the operating system user impersonated by the server data access agent.
For TCP/IP, there are two methods by which a user can be authenticated when connecting to the Adapter for CICS Transactions:
Is the user name by which you are known to the adapter. This field is only displayed when the security mode of the server is non-trusted.
Is the password associated with the user name. This field is only displayed when the security mode of the server is non-trusted.
The level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default.
If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down list and enter a name in the Profile Name input box. (The extension is added automatically.)
Explicit. The user ID and password are explicitly stated in SET CONNECTION_ATTRIBUTES commands. You can include these commands in the server global profile, edasprof.prf, for all users.
ENGINE CICSTRAN SET CONNECTION_ATTRIBUTES [connection] [node_name]/userid,password: "parameters_list"
Password passthru. The user ID and password are explicitly specified for each connection and passed to CICS Transactions, at connection time, for authentication.
ENGINE CICSTRAN SET CONNECTION_ATTRIBUTES [connection] [node_name] /: "parameters_list"
Trusted. The adapter connects to an operating system login using the credentials of the operating system user impersonated by the server data access agent.
ENGINE CICSTRAN SET CONNECTION_ATTRIBUTES [connection] [node_name] /: "parameters_list"
where:
Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.
Is a logical name used to identify this particular set of connection attributes. In the Access File, it becomes the CONNECTION=connection_name value. See Access File Attributes.
Is a name of the NODE definition in the ODIN configuration file.
Is the primary authorization ID by which you are known to the Adapter for CICS Transactions.
Is the password associated with the primary authorization ID.
The following parameters are supported (some required; some optional):
application_ID is the application ID of the CICS region. This parameter is optional.
mirror_name is the name of the mirror transaction. This value overwrites the MIRROR value provided when the Listener is configured. This parameter is optional.
communication is the communication protocol being used. The options are: TCP/IP and EXCI.
iWay Software |