DOCSLIB.ORG

JAMS User Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
JAMS User Guide JAMS User Guide Order Number: JAMS-UG-42 This manual provides a complete description of the Job Access & Management System. Revision/Update Information: This manual supersedes the Guide to the Job Access & Management System, Version 4.0. Operating System and Version: OpenVMS/VAX Version 6.2 or higher, OpenVMS/AXP V6.2 or higher Software Version: JAMS Version 4.2 The information in this document is subject to change without notice and should not be construed as a commitment by MVP Systems Incorporated. MVP Systems, Inc. assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. Restricted Rights Notice: Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. All Rights Reserved. Printed in the U.S.A. If you have questions about JAMS please feel free to call JAMS technical support at (866) 259-5267. Technical support is available around the clock, 24 hours a day, 7 days a week. The mailing address is: TECHNICAL SUPPORT DEPT. MVP SYSTEMS INC. 2700 E. MAIN ST. SUITE 108 COLUMBUS, OH 43209 E-Mail: [email protected] WWW: http://JAMS.mvpsi.com WWW: http://www.mvpsi.com The following are trademarks of Hewlett-Packard Company: Alpha, DECnet, DECwindows, OpenVMS, VAX, VMS, VMScluster. Window and Windows NT are registered trademarks of Microsoft Corporation. Motif is a registered trademark of The Open Group, Inc. Copyright ©2003 MVP Systems, Inc. Contents PREFACE x CHAPTER 1 OVERVIEW OF JAMS 1–1 1.1 INTRODUCTION 1–1 1.2 CAPABILITIES OF THE JOB ACCESS AND MANAGEMENT SYSTEM 1–1 1.2.1 User Access to Batch Processing 1–2 1.2.1.1 Menu based job submission • 1–3 1.2.1.2 DECwindows/Motif based job submission • 1–3 1.2.1.3 Command line interface • 1–3 1.2.1.4 Windows 9x/NT/2000 based job submission • 1–3 1.2.1.5 Callable interface • 1–3 1.2.2 Managing Batch Jobs 1–4 1.2.3 Tracking Batch Job History 1–4 1.2.4 Remote Access 1–4 1.2.5 Recurring Jobs 1–4 1.2.5.1 Time Based Schedules • 1–5 1.2.5.2 Event Based Schedules • 1–5 1.2.6 Maintaining Schedules 1–5 1.2.7 Control of Printed Reports 1–6 CHAPTER 2 GETTING STARTED WITH JAMS 2–1 2.1 AFTER THE INSTALLATION 2–1 2.1.1 Job Execution History 2–1 2.1.2 Job Failure Alerting 2–1 2.1.3 Job Monitoring and Management 2–1 2.2 DEFINING AND USING JAMS JOBS 2–1 2.3 SYSTEMS DEFINITIONS 2–2 2.4 JOB DEFINITIONS 2–3 iii Contents 2.4.1 Automatic Job Submission 2–3 2.4.2 Parameters 2–4 2.4.3 Source Code 2–4 2.5 SETUP DEFINITIONS 2–5 2.6 SEQUENCING 2–6 2.6.1 Setups 2–6 2.6.2 Dependencies 2–7 2.6.2.1 Job Dependencies • 2–7 2.6.2.2 Variable Dependencies • 2–8 2.6.3 Precheck Jobs 2–8 2.6.4 Resources 2–9 CHAPTER 3 GETTING STARTED ON WINDOWS NT/2000 3–1 3.1 GETTING READY FOR WINDOWS NT 3–1 3.1.1 Install and Configure the JAMS Agent 3–1 3.1.2 Define NT Usernames in JAMS 3–2 3.1.3 Grant ‘‘Log on as a batch job’’ to NT accounts or groups 3–2 3.1.3.1 Granting rights under Windows NT V4.0 • 3–2 3.1.3.2 Granting rights under Windows 2000 • 3–3 3.1.3.3 Granting rights with the NTRights.exe Utility • 3–3 3.2 CREATING NT JOBS 3–3 3.2.1 Windows NT Execution Methods 3–3 3.2.2 Windows NT Example Job 3–3 CHAPTER 4 GETTING STARTED ON UNIX 4–1 4.1 GETTING READY FOR UNIX 4–1 4.1.1 Define Unix Usernames in JAMS 4–1 4.1.2 Verify that the rexec daemon is enabled on your target 4–1 4.2 CREATING UNIX JOBS 4–2 4.2.1 Rexec Execution Methods 4–2 4.2.2 Rexec Example Job 4–2 iv Contents CHAPTER 5 USING JAMS_MASTER 5–1 5.1 JAMS_MASTER 5–1 5.1.1 Foreign Command Lines 5–1 5.2 CUSTOMIZING JAMS_MASTER 5–1 5.2.1 Remote Connections 5–2 5.2.2 Title 5–2 5.2.3 Default Job Submission Menu 5–2 5.2.4 Messages 5–2 5.2.5 Date and Time Format 5–3 5.2.6 Monitor Options 5–3 CHAPTER 6 THE SCREEN BASED ENVIRONMENT 6–1 6.1 THE MAIN MENU 6–1 6.1.1 History Inquiry 6–1 6.1.2 Definitions 6–4 6.1.2.1 Setup Definitions • 6–4 6.1.2.2 Job Definitions • 6–4 6.1.2.3 System Definitions • 6–5 6.1.2.4 Trigger Definitions • 6–5 6.1.2.5 Variable Definitions • 6–5 6.1.2.6 Menu Definitions • 6–5 6.1.3 Job Submission 6–5 6.1.4 Show Current Jobs 6–5 6.1.5 Monitor Current Jobs 6–6 6.1.5.1 Monitor Options • 6–8 6.1.5.2 Job Management Menu • 6–10 6.1.6 Management Functions 6–12 6.1.6.1 Named Times • 6–12 6.1.6.2 Dates • 6–12 6.1.6.3 Access Control • 6–13 6.1.6.4 Node Definitions • 6–13 6.1.6.5 Node Groups • 6–13 6.1.6.6 Configuration • 6–13 6.1.6.7 Date Types • 6–13 6.2 COMMON FUNCTIONS AND FEATURES 6–13 6.2.1 On-line Help 6–13 6.2.2 Menus 6–14 v Contents 6.2.3 Insert/Overstrike 6–14 6.2.4 Moving Between Fields 6–14 6.2.5 Exit Key 6–14 6.2.6 Find Key 6–15 6.2.7 List Screens 6–15 6.2.8 Screen Layout 6–15 6.2.9 Maintenance Functions 6–15 6.2.9.1 Maintenance Mode Menu/Indicator • 6–16 6.2.9.2 Key Fields • 6–17 6.2.9.3 Data Entry Screens • 6–17 6.2.9.4 Special Function Keys • 6–17 CHAPTER 7 JAMS WINDOWS INTERFACE 7–1 7.1 STARTING THE JAMS WINDOWS 9X/NT/2000 INTERFACE 7–1 7.2 SUBMIT WINDOW 7–1 7.2.1 Navigating the Window 7–1 7.2.2 File menu 7–2 7.2.3 Action menu 7–3 7.2.4 Window menu 7–3 7.3 SUBMITTING A JOB 7–3 7.4 MONITOR WINDOW 7–4 7.4.1 The Monitor Display 7–4 7.4.2 Monitor Detail Lines 7–5 7.4.3 File menu 7–6 7.4.4 Action menu 7–6 7.4.5 Window menu 7–7 7.5 HISTORY WINDOW 7–7 7.5.1 The History Display 7–8 7.5.2 File menu 7–8 7.5.3 Action menu 7–9 7.5.4 Window menu 7–9 7.5.5 History Search Window 7–9 7.6 USING HELP 7–10 vi Contents CHAPTER 8 JAMS DECWINDOWS/MOTIF INTERFACE 8–1 8.1 STARTING THE JAMS DECWINDOWS/MOTIF INTERFACE 8–1 8.1.1 Remote Connections 8–1 8.2 SUBMIT WINDOW 8–1 8.2.1 Navigating the Window 8–2 8.2.2 File menu 8–2 8.2.3 Action menu 8–3 8.2.4 Window menu 8–4 8.3 SUBMITTING A JOB 8–4 8.4 MONITOR WINDOW 8–4 8.4.1 The Monitor Display 8–4 8.4.2 Monitor Detail Lines 8–4 8.4.3 File menu 8–6 8.4.4 Action menu 8–7 8.4.5 Window menu 8–8 8.5 HISTORY WINDOW 8–8 8.5.1 The History Display 8–9 8.5.2 File menu 8–9 8.5.3 Action menu 8–9 8.5.4 Window menu 8–10 8.5.5 History Search Window 8–10 8.6 DEFINITIONS WINDOW 8–11 8.6.1 Button Bar 8–12 8.6.2 The Definitions Display 8–12 8.6.3 File menu 8–12 8.6.4 Action menu 8–13 8.6.5 Window menu 8–13 8.6.6 Management menu 8–14 8.6.7 Search Criteria 8–14 8.7 CONNECT DIALOG 8–14 8.8 USING HELP 8–15 vii Contents CHAPTER 9 SUBMITTING AD HOC JOBS 9–1 9.1 SUBMITTING A JAMS JOB 9–1 9.1.1 Replacing the OpenVMS SUBMIT Command 9–1 9.2 SELECTING A JOB TO SUBMIT 9–2 9.2.1 Parameters 9–2 9.2.2 Report Overrides 9–4 CHAPTER 10 ENTERING GENERIC DATE SPECIFICATIONS 10–1 10.1 DATE SPECIFICATIONS 10–1 10.1.1 Scheduled Date 10–1 10.1.2 Default Parameter Values 10–1 10.1.3 Setup Parameter Values 10–1 10.2 SIMPLE SPECIFICATIONS 10–2 10.2.1 Description of components 10–2 10.2.2 Valid Simple Date Specifications 10–3 10.3 COMPLEX SPECIFICATIONS 10–3 10.3.1 User Defined Periods 10–4 10.3.2 Weeks 10–4 10.3.3 Valid Complex Date Specifications 10–4 CHAPTER 11 MANAGING JAMS 11–1 11.1 JAMS PROCESSES 11–1 11.1.1 The JAMS_MONITOR process 11–1 11.1.2 The JAMS_SCHEDULE process 11–2 11.1.2.1 Controlling the JAMS_SCHEDULE node selection • 11–2 11.1.2.2 Customizing JAMS_SCHEDULE startup • 11–3 11.1.3 The JAMS_NETWORK process 11–3 11.1.3.1 Controlling the JAMS_NETWORK node selection • 11–3 11.1.4 The JAMS Agent Windows NT/2000 Service 11–4 11.1.5 Log Files 11–5 viii Contents 11.2 RECURRING JOBS 11–5 11.3 RELATIVE CPU POWER RATINGS 11–5 11.4 SECURITY 11–6 11.5 BACKING UP THE JAMS DATABASE 11–7 11.6 JAMS QUEUE CHARACTERISTICS 11–7 11.6.1 Production & Debug Characteristics 11–8 INDEX FIGURES 6–1 Main Menu 6–2 6–2 History List Screen 6–3 6–3 History Detail Screen 6–4 6–4 Monitor Jobs Display 6–6 6–5 Monitor Options 6–9 6–6 Job Management Pop-up Menu 6–11 6–7 Job Detail 6–12 6–8 Sample JAMS Screen 6–16 7–1 Windows Submit Window 7–2 7–2 Windows Monitor Window 7–4 7–3 Windows History Window 7–8 8–1 DECwindows Submit Window 8–2 8–2 DECwindows Monitor Window 8–5 8–3 DECwindows History Window 8–8 8–4 DECwindows Definitions Window 8–11 9–1 Job Submission Menu 9–3 9–2 Sample Parameter Form 9–4 9–3 Sample Job/Report Override Form, one Report 9–5 9–4 Sample Job/Report Override Form, many Reports 9–6 ix Preface This manual provides a detailed description of the capabilities of the Job Access & Management System (JAMS).
Load more

