Provided by: libpcp3-dev_3.5.11_amd64 bug


       pmNameInDom,  pmRequestInDomName,  pmReceiveInDomName  -  translate an instance identifier
       into an instance name


       #include <pcp/pmapi.h>

       int pmNameInDom(pmInDom indom, int inst, char **name);
       int pmRequestInDomName(int ctx, pmInDom indom, int inst);
       int pmReceiveInDomName(int ctx, char **name);

       cc ... -lpcp


       For the instance domain indom, in the current Performance Metrics Application  Programming
       Interface (PMAPI) context, locate the instance with the internal instance identifier given
       by inst, and return the full external instance identification via name.

       The value for the instance domain indom is typically extracted from  a  pmDesc  structure,
       following a call to pmLookupDesc(3) for a particular performance metric.

       The  space  for the value of name will have been allocated in pmNameInDom with malloc(3C),
       and it is the responsibility of the caller to free(3C) the space  when  it  is  no  longer

       pmNameInDom returns zero on success.

       pmRequestInDomName  and pmReceiveInDomName are used by applications which must communicate
       with the PMCD asynchornously.  These functions take explicit context handle ctx which must
       refer  to  a  host  context  (i.e.  created  by  passing PM_CONTEXT_HOST to pmNewContext).
       pmRequestInDomName sends request to translate internal  instance  identifier  to  external
       instance  name  to  PMCD and returns immediately, pmReceiveInDomName reads reply from PMCD
       without waiting, it is the responsibility of the application to make  sure  the  data  are
       ready before calling pmReceiveInDomName.


       PMAPI(3),    pmGetConfig(3),   pmGetInDom(3),   pmLookupInDom(3),   pmNameInDomArchive(3),
       pcp.conf(4) and pcp.env(4).


              indom is not a valid instance domain identifier

              The instance identifier inst is not known for the  instance  domain  indom  in  the
              current PMAPI context

              Context is currently in use by another asynchronous call