Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Search   |   PDF Files   |   Contact   |
eLink Adapter for Mainframe Doc Home   |   eLink Adapter for Mainframe User Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

To enable your eLink Adapter for Mainframe (eAM), proper configuration based on your system's architecture is required. This section covers the following topics:

• Preparing for Configuration

• Configuring the eAM Gateway with the CRM

  Note: All references to ATMI files, functions, and documentation apply to Tuxedo, eLink Platform, and WebLogic Enterprise files, functions, and documentation.

Before you can properly configure your eAM gateway with the CRM, you must complete the following prerequisites:

• Determine Your System Architecture

• Configure the Local Host

• Configure the Remote Host

Determine Your System Architecture

To determine your system's architecture, you must determine the location of the eAM components in that architecture.

The following basic components of the eAM system are factors in configuring your system:

• eAM gateway (GWSNAX)

  The eAM gateway is the transactional SNA gateway. It is implemented as an ATMI domain gateway and uses the ATMI environments. The gateway communicates over a Transmission Control Protocol/Internet Protocol (TCP/IP) connection.

• CRM

  The Communications Resource Manager (CRM) communicates with the SNA network, normally using an SNA stack. It communicates over the gateway with eAM clients over a Transmission Control Protocol/Internet Protocol (TCP/IP) connection.

• SNA stack
  The stack is vendor-supplied software that provides connectivity to an SNA network.

System Architecture

Your system architecture will reflect one of the following basic eAM configurations:

• Local Configuration

• Distributed Configuration-CRM on OS/390 Host

• Distributed Configuration-CRM on UNIX/NT Platform

Local Configuration

Local configuration combines the ATMI platform, the eAM gateway, CRM, and SNA stack (PU2.1 server) on the same UNIX or Windows NT platform, as shown in Figure 2-1. It features the widely used TCP/IP connectivity between the eAM gateway and CRM, giving a high-performance communications interface. On the mainframe side, the CRM uses a stack to communicate over a System Network Architecture (SNA) interface with the host system. This configuration allows you to:

• Connect to an existing SNA network.

• Consolidate the ATMI platform and eAM systems on the same platform.

• Avoid having to deploy any subsystems to the host.

  Note: A one-to-one relationship exists between the eAM gateway and CRM. The eAM gateway cannot be configured to handle multiple CRM processes.

  Figure 2-1 Local eAM Configuration on UNIX/NT Platform

  

Distributed Configuration-CRM on OS/390 Host

This distributed configuration deploys the CRM to the OS/390 host system as shown in Figure 2-2. It employs TCP/IP connectivity with the host, eliminating the need for a local SNA stack. This configuration provides a faster network interface and is less complex than the local configuration.

Distributed Configuration-CRM on UNIX/NT Platform

This distributed configuration deploys the CRM and stack to a UNIX or Windows NT platform, as shown in Figure 2-3. It employs the TCP/IP connectivity between the eAM gateway and CRM, as well as the SNA connectivity to the host. This configuration allows you to use multiple stacks from different stack vendors. Also, on the ATMI platform side, you have a greater variety of UNIX/NT-based platform manufacturers to choose from.

Configure the Local Host

Ensure that the local host is prepared to conduct operations with the remote host by completing the following task:

• Configure the Local LU for the appropriate stack.

Refer to the BEA CRM Administration Guide for more information about this task.

Ensure that the remote host is prepared to conduct operations with the ATMI local domain by completing the following tasks:

1. Configure the Remote LU.

2. Complete cross-platform definitions, if necessary.

3. Activate the connection between the remote host and the local host.

Refer to the BEA CRM Administration Guide for more information about these tasks.

The following list summarizes the tasks that must be completed to configure the eAM gateway (GWSNAX):

1. Edit the DMTYPE file.

2. Edit the UBBCONFIG file and load to create the binary.

3. Edit the DMCONFIG file and load to create the binary.

4. Start the CRM.

5. Start the ATMI servers.

The DMTYPE file is an ASCII file. Use any text editor to edit this file.

1. Insert the following line in the DMTYPE file located in the $TUXDIR/udataobj directory:

• For UNIX:

  SNAX::::

• For Windows NT:

  SNAX;;;;

