From: SMTP%"HaymanR@icefog.uacn.alaska.edu" 8-SEP-1993 09:34:16.31 To: EVERHART CC: Subj: Re: Maintaining multiple VMS machines X-Newsgroups: comp.os.vms From: HaymanR@icefog.uacn.alaska.edu (Randy M. Hayman) Subject: Re: Maintaining multiple VMS machines Message-ID: <1993Sep8.004757.29674@raven.alaska.edu> Lines: 171 Sender: news@raven.alaska.edu (USENET News System) Nntp-Posting-Host: icefog.uacn.alaska.edu Reply-To: HaymanR@icefog.uacn.alaska.edu Organization: University of Alaska Computer Network X-Newsreader: mxrn 6.18-6 Date: Wed, 8 Sep 1993 00:47:57 GMT To: Info-VAX@KL.SRI.COM X-Gateway-Source-Info: USENET In article <1993Sep7.113954.1@ualr.edu>, domiller@ualr.edu writes: |>I am trying to maintain several (>20) VMS systems and I am running into a |>problem I hope someone else has solved. How do you keep systems in sync with |>regard to software versions. Reality says that I can't upgrade VMS (or Fortran |>or c, etc.) on every machine at the same time. Are there any good tools |>commercially or in-house to at least track what's on each machine (and |>preferably to check against the latest CONDIST to see what needs to be |>changed)? |> |>If there is no definitive answer to this, I have been working on a routine to |>try and determine the software state of a machine. Any comments would be |>welcome. |> Dale |>-- |> |>Dale O. Miller - domiller@ualr.edu | University of Arkansas at Little Rock |>Systems Programmer | 2801 S. University Ave. |>Voice: +1 501 569 8714 | Little Rock, AR 72204-1099 USA I've had a similar albeit smaller problem - only 1/2 dozen systems, but I created a program to assist myself, below is the readme file I created about my creation: IMAGE_ANLZ ($$read.me file) I created this package to make it easy for myself to keep multiple VAX/VMS systems at the same revision levels of various layered products. This package will create an output file of images, their version, their name, and their location (including nodename if specified in the input stream - see examples below) This package will take a data file of the form created by the command: $ dir/nohead/notrail/out=filename.in node::disk:[directory]*.exe; and will send the analysis to your terminal or a file. To compare software versions over multiple systems, run the image_anlz.exe executable, sending the output to a filename.out, then a simple $ search filename.out imagename command will show the versions of imagename.exe found. Examples below may make more sense. Modification History of $$read.me file: sxrmh1 05-Jun-1991 v1.2 updated sxrmh1 21-May-1991 v1.1 updated sxrmh1 02-May-1991 v1.0 created *** NOTE ********************************************************************* It should not be necessary for you to re-compile this utility, but if you do.. For modifications to the source files: Add Modification History data to this and all source files, then update the image_anlz.opt and image_anlz_out.opt files for correct version numbers, and @compile.com to do the rest. <> Compile.com as shown below has a site specific copy command in it. Change the copy command to conform to your site. Change the rename command to conform to your site. $! compile.com $! $!----------------------------------------------------------------------------- $! $ on warning then goto exit $! $ write sys$output " ...compiling IMAGE_ANLZ..." $ cc image_anlz/list $ write sys$output " ...compiling IMAGE_ANLZ_OUT..." $ cc image_anlz_out/list $ write sys$output " ...linking IMAGE_ANLZ and IMAGE_ANLZ_OUT with options..." $ link image_anlz,image_anlz.opt/options,image_anlz_out,image_anlz_out.opt/options $! $! Now to place the executables in the two places we use them from... $ copy/log/confirm *.exe acad3a::uacn_util:[image_anlz] $ rename/log/confirm *.exe [-] $! $! If we've made it this far, we don't need these anymore... $ delete image_anlz.lis;*,image_anlz.obj;*,image_anlz_out.lis;*,- image_anlz_out.obj;* $! $EXIT: $ exit <> image_anlz_out.c assumes that the header files (ih%def.h) are located in the same directory as the other source files of this package. If you move these files to your local 'library' directory, ensure the source code gets updated. ****************************************************************************** Minimal Documentation: The input file can be either an image file name (.exe extension required) or a data file name (any valid filename except filename.exe), or sys$input. File(s) may be on another node, provided that DECnet has a working link to that node, and that proper proxies are set up. You may wish to avoid using proxies, then run the image_anlz.exe image on each node, with that node's image file. No wildcards are allowed in any files. Output can be to sys$output, or any valid filename - sorry, no print queues, or device specifications. Input can be from sys$input, but there's no prompt - just enter the valid filename when the output stops, and to exit using this method - primitive I know. Code has some additional documentation (comments) in it. Example(s): $! create a template file for image_anlz to analyze multiple images... $! (if proxys are set up, you may also include other nodes' images...) $ dir/nohead/notrail/out=rmh.test dsku:[sxrmh1]*.exe; $ r image_anlz Please enter the Image or Data file to read from: rmh.test Please enter a file to Output results to: sys$login:rmh.out ................................................................ 62 images found. $ type sys$login:rmh.out Analysis taken on : 5-JUN-1991 09:44:57.32. If the image was patched, there may still be no ECO levels installed. Version Name Location ---------------- ---------------- ------------------------------------ V1.0 CHAR DSKU:[SXRMH1]CHAR.EXE;2 Date of Most Recent Patch: 29-APR-1991 09:36:02.13. ECO levels installed: 129, V1.0 DF DSKU:[SXRMH1]DF.EXE;2 Date of Most Recent Patch: 29-APR-1991 13:53:12.11. ECO levels installed: 1.0 ENTER DSKU:[SXRMH1]ENTER.EXE;1 .. .. .. 62 images found. $ r image_anlz Please enter the Image or Data file to read from: sys$system:vaxc.exe Please enter a file to Output results to: sys$output ^^^^^^^^^^ Analysis taken on : 5-JUN-1991 09:51:37.96. If the image was patched, there may still be no ECO levels installed. Version Name Location ---------------- ---------------- ------------------------------------ VAX C V3.1-051 VAXC sys$system:vaxc.exe I've got 2 VMS_SHARE files with complete source and documentation for those interested. If enough interest is generated, I'll post to vmsnet.sources.d also. -- Randy M. Hayman HaymanR@icefog.uacn.alaska.edu