It is not necessary to allocate a control file for this function. Under CMS, on the ID where you plan to run CA MIM, enter the following command:
VMPROOF vdev
Specifies the virtual address of the DASD where the control file resides, or will reside.
VMPROOF displays several lines of information about the DASD similar to the following example. The information varies according to the kind of system.
vmproof 945 VERSION 2.0 Controller type 3880, Model 05 DASD type 3380, Model 1E 00885 cyls (0375 hex) Device characteristics: 0000 38800533 801E8100 0000200E 0375000F 0010 DE00BB60 04400120 01EC00EC 00000000 0020 00000000 00000000 23230900 BB740000 0030 00000000 00000000 00000000 00000000 Real device address: 0227, Real VOLSER: "MVS340" Starting real cylinder: 06EA (hex) Extent: 0375 (hex) Size of real pack: 02655 (decimal) 0A5F (hex) WARNING:Not a full pack minidisk. Does not start on real cylinder 0. WARNING:Not a full pack minidisk. Extent is less than full pack. Ready;
The preceding example shows the result you might see on a z/VM system. The results show that the DASD at 945 is a minidisk on the MVS340 pack at real address 227. VMPROOF warns that the DASD is not a full pack minidisk. This is not necessarily an error, but does mean that CP does not transmit reserve and release orders to the real device.
If the control file shares multiple processors, serialization does not work properly. If the control file is only shared among guests on the same z/VM system, however, virtual reserve/release processing enables the control file to work correctly, even in the presence of this warning.
In this example, 945 is not a full pack because it fails both tests that CP uses to define a full pack; to be qualified by CP as a full pack minidisk, cylinder 0 of the minidisk must correspond with cylinder 0 of the real disk, and the size of the minidisk must be equal to or larger than the size of the real pack. VMPROOF also reports the size of the real pack, so you can update your MDISK statement if necessary.
VMPROOF also issues a warning if the virtual DASD does not support reserve/release. This warning is usually an indication that 'V' needs to be added to the MDISK mode to invoke virtual reserve/release processing.
When a DASD device is attached to the user instead of being defined as a minidisk, VMPROOF reports that the device is DEDICATED. Dedicated DASD handles RESERVE/RELEASE correctly if the DASD controller itself handles the orders.
The display also includes device characteristics in four lines of hexadecimal data. This is the 64-byte response to a "read device characteristics" order sent to the DASD. This information may be useful in debugging difficult configuration problems.
|
Copyright © 2014 CA.
All rights reserved.
|
|