The CMSFP control file differs from the CMS control file only in the way VMPROOF and MIMGR address it. For a CMSFP control file, VMPROOF performs I/O on the full pack on which the minidisk resides. It is not even necessary for MIMGR to have a link or an MDISK statement to the minidisk.
The following sample lines from a directory entry illustrate the way to define a CMSFP control file:
USER MIMGR
. . .
MDISK 291 3390 447 011 VMVOL1 MW
MDISK 555 3390 000 885 VMVOL1 MWV
In this example, the first MDISK statement defines a minidisk for MIMGR at virtual address 291. The minidisk is 11 cylinders in length, and the first cylinder is at decimal real cylinder 447 on the real pack labeled VMVOL1. The second line defines a full pack disk on the same real pack, at virtual address 555. It is not necessary to know the real address of pack VMVOL1.
VMPROOF will need three pieces of information about the minidisk to use this file in CMSFP mode. First, it needs the vdev address of the full pack minidisk. Second, it needs the VOLSER of the minidisk (not the VOLSER of the full pack), and finally, the absolute cylinder, in hex, where the 291 minidisk is allocated on the full pack.
The following commands would be used to prepare the minidisk for control file testing, and then to start the test:
FORMAT 291 B#1#CTFL1 FORMAT 291 B 1 (RECOMP VMPROOF 555 CMSFP F007 CTFL1 1BF
Note: The value "1BF" is derived by converting the origin of the 291 disk, as stated on the MDISK statement, to hex.
When you are running VMPROOF on two or more z/VM systems and each system addresses the same CMSFP format control file, it is only necessary to define the minidisk that corresponds to the control file on one of the systems. The minidisk is only used to perform the CMS FORMAT and CMS FORMAT RECOMP functions, and this is only needed one time. All systems that will run VMPROOF must define or link the full pack minidisk to the user who will run VMPROOF.
CMSFP and CMS control files have exactly the same data structure. Therefore, some systems can refer to a control file as a CMS control file and others can refer to the same file as a CMSFP control file. Those referring to the CMS control file will perform I/O to the minidisk and those referring to the control file as CMSFP will perform all I/O to the full pack.
In z/VM, reserves are sent to the real DASD only if the RESERVE order was originally sent to a full pack minidisk, and only if the SHARED attribute is on for the real pack. This makes it necessary to address DASD as a full pack in z/VM to assert RESERVE on a real pack.
|
Copyright © 2014 CA.
All rights reserved.
|
|