Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmnewcontextzone(3) [centos man page]

PMNEWCONTEXTZONE(3)					     Library Functions Manual					       PMNEWCONTEXTZONE(3)

pmNewContextZone - establish a reporting timezone based on a PMAPI context C SYNOPSIS
#include <pcp/pmapi.h> int pmNewContextZone(void); cc ... -lpcp DESCRIPTION
The current reporting timezone affects the timezone used by pmCtime(3) and pmLocaltime(3). If the current PMAPI context is an archive, pmNewContextZone uses the timezone from the archive label record to set the current reporting timezone. If the current PMAPI context corresponds to a host source of metrics, pmNewContextZone executes a pmFetch(3) to retrieve the value for the metric pmcd.timezone and uses that to set the current reporting timezone. In both cases, pmNewContextZone returns a value to identify the current reporting timezone that may be used in a subsequent call to pmUse- Zone(3) to restore this reporting timezone. SEE ALSO
PMAPI(3), pmCtime(3), pmFetch(3), pmGetConfig(3), pmLocaltime(3), pmNewContext(3), pmNewZone(3), pmUseZone(3), pmWhichZone(3), pcp.conf(5), pcp.env(5) and environ(5). DIAGNOSTICS
PM_ERR_NOCONTEXT the current PMAPI context is not valid other a return value less than zero indicates a fatal error from a system call, most likely malloc(3C) Performance Co-Pilot PCP PMNEWCONTEXTZONE(3)

Check Out this Related Man Page

PMGETINDOMARCHIVE(3)					     Library Functions Manual					      PMGETINDOMARCHIVE(3)

pmGetInDomArchive - get instance identifiers for a performance metrics instance domain C SYNOPSIS
#include <pcp/pmapi.h> int pmGetInDomArchive(pmInDom indom, int **instlist, char ***namelist); cc ... -lpcp DESCRIPTION
Provided the current Performance Metrics Application Programming Interface (PMAPI) context is associated with an archive log, pmGetInDo- mArchive will scan the union of all the instance domain metadata for the instance domain indom, and return via instlist the internal instance identifiers for all instances, and via namelist the full external identifiers for all instances. This routine is a specialized version of the more general PMAPI routine pmGetInDom. The number of instances found is returned as the function value (else less than zero to indicate an error). The value for the instance domain indom is typically extracted from a pmDesc structure, following a call to pmLookupDesc(3) for a particu- lar performance metric. The resulting lists of instance identifiers (instlist and namelist), and the names that the elements of namelist point to, will have been allocated by pmGetInDomArchive with two calls to malloc(3C), and it is the responsibility of the caller to free(instlist) and free(namelist) to release the space when it is no longer required. When the result of pmGetInDomArchive is less than one, both instlist and namelist are undefined (no space will have been allocated, and so calling free(3C) is a singularly bad idea). 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). Values for these variables may be obtained programmatically using the pmGetConfig(3) function. SEE ALSO
PMAPI(3), pmGetConfig(3), pmGetInDom(3), pmLookupDesc(3), pmLookupInDomArchive(3), pmNameInDomArchive(3), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
PM_ERR_NOTARCHIVE the current PMAPI context is not associated with an archive log PM_ERR_INDOM_LOG indom is not a defined instance domain identifier for the archive log Performance Co-Pilot PCP PMGETINDOMARCHIVE(3)
Man Page

Featured Tech Videos