Configuring the Parameter Library (Parmlib) › Initial Configuration of the Parmlib

Initial Configuration of the Parmlib

Complete the following steps to customize the parmlib that was allocated and populated by running the VTA08NON job in the chapter "System Setup".

Detailed explanations of the parmlib attributes and their values can be found in the chapter "The Parameter Library (PARMLIB)." The attribute settings in the sample parmlib members are generally acceptable at any site, but should be reviewed. Where applicable we will direct your attention to a specific attribute to make a recommended change.

Follow these steps:

1. Edit OSPARMS in PREFIX.PARMLIB.

   Follow the comments in the member to set up the attributes in the Startup Options, Dynamic Options, and Open System Server sections.

   The following parmlib attributes will need to be updated or reviewed:

   Startup Options Section

   • CacheDefaultDataClass should be set to the data class name you defined.
   • CacheDefaultStorageClass should be set to the storage class name you defined.
   • DsnameBSDS1 should be set to the name of the BSDS1 data set you defined.
   • DsnameGlobalVcat should be set to the name of the Global VCAT you defined.
   • DsnameLocalVcat should be set to the name of the Local VCAT you defined. Using symbolic substitution is recommended. If you followed the recommended naming standard, a value of ‘CAVTAPE1.&SYSNAME..&SVTS.VCAT’ would be used.
   • MessagePrefix should be left at the default value of &SVTS.
   • SubAddressSpacename should be left at the default value of &JOBNAME.
   • Tasklib is set to Automatic which will dynamically allocate and APF authorize a loadlib data set for use when starting and restarting the Virtual Device Controllers address spaces. If you are executing IBM health checks, this may provoke messages. See Library Mode for this attribute in the chapter "The Parameter Library (PARMLIB)" to prevent the health check messages.
   • ZIIPExploitation should be changed to Y if you have a zIIP engine installed or want RMF to track potential zIIP usage.

   Dynamic Options Section

   • ForeignTapesExpdt should be set to the same value used by your tape management system.
   • HardwareCompressionOption should be set to N if the network storage you will use already performs compression or data deduplication.
   • Logstream should be updated with the IBM system logger log stream name defined for CA Vtape use.
   • PercentRunOnzIIP should be set to 100 if you are tracking potential zIIP usage or to an appropriate percentage if you have a zIIP engine installed. Discussing this setting with your z/OS or DB2 Performance and Tuning Specialist is recommended.
   • ScratchVolumesThreshold should be reviewed. Setting it to a high value like 5000 to begin with will ensure that you are warned of a pending shortage in plenty of time to address it. It will also allow you the time to determine the number of Virtual Volumes you will use and scratch daily so you can calculate a better threshold value.

   Open System Server Section

   • The IPAddress and Port attributes should be assigned appropriate values used for communication through TCPIP with the CA Cloud Linux Server. This allows the Subsystem to query status and asynchronously communicate requests with the CA Cloud Linux Server.
   • The PipeUnitAddress attribute should be assigned the CTC device addresses used to communicate Virtual Volume data with the CA Cloud Storage for System z Server. These CTC connections provide secure and high performance transmission of data with the CA Cloud Linux Server.
2. Edit OSPOOLS.

   Follow the comments in the member to customize the Volume Pool Definitions and Volume Pool Sections.

   Note: If you have a tape management system, the VOLSER range or ranges should be defined in the tape management system to allow it to track and control the use of the Virtual Volumes just like physical tapes. The range or ranges defined should be reserved solely for the use of CA Vtape.

   The subset of VOLSERs reserved for disaster recovery testing should be defined in Pool8.

3. Edit OSDRIVE.

   Follow the comments in the member to:

   • Split the primary set of Virtual Devices between controller 1 and controller 2. If needed, up to eight controllers can be defined.
   • Uncomment and update the ChpidDeviceList attributes with the list of devices who’s CHPIDs will be used by the Virtual Devices. The device addresses of OSA cards or for DASD volumes in different DASD subsystems should be used.

     Note: For more detailed information on choosing CHPIDs, see the section Virtual Device Channel Paths in the chapter "Virtual Device Engine".

4. Create OSDRALT.

   Copy OSDRIVE into OSDRALT and change the primary set of Virtual Devices to the alternate set. This member will be used to avoid an IPL if the operating system boxes the current set of Virtual Devices and will not let them be varied back online after they have been restarted in CA Vtape.

5. Edit OSGROUP.

   Follow the comments in the member to set up the group options.

   Note: Pool8 is reserved for disaster recovery testing and should not be coded on the VolumePools attribute for any active group.

6. Edit OSFILTR.

   Follow the comments in the member to add one or more Data Set Name Filters or Data Class Filters.

   If Data Class filters are entered, make the corresponding changes in the DFSMS ACS routines to assign the entered Data Classes to data sets whose tape mounts should be intercepted by CA Vtape.

   Note: Do not add the CacheDefaultDataClass value as one of the data class filters.

7. Secure the SUTPARMS member.

   Copy the generated SUTPARMS member from the SVTJCL library to the parmlib. This will insure that this member, which contains the internal configuration data needed by CA Vtape to initialize new control data sets, will not be accidentally overlaid or deleted and will be available at your disaster recovery site.