APPLMON console command
The APPLMON command initiates activity against application space information that is maintained in the application collector database.
The APPLMON command causes this information to be processed by the Automation component and logs snapshots to the space collector database.
Keywords on the APPLMON command can control the applications that are processed by the request, whether snapshots are taken to the space collector database, and whether automation activity is performed against the information.
The APPLMON command can be scheduled through the BMC AMI Storage scheduled services facility by using the SMSCHDxx PARMLIB member, or through any automated operations package. This command can be used to control the interval at which the space collector takes snapshots of application space information. This data is then available in views and through the BMC AMI Ops Infrastructure or BMC AMI Storage batch reporting facilities. The frequency with which the APPLMON command is issued determines the granularity of historical space reporting. This command also determines the frequency at which application space information is run against the AUTOAPPL solutions specified on the command.
As distributed, the SMSCHDxx member contains a service request to issue the APPLMON command once every hour; the command requests requesting both logging to the space collector database and Automation activity to check for applications over 95% full of budget.
See the following information:
Usage notes
Consider the following information when using the APPLMON command:
- The application collector must be active when the APPLMON command is issued. Otherwise the command is ignored.
- If the SVSGC component is not active, the APPLMON command will be ignored.
- If the SVSGD component is not active and historical logging is requested, the logging will not occur.
- If the SVESA component is not active and automation was requested, the automation will not occur. If at least one requested component is not active, the request is ignored.
APPLMON command keywords
The following table describes the keywords for the APPLMON command:
Keyword | Description |
|---|---|
APPL= APPLICATION= | Specifies a list of application names (defined by BMC AMI Storage) or application name masks on which to perform the APPLMON commandThe list is limited only by the space that is available on the command entry. If a mask is used, any defined application name that matches the mask value is processed by the command. Application names containing spaces must be enclosed in apostrophes.This keyword is required.Valid values are from 1 to 50 characters and should match a defined application in the application collector. |
SOL= SOLUTION= SOLUTION=(solution, solution, solution...) SOL=(solution, solution, solution...) | Specifies names of one or more AUTOAPPL solutions separated by commasYou can specify as many solution names as will fit on the command line. Any value, up to 8 characters, can be specified. Each application processed by the command is interrogated against each solution in the list. The order of the solutions does not matter, as each solution in the list is processed regardless of the result of the previous solution in the list.The solution value specified here should match the SOLUTION value specified on a SET statement in the AUTOAPPL function RLST member. The values specified here associate the APPLMON request with one or more SET statements in the AUTOAPPL RLST member. For more information, see Using BMC AMI Storage Automation. If this keyword is optional, but if it is not specified, Automation component processing is not initiated during processing of this APPLMON request. In this situation the LOG=Y keyword must be specified on the command, as either automation or logging activity must take place. |
LOG LOG=Y | N | Specifies whether snapshots of application space information should be logged to the space collector historical databaseIf not specified, LOG=N is assumed and application snapshots are not logged to the space collector database. Note: Decreasing or shortening the interval at which the APPLMON command with LOG=Y is issued increases the granularity of space collector historical reporting, at the expense of space in the space collector database. The more often the APPLMON command with LOG=Y is issued the shorter the retention period of data in the space collector database. The SPDB view can be used to determine usage of the space collector database by record type, allowing you to determine the impact of changing the granularity of this reporting. |
Examples of the APPLMON command
To run all applications through Automation solutions SOL1, SOL2, and SOL3, and then to log the application snapshots to the space collector database, use the following command:
To run selected applications through Automation solution SOL4 without logging to the space collector database, use the following command:
To take snapshots to the space collector database for selected applications, use the following command:
Because the space collector uses z/OS enclaves, you can use z/OS Workload Manager (WLM) to assign performance goals for selected work performed by the APPLMON command.