1PMSTORE(1) General Commands Manual PMSTORE(1)
2
6 pmstore - modify performance metric values
7
9 pmstore [-h host] [-i instances] [-n pmnsfile] metricname value
10
12 Under certain circumstances, it is useful to be able to modify the val‐
13 ues of performance metrics, for example to re-initialize counters or to
14 assign new values to metrics that act as control variables.
15 pmstore changes the current values for the nominated instances of a
17 single performance metric, as identified by metricname and the list of
18 instance identifiers following the -i argument. instances must be a
19 single argument, with elements of the list separated by commas and/or
20 white space. By default all instances of metricname will be updated.
21 Normally pmstore operates on the default Performance Metrics Name Space
23 (PMNS), however if the -n option is specified an alternative namespace
24 is loaded from the file pmnsfile.
25 Unless directed to another host by the -h option, pmstore will interact
27 with the Performance Metric Collector Daemon (PMCD) on the local host.
28 The interpretation of value is dependent on the syntax used in its
30 specification and the underlying data type of metricname, as follows.
31 1. If the metric has an integer type, then value should be an optional
33 leading hyphen, followed either by decimal digits or ``0x'' and
34 some hexadecimal digits. ``0X'' is also acceptable in lieu of
35 ``0x''. See strtol(3C) and the related routines.
36 2. If the metric has a floating point type, then value should be
38 either in the form of an integer described above, or a fixed point
39 number, or a number in scientific notation. See strtod(3C).
40 3. If the metric has a string type, then value is interpreted as a
42 literal string of ASCII characters.
43 4. If the metric has an aggregate type, then an attempt is made to
45 interpret value as an integer, else a floating point number, else a
46 string. In the first two cases, the minimal word length encoding
47 is used, e.g. ``123'' would be interpreted as a 4-byte aggregate,
48 ``0x100000000'' would be interpreted as an 8-byte aggregate.
49 The output reports the old value and the new value for each updated
51 instance of the requested metric.
52
54 $PCP_VAR_DIR/pmns/*
55 default PMNS specification files
56
58 Environment variables with the prefix PCP_ are used to parameterize the
59 file and directory names used by PCP. On each installation, the file
60 /etc/pcp.conf contains the local values for these variables. The
61 $PCP_CONF variable may be used to specify an alternative configuration
62 file, as described in pcp.conf(4).
63
65 pmcd(1), pminfo(1), pmval(1), strtod(3C) and strtol(3C).
66
68 Two messages indicate a mismatch between the internal data type for
69 metricname and the value provided.
70 The value "???" is out of range for the data type (PM_TYPE_...)
72 The value "???" is incompatible with the data type (PM_TYPE_...)
74Performance Co-Pilot SGI PMSTORE(1)