The AUTOSTAT function creates a Snapshot of selected MUFs with their active tasks.
This function opens the AutoStatus database in the repository MUF using the standard DBSIDPR connection and then calls an internal API to collect information about the tasks running on one or more target MUFs in this same LPAR. The repository MUF can also be a target MUF.
To execute AutoStatus, the repository MUF must be at CA Datacom/DB Version 14.0. AutoStatus allows a target MUF to be CA Datacom/DB r11 or greater.
The AutoStatus database is installed as part of a new install or upgrade. The default database ID is 1018. If you decide to change the AutoStatus database to a different DBID, we recommend that the database be left as 1018.
The process allows a single Snapshot to collect information about 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 record recorded by this Snapshot (S_MUF_DATETIME).
For more information about how to implement and use AutoStatus, see the AutoScope User Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|