# Compaq ACMS for OpenVMS
Remote Systems Management Guide

Previous | Contents | Index

ACMS processes read the Collection table during process startup to determine which classes to begin collecting. Once the Remote Manager has been started, the ACMSMGR SHOW PROCESS command can be used to determine the class states for the currently running ACMS processes.

In order for collection data to be written to a snapshot file, the following conditions must be met:

- A qualifying entity must be running (one with an entity type and name matching fields in the Collection table).
- The collection state and storage state for that entity must be enabled.
- The current time must fall between the storage start time and storage end time.

If all these conditions are met, the Remote Manager opens the snapshot file for shared write operations. The file remains open until the storage state is set to DISABLED or until the snapshot period expires.

When multiple collection records apply to a given process, the records are assigned weights according to a precedence of name, then entity, and then class. Within a column, wildcard entries are weighted less than nonwildcard entries. The row with the highest weight that applies to a process is used. The command ACMSMGR SHOW COLLECTION displays weights for each row in the table. See Section 5.1.1 for a discussion of the Collection table and how weights are assigned.

In contrast to typical collections, weighting for data snapshot threads does not apply. Therefore, it is possible for redundant collection data to be written to one or more snapshot files. If multiple collection records compile overlapping data, and each has their storage state set to ENABLED, each record writes data to the designated snapshot file.

## Example

    $  ACMSMGR ADD COLL/ENT=EXC/CLASS=RUNTIME/NAME=VR_APPL/COLL_STATE=ENABLED

> This command creates an entry in the Collection table. As a result of this command, the EXC entity for VR_APPL will begin collecting run-time information; however this data will not be saved and written to the data snapshot file.

# 11.3 ACMSMGR ADD FILTER++

Adds records to the Remote Manager Error Filter table.

## Format

> ### ACMSMGR ADD FILTER [/qualifiers]

> Command Qualifier | Default
> --- | ---
> /CODE=value | None.
> /FILE=file-name | None.
> /NAME=error-name | None.
> /NODE=node-name | Translation of logical ACMS$MGMT_SERVER_NODE
> /USER=user-name | Translation of logical ACMS$MGMT_USER

## Privileges Required

> ACMS$MGMT_WRITE

## Parameters

> None.

## Qualifiers

> ### /CODE=value

> This qualifier specifies the decimal or hexadecimal value (such as, %x5258028) related to the error message being filtered.

> ### /FILE=file-name

> This qualifier specifies the name of an input file that contains a list of error filter values. The Remote Manager reads this file and adds each code or symbolic name to the Error Filter table.

> ### /NAME=error-name

> This qualifier specifies the symbolic name (such as, %ACMSACC-W-TCS_LOADING) related to the error message being filtered.

> ### /NODE=node-name

> This qualifier specifies a fully- or partially-qualified TCP/IP host name. This name must match the current DECnet host name. IP addresses and host names (or aliases) that exceed six characters or include mixed case are not allowed. For more information on TCP/IP host names and defining aliases, see Section 2.2.1.

> To execute the command on more than one node, you can specify the node names in a comma-separated list. The ACMSMGR utility attempts to perform the operation sequentially on each node in the list.

> If the /NODE qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_SERVER_NODE. If the logical is defined, the value of the logical is used by default.

> In order for the command to execute, either the /NODE qualifier must be provided on the command line, or the ACMS$MGMT_SERVER_NODE logical must be defined.

> ### /USER=user-name

> This qualifier specifies the name of the OpenVMS account on the server node to be used for authorization. If this qualifier is specified, an explicit login must already have been completed successfully (see Section 11.9).

> If the /USER qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_USER. If the logical is defined, the value of the logical is used by default.

> If the /USER qualifier is not specified and the ACMS$MGMT_USER logical is not defined, the ACMSMGR utility attempts proxy access. See Section 4.4.1.2 for a discussion of proxy access.

## Notes

