Structure of DDS requests

To request performance data in a z/OS environment, an application must send an HTTP request to the DDS server located on the monitored z/OS sysplex.

To request cross platform performance data from distributed platforms, the HTTP request must be sent to the DDS server with the monitored AIX®, Linux or Windows system defined in its configuration file.

Topic Description and purpose of parameters first explains the set of request parameters, used in the various request types. Then, How to specify different types of requests presents detailed information about the purpose of the request types and how to specify them.

Here is an example request for a certain performance metric for a specified resource: it requests the response time (denoted by the metric ID 8D10F0) of volume SYSLIB of system SYSA:

http://ddshost:8803/gpm/perform.xml?resource=SYSA,SYSLIB,VOLUME&id=8D10F0

An example request for the Postprocessor CPU and CRYPTO reports looks similar to the following:

http://ddshost:8803/gpm/rmfpp.xml?reports=CPU,CRYPTO&date=20090801,20090804

http://<ddshost>:<ddsport>/gpm/<filename>?<parm_1>=<value_1>&…&<parm_n>=<value_n>

The parameters have the following meanings:

ddshost

is the IP address or the symbolic name of the DDS server.

Example:

ddshost

ddsport

is the port number of the DDS server (GPMSERVE or GPM4CIM).

Example:

8803

filename

is the filename of the XML document you want to retrieve, followed by the extension .xml. It determines the request type and the returned XML document type. The valid filenames are described in How to specify different types of requests.

Examples:

perform.xml
rmfpp.xml

<parm_1>=<value_1>&…&<parm_n>=<value_n>

is the query string within the request. It is composed of multiple parameter/value pairs, separated by & characters, that precisely specify the requested information. Available parameters are described in Description and purpose of parameters.