DOCSLIB.ORG

MTS Volume 14, 360/370______Assemblers______In MTS, for Details)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
MTS Volume 14, 360/370______Assemblers______In MTS, for Details) M T S The Michigan Terminal System Volume 14: 360/370 Assemblers in MTS May 1983 Updated September 1986 (Update 1) The University of Michigan Computing Center Ann Arbor, Michigan ***************************************************** * * * This obsoletes the August 1978 edition. * * * ***************************************************** 1 DISCLAIMER The MTS Manual is intended to represent the current state of the Michigan Terminal System (MTS), but because the system is constantly being developed, extended, and refined, sections of this volume will become obsolete. The user should refer to the Computing_________ Center______ Newsletter,__________ Computing Center Memos, and future Updates to this volume for the latest information about changes to MTS. Copyright 1983 by the Regents of the University of Michigan. Copying is permitted for nonprofit, educational use provided that (1) each repro duction is done without alteration and (2) the volume reference and date of publication are included. Permission to republish any portions of this manual should be obtained in writing from the Director of the University of Michigan Computing Center. 2 MTS 14: 360/370 Assemblers in MTS May 1983 Page Revised September 1986 PREFACE_______ The software developed by the Computing Center staff for the operation of the highspeed processor computer can be described as a multiprogramming supervisor that handles a number of resident, reentrant programs. Among them is a large subsystem, called MTS (Michigan Terminal System), for command interpretation, execution control, file management, and accounting maintenance. Most users interact with the computer’s resources through MTS. The MTS Manual is a series of volumes that describe in detail the facilities provided by the Michigan Terminal System. Administrative | policies of the Computing Center and the physical facilities provided | are described in other publications. | | The MTS volumes now in print are listed below. The date indicates | the most recent edition of each volume; however, since volumes are | periodically updated, users should check the file *CCPUBLICATIONS, or | watch for announcements in the UM__________________ Computing News, to ensure that their | MTS volumes are fully up to date. | | | Volume 1: The____________________________ Michigan Terminal System, January 1984 | Volume 2: Public________________________ File Descriptions, April 1982 | Volume 3: System______________________________ Subroutine Descriptions, April 1981 | Volume 4: Terminals_____________________________ and Networks in MTS, March 1984 | Volume 5: System_______________ Services, May 1983 | Volume 6: FORTRAN______________ in MTS, October 1983 | Volume 7: PL/I___________ in MTS, September 1982 | Volume 8: LISP____________________ and SLIP in MTS, June 1976 | Volume 9: SNOBOL4______________ in MTS, September 1975 | Volume 10: BASIC____________ in MTS, December 1980 | Volume 11: Plot_______________________ Description System, August 1978 | Volume 12: PIL/2____________ in MTS, December 1974 | Volume 13: The_____________________________ Symbolic Debugging System, September 1985 | Volume 14: 360/370_________________________ Assemblers in MTS, May 1983 | Volume 15: FORMAT__________________ and TEXT360, April 1977 | Volume 16: ALGOL______________ W in MTS, September 1980 | Volume 17: Integrated__________________________ Graphics System, December 1980 | Volume 18: The___________________ MTS File Editor, August 1985 | Volume 19: Tapes______________________ and Floppy Disks, February 1983 | Volume 20: Pascal_____________ in MTS, December 1985 | Volume 21: MTS_________________________________ Command Extensions and Macros, April 1986 Other volumes are in preparation. The numerical order of the volumes does not necessarily reflect the chronological order of their appearance; however, in general, the higher the number, the more specialized the volume. Volume 1, for example, introduces the user to 3 MTS 14: 360/370 Assemblers in MTS Page Revised September 1986 May 1983 MTS and describes in general the MTS operating system, while Volume 10 deals exclusively with BASIC. The attempt to make each volume complete in itself and reasonably independent of others in the series naturally results in a certain amount of repetition. Public file descriptions, for example, may appear in more than one volume. However, this arrangement permits the user to buy only those volumes that serve his or her immediate needs. Richard A. Salisbury General Editor 4 MTS 14: 360/370 Assemblers in MTS May 1983 PREFACE____________________ TO VOLUME 14 The May 1983 revision reflects the changes that have been made to MTS since August 1978. Some of these changes were described Update 1 (October 1979), Update 2 (April 1980), and Update 3 (January 1981) and are incorporated into this edition. Since January 1981, further changes have been made to the Message Macros and the Structured Programming Macros and are described herein. In addition, the descriptions of the *ASMG and *ASMT assemblers have been removed since they are no longer actively supported by the Computing Center. These descriptions are available through the *GENDOC program. The sections "IOH," "Extensions to the Amdahl 470 Operations," and "Extensions to the System/360 Model 67 Operations" have been moved into Volume 14 from MTS Volume 5, System_______________ Services. 5 MTS 14: 360/370 Assemblers in MTS May 1983 6 MTS 14: 360/370 Assemblers in MTS May 1983 Page Revised September 1986 Contents________ Preface . 3 EXIT . 77 FLOAT . 79 Preface to Volume 14 . 5 FREESPAC . 80 GETSPACE . 81 360/370 Assemblers in MTS . 11 GUSER . 82 INSTSET . 85 Assembler H . 13 IOH Macros . 87 *ASMH . 14 KWLHT . 89 Assembler Options . 14 KWRHT . 90 BATCH Option . 18 KWSET . 98 Assembler H Extensions . 18 LABEL . 99 I/O Unit Usage . 24 LITADDR . .100 SCARDS Input . 24 MAXxx, MINxx . .101 Macro Libraries and COPY MOUNT . .104 Sections . 24 MSG, PMSG, PHRASE . .105 SPRINT Output . 26 MTS . .106 SPUNCH and Unit 1 Output . 27 MTSCMD . .107 Diagnostics and Return Codes 27 MTSMODS . .108 Assembler H Messages . 28 QUIT . .109 Invoking ASMH from a Program 30 READ . .110 REQU . .113 Differences between *ASMG, RETURN . .115 *ASMH, and *ASMT . 33 REWIND . .117 SAVE . .118 Utility Programs for SCARDS . .120 Assembler Users . 41 SERCOM . .123 *ASMTIDY . 42 SPIE . .126 *PEXIT . 47 SPRINT . .128 SPUNCH . .131 Macro Libraries . 51 STIMER . .134 Using Macro Libraries . 52 SYSTEM . .137 Constructing a Macro Library 52 TRL, TRTL . .138 SystemSupplied Macros . 54 TRTAB . .139 ASMTYPE . 55 TTIMER . .143 A8, S8, A8R, S8R . 56 WRITE . .144 ASSIGN . 58 BPI . 59 The Message Macros . .147 CALL . 62 Examples . .147 CMD . 65 MSG Macro Operators . .148 CMDNOE . 66 The "IF" Operators . .156 CNTRL . 67 IF Operator Formats . .157 DFAD, DFSB, DFMP . 70 IF Comparison Operators . .157 DCI, DCINIT . 70.1 OUTPUT Operator . .158 DFIX, EFIX . 71 OUTPUT operators . .158 DISMOUNT . 72 Optional OUTPUT Operators .159 ENTER . 73 PICTURE Operator . .160 ERROR . 76 MSG Examples . .161 7 MTS 14: 360/370 Assemblers in MTS Page Revised September 1986 May 1983 Extensions to the Amdahl Structured Programming Macros .165 470/5860 Operations . .261 Logical Expressions . .165 ExtendedBranch Operations .261 Simple Conditions . .166 Branch and Store . .261 Compound Conditions . .171 ExtendedPrecision IF, THEN, ELSE, ELSEIF, FloatingPoint Operations . .262 ENDIF . .173 Divide . .262 DOCASE, CASE, ELSECASE, Search List Instruction . .264 ENDCASE . .176 DO, ENDDO . .179 Extensions to the System/360 REDO, EXITDO, NEXTDO . .185 Model 67 Operations . .265 DEFCC . .187 ExtendedPrecision FLAGS . .189 FloatingPoint Operations . .265 FLAGVAL . .192 Add Double . .266 SET . .193 Subtract Double . .267 TEST . .195 Multiply Double . .268 MACSET . .197 MixedPrecision FloatingPoint Operations . .269 IOH . .201 Load Mixed . .269 Introduction . .201 Add Mixed . .269 A Simple Case . .201 Subtract Mixed . .269 Format Terms . .203 Multiply Mixed . .270 Types of Format Divide Mixed . .270 Specifications . .204 Swap Register Instruction . .271 Integer . .204 Search List Instruction . .271 FloatingPoint (Ftype) . .204 FloatingPoint (Etype) . .206 The MacroLibrary Editor . .279 Character . .207 MacroLibrary Editor Hexadecimal . .207 Command Language . .282 Packed Decimal . .208 MacroLibrary Editor Literals . .208 Commands . .285 Spaces and Tabs . .209 ADD . .285 Line Skips . .210 BUILDIR . .285 Modifiers . .210 CLEAR . .285 Multiplicities, Groups, COMMENT . .286 and Blocks . .212 COPY . .286 FormatBreak Characters . .213 CREATE . .286 Rescanning the Format . .214 DELETE . .287 Standard Format I/O . .215 DISPLAY . .287 IOH Macros . .217 EDIT . .287 Special Features of IOH . .224 EMPTY . .288 Additional Entry Points EXPLAIN . .288 to IOH . .224 HELP . .289 Format Variables . .229 INCLUDE . .289 Changing Defaults . .233 LIST . .289 Appendix A: IOH Format MCMD . .290 Specifications . .238 MTS . .290 Appendix B: IOH Calling PUNCH . .290 Sequences . .255 RENAME . .291 General Structure of the RENUMBER . .291 Calling Sequence . .255 REPLACE . .292 Description of the OPEN RETURN . .292 and CLOSE Routines . .257 8 MTS 14: 360/370 Assemblers in MTS May 1983 Page Revised September 1986 SET . .292 External Dummy Sections STOP . .293 (Assembler F only) . .312 UPDATE . .294 COM Define Blank Common Command Modifiers . .295 Control Section . .312 BREAK . .295 MachineInstructions . .313 COMSAVE . .295 Instruction Alignment and EMPTY . .295 Checking . .313 FULL . .295 Operand Fields and HDRGEN . .296 Subfields . .313
Load more

