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  #define
24       _DATESTAMP YYYYMMDD
25
26       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
30       The  -a  option  suppresses  the argument re-ordering and processes all
31       files in the order they appear on the command line.
32
33       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
38                 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
54       Produces the resulting PMNS in out.
55
56                 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
72       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
76       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
83       The -v option produces one line of diagnostic output as each infile  is
84       processed.
85
86       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
91       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

CAVEAT

96       Once the writing of the new outfile file has begun, the signals SIGINT,
97       SIGHUP  and SIGTERM will be ignored to protect the integrity of the new
98       file.
99

PCP ENVIRONMENT

101       Environment variables with the prefix PCP_ are used to parameterize the
102       file  and  directory names used by PCP.  On each installation, the file
103       /etc/pcp.conf contains the  local  values  for  these  variables.   The
104       $PCP_CONF  variable may be used to specify an alternative configuration
105       file, as described in pcp.conf(5).
106

SEE ALSO

108       pmnsadd(1),    pmnsdel(1),    pmLoadASCIINameSpace(3),     pcp.conf(5),
109       pcp.env(5) and pmns(5).
110
111
112
113Performance Co-Pilot                  PCP                         PMNSMERGE(1)
Impressum