> When adding new error filter records, you must specify either the /CODE, /NAME, or /FILE qualifier.

> ACMS processes read the Error Filter table during process startup to determine which errors to refrain from sending to the Remote Manager server. Error filtering begins or ends immediately after filter records are added. The Remote Manager signals the appropriate ACMS process as soon as it has reevaluated the Error Filter table following an addition. Messages are sent to active ACMS processes using the ACMS Trace Monitor.

> Certain system messages, such as event flags (ACMSACC-I-EVENT), often spawn further status messages indicating the cause of the event (ACMSACC-W-FORCEOUT). Error filtering is explicit; that is, only the specified messages are suppressed. If you want to filter the initial and subsequent system messages, you must add each message to the Error Filter table. See Section 5.5 for information on working with error logs and error filtering.

> Errors are also filtered using the command SET PARAMETER/ERROR_INTERVAL=n. Any errors that are rebroadcast within the specified interval are not sent to the Remote Manager server. The command ACMSMGR SHOW PARAMETER can be used to determine the the current error interval for ACMS systems.

## Example

    $  ACMSMGR ADD FILTER /NAME="ACMSACC-W-FORCEOUT" /NODE=SPARKS

> This command adds the ACMS ACC force out warning message to the Error Filter table. If this message is generated by an ACMS process on node SPARKS, it is not relayed to the Remote Manager.

    $  ACMSMGR ADD FILTER /FILE=DISK$1:[USER1]FILTER_ERR.DAT

> This command adds all the system messages in the file FILTER_ERR.DAT to the Error Filter table. These messages are no longer relayed to the Remote Manager.

Note #### ++ This command (and its qualifiers) is only for use with systems running ACMS Version 4.4 or higher.

# 11.4 ACMSMGR ADD TRAP

Adds records to the Remote Manager Trap table.

## Format

> ### ACMSMGR ADD TRAP [/qualifiers]

> Command Qualifier | Default
> --- | ---
> /ENTITY=[*,entity-name] | Qualifier is required.
> /NAME=[*,entity-name] | * (all)
> /NODE=node-name | Translation of logical ACMS$MGMT_SERVER_NODE
> /PARAMETER=keyword | EXISTS
> /SEVERITY=[I,W,E,F] | E
> /TRAP_MIN=value | -1
> /TRAP_MAX=value | -1
> /USER=user-name | Translation of logical ACMS$MGMT_USER

## Privileges Required

> ACMS$MGMT_OPER

## Parameters

> None.

## Qualifiers

> ### /ENTITY=[*, ACC, CP, EXC, MGR, QTI, TSC]

> This required qualifier specifies the entity or entities for which a trap should be set.

> ### /NAME=[*, entity-name]

> This qualifier specifies particular instances of an entity. Wildcards (*) are allowed in names.

> This field is ignored for the MGR entity.

> For ACC, CP, QTI, and TSC entity types, the entity name is the process name. For the EXC entity type, the entity name is the name of the application (for example, VR_APPL).

> The default is all (*).

> ### /NODE=node-name

> This qualifier specifies a fully- or partially-qualified TCP/IP host name. This name must match the current DECnet host name. IP addresses and host names (or aliases) that exceed six characters or include mixed case are not allowed. For more information on TCP/IP host names and defining aliases, see Section 2.2.1.

> If the /NODE qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_SERVER_NODE. If the logical is defined, the value of the logical is used by default.

> In order for the command to execute, either the /NODE qualifier must be provided on the command line, or the ACMS$MGMT_SERVER_NODE logical must be defined.

> ### /PARAMETER=[EVENT_SEVERITY, EXISTS]

> This parameter specifies the field that should be monitored.
> - EVENT_SEVERITY
>   Internal Remote Manager events are to be monitored. The Remote Manager logs internal events in the Remote Manager log. (See Section 4.7 and Section 11.33 for discussions of the Remote Manager log.) Traps can be generated based on the severity levels of these events.
> - EXISTS
>   Process existence is to be monitored. Traps are generated if the associated entity type and name either starts or stops.

