Use the DEVTYPE record to customize the name, attributes, or space characteristics of a specific device type.
DEVTYPE name {"ParmA" | "ParmB"} [("Options"]
ParmA:
prototype [blksize [units]]
ParmB:
X’hhhh’ blksize units tracks bytes num512blks num1Kblks num1Kblks num2Kblks num4Kblks [ sector ...]
Options:
[CACHE | NOCACHE] [CYL0RES pages] [FBA] [MDC | NOMDC]
DEVTYPE is defined in the DASD CONFIG file.
Specifies the customized device type name. You can make the name anything that is meaningful to your installation. See the Name column in the table for the device type names supplied by CA VM:Director.
Identifies a device type that CA VM:Director supplies and that you want to use as a model for the new device type. To create the new device type, CA VM:Director uses all values defined for the prototype device, except those values that the blksize and units parameters or the options override.
If you specify the prototype form, as opposed to the X’hhhh’ form of the record, then the blksize and units parameters are optional. You can use them to override the values found in the prototype. However, you cannot specify any of the other parameters. You can still include any options that apply.
Identifies the device type as a new one with no prototype definition. Replace hhhh with the new device’s two‑byte device class and type, specified in hexadecimal. (IBM defines these values.)
The type codes for existing devices differ between different operating systems. Be sure to use the correct codes for your running system.
For the name parameter, specify the device name as the true device type that the MDISK directory record supports. If you do not, some commands using this device name may fail.
If you specify the X’hhhh’ form, as opposed to the prototype form of the record, you must also specify all remaining parameters except for the sector1 ... sectorn parameters. Those parameters are only required if the defined device type will be used to contain the online directory.
Specifies a default CMS blocksize that CA VM:Director uses whenever you format a minidisk. You can override this default on input screens and on some commands. Valid values are 512, 1024, 2048, 4096, 1K, 2K, and 4K.
Specifies the maximum number of allocatable units (cylinders or blocks) described by EXTENT records in the configuration file.
Specifies the number of bytes on each track of CKD devices. The number must be greater than 0 and less than 1000000. For current FBA devices, the number is always 512.
Note: For the following parameters, CA VM:Director validates the space characteristic by verifying that the specified number for each size block multiplied by the blocksize does not exceed the number of bytes per allocatable unit.
Specifies the number of 512‑byte blocks for each allocatable unit. This number must be less than 10000.
Specifies the number of 1K‑byte blocks for each allocatable unit. This number must be less than 1000.
Specifies the number of 2K‑byte blocks for each allocatable unit. This number must be less than 1000.
Specifies the number of 4K‑byte blocks for each allocatable unit. This number must be less than 1000.
Specifies a list of the optional, one‑byte Rotational Position Sensing (RPS) values required for CKD devices to contain the online directory.
The RPS values in the sector list represent the physical locations on the disk surface where CA VM:Director can read or write directory pages. CA VM:Director requires these values when a disk of this device type will contain the online directory.
Note: CA VM:Director does not verify these codes. Because you cannot calculate the values, contact Technical Support for the correct values to enter for any new device type.
FBA devices do not support RPS, and you cannot use this parameter with them. However, you can still use FBA devices to contain the online directory on systems that support them.
Indicates that the device type supports caching (CACHE) or does not support caching (NOCACHE).
Specifies the number of pages to reserve for allocation information when the object directory begins in cylinder 0. Specify the CYL0RES option only if you are creating a new device type that will contain the object directory, and if the object directory will start in cylinder 0 of the new device.
You do not need to specify this option if the new device is an FBA device, or if the object directory will not start in cylinder 0 of the new device.
Indicates that the device type is a fixed block architecture (FBA) device. This option is required when you are defining an FBA device.
Indicates that caching uses expanded memory to cache the minidisk, regardless of the DASD device the minidisk is on (MDC), or that no expanded memory caching is to be used for the minidisk (NOMDC).
The DEVTYPE record provides support for a new device type between releases of CA VM:Director or makes device type names more meaningful or more usable. For example, if you change 3390‑3 to 3390‑9, CA VM:Director rechecks existing VOLUME and EXTENT records to ensure the update does not invalidate them.
The DEVTYPE record enables you to customize device types by specifying either a prototype device type or an explicit device type. Differences between the two methods are explained in the parameter definitions.
You can redefine entries that CA VM:Director supplies and change the default block size or limit the number of allocatable units for a device type. For example, if you use the name TEST90 for a 3390 with only 200 cylinders, you can also use the available options to override the defaults that CA VM:Director specifies.
The DEVTYPE record is optional as long as the device types that you use are included in those that CA VM:Director supplies. This is the case for most installations, except when a new device type is announced. When CA VM:Director includes support for new device types in a subsequent release, that DEVTYPE record will be unnecessary.
|
Copyright © 2014 CA.
All rights reserved.
|
|