Activating Shared Databases on VM Systems

Installation Options › Shared Database Support › Activating Shared Databases on VM Systems

Activating Shared Databases on VM Systems

Follow these steps to implement CA ACF2 for z/VM shared databases:

Modify the user directory and, if necessary, the IBM HCPRIO module. There are different requirements for this step, depending on how your site intends to share databases (sharing with guest virtual machines, sharing with other processors, or sharing with both). In addition, you can share databases on a full disk pack or a partial pack.
Modify the service machine ACFSTART EXEC.
Modify, assemble, and reload the ACFFDR.
Merge the databases using the ACFDBVSM utility program.

Details follow on the next few pages.

Step 1: Modify the User Directory and HCPRIO

Some sites share their database with a guest VM system. Other sites share their database with one or more processors. Whatever the case, your configuration setup depends on whether the database resides on a full pack minidisk or a partial pack minidisk.

Skip to Requirements for Sharing on a Partial Pack Minidisk if you intend to share databases on a partial pack minidisk.

Requirements for Sharing on a Full Pack Minidisk

The requirements differ, depending on whether you are sharing with other processors, guest virtual machines, or both.

For each processor sharing the full pack minidisk, it is imperative that there be only one system directory MDISK definition in MWV mode. All other accesses by that processor must be through a directory LINK definition in MW mode to the pack's MDISK definition in MWV mode.

For each processor sharing the full pack minidisk, we recommend you give the CA‑ACF2 service machine the sole MDISK definition in MWV mode.

Full Pack Scenarios

Different scenarios are possible for sharing databases on a full pack minidisk. Follow the instructions under the heading that coincides with the scenario at your site:

Sharing Only with Other Guest Machines:
The system directory for the CA ACF2 for z/VM service machine must include an MDISK definition in MWV mode for access to the full‑pack minidisk or must include a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

The system directory for the guest machine can include an MDISK definition in MWV mode for access to the full pack minidisk (as long as you did not define another MWV MDISK statement) or it must include a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

You can define more than one guest machine on the VM processor.

The following processor directory entries illustrate a possible scenario for sharing CA ACF2 for z/VM databases with a guest machine on a full‑pack minidisk:
```
USER ACF2VM . . .
```
```
    .
```
```
    .
```
```
MDISK 300 3380 000 885 VSMPCK MWV
```
```
    .
```
```
    .
```
```
    .
```
```
USER GUESTVM
```
```
    .
```
```
    .
```
```
LINK ACF2VM 300 300 MW
```
Proceed to Step 3: Modify, Assemble, and Reload the ACFFDR after you modify the user directory.
Sharing Only with Other Processors:
The system directory for the CA ACF2 for z/VM service machine on the first processor must include an MDISK definition in MWV mode for access to the full pack minidisk or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

The system directory for the CA ACF2 for z/VM service machine on another processor must include an MDISK definition in MWV mode for access to the full pack minidisk or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

You must generate the real DASD as SHARED in the HCPRIO definition for the device.

The following processor directory entries illustrate a possible scenario for sharing CA ACF2 for z/VM databases with another processor on a full pack minidisk:
```
USER ACF2VM . . .
```
```
    .
```
```
    .
```
```
MDISK 300 3380 000 885 VSMPCK MWV
```
Other Processor Directory Entries:
```
USER ACF2VM . . .
```
```
    .
```
```
    .
```
```
MDISK 300 3380 000 885 VSMPCK MWV
```
Proceed to Step 3: Modify, Assemble, and Reload the ACFFDR after you modify the user directory and HCPRIO.
Sharing with Guest Machines and Other Processors:
The system directory for the CA ACF2 for z/VM service machine on the first processor must include an MDISK definition in MWV mode for access to the full‑pack minidisk or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

The system directory for the guest machine on the first processor can include an MDISK definition in MWV mode for access to the full pack minidisk (as long as you did not define another MWV MDISK statement) or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode. You can define more than one guest machine.