> ### /SEVERITY=[I, W, E, F]

> This qualifier specifies the severity to be associated with the trap. Severity codes are embedded in the trap message and must be parsed by the trap receiver. Severities are informational (I), warning (W), error (E), or fatal (F).

> ### /TRAP_MIN=value

> This qualifier specifies the minimum allowable value for the parameter being monitored. A trap is generated if the parameter value is less than the minimum. See Section 9.13.2 for a list of valid values.

> ### /TRAP_MAX=value

> This qualifier specifies the maximum allowable value for the parameter being monitored. A trap is generated if the parameter value is greater than the maximum. See Section 9.13.2 for a list of valid values.

> ### /USER=user-name

> This qualifier specifies the name of the OpenVMS account on the server node to be used for authorization. If this qualifier is specified, an explicit login must already have been completed successfully (see Section 11.9).

> If the /USER qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_USER. If the logical is defined, the value of the logical is used by default.

> If the /USER qualifier is not specified and the ACMS$MGMT_USER logical is not defined, the ACMSMGR utility attempts proxy access. See Section 4.4.1.2 for a discussion of proxy access.

## Notes

> When adding new trap records, the combination of entity, name, and parameter must be unique.

> Traps become active as soon as they are added to the Trap table and the SNMP interface is running.

> See Section 9.13.2 for a discussion about setting appropriate trap minimums and maximums. See also Section 9.13.3 for a description of the trap message generated.

## Example

    $  ACMSMGR ADD TRAP /ENT=ACC/PARAMETER=EXISTS/TRAP_MIN=1

> This command causes an SNMP trap to be generated whenever the ACC process stops if the SNMP interface is running.

# 11.5 ACMSMGR DELETE COLLECTION

Deletes records from the Collection table.

## Format

> ### ACMSMGR DELETE COLLECTION [/qualifiers]

> Command Qualifier | Default
> --- | ---
> /CLASS=class-name | * (all)
> /ENTITY=[*,entity-name] | Qualifier is required.
> /NAME=[*,entity-name] | * (all)
> /NODE=node-name | Translation of logical ACMS$MGMT_SERVER_NODE
> /USER=user-name | Translation of logical ACMS$MGMT_USER

## Privileges Required

> ACMS$MGMT_WRITE

## Parameters

> None.

## Qualifiers

> ### /CLASS=[*, CONFIG, ERROR, ID, POOL, RUNTIME]

> This qualifier specifies the class to be enabled or disabled. The default is * (all). See Section 5.1.1 for a description of each class type.

> ### /ENTITY=[*, ACC, CP, EXC, GROUP, QTI, SERVER, TSC]

> This required qualifier specifies the entity or entities for which collection should be enabled or disabled.

> ### /NAME=[*, entity-name]

> This qualifier specifies particular instances of an entity. Wildcards (*) are allowed in names.

> For ACC, CP, QTI, and TSC entity types, the entity name is the process name. For the EXC entity type, the entity name is the name of the application (for example, VR_APPL).

> Server and task group names can be specified as compound names made up of an application name and a server or task group name, separated by a period (for example, VR_APPL.VR_READ_SERVER). Either part of server or task group names can be a wildcard (for example, *.VR_READ_SERVER or VR_APPL.*). If only one part of a server or task group name is specified, it is assumed to be the application name, and the server or task group name is wildcarded. For example, VR_APPL is equivalent to VR_APPL.*.

> The default is all (*), which is equivalent to *.* for a compound name.

> ### /NODE=node-name

> This qualifier specifies a fully- or partially-qualified TCP/IP host name. This name must match the current DECnet host name. IP addresses and host names (or aliases) that exceed six characters or include mixed case are not allowed. For more information on TCP/IP host names and defining aliases, see Section 2.2.1.

> If the /NODE qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_SERVER_NODE. If the logical is defined, the value of the logical is used by default.

