4.1.1.3 Modify the DMCONFIG File
The DMCONFIG
file must contain both local and
remote definitions for the simple server.
Note: A sample DMCONFIG
file is included with the
simple server.
Listing Sample DMCONFIG File
*DM_LOCAL_SERVICES
#The ATMI reverse string server
MIRROR LDOM=”simpsnad”
CONV=N
RNAME=”MIRRORSERV”
INBUFTYPE=”STRING”
OUTBUFTYPE=”STRING”
DOUBLEMIRROR
CONV=N
RNAME="MIRRDPLS"
INBUFTYPE="STRING"
OUTBUFTYPE="STRING"
*DM_REMOTE_SERVICES
#The CICS upper-case DTP and DPL servers
SIMPDPL AUTOTRAN=N
LDOM=”simpsnad”
RDOM=SNAG1
CONV=N
RNAME=”TOUPDPLS”
INBUFTYPE=”STRING”
OUTPBUFTYPE=”STRING”
FUNCTION=”DPL”
SIMPDTP AUTOTRAN=N
LDOM=”simpsnad”
RDOM=SNAG1
CONV=N
RNAME=”DTPS”
INBUFTYPE=”STRING”
OUTPBUFTYPE=”STRING”
FUNCTION=”APPC”
In the preceding DMCONFIG
file example, both
instances of the LDOM
name correspond to the SNA
domain name in the DM_LOCAL_DOMAINS
section. The
server is a request/response server.
In the DM_LOCAL_SERVICES
section, the
RNAME=”MIRRORSERV”
and
RNAME="MIRRDPLS"
values are the names passed from the
CICS/ESA environment. MIRROR
and
DOUBLEMIRROR
refer to the advertised services provided
by the mirrorsrv
server named in the
UBBCONFIG
file. The CONV=N
definition
indicates the protocol that is observed by the SNA domain, although
the CICS/ESA client does not perform an ATMI
tpcall
.
In the DM_REMOTE_SERVICES
section, the
RNAME
value identifies what is invoked in the CICS/ESA
domain. For the Distributed Program Link (DPL) request, the
RNAME
equals the name of the program called (or
for alternate mirror transaction identifiers, a
TRANSID
/program name combination). For the
Distributed Transaction Processing (DTP) request, the
RNAME
equals the name of the transaction
ID.
If you want to run transactional verification tests, you must
enter a link definition MAXSYNCLVL=2
in the
DM_SNALINKS
section. If you want to run
non-transactional DPL tests only, you must enter
MAXSYNCLVL=1
.
Parent topic: Building ATMI Platform Executables