DOCSLIB.ORG

A COMPARISON BETWEEN PC SAS and UNIX SAS We Start with a Simple Comparison on General Issues Between PC SAS and UNIX SAS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A COMPARISON BETWEEN PC SAS and UNIX SAS We Start with a Simple Comparison on General Issues Between PC SAS and UNIX SAS UNIX Comes to the Rescue: A Comparison between UNIX SAS® and PC SAS® Chii-Dean Lin, San Diego State University, San Diego, CA Ming Ji, San Diego State University, San Diego, CA ABSTRACT Running SAS under PC and under UNIX environment are very similar in general. However, some differences do exist between PC SAS and UNIX SAS. A SAS code may run smoothly under PC SAS but not under UNIX SAS. In this paper, we compare the differences between PC SAS and UNIX SAS. Features that are different between PC SAS and UNIX SAS are summarized. In addition, we show a step-by-step procedure for running a PC created SAS code on a UNIX server. This paper is intended for beginners with basic SAS knowledge. INTRODUCTION “I really need the SAS results by Friday but my PC and my colleagues’ PCs can only get half of them. What should I do?” If you have a UNIX account, one suggestion would be to upload the program(s) to UNIX and run program(s) there. Even if you follow all the necessary rules and procedures of putting SAS program(s) and data sets into UNIX, sometimes the program will not run as smooth as you wish. Generally speaking, PC SAS and UNIX SAS are so similar that people usually are not aware of any problems until they try to execute a PC SAS program on UNIX (or vice versa) and run into trouble. In this paper, we compare differences between PC SAS and UNIX SAS and discuss potential problems when running a PC created SAS program on a UNIX platform. Kutler (2003) discussed the Linux/Unix & X-windows systems for SAS system administrators who would like to implement an open environment within their SAS installation. Zhang (2003) showed how one can use ODS, FTP, DDE, etc for integrating between UNIX & SAS. Our focus of this paper is not, however, to show how to integrate between PC and UNIX using SAS/CONNECT or accessing the interfaces for client/server database systems using SAS/ACCESS. Instead, we emphasize on running a SAS code on either PC or UNIX in a more traditional way: write a program, submit it, and get results. PCs are more powerful and faster than before. Even so, we still receive requests for help from students asking how to run programs such as SAS or S-plus on UNIX due to time limit or memory problem on PC. It is clear that the UNIX platform still holds some edges for running large programs over the PC platform. In this paper, we first compare major differences between PC SAS and UNIX SAS. This gives readers a quick snapshot on how SAS functions under these two systems. After giving a general idea how SAS behaves under PC and UNIX, we provide a detailed illustration on some major issues and provide simple programs for comparison purposes. A step-by-step procedure is provided on how one can run a PC created SAS program using UNIX batch mode and how one can edit the program on UNIX. The procedure gives readers a guideline to run a SAS code from PC SAS to UNIX SAS. Finally, we conclude with a brief discussion. A COMPARISON BETWEEN PC SAS AND UNIX SAS We start with a simple comparison on general issues between PC SAS and UNIX SAS. A summarized table showing the comparisons is listed below. Sample SAS codes used to show the differences are given in the next section. Note that some of the comparisons are based on the windowing environment in PC SAS and on the batch mode in UNIX SAS. Running SAS codes under PC windowing environment and under UNIX batch mode are our major concern. This is because windowing environment is used the most under PC while the background batch mode under UNIX can be used as an alternative option for running a long processing SAS program. Some of the differences listed below may be due to the running modes such as windowing environment and batch mode and not due to the PC SAS and the UNIX SAS environment. Server PC-SAS UNIX-SAS Invoking a SAS session -Windowing environment mode. -Display manager mode (if connects from a PC, -Batch mode. one needs an X Window manager such as XWIN32 to run the Display manager mode). -Non-interactive mode (Batch mode). -Line command mode. Terminating a SAS -Windowing environment mode: All modes: use kill PID under UNIX prompt process Use BREAK icon (circled (See next section for detailed description). exclamation point (!)) or CTRL+BREAK. -Batch mode: Click on cancel icon. Case Sensitive? No The UNIX environment is case sensitive but not 1 the SAS session. File directories and external file names called within SAS are case sensitive. Output & Log file -Windowing environment mode: -Display manager mode: same as PC-SAS. accumulate under the Output -Batch mode: override the existing .lst and .log Window & the Log Window. files when rerun the SAS code unless redirect to -Batch mode: override the existing different files. .lst and .log files when rerun the SAS code. Executing system Yes Yes commands within SAS? Running multiple jobs? Yes. Not efficient. Yes. Batch mode submission allows us to submit many jobs simultaneously. Line width restriction No Yes. The lines that is longer than 135 columns when creating a SAS will be automatically moved to next line. (See code? the example below) The submitted code will Windowing environment mode: the Display manager mode: the SAS code will remain in the Program SAS code will remain in the disappear from the Program Editor window after a Editor under the Display Program Editor window after a submission. Can use RUN --> RECALL LAST manager mode? submission. SUBMIT to recall the submitted SAS code. Methods for submitting Right click on the mouse and Under UNIX prompt, type sas filename.sas a batch mode job: select batch submit icon when &, where filename.sas is the SAS code you like pointing to the SAS program file or to run. drag the SAS program file to the SAS shortcut icon. Page break effect when Windowing environment mode: no Windowing environment mode: no effect (save exporting output files to effect (save from Output Window). from Output Window). other text editing Batch mode: the page break effect Batch mode: the page break effect exists (export software such as exists (export from .lst file). from .lst file). Microsoft Word: The above table provides a quick comparison between PC SAS and UNIX SAS. In this paper, we focus our discussions on running programs using windowing environment on PC and background batch mode on UNIX. The following is a simple SAS code that assigns a new variable based on two existing variables under DATA STEP and under PROC IML. Note that the assignment of z was written in a long line under the SAS Program Editor window. That is, there is no line break as shown here. The same SAS code was uploaded and run under a UNIX environment. Partial log files of the submitted SAS code under a PC SAS environment and under a UNIX SAS environment are shown below. We note that there is no error when the SAS code runs under PC but a syntax error message is issued when the same SAS code runs under UNIX SAS. We notice this same phenomenon under either DATA STEP or PROC IML. data test; x = 5; y = 10; z = x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x +y; run; proc print; run; proc iml; x = 5; y = 10; z = x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x +y; print x y z; quit; run; 2 A partial log file using PC SAS shows no error. NOTE: SAS initialization used: real time 1.90 seconds cpu time 1.85 seconds 1 data test; 2 x = 5; 3 y = 10; 4 5 z = x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y 5 ! + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x 5 ! - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x 6 + y + x * y + x - y + x + x + x + x +y; 7 run; NOTE: The data set WORK.TEST has 1 observation and 3 variables. NOTE: DATA statement used: real time 0.84 seconds cpu time 0.09 seconds If we upload the same SAS code and run under a UNIX platform, a warning message and an error is shown. A partial log file is listed: 1 data test; 2 x = 5; 3 y = 10; 4 WARNING: Truncated record. 5 z = x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + 5 ! x + x + y + y/x + x*y + 3 + x + x + y + x +y +x + x + y + x * y + x - y + x + x + x + x + y + y/x + x*y + 3 + x + x + y 5 ! + x +y +x + x 6 run;; ___ ___ ___ 22 22 22 ERROR 22-322: Syntax error, expecting one of the following: !, !!, &, *, **, +, -, /, <, <=, <>, =, >, ><, >=, AND, EQ, GE, GT, ERROR 22-322: Syntax error, expecting one of the following: !, !!, &, *, **, +, -, /, <, <=, <>, =, >, ><, >=, AND, EQ, GE, GT, ERROR 22-322: Syntax error, expecting one of the following: !, !!, &, *, **, +, -, /, <, <=, <>, =, >, ><, >=, AND, EQ, GE, GT, LE, LT, MAX, MIN, NE, NG, NL, OR, ^=, |, ||, ~=.
Load more

