DOCSLIB.ORG

14 * (Asterisk), 169 \ (Backslash) in Smb.Conf File, 85

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

,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 (application programming interface), 9 broadcast registration, 13 385 ,sambaIX.fm.28352 Page 386 Friday, November 19, 1999 3:40 PM 386 Index broadcast resolution, 13, 59 clients, testing with nmblookup broadcasting program, 279 troubleshooting with tcpdump .CMD scripts, 192 utility, 255 code pages, 234 (see also browsing; name resolution) multiple, 30 browse lists, 21, 116 coding system option, 235 options for, 124, 127 command string, SMB, 75 propagation, 24 commands for Samba, 366–377 restricting shares from, 115 commas in values, 84 browsing, 21–23, 114–127 comment option, 99 client-side, testing with net view, 280 comments in smb.conf (Samba configuration options for, 122–127 configuration) file, 85 elections, 23, 116–119 compatibility, Samba with Windows NT, 30 machines, list of, 21 compilers, 33 options for, list of, 122 compiling Samba, 38–41 preventing, 115 in version 2.0, 29 resources of a specific machine, 21–23 config file option, 91 server from client, 281 configuration files troubleshooting, 275–282 for individual clients, 253 with smbclient, 276–278 machine-specific, 87 bug avoidance options, 240–245 sample of, 379–383 list of, 240–241 smb.conf (Samba configuration) file (see smb.conf file) C configuration options browsing, 122–127 cache size, new option for (Samba version disk share, 97–100 2.0), 239 format of, 83 cache time (printers), option for, 220 list of, 329–356 capitalization, 84 server, 94–96 Carnegie Mellon University, 35 configuring disk shares, 96–100 carriage-returns for scripts, 193 configuring DNS (Windows NT), 68 case sensitivity configuring Samba, 34–38 hostnames and, 5 configuration file options for, 146 creating, 41–45 usernames and, 163 testing, 45 CD-ROM with this book (see also smb.conf (Samba Samba distribution, 28, 32 configuration) file) testing tools, 28 configure script certificate authority, 300–303 GNU, 34 change notification, new option for (Samba sample execution, 38 version 2.0), 239 options, 34–37 change notify timeout option, 239 performance tuning, 312–328 Change Windows Password dialog box, 52 benchmark for, 312, 314 changes at runtime, 85 other options for, 319–328 chat characters for passwords, 178 server, 93–96 CIFS (Common Internet File System), 3 with SSL, 295–311 (see also SMB/CIFS protocol) requirements for, 296 client code page option, 234 configuring TCP/IP networking client users (see users) protocol, 55, 66–71 client variables, 86 ,sambaIX.fm.28352 Page 387 Friday, November 19, 1999 3:40 PM Index 387 configuring Windows clients, 50–81 DFS, support for, 35 Windows 95/98 computers, 50–63 DHCP (Dynamic Host Configuration Windows NT 4.0 computers, 63–73 Protocol), 57, 67 basic configuration, 63–67 dialup connection, 53 configuring WINS address, 70 Digital Pathworks clients, option for, 244 connected systems, status of, 9 directories connections barring users from viewing active, option for, 244 contents, 130, 133 current, list of, 370 installation, 40 resources, connecting to, 81 permissions, options for, 140 scripts for, 198 for Samba startup file, 363 SMB, 77 target, 40 testing, 259–263 working, option for, 134 virtual, 78 directory mask option, 138, 141 copy option, 92 disabling/enabling features, 34 creation masks, 138 discussion archives for Samba, 293 option for, 140 disk quotas, support for, 37 cryptography, private key, 35 disk shares, 4–7, 49, 82–113 CVS (Concurrent Versions Systems), 378 advanced, 114–154 Cyclic Software, 378 configuring, 96–100 creating, 96 D maximum size of, option for, 242 path option, 98 daemons, 82, 359–362 disk sync, options for, 245 killing, 48 DMB (domain master browser), 119–122 messages generated by, reading, 8 option for, 126 stand-alone, 47 resource type, 24 starting, 46–48 DNS Configuration tab, 57 status report, 8 DNS (Domain Name System), 57 testing, 49 configuring, 68 with testparm, 266 as fallback for WINS address, 71 troubleshooting, 264–268 names Unix, 2 NetBIOS names and, 14 viewing, 8 resource types and, 15 (see also smbd daemon; nmbd daemon) option for, 228 data transfer protocol, 6 resources for further information, 293 datagram service, 10, 16–18 tab, 68 deadtime option, 241 dns proxy option, 228 debug files, 49 docs directory, 34 debug level option, 251, 314 test utilities, 254 debug timestamp option, 112 documentation for Samba, 291 default case option, 146 importance of reading, 34 default services, 115 domain controllers, 20, 169 option for, 124 for Windows 95/98, 18–20 defending hostnames, 12 domain group map option, 191 delays, troubleshooting, 287 domain logons, 28, 184 delete, 142 configuring Windows 95/98 for, 188 delete readonly option, 139, 142 configuring Windows NT 4.0 for, 189 delete veto files option, 135 scripts for, 192–200 dfree command option, 241 domain logons option, 190 ,sambaIX.fm.28352 Page 388 Friday, November 19, 1999 3:40 PM 388 Index domain master browser (see DMB) /etc/resolv.conf file, 57 domain master option, 126 /etc/services configuration file, adding Domain Name System (see DNS) SWAT tool to, 41, 48 domain user map option, 191 Ethernet adaptor cards, 53, 70 domain-level security, 164, 169–171 linking to TCP/IP networking domains, 18–20 protocol, 55 adding Samba server to Windows NT execute permissions, 47 domain, 171 /export/samba/test directory, 42 behavior vs. Windows workgroups, 20 controllers (see domain controllers) F logons (see domain logons) fake directory create times option, 232 new option for password timeout fake oplocks option, 153 (Samba version 2.0), 239 FAQ, Samba, 291 roles in assumed by Samba, 26 fast locking, 36 Windows, 18, 28, 184–192 fatal error, option for, 244 authentication, 170 fault tree, 257–291 caution when selecting, 190 how to use, 257 support for, 28 "File and Printer Sharing for Microsoft dont descend option, 133 Networks", 53, 60, 246 DOS file permissions and file creation masks, 138 attributes, 135–143 filenames DOS-formatted carriage returns, 193 8.3 format, 143 downloads limitations on, 143 Samba, 32 representing/resolving, 145 obtained using CVS, 378 Unix, option for, 245 tcpdump utility, 78, 257 files drive letters, mapping, 5 archive, 137 dynamically linked libraries, 33 attributes, 135–143 deleting, option for, 129 E hidden, 128, 136 elections, 23 options for, 134 operating system values in, 117 open, option for maximum order of decisions in, 118 number of, 243 role settings in, 117 permissions, 135–143 WINS servers and, 26 options for, 140 enabling/disabling features, 34 read-only, 136 encrypt passwords option, 181 deleting, 139, 142 encrypted passwords, 172 system, 136 Microsoft format, 183 in use, status of, 9 option for, 181 veto, 129–131 vs. plaintext passwords, 173 option for deleting, 135 Entire Network icon, 4 filesystems enumerated lists, 91 differences between, 127–131 errors links and, 130 searching for, 38 options for, 132–135 syntax, 45 reporting on by Samba, option for, 242 /etc/hosts file, 57, 60 (see also files) /etc/inetd.conf configuration files, 48 fixed user configuration, 196 adding SWAT tool to, 41 flat namespaces, 14, 25 ,sambaIX.fm.28352 Page 389 Friday, November 19, 1999 3:40 PM Index 389 follow symlinks option, 133 hosts force create mode option, 141 files (Windows 95/98), 59 force directory mode option, 141 files (Windows NT computers), 71 force group option, 139, 141 networking option for connections, 101, force user option, 139, 141 103, 105 foreign-language characters, 234–236 subnets and, caution with, 102 free space on disk, option for, 241 hosts allow option, 103 fstype option, 242 hosts deny option, 105 FTP (File Transfer Protocol), 6 hosts equiv option, 184 sites for Samba downloads, 32 how-tos, fault tree, 257–291 http, 6 G HUP (hangup) signal, 48 gateway field, 68 getwd cache option, 134, 320 I global options, 90 Identification Changes dialog box [globals] section, 88 (Windows NT), 63 GNU autoconf, 29 Identification tab, 60 GNU configure script, 34 implementations, Microsoft, 18–27 GNU General Public License (GPL), 3, 378 include option, 92 groups, 155–158 inetd daemon,
Recommended publications
  • Edit Bibliographic Records

    Edit Bibliographic Records

    OCLC Connexion Browser Guides Edit Bibliographic Records Last updated: May 2014 6565 Kilgour Place, Dublin, OH 43017-3395 www.oclc.org Revision History Date Section title Description of changes May 2014 All Updated information on how to open the diacritic window. The shortcut key is no longer available. May 2006 1. Edit record: basics Minor updates. 5. Insert diacritics Revised to update list of bar syntax character codes to reflect and special changes in character names and to add newly supported characters characters. November 2006 1. Edit record: basics Minor updates. 2. Editing Added information on guided editing for fields 541 and 583, techniques, template commonly used when cataloging archival materials. view December 2006 1. Edit record: basics Updated to add information about display of WorldCat records that contain non-Latin scripts.. May 2007 4. Validate record Revised to document change in default validation level from None to Structure. February 2012 2 Editing techniques, Series added entry fields 800, 810, 811, 830 can now be used to template view insert data from a “cited” record for a related series item. Removed “and DDC” from Control All commands. DDC numbers are no longer controlled in Connexion. April 2012 2. Editing New section on how to use the prototype OCLC Classify service. techniques, template view September 2012 All Removed all references to Pathfinder. February 2013 All Removed all references to Heritage Printed Book. April 2013 All Removed all references to Chinese Name Authority © 2014 OCLC Online Computer Library Center, Inc. 6565 Kilgour Place Dublin, OH 43017-3395 USA The following OCLC product, service and business names are trademarks or service marks of OCLC, Inc.: CatExpress, Connexion, DDC, Dewey, Dewey Decimal Classification, OCLC, WorldCat, WorldCat Resource Sharing and “The world’s libraries.
  • Legacy Character Sets & Encodings

    Legacy Character Sets & Encodings

    Legacy & Not-So-Legacy Character Sets & Encodings Ken Lunde CJKV Type Development Adobe Systems Incorporated bc ftp://ftp.oreilly.com/pub/examples/nutshell/cjkv/unicode/iuc15-tb1-slides.pdf Tutorial Overview dc • What is a character set? What is an encoding? • How are character sets and encodings different? • Legacy character sets. • Non-legacy character sets. • Legacy encodings. • How does Unicode fit it? • Code conversion issues. • Disclaimer: The focus of this tutorial is primarily on Asian (CJKV) issues, which tend to be complex from a character set and encoding standpoint. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations dc • GB (China) — Stands for “Guo Biao” (国标 guóbiâo ). — Short for “Guojia Biaozhun” (国家标准 guójiâ biâozhün). — Means “National Standard.” • GB/T (China) — “T” stands for “Tui” (推 tuî ). — Short for “Tuijian” (推荐 tuîjiàn ). — “T” means “Recommended.” • CNS (Taiwan) — 中國國家標準 ( zhôngguó guójiâ biâozhün) in Chinese. — Abbreviation for “Chinese National Standard.” 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations (Cont’d) dc • GCCS (Hong Kong) — Abbreviation for “Government Chinese Character Set.” • JIS (Japan) — 日本工業規格 ( nihon kôgyô kikaku) in Japanese. — Abbreviation for “Japanese Industrial Standard.” — 〄 • KS (Korea) — 한국 공업 규격 (韓國工業規格 hangug gongeob gyugyeog) in Korean. — Abbreviation for “Korean Standard.” — ㉿ — Designation change from “C” to “X” on August 20, 1997. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated Terminology & Abbreviations (Cont’d) dc • TCVN (Vietnam) — Tiu Chun Vit Nam in Vietnamese. — Means “Vietnamese Standard.” • CJKV — Chinese, Japanese, Korean, and Vietnamese. 15th International Unicode Conference Copyright © 1999 Adobe Systems Incorporated What Is A Character Set? dc • A collection of characters that are intended to be used together to create meaningful text.
  • The Luacode Package

    The Luacode Package

    The luacode package Manuel Pégourié-Gonnard <[email protected]> v1.2a 2012/01/23 Abstract Executing Lua code from within TEX with \directlua can sometimes be tricky: there is no easy way to use the percent character, counting backslashes may be hard, and Lua comments don’t work the way you expect. This package provides the \luaexec command and the luacode(*) environments to help with these problems, as well as helper macros and a debugging mode. Contents 1 Documentation1 1.1 Lua code in LATEX...................................1 1.2 Helper macros......................................3 1.3 Debugging........................................3 2 Implementation3 2.1 Preliminaries......................................4 2.2 Internal code......................................5 2.3 Public macros and environments...........................7 3 Test file 8 1 Documentation 1.1 Lua code in LATEX For an introduction to the most important gotchas of \directlua, see lualatex-doc.pdf. Before presenting the tools in this package, let me insist that the best way to manage a non- trivial piece of Lua code is probably to use an external file and source it from Lua, as explained in the cited document. \luadirect First, the exact syntax of \directlua has changed along version of LuaTEX, so this package provides a \luadirect command which is an exact synonym of \directlua except that it doesn’t have the funny, changing parts of its syntax, and benefits from the debugging facilities described below (1.3).1 The problems with \directlua (or \luadirect) are mainly with TEX special characters. Actually, things are not that bad, since most special characters do work, namely: _, ^, &, $, {, }. Three are a bit tricky but they can be managed with \string: \, # and ~.
  • Compaq TCP/IP Services for Openvms Concepts and Planning

    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.
  • List of Approved Special Characters

    List of Approved Special Characters

    List of Approved Special Characters The following list represents the Graduate Division's approved character list for display of dissertation titles in the Hooding Booklet. Please note these characters will not display when your dissertation is published on ProQuest's site. To insert a special character, simply hold the ALT key on your keyboard and enter in the corresponding code. This is only for entering in a special character for your title or your name. The abstract section has different requirements. See abstract for more details. Special Character Alt+ Description 0032 Space ! 0033 Exclamation mark '" 0034 Double quotes (or speech marks) # 0035 Number $ 0036 Dollar % 0037 Procenttecken & 0038 Ampersand '' 0039 Single quote ( 0040 Open parenthesis (or open bracket) ) 0041 Close parenthesis (or close bracket) * 0042 Asterisk + 0043 Plus , 0044 Comma ‐ 0045 Hyphen . 0046 Period, dot or full stop / 0047 Slash or divide 0 0048 Zero 1 0049 One 2 0050 Two 3 0051 Three 4 0052 Four 5 0053 Five 6 0054 Six 7 0055 Seven 8 0056 Eight 9 0057 Nine : 0058 Colon ; 0059 Semicolon < 0060 Less than (or open angled bracket) = 0061 Equals > 0062 Greater than (or close angled bracket) ? 0063 Question mark @ 0064 At symbol A 0065 Uppercase A B 0066 Uppercase B C 0067 Uppercase C D 0068 Uppercase D E 0069 Uppercase E List of Approved Special Characters F 0070 Uppercase F G 0071 Uppercase G H 0072 Uppercase H I 0073 Uppercase I J 0074 Uppercase J K 0075 Uppercase K L 0076 Uppercase L M 0077 Uppercase M N 0078 Uppercase N O 0079 Uppercase O P 0080 Uppercase
  • Design of the PATHWORKS for ULTRIX File Server by Anthony J

    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.
  • PATHWORKS for DOS Microsoft Windows Support Guide

    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.
  • 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

    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.
  • Software Product Description

    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.
  • Compaq PATHWORKS for Openvms Server Installation and Configuration Guide

    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.
  • PATHWORKS Openvms Alphaserver 4X00 DIGITAL Hitest Notes

    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...................................................................
  • VAX VMS at 20

    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