First, allocate the control file on the pack you will share between z/VM and z/OS. Allocation of a z/OS format file can only be done from z/OS, either by using TSO or by submitting a job. A z/OS format control file should be allocated as a sequential file, and usually should be ten (10) cylinders long. Allocate only a single extent.
Log on to MIMGR and IPL CMS. Link in write mode to the DASD containing the file you allocated on z/OS. The link could be established by putting an MDISK or LINK statement in the directory entry for MIMGR or it could be done by using the CP link command. Alternatively, you could attach the z/OS pack to the MIMGR user ID or could use an equivalent DEDICATE statement in the directory.
Start the VMPROOF program. In the example, we assume that the z/OS pack is available to MIMGR at virtual address 945, and that the control file data set is named 'MIM.CF.01'.
VMPROOF 945 MVS F007 MIM.CF.01
VMPROOF verifies the configuration of 945, formats the area beginning at cylinder 1, and then begins writing and reading simulated control file data.
You can issue a similar command on other z/VM systems or on other guests that share the control file to verify that serialization is working as you expect. As described, the parameter F007 would be changed for each additional system you add to the test. Only the first system uses the letter "F" (others all use "N"), and each system uses a different second digit. Also, each system uses a different delay time.
|
Copyright © 2014 CA.
All rights reserved.
|
|