AUTOCOLL (Collect and Manage Snapshots)

The AutoCollect functions record information in Snapshots of selected Dynamic System Tables. These Snapshots are recorded in a permanent database so you can run reports and analyze the results.

The SNAPSHOT function of AUTOCOLL (and AUTOSTAT) is unique in the ability to communicate to two MUFs at the same time. When the SNAPSHOT executes, it uses an internal communication path to connect to the MUF that is the source of the Snapshot. This connection requires that the Snapshot must be executed on the same LPAR as the source MUF. For the Snapshot to store its collected data, the Snapshot connects to the repository MUF using the standard DBSIDPR connection path. This connection path supports the standard pathways such as SVC, XCF, and CCI. When executing a SNAPSHOT function, be aware of the following:

Verify that DBUTLTY is communicating with the desired repository MUF by executing DBUTLTY with the same System Identifier module (DBSIDPR) used by the MUF.
Verify proper load library concatenation by keeping the System Identifier modules (DBSIDPR) in separate load libraries.
AutoCollect does not look at or record any information about additional buffer pools specified with the MUF startup option BUFFER_POOL_DEF. That is, AutoCollect only preserves and provides feedback for the standard buffer pools. For details about the additional buffer pools, see the CA Datacom/DB Database and System Administration Guide.