PMLOOKUPINDOM(3) Library Functions Manual PMLOOKUPINDOM(3)NAME
pmLookupInDom - translate an instance name into an instance identifier
C SYNOPSIS
#include <pcp/pmapi.h>
int pmLookupInDom(pmInDom indom, const char *name);
cc ... -lpcp
DESCRIPTION
For the instance domain indom, in the current Performance Metrics Application Programming Interface (PMAPI) context, locate the instance
with the external identification given by name, and return the internal instance identifier.
Only the leading non-space characters of name will be used to identify the instance.
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.
pmLookupInDom will return a positive instance identifier on success.
SEE ALSO PMAPI(3), pmGetConfig(3), pmGetInDom(3), pmLookupDesc(3), pmLookupInDomArchive(3), pmNameInDom(3), pcp.conf(5) and pcp.env(5).
DIAGNOSTICS
PM_ERR_INDOM
indom is not a valid instance domain identifier
PM_ERR_INST
The external instance name is not known for the instance domain indom in the current PMAPI context
Performance Co-Pilot PCP PMLOOKUPINDOM(3)
Check Out this Related Man Page
PMADDPROFILE(3) Library Functions Manual PMADDPROFILE(3)NAME
pmAddProfile - add instance(s) to the current PMAPI instance profile
C SYNOPSIS
#include <pcp/pmapi.h>
int pmAddProfile(pmInDom indom, int numinst, int *instlist);
cc ... -lpcp
DESCRIPTION
The set of instances for performance metrics returned from a pmFetch(3) call may be filtered or restricted using an instance profile.
There is one instance profile for each context the application creates at the Performance Metrics Application Programming Interface
(PMAPI(3)), and each instance profile may include instances from one or more instance domains (see pmLookupDesc(3)).
pmAddProfile may be used to add new instance specifications to the instance profile of the current PMAPI context.
In the simplest variant, the list of instances identified by the instlist argument for the indom instance domain are added to the instance
profile. The list of instance identifiers contains numinst values.
The indom value would normally be extracted from a call to pmLookupDesc(3) for a particular performance metric, and the instances in
instlist would typically be determined by calls to pmGetInDom(3) or pmLookupInDom(3).
To select all instances in all instance domains, use
pmAddProfile(PM_INDOM_NULL, 0, (int *)0)
This is the only case where indom may be equal to PM_INDOM_NULL. If numinst is zero, or instlist is NULL, then all instances in indom are
selected.
SEE ALSO PMAPI(3), pmDelProfile(3), pmFetch(3), pmGetInDom(3), pmLookupDesc(3), pmLookupInDom(3), pmNewContext(3), pmUseContext(3) and pmWhichCon-
text(3).
DIAGNOSTICS
PM_ERR_PROFILESPEC
indom was PM_INDOM_NULL and instlist was not empty
CAVEAT
It is possible to add non-existent instance domains and non-existent instances to an instance profile. None of the routines that use the
instance profile will ever issue an error if you do this. The cost of checking, when checking is possible, outweighs any benefits.
Performance Co-Pilot PCP PMADDPROFILE(3)
I have a file with 3 columns. Often the first two will hold the same values and the third may differ. I only want one row for each.
i.e.
aaa,bbb,1
aaa,bbb,2
aaa,bbb,3
xxx,yyy,1
xxx,yyy,2
zzz,rrr,5
Should be
aaa,bbb,1
xxx,yyy,1
zzz,rrr,5
I just want the first instance of... (20 Replies)
Hi,
I am new registered user here in this UNIX forums.
I am a new system administrator for AIX 6.1. One of our servers performs poorly every time our application (FINACLE) runs many processes/instances. (see below for topas snapshot)
I use NMON or Topas to monitor the server utilization. I... (9 Replies)