Using VTAM to establish communication between different OPERTUNE systems

VTAM is used to establish communication between different OPERTUNE systems on the same MVS system or across multiple MVS systems. Using VTAM allows a host OPERTUNE to modify or tune a remote subsystem not under its direct control.

VTAM communication illustrates communication between different OPERTUNEs using VTAM:

Before an OPERTUNE system can communicate with other OPERTUNE systems, it must have an APPLID defined in its system profile. If an APPLID is specified but not yet activated, the starting OPERTUNE periodically tries to establish communications with the newly activated APPLID. The system profiles of all OPERTUNE communicating with each other should be stored in the same profile data set (see System-profiles). For two OPERTUNE systems to communicate using different profile data sets, each profile data set must include system profiles for both OPERTUNE systems.

Establishing the OPERTUNE network

If the OPERTUNE that you are trying to establish connections with is up and has an active APPLID defined in its system profile, two sessions are established as shown in Establishing sender/receiver scenarios.

• Sender session—used to send requests to the remote OPERTUNE and receive the responses
• Receiver session—used to receive remote requests and send results back

Establishing sender/receiver scenarios

To define an OPERTUNE system to VTAM

To define an OPERTUNE system as part of the OPERTUNE network, prepare the system for VTAM communications as follows:

1. Specify the VTAM APPLID in the OPERTUNE system profile (see VTAM APPLIDs).

2. Define the APPLID in a VTAMLST data set member as shown below for APPLA and APPLB. The member name cannot be the same as the VTAM APPLID name.

   APPLOPTN VBUILD TYPE=APPL
   APPLA APPL SONSCIP=NO,PARSESS=YES,
    EAS=(10),ACBNAME=APPLA
   APPLB APPL SONSCIP=NO,PARSESS=YES,
    EAS=(10),ACBNAME=APPLB 
3. Activate the APPLID as follows:
   V NET,ID=xxxxxxxx,ACT
   xxxxxxxx is the name of the VTAMLST data set member containing the APPLID definition.

Setting up cross-domain communication

For a host OPERTUNE on one MVS system to communicate with a remote target OPERTUNE on a different MVS system, you must define the remote VTAM APPLID as a cross-domain resource. The following steps are involved in setting up cross-domain communication, such as the one shown in Cross-domain VTAM sessions.

Cross-domain VTAM sessions

For MVSA

1. Specify the VTAM APPLID APPLA in the system profile of OPERTUNE OPTA.

2. Define the APPLID APPLA in a VTAMLST data set member as follows (the member name cannot be the same as the VTAM APPLID name.):

   APPLopertuneID VBUILD TYPE=APPL
   APPLA   APPL    SONSCIP=NO,PARSESS=YES,
      EAS=(10),ACBNAME=APPLA
3. Activate the APPLA as follows:
   V NET,ID=xxxxxxxx,ACT
   xxxxxxxx is the name of the VTAMLST data set member containing the APPLA definition.

4. Add a cross-domain resource member CDRSA in your VTAMLST data set to define the remote APPLB as follows (The member name cannot be the same as the label on the VBUILD statement.):

   CDRS1 VBUILD  TYPE=CDRSC
   APPLB CDRSC  CDRM=D2
5. Activate CDRS1 in MVSA, using the VARY command as follows:
   V NET,ID=CDRSA,ACT

For MVSB

1. Specify the VTAM APPLID APPLB in the system profile of OPERTUNE OPTB.

2. Define the APPLID APPLB in a VTAMLST data set member as follows (the member name cannot be the same as the VTAM APPLID name.):

   APPLopertuneID VBUILD TYPE=APPL
   APPLB   APPL   SONSCIP=NO,PARSESS=YES,
      EAS=(10),ACBNAME=APPLB
3. Activate the APPLB as follows:
    V NET,ID=xxxxxxxx,ACT
   xxxxxxxx is the name of the VTAMLST data set member containing the APPLB definition

4. Add a cross-domain resource member CDRSB in your VTAMLST data set to define the remote APPLA as follows (The member name cannot be the same as the label on the VBUILD statement.):

   CDRS2 VBUILD    TYPE=CDRSC
   APPLA CDRSC    CDRM=D1
5. Activate CDRS2 in MVSB, using the VARY command as follows:
   V NET,ID=CDRSB,ACT