PAGESWAPPER MicroVAX at DECtown A new VAX processor was displayed but not demonstrated at a DEC trade show in Boston August 29-31. Labeled the "MicroVAX", the cabinet was the same style as a Micro-PDP11, and could have been empty for all the visitors could see, since the cover was not removed. 1 PAGESWAPPER - September 1983 - Volume 5 Number 3 MicroVAX at DECtown The DEC employees assigned to explain (guard?) the MicroVAX started off by warning that they were only authorized to say a few limited things about the machine, and they kept true to their mandate! Not a word about disk size (in the cabinet), memory size, or processor speed. They said the processor was "VMS-compatible", which they distinguished from the customer-suggested term "subset" by saying that any VMS unprivileged program which runs on a 780/50/30 would run on the MicroVAX. Further they said that programs developed on the MicroVAX could be run on the other processors (not such a great leap of faith, but when a customer said that was an implicit statement that the machine had enough capacity to do program development, there was no dispute from the DEC folks). The machine was described as having a Q-bus, and under questioning a DEC guardian (with a small G) said the processor would not run in compatibility mode. We don't give prices in the Pageswapper, but it is interesting to note that DEC wasn't giving them at the trade show either (at least not for the MicroVAX or the VT200 family described below). First customer ship for the MicroVAX is planned to happen by July 1984, and the official product announcement will be "soon". Another VAX on display was what some customers referred to as an 11/725. The sign I saw did not refer to it by that number, but said "New Low cost VAX (LCN) with New 8" Disk (AZTEC)". That machine is apparently a repackaging of the 11/730 processor, in a shorter cabinet. The forum for all of this was called DECtown, and was divided according to DEC internal structure into various display areas. Thus VAXs of various flavors were spread all over the floor, devoted to particular end-user interests, and quite secondary to the prime emphasis of showcasing software and pretty terminal cabinets. Those terminals were very often from the VT200 family, finally on display. There was one booth dedicated to the VT200 terminals, but no literature to carry away. From what was shown though, there were basically three models: o VT220 - successor to the VT100 This is the bottom of the line, and one DEC marketeer at the VT200 booth claimed it was actually patterned after the VT102 and therefore would support character-insert mode. He seemed a little shaky on that point though, so check it out yourself. Although patterned after the DEC personal computer cabinetry, the tube on this one is quite a bit bulkier, because all the electronics are in the tube housing. Only two pieces, but more bulk on top of the desk. 2 PAGESWAPPER - September 1983 - Volume 5 Number 3 MicroVAX at DECtown o VT240 - successor to the VT125 (and Textronix?) One giant step for graphics fans, as this supports not only REGIS, but also Tektronix 4010/4014 protocol (I think I got the numbers right). Just monochrome, but the tube housing is back down to the size used on the DEC personal computers, because they put the electronics in a separate box (considerably smaller than the one for a DEC personal computer, but still one you might want to consider putting under the desk). o VT241 - color inside a DEC cabinet Well, this one has the separate electronics box and also a tube housing even bulkier than the VT220. It has RGB output for an external monitor and does RGB output to its own screen. The keyboards are all the DEC personal computer type keyboard. Something not actually revolutionary, but a lot of fun was a little box called DECtalk, which was a fairly stand-alone speech synthesizer. There were instances of it connected in various display areas, but my favorite was a phone booth where the demonstrator would dial up using just a telephone and via touch-tone commands direct the computer read his mail to him. Not the world's most human voice, but understandable and no traces of a Swedish accent. One item NOT in DECtown was a terminal server. I say that because there was a box labeled "terminal server", but its keeper admitted it had no software in it to perform that function. 3 PAGESWAPPER - September 1983 - Volume 5 Number 3 In this issue... In this issue... MicroVAX at DECtown . . . . . . . . . . . . . . . . 1 In this issue... . . . . . . . . . . . . . . . . . . 4 Editor's Workfile . . . . . . . . . . . . . . . . . 5 Letters to the Editor . . . . . . . . . . . . . . . 6 On Commercialism . . . . . . . . . . . . . . . . . . 7 The DBMS Monitor . . . . . . . . . . . . . . . . . . 9 LUG Agenda . . . . . . . . . . . . . . . . . . . . 26 LUG Meeting Report . . . . . . . . . . . . . . . . 27 UNLUG? . . . . . . . . . . . . . . . . . . . . . . 32 Preliminary Roadmap for Las Vegas . . . . . . . . 33 INPUT/OUTPUT . . . . . . . . . . . . . . . . . . . 57 DECUS Symposia Proceedings . . . . . . . . . . . . 64 INPUT/OUTPUT Submission Form . . . . . . . . . . . 65 System Improvement Request Submission Form . . . . 67 General material for publication in the Pageswapper should be sent (US mail only -- no "express" services please) to: Larry Kilgallen, PAGESWAPPER Editor Box 81, MIT Station Cambridge, MA 02139-0901 Preference is given to material submitted as machine-readable text (best is Runoff source). Please do not submit program source, as that is better distributed on the VAX SIG tape. Material for "The DBMS Monitor" section of the Pageswapper (pertaining to VAX-11 DBMS) should be sent to: Julie Llewellyn United Technologies Microelectronics Center 1365 Garden of the Gods Road Colorado Springs, CO 80907 Change of address, reports of non-receipt, and other circulation correspondence should be sent to: DECUS U.S. Chapter, MRO2-1/C11 Attention: Publications Department One Iron Way Marlborough, MA 01752 USA Only if discrepancies of the mailing system are reported can they be analyzed and corrected. 4 PAGESWAPPER - September 1983 - Volume 5 Number 3 Editor's Workfile Editor's Workfile by Larry Kilgallen, Pageswapper Editor A question came up in a SIG steering committee discussion to which I had an answer, so I thought I would answer it here as well in case anyone else is in the same position. The question is "Has anyone seen the Spring 1983 SIG Tape?" (the one discussed on page 14 of the August Pageswapper). The answer is a definite YES - the tape librarian for my LUG has received it and has started distributing it, so by the time you read this it should be true for your LUG as well. That word "should" is used not on the basis of some guarantee but as my estimation of how quickly we all should act when sitting on software for which the next person is waiting. A great thing happened this month - I got the August Pageswapper back in the mail before submitting the September one to the Decus Office. Not yet enough time for readers of the August issue to have responded, but it does represent a great deal of progress. I am still having a very hard time drumming up support for the Pageswapper in the form of articles for publications. Joe Angelico told me he had gotten no mail in response to his request for suggestions on the Las Vegas Campground. I told him that's to be expected; I hardly get any mail in response to the Pageswapper in general. I know you are out there; over 3400 have signed up for the Pageswapper now that it cost money. When I meet SIG members they always tell me they read it, but the quality of what can be read depends on whether YOU send in the article on that particular item of interest you haven't heard about elsewhere. If I have made you feel guilty but you can't think of a subject, how about taking a piece of the SIG tapes. Write a review, critical appraisal, or just plain introduction to some set of programs on the tape which are familiar to you. Yes, there are documentation files on the tape, but there may be some LUG members who have not bothered to get the tape because they do not know what is on it, or what use it might be in their own situation. Has anyone been aided by a SIG tape program, or is there one you absolutely depend upon in your shop? Write to the Pageswapper about it. My final note is a warning for system managers to guard your VAX. There has been a rash of break-ins and attempts around the country lately, and in the case of VMS some installations have apparently not bothered to change the passwords on the three accounts which come shipped with the machine. The security expert for one multi-VAX organization I know did a survey of his 5 PAGESWAPPER - September 1983 - Volume 5 Number 3 Editor's Workfile organization's machines and was shocked to find that some of those did not have the passwords changed. The expert spends his time worrying about much more sophisticated security issues than changing the factory password, but some of the autonomous system managers in the organization were obviously much less diligent. A particular target of recent penetration attempts seems to be machines connected to packet switched networks; I would presume that this is because the odds of finding a computer rather than a human at a randomly generated number are so much greater. Larry Kilgallen, Pageswapper Editor Letters to the Editor Dear Larry: The VAX System SIG cassettes from the DECUS Spring '83 Symposium are the greatest thing since sliced bread. They would be greater if the handouts were available that went with the sessions. I'd pay up to about $100 for a reasonably complete set. I'm sure other people would be interested. Can you help? Ask around? Publish the results? Sincerely, Peter P. Zadarlik Vice President - Information Resources Response Well I did ask around, and I have some good news and some bad news. The good news is that the DECUScope issue mailed in July to all members offered the Saint Louis handouts for sale. The bad news is that the orders had to be in by Friday August 19th. Maureen Levine of the Decus staff said that if someone was very lucky they might be able to try ordering late on the off chance there was an overprint. 6 PAGESWAPPER - September 1983 - Volume 5 Number 3 On Commercialism On Commercialism by Ray Kaplan Proceedings and Session Notes Publications Committee A recent PAGESWAPPER contained a letter from Dave Johnson of the BAYVAX LUG that complained about the presence of third party vendors in the exhibit hall at the St. Louis Symposium. This is an answer to Dave's letter. As editor of the DECUS U.S. Chapter Symposium Proceedings, I find myself right in the middle of the DECUS commercialism "battle". Ever since our decision to combine the Mini/Midi Symposium papers with the DEC System 10/20 Symposium papers, there has been big trouble in proceedings land. The two groups have distinctly different flavors, and it is a real problem to try to apply a commercialism policy evenly to them all at once. As a veteran of "DECUS commercialism wars" that date back to the time when the VAX SIG formally objected to the DECUS U.S. Chapter Publications commercialism policy in Miami, I think that I am in a good position to chat about this hot topic. First, the matter of the third party vendors on the display floor at the St. Louis Symposium. DIGITAL owns that portion of the symposium, not DECUS. While DECUS has an influence on DIGITAL, DECUS does not control the display area. Many a hot battle has raged over the decision to even allow DIGITAL to come show off their wares. My contention is that DECUS would be worse off if DIGITAL did not bring their show to our Symposia. The DIGITAL person who is responsible for the DECUS interface into DIGITAL's Central Engineering Organization has been quite successful at convincing DIGITAL management to allow even more engineers to come to our Symposia. I am sure that this is due, at least in part, to DIGITAL's perception that DECUS wants to be a "good partner" to DIGITAL. I will bet that DIGITAL looks at this as an opportunity to show THEIR user group all of the things that are new. I will bet that OUR user group wants to continue to see DIGITAL participate on such a grand scale. I, for one, want to see DIGITAL bring their display to our Symposia. I assure you, if DECUS had to pay to have DIGITAL come to our Symposia, we would not have anywhere near as nice a display as we have now. A good portion of the DIGITAL people who come to Symposia would not be there if it were not for the DIGITAL display floor. The bone of contention is, then, the presence of third party software vendors on the display floor. Contrary to popular belief, no "restraint of trade injunction" was issued as a result of complaints by vendors that were not included in the 7 PAGESWAPPER - September 1983 - Volume 5 Number 3 On Commercialism DIGITAL exhibit. Fact of the matter is, that the third party vendors that were there all had signed marketing agreements with DIGITAL. DIGITAL markets third party software through this agreement. Display floor space was by invitation to a select number of these vendors. Some of the invited vendors turned the invitations down, and some of the vendors accepting invitations could not make it. How did the whole thing get started? I am told that someone said "hey, why don't we try this". Since DECUS is in the business of serving its membership the answer was "sure, lets try it". Well, needless to say, the amount of noise generated caused a reassessment of that decision. As a result of the outcry, I am told, there will no longer be any third party participation on the DIGITAL display floor. The sad part is that most of the complaints came from vendors who did not have marketing agreements with DIGITAL. I would say that this is a fair loss to the society, since some of us do not have a chance to see any of this software anywhere else (including DEXPO). The broader question is, of course, who gets to use DECUS as a "sales tool". As your Proceedings editor, my attitude is that if anyone does, that someone is going to be ME! After all, a well defined market segment like the DECUS membership could be worth quite a lot to any marketing effort! I want to make sure that DECUS stays a TECHNICAL society, devoted to the exchange of information among the DIGITAL Computer user community. To that end, I believe that DECUS must have a "special relationship" with DIGITAL. That "special relationship" currently is responsible for the very existence of DECUS. In my opinion, DECUS should be tolerant of "experiments" that try to disseminate information to the user community in new ways. 8 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor The DBMS Monitor Ken Moore of DEC has sent a copy of the slides used in the Spring 1983 symposium sessions: VAX-11 DBMS Futures and VAX-11 DBMS - DB Design and Tuning. The figures that accompanied the slides are not available. Please send material for the DBMS Monitor to: Julie Llewellyn United Technologies Microelectronics Center 1365 Garden of the Gods Road Colorado Springs, CO 80907 Items submitted to the DBMS Monitor will be forwarded to the VAX Pageswapper which may reprint them for wider distribution to the DECUS community. VAX-11 DBMS Database Design and Tuning ---------------------------------------------------------------- ---------------------------------------------------------------- VAX-11 DBMS Database Design and Tuning Outline * Three Number 1 Rules * Database design * Program design * Miscellaneous tips ---------------------------------------------------------------- ---------------------------------------------------------------- Three Number 1 Rules 1. Is this a DBMS application? 2. VAX/VMS Tuning 3. Proper logical database design ---------------------------------------------------------------- ---------------------------------------------------------------- 9 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor Three Number 1 Rules Is this a DBMS application? * Complexity of schema? * Willing to pay for data independence, integrity, consistency? * If not, use RMS. ---------------------------------------------------------------- ---------------------------------------------------------------- Three Number 1 Rules VAX/VMS Tuning * VAX configuration - Enough disk, memory, CPU * More rather than larger disks * VMS tuning - Swapping, page fault rate, I/O rates. Check for resource waits. * VMS parameters - Automatic working set adjustment, ACP caches. * Install DBMSHR, programs, DTRSHR (if you have it) ---------------------------------------------------------------- ---------------------------------------------------------------- Three Number 1 Rules Proper logical database design * Minimum number of sets * Calc or sorted set for key searches * Nothing DBMS can do when database design is wrong ---------------------------------------------------------------- ---------------------------------------------------------------- Database Design Life Cycle 1. Requirements analysis 2. Logical design 10 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor 3. Physical design 4. Operational system 5. Modification ---------------------------------------------------------------- ---------------------------------------------------------------- Database Design Requirements analysis * Flow of information - Objects, processes * Security * Reliability * Performance ---------------------------------------------------------------- ---------------------------------------------------------------- Database Design Logical design * Entities (Records) * Entity Attributes (Items) * Relationships (Sets) * Other (Areas) * View integration vs. global design ---------------------------------------------------------------- ---------------------------------------------------------------- ---------------------------------------------------------------- ---------------------------------------------------------------- ---------------------------------------------------------------- ---------------------------------------------------------------- Logical design Transaction requirements 11 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * Affected records * Relationships used * Frequency * Priority ---------------------------------------------------------------- ---------------------------------------------------------------- Logical design Transaction Load * Compute number of I/Os * Compute volue of I/O * Weight by frequency and priority * e.g., Find the supervisor of the employee responsible for a part - I/O = 1.2 (PART) 1 (EMPLOYEE) 1 (DIVISION) 1 (EMPLOYEE) = 4.2 - I/O volume = 130 75 45 75 = 325 bytes - Real I/O volume = I/O * I/O-Clustersize ---------------------------------------------------------------- ---------------------------------------------------------------- Logical design Tradeoffs * Collapse hierarchies * Split records * Add entry points ---------------------------------------------------------------- ---------------------------------------------------------------- Logical design Shadow Clustering 12 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor +------------+ | Record_A | 10 occurrences +------------+ | Set A_B v +------------+ | Record_B | 100 occurrences +------------+ | Set B_C v +------------+ | Record_C | 1000 occurrences +------------+ ---------------------------------------------------------------- ---------------------------------------------------------------- Logical design Sorted Sets * Load in random order - Space optimal * Load in descending order (ascending set) - Load, retrieval optimal * Don't sort on dates - Use ORDER LAST, if possible ---------------------------------------------------------------- ---------------------------------------------------------------- Physical Design Storage Schema * Cluster via most frequent set * Dynamic allocation * Record placement * Set order * Numeric strings * Index node size ---------------------------------------------------------------- ---------------------------------------------------------------- Physical Design Database Parameters 13 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * DBO/SHOW STATISTICS * Short transactions * Page vs. I/O cluster size * Integral number of pages per buffer * Page fault rate ---------------------------------------------------------------- ---------------------------------------------------------------- Program Design General Considerations * Concurrency requirements * Short vs. long transactions * Load programs ---------------------------------------------------------------- ---------------------------------------------------------------- Program Design DML Statements * COMMIT RETAINING * FIND vs. FETCH * Item list * CALC or sort key for FIND USING * PLACE * ACCEPT ---------------------------------------------------------------- ---------------------------------------------------------------- Miscellaneous * Read the documentation - Especially DBA and Performance Guides * Create oversize database 14 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * Avoid data conversions/scaling * Use hardware data types * RUJ location * One large vs. many small disks * COBOL DML, FDML vs. Callable DBQ 15 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor Future Features of VAX-11 DBMS ---------------------------------------------------------------- ---------------------------------------------------------------- VAX-11 DBMS Future Features Overview * Security - Security schemas - Value-based security - Access control - Security audit * Performance * DML features * Utilities * Packaging and doucmentation * The far future and never-never land ---------------------------------------------------------------- ---------------------------------------------------------------- Database Security Problems and goals * Privacy of data * Control DML commands * Control DBO commands * Provide security audit trail and alarms * Provide "real" security * Compatibility with VMS or CDD 16 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * Compatibility with VAX-11 DBMS V1 * No significant performance penalty ---------------------------------------------------------------- ---------------------------------------------------------------- Database Security Solution * Security schema * Command authorization list * Audit trail and alarms * Run in exec and kernel mode * Uses ACLs and UICs * Default is "open" database (but "closed" security schemas) * Bitmaps and CHECK evaluator ---------------------------------------------------------------- ---------------------------------------------------------------- Database Security Non-goals * Timing channels * Provably secure DBMS * Non-discretionary controls * Database meta-data ---------------------------------------------------------------- ---------------------------------------------------------------- Security Schemas Goals * Purpose - Defines an allowed way of accessing the database * Selection of proper security schema based on user attributes 17 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * Verb security * Levels of security granularity * Value-based security * Compatibility with DBMS V1 ---------------------------------------------------------------- ---------------------------------------------------------------- Security Schemas Mapping * User requests database-name, subschema * Security schema selected based on user-attributes (UIC) +-----+ | | | S | | e S | | c c | +-----------+ | u h | +-----------+ +-----------+ | Subschema |--| r e |--| Schema |--| StoSchema |--Database +-----------+ | i m | +-----------+ +-----------+ | t a | | y | | | +-----+ ---------------------------------------------------------------- ---------------------------------------------------------------- 18 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor Security Schemas General Format SECURITY SCHEMA NAME IS FOR SCHEMA ... AREA NAME IS {GRANT | DENY} PERMISSION FOR RECORD NAME IS {GRANT | DENY} PERMISSION FOR {ERASE | FIND | GET | MODIFY | STORE} SCOPE IS ITEM NAME IS {GRANT | DENY} PERMISSION FOR {GET | MODIFY} SCOPE IS SET NAME IS {GRANT | DENY} PERMISSION FOR {CONNECT | DISCONNECT | RECONNECT} OWNER IS MEMBER IS {GRANT | DENY} PERMISSION FOR {CONNECT | DISCONNECT | RECONNECT} SCOPE IS ---------------------------------------------------------------- ---------------------------------------------------------------- Security Schemas Read-only Schema | SECURITY SCHEMA read_only FOR parts | | GRANT CONCURRENT RETRIEVAL | GRANT PROTECTED RETRIEVAL | GRANT EXCLUSIVE RETRIEVAL | GRANT BATCH RETRIEVAL ---------------OR-------------- | SECURITY SCHEMA read_only_verbs FOR parts | | GRANT FIND | GRANT GET | GRANT IF ---------------------------------------------------------------- ---------------------------------------------------------------- Value-Based Security 19 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor Philosophy ---------------------------------------------------------------- ---------------------------------------------------------------- Value-Based Security Implementation * SCOPE clauses for records, items, sets * Update outside user scope = security violation * Retrieval outside user scope = End_of_collection * FIND ALL returns visible records * Set currency not updated if set SCOPE is false * EMPTY, MEMBER, TENANT conditions operate on visible members ---------------------------------------------------------------- ---------------------------------------------------------------- Value-Based Security Example SECURITY SCHEMA im_group FOR personnel RECORD employee SCOPE salary LE 30000 SET works_for OWNER department MEMBER employee SCOPE dept_cost_center IN department EQ "3N3" AND salary IN employee LE 30000 ---------------------------------------------------------------- ---------------------------------------------------------------- Access Control ACLs * Ordered list of entries * Each entry has identifier/rights 20 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * Evaluated non-hierarchical, first-match ---------------------------------------------------------------- ---------------------------------------------------------------- Access Control Database Operator Commands * Command Authorization List (CAL) in each database * Each command has ACL * Command groups: USER, MANAGER * No CAL for /CREATE, /MONITOR, and DBO CDD commands * Controlled with DBO/GRANT ---------------------------------------------------------------- ---------------------------------------------------------------- Access Control User Execution List (UEL) * UEL in each database controls security schema mappings * UEL is an ACL that takes an identifier and output a security schema * Controlled with DBO/PERMIT ---------------------------------------------------------------- ---------------------------------------------------------------- Security Audit Audit Trails * Written during ACL success/failure access * Written for BIND, UNBIND, DML verbs, DBO commands * Contains UWA data, completion status, user context * Auditable objects controlled via /AUDIT options * Auditable objects are verbs, records, sets, and DBO commands ---------------------------------------------------------------- ---------------------------------------------------------------- 21 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor Performance Space Area Management * Improves free space search time when nearly-full and "clumped" * Intervals and thresholds are setable * Optional, but fixed for the life of the database ---------------------------------------------------------------- ---------------------------------------------------------------- Performance Boolean RSE * FIND/FETCH WHERE * Boolean has AND, OR, NOT, EQ, NE, LT, GT, GE, LE, CONTAINS, MATCHES * CONTAINS is case insensitive and MATCHES is case sensitive * MATCHES includes "*", "%", and "^" (quote) * Index and CALC set optimization WITHIN SET ---------------------------------------------------------------- ---------------------------------------------------------------- Performance Miscellanoues * CPU improvements for large schemas * Item mover optimizations * Buffers held across transactions with COMMIT RETAINING ---------------------------------------------------------------- ---------------------------------------------------------------- DML Features DML Statements * READY BATCH RETRIEVAL (snapshot) - Snapper sees consistent view without deadlocks 22 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor - Writers put before-images into the database - Minimal performance degradation due to snapshot cache * READY BATCH UPDATE (disable RUJ) * READY WAIT * FIND/FETCH FOR UPDATE * Call DBM$STATS * DML statistic audit trail ---------------------------------------------------------------- ---------------------------------------------------------------- DML Features Multiple Databases per Process * One stream per compilation unit * Initial support for FORTRAN, PL/I, BLISS, MACRO * Later support for C, COBOL, PASCAL * DBQ - BIND ON STREAM, SET STREAM ---------------------------------------------------------------- ---------------------------------------------------------------- Utilities ---------------------------------------------------------------- ---------------------------------------------------------------- Utilities ---------------------------------------------------------------- ---------------------------------------------------------------- LOAD Utility Load Language 23 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor * Record and item definitions * Initial SORT or PLACE * Set significant items * Set insertion by value or by CONNECT with boolean * Load sequence define by nested, ordered loops ---------------------------------------------------------------- ---------------------------------------------------------------- LOAD SEQUENCE Example Summary LOAD SEQUENCE IS LOOP class ALL part WHERE part_code EQ class_code ENDLOOP ALL vendor ALL component ALL employee LOOP supply ALL quote WHERE part_id OF supply EQ part_id OF quote AND Vend_name OF supply EQ vend_name of quote ENDLOOP ALL division ---------------------------------------------------------------- ---------------------------------------------------------------- Utilities Summary * RECALC * Add areas * Large schemas * On-line backup (optional) * On-line verify ---------------------------------------------------------------- ---------------------------------------------------------------- 24 PAGESWAPPER - September 1983 - Volume 5 Number 3 The DBMS Monitor Packaging and Documentation * Documentation will be more task-oriented * New "Database Design Guide", "Security and Integrity Guide", "Database Tuning and Restructuring Guide" * New run-time only kit * Distributed on one piece of "large" media ---------------------------------------------------------------- ---------------------------------------------------------------- VAX-11 DBMS Futures The Far Future * Cluster databases * Design tools * In-place restructuring * Journalling improvements * Set selection by value * New data types * Redefines ---------------------------------------------------------------- ---------------------------------------------------------------- VAX-11 DBMS Futures Never-Never Land * Relational DML * Small (<20MB) disk systems * Distributed across low-bandwidth links 25 PAGESWAPPER - September 1983 - Volume 5 Number 3 LUG Agenda LUG Agenda The following LUG meeting information is published with the understanding that Pageswapper readers will receive it too late to attend the meetings. The purpose, rather, is to share meeting topic ideas among LUGS. o BAYVAX LUG (San Francisco area) - Thursday August 11, 1983 From 9 am to noon at Lockheed (Sunnyvale). Dave Johnson of Lockheed will talk about how to use QIO and other system services from higher level languages (Fortran, Pascal, etc.) In about 1 hour he will cover some information in the manuals which may not be obvious to the novice user. We will then have Richard Case of DEC give us an overview of Digital's office automation strategy, with detailed coverage (and a live demo) of the "All-in-One" software package. His talk will take about an hour. We will also have the usual Forum and Pass-the-Paper. o LLnLLUG (Lawrence Livermore) - Wednesday, August 24, 1983 Robyn Allsman and the Networks SIG will present four speakers on "Local Area Networks at LLNL." The speakers will be: - Tom Brengle - Review of options considered designing the MNET Ethernet system - Dennis O'Brien and Peter Bego - Integrated Computer-Aided Engineering Network (iCAEn) Status report and performance measurement - Kevin Blackwell - Integrating CAD/CAM into iCAEn - John McCall - AdmiNet - Experiences using the Sytek broadband local area network 26 PAGESWAPPER - September 1983 - Volume 5 Number 3 LUG Meeting Report LUG Meeting Report o LLnLLUG (Lawrence Livermore) Newsletter - July 21-22, 1983 Trip to DEC, Colorado Springs by Gary Kessler On 21 July, thirteen people from the Lab met with personnel from Digital at their manufacturing plant in Colorado Springs, Colorado. The Colorado Springs facility is about seven years old and comprises 750,000 square feet. Their charter is to design and manufacture large mass storage devices, particularly the RAxx family of disk drives and controllers. Specifically, they build the RA80, RA81, RA60, UDA50 and HSC50. (More information on these devices is given below.) Colorado Springs is also the "home" of the North America Remote Diagnostic Center and Telephone Support Center. We met with the following people from Digital: Barbara Crane from Advanced Development talked about the charter of the engineering organization and disk head technology. Paul Massiglia, RA81 Product Manager, discussed the technical features of the RA81 disk. Dennis Shaw, Customer Services Support Manager of Maintainability Engineering, discussed how the maintenance of the RAxx family is built into the design of the devices. Finally, Bob Blackledge, HSC50 Hardware Engineering Manager, discussed the HSC50 and VAX cluster concepts. Lab attendees included Roger Anderson, Gus Dorough, Dave Hunt, George Pavel, Fred Strange, and Allan Van Lehn. Dick Daley and Jeanne Kline from the Oakland DEC office were also there, as were six people from Lockheed, Sunnyvale. The following information are my notes, comments and projections. Some of the information was from the speakers' presentations, some from personal discussions, and some from my own information or best guess. Although there was no non-disclosure information in the formal presentations, I have avoided quoting anyone. DEC's engineering groups, in fact, DEC itself, does not do a lot of pure research. They depend on research going on elsewhere. Engineering also maintains 27 PAGESWAPPER - September 1983 - Volume 5 Number 3 LUG Meeting Report responsibility over products throughout their entire life cycle as a product. That is, engineering does not relinquish control to field service once a product is released. The RAxx disk family was purposely designed to allow reuse of many parts to bring down the long-term production costs. E.g. the RA80 and RA81 use mostly the same pieces; some electroncs, the disk and the heads are different. There are approximately 300 process steps involved in making a head slider. Some of these new ideas and technologies were discussed. The most obvious problem in making heads and disks with higher and higher information density is the flying height of the head. Horizontal and vertical recording of data on the disk was also mentioned. Vertical recording allows more information on a disk, but it is so "stable" that there is a very small magnetic field to read. Thus, heads must fly very close. Since many of the heads that are manufactured fail in tests, some of the new head sliders are being built with 2 read/write heads. This increases the chance that one of the heads is good. Also, it provides a mechanism for future development of sliders with 2 R/W heads acting in parallel. Thin film heads are coming in the future, for increased transfer rate, lower flying height, etc. A brief discussion was held on how the disk heads are positioned. Early disks put servo position data on one side of the disk's recording surface; the other side was for the customer's data! This "dedicated" servo method is utilized on the RA80. "Embedded" servo information, as used on the RA60, interleaves servo and customer data on the recording surfaces. Finally, the RA81 uses a combination of the two. Dedicated servo data provides for gross movements of the heads, while embedded data is for fine tuning. Paul Massiglia, RA81 Product Manager, discussed further the Digital Storage Architecture (DSA). Digital entered the big disk manufacturing fracus specifically to compete with IBM and CDC. One of the most valuable functions of DSA is that all DSA devices use the same driver "language". Thus, the CPU pokes the controller, which pokes the device. The CPU does not know, nor care, what disk is out there; it communicates with the controller only. 28 PAGESWAPPER - September 1983 - Volume 5 Number 3 LUG Meeting Report The RAxx disk family is currently comprised of three models. The RA80 is a 121 MB fixed Winchester disk, the RA81 is a 456 MB fixed Winchester, and the RA60 is a 205 MB removable. (NOTE: The R80 disk is a 124MB fixed disk. (This is the disk that comes with 730s.) This essentially is an RA80, but NOT a member of DSA. The 3 MB were sacrificed to make the RA80 a DSA device.) The UDA50 was the first controller for DSA, and provides the interface between RAxx disks and a PDP-11/44 or /70, a VAX or a DECSYSTEM-20. (These CPUs are referred to a "compute servers" by the disk types!) Support is provided for VMS, TOPS-20, RSX, RT, RSTS(?), and UNIX. The UDA50 allows all RAxx devices to be connected by a star configuration, rather than a daisy chain. The advantage is that any disk may be brought on-line or off-line without affecting the others. In a daisy chain, bringing the second disk off-line will bring the third, fourth, etc., off-line with it. The UDA and HSC can each control up to 4 devices (Pageswapper editor's note: more on an HSC50 with additional plug-in modules). On a 750, 2 UDA50s may plug into 1 UNIBUS. A large portion of the disk space is "reserved" for error recovery. A disk sector is comprised of 4 copies of a 32-bit header, 512 bytes of data (576 bytes for DECSYSTEM-20), then 186 bits of ECC/EDC (Error Correcting Code/Error Detection Code). The ECC is used by the drives, whereas the EDC is used by the controllers. No bad data is (purposely) sent to the CPU. four copies of the header are used in case one is destroyed; the claim is that "democracy" is used to determine which header is correct. (No statement as to what to do in case of a tie. I've always thought that democracy worked best when an odd number of people were around; in fact, a prime number of people!) The 186 bits of ECC/EDC are comprised of a 170 bit "Solomon" ECC code and a CRC-16 EDC. The Solomon code can correct up to 8 discontiguous errors in a disk sector, or bursts of up to 80 bits in error. The claim is that as densities increase, errors tend to be of 1 or 2 bits. If a CRC error is detected by the controller, retransmission will be attempted 'N' times, were 'N' is dependent upon disk type. E.g., the RA60 is removable, thus is more susceptible to environmental changes. Most RA60 errors are soft, so more re-tries are allowed. Conversely, the RA80/81 are sealed, thus a persistent error may well be hard, so 'N' is lower than that for the RA60. 29 PAGESWAPPER - September 1983 - Volume 5 Number 3 LUG Meeting Report One of the other nifty features of the RA80/81 is in terms of maintenance. To run diagnostics on the RA80, the top of the box must be opened, and some thumb-wheels on a PC board twiddled with. The RA60 and RA81 use a standard ASCII port and a hand-held terminal (or VT100)! In a number of discussions, the Fujitsu Eagle disk drive was mentioned as competing with the RA81 (Or perhaps, vice versa.) In any case, George Paval "owns" a bunch of Eagles. Between various pieces of marketing information, we have pieced together the following RA81/Eagle comparison: RA81 Eagle Internal Drive Error Log No Periodic Fault Isolation No accessories for repair Cable and extender required Separate motor Motor in HDA 248 ICs 432 ICs Proven MTBF: 10Khr Claimed MTBF: 10Khr Calculated MTBF: 13.5Khr Calculated MTBF: 10.5Khr Drive Diagnostics Host Diagnostics Offline Test Host System Test 235 Fault Codes 16 Fault Codes No special tools required 3 special tools Hand-held terminal for Oscilliscope & meter for repair repair Isolates faults Detects faults 7 major Field Replaceable 11 major Field Replaceable Units Units 3 PC Boards 8 PC Boards No Field Adjustments 10 Field Adjustments 425 Connections 1100 Connections 456MB (formatted) 414MB (formatted) 2.2MB/sec transfer 1.9MB/sec transfer rate rate 36ms access time 25ms access time In discussions of DSA, it was mentioned that there is a longer cycle time to get the first product of a family out (like the RA80), but that others came out more quickly. In showing the time lines for design, production and release of new RAxx disks, it was implied that a new RAxx fixed disk was coming. From the bits and pieces that we were scattered, it appears than an RA81 follow-on is coming, and will cost about what an RA81 costs, will have about double the capacity (800-900MB), and will be available in 12-15 months. It was also implied that a disk with capacity over 1.5GB is probably being designed now, for release in another 2 years or so. 30 PAGESWAPPER - September 1983 - Volume 5 Number 3 LUG Meeting Report The HSC50 intelligent controller provides a high-speed interface between CPUs and mass storage devices. The cluster concept requires that CPUs and disks be able to go on- or off-line without affecting the rest of the cluster. Thus, the HSC provides redundant bus connections all around, so that one may fail without bringing down the cluster. Devices on a cluster are all connected via a star coupler, where no devices are more than 84 meters apart. The claim was made that 15 VAXs and 1 HSC50 is the best balance of HSCs to "compute servers". The HSC50 performs "rotational optimization" on the disk by continuously checking the head position. It will send data to the controller in the optimal fashion for the disk and the head; the controller will put it back in order, if fragmented, prior to transmitting to the CPU. The HSCs also handle dual-ported disks. Dual-porting is not dynamic. Thus, if controller A controls a disk, controller B cannot get to it. If A fails, however, we want B to be able to gain access. The HSCs provide static dual-porting with failover. That is, if A fails, then control of the disk automatically goes to B. On Friday, about 6 or so of us went to the Remote Diagnosis Center. Currently, remote diagnosis is available for the DECsystem-10, DECSYSTEM-20, PDP-11/44 and 11/70, and VAX-11/750 and 780. The VAX-11/730 is "remote diagnosable" (that's a quote!), but this is typically only used by field service. The VAX group is comprised of 17 people, working 7 days a week, 24 hours/day. Many of these people get "stolen" by the Telephone Support Center, which was the next group we saw. All incoming calls are checked on the computer for a valid ID number, then screened by size of system - large is 10s, 20s and VAX, everything else is small. TSC was in the midst of moving across the street the day we were there, so we were unable to see them really in action, but we were able to chat with some of the folks. Some members of our group spent some time talking to some of the RSX TSC people. All-in-all, it was nice to see that Digital is actually working in the direction that one might have extrapolated from their past track record. It was good also to have some input on their directions. Gary C. Kessler ELECTRONICS ENGINEERING Lawrence Livermore National Laboratory 31 PAGESWAPPER - September 1983 - Volume 5 Number 3 UNLUG? UNLUG? by Ray Kaplan As an active DECUS member with DECUS U.S. Chapter Leadership responsibilities, I have trouble trying to explain this, but here goes. Out here in Tucson, we have a generally licensed DECUS LUG called the Tucson User Group. Up until the last few months, the TUG LUG has been doing it's best to serve the needs of the local DECUS community of 8s, 11s, and VAXes. Of late the local VAX community (led by a renegade named Joel Snyder from COMPUSERVE), has run off and formed what they call "the UNLUG". They decided that they wanted to be "overtly commercial", and wanted no part of what they perceived to be the "complex bureaucracy" that surrounded being a DECUS LUG. To date, they have not had a meeting that I would consider to have violated the DECUS LUG commercialism policy, and they continue to resist my efforts to convince them that a LUG can be nearly as "loose" as the members want it to be. So far the UNLUG has had some nice programs. We are into comparing vendor software. We have had meetings on screen managers, data bases, and are about to have one on electronic spread sheets. The meetings usually have a novice Q and A session, a presentation by a member of the group on something interesting, an advanced Q and A session, and a "wizards rap" that usually adjourns to a nearby bar for beers. Typically a simple opening question gets explored to great depth until everyone "warms up". For instance, in the last meeting a question about "what is a layered product" ended up in exploring the whole structure of the VAX/VMS environment. We have had some nice presentations. Chris Janton (alias FACE) from the University of Arizona Computer Center presented a documentation generator tool that he built. Face also has presented the results of a "fiche reading" that yielded a gold mine of undocumented little services and routines that are so far undocumented. Bob Premovich and Mark Olsen from the University of Arizona Health Sciences Center presented a screen editor that they wrote in VAX Basic which makes up for the difficulties in the VAX foreign terminal support facility. So, on it goes. When in Tucson, look us up. The Tucson User Group meets every second Thursday of the month. The Tucson UNLUG meets some Mondays of the month. 32 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas Preliminary Roadmap for Las Vegas Jack D. Cundiff VAX Systems SIG Symposia Coordinator Muskingum College New Concord, Oh 43762 PRELIMARY ROADMAP FOR LAS VEGAS This is a ROADMAP to the Fall 1983 DECUS Symposium for those interested in VAX topics. It outlines all sessions being sponsored by the VAX Systems SIG and includes some related sessions sponsored by other SIGs as well. Sessions are grouped into several differing categories. These categories are: MANGEMENT TECHNICAL NOVICE GENERAL This document is intended to be your starting guideline for the FALL symposium. It is not exhaustive, and certainly does not reflect the sessions that will develop in Las Vegas such as BOFs. As you make your travel plans, please note that the Advanced Question and Answer session has been scheduled for Friday afternoon at 2:30. This also allows more time to prepare for the MAGIC session on Thursday evening. DECUS works because you participate and contribute to our common activities. In order to enhance that partici- pation we have made a special effort to schedule all WORKING GROUP sessions on late Monday afternoon and evening. Join with these working groups and get acquainted. It will also help you get a better understanding of that working groups sessions for the rest of the symposium. This is the first way to become more active in our SIG! We need your insights and HELP, so come and buttonhole us. The SIG leadership will be at these working group sessions. If you have a session you would like to present or have the working group to consider for the Spring Symposium in Cincinnati, please let the working group chairman know. The SIG has the preliminary planning for Cincinnati during the Symposium. Please let me know if this preliminary roadmap is useful to you. What can be done to improve it? What should we (the VAX Systems SIG) do to continue to develop these kinds of materials? What do you want for a SIG guide? A symposium guide? 33 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas SESSIONS FOR LAS VEGAS THE FOLLOWING ARE THE COLUMN HEADINGS AND EXPLANATIONS. HEADING EXPLANATION DAY DAY OF SESSION STRT START TIME OF SESSION STOP STOPPING TIME OF SESSION N NOVICE SESSION I INTERMEDIATE SESSION A ADVANCED SESSION M MANAGERIAL SESSION G GENERAL SESSION T TECHNICAL SESSION TITLE TITLE SPEAKER SPEAKER THE FOLLOWING ARE THE MANAGEMENT SESSIONS: MONDAY --- MANAGEMENT DAY STRT STOP N I A M G T TITLE SPEAKER MON 14:15 15:00 I M T VAXCLUSTER TECHNICAL CONCEPTS II BECKHARDT, STEVE MON 16:30 17:30 M VAX COMMERCIAL WORKING GROUP SESSION GILL, STEPHEN MON 17:30 18:30 M VAX SIG SYSTEM MANAGEMENT WORKING GROUP JOSEPH ANGELICO MON 21:00 22:00 I M T VAX SECURITY WORKING GROUP MEETING BROWN, C. DOUGLAS 34 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas TUESDAY --- MANAGEMENT DAY STRT STOP N I A M G T TITLE SPEAKER TUE 12:00 13:00 M GETTING STARTED WITH AI DEC TUE 16:00 17:00 I M VMS REMOTE SYSTEM _& NETWORK MANAGEMENT HANCOCK, BILL TUE 17:00 17:30 M G INTEGRATION OF PROJECT ACCOUNTING WITH VMS DIXON, WALTER V. 35 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas WEDNESDAY --- MANAGEMENT DAY STRT STOP N I A M G T TITLE SPEAKER WED 08:30 09:00 M T VAX SITE PREPARATION REHSE, SUSAN T. WED 10:30 11:30 N M SYSTEM MANAGEMENT FOR THE NEW VAX/VMS MANAGER CUNDIFF, JACK WED 14:00 14:30 N M NEW VAX, WHAT TO DO NEXT DOW-PLEINES,BARBARA WED 16:30 17:30 I M T VMS SYSGEN PARAMETERS WHOLEY, LOUISE THURSDAY --- MANAGEMENT DAY STRT STOP N I A M G T TITLE SPEAKER THR 17:00 18:30 I M HOW I MANAGE MY VMS SYSTEM JOHNSON, DAVID A. FRIDAY --- MANAGEMENT DAY STRT STOP N I A M G T TITLE SPEAKER FRI 08:30 09:00 N M SOFTWARE AIDS FOR VAX SYSTEM MANAGEMENT CARLETON, THURSTON P. FRI 09:30 10:30 N I M NOVICE SYSTEM MANAGERS CLINIC ANGELICO, JOSEPH F. 36 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas THE FOLLOWING ARE THE TECHNICAL SESSIONS: MONDAY --- TECHNICAL DAY STRT STOP N I A M G T TITLE SPEAKER MON 10:30 11:30 N I T APPLICATION OF THE TERMINAL-INDEPENDENT PROCEDURE IN VAX/VMS GLAZE, TIM LEON MON 12:30 13:30 T VAX PROGRAM OVERVIEW BROWN, REID MON 13:30 14:15 I A T VAXCLUSTER TECHNICAL CONCEPTS I ALTMANN, KERBEY MON 14:15 15:00 I M T VAXCLUSTER TECHNICAL CONCEPTS II BECKHARDT, STEVE MON 15:00 16:00 I T VAXCLUSTER HARDWARE DIGITAL REP MON 15:00 16:00 A T CONNECT-TO-INTERRUPT WITH DMA COE, TOM MON 16:00 17:00 A T GROWING A VAX TO A VAXCLUSTER DIGITAL PANEL MON 17:00 18:00 T VAX PROCESSOR DIRECTIONS - PART 1 BROWN, REID MON 18:00 19:00 A T VMS INTERNALS WORKING GROUP MEETING FRIEDBERG, CARL MON 18:30 19:00 A T PART ACCEL CONTRL & DTA ACQUISITION IN THE CONTEXT VAX/VMS SCHALLER,STUART C. MON 18:30 19:00 T SLIB 77 - A MAINTENANCE ALTERNATIVE FOR LARGE SCIENTIFIC G LUNSFORD, ALEX MON 19:00 20:00 T VAX PROCESSOR DIRECTIONS - PART 2 BROWN, REID MON 19:00 19:30 T A VAX-BASED SIMULATION OF NMR DATA ACQUISITION AND IMAGE CULLEN, MARK F. MON 19:30 20:30 I T SCRFT.MAR: HOW TO USE FOREIGN TERMINALS UNDER VMS SWENSON, STEVE 37 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas MON 20:00 21:00 T DISTRUBUTED REAL-TIME SOFTWARE FOR VAX BROWN, REID MON 20:00 21:00 A T INSIGHTS INTO THE AME FROM WRITING A CAMAC DRIVER FOR VMS CLOUT, PETER MON 21:00 21:30 I T RECORD NON HRDCPY TERM I/O TRANSACTIONS FOR DEFERRED PRINTIN R BERMAN, STEVEN MON 21:00 22:00 N I T VMS ARCHITECTURE KENAH, LAWRENCE MON 21:00 22:00 I M T VAX SECURITY WORKING GROUP MEETING BROWN, C. DOUGLAS MON 22:00 23:00 T INTERNAL DESIGN CRITERIA FOR VAX REAL-TIME SOFTWARE BROWN, REID 38 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas TUESDAY --- TECHNICAL DAY STRT STOP N I A M G T TITLE SPEAKER TUE 11:00 12:00 A T VAX BUSES, A DETAILED DISCUSSION & FUTURE DIRECTIONS DIGITAL REP TUE 12:00 13:00 I A T DISTRIBUTED LOCK MANAGER TECHNICAL DESCRIPTION BECKHARDT, STEVE TUE 13:00 14:00 T SOFTWARE PERFORMANCE CRITERIA FOR REAL-TIME APPLICATIONS BROWN, REID TUE 14:00 15:00 A T NEW MASS STORAGE ARCHITECTURE ALTMANN, KERBEY TUE 15:00 16:00 N I T VAX-11 RMS TUTORIAL KRICHEVSKY, TAMAR TUE 16:00 17:00 A T VAX-11 RMS FILE SHARING IN THE CLUSTER ENVIRONMENT THOMPSON, KEITH TUE 17:30 18:30 T PERFORMANCE OF HSC-MSCP SERVER-LOCAL DISKS VAX DEV GROUP TUE 18:00 19:00 T VAX/VMS IMAGE ACCOUNTING: USAGE AND EXAMPLES JAIN, RAJ TUE 18:30 19:00 T USER PANEL ON VAX REAL-TIME SOFTWARE BROWN, REID 39 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas WEDNESDAY --- TECHNICAL DAY STRT STOP N I A M G T TITLE SPEAKER WED 08:30 09:00 M T VAX SITE PREPARATION REHSE, SUSAN T. WED 08:30 09:30 T CI PERFORMANCE UNDER VMS VAX DEV GROUP WED 09:30 10:30 I T VAX SECURITY TUTORIAL DEC WED 10:30 11:30 I A T SECURITY MECHANISMS FOR VAX/VMS FUTURES SOPKA, JOHN WED 11:30 12:30 I A T PANEL DISCUSSION ON VAX/VMS SECURITY MECHANISMS BECKHARDT, STEVE WED 12:30 13:30 T USING COND AND EXIT HANDLERS TO STANDARIZE ERRORS ON VAX/VMS ROSENSTEIN, STEVEN J. WED 13:30 14:00 I T FUTURE DIRECTIONS IN DATA INTEGRITY YETTO, LARRY WED 14:00 14:30 I T VAX/VMS RECOVERY UNIT FACILITY SOPKA, JOHN R WED 14:30 15:00 I T CHECKPOINT/RESTART FACILITY SOPKA, JOHN R WED 14:30 15:30 N T NOVICE VAX CONFIGURATIONS LEONARD, DAVE WED 15:00 15:30 A T VAX/VMS PERFORMANCE MONITOR FOR USER PROGRAMS ROBERTSON, LARRY WED 15:30 16:30 T VMS PEFORMANCE MANAGEMENT VAX DEV GROUP WED 16:30 17:30 I M T VMS SYSGEN PARAMETERS WHOLEY, LOUISE WED 16:30 17:00 I T TRACKING DISK FILES BY OWNER UIC DIXON, WALTER V. 40 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas WED 17:00 18:00 N G T VAX APPLICATIONS AT FINANCIAL INSTITUTIONS NICHOLAS, MICHAEL WED 17:30 19:00 N T VAX NOVICE SOFTWARE CLINIC GREBUS,GARY 41 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas THURSDAY --- TECHNICAL DAY STRT STOP N I A M G T TITLE SPEAKER THR 08:30 09:30 T VAX/VMS MULTIPROCESSO DBMS USING MULTIPORT MEMORY LEONARD, DAVE THR 08:30 09:30 I T VAX/VMS ERROR LOGGING DRAYTON, ELLIOTT THR 09:30 10:30 I T THE VMS TERMINAL DRIVER SPITZ, ROBERT K. THR 11:00 12:00 I T PRACTICAL APPROACH TO VMS ENVIRONMENTAL SECURITY (PAVES) FISHCHER, JAMES B. THR 11:30 12:30 I A T VMS SHAREABLE IMAGES TEAGUE, JAMES W. THR 12:30 13:00 I T SHAREABLE IMAGES ON VMS FOR LARGE USER LIBRARIES JOHNSON, DAVID A. THR 13:00 14:00 I T VAX USER SYSTEM SERVICES SLATER, DAVID THR 14:00 14:30 I T VAX WORKLOAD CHARACTERIZATION LANPHAR, ROBERT THR 14:30 15:00 I T AN INTERACTIVE BENCHMARK COMPARISON OF A 11/780-11/782 LUBECK,OLAF THR 15:00 15:30 I T THE BERNI SCALE: A VAX PERFORMANCE MANAGEMENT METRIC LANPHAR, ROBERT THR 15:00 15:30 I T A HIGH SPEED ALTERNATIVE TO MAILBOXES ON VAX/VMS DODGE, DAVID L. THR 18:30 20:00 I A T HOW FAST CAN A VAX ... (A CASE HISTORY) HEIDOM, DON THR 18:30 19:30 N T VAX-11 SYMBOLIC DEBUGGER OVERVIEW DEC 42 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas FRIDAY --- TECHNICAL DAY STRT STOP N I A M G T TITLE SPEAKER FRI 08:30 09:30 T VMS REAL-TIME RESPONSIVENESS FORK & PROCESS LEVEL RESPONSE VAX DEV GROUP FRI 09:00 09:30 N T USING DCL'S ON VAX/VMS TO PROVIDE A MENU-DRIVEN INTERFACE WILD, FREDERIC H. FRI 09:30 10:30 T DESIGNING HIGH PERFORMANCE REAL-TIME APPLICATIONS FOR VAX/VM VAX DEV GROUP FRI 10:30 11:30 I T FLS-11 ON V/V: AN INTRO & DESCRIP FOR APPL & SYS PROG/DESIGN FRIEDBERG,CARL FRI 10:30 11:30 I T VAX REAL-TIME PERFORMANCE TEST RESULTS KAYFES, RICHARD FRI 12:30 13:30 N T TAPECOPY USER`S FORUM BINGHAM, JOE FRI 14:30 17:30 A T VAX SYSTEM ADVANCED QUESTION AND ANSWER FRIEDBERG, CARL 43 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas THE FOLLOWING ARE THE NOVICE SESSIONS: MONDAY --- NOVICE DAY STRT STOP N I A M G T TITLE SPEAKER MON 09:00 09:45 N I G VAX SYSTEMS UPDATE DIGITAL REP MON 10:30 11:30 N I T APPLICATION OF THE TERMINAL-INDEPENDENT PROCEDURE IN VAX/VMS GLAZE, TIM LEON MON 17:00 17:30 N G VAX NETWORKS WORKING GROUP MEETING KESSLER, GARY MON 21:00 22:00 N I T VMS ARCHITECTURE KENAH, LAWRENCE MON 21:30 23:00 N G VAX/VMS NOVICE QUESTIONS & ANSWERS HAYDT, NANCY TUESDAY --- NOVICE DAY STRT STOP N I A M G T TITLE SPEAKER TUE 08:30 10:00 N I G VAX HARDWARE PANEL DIGITAL PROD MGR TUE 10:00 11:00 N I G SMALL VAX FOR BUSINESS APPLICATIONS DIGITAL PROD MGR TUE 15:00 16:00 N I T VAX-11 RMS TUTORIAL KRICHEVSKY, TAMAR 44 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas WEDNESDAY --- NOVICE DAY STRT STOP N I A M G T TITLE SPEAKER WED 10:30 11:30 N M SYSTEM MANAGEMENT FOR THE NEW VAX/VMS MANAGER CUNDIFF, JACK WED 11:30 12:30 N G INTRODUCTION TO VMS COMMAND PROCEDURES HAYDT, NANCY WED 14:00 14:30 N M NEW VAX, WHAT TO DO NEXT DOW-PLEINES,BARBARA WED 14:30 15:30 N T NOVICE VAX CONFIGURATIONS LEONARD, DAVE WED 15:30 16:30 N G NOVICE REAL-TIME PROCESSING USING VAX/VMS ROBBINS,ROBERT WED 17:00 18:00 N G T VAX APPLICATIONS AT FINANCIAL INSTITUTIONS NICHOLAS, MICHAEL WED 17:30 19:00 N T VAX NOVICE SOFTWARE CLINIC GREBUS,GARY 45 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas THURSDAY --- NOVICE DAY STRT STOP N I A M G T TITLE SPEAKER THR 18:30 19:30 N T VAX-11 SYMBOLIC DEBUGGER OVERVIEW DEC FRIDAY --- NOVICE DAY STRT STOP N I A M G T TITLE SPEAKER FRI 08:30 09:00 N M SOFTWARE AIDS FOR VAX SYSTEM MANAGEMENT CARLETON, THURSTON P. FRI 09:00 09:30 N T USING DCL'S ON VAX/VMS TO PROVIDE A MENU-DRIVEN INTERFACE WILD, FREDERIC H. FRI 09:30 10:30 N I M NOVICE SYSTEM MANAGERS CLINIC ANGELICO, JOSEPH F. FRI 12:30 13:30 N T TAPECOPY USER`S FORUM BINGHAM, JOE 46 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas THE FOLLOWING ARE THE GENERAL SESSIONS: MONDAY --- GENERAL DAY STRT STOP N I A M G T TITLE SPEAKER MON 08:30 09:00 G VAX SYSTEM SIG ROADMAP MILLER, ROSS MON 09:00 09:45 N I G VAX SYSTEMS UPDATE DIGITAL REP MON 09:45 10:30 G VAX/VMS SYSTEM UPDATE KEMPSELL, TREVOR MON 11:30 12:30 G VAX LANGUAGES OVERVIEW STERN,SHIRLEY MON 17:00 17:30 N G VAX NETWORKS WORKING GROUP MEETING KESSLER, GARY MON 17:30 18:30 G VAX REAL-TIME WORKING GROUP MEETING FRAYNE, DENNIS MON 18:30 19:30 G VAX SYSTEM LUG MEETING ROBBINS,ROBERT MON 20:00 21:00 G ORGANIZATIONAL MEETING OF ARTIFICIAL INTELLIGENCE WORKING PEARL, MORRIS B. MON 21:30 23:00 N G VAX/VMS NOVICE QUESTIONS & ANSWERS HAYDT, NANCY 47 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas TUESDAY --- GENERAL DAY STRT STOP N I A M G T TITLE SPEAKER TUE 08:30 10:00 N I G VAX HARDWARE PANEL DIGITAL PROD MGR TUE 10:00 11:00 N I G SMALL VAX FOR BUSINESS APPLICATIONS DIGITAL PROD MGR TUE 13:00 13:30 G ARTIFICIAL INTELLIGENCE LANGUAGES FOR DIGITAL`S SYSTEMS DEC TUE 17:00 17:30 M G INTEGRATION OF PROJECT ACCOUNTING WITH VMS DIXON, WALTER V. WEDNESDAY --- GENERAL DAY STRT STOP N I A M G T TITLE SPEAKER WED 11:30 12:30 N G INTRODUCTION TO VMS COMMAND PROCEDURES HAYDT, NANCY WED 15:30 16:30 N G NOVICE REAL-TIME PROCESSING USING VAX/VMS ROBBINS,ROBERT WED 17:00 18:00 N G T VAX APPLICATIONS AT FINANCIAL INSTITUTIONS NICHOLAS, MICHAEL 48 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas DATE 25-Aug-83 PAGE 5 THURSDAY --- GENERAL DAY STRT STOP N I A M G T TITLE SPEAKER THR 12:45 13:30 G VAX-11 SYMBOLIC DEBUGGER TUTORIAL DEC THR 13:00 13:30 G VAX SYSTEM INTEGRITY MONITOR MOORE, W. BRUCE THR 13:30 15:00 G VAX SIG SYSTEM IMPROVEMENT REQUESTS GREBUS, GARY THR 15:30 17:00 G DIGITAL'S SOFTWARE ENGINEERING PROCESS HARRIS, TOM THR 15:30 18:30 G ADVANCED VAX/VMS SOFTWARE CLINIC FRIEDBERG, CRL THR 20:00 22:00 G MAGIC, WAR STORIES, AND HORROR TALES FRIEDBERG, CARL FRIDAY --- GENERAL DAY STRT STOP N I A M G T TITLE SPEAKER FRI 11:30 12:30 G INTERLISP FOR THE VAX DEC FRI 12:30 13:00 G COMMON LISP FOR DIGITAL SYSTEMS DEC FRI 13:30 14:30 G SIG BUSINESS MEETING MILLER,ROSS 49 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas The following sessions are VAX related and show the SIG responsible for the session. APL MON 12:30 AN APL TUTORIAL TUE 14:00 APL INTERNALS FOR DIGITAL SYSTEMS TUE 15:30 APL FOR TOPS-20 AND VAX/VMS BASIC MON 14:30 PROGRAMMING WITH VAX-11 BASIC MON 20:30 CROSS-BASIC TRANSLATOR TUE 18:30 BP2 FOR INDENT WED 8:30 BP2 AND VAX-11 BASIC COMPILER WED 12:00 ANSI BASIC PROS & CONS WED 17:30 NEW VAX-11 BASIC FEATURES THU 8:30 BASIC PLUS 2 AND THREADED CODE COBOL MON 12:30 ANNOUNCING VAX-11 COBOL VERSION 3 MON 13:00 NEW FEATURES IN COBOL-81 VERSION 2 TUE 16:00 SCREEN HANDLING WITH VAX-11 COBOL AND COBOL-81 ACCEPT/DISPLAY TUE 17:00 DEVELOPING COBOL-81 PROGRAMS USING VAX-11 COBOL THU 9:30 FILE DESIGN ON DISTRIBUTED VAX NETWORKS THU 14:00 OPTIMIZATION IN VAX-11 COBOL AND COBOL-81 THU 18:00 MULTI-LINGUAL COMMERCIAL APPLICATIONS WITH VAX-11 COBOL 50 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas DATA MANAGEMENT MON 10:30 VAX INFORMATION ARCHITECTURE OVERVIEW MON 11:30 VAX-11 CDD TECHNICAL TUTORIAL MON 12:30 PERFORMANCE MEASUREMENTS OF THE INGRES DATA BASE SYSTEM MON 13:00 VAX FORMS PRODUCTS: WHAT NEXT. MON 13:30 FMS TDMS MERGER MON 17:30 VAX-11 FMS OVERVIEW MON 20:00 INTRODUCTION TO VAX-11 DBMS MON 21:00 VAX-11 DBMS USERS PANEL TUE 9:00 HIRING YOUR DATA BASE MANAGEMENT SYSTEM TUE 11:30 CAM SYSTEM UTILIZING VAX-11 DBMS TUE 15:00 ARCHITECTURAL PRINCIPLES OF THE VAX INFORMATION ARCHITECTURE TUE 16:30 APPLICATION DESIGN USING THE VAX INFORMATION ARCHITECTURE TUE 17:30 INTERRELATIONSHIP OF VAX INFORMATION ARCHITECTURE PRODUCTS WED 8:30 COMPARISON OF FMS VERSUS TDMS APPLICATIONS WED 11:00 MACCS: A GRAPHIC DATA BASE SYSTEM FOR CHEMICAL COMPOUNDS WED 11:30 DATA MANAGEMENT SERVICES FOR ELAN WED 12:30 FUTURES OF DATA DICTIONARIES WED 13:30 VAX-11 TDMS (TERMINAL DATA MANAGEMENT SYSTEMS) OVERVIEW WED 14:30 IBM COEXISTENCE IN CORPORATE DSS COMPUTING THU 8:30 MIS MANAGEMENT WORKSHOP: PART 1 THU 10:30 RMS PRODUCT WISH LIST FOR ALL SYSTEMS THU 10:30 VAX INFORMATION ARCHITECTURE APPLICATION DEVELOPMENT AND THU 11:30 VAX INFORMATION ARCHITECTURE APPLICATION DEVELOPMENT AND THU 11:30 VAX-11 DECSTR: MANUFACTURING SHOP FLOOR CONTROL THU 11:30 MIS MANAGEMENT WORKSHOP: PART 2 THU 12:30 VAX-11 DBMS: DATA BASE DESIGN AND PERFORMANCE MANGEMENT THU 12:30 ADE PRODUCT UPDATE THU 13:00 RMS-11 PRODUCT GROUP BUSINESS MEETING THU 13:30 FORMS MANAGEMENT CLINIC THU 16:00 FUTURE DIRECTIONS IN APPLICATION DEVELOPMENT WITH THE VAX THU 17:00 VAX-11 FMS ADVANCED PROGRAMMING THU 17:30 VAX-11 DBMS DATA BASE DESIGN AND TUNING THU 18:30 VAX-11 CDD USER PANEL THU 18:30 VAX-11 DBMS/CDD PRODUCT GROUP MEETING THU 19:00 VAX-11 TERMINAL DATA MANAGEMENT SYSTEMS (TDMS) TECHNICAL THU 20:00 VAX-11 TDMS V1 - PERFORMANCE FRI 15:00 USE OF SPECIAL TERMINATORS IN FMS APPLICATIONS 51 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas DATATRIEVE MON 15:30 SO, WHAT IS DATATRIEVE ANYWAY? MON 19:00 VAX-11 DATATRIEVE APPLICATION DESIGN TRADE-OFFS TUE 11:30 DEVELOPMENT WITH DATATREIVE IN THE VAX INFORMATION TUE 18:30 INTERFACNG TO VAX-11 DATATRIEVE VIA COBOL WED 8:30 USING PRO/DATATRIEVE TO IMPLEMENT AN ORDER ENTRY SYSTEM WED 14:30 CUSTOMIZING VAX-11 DATATRIEVE WED 15:30 USING VAX-11 DATATRIEVE GRAPHICS WED 16:30 VAX-11 DATATRIEVE IN GOVERNMENT FINANCIAL MANAGEMENT THU 13:30 VAX-11 DATATRIEVE TECHNICAL TUTORIAL THU 15:00 VAX-11 DATATRIEVE WITH FORMS TUTORIAL DIBOL MON 15:00 INTERFACING DIBS-11 TO THE GENERAL LEDGER MON 16:00 DIBS-11 GENERAL LEDGER REPORT WRITER MON 17:00 DIBS-11 UPDATE AND FEEDBACK TUE 12:30 SOFTWARE PIRACY THU 8:30 DIBOL-83 PERFORMANCE OPTIMIZATION THU 9:30 DIBOL VERSION 2.1 THU 10:30 VAX-11 DIBOL: STUMP THE DEVELOPERS THU 11:30 EFFECTIVE USE OF FMS WITH DIBOL ON VAX/VMS THU 16:00 INTRODUCTION TO DIBOL PROGRAMMING THU 17:30 STRUCTURED PROGRAMMING CONCEPTS AND DIBOL-83 FRI 11:30 DIBOL: FUTURES AND WISH LIST EDUSIG MON 20:30 AN INTERACTIVE TESTING PROGRAM FOR THE VAX MON 21:00 VAXING IN A SMALL COLLEGE MON 21:30 PERFORMANCE OF VAX/VMS SYSTEMS IN THE EDUCATION ENVIRONMENT TUE 10:30 PROGRAMMING IN VAX-BASIC: A STRUCTURED APPROACH TUE 12:30 ACADEMIC VAX MANAGEMENT PANEL THU 14:00 STATISTICAL SOFTWARE PACKAGES FRI 10:30 ADMINISTRATIVE SOFTWARE FOR EDUCATION 52 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas GRAPHICS MON 19:00 A CRAY/VAX INTERACTIVE GRAPHICS SYSTEM TUE 11:30 VAX-11 DECGRAPH OVERVIEW TUE 13:00 VAX-11 DECSLIDE OVERVIEW TUE 16:00 REGIS COMPATIBILITY THU 16:30 DECOR: A TECHNICAL OVERVIEW THU 18:00 MATHLIB: A LIBRARY OF TOOLS FOR MATHEMATICAL MODELING, FRI 9:00 IMPROVING GRAPHICS DISPLAY PERFORMANCE UNDER VMS FRI 9:30 THE SOFTWARE DEVELOPMENT WORKBENCH: AN INTEGRATED SOFTWARE IAS TUE 12:30 IAS/VMS USER PANEL TUE 17:30 IAS,RSTS/E,RSX,VMS: HOW DIGITAL HAS APPROACHED MULTI-USER HARDWARE MICRO MON 12:30 VIDEO TERMINALS: CURRENT PRODUCTS & FUTURE NEEDS MON 13:30 PDP-11'S FRONT-ENDING FOR VAX'S MON 18:30 PROCESS CONTROL TOPICS MON 19:30 PROGRAMMING THE IEQ11/IEU11 FAMILY OF IEEE-488 BUS INTERFACE TUE 11:00 HOW THE J-11 STACKS UP AGAINST OTHER PROCESSORS TUE 15:00 MIGRATION PATHS FROM MICRO/PDP-11 TO VAX WED 10:30 VIDEO TERMINALS: FUNCTIONS AND FEATURES WED 12:30 DR11-W UNIBUS OPTION LABORATORY DATA ACQUISITION MON 15:30 LABSTATION 23: LOW SPEED DATA COLLECTION ON THE VAX WITHOUT TUE 17:00 SCIENTIFIC IMAGE PROCESSING WED 10:30 MODELING SYSTEMS FOR RESEARCH: MORE THAN A SPREADSHEET WED 11:00 RS/1 USER PANEL DISCUSSION WED 11:30 VAX IN COMPUTATIONAL CHEMISTRY WED 12:00 RS/1 WORKING GROUP WED 13:30 INTERFACING LABORATORY DATA SYSTEMS TO VAX WED 14:00 SAMPLE MANAGEMENT: VAX-11 LIMS/SM -- DATA BASE MANAGEMENT WED 16:30 MIGRATING LARGE LABORATORY SOFTWARE SYSTEMS TO THE WED 17:00 INTEGRATING THE VAX AND PROFESSIONAL 350 INTO THE LABORATORY FRI 15:30 FLEXIBLE IN-LINE DIGITAL FILTER FOR USE WITH LLNL ULTRASONIC FRI 16:00 LABORATORY DATA ACQUISITION THROUGH RS-232-C AND DZ-11 53 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas LARGE SYSTEMS WED 9:30 TECHNICAL COMPARISON OF TOPS-10/20 TO VAX/VMS THU 11:00 CONVERSION FROM TOPS-10/20 TO VAX/VMS USER PANEL THU 15:30 DIL USER PANEL FRI 9:30 MIXED 10/20/VAX NETWORKING FRI 13:30 TECHNICAL COMPARISON OF TOPS-10/20 LANGUAGES TO VAX LANGUAGE MUMPS THU 18:00 INTRODUCTION TO VAX-11 DSM THU 20:30 $ZCALL: THE VAX-11 DSM EXTERNAL CALL INTERFACE THU 21:00 VAX-11 DSM SYSTEM MANAGEMENT AND PERFORMANCE WORKSHOP NETWORKS MON 10:00 FUNDAMENTALS OF DATA COMMUNICATIONS MON 15:30 DECNET PARAMETERS TUTORIAL MON 16:30 DATA COMMUNICATIONS TUTORIAL MON 20:00 NETWORK MAGIC SESSION TUE 10:30 ETHERNET: A TECHNICAL OVERVIEW TUE 13:30 ETHERNET PERFORMANCE CONSIDERATIONS TUE 16:00 ETHERNET FIELD TEST PANEL TUE 17:00 INSTALLATION OF DIGITAL'S ETHERNET WED 9:30 NETWORK PEFORMANCE THU 9:30 VAX/VMS NETWORK PROXY LOGIN THU 16:00 NEW FEATURES OF STATISTICAL MULTIPLEXERS THU 18:00 COMMUNICATIONS: A DEFINITION FROM SINGLE LINE TO NETWORKS THU 20:30 USING AN INTELLIGENT DATA SWITCH IN A MULTIPLE HOST FACILITY FRI 11:30 VAX/VMS ARPANET USERS PANEL OFFICE AUTOMATION WED 17:00 INTRODUCTION TO DECTYPE WORD PROCESSING ON VAX AND RSX 54 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas RSTS MON 18:00 ANALYSIS AND THE CUSTOMER USING RSTS/E AND VMS RSX TUE 11:00 TUTORIAL: RSX SYSTEM DEVELOPMENT UNDER VAX/VMS COMPATIBILITY THU 16:00 EXPERIENCES ACCESSING VAX NATIVE CODE FROM COMPATIBILITY MOD THU 16:30 VMS TO RSX CONVERSIONS THU 17:00 REAL-TIME DISTRIBUTED PROCESSING FOR RSX/VAX SYSTEMS THU 17:30 FILES-11: THE ON-DISK STRUCTURE SITE MANAGEMENT AND TRAINING MON 11:30 TEACHING COMPUTERS AT YOUR SITE MON 11:30 WHAT THE NEW DECUS WILL BE MON 15:00 FIELD SERVICE "TODAY AND TOMORROW" TUE 9:30 ORGANIZING AGAINST DISASTER: A COOPERATIVE STRATEGY FOR WED 10:00 PRODUCTION, SALE, AND DISTRIBUTION OF DIGITAL DOCUMENTATION WED 11:00 VAX DOCUMENTATION OVERVIEW THU 13:00 GIVING EFFECTIVE PRESENTATIONS FRI 10:00 PROVIDING PROPER POWER AND GROUNDING FOR YOUR DIGITAL SPECIAL SOFTWARE AND OPERATING SYSTEMS MON 8:30 UNIX IS A FOUR LETTER WORD MON 11:30 CUSTOMER SERVICES FOR THE DIGITAL UNIX OFFERINGS TUE 9:30 VNX OVERVIEW TUE 10:30 AN ALTERNATE CLI ON VMS TUE 11:00 DIGITAL'S UNIX OPERATING SYSTEM FOR VAX TUE 12:30 UNIX AND VMS C0-EXISTENCE TUE 14:00 UNIX EMULATORS UNDER VAX/VMS PANEL THU 9:30 UNIX WISH LIST 55 PAGESWAPPER - September 1983 - Volume 5 Number 3 Preliminary Roadmap for Las Vegas TOOLS TUE 16:00 INTRODUCTION TO VAX-11 C TUE 17:00 VAX-11 C PORTABILITY WED 11:00 USE OF ENVIRONMENT FILES WITH VAX-11 PASCAL WED 12:00 PLANS FOR RPGII ON VAX THU 9:30 EDT MAGIC THU 11:30 A CMS DOCUMENT MANAGEMENT SYSTEM THU 12:30 BLISS LANGUAGE TUTORIAL THU 13:00 BLISS PRODUCT REVIEW THU 14:30 PDP-11 FORTRAN-77 FUTURES THU 16:00 VAX-11 FORTRAN OPTIMIZATION THU 19:00 RMS I/O FROM C FRI 10:00 MAKING VAX-11 C: A REFLECTION AND UPDATE FRI 10:00 APPLICATION OF STRUCTURED PROGRAMMING TECHNIQUES TO VAX-11 FRI 11:00 PCS32: DESIGN AND IMPLEMENTATION USING VAX-11 C FRI 14:00 A NEW REQUIREMENTS APPROACH FOR SOFTWARE SUCCESS 56 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT INPUT/OUTPUT A SIG Information Interchange A form for INPUT/OUTPUT submissions is available at the back of the issue. INPUT/OUTPUT 182 Caption: DEC Terminal VT61 Message: I would like to obtain any and all information for a VT61. I need a User's Guide, parts list, and full set of schematics. Also my power board has a short. Maybe someone could tell me a probable cause for this and/or aim me in the direction of some replacement parts (maybe another VT61 for use as parts). Any help would be appreciated. Contact: Ronald Barale Jr. 565 Sinclair Frontoq Road Milipitas, CA 95035-5470 (408) 945-1600 Date: June 29, 1983 INPUT/OUTPUT 183 Caption: TELEX Interface for VAX Message: We are looking for a hardware/software combination that would allow us to replace our TELEX machine with a "black box" into our VAX. It should function as a server to allow a user at any terminal to send a TELEX. It would also need to handle incoming messages. Contact: Ed Horst Atlas Steel Rule Die, Incorporated 2000 Middlebury Street Elkhart, IN 46516 (219) 294-5507 Date: July 19, 1983 57 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT INPUT/OUTPUT 184 Caption: DZ11 Output Port Communication Software Needed Message: Does anyone have a program which would allow a user to attach through a DZ11 output terminal port and modem to another computer? The functions desired are: (1) send a file, (2) receive a file, (3) send and receive character sequences from user's terminal and remote computer. Escape sequence handling to provide functions like full screen editing would be a plus. Contact: Donald Borsay Engineering Computer Lab 306 Bliss Hall Kingston, RI 02881 (401) 792-2559 Date: July 19, 1983 INPUT/OUTPUT 185 Caption: MWAIT Process - AST wait Message: Has anyone developed a method (program) to remove a process from the MWAIT state? Rebooting is not an adequate solution for online systems. Contact: Hugh Fraser Algoma Steel Corporation Limited 550 Queen Street West Sault Ste Marie, Ontario, Canada (705) 945-3666 Date: July 20, 1983 Editor's Note At several US Decus Symposia, VMS developers have responded that MWAIT is VMS's way of telling you something is wrong. In particular, if one were to blatantly modify VMS data structures until the process was "out" of MWAIT, the result would likely be corruption of those data structures so as to cause failure of other functions later on. The proper method for "curing" MWAIT is a total analysis to find the faulty software (drivers are a likely source of AST MWAIT) or system parameter. If anyone has a program to 58 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT do THAT, they should try selling it to DEC as a new subroutine for SDA. INPUT/OUTPUT 186 Caption: File Archiving Message: Need information on software to allow selective archiving and retrieving files. Ideally the system should have a user searchable file which contains pointers to files on tapes. The software should send a message to an operator asking for the tape to be mounted and the file retrieved. Contact: Charles A. Untulis Atari, Incorporated 1196 Borregas Sunnyvale, CA 94086 (408) 745-0510 Date: July 22, 1983 INPUT/OUTPUT 187 Caption: Bug fix for ETAPE.FOR on Spring 82 SIG Tape Message: ETAPE.FOR as distributed on the Spring 82 SIG Tape contains a bug which causes it to sometimes fail to write the last block of a file to tape. The parameter on line 413 %val(IO$WRITELBLK) should read %val(IO$_WRITELBLK). Other than this bug, I have found the utility to be quite useful and I recommend it to others. Contact: J. D. Case Purdue University Calumet Hammond, Indiana 46323 (219) 844-0520 Date: July 22, 1983 59 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT INPUT/OUTPUT 188 Caption: The Penultimate Macro Generator - REPLY TO I/O # 137 Message: Those interested in a general-purpose "macro processor" should investigate the implementation of SNOBOL IV on the Fall 1982 SIG tape; there are a few bugs but it basically works. The primary documentation of this implementation is: Ralph E. Griswold, "The Macro Implementation of SNOBOL4", San Francisco CA: W. H. Freeman and Co., 1972. If you have SNOBOL, who needs macros!?! Contact: Scott Marovich National Semiconductor DATACHECKER/DTS Mail Stop 10-200 1120 Kifer Road Sunnyvale, CA 94088-3595 (408) 721-6092 Date: July 22, 1983 INPUT/OUTPUT 189 Caption: RESPONSE TO "XPL Compiler" - I/O # 123 Message: An XPL compiler is available from DECUS that runs on either TOPS-10 or TOPS-20. The DECUS order numbers are: 10-291 and 20-122, media codes PA and MA respectively. Contact: Gerard K. Newman Science Applications, Incorporated 800 Oak Ridge Turnpike Oak Ridge, TN 37830 (615) 482-9031 x342 Date: July 22, 1983 INPUT/OUTPUT 190 Caption: RESPONSE TO "$ SET PROCESS/USERNAME=" I/O # 149 Message: See FICHE 324 M15. You can type in the resultant MACRO code from the BLISS compilation listing. I will also supply a printed copy of a program which changes the username associated with a process to anyone who sends me a SASE (it's short). 60 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT Contact: Gerard K. Newman Science Applications, Incorporated 800 Oak Ridge Turnpike Oak Ridge, TN 37830 (615) 482-9031 x342 Date: July 22, 1983 INPUT/OUTPUT 191 Caption: Run MBASIC Programs on VAX Message: We need to run programs developed under CP/M in MBASIC. We would like an MBASIC compiler or interpreter or conversion aids to VAX-11 BASIC. Contact: C. Collister Lincoln College Canterbury, NEW ZEALAND 252-811 Date: July 26, 1983 INPUT/OUTPUT 192 Caption: Looking for VAX DR11-K Sites Message: I am looking for any sites that have had any experience with a DR11-K (general purpose digital I/O interface). We are currently having one installed and field service is not having much success. I would be grateful for any help offered. Contact: Brian G. Forsyth Senior Engineering Technician Kennametal Incorporated PO Box 231 Latrobe, PA 15650 (412) 539-5315 Date: July 29, 1983 61 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT INPUT/OUTPUT 193 Caption: VAX-to-* File Transfer - REPLY TO I/O # 174 Message: The Spring 79 DECUS tape has an excellent piece of code to use as is or as starting material for a more personally tuned system. The program is called VAXNET and was submitted by Roger Lipsett and John Thompson of Intermetrics. VAXNET is fully documented including a help file. Contact: Tom Heim Jr. Digital Equipment Corporation 2500 West Union Hills Drive Phoenix, Arizona 85027 (602) 869-5780 Date: August 11, 1983 INPUT/OUTPUT 194 Caption: No Commercialism! Message: Items should NOT be printed in INPUT/OUTPUT that are of a commercial nature. This means that all software mentioned in I/O should cost no more than the cost of distributing the software. There are plenty of places to advertise or read about commercial software. In view of the tenants of DECUS, the Pageswapper should not be one of them. Contact: Jon Forrest Physics Department University of California, Santa Barbara Santa Barbara, CA 93106 (805) 961-2602 Date: August 11, 1983 INPUT/OUTPUT 195 Caption: PDP-8 to PC Interface Message: We are trying to interface a PDP-8 (COS-310) to a personal computer and would like to talk with a user who has done this. Contact: Claudette Forney Carrollton Graphics Incorporated Box 68 62 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT Carrollton, OH 44615 (216) 627-5511 Date: August 15, 1983 INPUT/OUTPUT 196 Caption: Zeroing Real Memory - REPLY TO I/O # 163 Message: There is a program available from the latest VAX LUG Decus Tape that claims to zero VAX memory 100 times. (I cannot vouch for it's completeness.). It is called [VAX82B.SDC.CLEAR]CLEAR.MAR and comes from System Development Corporation, 4810 Bradford Boulevard NW, Huntsville, LA 35805. Contact: Christopher Gordon Bendix Corporation - Oceanics Divison 15825 Roxford Street Sylmar, CA 91342 Date: August 16, 1983 63 PAGESWAPPER - September 1983 - Volume 5 Number 3 DECUS Symposia Proceedings DECUS Symposia Proceedings Listed below are the current DECUS Symposium Proceedings that can be ordered through the DECUS office in Marlboro, Massachusetts. All are Media Service Code YA. PRO-81/V07.1 1980 Europe Amsterdam, Holland PRO-81/V07.2 1980 U.S. Fall San Diego, California PRO-81/V07.3 1981 Canada Montreal, Quebec PRO-81/V07.4 1981 U.S. Spring Miami, Florida PRO-81/V07.5 1981 Australia Brisbane, Australia PRO-82/V08.1 1981 Europe Hamburg, Germany* PRO-82/V08.2 1981 U.S. Fall Los Angeles, California PRO-82/V08.3 1982 Canada Toronto, Canada PRO-82/V08.4 1982 U.S. Spring Atlanta, Georgia PRO-EUR-82 1982 Europe Warwick, United Kingdom PRO-ANA-82 1982 U.S. Fall Anaheim, California * Available from Geneva only. None available until further notice. 64 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT Submission Form INPUT/OUTPUT Submission Form A SIG Information Interchange Please reprint in the next issue of the Pageswapper If this is a reply to a previous I/O, which number? ________ Caption: ______________________________________________________ Message: ______________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ Contact: Name _______________________________________________________ Address ____________________________________________________ ____________________________________________________________ Telephone ____________________________ Signature _____________________________ Date ________________ Mail this form to: PAGESWAPPER Editor, DECUS, MRO2-1/C11, One Iron Way, Marlborough, MA 01752, USA 65 PAGESWAPPER - September 1983 - Volume 5 Number 3 INPUT/OUTPUT Submission Form Tear out to submit an I/O item PAGESWAPPER Editor DECUS, MRO2-1/C11 One Iron Way Marlborough, MA 01752 USA 66 PAGESWAPPER - September 1983 - Volume 5 Number 3 System Improvement Request Submission Form System Improvement Request Submission Form SIG ref no. _________ Page 1 of _____ ________________________________________________________________ Submittor: Firm: Address: Phone: ________________________________________________________________ Circle application area(s) most closely related to yours (OEMs circle end use): Transaction Processing Business EDP (accounting) Program Development Systems Development General Timesharing Student Timesharing Shared Small Applications Shared Large Applications Process Control Word Processing Large Simulation ________________________________________________________________ System Configuration: CPU Model: System Disk: Memory Size: Average User Load: Operating System: Version: ________________________________________________________________ Abstract (Please limit to four lines): ________________________________________________________________ Description (include justification and expected usefulness): Use additional pages if required Completed SIR should be returned to: Gary L. Grebus, Battelle Columbus Laboratories, 505 King Avenue, Columbus, Ohio 43201, USA 67 PAGESWAPPER - September 1983 - Volume 5 Number 3 System Improvement Request Submission Form Tear out to submit an SIR Gary L. Grebus Battelle Columbus Laboratories 505 King Avenue Columbus, Ohio 43201 USA 68