DOCSLIB.ORG

Uniaccess for OS 2200 System Administration Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Uniaccess for OS 2200 System Administration Guide UniAccess for OS 2200 System Administration Guide Title UniAccess 10R3 Product Suite Release 10R3 Document Version: 1.00 Last Revised: October 31, 2005 Copyright 2005. All rights reserved. Principal Authorship AIS Technical Publications Department Document Version This publication pertains to Release 10R3, version 1.00 of the Applied Information Sciences OS 2200 connectivity software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement and may be used or copied only in accordance with the terms of the agreement. Document Feedback The Applied Information Sciences Technical Publications Department welcomes corrections and comments on its documents. Please send corrections and comments to UniAccess Technical Support at the address below. Applied Information Sciences, Inc. 1850 Centennial Park Drive Reston, VA 20191 USA Phone (703) 860-7808 FAX (703) 860-7820 E-mail [email protected] Document Orders and Upgrades UniAccess documentation is provided on the UniAccess 10R3 PC Client CD for online viewing with Adobe Acrobat Reader. To order this CD, contact AIS at the above number or retrieve the documents from the Internet at http://www.uniaccess.com. Customers may make copies of the UniAccess 10R3 PC Client CD for their in-house use. Additionally, customers may print copies of the UniAccess documentation from the CD for their in-house use. Customers may purchase printed copies of any document or the right to make photocopies of printed documentation for their in-house use. To order printed documents or photocopy rights, contact AIS at the address given above. Upgrades are provided only at regularly scheduled software release dates. Copyright 1989 to 2005 Applied Information Sciences, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical or otherwise, without prior written permission of Applied Information Sciences, Inc. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in FAR subparagraphs 52.227-19(a)-(d) for civilian agency contracts and DFARS 252.227-7013(c)(1)(ii) for Department of Defense contracts. Applied Information Sciences, Inc. reserves all unpublished rights under the copyright laws of the United States. Applied Information Sciences Trademarks UniAccessTM is a trademark of Applied Information Sciences, Inc. Sybase Trademarks Sybase®, SYBASE® (logo), SQL Server®, Transact-SQL®, PowerBuilder®, and Adaptive Server® Enterprise are registered trademarks of Sybase, Inc. Client-LibraryTM, CT-LibraryTM, DB-LibraryTM, Embedded SQLTM, Enterprise Client/ ServerTM, Net-LibraryTM, Open ClientTM, Open ServerTM, and Tabular Data StreamTM are trademarks of Sybase, Inc. Other Trademarks Microsoft® is a registered trademark of Microsoft Corporation. Unisys® is a registered trademark of Unisys Corporation. All other company and product names used herein may be the trademarks or registered trademarks of their respective companies. Contents Contents . Table of Contents Preface About This Book. xvii Audience . xvii UniAccess System Product Suite . xvii Related Documentation. xviii Conventions Used in this Manual. xix Fonts and Format . xix Terminology . xx How This Manual Is Organized . xxii Part I: Basics 1 Introduction to UniAccessSystem for OS 2200 1-1 Client/Server Architecture . 1-2 Client/Server Overview . 1-2 Types of Servers . 1-4 Types of Clients . 1-5 UniAccess System for OS 2200 . 1-6 UniAccess ODBC Server for RDMS 2200. 1-6 UniAccess ODBC Server for DMS 2200 . 1-8 UniAccess Transaction Server . 1-8 UniAccess Transaction Client. 1-9 The OS 2200 Environment . 1-9 Components of the UniAccess System Environment . 1-11 Remote Client/Server Components . 1-14 Communication Link Protocols . 1-15 Host Components . 1-16 UniAccess System for OS 2200 Components . 1-17 Release 10R3: October 31, 2005 iv UniAccess for OS 2200 System Administration Guide 2 Application Development Overview 2-1 Types of Requests . 2-2 Language Requests . 2-2 Remote Procedure Calls (RPCs). 2-2 Comparing Language Requests and RPCs . 2-3 Direct and Indirect Requests. 2-4 Client Applications in the UniAccess System . 2-6 Remote Client Applications . 2-6 UniAccess Transaction Client Applications . 2-9 Server Applications in the UniAccess System . 2-11 Remote Server Applications . 2-11 UniAccess System Server Programs. 2-12 Part II: Installation and Initial Configuration Procedures 3 Planning Your UniAccess Installation 3-1 Before You Begin . 3-1 Hardware and Software Requirements . 3-4 Explanation of Values in Pre-Installation Checklist . 3-6 4 Installing the UniAccess System 4-1 Installation Checklist . 4-1 Explanation of Installation Requirements. 4-4 5 Planning Your UniAccess Configuration 5-1 Configuration Overview . 5-1 Configuration Requirements. 5-3 Explanation of Configuration Requirements . 5-4 6 Managing the UniAccess System 6-1 Starting UniAccess Operations. 6-2 Overview of UniAccess System Management . 6-3 UniAccess Configuration Management . 6-3 UniAccess Fixed-gate Management . 6-5 Steps in UniAccess System Management. 6-8 Initial UniAccess System Execution. 6-8 Subsequent UniAccess System Executions . 6-10 7 Preparing for ODBC and Open Client Users 7-1 Client Preparation Checklist . 7-1 Explanation of Actions in the Client Preparation Checklist . 7-2 Value Table for Client Users. 7-6 Release 10R3: October 31, 2005 Contents v Part III: Advanced UniAccess Procedures 8 Optimizing Performance 8-1 UniAccess Communication Server Optimization. 8-2 UniAccess Message Manager Optimization. 8-2 Database Performance . 8-4 Transaction Configuration and Design . 8-6 Registering Transactions. 8-6 UARS Performance . 8-7 UAHS Performance . 8-9 Server-Library Program Design . 8-12 Host Performance . 8-16 Processor Utilization. 8-16 I/O Utilization . 8-16 Memory Utilization — ClearPath IX, 2200/500, and 2200/900. 8-16 9 Providing Security 9-1 Overview of UniAccess System Security. 9-2 Component Security Responsibilities. 9-3 Using UniAccess System Security Facilities . 9-4 TIP Session Control . 9-5 UniAccess Security API . 9-6 Userid and Password. 9-6 UAUSER Definitions . 9-6 Co-existence With Unisys Security . 9-8 Security Options . 9-8 TIP Session Control . 9-8 UACS Background Security Requirement . 9-9 Console Privileges for UACS Commands . 9-10 10 Returning Server Program Messages to Client Applications 10-1 Server Program Message Overview . 10-1 Message Handling in the UniAccess System . 10-2 Messages Generated by UniAccess System Components . 10-3 Messages Generated by User-written Transactions . 10-5 Map and Message Definitions . 10-5 Map Definitions . 10-5 Message Definitions . 10-7 Server-Library Message Definitions..
Load more

