Guardian Performance Analyzer (GPA) User Guide
Guardian Performance Analyzer (GPA) User Guide – (544541-006) Page 29 of 131 
GPA Requirements 
GPA does not have to be run on the system being analyzed; the Measure data can be 
moved to another NonStop system. 
GPA requires the use of the following NonStop system products: 
Item 
NonStop system Product Number 
Measure* 
T9086 (Version is RVU dependent) 
* Must be installed on the system being analyzed. 
GPA licensing considerations: 
GPA needs to be registered for each NonStop node that will be passing Measure data to 
GPA. The registration process provides the vehicle for getting the licensekey to activate 
your copy of GPA and is described in the README file. The delivery of the licensekey 
will normally be via email so it is important to provide an email address in the 
registration contact details capable of receiving email attachments.  
GPA allows the flexibility of running GPA on one node and processing data from another, 
but all nodes need to be registered and have a licensekey. The licensekeys can 
be installed whereby all licensekeys are stored in a single file on a single node or on 
their individual nodes.  
For example, if you want to run all your GPA processing on a non-production node (i.e. a 
Development node) using Measure data from various production nodes then this can be 
easily accomplished. The only requirement is that each production node be registered 
for GPA and their particular licensekey be installed on the Development node. 
                      [Back to TOC] 










