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

Initial Configuration of the Parmlib

Customize the Parmlib that was allocated and populated by running the VTA08NON job in the chapter "System Setup".

For more information about the Parmlib attributes and their values, see the chapter "The Parameter Library (PARMLIB)." The sample Parmlib member attribute settings are typically acceptable at any site, but review them to ensure they will work at your site. Where applicable we direct you 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.

   Review and update the following Parmlib attributes:

   Startup Options Section

   • CacheDefaultDataClass to the data class name you defined.
   • CacheDefaultStorageClass to the storage class name you defined.
   • DsnameBSDS1 to the name of the BSDS1 data set you defined.
   • DsnameGlobalVcat to the name of the Global VCAT you defined.
   • DsnameLocalVcat 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 leave at the default value of &SVTS.
   • SubAddressSpacename leave at the default value of &JOBNAME.
   • Tasklib to Automatic which dynamically allocates 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 can provoke messages. See Library Mode for this attribute in the chapter "The Parameter Library (PARMLIB)" to prevent the health check messages.
   • ZIIPExploitation to Y if you have a zIIP engine that is installed or want RMF to track potential zIIP usage.

   Dynamic Options Section

   • ForeignTapesExpdt to the same value that your tape management system uses.
   • HardwareCompressionOption to N if the network storage you use already performs compression or data deduplication.
   • Logstream with the IBM system logger log stream name defined for CA Vtape use.
   • PercentRunOnzIIP 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. Review and set the value high (for example, 5000). The high value ensures that you are warned of a pending shortage early. The high value also provides the time to determine the number of Virtual Volumes you use and scratch daily so you can calculate a better threshold value.

   Open System Server Section

   • The IPAddress and Port attributes assigned appropriate values that are 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 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, define the VOLSER ranges in the tape management system to let the system track and control the use of the Virtual Volumes like physical tapes. Reserve the ranges that you define solely for the use of CA Vtape.

   Define the subset of VOLSERs reserved for disaster recovery testing 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 with CHPIDs that Virtual Devices use. Use the device addresses of OSA cards or for DASD volumes in a different DASD subsystem.

     Note: For more information about 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. Use this member 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. Do not code Pool8 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 you enter Data Class filters, make the corresponding changes in the DFSMS ACS routines. This assigns the entered Data Classes to data sets whose tape mounts CA Vtape intercepted.

   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 ensures that the member, which contains the internal configuration data that CA Vtape needs to initialize new control data sets, is not accidentally overlaid or deleted and is available at your disaster recovery site.