pmcpp(1) [centos man page]

PMCPP(1)						      General Commands Manual							  PMCPP(1)

NAME

       pmcpp - simple preprocessor for the Performance Co-Pilot

SYNOPSIS

       pmcpp [-D name[=value] ...]  [infile]

DESCRIPTION

       pmcpp  provides a very simple pre-processor for manipulating Performance Metric Name Space (PMNS) files for the Performance Co-Pilot (PCP).
       It is most commonly used internally to process the PMNS file(s) after pmLoadNameSpace(3) or pmLoadASCIINameSpace(3) is called.

       Input lines are read from infile (or standard input if infile is not specified), processed and written to standard output.

       All C-style comments of the form /* ... */ are stripped from the input stream.

       There are no predefined macros for pmcpp although macros may be defined on the command line using the -D option, where name and value  must
       follow the same rules as described below for the #define directive.

       pmcpp accepts the following directives in the input stream (like cpp(1)):

       *  #include "filename"
	  or
	  #include <filename>
	  In  either  case  the  directory search path for filename tries filename first, then the directory for the command line infile (if any),
	  followed by the $PCP_VAR_DIR/pmns directory.	#include directives may be nested, up to a maximum depth of 5.

       *  #define name value
	  Defines a value for the macro name which must be a valid C-style name, so leading alphabetic or ``_'' followed by zero or more  alphanu-
	  merics  or  ``_''.   value  is  optional (and defaults to an empty value) but when present it may not contain white space and quoting or
	  escaping is not supported.

       *  #undef name
	  Removes the macro definition, if any, for name.

       *  #ifdef name
	  ...
	  #endif
	  or
	  #ifndef name
	  ...
	  #endif
	  The enclosing lines will be stripped or included, depending if the macro name is defined or not.

       Macro substitution is achieved by breaking the input stream into words separated by white space or one of the characters ``.'' or  ``:''  -
       this  matches  the syntax of the PMNS, see pmns(5).  Each word is checked and if it matches a macro name, the word is replaced by the macro
       value, otherwise the word is unchanged.

       There is generally one output line for each input line, although the line may be empty if the text has been stripped due to the handling of
       comments or conditional directives.  When there is a change in the input stream, an additional output line is generated of the form:

		 # line "name"

       to indicate the following line of output corresponds to line number line of the input file name.

       Important cpp(1) features that are not supported by pmcpp include:

       *  #if expr
	  ...
	  #endif

       *  Nested use of #ifdef or #ifndef.

       *  #else within an #ifdef or #ifndef.

       *  Stripping C++ style comments, as in // comment

       *  Error recovery - the first error encountered by pmcpp will be fatal.

       *  cpp(1) command line options like -U , -P and -I.

PCP ENVIRONMENT

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

SEE ALSO

       cpp(1), pmLoadASCIINameSpace(3), pmLoadNameSpace(3), pmns(5), pcp.conf(5) and pcp.env(5).

Performance Co-Pilot															  PMCPP(1)

Check Out this Related Man Page

PMNSADD(1)						      General Commands Manual							PMNSADD(1)

NAME

       pmnsadd - add new names to the Performance Co-Pilot PMNS

SYNOPSIS

       $PCP_BINADM_DIR/pmnsadd [-d] [-n namespace] file

DESCRIPTION

       pmnsmerge(1)  performs  the  same  function as pmnsadd and is faster, more robust and more flexible. It is therefore recommended that pmns-
       merge(1) be used instead.

       pmnsadd adds subtree(s) of new names into a Performance Metrics Name Space (PMNS), as used by the components of	the  Performance  Co-Pilot
       (PCP).

       Normally  pmnsadd operates on the default Performance Metrics Namespace (PMNS), however if the -n option is specified an alternative names-
       pace is used from the file namespace.

       The default PMNS is found in the file $PCP_VAR_DIR/pmns/root unless the environment variable PMNS_DEFAULT is set, in which case	the  value
       is assumed to be the pathname to the file containing the default PMNS.

       The  new names are specified in the file, arguments and conform to the syntax for PMNS specifications, see pmns(5).  There is one PMNS sub-
       tree in each file, and the base PMNS pathname to the inserted subtree is identified by the first group named in	each  file,  e.g.  if  the
       specifications begin

		 myagent.foo.stuff {
		     mumble	123:45:1
		     fumble	123:45:2
		 }

       then the new names will be added into the PMNS at the non-leaf position identified by myagent.foo.stuff, and following all other names with
       the prefix myagent.foo.

       The new names must be contained within a single subtree of the namespace.  If disjoint subtrees need to be added, these	must  be  packaged
       into separate files and pmnsadd used on each, one at a time.

       All  of	the  files  defining  the  PMNS  must  be located within the directory that contains the root of the PMNS, this would typically be
       $PCP_VAR_DIR/pmns for the default PMNS, and this would typically imply running pmnsadd as root.

       As a special case, if file contains a line that begins root { then it is assumed to be a complete PMNS that needs to be merged, so none	of
       the subtree extraction and rewriting is performed and file is handed directly to pmnsmerge(1).

       Provided  some  initial integrity checks are satisfied, pmnsadd will update the PMNS using pmnsmerge(1) - if this fails for any reason, the
       original namespace remains unchanged.

       The -d option allows the resultant PMNS to optionally contain duplicate PMIDs with different names in the PMNS.	By default this  condition
       is considered an error.

CAVEAT

       Once  the  writing  of the new namespace file has begun, the signals SIGINT, SIGHUP and SIGTERM will be ignored to protect the integrity of
       the new files.

FILES

       $PCP_VAR_DIR/pmns/root	the default PMNS, when then environment variable PMNS_DEFAULT is unset

PCP ENVIRONMENT

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

SEE ALSO

       pmnsdel(1), pmnsmerge(1), pcp.conf(5), pcp.env(5) and pmns(5).

Performance Co-Pilot							PCP								PMNSADD(1)

Linux and UNIX Man Pages

pmcpp(1) [centos man page]

Check Out this Related Man Page