1. Ensure that the $TUXDIR/udataobj/DMTYPE file exists prior to editing the DMCONFIG file. See dmloadcf in Appendix A, "Reference Pages"for more information.

The UBBCONFIG file is an ASCII file that can be edited with any text editor. To edit the UBBCONFIG file, complete the following tasks:

1. Create a UBBCONFIG file for each application. Refer to the Configuration section in the appropriate ATMI platform product documentation for more specific information about the UBBCONFIG file.

2. Establish a new gateway configuration or modify an existing one by defining the domain and gateway administrative servers to the ATMI system in the UBBCONFIG file.

3. If the CRM is to run as an ATMI server, add a CRM entry to the *SERVERS section of the UBBCONFIG file. For a description, refer to the BEA CRM Administration Guide.

   Note: If the CRM is started as an ATMI process, it must precede the GWSNAX entry in the UBBCONFIG file.

4. Establish the eAM gateway by adding an entry to the *SERVERS section of the UBBCONFIG file. For a description, refer to the GWSNAX command in Appendix A, "Reference Pages." The following gateway features may be enabled in the UBBCONFIG file:

   • Data transformation

   • Bypassing user ID mapping

   • Encryption

   • Authentication

5. Refer to the appropriate ATMI platform documentation for instruction for using tmloadcf to load the UBBCONFIG file.

   Figure 2-4 Sample UBBCONFIG File Entries Specifying CRM as an ATMI Server

   

The configuration specified in the DMCONFIG file controls much of the operation of the eAM gateway (GWSNAX). A sample of this file is provided in the installation directory of your eAM product software.

Note: Because eAM may be installed on a variety of platforms, the procedures in this section make only general references to command entries. Many steps show UNIX command examples. Be sure to use the proper syntax for your platform when making command-line entries.

1. Verify that the eAM product software is installed and accessible to your text editor.

2. Verify that you have file permission to access the install directory and modify the sample DMCONFIG file.

