1PMIPUTRESULT(3)            Library Functions Manual            PMIPUTRESULT(3)
2
3
4

NAME

6       pmiPutResult - add a data record to a LOGIMPORT archive
7

C SYNOPSIS

9       #include <pcp/pmapi.h>
10       #include <pcp/import.h>
11
12       int pmiPutResult(const pmResult *result);
13
14       cc ... -lpcp_import -lpcp
15

DESCRIPTION

17       As  part of the Performance Co-Pilot Log Import API (see LOGIMPORT(3)),
18       pmiPutResult provides an interface for  developers  familiar  with  the
19       internal PCP data structures to create output archives directly.
20
21       By  building  the pmResult data structure directly, then calling pmiPu‐
22       tResult the developer avoids calls to pmiPutValue(3) and/or  pmiPutVal‐
23       ueHandle(3)  followed  by a call to pmiWrite(3) for each record written
24       to the archive.
25
26       Any metrics and instances  appearing  in  the  result  must  have  been
27       defined by prior calls to pmiAddMetric(3) and pmiAddInstance(3).
28
29       pmiPutResult will arrange for any new metadata (metrics and/or instance
30       domain changes) covered by result to be also written  to  the  PCP  ar‐
31       chive.
32
33       Because  of the complexity of the pmResult data structure, this routine
34       is not available in the Perl interface to the LOGIMPORT services.
35

DIAGNOSTICS

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

SEE ALSO

41       LOGIMPORT(3),     PMAPI(3),     pmiAddInstance(3),     pmiAddMetric(3),
42       pmiErrStr(3), pmiPutValue(3), pmiPutText(3), pmiPutLabel(3), pmiPutVal‐
43       ueHandle(3), pmiSetTimezone(3) and pmiWrite(3).
44
45
46
47Performance Co-Pilot                                           PMIPUTRESULT(3)
Impressum