Recommended publications
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • Flashboot User Manual
    FlashBoot User Manual © 2015 Mikhail Kupchik Contents 3 Table of Contents Foreword 0 Part I Introduction 5 1 Product................................................................................................................................... Overview 5 2 Why USB................................................................................................................................... Flash Disks? 5 3 Why FlashBoot?................................................................................................................................... 6 4 System................................................................................................................................... Requirements 7 5 Limitations................................................................................................................................... of Demo Version 8 6 Demo Version................................................................................................................................... -> Full Version 8 7 Support................................................................................................................................... & Feedback 8 Part II CD/DVD to USB conversions 9 1 Install ...................................................................................................................................full Win8/8.1/10 -> USB [BIOS mode] 9 2 Install................................................................................................................................... full
    [Show full text]
  • Level One Benchmark Windows NT 4.0 Operating Systems V1.0.5
    Level One Benchmark Windows NT 4.0 Operating Systems V1.0.5 Copyright 2003, The Center for Internet Security www.cisecurity.org Page 2 of 32 Terms of Use Agreement Background. CIS provides benchmarks, scoring tools, software, data, information, suggestions, ideas, and other services and materials from the CIS website or elsewhere (“Products”) as a public service to Internet users worldwide. Recommendations contained in the Products (“Recommendations”) result from a consensus-building process that involves many security experts and are generally generic in nature. The Recommendations are intended to provide helpful information to organizations attempting to evaluate or improve the security of their networks, systems and devices. Proper use of the Recommendations requires careful analysis and adaptation to specific user requirements. The Recommendations are not in any way intended to be a “quick fix” for anyone’s information security needs. No representations, warranties and covenants. CIS makes no representations, warranties or covenants whatsoever as to (i) the positive or negative effect of the Products or the Recommendations on the operation or the security of any particular network, computer system, network device, software, hardware, or any component of any of the foregoing or (ii) the accuracy, reliability, timeliness or completeness of any Product or Recommendation. CIS is providing the Products and the Recommendations “as is” and “as available” without representations, warranties or covenants of any kind. User agreements. By using the Products and/or the Recommendations, I and/or my organization (“we”) agree and acknowledge that: 1. No network, system, device, hardware, software or component can be made fully secure; 2.
    [Show full text]
  • 04 ISC 265 TESIS .Pdf
    Sistema Académico Web SAITICC UNIVERSIDAD TÉCNICA DEL NORTE FACULTAD DE INGENIERÍA EN CIENCIAS APLICADAS CARRERA DE INGENIERÍA EN SISTEMAS COMPUTACIONALES TRABAJO DE GRADO PREVIO A LA OBTENCIÓN DEL TÍTULO EN INGENIERÍA EN SISTEMAS COMPUTACIONALES TEMA “SISTEMA ACADÉMICO WEB UTILIZANDO SOFTWARE LIBRE” AUTOR: Edwin Fernando Valencia Pavón. DIRECTOR: Ing. Pedro Granda. Ibarra - Ecuador 2012 – 2013 Fernando Valencia Pavón ii Sistema Académico Web SAITICC CERTIFICACIÓN Certifico que el trabajo de Tesis ― IMPLEMENTACIÓN DE UN SISTEMA ACADEMICO WEB PARA EL INSTITUTO TECNOLÓGICO SUPERIOR DE LA INDUSTRIA DEL CUERO DEL CANTÓN COTACACHI” con el aplicativo "DISEÑO E IMPLEMENTACION DELSISTEMA ACADEMICO WEB PARA EL INSTITUTO TECNOLOGICO DE LA INSDUSTRIA DEL CUERO. ha sido realizado en su totalidad por la señor: Edwin Fernando Valencia Pavón ………………………………………… Ing. Pedro Granda Director de la Tesis. Fernando Valencia Pavón iii Sistema Académico Web SAITICC UNIVERSIDAD TÉCNICA DEL NORTE BIBLIOTECA UNIVERSITARIA AUTORIZACIÓN DE USO Y PUBLICACIÓN A FAVOR DE LA UNIVERSIDAD TÉCNICA DEL NORTE IDENTIFICACIÓN DE LA OBRA La Universidad Técnica del Norte dentro del proyecto Repositorio Digital Institucional, determino la necesidad de disponer de textos completos en formato digital con la finalidad de apoyar los procesos de investigación, docencia y extensión de la Universidad. Por medio del presente documento dejo sentada mi voluntad de participar en este proyecto, para lo cual pongo a disposición la siguiente información: DATOS DE CONTACTO CÉDULA DE IDENTIDAD: 100316986-7 APELLIDOS Y NOMBRES: Valencia Pavón Edwin Fernando DIRECCIÓN: Urbanización María José EMAIL: [email protected] TELÉFONO FIJO: 062928-583 TELÉFONO MÓVIL (0968398896) DATOS DE LA OBRA TÍTULO: SISTEMA ACADÉMICO WEB UTILIZANDO SOFTWARE LIBRE. AUTOR: EDWIN FERNANDO VALENCIA PAVÓN FECHA: Julio-2013 PROGRAMA: PREGRADO TÍTULO POR EL QUE INGENIERÍA EN SISTEMAS COMPUTACIONALES OPTA: DIRECTOR: ING.
    [Show full text]
  • Windows Intruder Detection Checklist
    Windows Intruder Detection Checklist http://www.cert.org/tech_tips/test.html CERT® Coordination Center and AusCERT Windows Intruder Detection Checklist This document is being published jointly by the CERT Coordination Center and AusCERT (Australian Computer Emergency Response Team). printable version A. Introduction B. General Advice Pertaining to Intrusion Detection C. Look for Signs that Your System may have been Compromised 1. A Word on Rootkits 2. Examine Log Files 3. Check for Odd User Accounts and Groups 4. Check All Groups for Unexpected User Membership 5. Look for Unauthorized User Rights 6. Check for Unauthorized Applications Starting Automatically 7. Check Your System Binaries for Alterations 8. Check Your Network Configurations for Unauthorized Entries 9. Check for Unauthorized Shares 10. Check for Any Jobs Scheduled to Run 11. Check for Unauthorized Processes 12. Look Throughout the System for Unusual or Hidden Files 13. Check for Altered Permissions on Files or Registry Keys 14. Check for Changes in User or Computer Policies 15. Ensure the System has not been Joined to a Different Domain 16. Audit for Intrusion Detection 17. Additional Information D. Consider Running Intrusion Detection Systems If Possible 1. Freeware/shareware Intrusion Detection Systems 2. Commercial Intrusion Detection Systems E. Review Other AusCERT and CERT Documents 1. Steps for Recovering from a Windows NT Compromise 2. Windows NT Configuration Guidelines 3. NIST Checklists F. Document Revision History A. Introduction This document outlines suggested steps for determining whether your Windows system has been compromised. System administrators can use this information to look for several types of break-ins. We also encourage you to review all sections of this document and modify your systems to address potential weaknesses.
    [Show full text]
  • Infosec Year in Review -- 1999
    InfoSec Year In Review -- 1999 M. E. Kabay, PhD, CISSP. Security Leader, INFOSEC Group, AtomicTangerine Inc. Category 11 Breaches of confidentiality Date 1999-01-29 Keyword data leakage privacy confidentiality control Web Source, Vol, No. RISKS 20 18 The Canadian consumer-tracking service Air Miles inadvertently left 50,000 records of applicants for its loyalty program publicly accessible on their Web site for an undetermined length of time. The Web site was offline as of 21 January until the problem was fixed. Date 1999-02-03 Keyword data leakage Web script QA vulnerability confidentiality Source, Vol, No. WIRED via PointCast An error in the configuration or programming of the F. A. O. Schwarz Web site resulted paradoxically in weakening the security of transactions deliberately completed by FAX instead of through SSL. Customers who declined to send their credit-card numbers via SSL ended up having their personal details — address and so forth — stored in a Web page that could be accessed by anyone entering a URL with an appropriate (even if randomly chosen) numerical component. Date 1999-02-10 Keyword e-commerce credit card personal information password privacy Source, Vol, No. RISKS 20 20 Prof. Ross Anderson of Cambridge University analyzed requirements on the AMAZON.COM online bookstore for credit card number, password, and personal details such as phone number. He identified several risks: (1) merchant retention of credit card numbers poses a far higher risk of capture than of capture in transit; (2) adding a password increases the likelihood of compromise because so many naïve users choose bad passwords and then write them down; (3) even the British site for Amazon contravenes European rules on protecting consumer privacy; (3) such practices make it easier for banks to reject their clients' claims of fraudulent use of their credit-card numbers.
    [Show full text]
  • RSX - 11 M-PLUS Mini-Reference
    RSX - 11 M-PLUS Mini-Reference Order No. AV-H435F-TC RSX - 11M-PLUS Mini-Reference Order Number. AV-H435F-TC RSX-ll M-PLUS Version 4.2 Digital Equipment Corporation Maynard, Massachusetts First Printing, September 1977 Revised, April 1982 Revised, April 1983 Revised, July 1985 R~vised, .September 1987 Revised, January 1989 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1977, 1982, 1983, 1985, 1987, 1989. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem VAX DEC/MMS lAS VAXcluster DECnet MASSBUS VMS DECsystem-lO PDP VT DECSYSTEM-20 PDT DECUS RSTS DECwriter RSX ~U~UIl~DTM ZK5077 Contents Preface vii Conventions ............................................... viii Online Help Files Online Help Files ............................................. 3 Command Line Interpreters Monitor Console Routine (MCR) Commands ......................... 7 Digital Command Language (DCL) ............................... 21 utilities BAD Command Summary ...................................... 67 iii BRU Command Summary ...................................... 69 CMP Command Summary ...................................... 74 DMP Command Summary .....................................
    [Show full text]
  • Unit 5 Windows 2000/XP History, and Data Management
    Unit 5 Windows 2000/XP History, and Data Management Copyright © 2002 Heathkit Company, Inc. All rights reserved. Microsoft Windows98 Microsoft WindowsMe Microsoft Windows 2000 Professional Microsoft WindowsXP 2 Windows 2000/XP or Windows 9x (95/98/Me)? Windows 9x Windows 2000/XP Runs on today’s Runs on “nearly any hardware, doesn’t run old hardware” well or at all on marginal hardware Secure, more difficult to Open, easy to configure configure Supports lots of Device support somewhat devices limited, so far 3 Windows XP or Windows 9x? If you need: Choose: Reliable, solid security Windows 2000/XP “Crash-proof” system Windows 2000/XP Support for older/slower Windows 9x machines Easy setup and configuration Windows 9x Support for that older scanner, Windows 9x CD Writer, NIC, Video, etc. 4 The Windows Business Consumer Universe 1990 Windows 3.1 Windows NT 3.51 Windows for Workgroups Windows NT 4 Windows 95 Windows 98 Windows 2000 Windows Me Today Windows XP Pro/Home 5 The Windows Business Consumer Universe 1990 Windows 3.1 Windows NT 3.51 Windows for Workgroups Windows NT 4 Windows 95 Windows 98 Windows 2000 Windows Me Today Windows XP Pro/Home 6 The TheWindows Windows Business Universe Consumer Universe 1990 Windows 3.1 Windows NT 3.51 Windows for Workgroups Windows NT 4 Windows 95 Windows 98 Windows 2000 Windows Me Today Windows XP Pro/Home 7 Windows XP Flavors • Windows XP Professional • Windows XP Home • Windows 2003 Server • Windows 2003 Enterprise Server • Windows 2003 Datacenter Server 8 Windows Package Types • Upgrade • Full Version
    [Show full text]
  • Microsoft Windows for MS
    Month Year Version Major Changes or Remarks Microsoft buys non-exclusive rights to market Pattersons Quick & Dirty Operating System from December 1980 QDOS Seattle Computer Products (Developed as 86-DOS) (Which is a clone of Digital Researches C P/M in virtually every respect) Microsoft buys all rights to 86-DOS from Seattle Computer Products, and the name MS-DOS is July 1981 86-DOS adopted for Microsoft's purposes and IBM PC- DOS for shipment with IBM PCs (For Computers with the Intel 8086 Processor) Digital Research release CP/M 86 for the Intel Q3 1981 CP/M 86 8086 Processer Pre-Release PC-DOS produced for IBM Personal Mid 1981 PC-DOS 1.0 Computers (IBM PC) Supported 16K of RAM, ~ Single-sided 5.25" 160Kb Floppy Disk OEM PC-DOS for IBM Corporation. (First August 1982 PC-DOS 1.1 Release Version) OEM Version for Zenith Computer Corporation.. (Also known as Z-DOS) This added support for September 1982 MS-DOS 1.25 Double-Sided 5.25" 320Kb Floppy Disks. Previously the disk had to be turned over to use the other side Digital Research release CP/M Plus for the Q4 1982 CP/M Plus Intel 8086 Processer OEM Version For Zenith - This added support for IBM's 10 MB Hard Disk, Directories and Double- March 1983 MS-DOS 2.0 Density 5.25" Floppy Disks with capacities of 360 Kb OEM PC-DOS for IBM Corporation. - Released March 1983 PC-DOS 2.0 to support the IBM XT Microsoft first announces it intention to create a GUI (Graphical User Interface) for its existing MS-DOS Operating System.
    [Show full text]
  • L38 Ñ Windows XP
    History History (cont.) (Timeline from www.cgonline.com) 10/81 — IBM PC (“Personal Computer”) 10/88 — OS/2 1.1 (Windows-like GUI, end and PC-DOS 1.0 of collaboration when IBM gets upset with Microsoft for improving Windows) 3/83 — Microsoft MS-DOS 2.0 (hard disk, file system) 5/90 — Windows 3.0 (big success!) 11/83 — Windows announced (vaporware!) 4/92 — Windows 3.1 (bug fixes etc.) 11/84 — MS-DOS 3.1 10/92 — Windows for Workgroups 3.1 (adds networking, but fails in market) 11/85 — Windows 1.0 (tiled windows, doesn’t do well in market) 5/93 — Windows NT 3.1 (visually like Windows 3.1, but stable 32-bit platform) 4/87 — IBM & Microsoft OS/2 1.0 (next generation, DOS-like command lines) 11/93 — Windows for Workgroups 3.11 (precursor to Windows 95) 12/87 — Windows/386 (uses 80386’s virtual memory to allow safe “preemptive” 5/94 — MS-DOS 6.22 (DOS final version) multitasking) 9/94 — Windows NT 3.5 6/95 — Windows NT 3.51 (faster) 1 Fall 2002, Lecture 38 2 Fall 2002, Lecture 38 History (cont.) What is Windows XP? 8/95 — Windows 95 (originally Windows I 32/64 -bit preemptive multitasking 4.0) (long file names, plug and play operating system for AMD K6/7, Intel hardware, taskbar and Start menu, IA32/64 and later microprocessors HUGE success in market!) ● Replaces Windows 95/98/Me as well as Windows NT/200 7/96 — Windows NT 4.0 (Windows 95 GUI, first successful version of NT) I Key goals 6/98 — Windows 98 (Windows 95 + ● security, reliability, ease of use Internet Explorer 4.0, success in market) ● Windows and POSIX compliance ● high performance, extensibility 2/00 — Windows 2000 (Windows NT 4.0 + plug and play, DirectX, USB, etc.) ● portability, international support 9/00 — Windows Me (Millennium Edition) I Various versions: XP Personal, XP (Windows 98 + IE 5.0, media support, Professional, XP Server last version in Windows 9x line) I Uses a micro-kernel architecture 9/01 — Windows XP (combines Windows ● Subsystems to provide OS personalities 2000 and ME, but based on NT/2000) for Win32, POSIX, etc.
    [Show full text]
  • MICROSOFT WINDOWS Early Versions Main Articles: Windows 1.0
    MICROSOFT WINDOWS Early versions Main articles: Windows 1.0, Windows 2.0, and Windows 2.1x Windows 1.0, the first version, released in 1985 The history of Windows dates back to September 1981, when Chase Bishop, a computer scientist, designed the first model of an electronic device and project "Interface Manager" was started. It was announced in November 1983 (after the Apple Lisa, but before the Macintosh) under the name "Windows", but Windows 1.0 was not released until November 1985.[5] Windows 1.0 achieved little popularity and was to compete with Apple's own operating system. Windows 1.0 is not a complete operating system; rather, it extends MS-DOS. The shell of Windows 1.0 is a program known as the MS- DOS Executive. Components included Calculator, Calendar, Cardfile, Clipboard viewer, Clock, Control Panel, Notepad, Paint, Reversi, Terminal and Write. Windows 1.0 does not allow overlapping windows. Instead all windows are tiled. Only modal dialog boxes may appear over other windows. Windows 2.0 was released in December 1987 and was more popular than its predecessor. It features several improvements to the user interface and memory management.[citation needed] Windows 2.03 changed the OS from tiled windows to overlapping windows. The result of this change led to Apple Computer filing a suit against Microsoft alleging infringement on Apple's copyrights.[6][7] Windows 2.0 also introduced more sophisticated keyboard shortcuts and could make use of expanded memory. Windows 2.1 was released in two different versions: Windows/286 and Windows/386. Windows/386 uses the virtual 8086 mode of Intel 80386 to multitask several DOS programs and the paged memory model to emulate expanded memory using available extended memory.
    [Show full text]
  • Major System Files, and Their Purpose: Windows 9X –Specific Files • IO.SYS the Io.Sys File Is an MS-DOS and Windows 9X
    Major System Files, and their purpose: Windows 9x –specific files IO.SYS The io.sys file is an MS-DOS and Windows 9x hidden system file that is used to load the operating system each time the computer boots. The file is not editable using normal text editors. MSDOS.SYS The MSDOS.SYS file is a hidden system file created on the root of the boot drive. To edit this file, type edit msdos.sys. The PC boot environment can be changed by changing the file contents. Given below is a typicalMSDOS.SYS file: Below is a sample MSDOS.SYS File [Paths] WinDir=C:\WINDOWS WinBootDir=C:\WINDOWS HostWinBootDrv=C [Options] BootGUI=1 Network=1 BootMulti=1 ; ;The following lines are required for compatibility with other programs. ;Do not remove them (MSDOS.SYS needs to be >1024 bytes). AUTOEXEC.BAT An AUTOEXEC.BAT file contains DOS commands that are executed automatically when a PC boots. The file is usually located in the root directory of the hard drive of the computer. The AUTOEXEC.BAT file is used to set defaults and to run programs that should be executed during startup. Example: PROMPT $P$G Use the PROMPT command to alter the default DOS prompt. The above command makes the DOS prompt display the current path and drive, and is very useful. COMMAND.COM 1. It does: The file contains internal command set and error messages 2. Default Attributes: Nil 3. Is it required for OS Start up: YES 4. Responsible for displaying the command prompt in a DOS based computer.
    [Show full text]