Mef\~O \!:J R::.; CORPOR[\TION from E)L.T

Total Page:16

File Type:pdf, Size:1020Kb

Mef\~O \!:J R::.; CORPOR[\TION from E)L.T r;:I. ~ CONTR.OL DATA r;:l c::\ CONTR.OL DATA \::J r:::J CORPOR[\TION MEf\~O \!:J r::.; CORPOR[\TION FROM e)l.T. LOC .... TION: TO. ------'LOCATIOH. IFROM Baseline Change LDCA liON: ~~-~~~~;~pma~----~L~~~~~~ [. H. Michehl ____--'--'2=..!;!bb9 ARH293 Distribut=-i=-on~~ ______~_L- ___L___ ~C~ntrol Board ~~HOP~ __ SUS;Eel, OATE; ~-- OATE: _fyO[~~O_~~.~/R~,~R~e~v~.~~(~ ____________________________~b 112/7B EffJt9; of AO/R Revisl.tms on Exis.tin9..JlRL'~s"--______________-lb1bntL __ Attached is the NPP-approved (VSER 180 Architectural Objectives, Revision C. This document should be reviewed against existing DR's per the accs direction memo of b/b/7B. When Revision ( of the (YBER lBO AO/R is approved by NPP, the following The three change summaries attached outline changes in content between procedure applies. Revision B {Rev. 9} and Revision C {Rev. 12}. Please submit your updated statements of comoliance to the NPP Program Office as soon as All projects operating against an existing CVeER 180 DR will carefully possible. review the revised AO/R and submit a new statement of compliance to the CVSER 180 Program Office within 10 working days of AO/R distribution. -12E. H. Mi~~h-e~h'l------~ DIt' ector AD&C /?/! . paj ~!1 'i,. 1'4 . 1<'' i!," ///~!.. ~-~7 H.Ny-Fr'pzie 6'178 L. V ~~11 J. tfclla e h <i{t 7/1 Attachments Vice Pr~sident Via President Vice p,f.esident 'Comput~r Programming New Product Program Computer Development Division ,,. I \ "~II'''n IN II.'.'. EHM L/102178 CHANGES - REV. 11 TO REV. ka Section 7.11.11.'1 Two sentence~ were removed as irrelevant: Section ].. Restricting objectives to R1 Clarifies S1/THETA project.objectives without compromising 2. Comparative CPU times. product line objectives.. 7.11.'1.].0.1 Paragraph removed - not directly related to objectives. No. 1~ - a reference for security design objectives. 7.5·1 BASIC speeds and benchmarks redefined. Clarifi~s between sensing and recording in the power system. &.2·3 Will support CYBERAMA. More precision on which disks are brought up by single button power-on. 8.'1 Clarification. hQuietJzingh dropped as a generally required option. 8. '1.7 MTTR average includes necessary trioS for parts. Feature matrix moved to section 11.1.5. Clarify assumption regarding degraded interruption~ Auto Power Recovery is to re~ui~e a 2~S second ride- through MG Set. .. 8.b.1I Clarifies critical PSR status of initial release. Further definition of short and long warnings. '1.], DoD Security Compliance is no longer excluded. Clarification, modification for performance is encouraged·. S} - Sam~ fUnction, iess implementation det~il. 10.'1.]. lD} - Clearer terminology. ].0. '1.2 Clarification of intent, remote maintenance interfaces 1'1} - Eliminates redundant information. are standard, the subsystem remains to be def5ned. Clarification of intent relative to compilers and compiler users. 2 port MUX is part of the basic mainframe in both C170 and (180 state· o.S. independence made a general product set requirement. MG Set Options reduced to eliminate proliferation of In the matrix - added ~PASCAL {~irth PASCAL}. development projects. 17} - Corrects compatibility objective of ALGOl LO Maintenance cost objectives stated in dollars and %. relative to ALGOL b8 Minimum THETA configuration is 11MB. Maximum defined Classification "medium, large and very ~arge" revised. real memory now is 32MB. O.S. independence requirement moved to Section 3.Q.1. Clarifies future terminals intent and relation to .(YBER 180 will comply with basis DoD security requirements. value added networks. Maximum terminal capacity {logical} has been.expanded. 12.".2-3 System Power cost changes. The Basic O.S. Is also prohibited from source code 12.5 Previous forecasts have been dropped. release for system software security considerations. 12.7.2 Schedul clarification~ Dual State link is a ].70/].80 feature only. MMF shared peripherals restricted to RMS and Front-ends~ 12.7.2.2.5 Some items delayed until b/7'1. User validation phased over 2 releases. Accounting phased over 2 releases~ Tasking added to Rl. Job· Dependency t~ R2. lBO state Basic tape I/O and volumes to R1. Online maintenance of tape in Rl via (170. Index Sequential to Rl~ All of DBnS ph,ased. ~ Change Summary - CYBtR 180· AO/R Second »rart or Rev. C {Rev. 11} Qu, /0 -h., (4w' I Section Section Minor wording changes to clarify the role of automatic power recovery. Requires that automatic power recovery Major Objectives - The specific areas of emphasis for be implemented in a safe manner. SJ, and THETA have been noted along with potential for impact on priority trade-off? The time constraints of short and long warnings are clarified. ]'.3.]' The release dates for 51 have been clarified. CEM does not mon1tor E5M or E~5. ],.3.3 The base for perforMance measurement remains CVBER 73. Added bullet regarding one button power for equipment other than the basic elements •. 2.0 Reference 10 has been updated and reference lS added. ~larifies the relationship of eq~ipment monitoring and power availability to peripherals in a multi-mainframe 3.]'.]'.], Per request of Engineering the terminology for inputl configuration. output unit.has been revl~ed. A reference to PP usage has been dropped {it was redundant The probable support of a two·IOU configuration has been to the earlier description}. noted and a reference to varying memory capacities added. The entire section'on Transaction Processing has been 3.},.J,.11 Minor wording changes to reduce the confusion regarding rp.placed. common memory vs. shared memory {the latter is low cost communication medium for dual mainframe configurations Sentence calling program structuring a subset of CYBER 170 only}. All other multi-mainframe configurations are Segment loader has'been dropped, was misleading. The independent of requirements for a common memory and the discussion of relative importance of loading performance term has been dropped. vs. generalized library format has been clarified. Batch processing has been dropped In p~iority and further The requirements for interchangeabre fi Ie formats, ('tc. clarification on the relationship between transaction have been clarified to apply to compilers and system processing and ti me-shar.ing has been made· util.ities {removing the requirement from data manag'ement subsystems}. c} Clarifies the 51 channel restrictions functionally remains the same, the implication of multiple f} defines the 2 port console multiplexor and reserves separate files has been removed. ], port for remote hardware and software maintenance. further modification/clarification to the accounting section, Clarifies the PP's·restricted accessing to central , memory as a software restriction. Clarifies PP software's A minimum configuration for pure 170 state has been added relationship to controlware. to support performance objectiVes in section 7. Adds requirement for controllers to interface to the 3. 11. L The applicability of these general product set technical configuration environment monitor. requirements to interpretive compilers is clarified. Severa' minor typographical corrections are made within the paragrapl Defines the minimum functional' characteristics of the The very last bullet regarding CYBER 180 system interface basic operator control console, beyond which operating standard was redundant and removed. system or diagnostic software cannot use. Clarifies the role of the (VBER 170 (C545 console with regard to Requires that Class I-III compilers must all honor the these requirements {the role of the (C54S In (180 System Interface Standard. Minor changes support levels systems remains weekly defined.} in the descriptive matrix. Add transaction interface to the matrix. Temperature monitoring and power control need not be "internal" to a mainframe. Clarifies the use of the Clarifies fORTRAN's relationship to ANSI standard. dewpoint recorder. on 180 systems. Revises the power Restructures (OBOl section with no change of content. requirement for multi-mainframe configurations to greater Clarifies BASIC relationsh)p between interpretive and power supply availability for shared elements. Clarifies object code generation. Several minor editorial changes motor generator sets options. made to the other paragraphs with no change in substance. Section Editorial changes have been made to improve clarity without changing basic con-tent; "Random memory management" "Min~r degradation in perform~nce" means compile speed. dropped - only a confusion factor. Global cross'reference listings .pply to PASCAL, SyMPl. Requirement fora Direct access method has been added. and the assembler. {The Basic Operating System-will no longer support a built-in Actual Key access method.} 1..0 This section has tieen completely rewritten in response to many questions. It should be carefully reviewed, although The last bullet regarding design trade-offs was removed. it is still preliminary. - This information also appears in the design priority The relationship of the 6nvironments and Uorkload Spec matrix. to these performance objectives is dbscribed. The DBMS requirement description of concurrent access drops "improved performance for key batch jobs." Dual The BMCaD performance base has been corrected {the base logging and dual recording has been changed to a separate, line had been measured incorrectly on a CVeER 73}. medium priority, -item. Performance ratio for P3 PASCAL-X changed from 8.7 ~o A definition of data base sizes has been added. Several 8." and special cases dropped to conform to the objectives minor editorial changes are made to this section. in Rev. B. This section has been revised for greDter clarity. Data Dictionary System{s} allows a choice between one ' generali~ed or two specialized products. The block copy performance requirement applies to all systems not just THETA. APl 2 replaces APlUM. Requirement clarified to specify dual mainframe shared Some priority changes have been made for DDl. All memory not a generalized common memory. priority If's dropped. The paragraph has been flagged as preliminary. 7.11.2 Terminology for the IOU cleaned up.
Recommended publications
  • Government Open Systems Interconnection Profile Users' Guide, Version 2
    NIST Special Publication 500-192 [ Computer Systems Government Open Systems Technology Interconnection Profile Users' U.S. DEPARTMENT OF COMMERCE National Institute of Guide, Version 2 Standards and Technology Tim Boland Nisr NATL INST. OF STAND & TECH R.I.C, A111D3 71D7S1 NIST PUBLICATIONS --QC- 100 .U57 500-192 1991 C.2 NIST Special Publication 500-192 . 0)0 Government Open Systems Interconnection Profile Users' Guide, Version 2 Tim Boland Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Supersedes NIST Special Publication 500-163 October 1991 U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Reports on Computer Systems Technology The National Institute of Standards and Technology (NIST) has a unique responsibility for conriputer systems technology within the Federal government. NIST's Computer Systems Laboratory (CSL) devel- ops standards and guidelines, provides technical assistance, and conducts research for computers and related telecommunications systems to achieve more effective utilization of Federal information technol- ogy resources. CSL's responsibilities include development of technical, management, physical, and ad- ministrative standards and guidelines for the cost-effective security and privacy of sensitive unclassified information processed in Federal computers. CSL assists agencies in developing security plans and in improving computer security awareness training. This Special Publication 500 series reports CSL re- search and guidelines to Federal agencies as well as to organizations in industry, government, and academia. National Institute of Standards and Technology Special Publication 500-192 Natl. Inst. Stand. Technol. Spec. Publ. 500-192, 166 pages (Oct. 1991) CODEN: NSPUE2 U.S.
    [Show full text]
  • Evitalia NORMAS ISO En El Marco De La Complejidad
    No. 7 Revitalia NORMAS ISO en el marco de la complejidad ESTEQUIOMETRIA de las relaciones humanas FRACTALIDAD en los sistemas biológicos Dirección postal Calle 82 # 102 - 79 Bogotá - Colombia Revista Revitalia Publicación trimestral Contacto [email protected] Web http://revitalia.biogestion.com.co Volumen 2 / Número 7 / Noviembre-Enero de 2021 ISSN: 2711-4635 Editor líder: Juan Pablo Ramírez Galvis. Consultor en Biogestión, NBIC y Gerencia Ambiental/de la Calidad. Globuss Biogestión [email protected] ORCID: 0000-0002-1947-5589 Par evaluador: Jhon Eyber Pazos Alonso Experto en nanotecnología, biosensores y caracterización por AFM. Universidad Central / Clúster NBIC [email protected] ORCID: 0000-0002-5608-1597 Contenido en este número Editorial p. 3 Estequiometría de las relaciones humanas pp. 5-13 Catálogo de las normas ISO en el marco de la complejidad pp. 15-28 Fractalidad en los sistemas biológicos pp. 30-37 Licencia Creative Commons CC BY-NC-ND 4.0 2 Editorial: “En armonía con lo ancestral” Juan Pablo Ramírez Galvis. Consultor en Biogestión, NBIC y Gerencia Ambiental/de la Calidad. [email protected] ORCID: 0000-0002-1947-5589 La dicotomía entre ciencia y religión proviene de la edad media, en la cual, los aspectos espirituales no podían explicarse desde el método científico, y a su vez, la matematización mecánica del universo era el único argumento que convencía a los investigadores. Sin embargo, más atrás en la línea del tiempo, los egipcios, sumerios, chinos, etc., unificaban las teorías metafísicas con las ciencias básicas para dar cuenta de los fenómenos en todas las escalas desde lo micro hasta lo macro.
    [Show full text]
  • International Standard
    International Standard INTERNATIONAL ORGANIZATION FOR STANDARDIZATION’ME~YHAPO~HAR OPrAHM3ALMfl l-l0 CTAHC\APTH3ALM@ORGANISATION INTERNATIONALE DE NORMALISATION Extension of the Latin alphabet coded Character set for bibliographic information interchange Extension du jeu de caractkres latins Codes emplo yk pour l’khange d’information bibliographique Second edition - 1983-11-01iT eh STANDARD PREVIEW (standards.iteh.ai) ISO 5426:1983 https://standards.iteh.ai/catalog/standards/sist/0f2b9bea-a782-4ed0-9a42- eb77e52da752/iso-5426-1983 UDC 003.344 : 025.3 Ref. No. ISO 5426-1983 (E) Descriptors: documentation, data processing, information interchange, bibliographic records, Character Sets, Latin characters. Price based on 6 pages Foreword ISO (the International Organization for Standardization) is a worldwide federation of national Standards bodies (ISO member bedies). The work of developing Inter- national Standards is carried out through ISO technical committees. Every member body interested in a subject for which a technical committee has been authorized has the right to be represented on that committee. International organizations, govern- mental and non-governmental, in liaison with ISO, also take part in the work. Draft International Standards adopted by the technical committees are circulated to the member bodies for approval before their acceptance as International Standards by the ISO Council. iTeh STANDARD PREVIEW International Standard ISO 5426 was developed by Technical Committee ISO/TC 46, Documen ta tion . (standards.iteh.ai) This second edition was submitted directly to the ISO Council,ISO 5in42 6accordance:1983 with clause 6.11.2 of part 1 of the Directiveshttps:/ /stforan dtheard stechnical.iteh.ai/c atworkalog /stofa ndISO.ard s/lts iscancelst/0f2b9 bandea- a782-4ed0-9a42- replaces the first edition (i.e.
    [Show full text]
  • Control Characters in ASCII and Unicode
    Control characters in ASCII and Unicode Tens of odd control characters appear in ASCII charts. The same characters have found their way to Unicode as well. CR, LF, ESC, CAN... what are all these codes for? Should I care about them? This is an in-depth look into control characters in ASCII and its descendants, including Unicode, ANSI and ISO standards. When ASCII first appeared in the 1960s, control characters were an essential part of the new character set. Since then, many new character sets and standards have been published. Computing is not the same either. What happened to the control characters? Are they still used and if yes, for what? This article looks back at the history of character sets while keeping an eye on modern use. The information is based on a number of standards released by ANSI, ISO, ECMA and The Unicode Consortium, as well as industry practice. In many cases, the standards define one use for a character, but common practice is different. Some characters are used contrary to the standards. In addition, certain characters were originally defined in an ambiguous or loose way, which has resulted in confusion in their use. Contents Groups of control characters Control characters in standards o ASCII control characters o C1 control characters o ISO 8859 special characters NBSP and SHY o Control characters in Unicode Control characters in modern applications Character list o ASCII o C1 o ISO 8859 Categories Translations Character index Sources This article starts by looking at the history of control characters in standards. We then move to modern times.
    [Show full text]
  • Axeda Supervisor Product Summary
    Axeda Supervisor Product Summary An in-depth look at the product suite: £ Wizcon for Windows & Internet £ WizPLC £ WizScheduler for Internet For additional information, please contact Axeda: Axeda Systems www.axeda.com www.axedasupervisor.com TRADEMARKS No portion of this publication may be reproduced, photocopied, stored on backup systems or transmitted without the prior written consent of the publisher. Axeda, Axeda Systems, Axeda DRM, Axeda Device Relationship Management System, Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda Usage, Automatic eCommerce, Firewall-Friendly, Axeda Supervisor, Wizcon, WizPLC, WizScheduler, WizAAM, WizSQL and Access. Insight. In Real Time are trademarks of Axeda Systems Inc. Axeda Hotline Plus, Axeda eXpert, Axeda eXpert Plus, Axeda Collaborate et Axeda Trace service marks of Axeda Systems Inc. All other products and trademarks are property of their respective owners. IMPORTANT NOTE This document describes the main features of the products and tools in the Axeda Supervisor suite. All technical features of the products may be modified without prior notice by Axeda. Copyright ©1986-2004 Axeda Systems Inc. Axeda Supervisor - Product Summary - p. 1 Table of Contents AXEDA SUPERVISOR - THE COMPLETE INTERNET-BASED SOLUTION FOR CONTROL AND INFORMATION................................4 FULL INTEGRATION WITH THE AXEDA DRM (DEVICE RELATIONSHIP MANAGEMENT) OFFERING..... 4 NEW DEDICATED SERVICES BASED ON AXEDA DRM .................................................................
    [Show full text]
  • International Standard 6438
    International Standard 6438 INTERNATIONAL ORGANIZATION FOR SfANDARDIZATION*ME~YHAPO~HAR OPTAHH3AlWlR fl0 CTAH&APTH3ALW@ORGANISATION INTERNATIONALE DE NORMALISATION Documentation - African coded Character set for bibliographic information interchange Documen tation - Jeu de caractkes africains Codes pour lechange d’informations bibliographiques First edition - 1983-08-01iT eh STANDARD PREVIEW (standards.iteh.ai) ISO 6438:1983 https://standards.iteh.ai/catalog/standards/sist/4456244e-4009-4f0f-8544- b43cc10faba4/iso-6438-1983 UDC 003.035 : 003.339 Ref. No. ISO 64384983 (E) Descriptors : documentation, Character Sets, coded Character Sets, information interchange. Price based on 6 pages Foreword ISO (the International Organization for Standardization) is a worldwide federation of national Standards bodies (ISO member bedies). The work of developing International Standards is carried out through ISO technical committees. Every member body interested in a subject for which a technical committee has been authorized has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. Draft International Standards adopted by the technical committees are circulated to the member bodies for approval before their acceptance as International Standards by the ISO Council. International Standard ISO 6438 was developediTeh byS TTechnicalAN DCommitteeAR DISO/TC P R46,E VIEW Documentation, and was circulated to the member( sbodiesta nind Junear d1982.s .iteh.ai) lt has been approved by the member bodies of the following countries : ISO 6438:1983 https://standards.iteh.ai/catalog/standards/sist/4456244e-4009-4f0f-8544- Australia India South Africa, Rep. Austria Italy b43cc10Spainfaba 4/iso-6438-1983 Canada Japan Sweden Czechoslovakia Netherlands United Kingdom Egypt, Arab Rep.
    [Show full text]
  • Need for Telecommunication Standards for Interconnection with the U.S
    NTIA-REPORT-81-62 Need for Telecommunication Standards for Interconnection with the U.S. Postal Service EMSS D.V. Glen R.E. Thompson u.s. DEPARTMENT OF COMMERCE Malcalm Baldrige, Secretary Dale N. Hatfield, Acting Assistant Secretary for Communications and Information February 1981 Preface The study reported here is part of a program conducted by the National Telecommunications and Information Administra­ tion~ Institute for Telecommunication Sciences (NTIA/ITS) for the United States Postal Service (USPS) in support of that agency·s proposed Electronic Mail Service System (EMSS). The current contract agreement number'between the USPS and the NTIA/ITS is 104230-79-T-1243. Previous reports for the USPS by the NTIA/ITS have dealt with satellite frequency requirements, earth-space attenuation predictions~ accuracy-cost studies, and electronic message service concepts and candidates (in unpublished form). Technical and management supervision of this report was provided by Dr. P. M. McManamon and R. F. Linfield of the NTIA/ITS. The views, opinions, and/or findings contained in this report are those of the authors and should not be construed as an official United states Postal Service or National Telecommunications and Information Administration position, policy, or decision, unless designated by other official documentation. iii TABLE OF CONTENTS Page LIST OF FIGURES vi LIST OF TABLES vii LIST OF ABBREVIATIONS viii ABSTRACT 1. INTRODUCTION 1 1. 1 Background 1 1.2 Purpose and Scope 2 1.3 Organization of this Report 3 2. INTERFACES OF THE USPS EMSS 3 2.1 EMSS Stations 3 ') ') ..., L...L.. Interconnection of Terminals with Stations I 2.3 Public and User Terminals 10 2.4 Local Telecommunications Network 15 2.5 Message Media Input/Output 15 3.
    [Show full text]
  • DECT Messenger Installation and Commissioning — Book 2 Avaya Communication Server 1000
    DECT Messenger Installation and Commissioning — Book 2 Avaya Communication Server 1000 7.5 NN43120-301, 03.02 March 2012 © 2012 Avaya Inc. protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not All Rights Reserved. modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and Notice software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can While reasonable efforts have been made to ensure that the be a criminal, as well as a civil, offense under the applicable law. information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the Third-party components right to make changes and corrections to the information in this document without the obligation to notify any person or organization of Certain software programs or portions thereof included in the Product such changes. may contain software distributed under third party agreements (“Third Party Components”), which may contain terms that expand or limit Documentation disclaimer rights to use certain portions of the Product (“Third Party Terms”). Information regarding distributed Linux OS source code (for those Avaya shall not be responsible for any modifications, additions, or Products that have distributed the Linux OS source code), and deletions to the original published version of this documentation unless identifying the copyright holders of the Third Party Components and the such modifications, additions, or deletions were performed by Avaya.
    [Show full text]
  • Federal Information Processing Standards Publication: Code For
    ANSI X3.4-1977 X3.4-1977 This standard has been adopted for Federal Government use. Details concerning its use within the Federal Government are contained in Federal Information Processing Standards Publication 1-2, Code for Infor¬ mation Interchange, Its Representations, Subsets, and Extensions. For a complete list of the publications available in the Federal Information Pro¬ cessing Standards Series, write to the Standards Processing Coordinator (ADP), Institute for Computer Sciences and Technology, National Bureau of Standards, Gaithersburg, MD 20899. ANSI® X3.4-1977 Revision of X3.4-1968 American National Standard Code for Information Interchange Secretariat Computer and Business Equipment Manufacturers Association Approved June 9, 1977 American National Standards Institute, Inc American An American National Standard implies a consensus of those substantially concerned with its scope and provisions. An American National Standard is intended as a guide to aid the manu¬ National facturer, the consumer, and the general public. The existence of an American National Stan¬ dard does not in any respect preclude anyone, whether he has approved the standard or not, Standard from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standard. American National Standards are subject to periodic review and users are cautioned to obtain the latest editions. The American National Standards Institute does not develop standards and will in no circum¬ stances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time.
    [Show full text]
  • Preview - Click Here to Buy the Full Publication
    This is a preview - click here to buy the full publication INTERNATIONALSTANDARD. INTERNATIONAL ORGANKATION FOR STANDARDIZATION l MEXAYHAPOAHA.2 OPI-AHI/f3AWiX l-l0 CTAHAAPTI/I3AWW.ORGANISATION INTERNATIONALE DE NORMALISATION Information processing - Basic mode control procedures for data communication Systems Traitemen t de I’in forma tion - Proc@dures de commande pour transmission de donnhes en mode de base First edition - 1975-02-01 UDC 681.327.18.01 Ref. No. ISO 1745-1975 (E) Descriptors : data processing, data transmission, control procedures, control characters. Price based on 19 pages This is a preview - click here to buy the full publication FOREWORD ISO (the International Organization for Standardization) is a worldwide federation of national Standards institutes (ISO Member Bodies). The work of developing International Standards is carried out through ISO Technical Committees. Every Member Body interested in a subject for which a Technical Committee has been set up has the right to be represented on that Committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. Draft International Standards adopted by the Technical Committees are circulated to the Member Bodies for approval before their acceptance as International Standards by the ISO Council. International Standard ISO 1745 was drawn up by Technical Committee ISO/TC 97, Computers and information processing, and circulated to the Member Bodies in May 1973. lt has been approved by the Member Bodies of the following countries : Australia Japan Switzerland Brazil Netherlands Thailand Canada New Zealand Turkey Czechoslovakia Pol and United Kingdom Egypt, Arab Rep. of Romania U.S.A. France South Africa, Rep.
    [Show full text]
  • Merlin Partner User Guide
    Merlin Partner User Guide Merlin - Version 1.18 Enterprise Europe Network 2 Merlin User Guide - updated 28 April 2015 Table of contents 1. Introduction 9 About Merlin 9 About this guide 9 Accessing Merlin 10 Merlin Logout 10 Browser Optimisation 11 What if I need help? 11 Icon Legend 11 Navigating Merlin 12 Exporting your Content 13 The Dashboards 13 Using the Filters 15 Clear Filters 16 Working with Technology, Market and NACE Keywords 17 When should I use different levels of keywords? 17 How do I select keywords in Merlin? 18 Where can I find a current list of Technology, Market and NACE keywords? 18 Who to Contact 18 Feedback 19 2. Change History 21 New features 21 Changes that impact your work 21 Features under development 21 3. Managing Profiles 23 Profile Workflow Overview 23 Profile creation 24 Internal Review Process 24 External Review Process 24 Blocking Scores 25 Enterprise Europe Network Profile expiry date 25 My Profiles Dashboard 25 Create a new profile 27 Review a profile 29 Edit a Draft profile 32 My Expired Profiles Dashboard 32 Modifying profile deadlines 33 Delete a profile 34 Archive a profile 35 Change your external reviewer status 35 Update your external reviewer information 36 Resign as an external reviewer 37 Reassign Profiles 38 4. Disseminating Profiles 39 Profile Search - Intranet 39 Intranet Simple Search 39 Intranet Advanced Search 40 Profile Search - Internet 43 Export Profiles 43 Export a Single Profile 43 Export All Profiles From Search Results 45 Merlin POD Web Service 45 5. Managing Clients and Queries
    [Show full text]
  • VOLUME VIII - FASCICLE Vlll/I
    This electronic version (PDF) was scanned by the International Telecommunication Union (ITU) Library & Archives Service from an original paper document in the ITU Library & Archives collections. La présente version électronique (PDF) a été numérisée par le Service de la bibliothèque et des archives de l'Union internationale des télécommunications (UIT) à partir d'un document papier original des collections de ce service. Esta versión electrónica (PDF) ha sido escaneada por el Servicio de Biblioteca y Archivos de la Unión Internacional de Telecomunicaciones (UIT) a partir de un documento impreso original de las colecciones del Servicio de Biblioteca y Archivos de la UIT. (ITU) ﻟﻼﺗﺼﺎﻻﺕ ﺍﻟﺪﻭﻟﻲ ﺍﻻﺗﺤﺎﺩ ﻓﻲ ﻭﺍﻟﻤﺤﻔﻮﻇﺎﺕ ﺍﻟﻤﻜﺘﺒﺔ ﻗﺴﻢ ﺃﺟﺮﺍﻩ ﺍﻟﻀﻮﺋﻲ ﺑﺎﻟﻤﺴﺢ ﺗﺼﻮﻳﺮ ﻧﺘﺎﺝ (PDF) ﺍﻹﻟﻜﺘﺮﻭﻧﻴﺔ ﺍﻟﻨﺴﺨﺔ ﻫﺬﻩ .ﻭﺍﻟﻤﺤﻔﻮﻇﺎﺕ ﺍﻟﻤﻜﺘﺒﺔ ﻗﺴﻢ ﻓﻲ ﺍﻟﻤﺘﻮﻓﺮﺓ ﺍﻟﻮﺛﺎﺋﻖ ﺿﻤﻦ ﺃﺻﻠﻴﺔ ﻭﺭﻗﻴﺔ ﻭﺛﻴﻘﺔ ﻣﻦ ﻧﻘﻼ ً◌ 此电子版(PDF版本)由国际电信联盟(ITU)图书馆和档案室利用存于该处的纸质文件扫描提供。 Настоящий электронный вариант (PDF) был подготовлен в библиотечно-архивной службе Международного союза электросвязи путем сканирования исходного документа в бумажной форме из библиотечно-архивной службы МСЭ. © International Telecommunication Union INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE YELLOW BOOK VOLUME VIII - FASCICLE Vlll/I DATA COMMUNICATION OVER THE TELEPHONE NETWORK RECOMMENDATIONS OF THE V SERIES VIIth PLENARY ASSEMBLY GENEVA, 10-21 NOVEMBER 1980 Geneva 1981 INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE YELLOW BOOK VOLUME VIII - FASCICLE VIII.1 DATA COMMUNICATION OVER THE TELEPHONE NETWORK RECOMMENDATIONS OF THE V SERIES VIIth PLENARY ASSEMBLY GENEVA. 10-21 NOVEMBER 1980 Geneva 1981 ISBN 92-61-01151-9 © I.T.U. CONTENTS OF THE CCITT BOOK APPLICABLE AFTER THE SEVENTH PLENARY ASSEMBLY (1980) YELLOW BOOK Volume I Minutes and reports of the Plenary Assembly.
    [Show full text]