pmnscomp(1)

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

NAME

6       pmnscomp  -  compile an ASCII performance metrics namespace into binary
7       format.
8

SYNOPSIS

10       pmnscomp [-d] [-f] [-n namespace] [-v version] outfile
11

DESCRIPTION

13       pmnscomp compiles a Performance Metrics Name Space (PMNS) in ASCII for‐
14       mat into a more efficient binary representation.  pmLoadNameSpace(3) is
15       able to load this binary representation significantly faster  than  the
16       equivalent ASCII representation.
17
18       If outfile already exists pmnscomp will exit without overwriting it.
19
20       By  convention,  the name of the compiled namespace is that of the root
21       file of the ASCII namespace, with .bin appended.  For example, the root
22       of  the  default  PMNS is a file named root and the compiled version of
23       the entire namespace is root.bin.
24
25       The options are;
26
27       -d   By default the PMNS to be compiled is expected to contain at  most
28            one  name  for  each  unique Performance Metric Id (PMID).  The -d
29            option relaxes this restriction and allows the  compilation  of  a
30            PMNS in which multiple names may be associated with a single PMID.
31            Duplicate names are useful when a particular metric may  be  logi‐
32            cally  associated  with more than one group of related metrics, or
33            when it is desired to create abbreviated aliases to name a set  of
34            frequently used metrics.
35
36       -f   Force overwriting of an existing outfile if it already exists.
37
38       -n   Normally  pmnscomp operates on the default PMNS, however if the -n
39            option is specified an alternative namespace is  loaded  from  the
40            file namespace.
41
42       -v   By  default, pmnscomp writes a version 0 compiled namespace, which
43            is compatible with versions of PCP before PCP2.0.  If version is 1
44            then pmnscomp will write a version 1 namespace which is compatible
45            with PCP2.0 or later.  Note that PCP version 2.0 or later can han‐
46            dle  both versions but PCP versions prior to PCP 2.0 can only han‐
47            dle version 0 compiled namespaces.
48
49       The default input PMNS is  found  in  the  file  $PCP_VAR_DIR/pmns/root
50       unless  the environment variable PMNS_DEFAULT is set, in which case the
51       value is assumed to be the pathname to the file containing the  default
52       input PMNS.
53

CAVEAT

55       Once  the  writing  of  the  new outfile has begun, the signals SIGINT,
56       SIGHUP and SIGTERM will be ignored to protect the integrity of the  new
57       file.
58

FILES

60       $PCP_VAR_DIR/pmns/*
61                 default PMNS specification files
62       $PCP_VAR_DIR/pmns/root.bin
63                 compiled  version  of  the default PMNS, when the environment
64                 variable PMNS_DEFAULT is unset
65       $PCP_VAR_DIR/pmns/stdpmid
66                 some standard macros for PMID generation
67

PCP ENVIRONMENT

69       Environment variables with the prefix PCP_ are used to parameterize the
70       file  and  directory names used by PCP.  On each installation, the file
71       /etc/pcp.conf contains the  local  values  for  these  variables.   The
72       $PCP_CONF  variable may be used to specify an alternative configuration
73       file, as described in pcp.conf(4).
74

DIAGNOSTICS

80       Cannot  open  ``xyz''  - the filename for the root of the PMNS that was
81       passed to pmLoadNameSpace(3) is bogus.
82
83       Illegal PMID - either one of the three PMID components (see pmns(4)) is
84       not  an integer, or the value for one of the components is negative, or
85       too large.
86
87       Expected ... - specific syntax errors when a particular type of lexical
88       symbol  was  expected  and  not  found; the messages are intended to be
89       self-explanatory.
90
91       Internal botch - implementation problem for the parser ...
92
93       Duplicate name ``abc'' in subtree for ``pqr.xyz'' - for  each  non-leaf
94       node, the names of all immediate descendents must be unique.
95
96       No  name  space  entry  for ``root'' - the special non-leaf node with a
97       pathname of ``root'' defines the root of  the  PMNS,  and  must  appear
98       somewhere in the PMNS specification.
99
100       Multiple  name space entries for ``root'' - more than one ``root'' node
101       does not make sense!
102
103       Disconnected subtree (``abc.xyz.def'') in name space - the pathname for
104       this  non-leaf  node  does  not correspond to any pathname in the PMNS,
105       hence this non-leaf node is ``orphaned'' in the PMNS.
106
107       Cannot find definition for non-terminal node ``xyz'' in name space -  a
108       non-terminal  node  is named as part of its parent's specification, but
109       is never defined.
110
111       Duplicate metric id (xxx) in name space for metrics ``abc'' and ``xyz''
112       - each PMID must be unique across the PMNS.
113
114
115
116Performance Co-Pilot                  SGI                          PMNSCOMP(1)