Recommended publications
  • Chapter 5 Formatting Pages: Basics Page Styles and Related Features Copyright
    Writer 6.0 Guide Chapter 5 Formatting Pages: Basics Page styles and related features Copyright This document is Copyright © 2018 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors Jean Hollis Weber Bruce Byfield Gillian Pollack Acknowledgments This chapter is updated from previous versions of the LibreOffice Writer Guide. Contributors to earlier versions are: Jean Hollis Weber John A Smith Ron Faile Jr. Jamie Eby This chapter is adapted from Chapter 4 of the OpenOffice.org 3.3 Writer Guide. The contributors to that chapter are: Agnes Belzunce Ken Byars Daniel Carrera Peter Hillier-Brook Lou Iorio Sigrid Kronenberger Peter Kupfer Ian Laurenson Iain Roberts Gary Schnabl Janet Swisher Jean Hollis Weber Claire Wood Michele Zarri Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected] Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published July 2018. Based on LibreOffice 6.0. Note for macOS users Some keystrokes and menu items are different on macOS from those used in Windows and Linux. The table below gives some common substitutions for the instructions in this book.
    [Show full text]
  • UEFI Shell Specification
    UEFI Shell Specification January 26, 2016 Revision 2.2 The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or to any contribution thereto. The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this information is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses and of lack of negligence, all with regard to this material and any contribution thereto. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." The Unified EFI Forum, Inc. reserves any features or instructions so marked for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SPECIFICATION AND ANY CONTRIBUTION THERETO. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR ANY CONTRIBUTION THERETO BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS DOCUMENT, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Mountbatten Pro User Guide
    User Guide Mountbatten Pro Revision 2 © Harpo Sp. z o. o. ul. 27 Grudnia 7, 61-737 Poznań, Poland www.mountbattenbrailler.com Thank you for purchasing a Mountbatten Pro. Since 1990, the Mountbatten range of Braille Writers has been offering expanded Braille writing opportunities to people all around the world. Mountbatten Braille Writers are in use in countries all over the world, bringing and supporting Braille literacy in many languages. To get the most from your new MB Pro, please read the first section, Welcome, and follow it with the second section, Exploring the MB Pro. After that, you can skip to the sections you want to read first, because you will have the most important basic information. News, resources, regular updates to this User Guide and a range of support material can be obtained from the Mountbatten website: www.mountbattenbrailler.com This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Contents Welcome................................................................................................................................................................ 1 Reading your User Guide.................................................................................................................................. 1 Very Important!.................................................................................................................................................
    [Show full text]
  • The Vim Tutorial and Reference the Vim Tutorial and Reference by Steve Oualline
    The Vim Tutorial and Reference The Vim Tutorial and Reference By Steve Oualline vim-1.0.odt (28. Sep. 2007) The Vim Book Page 1 The Vim Tutorial and Reference Table of Contents Introduction..............................................................................................26 Chapter 1:Basic Editing............................................................................28 Chapter 2:Editing a Little Faster..............................................................42 Chapter 3:Searching.................................................................................59 Chapter 4:Text Blocks and Multiple Files.................................................69 Chapter 5:Windows and Tabs....................................................................83 Chapter 6:Basic Visual Mode....................................................................99 Chapter 7:Commands for Programmers.................................................111 Chapter 8:Basic Abbreviations, Keyboard Mapping, and Initialization Files.........................................................................................................148 Chapter 9:Basic Command-Mode Commands.........................................159 Chapter 10:Basic GUI Usage...................................................................168 Chapter 11:Dealing with Text Files.........................................................175 Chapter 12:Automatic Completion.........................................................192 Chapter 13:Autocommands.....................................................................202
    [Show full text]
  • Bbedit 10.5.5 User Manual
    User Manual BBEdit™ Professional HTML and Text Editor for the Macintosh Bare Bones Software, Inc. ™ BBEdit 10.5.5 Product Design Jim Correia, Rich Siegel, Steve Kalkwarf, Patrick Woolsey Product Engineering Jim Correia, Seth Dillingham, Jon Hueras, Steve Kalkwarf, Rich Siegel, Steve Sisak Engineers Emeritus Chris Borton, Tom Emerson, Pete Gontier, Jamie McCarthy, John Norstad, Jon Pugh, Mark Romano, Eric Slosser, Rob Vaterlaus Documentation Philip Borenstein, Stephen Chernicoff, John Gruber, Simon Jester, Jeff Mattson, Jerry Kindall, Caroline Rose, Rich Siegel, Patrick Woolsey Additional Engineering Polaschek Computing Icon Design Byran Bell Packaging Design Ultra Maroon Design Consolas for BBEdit included under license from Ascender Corp. PHP keyword lists contributed by Ted Stresen-Reuter http://www.tedmasterweb.com/ Exuberant ctags ©1996-2004 Darren Hiebert http://ctags.sourceforge.net/ Info-ZIP ©1990-2009 Info-ZIP. Used under license. HTML Tidy Technology ©1998-2006 World Wide Web Consortium http://tidy.sourceforge.net/ LibNcFTP ©1996-2010 Mike Gleason & NcFTP Software NSTimer+Blocks ©2011 Random Ideas, LLC. Used under license. PCRE Library Package written by Philip Hazel and ©1997-2004 University of Cambridge, England Quicksilver string ranking Adapted from available sources and used under Apache License 2.0 terms. BBEdit and the BBEdit User Manual are copyright ©1992-2013 Bare Bones Software, Inc. All rights reserved. Produced/published in USA. Bare Bones Software, Inc. 73 Princeton Street, Suite 206 North Chelmsford, MA 01863 USA (978) 251-0500 main (978) 251-0525 fax http://www.barebones.com/ Sales & customer service: [email protected] Technical support: [email protected] BBEdit and “It Doesn’t Suck” are registered trademarks of Bare Bones Software, Inc.
    [Show full text]
  • Word Processing  Basic Features of a Word Processor:  Font and Paragraphs Lecture 9 – COMPSCI111/111G S2 2018  Styles  Headers, Footers, Footnotes, Endnotes
    Today’s lecture Storing information using ASCII Word processor basics: File formats WYSIWYG Word processing Basic features of a word processor: Font and paragraphs Lecture 9 – COMPSCI111/111G S2 2018 Styles Headers, footers, footnotes, endnotes Referencing ASCII ASCII ASCII = American Standard Code for Information Excerpt of an ASCII table Interchange A65 L 76 W 87 g 103 r 114 Associates English characters with numbers B 66 M 77 X 88 h 104 s 115 meaning text in documents can be stored as C 67 N 78 Y 89 i 105 t 116 strings of binary D 68 O 79 Z 90 j 106 u 117 E 69 P 80 … k 107 v 118 Each ASCII code is 7 bits long, meaning ASCII can F70Q81 a97 l 108 w 119 represent 128 characters G 71 R 82 b 98 m 109 x 120 H 72 S 83 c 99 n 110 y 121 There are other encoding schemes such as UTF-8 I 73 T 84 d 100 o 111 z 122 and Unicode J 74 U 85 e 101 p 112 K 75 V 86 f 102 q 113 ASCII ASCII What is the ASCII code for ‘EASY’? Text you type: YES EASY 69 65 83 89 The text in ASCII: 89 69 83 Binary stored by the computer: What is the ASCII code for ‘CompSci’? 1011001 1000101 1010011 CompSc i 67 111 109 112 83 99 105 Text editors Word processors Application software that enables the user to Application software that enables the user to edit text edit text and add formatting to the text Text is stored using ASCII or another encoding Files created by word processors store text and scheme formatting information according to a format Used to edit: Proprietary standards, eg.
    [Show full text]
  • GREP and Metacharacters in the Indesign CS5 and CS5.5 Find
    GREP and Metacharacters in the Find/Change dialog box of InDesign CS5 & 5.5 Description Text GREP Quotation Marks Text GREP Beginning of Paragraph . ^ Found (Change Field) GREP Tab . ^t . \t Any Double Quotation Marks . “ . “ End of Paragraph . $ Found Text . $0 Forced Line Break . ^n . \n Any Single Quotation Marks . ‘ . ‘ Beginning of Story . .\A . Found 1 . $1 End of Paragraph . ^p . \r. Straight Double Quotation Marks “ . ^” . ~” End of Story . \Z Found 2 . $2 Symbols Text GREP Double Left Quotation Marks “ . ^{ . ~{ Repeat GREP Found 3 . $3 Bullet Character • . ^8 . .~8 Double Right Quotation Marks “ . ^} . ~} Zero or One Time . ? Found 4 . $4 Carat Character ^ . ^^ . \^ Straight Single Quotation Mark ‘ . ^’ . ~’ Zero or More Times . * Found 5 . $5 Backslash Character \ . \ . \\ Single Left Quotation Mark ‘ . ^[ . ~[ One or More Times . +. Found 6 . $6 Copyright Symbol © . ^2 . ~2 Single Right Quotation Mark ’ . ^] . ~] Zero or One Time (Shortest Match) . ?? Found 7 . $7 Ellipsis … . ^e . ~e Break Character Text GREP Zero or More Times (Shortest Match) . *? Found 8 . $8 Paragraph Symbol ¶ . ^7 . ~7 Standard Carriage Return . ^b. .~b One or More Times (Shortest Match) . +? Found 9 . $9 Registered Trademark Symbol ® . ^r . ~r Column Break . ^M . ~M Match GREP More undocumented GREP codes Section Symbol § . ^6 . .~6 Frame Break . ^R . .~R Marking Subexpression . () Letter . \p{letter} Trademark Symbol ™ . ^d. .~d Page Break . ^P . .~P Non-Marking Subexpression . (?:) Lowercase letter . \p{lowercase_letter} Open Parenthesis ( . ( . \( Odd Page Break . ^L . ~L Character Set . [] Uppercase letter . \p{uppercase_letter} Closed Parenthesis ) . ) . \) Even Page Break . ^E . ~E Or . .| Titlecase letter . \p{titlecase_letter} Open Brace Character { . { . \{ Discretionary Line Break . .^k . ~k Positive Lookbehind . (?<=) Spacing modifier letter . .\p{modifier_letter} Closed Brace Character } .
    [Show full text]
  • Documentation for Confluence 7.4 2
    Documentation for Confluence 7.4 2 Contents Get started . 6 Tutorial: Navigate Confluence . 7 The dashboard . 8 The space directory . 10 The space sidebar . 11 Keyboard shortcuts . 14 Complete your mission . 16 Tutorial: Space ace . 17 Create a project space . 18 Create your personal space . 20 Create the team's PR space . 21 Delete and archive spaces . 23 Spaces . 24 Create a Space . 27 Create a Space From a Template . 30 Space Keys . 32 Navigate Spaces . 33 Space Permissions Overview . 35 Assign Space Permissions . 38 Make a Space Public . 41 Give Access to Unlicensed Users from Jira Service Desk . 43 Organize your Space . 44 Set up a Space Home Page . 49 Use Labels to Categorize Spaces . 53 Customize your Space . 55 Configure the Sidebar . 57 Edit a Space's Color Scheme . 59 Apply a Theme to a Space . 61 Documentation theme migration FAQ . 62 Customize Space Layouts . 68 Archive a Space . 70 Delete a Space . 72 Export Content to Word, PDF, HTML and XML . 73 Customize Exports to PDF . 76 Advanced PDF Export Customizations . 82 Create a PDF in Another Language . 85 Pages and blogs . 86 Create and Edit Pages . 87 Blog Posts . 90 The Editor . 92 Symbols, Emoticons and Special Characters . 96 Collaborative editing . 98 Move and Reorder Pages . 101 Copy a Page . 103 Delete or Restore a Page . 106 Add, Remove and Search for Labels . 108 Display Pages with Label Macros . 111 Drafts . 112 Concurrent Editing and Merging Changes . 114 Page Restrictions . 115 Links . 120 Anchors . 125 Tables . 128 Add, Assign, and View Tasks . 131 Autocomplete for links, files, macros and mentions .
    [Show full text]
  • TABLE of CONTENTS Installation
    11.1 TABLE OF CONTENTS Installation ......................................................................................................................................... 1 Launching / Activating / Registering Final Draft ........................................................................................................ 1 Opening and Activating Final Draft .............................................................................................................................. 1 Deactivation ................................................................................................................................................................................ 2 Frequently-Asked Questions .................................................................................................................................................. 3 What is product activation? ............................................................................................................................................... 3 How do I move my activation to another computer? ....................................................................................... 3 Is product activation the same as product registration? ................................................................................. 3 Do I have to register my copy of Final Draft? What are the benefits of registering? ...................... 3 What is deactivation and when should I do it?.....................................................................................................
    [Show full text]
  • Pro Powershell for Database Developers
    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® Cafferky RELATED Pro PowerShell for Database Developers Pro PowerShell for Database Developers helps you master PowerShell application development by continuing where other books leave off. There are no “Hello World” functions here, just real-world examples that get down to business. Develop and deploy database and ETL applications in a reusable framework. Read from any data source and write to any destination. Integrate PowerShell with SQL Server. Pro PowerShell for Database Developers shows how to dive into the PowerShell environment and customize it to your needs. Learn about function polymorphism using parameter sets, and extend objects via PowerShell-style inheritance. Use PowerShell as an ETL tool surpassing even SSIS. Write full-blown Windows GUI applications, and implement multi-threading through the .NET Windows Workflow Foundation. All these topics are explained using real-world examples encapsulated into modules you can immediately put to use in your organization. You’ll reap even more as you come to grips with all that PowerShell can do. Begin the journey toward deep expertise and amazing productivity with Pro PowerShell for Database Developers. Shelve in: ISBN 978-1-4842-0542-6 54999 .NET User level: Intermediate–Advanced SOURCE CODE ONLINE 9781484 205426 www.apress.com Pro PowerShell for Database Developers Bryan Cafferky Pro PowerShell for Database Developers Copyright © 2015 by Bryan Cafferky This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed.
    [Show full text]
  • Duxbury Manual
    Duxbury Braille Translator Manual Welcome to DBT! Thank you for choosing the Duxbury Braille Translator! DBT has several types of on-line help. This help system is the standard for Microsoft Windows XP and later. Before we proceed, you may wish to adjust the size of text displayed here. If you have a wheel mouse, click anywhere in this topic, hold down the Control key, and roll the mouse wheel backwards and forwards to increase or decrease the font size to an acceptable level. If you do not have a wheel mouse, the text size can be adjusted via the "Text Size" option in Internet Explorer's View menu. Note also that if you wish to print a Topic, your selected text size will be reflected in the printed output. Learn how to use this help system Guidelines for the Use of Braille Translators One of the most important, and perhaps obvious, things to watch out for when producing braille, is using the correct Language Translation Tables. An English document, translated using French braille rules would produce a very strange form of braille. But even an English document has its own National Braille Table. BANA has an excellent set of general guidelines for the use of braille translators, entitled "Guidelines for the Production of Braille Materials Through the Use of Braille Translation Software," available on its web site at: http://www.brailleauthority.org Many pointers given there are applicable generally, not only in BANA countries. BAUK also publishes various material relating to English/British braille. You can find more information on BAUK at http://www.bauk.org.uk.
    [Show full text]
  • Text2pdf Documentation
    Text2PDF FyTek, Inc. Web site: http://www.fytek.com FyTek's Text2PDF Trademarks FyTek, FyTek Text2PDF and the FyTek logo are registered trademarks or trademarks of FyTek Incorporated in the United States and/or other countries. Acrobat, Adobe, Adobe PDF and Adobe Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product names, logos, designs, titles, words or phrases mentioned within this publication may be trademarks, servicemarks, or tradenames of FyTek, Inc. or other entities and may be registered in certain jurisdictions including internationally. FyTek Disclaimer FYTEK, INC. MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING THE ENCLOSED COMPUTER SOFTWARE PACKAGE, ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE. Copyright © 2000-2020 FyTek, Inc. All rights reserved. This manual may not be copied, photocopied, reproduced, translated, or converted to any electronic or machine-readable form in whole or in part without prior written approval of FyTek, Inc. This guide may contain links to third-party websites that are not under the control of FyTek, and FyTek is not responsible for the content on any linked site. If you access a third-party website mentioned in this guide, then you do so at your own risk.
    [Show full text]