03.03.2015 Views

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Tape File Management Utilities<br />

Message paths are accessed by the system using direct physical IOCS and<br />

should be defined as SD files <strong>for</strong> label purposes. It is recommended that you<br />

locate MACC queue files on physical disk volumes other than those that<br />

contain the Catalog or Audit Trail data sets.<br />

Initializing Multi:ACCESS Queue Files<br />

Use the MACC INITIAL command of the DYN<strong>CA</strong>T utility program:<br />

MACC INITIAL DDNAME=DYN2<strong>CA</strong>1<br />

The DDNAME must be one of the PATHID values specified in the DTPATH<br />

option record.<br />

Execute the MACC INITIAL command once <strong>for</strong> each unique PATHID specified in<br />

the DTPATH option record. When DYN<strong>CA</strong>T has completed processing, the<br />

message paths will be ready <strong>for</strong> use.<br />

Note: If any of the participating systems run MVS, the MACC queue files<br />

should be allocated on MVS to ensure inclusion in the MVS Master Catalog.<br />

Per<strong>for</strong>ming Catalog Synchronization<br />

Catalog synchronization is a process by which a catalog on one system is<br />

updated with in<strong>for</strong>mation extracted from another system, so that both systems<br />

maintain the same volume status in<strong>for</strong>mation.<br />

An extract facility is supplied with each system to convert tape database<br />

in<strong>for</strong>mation into a common <strong>for</strong>mat so that it can be compared to determine if<br />

any discrepancies exist between the two systems. Volumes from each system<br />

are marked as either in active or scratch status.<br />

The synchronization facilities accept the extracts from each system as input<br />

and per<strong>for</strong>m the analysis. All discrepancies are indicated on an exception<br />

report, and the in<strong>for</strong>mation needed to resolve the discrepancies is written to<br />

two distinct update files, one <strong>for</strong> each system.<br />

Each system also provides a product-specific update utility used to apply<br />

synchronization in<strong>for</strong>mation to its respective database. Any updates that<br />

cannot be per<strong>for</strong>med are detailed in error reports. These errors may require<br />

additional research and manual correction.<br />

Chapter 3: Supporting Tape File Management 3–17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!