Disk devices are generated as devices with the device type code A5 or AA on a disk controller.
When you attach a disk device, the attributes of the device are ascertained dynamically and used to update the BS2000 device tables regardless of the generated device type code (within the device type codes for disk devices).
The device and controller ports and the operating mode of the controllers are defined during generation with IOGEN and entered in the IOCF.
For information on “dynamic I/O configuration modification”, see "I/O configuration".
Parallel Access Volume (PAV)
The generation of Parallel Access Volumes (PAV) is recommended for ETERNUS DX/AF disk storage systems, see "PAV" in section "General conditions for hardware generation" and in the “Introduction to System Administration” [4] manual.
For Fast DPAV Alias devices the device type code A6 is used.
Changing disk controllers and/or devices
Replacing a previously generated (i.e. old) storage system by a new one results in changed WWPNs of the Storage Ports. Therefor the CTL statements have to be adapted to the new FC target ports. An updated generation and IOCF is required. No further changes are required if the following conditions apply:
the same server channel ports are used
the devices connected to the new disk controller have the same addresses (LUNs) as the devices connected to the old disk controller
Generating virtual devices (SNAP disks)
In BS2000 for SU /390, virtual devices or SNAP disks must be generated as disks of the same type as the original disks. When a pubset with snapsets is to be used on more than one BS2000 system, the same number of SNAP disks must be generated on all of these systems.
For information on generating virtual devices on SU x86, see the “SHC-OSD” manual [12].