5                     VMS System Performance Meter V2.4 5                     ---------------------------------   + System Requirements:   VAX VMS V5.5 -> V7.1 ?                      Alpha VMS V6.1 -> V7.1 (not tested on 1.5) -                      Motif 1.1 to Motif 1.2-4 5                      DEC C 5.x (tested on 5.3 to 5.7)   K In this .ZIP file you should find all the files related to Perf_Meter V2.4,  including three .COM files.   N  MAKE_PERF_METER.com will remake the .EXE or .EXE_ALPHA files from the source.P It determines whether you are building on a VAX or an Alpha, and figures out theH version of Motif to use. See the command file for command line options.   M  PFM$STARTUP.com should be run at system startup (you might need modify it to O reflect the location of Perf_Meter files on your system) , if you want everyone  to be able to run Perf_Meter.   O  PERF_METER.com is a template for defining logicals and customizing the devices F monitored by the Performance Meter. Change this to reflect your systemO requirements, and make it available as a template for local users to customize. C This is the command file you should add to your Applications menu.     NOTES: =====   K  From version 2.3 onwards, you must run PERF_METER with WORLD privilege, or K install the image with WORLD privilege. This is so that $GETJPI can do it's P thing. If run without this privilege, the top process will usually be yourself !  J  On Alphas, CMKRNL privilege is needed to get the PERF_METER to run at allP because of the protection on certain executive data fields. It must therefore beO installed with CMKRNL and WORLD privileges if non-privileged users are going to  run it.   J  The CPU percentages are calculated the way monitor calculates them, which8 means that on a 2 CPU SMP system, 100% really means 50%.  M  Users should copy the example PERFMETER.DAT initialization file to their own M DECW$USER_DEFAULTS directory if they wish to customize the appearance of the   application.     Changes in V2.4  ---------------   $  - Fixed memory leaks in TOPPROC.CPU  I  - Added a "dynamic" icon display. When the Performance Meter is iconized 7    the state bar graph is displayed in the icon window.   N  - Added the "tomato of memory" to the state bar graph window and icon window.H    It shows a pie chart of free and modified pages against total memory.  I  - Slight changes to window titles, so that system version and memory are L    shown in the man window title bar, and the icon title has had the machineP    name moved to the start to make life easier if you SET DISPLAY to one machine'    and monitor several different nodes.   ?  - PERFMETER.DAT Motif initialization file has extra parameters B    neutralColour, iconForeground, iconBackground and useIconWindow#    which are explained in the file.   ,  PJO 12-Mar-1998 <phil@pottsoft.demon.co.uk>=                  http://www.pottsoft.demon.co.uk/pds/pds.html 8                  http://www.yrl.co.uk/~phil/pds/pds.html   Changes in V2.3  ---------------   I  - Added back the UIL definitions for additional devices to be monitored.   D  - Changed the .UIL to use fixed areas of the screen, even when textE    exceeds the available space. This fixes some display problems with E    long device TITLEs or when the TOP CPU user has an image file name %    longer than the Perf_Meter window.   J  - Modified the C code which gets CPU usage and state times not to requireF    CMKRNL on the VAX version (like in version 2.0) so "ordinary" usersC    can see CPU usage without having to install the .EXE with CMKRNL B    privilege. Without WORLD privilege the user can only see his orH    her own MAX CPU usage. On the Alpha, KERNEL mode is needed to get theI    CPU usage time. See the comments in the Perf_Meter.C code for details.   E  - Note that like in previous versions device logicals can consist of H    other logicals, and can point to multiple devices. But only the firstD    device will have its IO monitored. I am working on a version thatD    will sum over devices, like the VWS (for those of you old enough)0    version supports. That may be available soon.    RDS 24-May-1995  PJO 12-Jun-1995