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 [-adfv] 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 forces the removal of
74 outfile (if it exists), before the check is made.
75 The -d option allows the resultant PMNS to optionally contain duplicate
77 PMIDs with different names in the PMNS. By default this condition is
78 considered an error.
79 The -v option produces one line of diagnostic output as each infile is
81 processed.
82 Once all of the merging has been completed, pmnsmerge will attempt to
84 compile the resultant namespace using pmnscomp(1) - if this fails for
85 any reason, outfile will still be created, but pmnsmerge will report
86 the problem and exit with non-zero status.
87
89 Once the writing of the new outfile file has begun, the signals SIGINT,
90 SIGHUP and SIGTERM will be ignored to protect the integrity of the new
91 file.
92
94 Environment variables with the prefix PCP_ are used to parameterize the
95 file and directory names used by PCP. On each installation, the file
96 /etc/pcp.conf contains the local values for these variables. The
97 $PCP_CONF variable may be used to specify an alternative configuration
98 file, as described in pcp.conf(4).
99
101 pmnsadd(1), pmnscomp(1), pmnsdel(1), pcp.conf(4), pcp.env(4) and
102 pmns(4).
103Performance Co-Pilot SGI PMNSMERGE(1)