[ man7.org ](../../../index.html) > Linux > [ man-pages ](../index.html) |  [ Linux/UNIX system programming training ](http://man7.org/training/)  
---|---  
  
* * *

#  pcpcompat(1) — Linux manual page

NAME  |  INTRODUCTION  |  PYTHON2  |  QT4  |  NSS  |  SAR2PCP, IOSTAT2PCP  |  PMLOGCONF-SETUP  |  PMMGR  |  PCP-COLLECTL  |  PCP-WEBAPPS  |  PMWEBD  |  SEE ALSO  |  COLOPHON   
---  
|  
      
    
    _PCPCOMPAT_(1)             General Commands Manual            _PCPCOMPAT_(1)
    

##  NAME  top

    
    
           **PCPCompat** , **pcp-collectl** , **pmmgr** , **pmwebd** - backward-compatibility
           in the Performance Co-Pilot (PCP)
    

##  INTRODUCTION  top

    
    
           The Performance Co-Pilot (PCP) is a toolkit designed for
           monitoring and managing system-level performance.  These services
           are distributed and scalable to accommodate the most complex
           system configurations and performance problems.
    
           In order to achieve these goals effectively, protocol and on-disk
           compatibility is provided between different versions of PCP.  It
           is feasible (and indeed encouraged) to use current PCP tools to
           interrogate any remote, down-rev or up-rev [pmcd(1)](../man1/pmcd.1.html) and also to
           replay any historical PCP archive (the PCP testsuite includes PCP
           archives created over 20 years ago!).
    
           From time to time the PCP developers deprecate and remove PCP
           utilities, replacing them with new versions of utilities
           providing comparable features.  This page describes replacement
           utilities for historical PCP tools.
    

##  PYTHON2  top

    
    
           PCP provides **python**(1) interfaces for the [PMAPI(3)](../man3/PMAPI.3.html) (Performance
           Metrics API), the [PMDA(3)](../man3/PMDA.3.html) API (Performance Metrics Domain
           Agents), the **mmv_stats_register**(3) API (Memory-Mapped Values) and
           PCP archive creation [LOGIMPORT(3)](../man3/LOGIMPORT.3.html) API.
    
           With **python** version 2 reaching end-of-life in 2020 we have
           deprecated the **python** version 2 interfaces in PCP (shipped, but
           no longer supported).  In the next major release of PCP (v7)
           version 2 support will be retired (completely removed).  All PCP
           APIs and **python** -based tools support **python** version 3 and have for
           several years - upgrading is strongly recommended.
    

##  QT4  top

    
    
           PCP provides optional graphical user interfaces built on the
           cross-platform Qt library, particularly [pmchart(1)](../man1/pmchart.1.html) and [pmtime(1)](../man1/pmtime.1.html).
    
           With Qt v4 reaching end-of-life in 2015 we have removed support
           for all versions before Qt v5.  In addition, some features are
           missing in early versions of Qt v5 that are now mandatory when
           building and using PCP Qt tools.  As a result the minimum
           required version of Qt for PCP v6 and beyond is now Qt 5.6.
    

##  NSS  top

    
    
           Versions of PCP before v6 used a combination of both Mozilla NSS
           (Network Security Services) and OpenSSL for the encryption
           component of the secure sockets functionality.  Starting with PCP
           v6 this has been simplified into exclusive use of OpenSSL for all
           use of encryption across PCP.  This change affects configuration
           of optional functionality in [pmcd(1)](../man1/pmcd.1.html) and [PMAPI(3)](../man3/PMAPI.3.html) client tools
           using secure sockets.
    
           The net effect of this change is that encryption is configured in
           the same ways, using the same certificates, across the HTTPS
           functionality in [pmproxy(1)](../man1/pmproxy.1.html), as well as the encrypted PCP
           protocol functionality between **pmcd** , **pm