! SYSTAT V7.0							    30-JUL-1993   A     SYSTAT is a little utility i stomped up several years ago. It ?     sort of takes off where SHOW SYSTEM stops. It allows you to >     select processes to display by several different criteria.  9     SYSTAT was originally written in VAX BASIC and it was A     put on a Canadian DECUS tape in the early 80's when Vancouver C     hosted DECUS. Later, when i got my hands on a BLISS32 compiler, <     i translated it to BLISS. Since their are very few BLISS>     compilers around, most recently (ie: the past week) it has<     been rewritten in VAX C and most of the functionality of5     $PROCESS_SCAN has been added via new qualifiers.    @     With SYSTAT, you can display an open file list for a process>     with a brief or full level of information, display anotherF     process' recall buffer, last command, or default device/directory.?     since special kernel ast's aren't clusterwide, you can only A     show that stuff on the current node. i'm considering a future ?     release that has a netserver that will collect the info for      other nodes.  @     You can also get a formatted list of process quotas, rights,>     login information, vector processor usage, and privileges.<     With the /FULL qualifier you can get a display of almostA     all information that $GETJPI can retrieve from a process (the H     display looks pretty cluttered; SYSTAT tries to get the display into>     a standard 24 x 80 screen. if your have more lines as on a+     DECterm, more lines will be displayed).   H     SYSTAT may be installed with WORLD privilege to allow non-privileged=     users to show info about any process. To allow display of J     open files, command line buffer, recall buffer, and default directory,J     to non-privileged users, you can install SYSTAT with CMKRNL privilege.    ( 	o build the AXP EXE with SYSTAT-AXP.MMS@ 	o build the VAX EXE with SYSTAT-VAX.MMS  I have no idea if this9 	  still works as I haven't had access to a VAX for years G 	o the provided ALPHA EXE runs under OpenVMS 7.2. There is a hard-coded C 	  offset in the GETCOMMAND routine since I didn't know another way ? 	  to get the data.  When I get 7.3, I will find the offset and B 	  update the procedure unless someone knows a version-independant 	  way of getting at the data.; 	o For other versions of OpenVMS, you might want to run the < 	  SYMBOLS.COM procedure to generate the C include files for 	  the specific version of VMS. 