> In order for the command to execute, either the /NODE qualifier must be provided on the command line, or the ACMS$MGMT_SERVER_NODE logical must be defined.

> ### /USER=user-name

> This qualifier specifies the name of the OpenVMS account on the server node to be used for authorization. If this qualifier is specified, an explicit login must already have been completed successfully (see Section 11.9).

> If the /USER qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_USER. If the logical is defined, the value of the logical is used by default.

> If the /USER qualifier is not specified and the ACMS$MGMT_USER logical is not defined, the ACMSMGR utility attempts proxy access. See Section 4.4.1.2 for a discussion of proxy access.

## Notes

> When deleting collection records, the combination of class, entity, and name must exactly match the row to be deleted. Deleting a collection record automatically terminates all related snapshot threads.

> It is not possible to delete records for the ID and CONFIG class. By default, all ACMS processes collect ID and CONFIG class data.

> Collections begin or end immediately after collection records are deleted. The Remote Manager signals the appropriate ACMS process as soon as it has reevaluated the Collection table following a deletion. Messages are sent to the ACMS process using the ACMS Trace Monitor.

> ACMS processes read the Collection table during process startup to determine which classes to begin collecting.

> The ACMSMGR SHOW PROCESS command can be used to determine the class states for the currently running ACMS processes.

## Example

    $  ACMSMGR DELETE COLL/ENT=EXC/CLASS=RUNTIME/NAME=VR_APPL

> This command deletes the entry in the Collection table for run-time collection by the VR_APPL application. After the deletion, if there are no other Collection table entries that apply to the run-time class for VR_APPL, run-time collection is disabled.

# 11.6 ACMSMGR DELETE FILTER++

Removes records from the Remote Manager Error Filter table.

## Format

> ### ACMSMGR DELETE FILTER [/qualifiers]

> Command Qualifier | Default
> --- | ---
> /CODE=value | None.
> /NAME=error-name | None.
> /NODE=node-name | Translation of logical ACMS$MGMT_SERVER_NODE
> /USER=user-name | Translation of logical ACMS$MGMT_USER

## Privileges Required

> ACMS$MGMT_WRITE

## Parameters

> None.

## Qualifiers

> ### /CODE=value

> This qualifier specifies the hexadecimal value (such as, %x5258028) related to the error message being filtered.

> ### /NAME=error-name

> This required qualifier specifies the symbolic name (such as, %ACMSACC-W-TCS_LOADING) related to the error message being filtered.

> ### /NODE=node-name

> This qualifier specifies a fully- or partially-qualified TCP/IP host name. This name must match the current DECnet host name. IP addresses and host names (or aliases) that exceed six characters or include mixed case are not allowed. For more information on TCP/IP host names and defining aliases, see Section 2.2.1.

> If the /NODE qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_SERVER_NODE. If the logical is defined, the value of the logical is used by default.

> In order for the command to execute, either the /NODE qualifier must be provided on the command line, or the ACMS$MGMT_SERVER_NODE logical must be defined.

> ### /USER=user-name

> This qualifier specifies the name of the OpenVMS account on the server node to be used for authorization. If this qualifier is specified, an explicit login must already have been completed successfully (see Section 11.9).

> If the /USER qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_USER. If the logical is defined, the value of the logical is used by default.

> If the /USER qualifier is not specified and the ACMS$MGMT_USER logical is not defined, the ACMSMGR utility attempts proxy access. See Section 4.4.1.2 for a discussion of proxy access.

## Notes

> Either the /CODE or /NAME qualifier must be specified. When deleting error filter records, the combination of code (or name) and node must exactly match the row to be deleted.

> ACMS processes read the Error Filter table during process startup to determine which errors to refrain from sending to the Remote Manager server. Error filtering ends immediately after filter records are deleted. The Remote Manager signals the appropriate ACMS process as soon as it has reevaluated the Error Filter table following a deletion. Messages are sent to active ACMS processes using the ACMS Trace Monitor.

