Overview

The Universal Query (UQUERY) utility queries any Universal Broker for Broker-related and active component-related information.

Usage

UQUERY returns information for a Universal Broker that is installed on the host, as specified by configuration options on the command line or in a configuration file. Information regarding the components managed by a particular Broker also can be requested.

UQUERY registers with a locally running Universal Broker. Consequentially, a Universal Broker must be running in order for a UQUERY to execute.

Network Alias Look-Up

When a Linux/Unix or Windows task that uses the Agent Cluster Distribution type Network Alias is launched, the task first will confirm if a non-expired cached Universal Agent name is available, and if so, this name will be used.

If the name is not available, a UQUERY look-up will be performed and the returned IP address will be used to look up the required Universal Agent name to be used for the task. The name will be cached based upon the Agent Cluster cache retention definition. If no active or registered Agent is found, the task will enter a status of Undeliverable and the UQUERY look-up will be retried after a period (in minutes) specified by the Agent Cluster Network Alias Retry Interval.

Examples

For an example of Universal Query output, and examples of how to run Universal Query, see Examples of Querying for Job Status and Activity.

Detailed Information

The following pages provide detailed information for Universal Query:

Universal Query Examples

See Monitoring and Alerting for examples of how to use Universal Query.

Browser not supported