NASA CONTRACTOR-,. REPORT PC: COPY: U LOAN RETURN io AFWL (WLiL-2) YlRTLAND AFB, N MEX MAMOS: A MONITOR SYSTEM UNDER IBSYS FOR THE IBM 7090/7094 by Alfred E, Beam Prepared by UNIVERSITY OF MARYLAND College Park, Md. for NATIONALAERONAUTICS AND SPACE ADMINISTRATION WASHINGTON, D. C. MAY 1966 ~~ - TECH LIBRARY KAFB, NY I NASA CR-488 MAMOS: A MONITOR SYSTEM UNDER IBSYS FOR THE IBM 7090/7094 By Alfred E. Beam Distribution of this report is provided in the interest of informationexchange. Responsibility for thecontents resides in the author or organization that prepared it. Prepared under Grant No. NsG-398 by UNIVERSITY OF MARYLAND College Park, Md. for NATIONAL AERONAUTICS AND SPACE ADMINISTRATION For sale by the Clearinghouse for Federal Scientific and Technical Information Springfield, Virginia 22151 - Price $7.00 Abstract This report describesan operating system which operates on the IBM 7090/7094 under the IBSYS or DC-IBSYS Monitor. The system processes jobs written in theMAD language, ALGOL language, FORTRAN language, and UMAP language. The processors of the system are among the fastest currently available. A very extensive library of programs is also provided. The system isespecially useful for processing student jobs. iii TABLE OF CONTENTS Page Abstract iii Acknowledgements vii 1.1-1 1 .l-1 1.2-1 2. "OS System Operation And Installation Options 2.1-1 2.1 Introduction 2.1-1 2.2 The "OS Distribution Tape 2.2-1 2.3 "OS Operating Arrangement 2.3-1 2.4 Options And Assembly Parameters 2.4-1 3. "OS Monitor System Under IBSYS 3.1-1 3.1 Introduction 3.1-1 3.2 "OS Control Cards And Their Functions 3.2-1 Job Deck 3.2-4 3.3 MAD Under "OS 3.3-1 MAD Job Decks And Examples 3.3-2 3.4 ALGOL Under "OS 3.4-1 References To Hardware Representation 3.4-2 ALGOL Job Decks And Examples 3.4-7 'CODE' Procedure 3.4-9 ALGOL Input/Output 3.4-10 3.5 "OS Job Deck Composition In General 3.5-1 PING PONG 3.5-3 TEACHER And UNKNOWN Jobs 3.5-5 FORTRAN I1 ToMAD Translator 3.5-6 Regression Job 3.5-8 Example 3.5-20 3.6 MAMOS Organization And Coding Information 3.6-1 Low Core Package(10s) 3.6-2 Logical Input/Output Units 3.6-3 Non-Data Selects 3.6-4 Data Selects 3.6-5 Input OnSYSIN1 3.6-9 Output On SYSOUl 3.6-10 output on SYSPP1 3.6-10 Routines For1/0 Unit Tables 3.6-12 Octal Core Dump 3.6-14 System Records 3.6-14 Pause Routine 3.6-15 Floating Point Trap' 3.6-16 Subroutine Trace 3.6-16 V TABLE OF CONTEWS - Continued Page 3.7 UMAP Assembler Under "0s 3.7-1 Symbols 3.7-3 Elements, Terms, And Expressions 3.7-5 UMAP Card Format 3.7-10 Qualifiers 3.7-15 Literals 3.7-17 Error Cornnents And Error Flags 3.7-24 Pseudo-Operations 3.7-26 MACROS 3.7-55 Combined Operations Table 3.7-92 3.8 "OS Library Of Subroutines 3.8-1 vi Acknowledgements In the past months there have been man many hours expended in the preparation of the completed version of"OS. I would like to express my deep appreciation to the many people who so have freely contributed their time and effort in the preparation"OS of and without whose help, completion of the system would not have been possible. Much credit for the system must be given to the staff of the University of Michigan Computing Center, for without the many components of the Michigan Executive System which were adapted forMAMOS the monitor, MAMOS would not be worthyof being called a system. I am very grateful to Professor Bernard Galler of the University of Michigan for making the entire Michigan Executive System and write-ups available to the Computer Science Center. Many thanks are due to the staffof the University of Illinois Digital Computer Laboratory for their contribucionof the ALCOR-Illinois ALGOL compiler whichwas made a component of "OS. I would like to expressmy thanks to Messrs.John Bielec, George Lindamood, William Cleveland, Howard Wactlar, Dr.and Earl Schweppe who were very helpful in checking various partsof the system through their early use of"OS. Special thanks go to Mr. Robert Herbold for his ex- cellent help in finding some very elusive bugs, andMr. Johnto Montague for writing some subroutines and several test programs for the general check-out of the system. Also to Mr. Gunter Meyer for writing some sub- routines. Early use of "OS in courses taught by Dr. Earl Schweppe, Dr. Howard Tompkins, andthe faculty of the Electrical Engineering Department greatly aided in checking out the system. It is a pleasure to acknowledge also the valuable assistance rendered to "OS by a number of other installations.In particular to Mr. William Cahill, Head of the Mathematics and Computing Branch of the Theoretical Di- vision of the Goddard Space Flight Center for the use of his installation in checking "OS under the Direct Coupled System (E-IBSYS). Also to Messrs. Nate Dillard and Sam Waxof the above installation for their aid in getting MAMOS edited into their system. To Dr. Robert F. Rosin of the Yale Computing Center for earlyuse of MAMOS under DC-IBSYS and detection of some errorsin the system. Finally, many thanks to Mr. Jack Otley for his general assistance and in particular for getting together the descriptionof the "OS library; and to Mrs. StellaTobin, Miss Alexandra Sieg, and Miss Carol Fung for typing the write-up. Vii 1.1-1 1 The "OS Monitor And JOB Definition 1.1 Introduction This write-up describes the7090/7094 "OS Monitor. MAMOS is a sub-monitor in that it operates under theIBM Basic Monitor(IBSYS). MAMOS operates under7090/7094 IBSYS which has at least eight IBM 729 tape units, or under IBSYS for IBM704X to 709Y direct coupled systems. "OS processes programs written in MADthe language, the FORTRANI1 language, ALGOL language, and theUMAP language. UMAP is very similar to the FAP language under theFORTRAN I1 Monitor. Other language translators will be added to "OS in the future. Chapter 3 of this write-up contains "OS a description which is written for the general user. There are several references to section1.2 in Chapter 3, and except for section1.2 the general user may ignore the first 2 chaptersof this write-up. Chapter 2 is written mainly forthe systems programmer. .. ... .... - . .. ... .. .... .. 1.2-1 1.2 Sub-system Selection andJob Identification A deck of cards [DECK1 is defined hereas a card deck arranged in such a manner that when operated uponby "OS, it produces the desired result for the user. A job deck [JOB1is definedas one or more IBSYS control cards followed by a [DECK]. The IBSYS control cards are describedin IBM 7090/7094 Operating Systems Basic Monitor(IBSYS). Individual installations have several options in their use of the IBSYS control cards and it is impossible to describe, in general, the specific IBSYS cards required for a[JOB]. Hence a [JOB] is now defined for"OS as it operates under IBSYS at the Universityof Maryland Computer Science Center. A job deck [JOB] is definedas two IBSYS control cards followed by [DECK] as follows. $EXECUTE "OS $ID name*task*options$anycomment [ DECK] 1.2-2 $MECUTE is punched in card columns 1-8 and the system name"OS is punched starting in card column 16. This card is used by IBSYS to locate on the system tape, call in, and relinquish control"OS. to The second card above is the job (or identification) card, and it serves two purposes. 1) It is a signal for the beginningof a job, 2) It provides information for accounting. The job card has $ID punched in card columns1-3 and the name, task, and optional fields are punched in card columns7-66. The fields are separated by an asterisk (*). The dollar ($) character and the asterisk(*) character are not allowed within any of the fields. Any desired comment may follow the dollar sign which terminates the fields. The name and task fields are describedas follows. i) name field: This field consists of the users last name followed by any other identifying characters (except$ and *) the user may wish to use. The name field can be from6 to 18 characters in length. ii) task field: This field consists of 10 characters having the form xxx/yy/zzz where xxx is the department identification. yy is the year the task was established. zzz is the task serial number. There are6 optional fields which may be specified: time field: This field consists of a decimal integer followed by by the characterS (for seconds) or the characterM (for minutes). The specified time is the maximum time which the program will be allowed to run during execution. If the time specified is exceeded, then execution is terminated and processing of the next job is begun. print field: This field consists of a decimal integer followed by the character P (for pages). The specified number of pages is the maximum numberof pages allowed to be writtenon the output tape during execution. punch field: This field consists of a decimal integer followed by the character C (for cards). The specified number of cards is the maximum numberof cards allowed to be writtenon the punch tape during execution. 1.2-3 dump field: This field consists of two decimal integers sepa- rated by a slash and the second integer is followedby the character D (for dump).