The VTAM (Virtual Telecommunications Access Method) component has to be configured for CICS partners running on the IBM mainframe (z/OS system). VTAM is an IBM product that runs on the mainframe and enables access to a CICS region on that mainframe. Requests from the proxy are passed to VTAM and then to CICS. Therefore, some VTAM definitions are needed.
VTAM definitions are coded using macros. The Management Console generates an input file for the VTAM configuration during the configuration run (see section Configuring EIS partners of type CICS ). This input file contains definitions for the Physical Unit (PU) in VTAM.
In the case of a single proxy, the name of the generated input file is:
ProxyID.<p-id>.EisPartnerID.<e-id>.VTAM.txt
In the case of a proxy in a cluster, the name of the generated input file is:
ClusterID.<c-id>.ProxyID.<p-id>.EisPartnerID.<e-id>.VTAM.txt
<p-id>, <e-id> and <c-id> designate the IDs for the proxy, EIS partner and proxy cluster assigned by the Management Console.
BeanConnect does not transfer the VTAM configuration file to the EIS platform. The generated input file has to be transferred to the EIS partner host using common file transfer mechanisms. After that, the VTAM administrator can use the file to carry out the configuration activities. Note that the VTAM administrator has to adapt some VTAM definitions to the needs of the partner application. BeanConnect cannot guarantee the uniqueness of the definitions when generating the file because it has no access to the complete VTAM definitions. Therefore, the configuration file contains some question marks which must be replaced with the proper values.