From: VAXMAN 30-NOV-1983 15:45 To: ALTCHULER,HEYER,LI,VAXMAN Subj: To Send Files Through MAIL. To send a file: Form 1: a. Enter MAIL Utility: $ MAIL b. Use "SEND" command: MAIL> SEND abc.dat To: xxxx Subj: xxxxxxx c. EXIT MAIL. Form 2: a. As a DCL command: $ MAIL/SUBJ="xxxxx" abc.dat username From: VAXMAN 30-NOV-1983 15:46 To: ALTCHULER,HEYER,LI,VAXMAN Subj: Filing Messages in MAIL. To save a MAIL message: 1. Enter MAIL Utility: $ MAIL 2. View Requested Message: MAIL> 23 <-- For example, msg #23 3. Use File command: MAIL> file abc.dat <-- creates "abc.dat" 4. Edit File "ABC.DAT" to remove from-to headings. The entire message is filed as one continous file, with headings at the top. The first line of the file is a form-feed character. From: VAXMAN 5-DEC-1983 10:51 To: SCHNEIDER,VANDERPLOEG,SHULMAN,LOGAN,MOSELEY,LI,OPERATOR,VAXMAN Subj: Access to Flight Surgeon's Software. Dr. Schneider, Dr. Vanderploeg requested access to the Flight Surgeon's menu for you: Dr. Victor Schneider is filling in as a MOCR Surgeon for Dr. Shulman for the end of the mission. Therefore he will require menu access the same as the rest of the flight surgeons have for the next week. Please implement this today (Monday, Dec 5). Thanks, Jim Vanderploeg I have modified your LOGIN.COM file to define an extra symbol, "MEN*U": $ MENU <-- Run standard Flight Surgeon's Menu. Your original LOGIN.COM was renamed "LOGINOLD.COM". Please reply with any questions or comments. --Scott Sibley, Ford VAX System Manager From: VAXMAN 2-FEB-1983 00:31 To: VAXMAN Subj: EE Editor on VT Terminals Don't waste your time on EDT! I have a symbol "VT" with the others in LIB0:[SIBLEY]DEFCMDSYM.COM. The "VT" defines: $ EE <-- EE to have VT screen clearing. $ K*LEAR <-- DCL to clear VT screen (just "K"). $ C*LEAR <-- Better way to spell "KLEAR" in a command file. $ JU*MP <-- Turns off VT smooth scroll (fast output). The "EE" command then invokes the VT environment; so you can use macros ', 'P, '] to replace HP macros :, :P, :] (use an apostrophe for the colons). The shift-case colon is also annoying in ellipsis changes. You might "SET MATCH `" (the accent mark by the backspace key) for VT typing speed. I was very disappointed to find that EDT is a lousy substitute for EE, typing-wise; but worse, EDT chews up VAX interrupts and moves the cursor as slow as a snail. --Scott From: VAXMAN 9-FEB-1983 05:19 To: VAXMAN Subj: Theory for MAIL.MAI Creation I have a theory to explain how VAX MAIL determines what disk to send mail to. Apparently, SYSUAF.DAT is updated to give the login count for new mail. The MAIL command checks SYSUAF.DAT for valid "To:" usernames and sends each person's mail to the pre-set default device & default directory locations. Any recipient who does not have a default device causes MAIL to update the sender's current device (as in "SHOW DEF") -- standard default rule, *:[*]MAIL.MAI. --Scott^Z From: LOGPRO 24-FEB-1983 13:48 To: VAXMAN Subj: Real Life VAX Problem as experienced at DECUS Scott: I just finished talking to a guy (Ralph Blough) who is having the double- precision "changing digits" problem. Remember in one of the VAX sessions, there was a guy who had the double precision problem beyond 7 or 8 decimal places, with digits changing for no reason. Ralph (I assume he is working with Warren's VAX) is having this problem. I told him that I remembered the story but couldn't remember the outcome. Do you? I told him that you would call him with some possible insights. His number is 280-6861. They are simply reading in a double precision number and then immediately printing it out with different answers each time beyond the "problem" decimal place. Keep me informed. --Bob From: VAXMAN 11-MAR-1983 12:34 To: SMOCK,VAXMAN Subj: Keeping Notes with INFO. I keep the Bi-weekly notes in an INFO-format file, "NOTE.", which is updated by the "HEY" command. I plan to have a "NOTE -UPDATE" eventually. Look at "HEY -HELP"; start by "HEY -CREATE". Some hints on useful notes: - State Accomplishments - Make the note topic a predicate phrase which says "I did something" such as "Created NOTE Log Today.". - Abbreviate Wording - The topic is limited to length of the input line, perhaps 60 chars. Omit articles; truncate long words; think of short synonyms. End with a period, indicating end of a thought. - Choose Keywords - Only the topic line will be searched by "INFO"; choose words that will aid topic search. For example, when I report SYSUAF changes, I try to say "Authorized XXXXXX for XXXXXX." - Edit Out Mistakes - Since INFO files are text files, they can be edited. If a line is too long, a word is wrong, or something needs more explanation, just edit "NOTE." whenever convenient. There's nothing to prevent re-wording something logged weeks earlier. --Scott From: THOMPSON 31-MAR-1983 09:20 To: VAXMAN Subj: RE: Can you tell me what to answer (see below)? --Scott IT MAKES A DIFFERENCE AS TO WHICH TRS-80 COMPUTER HE MIGHT BE USING. ALSO, IT WOULD DEPEND ON THE TERMINAL PACKAGE BEING UTILIZED. I HAD A SIMILAR PROBLEM AT FIRST ALSO. GENERALLY HERE IS HOW HE SHOULD BE CONFIGURED: SPEED 300 BAUD PARITY EVEN OR NONE WORD LENGTH 7 BIT STOP BITS ALWAYS 1 DUPLEX FULL LINE FEEDS NONE HE MAY CALL ME AT 488-8111 IF HE HAS ADDITIONAL QUESTIONS. --SCOTT From: VAXMAN 25-APR-1983 16:02 To: OPERATOR,VAXMAN,CAMPBELL Subj: Reply to Paul Swank's BIMED Problem (see below). --Scott Paul, BIMED issues the "image file not found" message when an image file cannot be created in the "TEMPDIREC" directory. Usually, TEMPDIREC is "LIB0:[UTIL.TEMPFILES]" If the LIB0 disk quota is exceeded, the image file cannot be created. Error messages are suppressed during the LINK command which generates the *.EXE file, so the exact file-creation problem is not explained under BIMED. Naturally, this is a bad strategy, and hence, image file errors produce cryptic results. The LIB0 disk use for UIC [251,2] was 685 out of 700. I increased the quota to 2000 blocks. I intend to fix BIMED to use the LIB2 quota when available. Sorry for the inconvenience. --Scott Sibley From: VAXMAN 17-MAY-1983 16:25 To: LI,GUIDRY,OPERATOR,SMOCK,VAXMAN,CAMPBELL Subj: TOTAL Tape Library Database Not Needed. Marian, Betty, Annette and I have extracted all the current information from the Tape Library database. This database is no longer needed. All index information is now in INFO format, so you can delete the database. ACTION: Delete LIB1 Tape Library database: LIB1:[TOTAL]*.LIB;* (?) Delete T/ASK files: LIB0:[TOTAL]DIRTDB.TAP Delete LSMOC "TAPELIBR" form: LIB0:[LSM]TAPELIBR*.DAT Delete DBMAN's "TAPELIBR" form: LIB0:[NASAPROG.LSMOC.FORMS]TAP*.* Delete DBMAN's source: LIB0:[NASAPROG.LSMOC.FORMS.CODE]TAP*.* Delete Access/Form record: Use AFEDIT to delete "TAPELIBR" entry. FUTURE: I will delete the [OPERATOR]TAPES.EXE program, the ONLINE.EDT, and the tape-library T/ASK retrieval & NED Editor command files. --Scott From: VAXMAN 5-DEC-1983 19:09 To: SCHNEIDER,LI,OPERATOR,VAXMAN Subj: Flight Surgeon's Menu. Dr. Schneider, I wasn't sure if you were familiar with the Flight Surgeon's menu options. Let us know if you have any questions. --Scott Sibley Ford VAX System Manager From: VAXMAN 3-JAN-1984 16:27 To: SHULMAN,LI,VAXMAN Subj: [SHULMAN]*.EZ;* Files. Ellen, I sent MAIL to Marian Li about the *.EZ files. She replied that these files existed due to an abnormal exit (such as a control-Y) while running pre-defined plots. You can delete the old files as before: $ DEL *.EZ;* <-- Delete all files of type ".EZ" If you want a log of the deleted files, add "/LOG": $ DEL/LOG *.EZ;* <-- Delete all ".EZ" files & log names. The names of the files will be displayed on the terminal screen. Let us know if you want to get rid of any other files. --Scott Sibley Ford VAX System Mgr. From: VAXMAN 8-DEC-1983 12:22 To: POOL,HEYER,MOSELEY,LI,OPERATOR,VAXMAN Subj: Deleted 111 MAIL Msgs. Dr. Pool, I worked with Bob Heyer to delete the first 111 messages from your VAX/VMS personal MAIL file: - Original MAIL.MAI was renamed to "OLDMAIL.MAI". - New MAIL.MAI was created with 111 messages deleted. - All remaining messages were marked as "previously read". I did not consciously read your remaining 19 messages. If you have any questions or comments, please let us know. (Your OLDMAIL.MAI file will be deleted after 20-Dec-83). --Scott Sibley Ford VAX System Manager From: VAXMAN 4-JAN-1984 16:12 To: CHIZEK,VAXMAN Subj: Bits, Bytes & Blocks. Virginia, A disk block is used to measure disk sizes: 1 BLOCK = 512 BYTES 1 BYTE = 8 BITS Storage sizes are powers of 2: 1 K (Kilobyte) = 2**10 BYTES = 1,024 BYTES 1 Meg (Megabyte) = K*K = 1,048,576 BYTES --Scott From: VAXMAN 3-JAN-1984 23:31 To: WINSTON,OPERATOR,SMOCK,VAXMAN Subj: Protecting VAX MAIL Files. Jody, Please ask Austin Gosling to protect his VAX MAIL file from an accidental purge after receiving new unread MAIL while using the MAIL utility: $ SET PROTECTION=(SYSTEM:RW,OWNER:RW) MAIL.MAI In accordance with our "VAX Users' Bill of Rights", the management staff honors the privacy of user accounts; we won't read a user's MAIL file without his permission. For secure information, I recommend encrypting data through a user-defined algorithm to minimize any fears. --Scott Sibley Ford VAX System Manager From: VAXMAN 4-JAN-1984 20:44 To: OPERATOR,SMOCK,LI,LIU,VAXMAN Subj: Fix for DECwriter Hangup. I think the DECwriter console terminal, "OPA0:", registers the error for "out-of-paper" due to excessive line length. I reset the width: $ SET TERMINAL/PERMANENT/WIDTH=117 OPA0: and the value "117" seems to work OK for now.... I also changed the entry for OPA0 in the SETTERMS.COM file. --Scott From: VAXMAN 20-JAN-1984 22:43 To: OPERATOR,SMOCK,LI,VAXMAN Subj: Friday Night Shutdowns. I've been having the most unspeakably horrible, horrible problems with the "LPA0" print queue. I couldn't dismount the LIB2 disk because of a LIB2:[LI] print job. I tryed: - aborting the print job. - stopping the LPA0 que. - stopping SYS$PRINT & re-queueing the job. - deleting the LPA0 que. - stopping the printer symbiont, "PRTSYMB1". - re-booting the VAX. I finally tried copying the 8-JAN-84 SYS$SYSTEM:JBCSYSQUE.EXE file from a backup disk and re-booting. Naturally, all the 8-Jan-84 jobs started running, so I stopped them & deleted the pending jobs. When I submitted a new print job, it hung up again -- PRINTER OFFLINE! --Scott From: VAXMAN 27-JAN-1984 15:12 To: BIELSTEIN,LI,OPERATOR,VAXMAN Subj: Correcting Typing Errors in MAIL. Dr. Bielstein, To correct errors while typing MAIL messages, you have the following options: - Erase previous letters on the current line: Press "DEL" (delete) key. - Erase the entire current line: Press Ctrl-U (the "CNTL" & "U" keys). - Erase the whole MAIL message: Press Ctrl-C (the "CNTL" & "C" keys). It is not possible to modify a line once you have pressed the "RETURN" key to start the next line -- you would be forced to erase the whole message. If you plan to send a detailed message, it would be best to edit it into correct format with a text editor, such as "EE", and then send the edited file through MAIL (as with "MAIL> SEND XXX.DAT"). --Scott Sibley Ford VAX System Mgr. From: VAXMAN 4-JAN-1984 15:53 To: OPERATOR,SMOCK,LI,VAXMAN Subj: Missing Items. Annette, Only my DisneyLand mug disappeared; I took the St. Louis & Las Vegas cups home. I hadn't heard anything about your leather jacket. Ron Nachtman said a video cassette recorder was missing from the Bone Densiometer lab, and he saw a maintenance guy snooping around during the break. I think we should put the HP terminals in the VAX machine room during all future holiday periods -- we'd never get them replaced. That's why I keep all the disk packs in the VAX machine room. --Scott From: VAXMAN 19-JAN-1984 19:36 To: OPERATOR,SMOCK,LI,VAXMAN Subj: Weekly Disk Backup Schedule. Since Dr. Moseley appears to be unable to obtain an extra disk drive, and the incremental backup coverage now spans two full weeks, Monday - Saturday, I will no longer run full disk backups every week. During a shuttle mission, we can provide 24-hour availability for up to 14 consecutive days without losing major backup coverage. All disk packs will be online at all times. The decrease in full disk backups will also reduce the wear and hazards of copying or handling disk packs. Opening of disk drives to unfiltered room air will be reduced. Of course, with our vast disk space, full backups every week would improve safety, but our limited manpower simply cannot provide complete support for a large, 100-user-per-month computer system. --Scott From: VAXMAN 23-JAN-1984 18:51 To: OPERATOR,SMOCK,LI,LIU,VAXMAN Subj: BACKUP Utility Losing Files. Annette, I took a look at the December ERRLOG tape & verified your command as correct, and that the highest-version file had been left out. When I re-ran the BACKUP command, the same problem occurred. I think the BACKUP utility has an error. I went ahead and saved all the files, including the January *.OLD, without any problems, so I wrote in the "Date Saved" and put the tape in the rack. ACTION: Note bug in "BACKUP". (I will delete the December *.OLD files.) FUTURE: Watch for other bugs in "BACKUP". I may call DEC about this bug. When VMS V4.X is installed, we can check for bug fixes. --Scott From: VAXMAN 18-MAY-1983 22:12 To: OPERATOR,SMOCK,LI,CAMPBELL,VAXMAN Subj: Cleaning of Disk Packs. Annette, Bob, Marian, Don, During the 1982 Fall DECUS U.S. Symposium, DEC presented a session entitled "Care and Feeding of DEC Computers". They recommended that disk packs should be cleaned every three months. We're about 8 months overdue. Don, can you find out if "every three months" is accurate and ask Bob Heyer to schedule another disk-pack cleaning period. Also, last time, they "cleaned" every last disk pack. I DON'T THINK THEY SHOULD BE ALLOWED TO TOUCH THE ACTIVE DISK PACKS. They can clean them the following time, in backup rotation. --Scott From: VAXMAN 20-MAY-1983 12:36 To: CAMPBELL,SMOCK,VAXMAN Subj: 9600-baud Lines at Ford. Don, Bob, We need to find out about getting high-speed (9600-baud) phone lines at the Ford Bldg. We can set terminal lines as "/AUTOBAUD" to work with both the current 1200-baud phone lines & the high-speed lines. High-speed I/O is an important part of the "paper-less software" methodology that we are trying to develop. Once fully designed, this concept should be presented to general software management. --Scott From: VAXMAN 20-MAY-1983 18:26 To: CAMPBELL,SMOCK,LI,VAXMAN Subj: Bad DEC RA81 Disk Drive. Don, I just finished talking to Kin Leung at the Lunar & Planetary Institute about the Houston DECUS during August 12-13. He said the committee would be scheduling presentations in June. Kin also said that he had ordered an RA81 disk drive (1,012,000 blocks) but it was delayed because of an engineering hold. Apparently, the disk sub-system returns a successful write status to the VAX but loses output data sent for storage! Considering the software errors found in VMS V3.0, experience would dictate "avoid new DEC products". I strongly recommend using older, proven hardware (like an RM05). Although technically, the customer can have his way; ethically, we should try to minimize potential future problems. --Scott From: VAXMAN 20-JUN-1983 18:20 To: CHIZEK,VAXMAN,LI Subj: Multiple Definition of USEXIT. Virginia, Good news! I ran some tests, and it looks like the "$ LINK" command will ignore additional definitions of a subprogram -- it gives a warning message and keeps the first definition. This allows us to use just one Command Interpreter object library and link to special USEXIT.OBJ files (expecting a LINK warning about multiple "USEXIT"'s). I put a USEXIT.FLE file with PRELIM.FLE, fixed the EEPAGEGEN.COM file, and it works OK. To complete FORTRAN-77 conversion, modify "ENTMOD.FOR" to store blank-filled module names in the module stack. --Scott From: VAXMAN 7-JUL-1983 21:16 To: VAXMAN,SMOCK Subj: Write-Locked LIB0 Disk (sent to "ALTCHULER"). --Scott Steve, I hope you didn't get locked out on the LIB0 disk. I forget that "$ ANALYZE/DISK/REPAIR/CONFIRM LIB0:" will write lock LIB0 while the command is running. --Scott From: VAXMAN 11-JUL-1983 15:39 To: OPERATOR,LI,VAXMAN Subj: (MAIL sent to Bonnie Dunbar; see below.) --Scott Bonnie, I logged you off terminal TTC3. I think you were in the Text Editor sub-system of Easy Graphing: )E <-- "E" transfers to "EDIT" within Easy Graphing (EZ). >Q <-- "Q" will "QUIT" & return to Easy Graphing. )BYE <-- "BYE" is then valid to exit. $ LO <-- "LO" will then do a LOGOUT. I realize this can be confusing. "EDIT" is the only major sub-mode in Easy Graphing. I will try to add "BYE" and "EXIT" along with "QUIT" as valid edit commands. In any event, you can use control-Y (^Y) to abort most programs to the "$" prompt. --Scott Sibley From: VAXMAN 13-JUL-1983 19:23 To: DBMAN,SMOCK,OPERATOR,VAXMAN Subj: LSMOC Modification Freeze. Marian, Bob, Annette, and I will make no changes at all to the LSMOC production files until you have time to coordinate & test the changes. This is the very LAST time these problems will occur. ACTION: When you can coordinate & test changes: - Remove key-check files from [LSM]. - Move (dbname)*.COM files to [NASAPROG.LSMOC.FORMS...]. - Change DBIP & DBUP to refer to [NASAPROG.LSMOC.FORMS]. FUTURE: You (Marian) will direct all LSMOC changes. LSMOC & LSMOC2 & DATAENTRY will NEVER be used for initial testing because the VAX may crash (as it did) during the tests. We must use LSMOC3 & TESTENTRY to create working LOGIN.COM systems. --Scott From: VAXMAN 22-JUL-1983 16:19 To: OPERATOR,LI,SMOCK,LIU,VAXMAN Subj: Database Tape Block Size Still 32256. I did NOT change the Operator "MENU" disk backup sub-option "C" to copy the database BACKUP save sets from disk to tape with a new /BLOCKSIZE: Tape Blocksize: Now 32256 Recommended 32528 The other block size is documented in "$ HELP BACKUP /BLOCKSIZE" as the default size of disk save-set blocks under VMS V3.2; this size is also given in the "Command Language User's Guide"; however, just to be safe, I ran a "DIRECTORY/FULL" of a save set & it shows 32256. --Scott From: VAXMAN 22-JUL-1983 21:42 To: OPERATOR,SMOCK,LI,LIU,VAXMAN Subj: VAX Lab Floor Buffing. Annette, Bob, Don't permit any buffing in the VAX machine room. I'm afraid that wax dust may get inside the disk packs. Please keep the connecting door closed during buffing out in the lab area. --Scott From: VAXMAN 30-JUL-1983 00:43 To: MORGAN,OPERATOR,VAXMAN Subj: Large VT100 Characters. Celia, There is a program which will display files in large characters on a VT100-type terminal. Use the following commands: $ @LIB0:[UTIL]BootProm <-- Defines "PROMPTOR" for sign-on session. $ PROMPTOR <-- Runs program to display a file. The PROMPTOR program will ask for a file name; press the "RETURN" key to advance to the next page of the file. --Scott Sibley Ford VAX System Manager From: VAXMAN 5-AUG-1983 11:37 To: SMOCK,LI,VAXMAN Subj: TOTAL REFR fix in DBIP/DBUP. Bob, I read your bi-weekly event-log entry about the INTEGER*2 change. The comparison should probably be done in CHARACTER*4 variables. If a pointer value has the numeric equivalent of "EN", the test would be incorrect: C*4 type "END.": E N D . 45 4E 44 2E I*2 type "END.": N E . D 4E 45 2E 44 The hexadecimal number "454E" is decimal 17742, which might be a valid pointer number. Do you check for both "EN" and "D."? --Scott From: VAXMAN 16-AUG-1983 19:21 To: SMOCK,OPERATOR,LI,LIU,VAXMAN Subj: VAX/VMS Boot Omits Site Initialization. I have changed the VAX/VMS boot sequence to omit the site-specific command file which mounts disk, starts queues, etc. The boot file will disable non-operator LOGINs (users know the VAX boot by garbage on their screens), but the console will explain the start up: To Mount Disks, Start Queues & Allow Users: Sign on OPERATOR; Type: STARTSITE The "STARTSITE" command mounts disks, starts queues & sets the login quota. If DEC boots the VAX, users can't sign on. Also, STARTSITE works only once: $ startsite STARTSITE - Site Start-up already performed; command terminated. We can add options to STARTSITE in the future. --Scott From: VAXMAN 16-AUG-1983 20:15 To: NASTRAN,OPERATOR,VAXMAN Subj: SL4 Disk Space. James, I have assigned the name "SL4" ("Space Lab 4") to the second RM05 disk drive (physical device name "__DRA3"). The disk pack currently on SL4 has a "[NASTRAN]" directory and 130,000 free blocks which you may use. Sid Balikian, of DEC, ran preliminary diagnostics for the RM05 disk drive, and they passed successfully. When you access files on the SL4 disk, you should use the name "SL4" and not "DRA3" since the "DRA3" name will change if you move from the RM05 drive to the originally intended RA60. The conversion can be accomplished simply by re-assigning "SL4" to refer to the RA60 disk drive. --Scott Sibley Ford VAX System Manager From: VAXMAN 29-AUG-1983 16:14 To: MORGAN,OPERATOR,VAXMAN,LI Subj: Inserting Multiple Lines Celia, Annette, To insert multiple blank lines in a file, you can use the "Repeat" command in EE to repeat the insert command: >I; N; *100 The above command line inserts ("I") a blank line, moves to the next ("N") line, and repeats 100 times. For more than 100 lines: >I; N; *100; *10 That repeats 10 * 100, or 1000, times. --Scott From: VAXMAN 30-AUG-1983 19:51 To: SHULMAN,VAXMAN,LI,OPERATOR Subj: Online MOCR Handbook Ready. Ellen, We have implemented the online version of the STS Medical Console Handbook as the LOGIN menu option "MOCR Handbook". As you suggested, the program has an option to display the index & an option to display the book sections. Whenever you have time, please respond back with any questions or comments (VAX Lab 483-5353). The online handbook reflects the July 1983 revision, chapters 5 - 7, with the entire index. The figures (charts) are planned for mid Sept. To improve readability, we made the following minor changes: - Abbreviated long section titles to fit each on 1 index line. - Re-worded some index titles to match the book-section titles. - Omitted long tox. keywords which already match sub-section titles. As expected, you can search by any words, section numbers, or their abbreviated prefixes (such as: PCS, PC, PRES CONT). --Scott Sibley From: VAXMAN 19-SEP-1983 13:06 To: SHULMAN,LI,OPERATOR,ANDERSON,VAXMAN Subj: Added Handbook Figures. Ellen, Annette Walker & I have added the figures (charts) to the online MOCR Handbook. All the figures are listed in the index, but only the tabular charts for sections 6.0 - 7.0 were typed in. We are currently proofreading the charts to match the Xerox copies. Whenever you have time, please respond back with any questions or comments (VAX Lab 483-5353). The figures (July 1983 revision) were modified as follows: - Numbered as "Fx.x" to distinguish figure "F6.2" from section "6.2". - Squeezed to fit within 78 columns on the terminal CRT screen. - Condensed roughly 30% by omitting alternate bar lines & blank lines. --Scott Sibley Ford VAX System Manager From: VAXMAN 22-SEP-1983 11:57 To: SMOCK,LI,LIU,OPERATOR,VAXMAN Subj: Checking VAX Hardware Rev. Level. To check the VAX CPU hardware revision level, examine the System ID Register bit pattern: $ id = F$GETSYI("SID") $ show symbol id ID = 20448366 Hex = 0138046E Octal = 002156 Using the Hex format, convert the 2nd pair of digits to binary: From 01 38 04 6E, Hex 38 = Binary 0011 1000 <-- Convert to binary. XXX X <-- Re-group digits (rev. = 7). For example, rev. 8 would be binary "0100 0000", or hex "40", in the SID hexadecimal display. --Scott From: VAXMAN 30-SEP-1983 09:27 To: EWART,VAXMAN Subj: Rules for BME Forms. Pam, There are some limitations to constructing BME forms. I don't know all the rules, but they include: 1. Limited Size (whatever fits in the Hewlett-Packard screen buffer). 2. Space in Column 1 (the VAX/VMS "TYPE" command chops off column 1). We could fix the "BME" program for column 1 in the future. --Scott Sibley Ford VAX System Manager From: VAXMAN 12-OCT-1983 20:09 To: OPERATOR,SMOCK,LI,LIU,VAXMAN Subj: Copying Daily Disk Backups to Tape. Annette, Use "BACKUP" user-ID menu options "C2" & "C3" to copy the daily disk backup save sets to the "LB2..." & "SL4..." tapes. I initialized both "WED" & "THU" tapes. The menu will check for correct labels: Enter option: C2 TAPE DRIVE to receive LB2WED backup (0 or 1): 1 _MTA1: allocated Ready to copy LB2WED save set to LB2WED tape on MTA1:, OK? Y %MOUNT-I-MOUNTED, SL4WED mounted on _MTA1: Wrong Tape on MTA1:, "SL4WED" -- expected "LB2WED". Tape dismounted. Enter option: The copy step is coded in the menu -- no jobs are submitted. --Scott From: VAXMAN 13-OCT-1983 16:51 To: CHIZEK,LI,VAXMAN Subj: Sort by Added Key. Virginia, An easy way to do a multi-key sort is by "added-key" algorithms. This method is used in some commercial sort programs: - Add a comparison key to each record: - - Concatenate sort fields, in order, as the key for each record. - - Reverse order (descending) fields are in two's complement or ? - Create a list of record numbers (subscripts). - Sort the record keys in ascending order, moving only keys & numbers. - The list of record numbers is a sorted permutation of array pointers. Throughout the program, access all records by looking in the array of record numbers. No matter how the sort is done, the program logic will be unchanged. A generalized "sort-key-and-move-number" routine could then be used in a large number of different programs. --Scott From: VAXMAN 16-MAR-1984 21:28 To: LI,SMOCK,MOSELEY,HEYER,OPERATOR,LIU,VAXMAN Subj: Disk Data Integrity Chart. I have finished the backups for the database disk & RP06 clone of the LIB0 system disk. The overall data-integrity plan is now in effect; it encompasses approximately 5 gigabytes (5 billion characters) of disk storage. To view the current Data Integrity Chart, type: $ DISK CHART <-- displays Data Integrity Chart The overall plan has been implemented in stages over the past 2 months, using only the overtime budgeted for periodic disk backups. As we follow the plan in the future, we will be protected from almost any conceivable disaster. --Scott Sibley, Ford VAX System Manager From: VAXMAN 3-FEB-1984 22:42 To: OPERATOR,LI,VAXMAN Subj: Fixed Dr. Moseley's Terminal. Someone had removed the tab stops in the VT132 SET-UP mode. We re-entered the tab stops and saved the terminal status ("S") so that the tabs in MAIL wouldn't slide off the screen. --Scott From: VAXMAN 23-FEB-1984 17:41 To: LI,OPERATOR,GUIDRY,VAXMAN Subj: Dr. Dunn's VT Cable Loose. Marian, Dr. Dunn found his VT terminal cable was disconnected. Someone had been using his terminal.... No repair call was needed. --Scott From: VAXMAN 7-MAR-1984 09:42 To: AUSTIN,VAXMAN Subj: RE: Command Definition Utility. Austin, I don't use the VAX/VMS Command Definition Utility because: - I created many DCL extensions prior to its existence. - It adds a level of complexity for new employees. - It is very DEC-VAX/VMS-dependent. - DEC has a history of incorrectly upgrading products (lack of testing). - DCL command files are simple & easy to read. - Modification of DCL command files requires no compilation steps. - DCL commands to process parameters are fast relative to total duration. - I intend to re-write the extensions for the U.S. Army Ada Lang. System. Since I don't anticipate a reliable "design-freeze" period for VMS, I can't justify depending on anything other than the Ada Language System. --Scott From: VAXMAN 9-APR-1984 10:20 To: LOGAN,SHULMAN,STEWART,SCHNEIDER,VANDERPLOEG,LI,OPERATOR,VAXMAN Subj: Using MAIL. To access the MAIL program at the DCL-command level, you can shorten the command to "MAI" (all DCL commands can be abbreviated to 4 letters). To read new messages while in "MAIL", you must access the highest MAIL file, "MAIL.MAI;", containing the new message(s) -- use "READ MAIL": $ MAI <-- Invoke MAIL program as a DCL command. . . . New mail from XXXXXX MAIL> READ MAIL <-- Reads messages from file "MAIL.MAI;". --Scott Sibley, Ford VAX System Manager From: VAXMAN 19-OCT-1983 11:02 To: VANDERPLOEG,OPERATOR,VAXMAN Subj: VAX Modem Connection. Dr. Vanderploeg, I don't know the specific settings for an IBM PC, but for a TRS-80 computer, the following seem to work: Parity - even or none Stop Bit - always 1 Duplex - full I will be attending the Houston DECUS VAX LUG meeting tonight & the topic will be interfacing microcomputers to the VAX. --Scott Sibley Ford VAX System Manager From: VAXMAN 21-OCT-1983 21:25 To: LI,VAXMAN Subj: MAIL sent to OPERATOR,LIU,GUIDRY,SMOCK,VAXMAN. --Scott Annette, If you need to dismount the LIB2 disk pack, you must remove all hooks set by the "INGRES" database. I have created a command file to remove the installed images: LIB0:[SYSMAN]KILINGRES.COM Matthew, you'll need to coordinate this with Annette if LIB2 must be dismounted. To restart INGRES, ask Bill to sign on "SYSMAN" and: @LIB2:[INGRES]INGRESINS "OPERATOR" does not have sufficient privileges to run the INGRES database. I don't know which ones are needed. --Scott From: VAXMAN 1-NOV-1983 18:36 To: OPERATOR,LI,GUIDRY,LIU,SMOCK,VAXMAN Subj: Locking Out LSMOC Users. The [LSMOC], [LSMOC2] & [DATAENTRY]LOGIN.COM files have been modified to all recognize "test" mode. Sign on "LSMGOVERN" & check: $ HOW LOCK - Will lock all new users out of LSMOC, LSMOC2 & DATAENTRY. UNLOCK - Will reverse the effects of "LOCK" & allow access. The LOGIN.COM files now provide forced logout without the need to edit the LOGIN.COM files at all. --Scott From: VAXMAN 2-NOV-1983 21:29 To: LI,OPERATOR,SMOCK,LIU,VAXMAN,ANDERSON Subj: United States Location. Since some of our database users are not in Texas, we should expand our awareness in our messages: - Site: NASA/JSC Bldg. 37 (perhaps include "Houston, TX"). - Phone: (713) 483-5353 The "JSC" & telephone area code may help remote users (such as NASA/KSC). ACTION: Add "JSC" & "(713)" to existing messages as time permits. FUTURE: Maintain a nation-wide, or world-wide, view in our software. --Scott From: VAXMAN 3-NOV-1983 18:49 To: HEYER,VAXMAN Subj: Deleting MAIL Messages. Bob, You probably retained your old MAIL messages by using the MAIL "QUIT" command instead of "EXIT". The "QUIT" option preserves the original state of your MAIL file. The VAX/VMS DEC developers often give "QUIT" the added meaning of "abort, don't change anything": EXIT - Take normal exit & save changes. QUIT - Quit immediately and don't change anything! These meanings for "EXIT" & "QUIT" apply to both the MAIL Utility & the EDT DEC Standard Text Editor. --Scott From: VAXMAN 4-NOV-1983 00:31 To: OPERATOR,LI,GUIDRY,SMOCK,CHIZEK,LIU,VAXMAN Subj: Chemical Formulas. I think most dictionaries have the "Periodic Table of the Elements" listed near the word "element". We should all be familiar with the chemical element names & symbols since medical information often contains many symbolic chemical formulas. --Scott From: VAXMAN 6-NOV-1983 15:22 To: AUSTIN,VAXMAN Subj: LISP Language. Austin, I used the LISP language in the graduate program at the Georgia Tech. School of Information & Computer Science during 1979. Personally, I found that LISP was very difficult to learn -- the built-in functions were not well explained & so it reminded me of learning integral calculus by trial- and-error methods. I think that the most useful features of LISP can be performed by a library of Ada or Pascal procedures, but the LISP language requires fewer lines of code to perform some algorithms. I have a hunch that in the future, the technological level of Ada programs will dwarf almost all others as trivial -- any major, complex algorithms will be worth coding (& verifying) in Ada, with the advantage of user-defined types, parameter checking, and CPU-memory protection for individual program modules. --Scott Sibley Ford VAX System Manager From: VAXMAN 17-NOV-1983 17:39 To: BME,EWART,LI,VAXMAN Subj: Defining EE Editing Macros. Pam, Natalie, Just to review the procedure for defining EE macros, here are some examples: DEF XX "TIME 315:23:" <-- XX gives day & hour prefix. DEF DAY "TIME 315:" <-- DAY gives day prefix. DEF END /EXIT/ <-- END puts file & exits. HELP XX DAY END <-- Shows macros by name. HELP/MACRO <-- Shows all defined macro names. For more details, you can also search for information: INFO 99 MACRO EE has space to define about 100 extra macros. The macro names cannot include numeric characters such as the digits "0" - "9". --Scott Sibley Ford VAX System Manager From: VAXMAN 18-NOV-1983 13:53 To: LOGAN,LI,OPERATOR,VAXMAN Subj: Using "PHONE" on Non-DEC Terminals. Dr. Logan, The standard VAX/VMS operating system does not provide support for non-DEC (Digital Equipment Corp.) terminal features. As a result, all the non-DEC terminals cannot directly run DEC screen-control programs such as "$ PHONE" and "$ MONITOR". To support non-DEC terminal features, we must modify a special program in the operating system as several other VAX installations have done. This is on our "List of Things to Do", but will take several weeks to investigate. For the future, the American National Standards Institute (ANSI) is defining hardware & software standards to avoid these compatibility problems for proposed computer systems. --Scott Sibley Ford VAX System Manager From: VAXMAN 18-NOV-1983 16:25 To: LOGAN,LI,VAXMAN Subj: Creating a File. Dr. Logan, You can create a file several ways: - Use EE Editor: $ EE -NEW myfile.for - Use EDT Editor: $ EDIT/EDT myfile.for - Use CREATE cmd: $ CREATE myfile.for (text entered here) (enter control-Z to end) ^Z - Use GENFOR cmd: $ GENFOR (answer questions & then edit file) Any of the above will work for your user ID. --Scott Sibley Ford VAX System Manager From: VAXMAN 21-NOV-1983 15:21 To: OPERATOR,LI,SMOCK,GUIDRY,LIU,VAXMAN Subj: Checking Incremental Backup Journals. To check the journal files of the incremental disk backups, use the command: $ @LIB0:[BACKUP]CHECKJOU [filespec] All journal files have the form: LIB%day.BJL where "%" is the disk number, 0/2/3, and "day" is "MON", "TUE", "WED",.... If filespec is omitted, all journal files will be displayed. --Scott From: VAXMAN 23-NOV-1983 14:51 To: AUSTIN,VAXMAN Subj: Sub-directory Navigation. Austin, I wrote the "CD" ("Change Directory") command file to simplify navigation from one directory to another. To move upward: $ CD < <-- Moves up one sub-directory level. $ CD [-] <-- Uses DCL syntax to move upward. $ SET DEFAULT [-] <-- VAX/VMS command to move upward. The "CD" command remembers the 4 previous directory path names as global symbols 'SaveDir', 'SaveDir2', 'SaveDir3', and 'SaveDir4'. For more information, refer to: $ CD -HELP. --Scott Sibley Ford VAX System Manager From: VAXMAN 16-DEC-1983 19:12 To: DUNN,VAXMAN Subj: Sort Algorithm for BASIC. Dr. Dunn, The following routine uses the "straight sort" algorithm to sort an array (list) of character strings into alphabetical order (NOTE: This algorithm assumes A > Z.): 100 DIM STR$(10) 150 REM ------------------------ DEFINE ARRAY CONTENTS 210 STR$(1) = "APE" 220 STR$(2) = "ZEBRA" 230 STR$(3) = "CAT" 240 STR$(4) = "FINCH" 250 STR$(5) = "DOG" 255 REM ------------------------ SORT DEFINED ARRAY 260 NUMWORDS = 5 500 GOSUB 5000 800 REM ------------------------ STOP PROGRAM 900 STOP 5000 REM ======================== SORT STR$ ARRAY 5010 SIZE = NUMWORDS 5020 FOR J = 1 TO SIZE - 1 5025 MAXONE = J 5050 FOR K = J+1 TO SIZE 5060 IF STR$(K) <= STR$(MAXONE) THEN 5090 5070 MAXONE = K 5090 NEXT K 5200 TEMP$ = STR$(J) 5210 STR$(J) = STR$(MAXONE) 5220 STR$(MAXONE) = TEMP$ 5600 NEXT J 5650 REM ------------------------ 5650 RETURN 9000 END From: VAXMAN 3-JAN-1984 15:19 To: WINSTON,OPERATOR,VAXMAN Subj: 6250-bpi Tapes. Jody, Our tape drives support only 800 or 1600 bpi. I've never used any 6250-bpi drives. Perhaps Bob Heyer could find a compatible system on site. Please call him at 483-5281 (his secretary will deliver your messages). You can also send him VAX MAIL to "HEYER", but leave a telephone message to notify him to check his MAIL. I will forward these messages to him now. --Scott Sibley Ford VAX System Manager From: VAXMAN 29-OCT-1982 18:46 To: VAXMAN In terms of software design, the Library functions offer a higher level of abstraction; terminal control is provided by function calls instead of I/O statements. Also, some error checking is provided, which many programmers (especially VMS developers) might easily overlook. Library routines centralize code & standardize software capabilities. When DEC supports software, it supports it through VMS V3.0, V4.0, V99.0. Many DCL commands (MAIL, MONITOR, PHONE, etc.) use the VT terminal library routines. If the application will be VAX-dependent, and the library routines are adequate, then they should be used. Although the screen control routines help promote DEC terminal sales, an interface to a foreign-terminal database is available for dedicated VMS gurus. However, I agree with you; the library routines aren't terribly useful. That's why I created CRTScreen.OLB with more capabilities; and it has a VAX-independent, terminal-independent, human-readable database. --Scott From: VAXMAN 27-MAR-1984 18:57 To: MOSELEY,POOL,LI,LIU,SMOCK,VAXMAN Subj: (Dr. Moseley, this is a description of "computer science". --Scott) The following highly-specialized, and complex, areas of study are often considered within the realm of "computer science": - Artificial Intelligence (problem solving, pattern recognition, etc.) - Cognitive Science (Conceptual Dependency theory introduced at Yale) - Compiler Theory (study of automated computer-language translation) - Computability Theory - Computational Linguistics - Computer Graphics (modeling/manipulation of visual data) - Computer Numerical Methods (matrix algebra, finite-difference calculus) - Computer Simulation (modeling of deterministic/stochastic processes) - Ergonometrics (human-factors studies) - Information Science (database design, representation/organization) - Management Science (computerized resource/personnel management) - Robotics (Cybernetics) - Switching Circuit Theory (computer logic-circuit design) From: VAXMAN 19-APR-1984 18:48 To: OPERATOR,LI,MOSELEY,HEYER,POOL,VAXMAN Subj: NASA/JSC National Mmgt. Assoc. Annette, I went to the formation meeting of the NASA/JSC Chapter of the National Management Association (NMA). They announced that the chapter was for U. S. Government employees only -- contractors have their own chapters & Ford Aerospace is starting a chapter now. For the NASA/JSC Chapter, there are plans for 10 meetings per year at the Gilruth Recreation Center. Dues are a one-time fee of $10.00 & $78.00 per year (tax-free) for speakers, hand-outs & the dinner meetings. Their next meeting, "Charter Night", is planned for Tuesday night, 29-May-84, in the Gilruth banquet room. Dr. Moseley & Bob Heyer would probably like to join -- Dr. Griffin gave the introductory speech and kept referring, though reluctantly, to management as a science. --Scott From: VAXMAN 11-APR-1984 15:21 To: MOSELEY,HEYER,OPERATOR,LI,VAXMAN Subj: Ada Software Study. Dr. Moseley, I left a message with J. R. Garman (483-4788) of the NASA Ada Steering Group requesting any information he has about Ada-based word processing. He is working on obtaining the SofTech "Ada Language System" (VAX/VMS) which was developed for the U.S. Army entirely under goverment contract as public domain software ("free"). Perhaps the Army has already requested word-processing software as part of their contract with SofTech. I'll keep you posted of any new results as they occur. --Scott Sibley, Ford VAX System Manager From: VAXMAN 11-APR-1984 16:33 To: MOSELEY,HEYER,LI,OPERATOR,VAXMAN Subj: Computers Running Ada. Dr. Moseley, The following computer(s) run Ada software packages: SofTech: VAX/VMS and Military Computer Family (MCF) TeleSoft: VAX/VMS, IBM PC, IBM 370, MC68000-based PC Intellimac: VAX/VMS, MC68000-based PC, Apple LISA Data General: ECLIPSE MV-series (MV4000/MV8000/MV10000) Rolm: HAWK/32 (military equivalent of DG ECLIPSE MV series) More information on Ada is under "INFO": $ INFO ADA -ALL --Scott Sibley, Ford VAX System Manager From: VAXMAN 24-MAY-1984 13:06 To: OKRINSKY,OPERATOR,VAXMAN Subj: RE: Acronyms. Kimbra, The words "VAX" and "VMS" are acronyms of Digital Equipment Corporation: VAX - "Virtual Address eXtension", the main computer hardware VMS - "Virtual Memory System", the operating system software Both terms are probably also trademarks belonging to Digital. --Scott Sibley, Ford VAX System Manager