OSDRIVE is a parmlib member containing Virtual Control Unit numbers and device addresses used by CA Vtape to start Virtual Control Units and Virtual Devices. The Virtual Devices are local in scope, unique to a system or LPAR. They are affectively "cabled" to the Virtual Control Units they are defined to. Virtual Device 100 on LPAR SYS1 is not the same device as Virtual Device 100 on LPAR SYS2. Both devices can be on-line and servicing different tape mounts at the same time.
This section contains an alphabetic list of the Virtual Drive List attributes. The list contains a description of each attribute, its valid values, and the CA Vtape features it supports.
A valid online Channel Path ID (CHPID) must be assigned to every Virtual Device in order to successfully vary them online. ChpidDeviceList is an optional attribute which can be used to define up to eight physical devices from which active CHPIDs will be assigned to the devices of a Virtual Control Unit.
When the ChpidDevList attribute is not specified, the Subsystem will look for the device assigned to the //CHPID DD in the SVTSCE JCL procedure and it will use those CHPIDS for all the devices defined by all Virtual Control Units. If the //CHPID DD is not present, the Subsystem will use the CHPIDs assigned to the DASD device associated with the BSDS1 control data set.
This attribute offers the greatest degree of flexibility since it allows you to assign different CHPIDs to different Virtual Control Units to eliminate a single point of failure.
Up to eight, comma delimited devices can be defined. Only the first 8 CHPIDs found when parsing the device list will be used.
Note: CHPIDs that are initially assigned to a Virtual Device remain in effect until the next IPL. If you change the ChpidDeviceList, CHPID DD or BSDS1 location and then restart the Subsystem, the modifications will have no effect on the CHPIDs used for previously defined Virtual Devices. The modifications will take effect only for newly defined devices.
Note: Our recommendation is to define two Virtual Control Units with different ChpidDeviceList values. Those values should include at least two non-DASD devices that utilize different CHPIDs. This will ensure a minimum of two non-DASD CHPIDs are assigned to each Virtual Device and no more than half of the Virtual Devices are using these same CHPIDs.
Valid Values:
Defines a single Device address.
Defines a list of individual device addresses separated by commas.
Defines a range of device addresses with the starting and ending address separated by a dash (-) or a colon (:).
Defines a list and a range of device addresses separated by commas.
Feature: Virtual Device Engine
Determines which Virtual Devices are assigned to a particular VirtualControlUnit and that these devices should not be varied online when CA Vtape is started. The attribute can be repeated as many times as needed to define all the Virtual Devices for a Control Unit.
Valid Values:
Defines a single Virtual Device address.
Defines a list of individual Virtual Device addresses separated by commas.
Defines a range of Virtual Device addresses with the starting and ending address separated by a dash (-) or a colon (:).
Defines a list and a range of Virtual Device addresses separated by commas.
Feature: Virtual Device Engine
Determines which Virtual Devices are assigned to a particular VirtualControlUnit and that these devices should be varied online when CA Vtape is started. The attribute can be repeated as many times as needed to define all the Virtual Devices for a Control Unit.
Valid Values:
Defines a single Virtual Device address.
Defines a list of individual Virtual Device addresses separated by commas.
Defines a range of Virtual Device addresses with the starting and ending address separated by a dash (-) or a colon (:).
Defines a list and a range of Virtual Device addresses separated by commas.
Feature: Virtual Device Engine
Determines the number of Virtual Control Unit address spaces that are started. Up to eight can be started. Each address space controls only those Virtual Devices defined to it.
Note: We recommend that you define at least two Virtual Control Units. This will allow one Control Unit to be restarted if it develops a problem, affecting only its Virtual Devices while the other Control Unit and its devices continue to service virtual tape mounts.
Valid Values: 1 to 8
Default: 1
Feature: Virtual Device Engine
|
Copyright © 2013 CA.
All rights reserved.
|
|