DOCSLIB.ORG

Compaq TCP/IP Services for Openvms Concepts and Planning

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Compaq TCP/IP Services for Openvms Concepts and Planning Compaq TCP/IP Services for OpenVMS Concepts and Planning Part Number: AA-Q06TF-TE April 2002 Software Version: Compaq TCP/IP Services for OpenVMS Version 5.3 Operating Systems: OpenVMS Alpha Version 7.2–2, 7.3 OpenVMS VAX Version 7.2, 7.3 This manual describes concepts and planning taskstoprepareyoutousetheCompaqTCP/IP Services for OpenVMS product. Compaq Computer Corporation Houston, Texas © 2002 Compaq Information Technologies Group, L.P. COMPAQ, the Compaq logo, Alpha, OpenVMS, Tru64, VAX, VMS, and the Compaq logo are trademarks of Compaq Information Technologies Group, L.P., in the U.S. and/or other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries Motif, OSF/1, and UNIX are trademarks of The Open Group in the U.S. and/or other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq 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. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. Contents Preface 1 Introducing Compaq TCP/IP Services for OpenVMS 1.1 Overview of TCP/IP Services ................................................ 1–2 1.1.1 Data LinkLayer .......................................................... 1–3 1.1.2 InternetLayer ............................................................ 1–3 1.1.3 Transport Layer .......................................................... 1–3 1.1.4 Application Layer ........................................................ 1–4 1.2 Application Support .......................................................... 1–5 1.2.1 PATHWORKS and DECnet-over-TCP/IP Support .................. 1–5 1.3 APIs ............................................................................. 1–5 1.3.1 BerkeleySockets Interface ............................................. 1–5 1.3.2 OpenVMS QIO System Service Interface ............................ 1–6 1.3.3 ONC RPC ProgrammingInterface .................................... 1–6 1.3.4 SNMP Programming Interface ......................................... 1–7 1.4 Understanding RFCs ......................................................... 1–7 2 Understanding OpenVMS and UNIX Implementations 2.1 Evaluating the Computing Environment ................................. 2–1 2.1.1 Understanding the Open Systems Concept .......................... 2–1 2.1.2 Understanding theMiddleware Concept ............................. 2–2 2.2 File Compatibility ............................................................ 2–2 2.2.1 Directory Hierarchies ................................................... 2–3 2.2.2 File Specifications ........................................................ 2–4 2.2.3 Absoluteand Relative File Specifications ............................ 2–5 2.2.4 File Specifications ........................................................ 2–6 2.2.5 Case Sensitivity .......................................................... 2–6 2.2.6 File Types ................................................................. 2–7 2.2.7 VersionNumbers ......................................................... 2–7 2.2.8 Linking Files .............................................................. 2–7 2.2.9 File Structures ............................................................ 2–8 2.2.10 File Ownership ........................................................... 2–8 2.2.11 File Protections ........................................................... 2–9 2.3 Portability ...................................................................... 2–10 2.4 Determining Which File System to Use ................................... 2–11 3 OpenVMS Server and Network Configurations 3.1 Understanding OpenVMS VAX and Alpha Systems .................... 3–1 3.1.1 User Environment ....................................................... 3–1 3.1.2 System Management Environment ................................... 3–2 3.1.3 Programming Environment ............................................ 3–2 3.2 OpenVMS Cluster Configuration ........................................... 3–3 3.2.1 FailoverCapability ...................................................... 3–3 3.2.2 ConnectionLoadBalancing ............................................ 3–4 3.3 Multihoming and Multiple Interfaces ..................................... 3–4 Contents iii 3.3.1 Multihomed Computers ................................................. 3–5 3.3.2 Primary Interface ........................................................ 3–5 3.3.3 Pseudointerfaces ......................................................... 3–6 3.4 Serial Line Connections ...................................................... 3–6 4 OpenVMS Operating System TCP/IP Features 4.1 TCP/IP Management Control Program .................................... 4–1 4.2 Defining Logical Names ..................................................... 4–2 4.3 OpenVMS System Dump Analysis (SDA) Tool ........................... 4–2 4.4 System Messages ............................................................. 4–3 4.4.1 OPCOM .................................................................... 4–3 4.4.2 Log Files ................................................................... 4–3 4.5 ODS-5and ODS-2File Structures ......................................... 4–4 4.5.1 Considerations for System Management ............................. 4–4 4.5.2 Considerations for Users ................................................ 4–4 4.5.3 Considerations for Applications ........................................ 4–4 4.6 Network Printers ............................................................. 4–5 4.6.1 LinePrinter Daemon (LPD) Service .................................. 4–5 4.6.2 TELNET Print Symbiont ............................................... 4–7 4.6.3 Serial LinePrinterConnections ....................................... 4–7 4.6.4 Sharing Network Printers Using PATHWORKS (Advanced Server) ..................................................................... 4–7 4.6.5 PC-NFS .................................................................... 4–9 5 Network Server Services 5.1 Network Time Protocol (NTP) .............................................. 5–1 5.1.1 Time Distributed Through a Hierarchy of Servers ................. 5–2 5.1.2 How the OpenVMS System Maintains the System Clock ......... 5–2 5.1.3 How NTP Adjusts System Time ....................................... 5–2 5.1.4 Configuring the Local Host ............................................. 5–3 5.1.5 Using the Distributed Time Synchronization Service (DTSS) .... 5–3 5.2 Routing ......................................................................... 5–3 5.2.1 Static Routing ............................................................ 5–4 5.2.2 DynamicRouting ......................................................... 5–4 5.3 Remote ClientManagement(BOOTP/DHCP) ............................ 5–6 5.3.1 How DHCP Operates .................................................... 5–6 5.3.2 How DHCP Allocates IP Addresses ................................... 5–7 5.3.3 Relationship Between DHCP and BOOTP ........................... 5–9 5.3.4 Client ID ................................................................... 5–9 5.4 File Transfer Services ........................................................ 5–9 5.4.1 FTP (File Transfer Protocol) ............................................ 5–10 5.4.2 Trivial FTP (TFTP) ...................................................... 5–10 5.4.3 R Commands .............................................................. 5–10 5.4.4 DifferencesBetweenFTP and RCP ................................... 5–11 5.5 Simple Network Management Protocol (SNMP) ......................... 5–12 5.5.1 Configuring SNMP ....................................................... 5–12 5.5.2 Ensuring Access to Mounted Data .................................... 5–13 6 Mail Services 6.1 Post Office Protocol (POP) ................................................... 6–1 6.1.1 POP Server Process ...................................................... 6–1 iv Contents 6.1.2 How to Access Mail Messages from the POP Server ................ 6–2 6.1.3 How the POP Server Handles Foreign Message Formats ......... 6–2 6.1.4 How the POPServer Authorizes Users ............................... 6–2 6.1.5 Understanding POPMessage Headers ............................... 6–3 6.2 Simple Mail Transfer Protocol (SMTP) .................................... 6–5 6.2.1 How SMTP Clients and ServersCommunicate ..................... 6–5 6.2.2 Understanding How SMTP Translates OpenVMS Mail Headers 6–6 6.2.3 Understanding SMTP Addresses ...................................... 6–6 6.3 IMAP ...........................................................................
Load more

