Use this page to enable Mainframe Transaction Option (MTO) and configure CICS support for this server.
Note: You can use the resolved value of an environment variable in any fields for the entry of file or directory paths. To do this, prefix the environment variable you want to include with a dollar ($) sign; for example:
$production\programs
where production is an environment variable.
If you want to use a dollar sign as part of the value, rather than as an indicator of an environment variable, you must escape the dollar sign character with a backslash(\); for example:
\$production\programs
In this case, $production will not be replaced by the value of the environment variable.
Check this to enable MTO for this enterprise server.
Indicates whether or not CICS is enabled. In this release, CICS is automatically enabled when Mainframe Transaction Option is enabled.
Specify the system initialization table (SIT) to be used by this enterprise server. Defaults to DFH$IVP.
Specify the full path of the CICS transaction programs that will run in this enterprise server. Separate multiple paths with semi-colons on Windows or colons on UNIX. Mandatory if you use any other SIT than DFH$IVP.
Specify the full path of the VSAM files required by the CICS transaction programs that will run in this enterprise server. Separate multiple paths with semi-colons on Windows or colons on UNIX. Mandatory if you use any other SIT than DFH$IVP.
Specify the full path of any BMS map load modules required by the CICS transaction programs that will run in this enterprise server. Separate multiple paths with semi-colons on Windows or colons on UNIX. Mandatory if you use any other SIT than DFH$IVP.
Specify the full path of the resource definition file for this enterprise server. Mandatory if you use any other SIT than DFH$IVP.
Check this to enable support for CICS and JCL applications that use the EZASOKET APIs.