3. Set each of the parameters of the DMCONFIG file as described in the following sections and load the DMCONFIG file. Refer to the appropriate ATMI documentation for instruction for using dmloadcf to load the DMCONFIG file.

   1. Update the *DM_LOCAL_DOMAINS Section.

      This section identifies local domains and their associated gateway groups. The section must have an entry for each gateway group (Local Domain). Entries have the form:

      LDOM required parameters {optional parameters}

      In this entry, LDOM is an identifier value used to name each local domain. For a full description of the optional and required parameters, see DMCONFIG in Appendix A, "Reference Pages."

      For each LDOM entry, the value of the TYPE parameter distinguishes this gateway from other gateway types. Currently, SNAX replaces the value SNADOM used in previous releases. The parameter entry takes the form:

      TYPE={SNAX | OSITP | TDOMAIN}

      Select the value TYPE=SNAX for the LDOM entry.

   2. Update the *DM_REMOTE_DOMAINS Section.

      This section identifies the known set of remote domains and their characteristics. Entries have the form:

      LDOM required parameters

      In this entry, RDOM is an identifier value used to identify each remote domain known to this configuration. For a full description of the required parameters, see DMCONFIG in Appendix A, "Reference Pages."

      For each RDOM entry, the value of the TYPE parameter indicates that the remote domain communicates using the SNA protocol. The parameter entry takes the form:

      TYPE={SNAX | OSITP | TDOMAIN}

      Select the value TYPE=SNAX for the RDOM entry.

   3. Add the *DM_SNACRM Section.

      Note: *DM_SNACRM, *DM_SNASTACKS, and the *DM_SNALINKS sections have replaced the *DM_SNADOM section used in previous releases of eAM.

      Note: Any changes to the *DM_SNACRM, *DM_SNASTACKS, or *DM_SNALINKS sections require a cold start for the eAM domain. If you do not cold start the eAM domain, an error will occur on domain start-up indicating cold start required for the configuration change.

      The *DM_SNACRM section provides three keywords used to identify the CRM that provides ATMI transaction semantics in a given domain and its partners. Entries have the general form:

      <CRMName> parameters

      In this entry, <CRMName> is the locally known name of this SNACRM definition to be used when referencing this SNACRM in subsequent sections. This name is an ASCII string 1-30 characters in length. The parameters are the keyword/value pairs that make up the definition. All keywords are required for a valid SNACRM definition. Keywords can be in any order.

   • LDOM=<LocalDomainName> (Required)

     LDOM associates this SNACRM with a defined local domain. <LocalDomainName> is the reference to an entry in the *DM_LOCAL_DOMAINS section. This name is an ASCII string 1 to 30 characters in length. This parameter is required. This parameter has no default.

   • SNACRMADDR=<HexSocketAddress> (Required)

     SNACRMADDR provides the socket address the domain gateway uses to communicate with the SNACRM. This address represents the machine and port where the CRM runs. In a local configuration, this address is the local platform. In a distributed configuration, this address is a remote platform. This address must be used on the SNACRM command line. This parameter is required and has no default.

     <HexSocketAddress> is a TCP/IP address using //hostname:port_addr or the sockaddr_in format of family, port, address:

     <0xFFFFPPPPAAAAAAAA>

     In this entry, arguments and options are defined in the following way:

     FFFF is the hex value of the protocol family, always 0x0002 for the INET family.

     PPPP is the hex value of an unused TCP/IP port.

     AAAAAAAA is the hex value of the IP address for the machine running the SNACRM.

     Therefore, if the CRM was running on a machine named myhost with an IP address of 206.189.43.13, and you wanted to use port 6000 for the CRM, then SNACRMADDR would be:

     //myhost:6000 or 0x00021770CEBD2B0D

   • NWDEVICE=<Device Name> (Required)

     <Device Name> is the logical name used to access the network. For example:

     /dev/tcp

   1. Add the *DM_SNASTACKS Section.

      The DM_SNASTACKS section provides five keywords that identify the third-party SNA stack that should be used for connections established between a given domain and its partners. Entries have the general form:

      <StackReference> parameters

      In this entry, <StackReference> is the locally known name of this stack definition and it is used when referencing this stack in subsequent sections. This name is an ASCII string 1-30 characters in length. The parameters are the keyword/value pairs that make up the definition. Keywords can be in any order. All keywords are required for a valid stack definition.

   • LOCALLU=<LocalLUAlias> (Required)

     LOCALLU provides a reference to an LU alias defined in the third-party SNA stack. <LocalLUAlias> is the name used to identify the local LU definition as specified by the third-party SNA stack configuration. This name represents the end node for an LU6.2 connection. The value for this parameter is an ASCII string, 1-8 characters in length. This parameter is required. This parameter has no default. The third party SNA stack requires a corresponding definition for a local LU.

   • LTPNAME=<LocalTransactionProgramName> (Required)

     LTPNAME identifies the inbound transaction programs that are serviced by any SNACRM using this stack definition. <LocalTransactionProgramName> is the name used to identify inbound transaction programs for which an attach will be accepted. The only useful value is an asterisk that indicates all inbound attaches will be accepted. This parameter is required. This parameter has no default. Partial TP names are not supported. The third-party SNA stack requires a corresponding definition for inbound TP names.

   • SNACRM=<CRMName> (Required)

     SNACRM provides a name to which the associated SNACRM definition is referenced. <CRMName> is the name used to associate the *DM_SNACRM definition with this *DM_SNASTACKS entry. The value for this parameter is an ASCII string, 1-30 characters in length. This parameter is required. This parameter has no default.

   • STACKPARMS=<parameters required for third-party sna stack> (Required)

     STACKPARMS provides a method for the domain gateway to pass any required parameters to the third party SNA stack. The <parameters required for third-party sna stack> is an ASCII string, 1-128 characters in length. Currently, the only value used is the TCP/IP hostname for the machine running the third-party SNA stack. This parameter is required. This parameter has no default.

   • STACKTYPE={hp60 | ibm60 | spx62 | sun91 | ms40 | vtm28}

     This option is used to indicate which vender SNA stack is being used. It is also used to determine the names of specific eAM system libraries. Because of this, it is essential that the value of this option be coded correctly. These values are mapped to the equivalent eAM system library.

   1. Add the *DM_SNALINKS Section.

      The *DM_SNALINKS section provides 11 key words that define the SNA Link information required by domains of type SNA. Entries have the general form:

      <Link Name> parameters

      In this entry, <Link Name> is the indentifier value used to identify the connection between a local domain (LDOM) and a remote domain (RDOM). This name is an ASCII string 1-30 characters in length. The parameters are the keyword/value pairs that make up the definition. Keywords can be in any order.

   • STACKREF=<Stack Reference> (Required)

     This required parameter defines the stack that will be used for establishment of this link. The STACKREF string is the tag that was used in the corresponding definition established in the *DM_SNASTACKS section.

   • RDOM=<name>

     Each link defines a connection between an ATMI system application domain and a remote system connected with an SNA network. The remote system is, in ATMI terms, a remote domain. The RDOM option associates the link with a remote domain. This remote domain must have been configured with the TYPE=SNAX option. The RDOM name should match an RDOM value previously identified in the *DM_REMOTE_DOMAINS section.

   • LSYSID=<name>

     LSYSID is the four-character identifier for this link. This should match the connection ID in the CICS/ESA resource definition used by a partner CICS/ESA to communicate to the SNACRM across this link. If you are using the macro definition, it is a four-character name on the SYSIDNT option of the DFHTCT macro.

   • RSYSID=<name>

     RSYSID is the four-character remote sysid of the partner. Typically it is the sysid of a CICS/ESA region, but could also be the subsystem ID of an IMS control region. This parameter must match the actual sysid of the remote partner. This name is the SYSIDNT of the DFHSIT or the value in the CICS/ESA start-up overrides

   • RLUNAME=<name> (Required)

     The RLUNAME value represents an alias known to the third-party SNA stack that resolves to a VTAM netname for the remote application. This remote application is most likely the VTAM applid for a CICS/ESA region, however it could also be an APPC/MVS LU defined for use with IMS. The value must be unique within the SNA network. The value name should be 1-8 characters. This parameter is required. This parameter has no default. The third-party stack configuration requires a matching definition.

   • MODENAME=<name> (Required)

     MODENAME is VTAM mode entry defined to the third-party SNA stack. For a CICS/ESA link, this entry must be compatible with the session definition or profile entry for the corresponding connection. For an IMS connection, this entry must be compatible with the DLOGMOD entry on the LU definition used to access the IMS scheduler. The value name should be 1-8 ASCII characters. This parameter is required. This parameter must match the third-party SNA stack configuration and must be compatible with the corresponding entries defined to VTAM and/or CICS/ESA.

   • SECURITY={LOCAL | IDENTIFY | VERIFY | PERSISTENT | MIXIDPE}

     SECURITY specifies the security setting in CICS/ESA connection resource definition. It identifies the level of security enforced under CICS/ESA by the external security manager. Legal values are LOCAL, IDENTIFY, VERIFY, PERSISTENT or MIXIDPE. The default setting is LOCAL. PERSISTENT and MIXIDPE identify the setting in the remote connection definition, but are identical to the VERIFY option in this release of eAM.

   • MAXSESS=<number>

     This number represents the maximum number of sessions that can be concurrently acquired on this link. It must be greater than or equal to four, and less than or equal to the maximum number of sessions that can be configured by the SNA stack. The actual number of concurrent sessions is determined by both system configurations to be the lowest maximum number of sessions allowed by either system.

   • MINWIN=<number>

     This value is the minimum number of contention winners. Typically, this value is half the MAXSESS value. This number added to all CICS/ESA session definition winner numbers for the connection should be equal to the MAXSESS value.

   • STARTTYPE={AUTO|COLD}

     This option sets the recovery mode for transactional links. When set to AUTO, the system restarts using configuration and link data recovered from the transaction log. When set to COLD, the system uses configuration data taken from the current DMCONFIG file and loses any in-flight link data. Changing DMCONFIG file parameters and performing an AUTO start results in a message warning that changed parameters are ignored until the next cold start.

   • MAXSYNCLVL={0 | 1 | 2}

     This value represents the maximum sync-level conversation that can be supported on this link. The default is sync-level 2. If the installation is not licensed for sync-level 2, this parameter must be set to 0 or 1 for the link to be established. Transaction support is only available at sync-level 2.

     Sync-level 0

     A value of zero (0) means this link is non-transactional. No synchronization is maintained. This value can be used for sending and receiving messages from IMS via the APPC/MVS transparency interface.

     Sync-level 1

     Allows sync-level 0 capabilities as well as support for SYNCONRETURN Distributed Program Link (DPL) with CICS/ESA systems (outbound ATMI tpcall() requests with TPNOTRAN).

     Sync-level 2

     Supports all sync-level 0 and sync-level 1 features for systems able to exchange logs and compare states. In addition, full syncpoint synchronization at sync-level 2 is supported.

     Caution: If you set MAXSYNCLVL=2 or make no entry for this parameter (that is, accept the default) without having installed the eAM software licensed for that level, the system configuration automatically reverts to sync-level 1 and an error message is sent to the error log. To clear that error message, you must either reset the MAXSYNCLVL parameter to an appropriate value or purchase and install the correct software.

   1. Update the *DM_LOCAL_SERVICES Section.

      The *DM_LOCAL_SERVICES section provides information on the services exported by each local domain. Entries have the general form:

      <Local Service Name> parameters

      In this entry, <Local Service Name> is the local name of the exported service. This name is an ASCII string 1-15 characters in length. The parameters are the keyword/value pairs that make up the definition. Keywords can be in any order. For a full description of parameters, see DMCONFIG in Appendix A, "Reference Pages."

   • RNAME=<name> (Required)

     The RNAME option is the local-service name imported from a remote CICS/ESA region. This name is used by the CRM to select a local service.

     When the RNAME specifies an alternate mirror transaction identifier for explicit attachment for inbound DPL requests, it must be a combination of the alternate mirror TRANSID and a CICS/ESA program name in the following format:

     RNAME=AAAA:BBBBBBBB

     In this statement, the arguments and options are defined in the following way:

     AAAA is a 1-4 character alternate mirror TRANSID.

     BBBBBBBB is a 1-8 character CICS/ESA program name.

     The colon is required to indicate the TRANSID/program name combination. The TRANSID must be composed of acceptable CICS/ESA characters:

     A-Za-z0-9$@#./-_%&Q¢?!|"=,;<>

     Refer to "Special Treatment of TRANS ID for DPL" in "Application to Application Programming Considerations."

   1. Update *DM_REMOTE_SERVICES Section.

      The *DM_REMOTE_SERVICES section provides information on services "imported" and available on remote domains. Entries have the general form:

      <Remote Service Name> parameters

      In this entry, <Remote Service Name> is the name used by the local application for a particular remote service. This name is an ASCII string 1-15 characters in length. The parameters are the keyword/value pairs that make up the definition. Keywords can be in any order. For a full description of parameters, see DMCONFIG in Appendix A, "Reference Pages."

   • FUNCTION={APPC | DPL}

     The FUNCTION option has been added to allow outbound ATMI service requests to map to APPC transaction programs or CICS/ESA DPL programs. The default value is APPC.

   • RNAME=<name>

     The RNAME option is the name of the host TP_NAME. For non-CICS/ESA systems, this name can be up to 64 characters in length. For CICS/ESA systems, this name is the transaction ID for FUNCTION=APPC and the program name for FUNCTION=DPL requests. CICS/ESA trans-id names cannot exceed four characters and CICS/ESA program names cannot exceed eight characters. The RNAME option must observe these requirements.

     When the RNAME specifies an alternate mirror transaction identifier for explicit attachment to outbound DPL requests, it must be a combination of the alternate mirror TRANSID and an advertised remote CICS/ESA program name in the following format:

     RNAME=AAAA:BBBBBBBB

     In this statement, the arguments and options are defined in the following way:

     AAAA is a 1-4 character alternate mirror TRANSID.

     BBBBBBBB is a 1-8 character CICS/ESA program name.

     The colon is required to indicate the TRANSID/program name combination. The TRANSID must be composed of acceptable CICS/ESA characters:

     A-Za-z0-9$@#./-_%&Q¢?!|"=,;<>

     Refer to "Special Treatment of TRANS ID for DPL" in "Application to Application Programming Considerations."

If the CRM is run in distributed mode or from the command line, it must be started independently of the ATMI processes. Start the CRM in one of the following ways:

• For MVS, use the JCL that was modified during the installation process.

• For all other distributed configurations, use the SNACRM command in the following format:

  SNACRM [parameters] <HexSocketAddress> <group name>

Refer to SNACRM in Appendix A, "Reference Pages" for more information about this command.

Perform a tmboot as described in the appropriate ATMI platform documentation to start the ATMI servers. If it is already running, perform a tmshutdown and tmboot.