The system directory for the CA ACF2 for z/VM service machine on another processor must include an MDISK definition in MWV mode for access to the full pack minidisk or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

The system directory for the guest machine (if there is one) on the other processor can include an MDISK definition in MWV mode for access to the full pack minidisk (as long as you did not define another MWV MDISK statement) or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode. You can define more than one guest machine.

You must generate the real DASD as SHARED in the HCPRIO definition for the device.

The following directory entries illustrate a possible scenario for sharing CA ACF2 for z/VM databases with a guest machine and another processor on a full pack minidisk:
```
USER ACF2VM . . .
```
```
  ...
```
```
MDISK 300 3380 000 885 VSMPCK MWV
```
```
  ...
```
```
USER GUESTVM . . .
```
```
  ...
```
```
LINK ACF2VM 300 300 MW
```
Proceed to Step 3: Modify, Assemble, and Reload the ACFFDR once you modify the user directory and HCPRIO.

Requirements for Sharing on a Partial Pack Minidisk

The requirements differ, depending on whether you are sharing with other processors, guest virtual machines, or both.

For each processor sharing the partial pack minidisk, it is imperative that there be only one system directory MDISK definition in MWV mode. All other accesses by that processor must be through a directory LINK definition in MW mode to the pack's MDISK definition in MWV mode. There is one exception to this rule. For database sharing on a partial pack minidisk with other processors, the processor requires two MDISK statements: one for the partial pack and one for the full pack the partial pack is on.

Partial Pack Scenarios

Different scenarios are possible for sharing databases on a partial pack minidisk. Follow the instructions under the heading that coincides with the scenario at your site:

Sharing Only with Other Guest Machines:
The system directory for the CA ACF2 for z/VM service machine must include an MDISK definition in MWV mode for access to the partial pack minidisk or a LINK definition in MW mode to the partial minidisk's MDISK definition in MWV mode.

The system directory for the guest machine can include an MDISK definition in MWV mode for access to the partial‑pack minidisk (as long as you did not define another MWV MDISK statement) or a LINK definition in MW mode to the partial minidisk's MDISK definition in MWV mode. You can define more than one guest machine on each processor.

The following processor directory entries illustrate a possible scenario for sharing CA ACF2 for z/VM databases with a guest machine on a partial pack minidisk:
```
USER ACF2VM . . .
```
```
  ...
```
```
MDISK 300 3380 440 020 VSMPCK MWV
```
```
  ...
```
```
USER GUESTVM
```
```
  ...
```
```
LINK ACF2VM 300 300 MW
```
Proceed to Step 3: Modify, Assemble, and Reload the ACFFDR after you modify the user directory.
Sharing Only with Other Processors:
The system directory for the CA‑ACF2 service machine on the first processor must include an MDISK definition in MWV mode for access to the partial‑pack minidisk or a LINK definition in MW mode to the partial minidisk's MDISK definition in MWV mode.

To queue real reserves to the hardware, the processor requires another MDISK statement. We recommend you assign both MDISK statements to the CA ACF2 for z/VM service machine.

The directory for the CA ACF2 for z/VM service machine on the first processor must include an MDISK definition in MWV mode for access to the full pack minidisk or a LINK definition in MW mode to the full pack's MDISK definition in MWV mode.

The system directory for the CA ACF2 for z/VM service machine on another processor must include an MDISK definition in MWV mode for access to the partial pack minidisk or a LINK definition in MW mode to the partial minidisk's MDISK definition in MWV mode.

You must generate the real DASD as SHARED in the HCPRIO definition for the device.