Recommended publications
  • Unisys Clearpath MCP & OS 2200 Mainframes to the Google Cloud Platform
    WHITE PAPER Unisys ClearPath MCP & OS 2200 Mainframes to the Google Cloud Platform Reference Architecture Guide Astadia Mainframe-to-Cloud Modernization Series Abstract In businesses today, across all market segments, cloud computing has become the focus of current and future In this document, we will explore: technology needs for the enterprise. The cloud offers compelling • Why modernize a Unisys mainframe economics, the latest technologies and platforms, and the agility • The challenges associated with Unisys to adapt your information systems quickly and efficiently. mainframe modernization However, many large organizations are burdened by much older, previous generation platforms, typically in the form of a Unisys • An overview of the Unisys mainframe mainframe computing environment. • The Unisys mainframe to Google Cloud Platform Reference Architecture Although old and very expensive to maintain, the Unisys • An overview of Google Cloud Platform services mainframe platform continues to run many of the most important information systems of an organization. The purpose • A look at the Astadia Success Methodology of this reference architecture is to assist business and IT This document is part of the Astadia Mainframe professionals as they prepare plans and project teams to start to Cloud Modernization Series that leverages the process of moving Unisys mainframe-based application Astadia’s 25+ years of mainframe platform portfolios to the Google Cloud Platform (GCP). We will also modernization expertise. share various techniques and methodologies that may be used in forming a complete and effective Legacy Modernization plan. © 2020 Astadia. Inc. - All rights reserved. 75 State Street, Suite 100 Boston, MA 02109 All other copyrights and trademarks the property of their respective owners.
    [Show full text]
  • The Future of Business Using Enterprise Server
    Market Review Market Review Paper by Bloor Author David Norfolk Publish date June 2021 The Future of Business …using Enterprise Server 3.0 Services A company has to stay“ in business while modernising its systems and any modernisation must have a clearly documented business case and properly managed risk. What this means is that migrating a working system to a new platform may not be a good use of resources, especially as alternative modernisation options (such as the provision of cloud APIs or Application Programming Interfaces) are available. ” Executive summary he Future of Business will Well, the nub of the business issue we be largely built on the past, spotlight here is that migration to Cloud T for existing companies. is often recommended simplistically as Modernisation of what you have already, a platform for future business, almost as presumably “fit for current purpose” (or you a fashion option, with implied promises wouldn’t be in business) avoids waste and of ultimate agility, elastic capabilities mitigates certain classes of risk (although, without limits and low cost; but the if not done properly, it can add new risks). actuality is often different – and never Modernisation, of course, implies fit for quite being able to complete a migration evolution and change – once modernised, off Enterprise Server 3.0, because the you will be making further changes to business realities won’t let you, is accommodate new business. probably the most expensive scenario Modernisation of what For big enterprises, the world still runs of all. Cloud provides a wide choice of you have already,“ on very large, very resilient, servers – often platforms, some with innovative and presumably “fit for current referred to as “mainframes”, although attractive characteristics, but three truths Bloor prefers the term Enterprise Server remain important: purpose” (or you wouldn’t be in business) avoids 3.0.
    [Show full text]
  • BCIS 1305 Business Computer Applications
    BCIS 1305 Business Computer Applications BCIS 1305 Business Computer Applications San Jacinto College This course was developed from generally available open educational resources (OER) in use at multiple institutions, drawing mostly from a primary work curated by the Extended Learning Institute (ELI) at Northern Virginia Community College (NOVA), but also including additional open works from various sources as noted in attributions on each page of materials. Cover Image: “Keyboard” by John Ward from https://flic.kr/p/tFuRZ licensed under a Creative Commons Attribution License. BCIS 1305 Business Computer Applications by Extended Learning Institute (ELI) at NOVA is licensed under a Creative Commons Attribution 4.0 International License, except where otherwise noted. CONTENTS Module 1: Introduction to Computers ..........................................................................................1 • Reading: File systems ....................................................................................................................................... 1 • Reading: Basic Computer Skills ........................................................................................................................ 1 • Reading: Computer Concepts ........................................................................................................................... 1 • Tutorials: Computer Basics................................................................................................................................ 1 Module 2: Computer
    [Show full text]
  • Sperry Rand Third-Generation Computers
    UNISYS: HISTORY: • 1873 E. Remington & Sons introduces first commercially viable typewriter. • 1886 American Arithmometer Co. founded to manufacture and sell first commercially viable adding and listing machine, invented by William Seward Burroughs. • 1905 American Arithmometer renamed Burroughs Adding Machine Co. • 1909 Remington Typewriter Co. introduces first "noiseless" typewriter. • 1910 Sperry Gyroscope Co. founded to manufacture and sell navigational equipment. • 1911 Burroughs introduces first adding-subtracting machine. • 1923 Burroughs introduces direct multiplication billing machine. • 1925 Burroughs introduces first portable adding machine, weighing 20 pounds. Remington Typewriter introduces America's first electric typewriter. • 1927 Remington Typewriter and Rand Kardex merge to form Remington Rand. • 1928 Burroughs ships its one millionth adding machine. • 1930 Working closely with Lt. James Doolittle, Sperry Gyroscope engineers developed the artificial horizon and the aircraft directional gyro – which quickly found their way aboard airmail planes and the aircraft of the fledgling commercial airlines. TWA was the first commercial buyer of these two products. • 1933 Sperry Corp. formed. • 1946 ENIAC, the world's first large-scale, general-purpose digital computer, developed at the University of Pennsylvania by J. Presper Eckert and John Mauchly. • 1949 Remington Rand produces 409, the worlds first business computer. The 409 was later sold as the Univac 60 and 120 and was the first computer used by the Internal Revenue Service and the first computer installed in Japan. • 1950 Remington Rand acquires Eckert-Mauchly Computer Corp. 1951 Remington Rand delivers UNIVAC computer to the U.S. Census Bureau. • 1952 UNIVAC makes history by predicting the election of Dwight D. Eisenhower as U.S. president before polls close.
    [Show full text]
  • Clearpath Forward® As Open Systems
    ClearPath Forward® as Open Systems By: Peter Bye White Paper The IT industry’s understanding of what it means to be an open system has evolved over the years. The original concept focused on certain operating systems and hardware: for example, there should be more than one source of hardware. Today, openness is concerned with the interfaces a system supports. This understanding suggests that openness is not a binary attribute; systems are not simply open or closed but are somewhere on a spectrum of openness. This paper discusses the characteristics of open systems and establishes a framework for analysing the openness of any system. It then considers ClearPath Forward® systems using the framework. The results show that ClearPath Forward systems are towards the open end of the openness spectrum. They support the major interfaces, especially for co-operating with other systems in distributed architectures, for example within a service architecture implementation. The paper was last revised in 2014 with the title ‘ClearPath® as an Open System’. The 2018 revision reflects product name changes and the fact that all ClearPath Forward systems now use Intel hardware, with firmware providing the system architecture rather than hardware. ClearPath Forward Libra (ClearPath MCP-based) and Dorado (ClearPath OS 2200-based) systems use Unisys supplied Intel-based hardware. The ClearPath Software Series may run in hardware of the client’s choice. 2 Table of Contents Summary 4 Introduction 5 ClearPath Forward Systems: Architectural Positioning 5 What is an Open System? 6 Perspectives on Openness – An Analytical Framework 8 Evaluating ClearPath Forward Open Attributes 9 Perspective 1: Interfaces 9 Perspective 2: Application Development 17 Perspective 3: Systems Management and Operations 18 ClearPath System Mission-Critical Attributes 19 Sources of Information 20 Appendix A: ClearPath Forward Architecture 21 Appendix B: Glossary 23 About the Author 25 3 Summary Definitions of open systems have changed over the years.
    [Show full text]
  • Implementing and Developing Cloud Computing Applications [2011]
    Implementing and Developing Cloud Computing Applications K11513_C000.indd 1 10/18/10 2:47 PM Implementing and Developing Cloud Computing Applications DAVID E.Y. SARNA K11513_C000.indd 3 10/18/10 2:47 PM Auerbach Publications Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 © 2011 by Taylor and Francis Group, LLC Auerbach Publications is an imprint of Taylor & Francis Group, an Informa business No claim to original U.S. Government works Printed in the United States of America on acid-free paper 10 9 8 7 6 5 4 3 2 1 International Standard Book Number: 978-1-4398-3082-6 (Hardback) This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials or the consequences of their use. The authors and publishers have attempted to trace the copyright holders of all material reproduced in this publication and apologize to copyright holders if permission to publish in this form has not been obtained. If any copyright material has not been acknowledged please write and let us know so we may rectify in any future reprint. Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced, transmitted, or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying, micro- filming, and recording, or in any information storage or retrieval system, without written permission from the publishers.
    [Show full text]
  • Chapter 9: Sperry Rand Third-Generation Computers
    UNISYS: HISTORY: 1873 E. Remington & Sons introduces first commercially viable typewriter. 1886 American Arithmometer Co. founded to manufacture and sell first commercially viable adding and listing machine, invented by William Seward Burroughs. 1905 American Arithmometer renamed Burroughs Adding Machine Co. 1909 Remington Typewriter Co. introduces first "noiseless" typewriter. 1910 Sperry Gyroscope Co. founded to manufacture and sell navigational equipment. 1911 Burroughs introduces first adding-subtracting machine. 1923 Burroughs introduces direct multiplication billing machine. 1925 Burroughs introduces first portable adding machine, weighing 20 pounds. Remington Typewriter introduces America's first electric typewriter. 1927 Remington Typewriter and Rand Kardex merge to form Remington Rand. 1928 Burroughs ships its one millionth adding machine. 1930 Working closely with Lt. James Doolittle, Sperry Gyroscope engineers developed the artificial horizon and the aircraft directional gyro – which quickly found their way aboard airmail planes and the aircraft of the fledgling commercial airlines. TWA was the first commercial buyer of these two products. 1933 Sperry Corp. formed. 1946 ENIAC, the world's first large-scale, general-purpose digital computer, developed at the University of Pennsylvania by J. Presper Eckert and John Mauchly. 1949 Remington Rand produces 409, the worlds first business computer. The 409 was later sold as the Univac 60 and 120 and was the first computer used by the Internal Revenue Service and the first computer installed in Japan. 1950 Remington Rand acquires Eckert-Mauchly Computer Corp. 1951 Remington Rand delivers UNIVAC computer to the U.S. Census Bureau. 1952 UNIVAC makes history by predicting the election of Dwight D. Eisenhower as U.S. president before polls close.
    [Show full text]
  • Openti Component Standards
    D HS Business and Technical Standards Document Revised 2/25/16 Pennsylvania Department of Human Services Bureau of Information Systems DHS OpenTI Component Standards Version 2.1 DHS Open TI Component Standards.doc Page 1 of 129 D HS Business and Technical Standards Document Revised 2/25/16 December 27th, 2004 DHS Open TI Component Standards.doc Page 2 of 129 D HS Business and Technical Standards Document Revised 2/25/16 Table of Contents OLTP ........................................................................................................................................................ 14 OpenTI ..................................................................................................................................................... 14 Views ....................................................................................................................................................... 16 Administration .................................................................................................................................... 16 Symbolic Format ................................................................................................................................. 16 Symbolic Creation ............................................................................................................................... 18 Access ................................................................................................................................................. 18 Compilation........................................................................................................................................
    [Show full text]
  • Clearpath As an Open System
    ClearPath as an Open System By Peter Bye White Paper 1 The IT industry’s understanding of what it means to be an open system has evolved from an original narrow concept that focused on certain operating systems and hardware to one that focuses instead on the interfaces a system supports. This understanding suggests that ‘openness’ is not a binary attribute; systems are not simply open or closed but are somewhere on a spectrum of openness. This paper discusses the characteristics of open systems, establishes a framework for analysing the openness of any system and then considers ClearPath systems using the framework. The results show that ClearPath systems are towards the open end of the openness spectrum. They support the major interfaces, especially for co-operating with other systems in distributed architectures, for example within a service-oriented architecture (SOA) implementation. 2 Contents Executive summary ....................................................................................................................................... 1 Introduction.................................................................................................................................................... 3 What is an open system? .............................................................................................................................. 3 Perspectives on openness – an analytical framework .................................................................................. 6 Evaluating ClearPath system open attributes
    [Show full text]
  • Cobol 1 Cobol
    COBOL 1 COBOL COBOL Paradigm procedural, object-oriented Appeared in 1959 Designed by Grace Hopper, William Selden, Gertrude Tierney, Howard Bromberg, Howard Discount, Vernon Reeves, Jean E. Sammet Stable release COBOL 2002 (2002) Typing discipline strong, static Major OpenCOBOL, Micro Focus International implementations Dialects HP3000 COBOL/II, COBOL/2, IBM OS/VS COBOL, IBM COBOL/II, IBM COBOL SAA, IBM Enterprise COBOL, IBM COBOL/400, IBM ILE COBOL, Unix COBOL X/Open, Micro Focus COBOL, Microsoft COBOL, Ryan McFarland RM/COBOL, Ryan McFarland RM/COBOL-85, DOSVS COBOL, UNIVAC COBOL, Realia COBOL, Fujitsu COBOL, ICL COBOL, ACUCOBOL-GT, COBOL-IT, DEC COBOL-10, DEC VAX COBOL, Wang VS COBOL, Visual COBOL, Tandem (NonStop) COBOL85, Tandem (NonStop) SCOBOL (a COBOL74 variant for creating screens on text-based terminals) Influenced by FLOW-MATIC, COMTRAN, FACT Influenced PL/I, CobolScript, ABAP COBOL at Wikibooks COBOL (pronounced /ˈkoʊbɒl/) is one of the oldest programming languages. Its name is an acronym for COmmon Business-Oriented Language, defining its primary domain in business, finance, and administrative systems for companies and governments. The COBOL 2002 standard includes support for object-oriented programming and other modern language features.[1] History and specification The COBOL specification was created by a committee of researchers from private industry, universities, and government during the second half of 1959. The specifications were to a great extent inspired by the FLOW-MATIC language invented by Grace Hopper - commonly referred to as "the mother of the COBOL language." The IBM COMTRAN language invented by Bob Bemer was also drawn upon, but the FACT language specification from Honeywell was not distributed to committee members until late in the process and had relatively little impact.
    [Show full text]
  • Features of OS2200 System
    Namitha D Jadhav, Vanishree K ; International Journal of Advance Research, Ideas and Innovations in Technology ISSN: 2454-132X Impact factor: 6.078 (Volume 6, Issue 3) Available online at: www.ijariit.com Features of OS2200 System Namitha D Jadhav Vanishree K [email protected] [email protected] RV College of Engineering, Bengaluru, Karnataka RV College of Engineering, Bengaluru, Karnataka ABSTRACT Clear0Path OS 2200 is the0complete, premier operating environment for Clear Path Forward0Dorado systems. The OS 2200 operating0system sits at the environment’s core, 0delivering0the unmatched0security, robust scalability, availability, data integrity, and ultra-high-volume0transaction0processing0capabilities0core0business applications and digital business processes demand. These applications are run by transaction managers and application servers designed especially for and tightly0integrated with the OS 22000environment, enabling them to manage exceedingly high transaction volumes with ease. Keywords: Clearpath, OS2200, Demand Mode, Batch Processing I. INTRODUCTION Clear Path0OS 2200 is the complete, premier operating environment for Clear Path Forward Dorado0systems. The OS 2200 operating0system sits at the environment’s core, delivering the0unmatched security, robust0scalaBility, availaBility, data integrity, and ultra-high-volume transaction processing capabilities0core business applications0and digital business processes demand. These0applications are run By transaction0managers and application servers designed0especially
    [Show full text]
  • Nesi Manual Template
    H301e Bulk File Transfer (BFX™) Utility for Unisys OS2200 Systems Release 3.4.4 Software Reference Manual MAN-REF-H301e-3.4.4 Revision Record Revision* Description 3.4.3 (2/2017) Initial Extended Mode product release 3.4.3-01 Minor clarification on dslab 3.4.3-02 Minor clarification of keyval (unsupported – Error) 3.4.4 Maintenance update aligned with Release 3.4.4 © 2018 by Network Executive Software Inc. Reproduction is prohibited without prior permission of Network Executive Software Inc. Printed in U.S.A. All rights reserved. You may submit written comments to: Network Executive Software, Inc. Publications Department 6450 Wedgwood Road N, Suite 103 Maple Grove, MN 55311 USA Comments may also be submitted over the Internet by addressing e-mail to: [email protected] or, by visiting our web site at: http://www.netex.com Always include the complete title of the document with your comments. Page ii Preface MAN-REF-H301e-3.4.4 Preface This manual describes the user interface to the Network Executive Software (“NESi”) H301e Extended Mode Bulk File Transfer (BFX™) utility for Unisys OS2200 systems. BFX is used in conjunction with NESi’s NETwork EXecutive (NETEX®) family of software products for use on IP networks. The Extended Mode products (H300e/H301e) replace the basic mode products (H300IPC/H301). The first section of this manual, “Introduction” on page 1 is an introduction to BFX. It includes a description of BFX, network configurations that can support BFX, and the three programs which compose BFX and how they interact. “ECL and Control Parameters for BFX” on page 21 presents user control statements and parameters.
    [Show full text]