Previous Topic: Selecting a MUF as a Repository for a CollectionNext Topic: Allocating the AutoStatus Repository Database Datasets

AutoStatus Process › Selecting MUFs as a Source for Collection

Selecting MUFs as a Source for Collection

The process allows a single Snapshot to collect information from up to 100 active MUFs in the targeted LPAR.

Since AutoStatus uses the standard DBSIDPR to communicate to the repository MUF, the repository MUF can be on a different LPAR (assuming that you have the cross LPAR communication set-up in the repository MUF). For more information about setting up the repository MUF for cross LPAR access, see the section in the CA Datacom/DB Database and System Administration Guide for XCF and CCI communication.

When more than one MUF is selected as a target for an AutoStatus Snapshot, the data is collected from the target MUFs in serial fashion in alphabetic order.

For AutoStatus executions that have a significant number of MUFs, the actual process may run for a few seconds. To view all of this information as a single rowset, the same timestamp is loaded into each row created by this Snapshot execution (S_MUF_DATETIME).