The following processor directory entries illustrate a possible scenario for sharing CA ACF2 for z/VM databases with a VM processor on a partial pack minidisk:
```
USER ACF2VMEA . . .
```
```
  ...
```
```
MDISK 300 3380 440 020 VSMPCK MWV
```
```
MDISK 308 3380 000 885 VSMPCK MWV
```
Proceed to Step 3: Modify, Assemble, and Reload the ACFFDR after you modify the user directory and HCPRIO.
Sharing with Guest Machines and Other Processors:
When sharing with guest machines and other processors, the partial pack minidisk must start on cylinder zero. Define this partial pack minidisk for the CA ACF2 for z/VM service machine and the guest's directory entries as a full pack minidisk. It is the VTOC that DSF created to be a minipack that forces VSAM to treat the full pack as a partial pack.

To queue real reserves to the hardware, the system directory for the CA ACF2 for z/VM service machine on the first processor must include an MDISK definition in MWV mode for access to the partial pack minidisk (defined as a full pack) or a LINK definition in MW mode to the partial (defined as full) minidisk's MDISK definition in MWV mode.

The system directory for the guest machine on the can include an MDISK definition in MWV mode for access to the partial pack minidisk (defined as a full pack), as long as you did not define another MWV MDISK statement, or a LINK definition in MW mode to the partial (defined as full) minidisk's MDISK definition in MWV mode. You can define more than one guest machine.

The system directory for the CA ACF2 for z/VM service machine on another processor must include an MDISK definition in MWV mode for access to the partial pack minidisk or a LINK definition in MW mode to the partial minidisk's MDISK definition in MWV mode.

The system directory for the guest machine (if there is one) on the other processor can include an MDISK definition in MWV mode for access to the partial pack minidisk (as long as you did not define another MWV MDISK statement) or a LINK definition in MW mode to the partial minidisk's MDISK definition in MWV mode. You can define more than one guest machine.

You must generate the real DASD as SHARED in the HCPRIO definition for the device.

The following directory entries illustrate a possible scenario for sharing CA ACF2 for z/VM databases with a guest machine and another processor on a partial‑pack minidisk:
```
USER ACF2VMEA . . .
```
```
  ...
```
```
MDISK 300 3380 000 885 VSMPCK MWV
```
```
  ...
```
```
USER GUESTVM
```
```
  ...
```
```
LINK ACF2VMEA 300 300 MW
```

Proceed to Step 2: Modify the Service Machine ACFSTART EXEC after you modify the user directory and HCPRIO.

Step 2: Modify the Service Machine ACFSTART EXEC

Modify the service machine ACFSTART EXEC to include ACCESS and DLBL statements for the VSAM files.


   'ACCESS 300 V'            /* access vsam database disk      */

/* The VSAM DSN's on the DLBL statements below should be changed
   to reflect the actual DSN's of your VSAM CATALOG & datasets  */

   'DLBL IJSYSCT V DSN CATALOG MASTER'
   'DLBL RULES V DSN VMVSAM.ACF.RULES (VSAM'
   'DLBL LID V DSN VMVSAM.ACF.LOGONIDS (VSAM'
   'DLBL INFO V DSN VMVSAM.ACF.INFOSTG (VSAM'

Step 3: Modify, Assemble, and Reload the ACFFDR

To define the database groups, modify the @DDSN macro of the ACFFDR. You can define up to 16 database groups. See the Administrator Guide for complete instructions.


@DDSN
  PRIMARY,                    ** PRIMARY GROUP
  RULE='RULES',               ** CMS RULES CLUSTER
  LID='SYS1.ACF.LOGONIDS',    ** VSAM LOGONID CLUSTER
  INFO='INFO'                 ** CMS GEN RESOURCE CLSTR

Assemble the ACFFDR. After moving the ACFFDR to the service machine 193 disk, issue the following CP command to reload the new version into storage:

ACFSERVE RELOAD FDR

See the Administrator Guide for more information about ACFSERVE commands.

Step 4: Merge the Databases Using the ACFDBVSM Utility

Use the ACFDBVSM utility to merge the CMS databases into VSAM databases. To perform the merge with the ACFDBVSM EXEC, see the Report and Utilities Guide for more information.