Adobe Acrobat .Pdf

Total Page:16

File Type:pdf, Size:1020Kb

Adobe Acrobat .Pdf Pennsylvania ACEP 2001 ED Informatics Symposium Page 1/2 Computer Terminology Reference 2.2 Keith Conover, M.D., FACEP ADSL Asymmetric Digital Subscriber Line (form of CRT Cathode Ray Tube: standard type computer Firewire IEEE 1394 serial port (faster than USB) DSL) monitor display FLOPS Floating Point Operations/Second AFAIK (as far as I know; email) CPU Central Processing Unit FPM Fast Page Mode (RAM) AGP Advanced Graphics Port CSID Call Subscriber ID (for FAX and phone caller FYI For Your Information AIM AOL Instant Messenger ID) GIGO Garbage In, Garbage Out ALT. ALTernate lifestyle (USENET newsgroup CSLIP Compressed Serial Line Interface Protocol GIS Geographic Information System category) [Internet] GNU Gnu's Not Unix (operating system that really ANSI American National Standards Institute CSV Comma-Separated Value/Variable (file type) IS Unix) AOL America Online CTRL Control (computer keyboard key) GPS Global Positioning Satellite/System ARQ Automatic Repeat Request CYMK Cyan-Yellow-Magenta-Black (color model) GUI Graphical User Interface ASCII American Standard Code for Information DAC Data Acquisition and Control + Digital to GW-basic Gee Whiz BASIC Interchange Analog Converter HDSL High-Data-Rate Digital Subscriber Line ASP Association of Shareware Professionals dB Decibel (DSL) + High-Speed Digital Subscriber ASPI Advanced SCSI Programming Interface DBMS Data Base Management System Loop [Adaptec] DCD Data Carrier Detect HDTV High Definition Television ATA Advanced Technology Attachment (original DCE Data Communications Equipment + HEX Hexadecimal hard drive interface) Distributed Computing Environment [OSF] HP Hewlett-Packard (Company) ATDT Attention Dial Tone (modem command) + Distributed Computing Equipment HPFS High-Performance File System (Windows ATM Adobe Typeface Manager + Asynchronous DCF Data Communication Facility [IBM] + NT) Transfer Mode DDE Direct Data Entry + Dynamic Data HPGL Hewlett-Packard Graphics Language ATZ Attention Restore configuration profile from Exchange [Microsoft] HPIB Hewlett-Packard Interface Bus nonvolatile RAM (modem command) DDR Double Data Rate (double=speed of RAM) HPLJ Hewlett-Packard Laser Jet Autoexec Automatic Execution file (AUTOEXEC.BAT DDR-SDRAM Double Data Rate-SDRAM HSV Hue Saturation Value (color model) automatically executed on startup of DOS DIMM Dual Inline Memory Module HTML HyperText Markup Language systems) DIN Deutsche Industrie Norm (German HTTP HyperText Transport Protocol AWK (Unix language named after its authors... Al equivalent of EIA) HTTP-NG HTTP Next Generation Aho, Peter Weinberger and Brian DIP Dual In-line Package (e.g., DIP switches) HTTPS HyperText Transfer Protocol Secure Kernighan) DIR Directory (file) Hz Hertz (frequency, per second) B2B Business to Business DLL Dynamic Link Library IDE Integrated Development Environment BDSL Broadband DSL DMA Direct Memory Access/Addressing [Borland] + Integrated Drive Electronics + BEDO Burst Extended Data Out (RAM) DNS Domain Naming System (Internet address Intelligent Drive Electronics BIOS Basic Input/Output System (system chips) names) IEEE 1394 Firewire (faster serial port than USB) BPS Bits Per Second + Bytes Per Second DOS Disk Operating System IMAP Internet Message Access Protocol [Internet; a BsoD Blue (or black) Screen of Death: Windows DPI Dots Per Inch step up from POP] just died (again) DRAM Dynamic Random Access Memory IMHO (in my humble opinion; email) CAD Computer Aided Design DSL Digital Subscriber Line: fast Internet I/O Input/Output (serial and parallel ports) CADD Computer Aided Design and Drafting connection over existing phone lines IP Internet Protocol (as in TCP/IP) CC: Carbon Copy (email usage) DSTN Double Supertwisted Nematic (LCD screen IPX Internetwork Packet Exchange [Novell] CCITT Comite Consultatif International type) IR Infrared Telegraphique et Telephonique/ DTMF Dual Tone Multiple Frequency (phone tones) IrDA Infrared Data Association (Ir port standard) Consultative Committee for International DUN Dial-Up Networking (Microsoft) IRQ Interrupt Request (PC hardware signal) Telegraph and Telephone DVD Digital Video Disk; Digital Versatile Disk; 4.7 ISA Industry Standard Architecture CD Change Directory (UNIX/DOS) GB CD format ISDN Integrated Services Digital Network (digital CD-R Compact Disk - Recordable EBCDIC Extended Binary Coded Decimal Interchange phone line) CD0R/W Compact Disk - Rewritable Code [IBM] (is to ASCII as Sanskrit is to ISP Internet Service Provider CD-ROM Compact Disk - Read Only Memory English) IT Information Technology CD-WO Compact Disk - Write Once ECC Error Check Code + Error Checking and I-WAY Information Highway CD-XA Compact Disk - Extended Architecture Correction + Error Correction Code JPEG Joint Photographic Experts Group CDMA Code-Division Multiple Access ECP Enhanced Capabilities Port [Microsoft] KB Keyboard + Kilobyte (1,024 bytes; also kB) (wireless/cellphone protocol) EDO Extended Data Out (RAM) kHz Kilohertz CDPD Cellular Digital Packet Data (wireless EEPROM Electrically Erasable Programmable Read- LAN Local Area Network protocol) Only Memory LCD Liquid Crystal Display CERN The European Particle Physics Laboratory EIDE Enhanced Integrated Drive Electronics (hard LED Light Emitting Diode (initials originally from Conseil European drive interface) LF Line Feed pour la Recherche Nucleaire) EISA Extended Industry Standard Architecture LIF Low Insertion Force CERT Computer Emergency Response Team) (PC bus design) LINUX (Free-Source version of UNIX Operating CGI-BIN Common Gateway Interface – Binary EMACS Editing Macros [Unix editor] system named after Linus Torvalds) (programming for Web forms) EOF End of File (^Z character) listserv List Server [Internet] CIS CompuServe Information Service EPP Enhanced Parallel Port LPI Lines Per Inch CMOS Complementary Metal-Oxide Semiconductor EPROM Electrically Programmable Read Only LPT Line Printer (type of nonvolatile memory chip) + PC Memory + Erasable Programmable Read LPT1 First Parallel Printer Port configuration stored on CMOS Only Memory LPT2 Second Parallel Printer Port CMYK Cyan-Magenta-Yellow-Black (color model) ESDI Enhanced Small Device Interface LQ Letter Quality COAX Coaxial Cable (for Ethernet and similar EWAN Emulator Without A Good Name [Internet] LSI Large Scale Integration networks) FAQ Frequently Asked Question LZW Lempel-Ziv-Walsh (algorithm) COM1 First serial Port (asynchronous port) FAT File Allocation Table MB Megabyte (also mB; 1,000 kilobytes) COM2 Second serial Port FDC Floppy Disk Controller MBASIC Microsoft BASIC [Microsoft] COMDEX Computer Dealers Exposition (biggest yearly FDISK Fixed Disk (DOS utility) MBps Megabytes Per Second U.S. computer show) FIFO First-In, First-Out Mbps Megabits Per Second Pennsylvania ACEP 2001 ED Informatics Symposium Page 2/2 Computer Terminology Reference 2.2 Keith Conover, M.D., FACEP MD Make Directory (DOS/Unix) SDRAM Synchronous Dynamic Random Access .BAS Basic Language MEG Megabyte Memory .BAT Batch Processing MFS Macintosh File System [Macintosh] SGML Standard Generalized Markup Language .BIN Binary MHz Megahertz (million cycles per second) SGRAM Synchronous Graphics RAM .BMP Bitmap Picture MIDI Musical Instrument Digital Interface SIMM Single In-line Memory Module .CFG Configuration MIME Multipurpose Internet Mail Extension [email SIPP Single In-line Pin Package .CGM Computer Graphics Metafile + attachment protocol] SLIP Serial Line Interface Protocol .CHK CHKDSK MIPS Million Instructions Per Second S-MIME Secure MIME .COM Command MMX Multimedia Extensions (additional CPU SMTP Simple Mail Transfer Protocol (basic email .DAT Data instructions) protocol) .DIC Dictionary MODEM Modulator Demodulator SNOBOL String Oriented Symbolic Language .DOC Document + Documentation (file name MPC Multimedia Personal Computer (Microsoft) (Programming Language) extensions) MPEG Moving Picture Experts Group SO-DIMM Small Outline DIMM .DRV Device Driver (Also see .DVR) MSCDEX Microsoft Compact Disc Extension SRAM Static Random Access Memory .EPS Encapsulated PostScript MS-DOS Microsoft - Disk Operating System SSL Secure Sockets Layer .HLP Help MSG Message SVGA Super Video Graphics Array .HQX BinHexed [Macintosh] MSIE Microsoft Internet Explorer [Microsoft] SYSOP System Operator .ICO Icon MTBF Mean Time Between Failures TCP/IP Transmission Control Protocol/Internet .IDX Index NCSA National Center for Supercomputing Protocol .INI Initialize Applications TDMA Tone-Division Multiple Access .JPG Joint Photographic Experts Group NICAD Nickel Cadmium wireless/cellphone protocol (compressed graphics format) NIMH Nickel-Metal Hydride TEMP Temporary .ME Usually Read.ME NNTP Network News Transfer Protocol [Internet] Thomas The (U.S.) House (of Representatives) Open .MP3 MPEG 3 compressed audio NSFNET National Science Foundation Network Multimedia Access System .NDX Index OCX OLE Custom Control TIFF Tagged Image File Format .OLD Old version OLE Object Linking and Embedding [Microsoft] TMP Temporary .OVL Program Overlay PBSRAM Pipeline Burst RAM TWAIN Technology Without Any Interesting Name .OVR Program Overlay PC-DOS Personal Computer - Disk Operating System (connection between application and scanner .PAS PASCAL source code [IBM] software) .PCT Picture PCI Peripheral Component Interconnect/Interface UAE Unrecoverable Application Error .PCX Picture Image (PC Bus) UART Universal Asynchronous .PDF Portable Document Format (Adobe Acrobat) PCMCIA Personal Computer Memory Card Receiver/Transmitter + Printer Description [Borland,Lotus] International Association UDMA Ultra Direct
Recommended publications
  • Better Performance Through a Disk/Persistent-RAM Hybrid Design
    The Conquest File System: Better Performance Through a Disk/Persistent-RAM Hybrid Design AN-I ANDY WANG Florida State University GEOFF KUENNING Harvey Mudd College PETER REIHER, GERALD POPEK University of California, Los Angeles ________________________________________________________________________ Modern file systems assume the use of disk, a system-wide performance bottleneck for over a decade. Current disk caching and RAM file systems either impose high overhead to access memory content or fail to provide mechanisms to achieve data persistence across reboots. The Conquest file system is based on the observation that memory is becoming inexpensive, which enables all file system services to be delivered from memory, except providing large storage capacity. Unlike caching, Conquest uses memory with battery backup as persistent storage, and provides specialized and separate data paths to memory and disk. Therefore, the memory data path contains no disk-related complexity. The disk data path consists of only optimizations for the specialized disk usage pattern. Compared to a memory-based file system, Conquest incurs little performance overhead. Compared to several disk-based file systems, Conquest achieves 1.3x to 19x faster memory performance, and 1.4x to 2.0x faster performance when exercising both memory and disk. Conquest realizes most of the benefits of persistent RAM at a fraction of the cost of a RAM-only solution. Conquest also demonstrates that disk-related optimizations impose high overheads for accessing memory content in a memory-rich environment. Categories and Subject Descriptors: D.4.2 [Operating Systems]: Storage Management—Storage Hierarchies; D.4.3 [Operating Systems]: File System Management—Access Methods and Directory Structures; D.4.8 [Operating Systems]: Performance—Measurements General Terms: Design, Experimentation, Measurement, and Performance Additional Key Words and Phrases: Persistent RAM, File Systems, Storage Management, and Performance Measurement ________________________________________________________________________ 1.
    [Show full text]
  • Allgemeines Abkürzungsverzeichnis
    Allgemeines Abkürzungsverzeichnis L.
    [Show full text]
  • System Calls System Calls
    System calls We will investigate several issues related to system calls. Read chapter 12 of the book Linux system call categories file management process management error handling note that these categories are loosely defined and much is behind included, e.g. communication. Why? 1 System calls File management system call hierarchy you may not see some topics as part of “file management”, e.g., sockets 2 System calls Process management system call hierarchy 3 System calls Error handling hierarchy 4 Error Handling Anything can fail! System calls are no exception Try to read a file that does not exist! Error number: errno every process contains a global variable errno errno is set to 0 when process is created when error occurs errno is set to a specific code associated with the error cause trying to open file that does not exist sets errno to 2 5 Error Handling error constants are defined in errno.h here are the first few of errno.h on OS X 10.6.4 #define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system call */ #define EIO 5 /* Input/output error */ #define ENXIO 6 /* Device not configured */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file descriptor */ #define ECHILD 10 /* No child processes */ #define EDEADLK 11 /* Resource deadlock avoided */ 6 Error Handling common mistake for displaying errno from Linux errno man page: 7 Error Handling Description of the perror () system call.
    [Show full text]
  • Active@ UNDELETE Documentation
    Active @ UNDELETE Users Guide | Contents | 2 Contents Legal Statement.........................................................................................................5 Active@ UNDELETE Overview............................................................................. 6 Getting Started with Active@ UNDELETE.......................................................... 7 Active@ UNDELETE Views And Windows...................................................................................................... 7 Recovery Explorer View.......................................................................................................................... 8 Logical Drive Scan Result View..............................................................................................................9 Physical Device Scan View......................................................................................................................9 Search Results View...............................................................................................................................11 File Organizer view................................................................................................................................ 12 Application Log...................................................................................................................................... 13 Welcome View........................................................................................................................................14 Using
    [Show full text]
  • Active @ UNDELETE Users Guide | TOC | 2
    Active @ UNDELETE Users Guide | TOC | 2 Contents Legal Statement..................................................................................................4 Active@ UNDELETE Overview............................................................................. 5 Getting Started with Active@ UNDELETE........................................................... 6 Active@ UNDELETE Views And Windows......................................................................................6 Recovery Explorer View.................................................................................................... 7 Logical Drive Scan Result View.......................................................................................... 7 Physical Device Scan View................................................................................................ 8 Search Results View........................................................................................................10 Application Log...............................................................................................................11 Welcome View................................................................................................................11 Using Active@ UNDELETE Overview................................................................. 13 Recover deleted Files and Folders.............................................................................................. 14 Scan a Volume (Logical Drive) for deleted files..................................................................15
    [Show full text]
  • MSD FATFS Users Guide
    Freescale MSD FATFS Users Guide Document Number: MSDFATFSUG Rev. 0 02/2011 How to Reach Us: Home Page: www.freescale.com E-mail: [email protected] USA/Europe or Locations Not Listed: Freescale Semiconductor Technical Information Center, CH370 1300 N. Alma School Road Chandler, Arizona 85224 +1-800-521-6274 or +1-480-768-2130 [email protected] Europe, Middle East, and Africa: Information in this document is provided solely to enable system and Freescale Halbleiter Deutschland GmbH software implementers to use Freescale Semiconductor products. There are Technical Information Center no express or implied copyright licenses granted hereunder to design or Schatzbogen 7 fabricate any integrated circuits or integrated circuits based on the 81829 Muenchen, Germany information in this document. +44 1296 380 456 (English) +46 8 52200080 (English) Freescale Semiconductor reserves the right to make changes without further +49 89 92103 559 (German) notice to any products herein. Freescale Semiconductor makes no warranty, +33 1 69 35 48 48 (French) representation or guarantee regarding the suitability of its products for any particular purpose, nor does Freescale Semiconductor assume any liability [email protected] arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or Japan: incidental damages. “Typical” parameters that may be provided in Freescale Freescale Semiconductor Japan Ltd. Semiconductor data sheets and/or specifications can and do vary in different Headquarters applications and actual performance may vary over time. All operating ARCO Tower 15F parameters, including “Typicals”, must be validated for each customer 1-8-1, Shimo-Meguro, Meguro-ku, application by customer’s technical experts.
    [Show full text]
  • Life in the Fast Lane: Optimisation for Interactive and Batch Jobs Nikola Marković, Boemska T.S
    Paper 11825-2016 Life in the Fast Lane: Optimisation for Interactive and Batch Jobs Nikola Marković, Boemska T.S. Ltd.; Greg Nelson, ThotWave Technologies LLC. ABSTRACT We spend so much time talking about GRID environments, distributed jobs, and huge data volumes that we ignore the thousands of relatively tiny programs scheduled to run every night, which produce only a few small data sets, but make all the difference to the users who depend on them. Individually, these jobs might place a negligible load on the system, but by their sheer number they can often account for a substantial share of overall resources, sometimes even impacting the performance of the bigger, more important jobs. SAS® programs, by their varied nature, use available resources in a varied way. Depending on whether a SAS® procedure is CPU-, disk- or memory-intensive, chunks of memory or CPU can sometimes remain unused for quite a while. Bigger jobs leave bigger chunks, and this is where being small and able to effectively exploit those leftovers can be a great advantage. We call our main optimization technique the Fast Lane, which is a queue configuration dedicated to jobs with consistently small SASWORK directories, that, when available, lets them use unused RAM in place of their SASWORK disk. The approach improves overall CPU saturation considerably while taking loads off the I/O subsystem, and without failure results in improved runtimes for big jobs and small jobs alike, without requiring any changes to deployed code. This paper explores the practical aspects of implementing the Fast Lane on your environment.
    [Show full text]
  • Winreporter Documentation
    WinReporter documentation Table Of Contents 1.1 WinReporter overview ............................................................................................... 1 1.1.1.................................................................................................................................... 1 1.1.2 Web site support................................................................................................. 1 1.2 Requirements.............................................................................................................. 1 1.3 License ....................................................................................................................... 1 2.1 Welcome to WinReporter........................................................................................... 2 2.2 Scan requirements ...................................................................................................... 2 2.3 Simplified Wizard ...................................................................................................... 3 2.3.1 Simplified Wizard .............................................................................................. 3 2.3.2 Computer selection............................................................................................. 3 2.3.3 Validate .............................................................................................................. 4 2.4 Advanced Wizard....................................................................................................... 5 2.4.1
    [Show full text]
  • 007-2007: the FILENAME Statement Revisited
    SAS Global Forum 2007 Applications Development Paper 007-2007 The FILENAME Statement Revisited Yves DeGuire, Statistics Canada, Ottawa, Ontario, Canada ABSTRACT The FILENAME statement has been around for a long time for connecting external files with SAS®. Over the years, it has grown quite a bit to encompass capabilities that go beyond the simple sequential file. Most SAS programmers have used the FILENAME statement to read/write external files stored on disk. However, few programmers have used it to access devices other than disk or to interface with different access methods. This paper focuses on some of those capabilities by showing you some interesting devices and access methods supported by the FILENAME statement. INTRODUCTION – FILENAME STATEMENT 101 The FILENAME statement is a declarative statement that is used to associate a fileref with a physical file or a device. A fileref is a logical name that can be used subsequently in lieu of a physical name. The syntax for the FILENAME statement is as follows: FILENAME fileref <device-type> <'external-file'> <options>; This is the basic syntax to associate an external file or a device to a fileref. There are other forms that allow you to list or clear filerefs. Please refer to SAS OnlineDoc® documentation for a complete syntax of the FILENAME statement. Once the association has been made between a physical file and a fileref, the fileref can be used in as many DATA steps as necessary without having to re-run a FILENAME statement. Within a DATA step, the use of an INFILE or a FILE statement allows the programmer to determine which file to read or write using an INPUT or a PUT statement.
    [Show full text]
  • IT Acronyms.Docx
    List of computing and IT abbreviations /.—Slashdot 1GL—First-Generation Programming Language 1NF—First Normal Form 10B2—10BASE-2 10B5—10BASE-5 10B-F—10BASE-F 10B-FB—10BASE-FB 10B-FL—10BASE-FL 10B-FP—10BASE-FP 10B-T—10BASE-T 100B-FX—100BASE-FX 100B-T—100BASE-T 100B-TX—100BASE-TX 100BVG—100BASE-VG 286—Intel 80286 processor 2B1Q—2 Binary 1 Quaternary 2GL—Second-Generation Programming Language 2NF—Second Normal Form 3GL—Third-Generation Programming Language 3NF—Third Normal Form 386—Intel 80386 processor 1 486—Intel 80486 processor 4B5BLF—4 Byte 5 Byte Local Fiber 4GL—Fourth-Generation Programming Language 4NF—Fourth Normal Form 5GL—Fifth-Generation Programming Language 5NF—Fifth Normal Form 6NF—Sixth Normal Form 8B10BLF—8 Byte 10 Byte Local Fiber A AAT—Average Access Time AA—Anti-Aliasing AAA—Authentication Authorization, Accounting AABB—Axis Aligned Bounding Box AAC—Advanced Audio Coding AAL—ATM Adaptation Layer AALC—ATM Adaptation Layer Connection AARP—AppleTalk Address Resolution Protocol ABCL—Actor-Based Concurrent Language ABI—Application Binary Interface ABM—Asynchronous Balanced Mode ABR—Area Border Router ABR—Auto Baud-Rate detection ABR—Available Bitrate 2 ABR—Average Bitrate AC—Acoustic Coupler AC—Alternating Current ACD—Automatic Call Distributor ACE—Advanced Computing Environment ACF NCP—Advanced Communications Function—Network Control Program ACID—Atomicity Consistency Isolation Durability ACK—ACKnowledgement ACK—Amsterdam Compiler Kit ACL—Access Control List ACL—Active Current
    [Show full text]
  • Mobile Consumer Products
    Mobile Consumer Products www.amphenol.com.tr [email protected] Mobile Consumer Products Mobile Devices Amphenol Mobile Consumer Products (MCP) provides a broad range of components with content on the majority of the world’s mobile devices produced each year. Amphenol MCP designs and manufactures a full range of electro -mechanical interconnect products and antennas found in mobile phones, tablets, wearables and other mobile devices. Our broad product offering includes antennas, RF cables, RF switches, internal and external connectors, LCD connectors, board-to-board connectors, cord sockets, battery connectors, input -output connectors, charger connectors, metal and ceramic injection molded components, touch panels and electromechanical hinges. Our capability for high -volume production of these technically demanding, miniaturized products, combined with our industry-leading ability to react quickly to frequently changing customer requirements together with our speed of new product introduction are the critical factors for our success in this market. Amphenol MCP Locations n Sales Location n Sales and R&D Location n Sales, R&D and Manufacturing Location 2 www.amphenol.com.tr [email protected] 3 Mobile Consumer Products MIM CIM Moving (Metal (Ceramic Touch Acrylic Sheet Sapphire Mobile Cables Antennas Mechanisms Injection Injection Panels Lens (IMD) Glass Connectors Assemblies Molding) Molding) MCP Hong Kong HQ MCP USA HQ (IL) Shanghai Amphenol Airwave Amphenol USA (IL, CA, MI) Amphenol Finland Amphenol Qujing Tekhnology Amphenol Shanzhen Amphenol Beijing Amphenol Hangzhou Phoenix Amphenol Tianjin Amphenol Changzhou Amphenol Japan Amphenol South Korea Amphenol Taiwan Amphenol Malaysia n Sales Location n Sales and R&D Location n Sales, R&D and Manufacturing Location 2 www.amphenol.com.tr [email protected] 3 Mobile Devices Mobile Consumer Products Amphenol MCP uses state of the art technology to consistently produce high quality components for mobile applications.
    [Show full text]
  • SUGI 23: It's Only Temporary
    Coders© Corner It’s Only Temporary Janet Stuelpner, ASG, Inc., Cary, North Carolina Boris Krol, Pfizer, Inc., New York, New York ABSTRACT METHODOLOGY Very often during an interactive SAS® session, it is In previous versions of the SAS system, it was not necessary to create temporary external files. From possible to define both SAS data sets and ASCII release 6.11 of the SAS System we have the ability files in the same directory. Now there is an easy to create a flat file within the same directory that way to do it. contains SAS data sets. There are benefits to using this new technique. This paper will show you how to FILENAME fileref CATALOG ‘catalog’; define this file in the WORK directory and the benefits of its use. Above is a very general FILENAME statement. The words in upper case are required to remain the INTRODUCTION same. The fileref can be any valid file reference. The ‘catalog’ must be in the form: It is easy to create a permanent file using a LIBNAME statement for SAS data sets or a library.catalog.entry.entrytype FILENAME statement for external files. However, each operating system has its own mechanism for where library must be WORK and entrytype must be creating a file that is temporary in nature. By SOURCE. If this structure is adhered to, the definition, a temporary file, whether it is a SAS data temporary file will be created in the WORK set or an external file, is one that is deleted at the directory. The most common temporary library is end of the SAS session.
    [Show full text]