3.2.1.3.1 Option A: Edit the DMCONFIG File
The 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.
Note:
Because Oracle Tuxedo Mainframe Adapter for SNA 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.- Verify that the Oracle Tuxedo Mainframe Adapter for SNA product software is installed and accessible to your text editor.
- Verify that you have file permission to access the install
directory and modify the sample
DMCONFIG
file. - Set each of the parameters of the
DMCONFIG
file as described in the following sections and load theDMCONFIG
file. Refer to the appropriate ATMI documentation for instruction for usingdmloadcf
to load theDMCONFIG
file.- Update the *
DM_LOCAL_DOMAINS
SectionThis 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, seeDMCONFIG
in Appendix A, Administration Mode Commands.For eachLDOM
entry, the value of theTYPE
parameter distinguishes this gateway from other gateway types. Currently,SNAX
replaces the valueSNADOM
used in previous releases. The parameter entry takes the form:TYPE={SNAX | OSITP | TDOMAIN}
Select the value
TYPE=SNAX
for theLDOM
entry.To support SNAX reconnects to CRM automatically (as CRM restarting), you can setCONNECTION_POLICY
toON_STARTUP
and specify aRETRY_INTERVAL
(the default value is 60 seconds). For example:CONNECTION_POLICY=ON_STARTUP RETRY_INTERVAL=60
- Update the *
DM_REMOTE_DOMAINS
SectionThis section identifies the known set of remote domains and their characteristics. Entries have the form:
RDOM
required parametersIn 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, seeDMCONFIG
in Appendix A, Administration Mode Commands .For each
RDOM
entry, the value of theTYPE
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 theRDOM
entry. - Add the *
DM_SNACRM
SectionNote:
*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:<CRMName>
parametersIn this entry,
<CRMName>
is the locally known name of thisSNACRM
definition to be used when referencing thisSNACRM
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 validSNACRM
definition. Keywords can be in any order.LDOM= <LocalDomainName>
(Required)LDOM
associates thisSNACRM
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 defaultSNACRMADDR= <HexSocketAddress>
(Required)SNACRMADDR
provides the socket address the domain gateway uses to communicate with theSNACRM
. 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 theSNACRM
command line. This parameter is required and has no default.<HexSocketAddress>
is a TCP/IP address using/hostname:port_addr
or thesockaddr_
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, always0x0002
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 theSNACRM.
Therefore, if the CRM was running on a machine namedmyhost
with an IP address of206.189.43.13
, and you wanted to use port 6000 for the CRM, thenSNACRMADDR
would be://myhost:6000
or0x00021770CEBD2B0DNWDEVICE= <DeviceName>
(Required)<Device Name>
is the logical name used to access the network. For example:/dev/tcp
- Add the
*DM_SNASTACKS
SectionThe
DM_SNASTACKS
section provides five keywords that identify the third-party SNA stack that must be used for connections established between a given domain and its partners. Entries have the general form:<StackReference>
parametersIn 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 anySNACRM
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 associatedSNACRM
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={VT210 | IBM60}
This option is used to indicate which vender SNA stack is being used. It is also used to determine the names of specific Oracle Tuxedo Mainframe Adapter for SNA system libraries. Because of this, it is essential that the value of this option be coded correctly. These values are mapped to the equivalent Oracle Tuxedo Mainframe Adapter for SNA system library.
- Add the *
DM_SNALINKS
SectionThe *
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>
parametersIn 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.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. TheRDOM
option associates the link with a remote domain. This remote domain must have been configured with theTYPE=SNAX
option. TheRDOM
name must match anRDOM
value previously identified in the *DM_REMOTE_DOMAINS
section.LSYSID= <name>
LSYSID
is the four-character identifier for this link. This must match the connection ID in the CICS/ESA resource definition used by a partner CICS/ESA to communicate to theSNACRM
across this link. If you are using the macro definition, it is a four-character name on theSYSIDNT
option of theDFHTCT
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 theSYSIDNT
of theDFHSIT
or the value in the CICS/ESA start-up overridesRLUNAME= <name>
(Required) TheRLUNAME
value represents an alias known to the third-party SNA stack that resolves to a VTAMnetname
for the remote application. This remote application is most likely the VTAMapplid
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 must 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 theDLOGMOD
entry on the LU definition used to access the IMS scheduler. The value name must 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.
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 areSECURITY={LOCAL | IDENTIFY | VERIFY | PERSISTENT | MIXIDPE}SECURITY
LOCAL
,IDENTIFY
,VERIFY
,PERSISTENT
orMIXIDPE
. The default setting isLOCAL
.PERSISTENT
andMIXIDPE
identify the setting in the remote connection definition, but are identical to theVERIFY
option in this release of Oracle Tuxedo Mainframe Adapter for SNA.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. The default value isMAXSESS=64
.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 must be equal to theMAXSESS
value. The default value isMINWIN=0
.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 toCOLD
, the system uses configuration data taken from the currentDMCONFIG
file and loses any in-flight link data. ChangingDMCONFIG
file parameters and performing anAUTO
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. 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 ATMItpcall()
requests withTPNOTRAN
).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.
- Update the *
DM_LOCAL_SERVICES
SectionThe *
DM_LOCAL_SERVICES
section provides information on the services exported by each local domain. Entries have the general form:<Local Service Name>
parametersIn 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, seeDMCONFIG
in Appendix A, Administration Mode Commands.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 mirrorTRANSID
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 theTRANSID
/program name combination. TheTRANSID
must be composed of acceptable CICS/ESA characters:
Refer to “Special Treatment of TRANS ID for DPL” in “Application to Application Programming Considerations.”A-Za-z0-9$@#./-_%&Q¢?!|”=,; <>
- Update *
DM_REMOTE_SERVICES
SectionThe *
DM_REMOTE_SERVICES
section provides information on services “imported” and available on remote domains. Entries have the general form:<Remote Service Name>
parametersIn 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, seeDMCONFIG
in Appendix A, Administration Mode Commands.
TheFUNCTION={APPC | DPL}
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 isAPPC.RNAME= <name>
TheRNAME
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 forFUNCTION=APPC
and the program name forFUNCTION=DPL
requests. CICS/ESA trans-id names cannot exceed four characters and CICS/ESA program names cannot exceed eight characters. TheRNAME
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 mirrorTRANSID
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 theTRANSID
/program name combination. TheTRANSID
must be composed of acceptable CICS/ESA characters:A-Za-z0-9$@#./-_%&Q¢?!|”=,; <>
Refer to “Special Treatment of TRANS ID for DPL” in the “Application to Application Programming Considerations” section of the Oracle Tuxedo Mainframe Adapter for SNAReference Guide.
- Update the *