Recommended publications
  • 14 * (Asterisk), 169 \ (Backslash) in Smb.Conf File, 85
    ,sambaIX.fm.28352 Page 385 Friday, November 19, 1999 3:40 PM Index <> (angled brackets), 14 archive files, 137 * (asterisk), 169 authentication, 19, 164–171 \ (backslash) in smb.conf file, 85 mechanisms for, 35 \\ (backslashes, two) in directories, 5 NT domain, 170 : (colon), 6 share-level option for, 192 \ (continuation character), 85 auto services option, 124 . (dot), 128, 134 automounter, support for, 35 # (hash mark), 85 awk script, 176 % (percent sign), 86 . (period), 128 B ? (question mark), 135 backup browsers ; (semicolon), 85 local master browser, 22 / (slash character), 129, 134–135 per local master browser, 23 / (slash) in shares, 116 maximum number per workgroup, 22 _ (underscore) 116 backup domain controllers (BDCs), 20 * wildcard, 177 backups, with smbtar program, 245–248 backwards compatibility elections and, 23 for filenames, 143 A Windows domains and, 20 access-control options (shares), 160–162 base directory, 40 accessing Samba server, 61 .BAT scripts, 192 accounts, 51–53 BDCs (backup domain controllers), 20 active connections, option for, 244 binary vs. source files, 32 addresses, networking option for, 106 bind interfaces only option, 106 addtosmbpass executable, 176 bindings, 71 admin users option, 161 Bindings tab, 60 AFS files, support for, 35 blocking locks option, 152 aliases b-node, 13 multiple, 29 boolean type, 90 for NetBIOS names, 107 bottlenecks, 320–328 alid users option, 161 reducing, 321–326 announce as option, 123 types of, 320 announce version option, 123 broadcast addresses, troubleshooting, 289 API
    [Show full text]
  • Design of the PATHWORKS for ULTRIX File Server by Anthony J
    Design of the PATHWORKS for ULTRIX File Server By Anthony J. Rizzolo, Elizabeth A. Brewer, and Martha A. Chandler 1 Abstract The PATHWORKS for ULTRIX product integrates personal computers with the ULTRIX operating system on a local area network. The software supports both the TCP/IP protocol and the DECnet transport stacks. The design and implementation of the PATHWORKS for ULTRIX file server is based on a client-server model. The server provides file, print, mail, and time services to client PCs on the network. Network file service management is accessed through a PC-style menu interface. The file server's performance was optimized to allow parallelism to occur when the client is generating data at the same time the server is writing the data to disk. 2 Introduction The PATHWORKS for ULTRIX file server connects industry-standard personal computers running Microsoft's server message block (SMB) protocol to Digital computers running the ULTRIX operating system. The server provides a network operating system for PC integration among users of the ULTRIX, DOS, and OS/2 operating systems. The PATHWORKS for ULTRIX server provides file, print, mail, and time services to client PCs on the network. The software is layered on VAX systems and on reduced instruction set computer (RISC) hardware. It supports both the transmission control protocol/internet protocol (TCP/IP) and the DECnet transport stacks. The base product also provides centralized server-based management accessed through a PC-style menu interface. In addition, the PATHWORKS for ULTRIX server implements a network basic I/O system (NetBIOS) naming service that allows clients on the network to obtain the DECnet node address of the server in the DECnet environment or the TCP/IP address of the server in the TCP/IP environment.
    [Show full text]
  • PATHWORKS for DOS Microsoft Windows Support Guide
    PATHWORKS for DOS ' Microsoft Windows Support Guide PATHWORKS for DOS Microsoft Windows Support Guide Order Number: AA-MF87D-TH August 1991 Revision/Update Information: This document supersedes Microsoft Windows Support Guide, order number AA-MF87C-TH. Software Version: PATHWORKS for DOS Version 4.1 Digital Equipment Corporation Maynard, Massachusetts First Published, October 1988 Revised, April 1989, July 1990, October 1990, January 1991, August 1991 The infonnation 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. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(l)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1988, 1989, 1990, 1991. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments fonn at the end of this document requests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-I, DDCMP, DDIF, DEC, DECconnect, DEClaser, DE Cmate , DECnet, DECnet-DOS, DECpc, DECrouter, DECSA, DE C server, DECstation, DECwindows, DECwrite, DELNI, DEMPR, DEPCA, DESTA, Digital, DNA, EtherWORKS, LA50, LA75 Companion, LAT, LN03, LN03 PLUS, LN03 ScriptPrinter, METROWAVE, MicroVAX, PATHWORKS, PrintServer, ReGIS, RMS-ll, RSX, RSX-ll, RT, RT-ll, RX33, ThinWire, TK, ULTRIX, VAX, VAX Notes, VAXcluster, VAXmate, VAXmail, VAXserver, VAXshare, VMS, VT, WPS, WPS.PLUS, and the DIGITAL logo.
    [Show full text]
  • Migrating to SAS 6.08 for Windows: the Merck CANDA Experience Frank S
    Migrating to SAS 6.08 for Windows: The Merck CANDA Experience Frank S. Palmieri, Merck Research Laboratories Rob Rosen, Merck Research Laboratories Wanda Bidlack, Merck Research Laboratories Introduction ineluding a graphical user interface, database querying, In every industry there are computer applications that are graphing. statistical "analysis, document review features, critical for success. In the pharmaceutical industry, one file management utilities, and on-line help. In addition to such "critical success application" is known as a the migration, one of our objectives was to combine our Computer Assisted New Drug Application (CANDA). This existing CANDA features with those represented in is a tool designed to aid federal regulatory agencies in another CANDA system. The best features o~ both reviewing the effects of a drug before it is released to the systems remained and were placed on a common open market. As with any key system, performance and computing platform. We joined a statistical based CANDA, ease of use are important design considerations. Merck developed with SAS 6.07 on a RISC-based UHrix system, has created several CANDAs in the past six years, the and a medical based PC system that used Microsoft tools most recent o~ which involved migrating our latest CANDA for the document handling. Our goal was to create a from an Ultrix platform to a PC running Microsoft (MS) system with three primary features: a user friendly front­ Windows. end, a document review facility that depicts a visual duplicate o~ hard copy documents, and capabilities for Our new application is a large system based on MS Word querying data, creating graphics, and running statistical and the SAS 6.08 for Windows (Base, SCL, SAS/AF, analyses in a timely manner.
    [Show full text]
  • Software Product Description
    Software Product Description PRODUCT NAME: PATHWORKS for VMS, Version 4.0 SPD 30.50.07 (Formerly VMS Services for pes) DESCRIPTION • PATHWORKS for DOS (TCP/IP) - Software required for a personal computer running the DOS Operat­ PATHWORKS for VMS is based on the Personal Com­ ing System to access services of a PATHWORKS puting Systems Architecture (PCSA), which is an ex­ for VMS or PATHWORKS for ULTRIX server via tension of Digital Equipment Corporation's systems and the TCP/IP network transport. (Described in SPD networking architecture that merges the VAX, RISC and 33.45.xx.) personal computer environments. The PATHWORKS product family, developed under the PC SA architecture, • DECnetlPCSA Client: VAXmate - Required software provides a framework for integrating personal comput­ for VAXmates to use the facilities provided by PATH­ ers into an organization's total information system so WORKS for VMS. (Described in SPD 55.10.xx.) that different types of users can share information and PATH WORKS for VMS software allows VAX, MicroVAX, network services across the entire organization. VAXstation and VAXserver computers to act as applica­ The PATHWORKS family of software products includes: tion, data and resource servers to groups of personal computers. By using these server systems, personal • PATHWORKS for VMS - Software that allows a VMS­ computers can share applications, data and resources. based VAX system to act as a file, print, mail and Information can be accessed from local and remote sys­ disk server to DOS and OS/2® personal computers. tems and that information can be applied in DOS or (Described in this document.) OS/2 applications.
    [Show full text]
  • Compaq PATHWORKS for Openvms Server Installation and Configuration Guide
    Compaq PATHWORKS for OpenVMS Server Installation and Configuration Guide Order Number: AA–R6G1C–TE October 2001 This guide explains how to install and configure the PATHWORKS for OpenVMS (Advanced Server) software, including the standalone License Server and external authentication software, and the Upgrade utility. Revision/Update Information: This guide supersedes the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide, Version 6.0B. Operating System: OpenVMS Alpha Version 6.2, 7.2-1, 7.2-2, 7.3 OpenVMS VAX Version 6.2, 7.2, 7.3 Software Version: PATHWORKS V6.1 for OpenVMS (Advanced Server) Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation COMPAQ, the Compaq logo, OpenVMS, Tru64, DECnet, VAX, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation. Intel is a trademark of Intel Corporation. UNIX is a trademark of The Open Group. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq 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. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products.
    [Show full text]
  • PATHWORKS Openvms Alphaserver 4X00 DIGITAL Hitest Notes
    PATHWORKS OpenVMS AlphaServer 4x00 DIGITAL HiTest Notes EK-HPWVA-HN. B01 March 1997 Revision/Update Information: This is a revised manual Version 1.1. Operating System and Version: OpenVMS V6.2-1H3 Digital Equipment Corporation Maynard, Massachusetts First printing December 1996 Revised March 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. © Digital Equipment Corporation 1996, 1997. All rights reserved. The following are trademarks of Digital Equipment Corporation: AlphaServer, DEClaser, DECnet, DIGITAL, EtherWorks, OpenVMS, PATHWORKS, StorageWorks, VAX, and the DIGITAL logo. The following are third-party trademarks: Microsoft, MS-DOS, Windows 95, and Windows NT are registered trademarks and Windows is a trademark of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Oracle is a registered trademark of Oracle Corporation. Table of Contents 1 Introduction....................................................................................1–1 DIGITAL HiTest Suite and Its Advantages...................................................................
    [Show full text]
  • VAX VMS at 20
    1977–1997... and beyond Nothing Stops It! Of all the winning attributes of the OpenVMS operating system, perhaps its key success factor is its evolutionary spirit. Some would say OpenVMS was revolutionary. But I would prefer to call it evolutionary because its transition has been peaceful and constructive. Over a 20-year period, OpenVMS has experienced evolution in five arenas. First, it evolved from a system running on some 20 printed circuit boards to a single chip. Second, it evolved from being proprietary to open. Third, it evolved from running on CISC-based VAX to RISC-based Alpha systems. Fourth, VMS evolved from being primarily a technical oper- ating system, to a commercial operat- ing system, to a high availability mission-critical commercial operating system. And fifth, VMS evolved from time-sharing to a workstation environment, to a client/server computing style environment. The hardware has experienced a similar evolution. Just as the 16-bit PDP systems laid the groundwork for the VAX platform, VAX laid the groundwork for Alpha—the industry’s leading 64-bit systems. While the platforms have grown and changed, the success continues. Today, OpenVMS is the most flexible and adaptable operating system on the planet. What start- ed out as the concept of ‘Starlet’ in 1975 is moving into ‘Galaxy’ for the 21st century. And like the universe, there is no end in sight. —Jesse Lipcon Vice President of UNIX and OpenVMS Systems Business Unit TABLE OF CONTENTS CHAPTER I Changing the Face of Computing 4 CHAPTER II Setting the Stage 6 CHAPTER
    [Show full text]
  • Redocumenting Historic CIFS
    ReDocumenReDocumentingting HisHistorictoric CCIFSIFS Christopher R. Hertel Storage Architect and CIFS Geek Founder and CTO www.ubiqx.com SNIA Storage Developer's Conference ● September, 2009 Copyright © 2009 Christopher R. Hertel IIntntrrooduduccttiionsons Who am I? Why am I here? Where are we going? SNIA Storage Developer's Conference ● September, 2009 1 IIntntrrooduduccttiionsons ...and what am I doing in this handbasket? SNIA Storage Developer's Conference ● September, 2009 2 IInnttrroodducuctitioonsns Who am I? This geek here. SNIA Storage Developer's Conference ● September, 2009 3 IInnttrroodducuctitioonsns Who am I? Samba Team (12± years) jCIFS Co-Founder Started with SMB/CIFS circa 1990 (DEC Pathworks) SNIA Storage Developer's Conference ● September, 2009 4 IInnttrroodducuctitioonsns Who am I? I have founded a new company We do SAN and NAS consulting We are a team of geeks SNIA Storage Developer's Conference ● September, 2009 V IInnttrroodducuctitioonsns Why am I Here? To tell you about the exciting new documentation... SNIA Storage Developer's Conference ● September, 2009 6 IInnttrroodducuctitioonsns Why am I Here? To tell you about the exciting new documentation... ...that covers CIFS circa 19961996. SNIA Storage Developer's Conference ● September, 2009 7 IInnttrroodducuctitioonsns Why am I Here? To tell you about the exciting new documentation... ...that covers CIFS circa 19961996. Yes, really. Hang on... I'll explain why this is a good thing. SNIA Storage Developer's Conference ● September, 2009 8 IInnttrroodducuctitioonsns Why am I Here? To tell you about the exciting new Microsoft documentation... ...that covers CIFS circa 19961996. Part of the MCPP/WSPP documentation set. On-line, downloadable, and available to the public. SNIA Storage Developer's Conference ● September, 2009 9 IInnttrroodducuctitioonsns Why am I Here? Microsoft asked a member of the Samba Team to document SMB/CIFS.
    [Show full text]
  • PATHWORKS: PC Integration Software
    PATHWORKS: PC Integration Software Digital Technical] ournal Digital Equipment Corporation Volume 4 Number 1 Winter 1992 Editorial Jane C. Blake, Editor Kathleen M. Stetson, Associate Editor Helen L. Patterson, Associate Editor Circulation Catherine M. Phillips, Administrator Sherry L. Gonzalez Production Mildred R. Rosenzweig, Production Editor Margaret L. Burdine, Typographer Peter R. Woodbury, Illustrator Advisory Board Samuel H. Fuller, Chairman Robert M. Glorioso Richard]. Hollingsworth John W McCredie Alan G. Nemeth Mahendra R. Patel F. Grant Saviers Victor A. Vyssotsky Gayn B. Winters The Digital Technicaljournal is published quarterly by Digital Equipment Corporation, 146 Main Street ML01-3/B68, Maynard, Massachusetts 01754-2571. Subscriptions to thejournal are $40.00 for four issues and must be prepaid in U.S. funds. University and college professors and Ph.D. students in the electrical engineering and computer science fields receive complimentary subscriptions upon request. Orders, inquiries, and address changes should be sent to the Digital Technicaljournal at the published-by address. Inquiries can also be sent electronically to DTJ®CRL.DEC.COM. Single copies and back issues are available for $16.00 each from Digital Press of Digital Equipment Corporation, 1 Burlington Woods Drive, Burlington, MA 01830-4597 Digital employees may send subscription orders on the ENET to ROVAX::JOURNAL or by interoffice mail to mailstop ML01-3/B68. Orders should include badge number, site location code, and address. All employees must advise of changes of address. Comments on the content of any paper are welcomed and may be sent to the editor at the published-by or network address. Copyright© 1992 Digital Equipment Corporation.
    [Show full text]
  • Installation Guide
    Installation Guide Adaptive Server Enterprise 12.5 Sun Solaris DOCUMENT ID: 35889-01-1250-02 LAST REVISED: February 2002 Copyright © 1989-2002 by Sybase, Inc. All rights reserved. This publication pertains to Sybase database management 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 it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845. Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. 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 the prior written permission of Sybase, Inc. Sybase, the Sybase logo, ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Adaptive Server IQ, Adaptive Warehouse, AnswerBase, Anywhere Studio, Application Manager, AppModeler,
    [Show full text]
  • System Support Addendum
    System Support Addendum PRODUCT NAME: PATHWORKS for DOS, Version 4.0 SSA 55.07.1 G-A (Formerly DECnet PCSA Client for DOS) HARDWARE REQUIREMENTS Maximum disk space required for the installation of all PATHWORKS for DOS software is 12MB of tree disk Systems, components, and peripherals specified be­ space (or 23,000 blocks on a VMS server). low are supported except as noted for specific software components: Other configurations, using selected components, may require less disk space. • An Intel® 8086-, 8088-, 80286-, 80386-, 80486- based personal computer from the Supported Base Systems Chart. OPnONALHARDWARE • A minimum of 640KB system memory. Expanded Memory Specification Version 4.0 Support • One network connection, either asynchronous or via PATHWORKS for DOS software supports the use of Ex­ an Ethernet controller. Refer to the Supported Base panded Memory Specification (EMS) applications that Systems Chart at the end of this document for a list are EMS, Version 4.0 compliant. The PATHWORKS for of supported Ethernet controllers in the various sup­ DOS networking software that can be loaded into EMS ported systems. More than one communications de­ requires 144KB of memory. vice may be installed in a system subject to system limitations. If use of another device is required, the Digital Printers system may need to be rebooted. A device cannot typically be shared with other communications prod­ PATHWORKS for DOS software supports the following ucts. Digital printers which can be connected to the PC: • In a PC local area network, at least one base system LA75 LA75P must have one diskette drive capable of reading 5.25 LA50 LA210 inch (360KB) diskettes or 3.50 inch (720KB) diskettes W250 W252 to load the distribution media.
    [Show full text]