1PMNSMERGE(1) General Commands Manual PMNSMERGE(1)
2
6 pmnsmerge - merge multiple versions of a Performance Co-Pilot PMNS
7
9 $PCP_BINADM_DIR/pmnsmerge [-adfxv] infile [...] outfile
10
12 pmnsmerge merges multiple instances of a Performance Metrics Name Space
13 (PMNS), as used by the components of the Performance Co-Pilot (PCP).
14 Each infile argument names a file that includes the root of a PMNS, of
16 the form
17 root {
19 /* arbitrary stuff */
20 }
21 The order in which the infile files are processed is determined by the
23 presence or absence of embedded control lines of the form #define
24 _DATESTAMP YYYYMMDD
25 Files without a control line are processed first and in the order they
27 appear on the command line. The other files are then processed in
28 order of ascending _DATESTAMP.
29 The -a option suppresses the argument re-ordering and processes all
31 files in the order they appear on the command line.
32 The merging proceeds by matching names in PMNS, only those new names in
34 each PMNS are considered, and these are added after any existing met‐
35 rics with the longest possible matching prefix in their names. For
36 example, merging these two input PMNS
37 root { root {
39 surprise 1:1:3
40 mine 1:1:1 mine 1:1:1
41 foo foo
42 yawn
43 yours 1:1:2
44 } }
45 foo { foo {
46 fumble 1:2:1
47 mumble 1:2:3
48 stumble 1:2:2 stumble 1:2:2
49 } }
50 yawn {
51 sleepy 1:3:1
52 }
53 Produces the resulting PMNS in out.
55 root {
57 mine 1:1:1
58 foo
59 yours 1:1:2
60 surprise 1:1:3
61 yawn
62 }
63 foo {
64 fumble 1:2:1
65 stumble 1:2:2
66 mumble 1:2:3
67 }
68 yawn {
69 sleepy 1:3:1
70 }
71 To avoid accidental over-writing of PMNS files, outfile is expected to
73 not exist when pmnsmerge starts. The -f option allows an existing out‐
74 file to be unlinked (if possible) and truncated before writing starts.
75 Normally duplicate names for the same Performance Metric Identifier
77 (PMID) in a PMNS are allowed. The -d option is the default option and
78 is included for backwards compatibility. The -x option reverses the
79 default and pmnsmerge will report an error and exit with a non-zero
80 status if a duplicate name is found for a PMID in any of the input PMNS
81 files or in the merged output PMNS.
82 The -v option produces one line of diagnostic output as each infile is
84 processed.
85 Once all of the merging has been completed, pmnsmerge will attempt to
87 load the resultant namespace using pmLoadASCIINameSpace(3) - if this
88 fails for any reason, outfile will still be created, but pmnsmerge will
89 report the problem and exit with non-zero status.
90 Using pmnsmerge with a single input argument allows that PMNS file to
92 be checked. In addition to syntactic checking, specifying -x will also
93 enable a check for duplicate names for all PMIDs.
94
96 The available command line options are:
97 -a Process files in command line order.
99 -d, --dupok
101 Allow duplicate metric names per PMID. This is the default.
102 -f, --force
104 Overwrite output file if it already exists.
105 -v, --verbose
107 Verbose input processing.
108 -x, --nodups
110 Do not allow duplicate metric names per PMID.
111 -?, --help
113 Display usage message and exit.
114
116 Once the writing of the new outfile file has begun, the signals SIGINT,
117 SIGHUP and SIGTERM will be ignored to protect the integrity of the new
118 file.
119
121 Environment variables with the prefix PCP_ are used to parameterize the
122 file and directory names used by PCP. On each installation, the file
123 /etc/pcp.conf contains the local values for these variables. The
124 $PCP_CONF variable may be used to specify an alternative configuration
125 file, as described in pcp.conf(5).
126
128 pmnsadd(1), pmnsdel(1), pmLoadASCIINameSpace(3), pcp.conf(5),
129 pcp.env(5) and PMNS(5).
130Performance Co-Pilot PCP PMNSMERGE(1)