
Sharing the DSN Catalog Multi-Partition/CPU Environments
2-68 BIM-EPIC Installation and System Guide
Multi-Partition/CPU Environments
Sharing the DSN Catalog
BIM-EPIC automatically operates in a multi-partition environment. The number of partitions
is restricted only by the VSE system. BIM-EPIC can also run in a multi-CPU environment.
The DSN Catalog can be shared among real and virtual machines, under VSE and VM/CMS.
For BIM-EPIC in any machine to share the DSN Catalog with another BIM-EPIC, or CA-
EPIC for CMS, in another machine, some VSE and BIM-EPIC features must be activated to
ensure the integrity of devices and datasets. We recommend that you share one DSN Catalog
in a multi-CPU environment, instead of creating separate DSN Catalogs. If you share the
DSN Catalog, you must also share the volumes in your disk pools.
BIM-EPIC uses IBM’s LOCK file mechanism (VSE LOCK/UNLOCK) and
RESERVE/RELEASE facilities to ensure catalog integrity between machines and operating
systems. The CMSTAPE and MULTCPU configuration options are used to enable these
facilities.
Write the configuration option changes on your worksheet. See 2-5 to ensure that the required
operating system options are contained in your VSE supervisor. The following instructions
pertain to sharing catalogs and tape drives between multiple virtual or real machines.
In BIM-EPIC for VSE... In CA-EPIC for CMS...
Specify CMSTAPE=YES On the System Options Panel:
1. Enter the DOS CATALOG specifications
2. Set ALLOW DOS/EPIC TAPES to ‘Y’
The DSN Catalog must be on a VSE disk volume (with a VSE VTOC). The DSN Catalog can
be on a minidisk. If so, its minidisk must be linked to all VSE machines that access it with the
MWV option. For best performance, we recommend that the DSN Catalog be the only dataset
on the minidisk.
Description
Sharing a DSN
Catalog Between
VSE and CMS
Kommentare zu diesen Handbüchern