pmisettimezone(3) [centos man page]

PMISETTIMEZONE(3)					     Library Functions Manual						 PMISETTIMEZONE(3)

NAME

       pmiSetTimezone - set the source timezone for a LOGIMPORT archive

C SYNOPSIS

       #include <pcp/pmapi.h>
       #include <pcp/impl.h>
       #include <pcp/import.h>

       int pmiSetTimezone(const char *value);

       cc ... -lpcp_import -lpcp

Perl SYNOPSIS
       use PCP::LogImport;

       pmiSetTimezone($value);

DESCRIPTION

       As part of the Performance Co-Pilot Log Import API (see LOGIMPORT(3)), pmiSetTimezone sets the source timezone in the current context to be
       value.

       In the absence of a call to pmiSetTimezone the source timezone defaults to the timezone of the localhost.

DIAGNOSTICS

       pmiSetTimezone returns zero on success else a negative value that can be turned into an error message by calling pmiErrStr(3).

SEE ALSO

       LOGIMPORT(3), pmiErrStr(3), pmiSetHostname(3) and pmiStart(3).

Performance Co-Pilot														 PMISETTIMEZONE(3)

PMIPUTRESULT(3) 					     Library Functions Manual						   PMIPUTRESULT(3)

NAME

       pmiPutResult - add a data record to a LOGIMPORT archive

C SYNOPSIS

       #include <pcp/pmapi.h>
       #include <pcp/impl.h>
       #include <pcp/import.h>

       int pmiPutResult(const pmResult *result);

       cc ... -lpcp_import -lpcp

DESCRIPTION

       As  part of the Performance Co-Pilot Log Import API (see LOGIMPORT(3)), pmiPutResult provides an interface for developers familiar with the
       internal PCP data structures to create output archives directly.

       By building the pmResult data structure directly, then calling pmiPutResult the developer avoids calls to pmiPutValue(3) and/or	pmiPutVal-
       ueHandle(3) followed by a call to pmiWrite(3) for each record written to the archive.

       Any metrics and instances appearing in the result must have been defined by prior calls to pmiAddMetric(3) and pmiAddInstance(3).

       pmiPutResult will arrange for any new metadata (metrics and/or instance domain changes) covered by result to be also written to the PCP ar-
       chive.

       Because of the complexity of the pmResult data structure, this routine is not available in the Perl interface to the LOGIMPORT services.

DIAGNOSTICS

       pmiPutResult returns zero on success else a negative value that can be turned into an error message by calling pmiErrStr(3).

SEE ALSO

       LOGIMPORT(3), PMAPI(3), pmiAddInstance(3), pmiAddMetric(3), pmiErrStr(3), pmiPutValue(3), pmiPutValueHandle(3), pmiSetTimezone(3) and  pmi-
       Write(3).

Performance Co-Pilot														   PMIPUTRESULT(3)