|
2.
|
Edit the UBBCONFIG file and load to create the binary.
|
|
3.
|
Edit the DMCONFIG file and load to create the binary.
|
The DMTYPE file is an ASCII file. Use any text editor to edit this file.
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.
|
*GROUPS
SNAGRP LMID=mysys
GRPNO=4
LOCGRP LMID=mysys
BRPNO=5
*SERVERS
DEFAULT: CLOPT = “-A”
DMADM SRVGRP=LOCGRP
SRVID=14
GWADM SRVGRP=SNAGRP
SRVID=14
REPLYQ=Y
RESTART=N
GRACE=0
SNACRM SRVGRP=SNAGRP
SRVID=15
CLOPT=“-A--//dalhps2:4452 SNAGRP”
RESTART=Y
RCMD=rstsnagrp
GRACE=120
MAXGEN=2
GWSNAX SRVRGRP=SNAGRP
SRVID=16
RQADDR=”SNADOM”
REPLYQ=N
RESTART=Y
RCMD=rstsnagrp
GRACE=120
MAXGEN=2The configuration specified in the DMCONFIG file controls much of the operation of the Oracle Tuxedo Mainframe Adapter for SNA Gateway (GWSNAX). A sample of this file is provided in the installation directory of your Oracle Tuxedo Mainframe Adapter for SNA product software.
|
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.
|
LDOM required parameters {optional parameters}
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:
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:
|
c.
|
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 eLink Adapter for Mainframe. Any changes to the * DM_SNACRM, * DM_SNASTACKS, or * DM_SNALINKS sections require a cold start for the Oracle Tuxedo Mainframe Adapter for SNA domain. If you do not cold start the Oracle Tuxedo Mainframe Adapter for SNA 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:
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 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 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:
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.
<Device Name> is the logical name used to access the network. For example:
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:
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 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 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 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 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.
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:
In this entry, <Link Name> is the identifier 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.
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 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
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 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 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 Oracle Tuxedo Mainframe Adapter for SNA.
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.
The *DM_LOCAL_SERVICES section provides information on the services exported by each local domain. Entries have the general form:
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, “
Administrative Command Reference Pages.”
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:
AAAA is a 1-4 character alternate mirror TRANSID.
BBBBBBBB is a 1-8 character CICS/ESA program name.
The *DM_REMOTE_SERVICES section provides information on services “imported” and available on remote domains. Entries have the general form:
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, “
Administrative Command Reference Pages.”
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.
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:
AAAA is a 1-4 character alternate mirror TRANSID.
BBBBBBBB is a 1-8 character CICS/ESA program name.
If the environment variable CALLID_FIELDS_CFG and call ID configuration file are correctly set for Oracle Tuxedo Mainframe Adapter for SNA Gateway, and Oracle Tuxedo System and Applications Monitor Plus (TSAM Plus) call path is enabled on SNA Gateway, the call ID is collected to the ECID field in the TSAM Plus call path. For more information, see
"Call Path" in
Oracle Tuxedo System and Applications Monitor Plus Console Users Guide.
|
•
|
This feature only support STRING and CARRAY field types in VIEW. If the field type is CARRAY, TMA represents it in hexadecimal characters in upper case and doubles its length (two characters represent one single byte).
|
Set CALLID_FIELDS_CFG to enable this support. If it is not set, this support will not be enabled. It also specifies the configuration file location and field names. Both absolute file path and relative file path are supported.
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.
