Updated: 5 December 1994 !!! PLEASE READ THIS ENTIRE FILE BEFORE YOU INSTALL WHO !!!! WHO is an OpenVMS utility that provides information about the users currently logged in to the local or a remote system. WHO is installed via the OpenVMS standard installation tool -- VMSINSTAL. This WHO kit may be used on both OpenVMS/VAX and OpenVMS/AXP systems. The same kit installs on either platform. Please note that in order for WHO to correctly reach a remote node, WHO must be installed on that remote node. The local version of WHO activates the remote WHO in server mode via DECnet and requests the specified information from the remote node. If WHO is not installed on the target remote node you will get the following error message: %WHO-I-NONODE, unable to reach target node or task Similarly, WHO must be installed on ALL individual members of a cluster or local area OpenVMS Cluster. The WHO installation procedure will realize that you are installing on a CLUSTER and will install WHO cluster wide provided that you have a cluster common system disk. However, you must manually edit to ensure the SYSTARTUP_VMS.COM file is updated for all the nodes, particularly if you don't have a cluster common system disk. Also, WHO can only update the DCLTABLES on the installing node. You will have to reboot the remaining nodes to complete the installation. ------------------------------------------------------------------------------- To install WHO: WHO is installed via the VMSINSTAL product installation procedure. Login to the SYSTEM manager's account: $ copy DIVING""::sys$public:who056.a *.* ! get who kit $ set proc/priv=(all,nobypass) ! set privs $ @sys$update:vmsinstal WHO055 ! invoke installation WHO may optionally be installed across the E-net from your node. Login as SYSTEM ... then: $@sys$update:vmsinstal who056 DIVING""::sys$public: (If your node is far away, don't do it this way!) Installation notes: 1) The WHO V5.6 kit will install on either VAX or ALPHA platforms. I have included objects for both CPU types. Since OpenVMS/AXP T6.1-FT4 is still in field test, things are still in flux. This kit will correctly install on T6.1-FT4 which is all I had to test with. You may find bugs in the install procedure. I reasoned that having access to a WHO kit NOW was better than 3 months of regression testing on all the possible configurations. 2) WHO is written in FORTRAN. Your ALPHA system may not have the DEC$FORRTL shareable image library installed. If NOT the WHO IVP will fail and the product will not work. You must manually install the FORTRAN run time library. I suggest that you edit VMSIMAGES.DAT and add the line: sys$share:dec$forrtl /open/header/shared after the line for the "C" run-time library. I can only assume that omission will be fixed in a later resease of ALPHA/VMS.This problem does not occur on VAX/VMS based systems. 3) WHO V5.6 requires WORLD priviliges. This is required by sys$getjpi. WHO does NOT allow remote users to gain access to your system at elevated access and is therefor NOT a security "hole". 4) WHO V5.6 is a new baselevel of the code and will not interoperate with versions of WHO prior to WHO V5.5. If you have older versions of WHO installed on your system(s) please upgrade to this kit. Also Note that WHO V5.6 requires at least OpenVMS/VAX V6.0 or OpenVMS/AXP T6.1-FT4. 5) When using the WHO /ALL command with V5.x of WHO the Null process will have the "state" field blanked out. On VMS V4.x systems the Null process was always in "COM" state. On OpenVMS V5.x systems the Null process is always marked as "CUR". You will note that the "SHO SYS" command on VMS V5.x does not show the Null process at all. In order to avoid user confusion, WHO V5.x will blank out the Null process. 6) On Multi-processors (3520/40,8350,6000,7000,8800,9000,10000) the processor number of each current process will be displayed. The STATE field will show "CUR x" where "x" is the cpu number (in hex) that process is executing on. This is similar to the display produced by the "SHOW SYSTEM" command. Due to the time required for WHO to display the process list, on systems with a large number of processes, it may be possible for more than 1 process to "appear" scheduled on an individual processor. This is a normal occurence as WHO does not BLOCK the system to obtain a single coherent snapshot of the process list. The CPU numbers are listed as installed and will appear differently on some VAX processors. Note that the numbers are NOT usually linear (ie.. 1,2,3). If you do not have a multiprocessor, you have stopped CPU's using STOP/CPU or if the SYSGEN parameter MULTIPROCESSING is set to "0" the cpu number will not be displayed. 7) Th WHO installation procedure requires that the sysgen parameter SCSSYSTEMID be set to your DECnet node address. Also the SCSNODE parameter must be set to the DECnet node name. Please insure that these sysgen parameters are set properly before beginning the WHO installation. Take note that all the system queues (batch & print) MUST be empty when the SCSSYSTEMID parameter is changed or the system will hang during re-boot. To determine the required value of the SCSSYSTEMID parameter if not already set -- use the following formula: new_scssystemid = (area_number*1024) + node_number If your DECnet node address is 36.155 the new SCSSYSTEMID would be: scssystemid = (36 * 1024) + 155 scssystemid = 37019 ! new scssystemid value +--------------------------------------------------------------+ | *** Note: | | You must manually delete each entry in every queue | | on your system if you are changing either SCSNODE or | | SCSSYSTEMID. Your system will hang on re-boot if you | | fail to do this!!!! | +--------------------------------------------------------------+ Issue the following commands to change the parameters if needed: $run sys$system:sysgen sysgen> use current sysgen> sho scsnode ! verify current setting system> set scsnode "NODE" ! set to your DECnet node name. sysgen> sho scssystemid ! verify current setting sysgen> set scssystemid xxxxx ! set to new value sysgen> write current sysgen> exit $! ( delete all queue entries here if needed ) $@sys$system:shutdown.com ! system must be rebooted 8) The installation procedure makes WHO a known file (installed) only until the system is rebooted. WHO must be installed as a known image at system startup. Please edit SYS$MANAGER:SYSTARTUP_V5.COM to include the line: @SYS$SYARTUP:WHO$STARTUP.COM 9) The WHO installation procedure will remove all files from the VMS known file list that are named: "SYS$COMMON:[SYSEXE]WHO*.EXE". ANY FILES THAT MEET THE ABOVE CRITERIA WILL BE DELETED FROM THE KNOWN FILE LIST!! The files will NOT be deleted from your system. They will just be removed or un "installed" from the known file list maintained by the "MC INSTALL" utility. 10) The WHO IVP can only verify correct operation of WHO on your local system. However, WHO access to your node via DECnet will be tested within the IVP. If you are installing WHO onto a cluster or onto adjacent network nodes please test the network functions by issuing the command: $WHO If you only have a single node, you may test the network functions by testing WHO with my node: $WHO /ver DIVING %WHO-I-CRENETLINK, establishing DECnet link to node DIVING ... %WHO-I-REMIDENT, WHO V5.6 (5 April 1994) on OpenVMS/VAX V6.0 Host CPU: VAXstation 4000-M90 ( above shows what you should see as a return message ) 11) WHO will not recognize cluster alias names, therefore you must use a "physical" node name when refering to cluster nodes using WHO. 12) If installing WHO to a mixed architecture cluster (ie. VAX and AXP systems mixed) please be aware that the installation procedure builds the WHO executable as WHO05x.EXE in SYS$SYSTEM on both CPU types. The WHO ".EXE" file built on a VAX will not run on the ALPHA and vise-versa. Please take note that you must build the WHO kit on both processor types and that you should therefore NOT place the WHO executable in the cluster common sys$common:[sysexe] directory on a mixed architecture cluster. System managers take note!!!!! 13) The installation procedure will NOT work correctly on system with DECnet Phase V (OSI) installed. The actual executable should still work, but you will have to do the installation manually. I suggest that you print out and read the kitinstal.com file included in the kit for the steps necessary for a proper installation. ------------------------------------------------------------------------------ Release Notes: Version Release Date Changes --------+-------------------+------------------------------------------------- V2.7 08 September 1986 initial kit released V2.9 16 October 1986 modified version match algorithm addition of DECnet object number access V3.0 20 October 1986 fix bugs in username/image search make new V3.0 easynet kit & install procedure V3.1 27 October 1986 allow 5 char UIC group & member #'s New features added to help library baseline new version !!! Note: WHO V3.1 incompatible with previous releases of WHO... (sorry) V3.2 14 November 1986 internal test version V3.3 12 December 1986 add hardcopy terminal support add base priority in display baseline new version !!! Note: WHO V3.3 incompatible with previous releases of WHO... (sorry) V3.4 23 December 1986 add control-y-c-o handlers to restore screen fix installation procedure for correct install on LAVC clusters make a new network kit, compatible with V3.3 V3.5 19 May 1987 use leading zero suppression on UIC display compatible with both V3.4 & V3.3 of WHO V3.6 06 October 1987 Changed DECnet access so that object TASK is no longer required. This should fix WHO for compliance with SECURPACK restrictions. This version is compatible with V3.3,3.4,3.5 VMSINSTAL kit released. V3.7 08 October 1987 Added the /PAGE option like VAX/VMS TYPE Use defined terminal page size for displays so that scrolling works correctly on VAXstations with non standard window page lengths. V3.8 14 January 1987 Fix intermittent bug in kitinstal.com No code changes V4.0 20 April 1988 change the /ID switch to /VERSION and added the /OUTPUT command. Modified AST routines... V4.1 02 June 1988 fixed non-existant directory error on open of lun 3, last VMS V4 release V5.0 27 July 1988 removed brackets around UIC's, changed IPID to process state, now use DCL command parsing, add multiprocessing support, VMS pattern matching for username and image strings. WHO V5.0 requires VMS version 5 !!!!! V5.1 10 October 1988 Added "/CPU" qualifier. See help file! New Baseline released... V5.3 13 August 1991 Fixed bug in "/CPU" option; tested on X5.5 V5.4 19 November 1991 CMKRNL privilige no longer needed for the support of VAX multiprocessors. Requires at least VMS V5.4 or above. V5.5 7 July 1992 ALPHA Support. This WHO kit is functionally the same as WHO V5.4 but will correctly install on either VAX or ALPHA cpu types. The network password has been changed to: WHO$SERVER. Multi-processing on ALPHA has not been tested, this release might not work, but it won't crash you system. New Baselevel made. V5.6 5 April 1994 Tested on OpenVMS/VAX V6.0; OpenVMS/AXP T6.1-FT4 5 December 1994 OpenVMS/AXP changed to OpenVMS Alpha. ----------------------------------------------------------------------------- Known problems/bug reports as of current version (V5.6): Version Date reported/by Status ----------------------------------------------------------------------------- 4.0 01 June 1988 Fixed in V4.1 (something always slips by!) 50283::SONNENTAG When WHO fails to translate "SYS$NET" it aborts with an error of Open failure on unit 3 file FOR003. This happens when your default directory is set to rooted searchlisted directories. Workaround: Don't do that! This error can be artifically created by defining SYS$NET to anything. Other people have reported that this quirk doesn't appear when running V4.x of WHO on VMS V5.0. V5.1 10 August 1991 Fixed in V5.3 Paul Gallo When using the WHO/CPU option on processes that have been active for MORE that 99 hours. WHO will display an error on the screen where it would have printed the value. WHO V5.3 will truncate the CPUtime field appropriately and can accomodate uptimes as large as 9999 days. WHO V5.3 is compatible with the V5.1 release but not the previous releases. V5.2 Kit never released... V5.3 None reported... V5.4 None reported... V5.5 New kit V5.6 New kit ----------------------------------------------------------------------------- End of release notes.