1PMNSMERGE(1)                General Commands Manual               PMNSMERGE(1)
2
3
4

NAME

6       pmnsmerge - merge multiple versions of a Performance Co-Pilot PMNS
7

SYNOPSIS

9       $PCP_BINADM_DIR/pmnsmerge [-adfxv] infile [...]  outfile
10

DESCRIPTION

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
15       Each infile argument names a file that includes the root of a PMNS,  of
16       the form
17
18                 root {
19                     /* arbitrary stuff */
20                 }
21
22       The  order in which the infile files are processed is determined by the
23       presence or absence of embedded control lines of the form
24
25       #define _DATESTAMP YYYYMMDD
26
27       Files without a control line are processed first and in the order  they
28       appear  on  the  command  line.   The other files are then processed in
29       order of ascending _DATESTAMP.
30
31       The -a option suppresses the argument  re-ordering  and  processes  all
32       files in the order they appear on the command line.
33
34       The merging proceeds by matching names in PMNS, only those new names in
35       each PMNS are considered, and these are added after any  existing  met‐
36       rics  with  the  longest  possible matching prefix in their names.  For
37       example, merging these two input PMNS
38
39                 root {                    root {
40                                               surprise  1:1:3
41                     mine       1:1:1          mine      1:1:1
42                     foo                       foo
43                                               yawn
44                     yours      1:1:2
45                 }                         }
46                 foo {                     foo {
47                     fumble     1:2:1
48                                               mumble    1:2:3
49                     stumble    1:2:2          stumble   1:2:2
50                 }                         }
51                                           yawn {
52                                               sleepy    1:3:1
53                                           }
54
55       Produces the resulting PMNS in out.
56
57                 root {
58                     mine      1:1:1
59                     foo
60                     yours     1:1:2
61                     surprise  1:1:3
62                     yawn
63                 }
64                 foo {
65                     fumble    1:2:1
66                     stumble   1:2:2
67                     mumble    1:2:3
68                 }
69                 yawn {
70                     sleepy    1:3:1
71                 }
72
73       To avoid accidental over-writing of PMNS files, outfile is expected  to
74       not exist when pmnsmerge starts.  The -f option allows an existing out‐
75       file to be unlinked (if possible) and truncated before writing starts.
76
77       Normally duplicate names for the  same  Performance  Metric  Identifier
78       (PMID)  in a PMNS are allowed.  The -d option is the default option and
79       is included for backwards compatibility.  The -x  option  reverses  the
80       default  and  pmnsmerge  will  report an error and exit with a non-zero
81       status if a duplicate name is found for a PMID in any of the input PMNS
82       files or in the merged output PMNS.
83
84       The  -v option produces one line of diagnostic output as each infile is
85       processed.
86
87       Once all of the merging has been completed, pmnsmerge will  attempt  to
88       load  the  resultant  namespace using pmLoadASCIINameSpace(3) - if this
89       fails for any reason, outfile will still be created, but pmnsmerge will
90       report the problem and exit with non-zero status.
91
92       Using  pmnsmerge  with a single input argument allows that PMNS file to
93       be checked.  In addition to syntactic checking, specifying -x will also
94       enable a check for duplicate names for all PMIDs.
95

OPTIONS

97       The available command line options are:
98
99       -a   Process files in command line order.
100
101       -d, --dupok
102            Allow duplicate metric names per PMID.  This is the default.
103
104       -f, --force
105            Overwrite output file if it already exists.
106
107       -v, --verbose
108            Verbose input processing.
109
110       -x, --nodups
111            Do not allow duplicate metric names per PMID.
112
113       -?, --help
114            Display usage message and exit.
115

CAVEATS

117       Once the writing of the new outfile file has begun, the signals SIGINT,
118       SIGHUP and SIGTERM will be ignored to protect the integrity of the  new
119       file.
120

PCP ENVIRONMENT

122       Environment variables with the prefix PCP_ are used to parameterize the
123       file and directory names used by PCP.  On each installation,  the  file
124       /etc/pcp.conf  contains  the  local  values  for  these variables.  The
125       $PCP_CONF variable may be used to specify an alternative  configuration
126       file, as described in pcp.conf(5).
127

SEE ALSO

129       pmnsadd(1),     pmnsdel(1),    pmLoadASCIINameSpace(3),    pcp.conf(5),
130       pcp.env(5) and PMNS(5).
131
132
133
134Performance Co-Pilot                  PCP                         PMNSMERGE(1)
Impressum