> Errors are also filtered using the command SET PARAMETER/ERROR_INTERVAL=n. Any errors that are rebroadcast within the specified interval are not sent to the Remote Manager server. The command ACMSMGR SHOW PARAMETER can be used to determine the the current error interval for ACMS systems.

> See Section 5.5 for information on working with error logs and error filtering.

## Example

    $  ACMSMGR DELETE FILTER /NAME="ACMSACC-W-FORCEOUT" /NODE=SPARKS

> This command deletes the ACMS ACC force out warning message from the Error Filter table. If this message is generated by an ACMS process on node SPARKS, it is relayed to the Remote Manager and written to the error log.

Note #### ++ This command (and its qualifiers) is only for use with systems running ACMS Version 4.4 or higher.

# 11.7 ACMSMGR DELETE TRAP

Deletes a record from the trap table.

## Format

> ### ACMSMGR DELETE TRAP [/qualifiers]

> Command Qualifier | Default
> --- | ---
> /ENTITY=[*,entity-name] | Qualifier is required.
> /NAME=[*,entity-name] | * (all)
> /NODE=node-name | Translation of logical ACMS$MGMT_SERVER_NODE
> /PARAMETER=keyword | EXISTS
> /USER=user-name | Translation of logical ACMS$MGMT_USER

## Privileges Required

> ACMS$MGMT_OPER

## Parameters

> None.

## Qualifiers

> ### /ENTITY=[*, ACC, CP, EXC, MGR, QTI, TSC]

> This required qualifier specifies the entity or entities for which a trap should be set.

> ### /NAME=[*, entity-name]

> This qualifier specifies particular instances of an entity. Wildcards (*) are allowed in names.

> For the MGR entity, this field should always be set to asterisk (*).

> For ACC, CP, QTI, and TSC entity types, the entity name is the process name. For the EXC entity type, the entity name is the name of the application (for example, VR_APPL).

> The default is all (*).

> ### /NODE=node-name

> This qualifier specifies a fully- or partially-qualified TCP/IP host name. This name must match the current DECnet host name. IP addresses and host names (or aliases) that exceed six characters or include mixed case are not allowed. For more information on TCP/IP host names and defining aliases, see Section 2.2.1.

> If the /NODE qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_SERVER_NODE. If the logical is defined, the value of the logical is used by default.

> In order for the command to execute, either the /NODE qualifier must be provided on the command line, or the ACMS$MGMT_SERVER_NODE logical must be defined.

> ### /PARAMETER=[EVENT_SEVERITY, EXISTS]

> This parameter specifies the field that should be monitored.
> - EVENT_SEVERITY
>   Internal Remote Manager events are to be monitored. The Remote Manager logs internal events in the Remote Manager log. (See Section 11.33 and Section 4.7 for discussions of the Remote Manager log.) Traps can be generated based on the severity levels of these events.
> - EXISTS
>   Process existence is to be monitored. Traps are generated if the associated entity type and name either starts or stops.

> ### /USER=user-name

> This qualifier specifies the name of the OpenVMS account on the server node to be used for authorization. If this qualifier is specified, an explicit login must already have been completed successfully (see Section 11.9).

> If the /USER qualifier is not specified, the ACMSMGR utility checks for the presence of the logical name ACMS$MGMT_USER. If the logical is defined, the value of the logical is used by default.

> If the /USER qualifier is not specified and the ACMS$MGMT_USER logical is not defined, the ACMSMGR utility attempts proxy access. See Section 4.4.1.2 for a discussion of proxy access.

## Notes

> When deleting trap records, the combination of entity, name and parameter must exactly match a row in the trap table.

> Traps become deactive as soon as they are deleted from the Trap table.

## Example

    $  ACMSMGR DELETE TRAP/ENT=ACC/PARAM=EXISTS

> This command deletes a trap from the Trap table.

Previous | Next | Contents | Index