Mainframe Access is a general purpose server, supporting a variety of Micro Focus client products. The Quick Configuration process that you have completed enables a large number of Mainframe Access server features that satisfy most access requirements. This section describes the customization (beyond the quick configuration) that are needed to enable various additional features of Mainframe Access server.
The following table summarizes the required updates on a per-feature basis. This will help you to select the correct configuration activities for a specific feature:
| Feature | Customization |
|---|---|
| Audit Log | Refer to Allocating and Initializing an Audit Log Data Set to prepare the data set. Then see Editing Mainframe Access Parameters and update the audit log parameter to AUDIT_LOG="1". |
| Access List | Refer to Editing Access List Definitions for guidance in defining IP addresses and address ranges. Then see Editing Mainframe Access Parameters and update the access list check parameter to ACCESS_LIST_CHECK="1". |
| CICS support | Using CICS support, clients can interact with z/OS CICS servers for file access, remote program execution, transaction execution,
and so on. Activate support for this feature by setting
MCOLINK_MAXTASKS="2". The number of tasks supporting this feature can be increased in the future as your usage dictates.
To complete the setup for this feature you need to customize your client and the z/OS CICS server. |
| Remote IMS Option | Using the Remote IMS Option, clients can execute DL/I calls that are processed by a z/OS IMS server. Activate support for
this feature by setting
IMSLINK_MAXTASKS="2". The number of tasks supporting this feature can be increased in the future as your usage dictates.
To complete the setup for this feature you will need to customize your client and the z/OS IMS server. You must also install the Remote IMS server software in the target z/OS IMS server and enable APPC/MVS communications for that IMS server. All of the machine-readable installation materials for your Remote IMS Server can be found in the <hlq>.RIMS data set. |
| List DB2 | Mainframe Access' List DB2 feature dynamically identifies z/OS DB2 and IMS servers that are active on the z/OS system where Mainframe Access server is executing. This information can be helpful when defining these systems to Mainframe Access server and clients. Activate support for this feature by setting LIST_DB2="1". |
| Data Connect | Quick Configuration installs the Mainframe Access Data Connect server with SAF security checking active and without special customization for PC to mainframe file name mapping. If you need to alter this basic setup see the appendix Data Connect. |
| Enterprise Server/Mainframe Subsystem Support | Enterprise Server/Mainframe Subsystem Support (ES/MSS) enables Mainframe Access server to accept CICS ISC requests initiated
by z/OS CICS and route them to an ES/MSS server for execution. The combination of ES/MSS support and the CICS support creates
a bi-directional ISC connection between ES/MSS and z/OS CICS.
To complete the setup for this feature you need to customize your ES/MSS server(s) and the z/OS CICS server(s). See your Enterprise Server documentation and IBM z/OS CICS publications for help with this customization. |
| ChangeMan interface | Mainframe Access' Source Connect feature works with ChangeMan to provide client access to ChangeMan-managed files. For more information see the section ChangeMan ZMF in the appendix External Library Management Systems. |
| Panvalet interface | Mainframe Access' Source Connect feature works with Panvalet to provide client access to Panvalet-managed files. For more information see the section Panvalet in the appendix External Library Management Systems. |
| Librarian interface | Mainframe Access' Source Connect feature works with Librarian to provide client access to Librarian-managed files. For more information see the section Librarian in the appendix External Library Management Systems. |
| Endevor interface | Mainframe Access' Source Connect feature works with Endevor to provide client access to Endevor-managed files. For more information see the section Endevor in the appendix External Library Management Systems. |