Spring 1989 Submissions to the VAX SIG Tape from Allied Electronics Fort Worth, Texas [.Allied.DCL] DO_AUTOGEN.COM We paid good money some years back to have a DEC software guru on site to help with the initial tuning of our VAXcluster. The things he showed us about using AUTOGEN with Modparams.Dat have been automated in this procedure. It is a bit scary, since it runs AUTOGEN starting with GETDATA and finishing with SETPARAMS. But it does furnish you with a nice side-by-side before and after DIFFERENCES printout of all SYSGEN params that have changed. So you know immediately what changes your MODPARAMS fiddling has brought about, and can go fix anything you screwed up before something bad happens. If you give it "NOFEEDBACK" as P1, it'll do the run without AUTOGEN feedback; otherwise the default is to use FEEDBACK. Given the results I've had with FEEDBACK, I'll probably be changing the default to NOFEEDBACK in the near future... DO_AUTOGEN assumes that your Sys$Print printer can handle 132 columns produced by the /PARALLEL switch on DIFFERENCES. $ @DO_AUTOGEN or $ @DO_AUTOGEN NOFEEDBACK DORUN.COM Resubmission of a command procedure which allows you to submit a job to batch without having to build a command procedure for it. This is a rather simple minded guy, in that he only works for simple programs that don't require any additional input after the $RUN command. I've set this up as a foreign command (using LOGIN.MAR) so all I do is type $ DORUN Of course, you can do it this way: $ @DORUN NIGHTLY-VPA.COM This procedure runs VPA every night after 7:00 PM and mails me a message of every line in the VPA output that has the word "CONCLUSION" on it. When it doesn't have any conclusions to report, the message consists of 4 lines (one per node), each saying something to the effect that it didn't find anything. It's a good way to find out if anything funky is going on without having to look at the 50+ pages of printout every day. There are a couple of site dependencies marked in this code. I keep two weeks of the reports in the directory, and this procedure purges out any older than that. I use an old VAX SIG submission, MIDNIGHT, to schedule perpetual jobs like this one. $ @NIGHTLY_VPA REINSTALL.COM This simple guy uses SYSMAN to replace an installed image on every node of our cluster. It's very handy when you have a new version of a program that's a known image on every node of the cluster. It uses F$FILE_ATTRIBUTES first to make sure that the file is a known image on the current system, and stops if it isn't. REINSTALL starts up SYSMAN and does SET ENVIRONMENT/CLUSTER SET PROFILE/PRIV=CMKRNL DO INSTALL REPLACE within the SYSMAN environment. Much easier to do than logging into four different VAXen to execute the INSTALL command on each node, but still too much typing to do myself every time I upgrade an installed image. I've set this up as a foreign command (see LOGIN.MAR), so when I want to use it, I type $ REINSTALL REORGFILES.COM A resubmission of a command procedure I've been using every week for several years, this procedure optimizes and reorganizes indexed files. It first does an ANALYZE/FDL, then EDIT/FDL with the /NOINTERACTIVE to take the default optimizations, and then does a CONVERT/FDL to build a new, optimized file. $ @REORGFILES P1 P2 P3 Where P1 is the file-spec of the file to be rebuilt; P2 (optional) is "PURGE" if you want to throw away the old file and the un-optimized .FDL file; and P3 (optional) is a reassignment for Sys$Scratch, which is where CONVERT puts its work files. I have a command procedure with about a dozen activations of REORGFILES in it that gets done during off-hours every weekend (automatically scheduled using MIDNIGHT.COM). VPA_GRAPHS.COM I got tired of typing in the *LONG* VPA graph command lines, so I threw this together to give me a fairly complete selection of graphs for the previous business day. I limited the time span to noon to 4:00 PM to give me better granularity for our top usage times, doing composite graphs for the full cluster. Then it shows non-composite graphs (each node separately) for the time span of 7:00 AM to 7:00 PM so I can see if anything is cooking on any of the individual nodes. You can also change the time window and the date by passing info in P1 and P2. See the procedure for specifics on non-default execution. This is another procedure I've set up with a foreign command: $ GRAPH Please direct questions, comments, etc., to Alan Bruns Allied Electronics 401 E. 8th Street Fort Worth, TX 76102 (817) 336-5401 x 253