The MFAXML member also contains definitions that describe both application servers and services. Service definitions such as RIMS, MCO, MFA and ES-MTO provide an ID label and the LU 6.2 parameters needed to contact the server using SNA LU 6.2 protocols. The ID label is used in some client configurations to select a specific target server.
Application server's definitions such as DataConnect, Endevor, ChangeMan and AMS define address spaces that can be started and controlled by Mainframe Access server. The definition provides a JCL procedure name that can be used to start the address space, a server program name, values that govern the number of address spaces that can be started, etc.
If you use CICS Option or IMS Option, you must edit the Mainframe Access sample services definitions to customize them for your system. The application server and service definitions for the Mainframe Access Data Connect server will need to be edited only if you have changed the JCL procedure name or the VTAM APPL ACBNAME, or if the default logmode name cannot be used.
The sample definitions for services that you will not be using can be commented out and they will not affect the operation of Mainframe Access with services that you have customized. For example, if you are not using CICS Option you can leave the sample CICS target server definitions unchanged; or you can delete them altogether.
The sample server definitions are provided here as an example. Lines that begin with an asterisk are treated as comments and are skipped in processing.
<Configuration
TCP_PORT="2020"
NETWORK_ID="DDINET1"
LU62_APPLID="MFM62ACB"
APPLID_PASSWORD="MFM62PSW"
TRACING="0"
ORGANIZATION="YOUR_COMPANY_NAME"
>
<!-- Application Server address space definitions -->
<ApplicationServers>
<!-- Mainframe Access Server (Data Connect) address space -->
<DataConnect PROCEDURE="MFAS"
/>
<!-- Mainframe Access Application Server(s) for Endevor -->
<Endevor PROCEDURE="MFAAS" MAXIMUM="2" JOBNAME="MFAE"
/>
<!-- IDCAMS address space - needed for data set RENAME support -->
<AMS PROCEDURE="MFAMS" MAXIMUM="1" JOBNAME="MFAA"
/>
<!-- Mainframe Access Application Server for TSO command support -->
<TSO PROCEDURE="MFAAS" TSO_PROCEDURE="MFATSO"
TSO_JOBCHAR="W"
/>
</ApplicationServers>
<!-- Service Configuration -->
<Services>
<!-- MFA Data Connect server - only one DEFAULT server is supported -->
<MFA ID="DEFAULT" LUNAME="MFA62ACB" MODENAME="#INTER"
TPNAME="FILESHR2" SYNCLEVEL="1" SECURITY="0"
/>
<!-- Sample IMS servers - multiple servers may be defined -->
<!--
<RIMS ID="IMSA" LUNAME="IMSSYSA" MODENAME="IBMRDB"
TPNAME="MFDBTP6" SYNCLEVEL="0" SECURITY="0"
/>
<RIMS ID="DEFAULT" LUNAME="IMSTEST" MODENAME="IBMRDB"
TPNAME="MFDBTP6" SYNCLEVEL="0" SECURITY="0"
/>
-->
<!-- Sample CICS servers - multiple servers may be defined -->
<!--
<MCO ID="CICA" LUNAME="CICSSYSA" MODENAME="#INTER"
TPNAME="*" SYNCLEVEL="0" SECURITY="0"
/>
<MCO ID="DEFAULT" LUNAME="CICSTEST" MODENAME="#INTER"
TPNAME="*" SYNCLEVEL="0" SECURITY="0"
/>
-->
<!-- Sample ES/MSS servers - multiple servers may be defined -->
<!--
<ES-MTO ID="MTO1" ACBNAME="MFAMTO1" IPADDRESS="YOUR.MTO.HOSTNAME"
PORT="2200" SESSIONS="4" SOCKETS="1"
/>
<ES-MTO ID="MTO2" ACBNAME="MFAMTO2" IPADDRESS="101.102.103.104"
PORT="3300" SESSIONS="4" SOCKETS="1"
/>
-->
</Services>
</Configuration>
The section in bold above highlights the area of the XML file that you can edit, add, or remove parameters in order to control Mainframe Access behavior in regard to application servers and services. See Configuration reference for more information on the available parameters.