University of Arizona Submissions coordinated by: Joel M Snyder University of Arizona MIS Laboratories Department of Management Information Systems College of Business and Public Administration Tucson, Arizona 85721 (602) 621-2748 These are some preliminary programs that came out of our first six months with V4 of VAX/VMS. 1. BREAK Terminals which are set to be /DISCONNECTable can generate lots of spurious jobs if users lean on the BREAK key too much. Since our users were used to pounding on the BREAK key to talk to a IDX3000, V4 VAX systems often had 64 detached jobs running LOGINOUT. BREAK is a detached program (may be easily integrated into your existing DAEMON) which detects these monsters and cuts them off (before the normal disconnect process timeout) 2. ED1 When Digital gave us callable EDT, we implemented the long-requested EDT-which-remembers-the-last-file-you-edited. GOODBYE to all those awful EDT.COM files FOREVER! Also, for the fun of it, I implemented XLATE functionality, which allows you to go directly from EDT into PHONE, MAIL, or DCL and then back. It was easy. See our example EDTINI.SYS file for information on how to include this functionality. This particular program also implements file locking; that is, no two people can edit the same file at the same time. This was done for a particular customer; you may wish to comment out calls to ED1$ACQUIREMUTEX and ED1$RELEASEMUTEX if this feature is not needed at your site. In that case, you may also ignore ED1MUTEX.MAR. (I'm not sure, but since it uses $ENQ, it might even work on a cluster???) 3. ARRAYEDIT While writing ED1, I also thought that a subroutine which edits a FORTRAN character array might be handy, and here it is. Read ARRAYEDIT.FOR for documentation.