Use the following syntax to write this command.
┌─ , ───────────────┐ ►►─ AUTOSTAT ─▼─ MUFNAME=mufname ─┴─┬───────────────────────┬─────────────────► └─ ,DBID= ─┬─ 1018 ◄ ─┬─┘ └─ nnnn ───┘ ┌───────────────────────────────────┐ ►─┬──────────────────────────────┬─▼─┬───────────────────────────────┬─┴─────► └─ ,REPEATS= ─┬─ 0 ◄ ────────┬─┘ └─ ,SNAPEXCL= ─┬─ DURATION0 ──┬─┘ └─ 3 to 64800 ─┘ ├─ HEADER ─────┤ ├─ NOTACTIVE ──┤ ├─ REPCONNECT ─┤ └─ WARNMSG ────┘ ►─┬────────────────────────────┬─────────────────────────────────────────────►◄ └─ ,OUTTAG=cccccccccccccccc ─┘
Command
Invokes the AUTOSTAT function. Specifies to create a Snapshot of the specified MUFs with their active tasks.
Required Keyword
Identifies the MUF from which the task data is retrieved. You can repeat this parameter to include more than one MUF. Alternately, you can use a wild card character (*) to specify to select all MUFs whose names begin with the characters you specify.
The MUF name or beginning portion of a mufname with an asterisk (*)
(No default)
Optional Keywords
Specifies the database ID of the database where the Snapshot rowset is recorded.
1 to 5000
1018
Specifies a 1- to 16-character string that is used to fill in the USERTAG column on each row in the table. You can use this in various ways. For example, if you are collecting status information from multiple LPARs, you can indicate the LPAR where a given status was collected. In another case, you can process the status rows with your own program and, once a row has been read, you could place a value in the USERTAG column to indicate it has been processed.
1 to 16 characters
Blanks
Specifies whether the AutoStatus function should remain active and perform periodic Snapshots (until stopped by the user). A value of zero indicates that the function should run only once and then end. A numeric value between 3 and 64800 indicates that the function should remain active and the interval between the Snapshots will be set equal to the selected value in seconds. The interval is measured as the time from the end of one Snapshot and the beginning of the next Snapshot. You may want to set the parameter to a sufficient value, such as 600 (10 minutes), to keep the function from generating large numbers of rows in the AutoStatus database. If you are setting a repeats value, you need to set-up the appropriate job parameters to keep the system from canceling the job due to long execution times.
0 for none or from 3 to 64800
0 (Indicates that the function should not repeat)
Specifies the items to exclude.
Suppresses the creation of any detail task rows that have a DURATION of blanks. During the task inquiry, any task that has not had a given command in process for at least one second has a duration of blanks. This parameter is used to reduce the amount of detail task rows that are written to the AUTOSTAT database. With this option in place, only tasks with a command in process for a duration of one second (:01) or greater are written to the SNAPSHOT database.
Suppresses the writing of a new page header as each SYSPRINT page fills. When you want to keep the SYSPRINT to a minimum, you can use this option.
Suppresses the creation of any detail task rows that have a CURRENT_STATUS of NOTACTIVE. This parameter is used to reduce the amount of detail task rows that are written to the AUTOSTAT database.
Suppresses the open and close of the AUTOSTAT database URT for each Snapshot (see REPEATS). Specifying SNAPEXCL=REPCONNECT tells the utility to open the URT at the beginning of the AUTOSTAT function and to leave it open until the function is ended. In this mode, the AUTOSTAT function will issue a COMMIT at the end of each Snapshot process, but not close the URT.
Without the SNAPEXCL=REPCONNECT, the AUTOSTAT function disconnects from the repository MUF after each status Snapshot. Then, just prior to the next Snapshot, the function re-opens the URT and re-establishes communication to the repository MUF. This ensures that the URT does not remain open for long periods of time while the function is in a "wait" between Snapshots. When you want to limit the amount of opens and closes, and the associated messages in the repository MUF region, you should specify the SNAPEXCL=REPCONNECT option.
Note: With the SNAPEXCL=REPCONNECT option specified, you must terminate AUTOSTAT before issuing the EOJ to the repository MUF.
Suppresses the creation of warning messages when specified MUFs are not found (not active) when the status Snapshot is executed.
DURATION0, HEADER, NOTACTIVE, REPCONNECT, WARNMSG
Do not exclude
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|