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

NAME

6       pmDelProfile  - delete instance(s) from the current PMAPI instance pro‐
7       file
8

C SYNOPSIS

10       #include <pcp/pmapi.h>
11
12       int pmDelProfile(pmInDom indom, int numinst, int *instlist);
13
14       cc ... -lpcp
15

DESCRIPTION

17       The set of instances for performance metrics returned from a pmFetch(3)
18       call may be filtered or restricted using an instance profile.  There is
19       one instance profile for each context the application  creates  at  the
20       Performance Metrics Application Programming Interface (PMAPI), and each
21       instance profile may include instances from one or  more  instance  do‐
22       mains (see pmLookupDesc(3)).
23
24       pmDelProfile may be used to delete instance specifications from the in‐
25       stance profile of the current PMAPI context.
26
27       In the simplest variant, the list of instances identified  by  the  in‐
28       stlist  argument for the indom instance domain are removed from the in‐
29       stance profile.  The list of instance identifiers contains numinst val‐
30       ues.
31
32       The  indom  value  would  normally  be  extracted  from  a  call to pm‐
33       LookupDesc(3) for a particular performance metric, and the instances in
34       instlist would typically be determined by calls to pmGetInDom(3) or pm‐
35       LookupInDom(3).
36
37       If indom equals PM_INDOM_NULL and numinst is zero,  then  all  instance
38       domains  are  selected for deletion.  If instlist is NULL, then all in‐
39       stances in the selected domain(s) are removed from the profile.
40
41       To disable all  available  instances  in  all  domains,  use  pmDelPro‐
42       file(PM_INDOM_NULL,  0, NULL).  This is the only situation in which in‐
43       dom may be PM_INDOM_NULL.
44

CAVEAT

46       It is possible to delete non-existent instance domains and non-existent
47       instances  from an instance profile.  None of the routines that use the
48       instance profile will ever issue an error if you do this.  The cost  of
49       checking, when checking is possible, outweighs any benefits.
50

DIAGNOSTICS

52       PM_ERR_PROFILESPEC
53              indom was PM_INDOM_NULL and instlist was not empty
54

SEE ALSO

56       pmAddProfile(3),  PMAPI(3), pmFetch(3), pmGetInDom(3), pmLookupDesc(3),
57       pmLookupInDom(3),  pmNewContext(3),  pmUseContext(3)  and   pmWhichCon‐
58       text(3).
59
60
61
62Performance Co-Pilot                  PCP                      PMDELPROFILE(3)
Impressum