Previous Topic: P2P Security ConsiderationsNext Topic: Set Up a Simple P2P Configuration to Test TCP/IP Connectivity

CA Vtape P2P Option › Configure for CA Vtape P2P Subsystems

Configure for CA Vtape P2P Subsystems

Assuming that you have an active TCP/IP stack running on your zOS/390 system, activating CA Vtape P2P consists primarily of starting CA Vtape after configuring some additional parmlib members and attributes.

To configure parmlib

The following are the basic parmlib configuration steps.

  1. Setup the VTP2POPT (VTape P2P OPTions) member. This member defines basic TCP/IP and CA Vtape P2P processing options. The sample member VTP2POPT provided in the PARMLIB library includes a description of each attribute within this member. The default values for most attributes should suffice in many cases.

    Note: Keep in mind that this member is where you will describe the parameters used by the local system to establish the TCP/IP P2P Listener. The P2P Listener processes connection requests from remote systems.

  2. Setup the VTP2RMTS (VTape P2P REMotes) member. This member defines remote systems that are allowed to communicate with this local system. The sample member VTP2POPT in the PARMLIB library includes a description of each attribute within this member.

    Important! Only the remote systems defined in this member are allowed to communicate with this local system. This member effectively names each remote system and describes the TCP/IP attributes necessary to request and accept connections with that remote system.

  3. Define the names of the VTP2POPT and VTP2PRMT members in the parmlib <Directory> section of VTPARMS member. You will need to uncomment and add both the PeerToPeerOptions and PeerToPeerRemotes attributes to the parmlib <Directory> section. These attributes name the parmlib members containing the VTP2POPT and VTP2PRMT attributes.
  4. If you have not done so already, you will also need to know how to setup Virtual Volume Pooling using the VTPOOLS parmlib member. Virtual Volume Pooling is a requirement of CA Vtape P2P. It allows CA Vtape P2P connected systems to effectively share subsets of Virtual Volumes through volser ranges.
  5. Setup remote Virtual Tape Units (VTUs) or drives in the VTDRIVES member. Remote drives are only assigned when mounting a remote Virtual Volume. Likewise local drives (local VTUs) are only assigned for mounting local Virtual Volumes.
  6. Setup remote groups definitions in the VTGROUPS member. Remote groups are just like local groups but utilize a few additional attributes, which are:
  7. The attributes which distinguish a group definition as a remote group definition are RemoteSystemPrimary, RemoteSystemSecondary, or both. These attributes specify the name of the remote system with whom to communicate when the allocation or scratch mount of a data set associated with this group is requested.

    Note: A good description of these additional attributes can be found in the VTGROUP member of the CCUUPARM library.

  8. Setup remote data set or remote data class filters or both in the VTFILTR member. These filters are used for scratch mounts and define how to associate data sets with remote groups.