Joe Meadows Fred Hutchinson Cancer Research Center This submission contains updates and additions to material found in earlier submissions. DECNET This directory contains some examples of using the QIO interface to NETACP to retrieve information. Included is a short program that displays a list of known nodes (similar to NCP SHOW KNOWN NODES), and one that displays a list of links. A commented version of NFBDEF.H is included. This area should continue to grow in the future, and will simply be small examples of DECNET things you can do. FILE File is a utility which allows you to display and or change header information about a file. It is most usefull when you have somehow transferred a file from a non-VAX/VMS system to a VAX/VMS system (or vice versa), and you need to change characteristics of the file, such as changing the record size, or putting fortran carriage control back on a file. This utility does not create a new version of a file, it changes the information stored in the file header, making it quite fast. A good knowledge of RMS is usefull (necessary) when using this tool. FIND - (renamed from INDEX to FIND) FIND allows you to search very quickly through the file system for files based on a wide variety of criteria. By mapping the index file into memory it performs The Fastest searches of any utility like it. Basically you can search based on any attribute found in the file header (creation date, amount of fragmentation, logical block numbers, whatever), given a minimum and maximum value. You can perform AND or OR searches on multiple criteria. You can control what information will be displayed about the file. This is a "must have" (really!). Look at FIND.HLP if this plea doesn't convince you.. Try it once.. You'll like it. Note, this was posted to the internet (via info-vax) as INDEX, however, to avoid confusion with another DECUS program I have renamed it to FIND. Sadly, I didn't do it soon enough, so it was still INDEX on the Fall '87 DECUS Tapes. A few slight bugs have been stomped. KFE KFE is a short example program for accessing the known file database (installed images). This started out because someone asked me how to tell if a file was installed, and I couldn't spot a real easy way to do that. This will be expanded in the future to traverse through the window control blocks, to display how many people are actually sharing the file etc. Currently it simply lists the known images. It works as of VMS V4.7, I have not had a chance to check it under 5.0. MENU MENU is a menu utility (big surprise?). It has quite a few nice features, including the ability to compile menus for very fast startup. We have been using it here at the Hutch for a few months now and it works well for us. I meant to include some examples, and provide better documentation, but I didn't get to it yet (sorry). Look for updates in the future. SD SD is a nice simple fast SET DEFAULT. Why? Well, everyone seems hot to do such fancy things for such a simple task. I decided to include this version (written, what, maybe 5 years ago? Updated somewhat since then of course). One feature this has that most others don't is the ability to specify a wildcarded filespec and it will find the file and move to the directory where the (first matching) filespec is found. See the help file (SD.HLP) for more info. STATUS STATUS is a fancy cluster/network wide SHOW USERS type of program. You can specify what you want to see, and how you want to see it. It can display any GETJPI item, several GETSYI items, plus several other things. You can select which processes you want displayed. It is also very easily modified. Not neccesarily a "must have", but at least a "must see". Check out WHO.COM, SHOWUSERS.COM, and SHOWSYSTEM.COM in the [.STATUS] directory for examples of its use. If you do make modifications, I would be happy to try and add them to this distribution in the future - contact me. Includes many changes from earlier submission, bug fixes, security enhancements. UNMESSAGE UNMESSAGE decompiles message files. Note, the decompiled message file will not be exactly the same as the original, as certain information is not stored in these files. However, the message text files created can be rerun through the message compiler (MESSAGE) and the resulting file will produce exactly the same results as the original (I believe, I haven't heard otherwise!). This is usefull if you want to change (or simply extract) the text of error messages. UNSDL UNSDL is a utility to aid in creating include files from the system definitions given in the text library SYS$SHARE:STARLETSD. It works in conjunction with the SDL/NOPARSE/LANGUAGE=language command to generate include files for any language you have a language generator for. For example, DEC includes all the definitions that you would normally find in the STARLET macro library, such as $ACRDEF, $JPIDEF, etc. These definitions can be used to generate include files for the language of your choice. Currently I have written a 'C' language generator. There is a lengthy description included to aid people in writing other language generators. Updated to handle some of the new features found in VMS 5.0 version of SDL. C header files created by UNSDL are included in [.unsdl.vms4-7_h] and [.unsdl.vms5-0_h]. They may be removed to save space, the procedures ALL.COM and ALL5.COM can recreate the header files. VERB VERB is a utility to make it possible to modify (or simply look at) command definitions. This version fixes a minor bug with the cliflags() option, and handles disallows clauses in a prettier fashion. This is definitely a "must have" item as well. All of the non-macro code in this distribution has been compiled (using /debug) and the object files left intact. Since everyone has a macro compiler I have deleted object files for the macro code, to help save space. All programs have been compiled and linked, (under VMS V4.7), so you do not need to recompile anything (you may need to relink most of these things under VMS 5.0). I personally like to check the code and recompile things anyway, being a not-very-trusting-kind-of-guy. I have created Makefiles, for those of you with MAKE. If you do not have this, than GET IT! I have included some COMPILE.COM command procedures for those of you without MAKE. If you have suggestions, bugs/complaints, feel free to contact me. If you have spare money, feel free to make donations (to the FHCRC, not me!) Joe Meadows Jr. VAX/VMS System Manager / guru in training Fred Hutchinson Cancer Research Center 1124 Columbia St. Seattle Wa. 98104 bitnet - JOE@FHCRCVAX arpa/internet - JOE%FHCRCVAX.BITNET@OLY.ACS.WASHINGTON.EDU voice - (206) 467-4970