Recommended publications
  • CA Top Secret for Z/OS Control Options Guide
    CA Top Secret® for z/OS Control Options Guide r15 Ninth Edition This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • OS Structures and System Calls
    COS 318: Operating Systems OS Structures and System Calls Kai Li Computer Science Department Princeton University (http://www.cs.princeton.edu/courses/cos318/) Outline Protection mechanisms OS structures System and library calls 2 Protection Issues CPU Kernel has the ability to take CPU away from users to prevent a user from using the CPU forever Users should not have such an ability Memory Prevent a user from accessing others’ data Prevent users from modifying kernel code and data structures I/O Prevent users from performing “illegal” I/Os Question What’s the difference between protection and security? 3 Architecture Support: Privileged Mode An interrupt or exception (INT) User mode Kernel (privileged) mode • Regular instructions • Regular instructions • Access user memory • Privileged instructions • Access user memory • Access kernel memory A special instruction (IRET) 4 Privileged Instruction Examples Memory address mapping Flush or invalidate data cache Invalidate TLB entries Load and read system registers Change processor modes from kernel to user Change the voltage and frequency of processor Halt a processor Reset a processor Perform I/O operations 5 x86 Protection Rings Privileged instructions Can be executed only When current privileged Level (CPR) is 0 Operating system kernel Level 0 Operating system services Level 1 Level 2 Applications Level 3 6 Layered Structure Hiding information at each layer Layered dependency Examples Level N THE (6 layers) . MS-DOS (4 layers) . Pros Level 2 Layered abstraction
    [Show full text]
  • CA Top Secret R16 Security Target
    CA Top Secret r16 Security Target ST Version: 1.0 August 18, 2017 3333 Warrenville Road Suite 800 Lisle, IL 60532 Prepared By: Cyber Assurance Testing Laboratory 304 Sentinel Drive, Suite 100 Annapolis Junction, MD 20701 Security Target CA Top Secret r16 Table of Contents 1 Security Target Introduction ................................................................................................................. 6 1.1 ST Reference ................................................................................................................................. 6 1.1.1 ST Identification ................................................................................................................... 6 1.1.2 Document Organization ........................................................................................................ 6 1.1.3 Terminology .......................................................................................................................... 7 1.1.4 Acronyms .............................................................................................................................. 8 1.1.5 References ............................................................................................................................. 9 1.2 TOE Reference .............................................................................................................................. 9 1.3 TOE Overview .............................................................................................................................
    [Show full text]
  • CICS Essentials Auditing CICS – a Beginner’S Guide
    CICS Essentials Auditing CICS – A Beginner’s Guide Julie-Ann Williams Mike Cairns Martin Underwood Craig Warren ii CICS ESSENTIALS Foreword by Brian Cummings A thorough Audit Guide for CICS is something that is long overdue. This document provides a wealth of information about CICS, its operations, and its various resources and capabilities along with audit guidelines and recommendations. Various documents on AuditNet and other sources have taken a stab at parts or all of CICS, but are likely not up to date or sufficiently complete. CICS largely remains an environment that holds its mysteries against auditors and security officers alike. The results of poor understanding can lead to dangerous levels of unidentified risk to the applications and sensitive information of entities that use the power of CICS for critical business applications. Unlike any other environment, CICS security implementations fail in the first place because all of the security control is often only focused on transactions. Transactions are many levels of resources removed from the data files and data bases they query or update. In the end, we see the greatest level of security established for the least sophisticated technical users – end business users, and the least security facing the most technically sophisticated – the CICS sub-system programmer and the CICS Application programmer. For example, it is typical to leave FCT resources unsecured and to allow the CICS regions to have total rights to the data sets they access. This condition gives sub-system and application programmers full-reign to use CICS utilities to inherit the CICS regions’ authorities and gain full access to freely browse and update data.
    [Show full text]
  • 402197 350 System Manual.Book
    350 Cable Survey System System Manual Covers DeepView Software Version 5.x.x and Firmware Version 3.7 TSS (International) Ltd 1, Garnett Close Greycaine Industrial Estate Watford, Herts, WD24 7GL Telephone +44 (0)1923 470800 Facsimile +44 (0)1923 470842 24 hr Customer Support +44 (0)7899 665603 e-mail: [email protected] The information in this Manual is subject to change without notice and does not represent a commitment on the part of TSS (International) Ltd Document P/N 402197 Issue 2.4 abcdef January 2008 1 9 9 3 THE QUEEN'S AWARD FOR EXPORT ACHIEVEMENT Contents CAUTIONARY NOTICE This System Manual contains full installation and operating instructions and is an important part of the 350 System. This Manual should remain easily available for use by those who will install, operate and maintain the System. WARNINGS and CAUTIONS Where appropriate, this Manual includes important safety information. Safety infor- mation appears as WARNING and CAUTION instructions. You must obey these instructions: ❐ WARNING instructions alert you to a potential risk of death or injury to users of the 350 System. ❐ CAUTION instructions alert you to the potential risk of damage to the 350 System. For your convenience, the Table of Contents section includes copies of all the WARNING and CAUTION instructions contained in this Manual. Technical Support and contact information TSS (International) Ltd 1 Garnett Close, Greycaine Industrial Estate, Watford, Herts, WD24 7GL Tel: +44 (0)1923 470800 Fax: +44 (0)1923 470842 Out of UK Hours Technical Helpline: +44 (0)7899
    [Show full text]
  • Technical Services Attachment for Technology Support Services (TSS)
    Technical Services Attachment IBM Deutschland GmbH for T echnology S upport Services (TSS) Offerings Using this Attachment, Client may order TSS offerings from IBM. Additional details are provided in Transaction Documents (TDs). The agreement in place between the parties (CRA or equivalent) referenced in the signature block, this Attachment, and TDs are the complete agreement regarding TSS transactions hereunder. 1. Services IBM will provide Services, as described in this Technical Services Attachment for TSS Offerings (Attachment) and Statements of Work (SOW), Transaction Documents, and Change Authorizations (collectively Transaction Documents or TDs), to support Client’s Eligible Machines and Eligible Programs (collectively Eligible Products). This Attachment replaces all other previously accepted versions of this Attachment for the Client named in the signature block, as to new transactions dated after the effective date of this Attachment. IBM will identify Eligible Products, Specified Locations (entire information processing environment, or a portion thereof, at multiple sites or a single building), hours of coverage selected, applicable Services, and the contract period, in TDs. Additional details may be documented in the TD, as applicable to the specific transaction. Client may place service requests 24x7, by voice or electronically, however IBM will begin servicing the request during the applicable entitled coverage days and hours. Coverage is based on the time zone where the Eligible Machine is located. IBM provides Services during the hours of service selected in the Transaction Document. Eligible Machines must meet IBM’s safety and serviceability requirements. Any IBM inspection for maintenance eligibility is subject to a charge. IBM reserves the right to inspect a Machine within one month from the start of Service.
    [Show full text]
  • Norco College Technology Committee Meeting 12:50Pm-1:50 P.M
    Norco College Technology Committee Meeting 12:50pm-1:50 p.m. CSS 219 December 13, 2017 MINUTES Present Absent Ruth Leal (Co-Chair) Cathy Brotherton (CIS/BEIT) Damon Nance (Library) Kim K. Kamerin (AHWL) Daniel Lambros (IMC) Deven Fafard (ASNC) Sergio Quiroz (ASNC) Daren Koch (Tutorial) Lenny Riley (DOI) Guest James Finley (CIS/GAM) Ricardo Aguilera (TSS) Janet Frewing (Math) Mike Angeles (TSS) Mitzi Sloniger (COMM) Frank Martinez (TSS) Vanessa Acosta (A&R) 1. Call to Order 12:50 p.m. 2. Consent Calendar- Ruth Leal a. October 19, 2017 Minutes were reviewed. b. November 9, 2017 Minutes were reviewed. Motion (Finley/Frewing). Two abstentions. Approved. 3. Technology Plan – Ruth a. Subcommittees Report - Ms. Leal provided an update regarding the subcommittees. i. Goal #6 – Phase II computers were not all installed in the summer as reported and an email has been sent to all of the users to see if their computer was replaced or still needs to be replaced. Responses are slow but the committee will continue to follow-up. TSS will use the computers in inventory which were purchased for this in last year’s resource allocation process. TSS reported that there were 53 computers in the warehouse after installation of the podium computer project. The Phase II list was shared with Business Services and TSS in the September 2017. The committee will be updated on this in the spring. The Technology Principles and Guidelines were updated to reflect the prioritization process and new template approved by the Technology Committee. The committee reviewed the document. Motion (Acosta/Sloniger).
    [Show full text]
  • A Technical History of National CSS
    A Technical History of National CSS By Harold Feinleib Written: March 4, 2005 CHM Reference number: R0363.2016 A Technical History of National CSS By Harold Feinleib I knew I wanted to go into computers when I got my first program to work. That was quite a thrill. It happened in 1964 during my senior year at Cornell when I took the only course given in computers. I had to look to the Electrical Engineering school where we worked on a Burroughs 220, a computer filled with thousands of vacuum tubes that took up a good sized room. It was actually a very nice computer because it worked in decimal instead of binary. That memorable program was of course a Sort program—I had to sort a list of numbers. I wonder how many sort programs have been written before or since. It must be millions. With great enthusiasm, I interviewed at the campus-recruiting program where companies sent people to find new employees for their organization. In the 1960’s, unlike today, the job market was very active and no one had a problem getting started right after they graduated from college. I got some interest from three companies: Equitable Life to work in their actuarial program in New York City; IBM as a programmer to work in upstate NY; and with the Service Bureau Corporation to also work in midtown Manhattan. New York City was very appealing to me; I was 20 years old, and living in Manhattan was a very exciting prospect, so I took great interest in the Equitable and the SBC interviews.
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • MTS Volume 1, for Example, Introduces the User to MTS and Describes in General the MTS Operating System, While MTS Volume 10 Deals Exclusively with BASIC
    M T S The Michigan Terminal System The Michigan Terminal System Volume 1 Reference R1001 November 1991 University of Michigan Information Technology Division Consulting and Support Services DISCLAIMER The MTS manuals are intended to represent the current state of the Michigan Terminal System (MTS), but because the system is constantly being developed, extended, and refined, sections of this volume will become obsolete. The user should refer to the Information Technology Digest and other ITD documentation for the latest information about changes to MTS. Copyright 1991 by the Regents of the University of Michigan. Copying is permitted for nonprofit, educational use provided that (1) each reproduction is done without alteration and (2) the volume reference and date of publication are included. 2 CONTENTS Preface ........................................................................................................................................................ 9 Preface to Volume 1 .................................................................................................................................. 11 A Brief Overview of MTS .......................................................................................................................... 13 History .................................................................................................................................................. 13 Access to the System ...........................................................................................................................
    [Show full text]
  • CS 1550: Introduction to Operating Systems
    Operating Systems Lecture1 - Introduction Golestan University Hossein Momeni [email protected] Outline What is an operating system? Operating systems history Operating system concepts System calls Operating system structure User interface to the operating system Anatomy of a system call 2 Operating Systems Course- By: Hossein Momeni Samples of Operating Systems IBSYS (IBM 7090) MACH OS/360 (IBM 360) Apollo DOMAIN TSS/360 (360 mod 67) Unix (System V & BSD) Michigan Terminal System Apple Mac (v. 1– v. 9) CP/CMS & VM 370 MS-DOS MULTICS (GE 645) Windows NT, 2000, XP, 7 Alto (Xerox PARC) Novell Netware Pilot (Xerox STAR) CP/M Linux IRIX FreeBSD Solaris PalmOS MVS PocketPC VxWorks VxWorks 3 Operating Systems Course- By: Hossein Momeni Samples of Operating Systems (continue…) 4 Operating Systems Course- By: Hossein Momeni What is an Operating System? An Operating System is a program that acts as an intermediary/interface between a user of a computer and the computer hardware. It is an extended machine Hides the messy details which must be performed Presents user with a virtual machine, easier to use It is a resource manager Each program gets time with the resource Each program gets space on the resource 5 Operating Systems Course- By: Hossein Momeni Static View of System Components User 1 User 2 User 3 User 4 … User n Compiler Editor Database Calculator WP Operating System Hardware 6 Operating Systems Course- By: Hossein Momeni Dynamic View of System Components 7 Operating Systems Course- By: Hossein Momeni
    [Show full text]
  • Advanced Authentication Connector for Z/OS® Installation and Getting Started Guide © Copyright 2017 - 2020 Micro Focus Or One of Its Affiliates
    Micro Focus® Advanced Authentication Connector for z/OS® Installation and Getting Started Guide © Copyright 2017 - 2020 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Release: 1.1 Publication date: Updated May 2020 Table of Contents Welcome to Micro Focus® Advanced Authentication Connector for z/OS® . 5 Typographical Conventions . 6 Chapter 1 Overview . 7 Chapter 2 Implementing the Micro Focus Advanced Authentication Connector for z/OS . 9 Prerequisites . 10 Uploading the AACZ Product Distribution Files to the Host . 10 Creating the AACZ Started Task . 10 Additional Notes About Creating the AACZ Started Task. 12 Sample Start-Up Parameters. 12 Notes on the Use of Signed Certificates . 14 Using a Certificate that Has Been Signed by a Certificate Authority . 15 Using a Self-Signed Certificate . 15 RACF, ACF2, and Top Secret Requirements and Commands . 15 Defining an MFA Profile . 15 Defining Users to the NetIQ AA Server.
    [Show full text]