HP 3000 Manuals HP 3000 Manuals
HP Performance Collection Software Enhanced
by Gerry Wade
Software Technology Division
HP Performance Collection Software (PCS) is the HP 3000 part of the
LaserRX/MPE product. HP PCS is also included in the GlancePlus PAK
product.
Global Memory Fault Metrics Added
Eleven new performance metrics have been added to the Global data type to
provide more information on main memory shortages. These metrics can be
accessed using the extract program's "export" feature to copy data from
the log files into ASCII, Spreadsheet, or binary format files. To export
these new metrics, add the following metric names to your REPORT files:
TRANSIENT_FAULTS (Memory faults/second for transient
objects)
NMSTACK_FAULTS (Memory faults/second for Native Mode Stacks)
CMSTACK_FAULTS (Memory faults/second for Compatibility Mode Stacks)
NMCODE_FAULTS (Memory faults/second for Native Mode program files)
CMCODE_FAULTS (Memory faults/second for Compatibility Mode programs)
CMDATA_FAULTS (Memory faults/second for Compatibility Mode XDS)
NMLIB_FAULTS (Memory faults/second for Native Mode Libraries)
CMLIB_FAULTS (Memory faults/second for Compatibility Mode Libraries)
FILE_FAULTS (Memory faults/second for data files)
TOTAL_MEMORY_FAULTS (Memory faults/second for all object types)
MEMMGR_CLOCK_CYCLES (Number of memory manager clock cycles per hour)
POSIX Program File Names Supported
Programs that are run under the POSIX Hierarchical File System (HFS) will
have their POSIX pathname in place of the MPE program filename in the
process data type. Process names are in one of the following formats:
:commandname For MPE Command Interpreters
/dir/dir/dir/filename For POSIX processes where the pathname <= 24 bytes
...dir/dir/dir/filename For POSIX processes where the pathname > 24 bytes
file.group.account For processes in the MPE traditional directories
sh.hpbin.sys For POSIX shell processes or terminated POSIX processes
Applications can include Posix files in their definitions according to
the following rules:
* The pattern used in the FILE=, INTERACTIVE=, or BATCH= parameters
must always follow the rules for MPE files (FILE.GROUP.ACCOUNT
with MPE style wildcards accepted).
* Files in traditional MPE directories are matched as they always
have been.
* Files in POSIX directories are matched by constructing an "MPE
Style" filename as follows:
* All non-alphanumeric characters are eliminated from the
path.
* All lower case alpha are shifted to upper case.
* The first 8 characters of the filename are used as a
filename.
* The first 8 characters of the first directory are used as
the account.
* The first 8 characters of the second directory are used as
the group.
For example: The POSIX file
/usr/performance/bin/utility.and.such would translate to
UTILITYA.PERFORMA.USR.
Command Line Interface for Extract and Utility
The extract and utility programs allows commands to be entered through
the run-time ;INFO= string. Multiple commands may be entered separated
by a semicolon. For example:
:RUN UTILITY.SCOPE.SYS;INFO="SCOPE KILL"
:RUN EXTRACT.SCOPE.SYS;INFO="PROCESS KILLED;REPORT REPTFILE;EXPORT DAY-1"
Commands may also be entered in the shorter UN*X format:
UTILITY.SCOPE.SYS "-sk"
EXTRACT.SCOPE.SYS "-k -r REPTFILE -xp DAY-1"
See online help for full details.
User Selectable Summarization Interval for Exported Data
The default interval for exporting global and application summary data is
60 minutes. This default may now be changed using the SUMMARY= keyword
in your report file.
SUMMARY=15 Selects 15 minute summaries
SUMMARY=1440 Selects 1440 minute (1 day) summaries
User Selectable Missing Data Value for Exported Data
When exporting data from the log files, numeric data items that are
unavailable are normally written as zero. Unavailable metrics may be
seen when exporting application data in the multiple layout format and
when an application was not active during an interval. Global memory
fault metrics will be missing on log files collected by any version of
SCOPEXL prior to version B.nn.05. If you want to differentiate between
missing data and data with a value of zero, you may change the missing
value. Add a line similar to the following line to your report file.
MISSING=-99.99
Start and Stop Dates Can Be Set Relative to Log File Contents
The extract and utility programs can set the starting and stopping dates
based on the first and last date in an input log file. For example:
START FIRST Starts at the first date in the log file
STOP FIRST+7 Stops seven days after the first date in the log file
STOP LAST Stops at the last date in the log file
START LAST-10 Starts ten days before the last date in the log file