DOCSLIB.ORG

Openvms DCL Dictionary: N–Z

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openvms DCL Dictionary: N–Z OpenVMS DCL Dictionary: N–Z Order Number: AA–PV5LH–TK June 2002 This manual provides detailed reference information and examples for Compaq OpenVMS DCL commands and lexical functions. Revision/Update Information: This manual supersedes the OpenVMS DCL Dictionary, Version 7.3. Software Version: OpenVMS Alpha Version 7.3-1 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2002 Compaq Information Technologies Group, L.P. COMPAQ, the Compaq logo, Alpha, OpenVMS, Tru64, VAX, VMS, and the DIGITAL 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 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. Nothing herein should be construed as constituting an additional warranty. ZK6200 The Compaq OpenVMS documentation set is available on CD-ROM. Contents Preface ............................................................ vii NCS...................................................... DCLII–1 ON....................................................... DCLII–2 OPEN ..................................................... DCLII–6 PASSWORD ................................................ DCLII–10 PATCH (VAX Only) . ........................................ DCLII–12 PHONE . ................................................ DCLII–13 PIPE ..................................................... DCLII–14 PPPD ..................................................... DCLII–23 PRINT .................................................... DCLII–24 PRODUCT . ................................................ DCLII–38 PURGE . ................................................ DCLII–39 READ ..................................................... DCLII–43 RECALL . ................................................ DCLII–47 RENAME . ................................................ DCLII–50 REPLY .................................................... DCLII–55 REQUEST . ................................................ DCLII–64 RETURN . ................................................ DCLII–66 RUN (Image) ............................................... DCLII–68 RUN (Process) .............................................. DCLII–70 RUNOFF . ................................................ DCLII–80 SEARCH . ................................................ DCLII–81 SET...................................................... DCLII–89 SET ACCOUNTING . ........................................ DCLII–92 SET AUDIT ................................................ DCLII–95 SET BROADCAST . ........................................DCLII–108 SET CACHE/RESET . ........................................DCLII–110 SET CARD_READER . ........................................DCLII–111 SET CLUSTER/EXPECTED_VOTES .............................DCLII–112 SET COMMAND ............................................DCLII–114 SET CONTROL .............................................DCLII–117 SETCPU..................................................DCLII–119 SETDAY..................................................DCLII–123 SETDEFAULT.............................................DCLII–124 SET DEVICE ...............................................DCLII–127 SET DEVICE/SERVED .......................................DCLII–133 SET DIRECTORY . ........................................DCLII–134 SET DISPLAY ..............................................DCLII–138 iii SET ENTRY ................................................DCLII–145 SET FILE .................................................DCLII–156 SET HOST .................................................DCLII–165 SET HOST/DTE . ............................................DCLII–168 SET HOST/DUP . ............................................DCLII–175 SET HOST/HSC . ............................................DCLII–177 SET HOST/LAT . ............................................DCLII–179 SET HOST/RLOGIN .........................................DCLII–184 SET HOST/TELNET .........................................DCLII–186 SET HOST/TN3270 ..........................................DCLII–187 SETKEY..................................................DCLII–188 SET LOGINS . ............................................DCLII–189 SET MAGTAPE . ............................................DCLII–190 SET MESSAGE . ............................................DCLII–194 SET NETWORK ............................................DCLII–196 SETON...................................................DCLII–199 SET OUTPUT_RATE .........................................DCLII–200 SET PASSWORD ............................................DCLII–201 SET PREFERRED_PATH . ....................................DCLII–205 SET PREFIX . ............................................DCLII–207 SET PRINTER . ............................................DCLII–209 SET PROCESS . ............................................DCLII–213 SET PROMPT . ............................................DCLII–223 SET PROTECTION/DEFAULT .................................DCLII–224 SET QUEUE . ............................................DCLII–225 SET RESTART_VALUE . ....................................DCLII–233 SET RIGHTS_LIST ..........................................DCLII–235 SET RMS_DEFAULT .........................................DCLII–238 SET SECURITY . ............................................DCLII–244 SETSERVER...............................................DCLII–252 SET SYMBOL . ............................................DCLII–260 SET TERMINAL ............................................DCLII–263 SET TIME .................................................DCLII–277 SET VERIFY . ............................................DCLII–279 SET VOLUME . ............................................DCLII–282 SET WORKING_SET .........................................DCLII–287 SHOW ....................................................DCLII–289 SHOW ACCOUNTING ........................................DCLII–291 SHOW AUDIT . ............................................DCLII–293 SHOW BROADCAST .........................................DCLII–297 SHOW CLUSTER ...........................................DCLII–299 SHOW CPU ................................................DCLII–300 SHOW DEFAULT ...........................................DCLII–308 SHOW DEVICES ............................................DCLII–310 SHOW DEVICES/SERVED ....................................DCLII–321 SHOW DISPLAY ............................................DCLII–326 SHOW ENTRY . ............................................DCLII–328 iv SHOW ERROR .............................................DCLII–333 SHOW INTRUSION . ........................................DCLII–336 SHOW KEY ................................................DCLII–339 SHOW LICENSE ............................................DCLII–341 SHOW LOGICAL ............................................DCLII–349 SHOW MEMORY ............................................DCLII–355 SHOW NETWORK . ........................................DCLII–373 SHOW PRINTER ............................................DCLII–377 SHOW PROCESS . ........................................DCLII–380 SHOW PROTECTION ........................................DCLII–388 SHOW QUEUE .............................................DCLII–389 SHOW QUEUE/CHARACTERISTICS ............................DCLII–396 SHOW QUEUE/FORM ........................................DCLII–398 SHOW QUEUE/MANAGERS . ................................DCLII–400 SHOW QUOTA .............................................DCLII–403 SHOW RMS_DEFAULT .......................................DCLII–404 SHOW SECURITY . ........................................DCLII–405 SHOW SERVER .............................................DCLII–409 SHOW STATUS .............................................DCLII–412 SHOW SYMBOL ............................................DCLII–413 SHOW SYSTEM ............................................DCLII–415 SHOW TERMINAL . ........................................DCLII–423 SHOW TIME ...............................................DCLII–426 SHOW TRANSLATION .......................................DCLII–427 SHOW USERS ..............................................DCLII–429 SHOW WORKING_SET .......................................DCLII–434 SHOW ZONE ...............................................DCLII–436 SORT .....................................................DCLII–437 SPAWN ...................................................DCLII–438
Load more

Recommended publications
  • Operating System Engineering, Lecture 3
    6.828 2012 Lecture 3: O/S Organization plan: O/S organization processes isolation topic: overall o/s design what should the main components be? what should the interfaces look like? why have an o/s at all? why not just a library? then apps are free to use it, or not -- flexible some tiny O/Ss for embedded processors work this way key requirement: support multiple activities multiplexing isolation interaction helpful approach: abstract services rather than raw hardware file system, not raw disk TCP, not raw ethernet processes, not raw CPU/memory abstractions often ease multiplexing and interaction and more convenient and portable note: i'm going to focus on mainstream designs (xv6, Linux, &c) for *every* aspect, someone has done it a different way! example: exokernel and VMM does *not* abstract anything! xv6 has only a few abstractions / services processes (cpu, mem) I/O (file descriptors) file system i'm going to focus on xv6 processes today a process is a running program it has its own memory, share of CPU, FDs, parent, children, &c it uses system calls to interact outside itself to get at kernel services xv6 basic design here very traditional (UNIX/Linux/&c) xv6 user/kernel organization h/w, kernel, user kernel is a big program services: process, FS, net low-level: devices, VM all of kernel runs w/ full hardware privilege (very convenient) system calls switch between user and kernel 1 good: easy for sub-systems to cooperate (e.g. paging and file system) bad: interactions => complex, bugs are easy, no isolation within o/s called "monolithic";
    [Show full text]
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • The Design of a Pascal Compiler Mohamed Sharaf, Devaun Mcfarland, Aspen Olmsted Part I
    The Design of A Pascal Compiler Mohamed Sharaf, Devaun McFarland, Aspen Olmsted Part I Mohamed Sharaf Introduction The Compiler is for the programming language PASCAL. The design decisions Concern the layout of program and data, syntax analyzer. The compiler is written in its own language. The compiler is intended for the CDC 6000 computer family. CDC 6000 is a family of mainframe computer manufactured by Control Data Corporation in the 1960s. It consisted of CDC 6400, CDC 6500, CDC 6600 and CDC 6700 computers, which all were extremely rapid and efficient for their time. It had a distributed architecture and was a reduced instruction set (RISC) machine many years before such a term was invented. Pascal Language Imperative Computer Programming Language, developed in 1971 by Niklaus Wirth. The primary unit in Pascal is the procedure. Each procedure is represented by a data segment and the program/code segment. The two segments are disjoint. Compiling Programs: Basic View Machine Pascal languag program Pascal e compile program filename . inpu r gp output a.out p t c Representation of Data Compute all the addresses at compile time to optimize certain index calculation. Entire variables always are assigned at least one full PSU “Physical Storage Unit” i.e CDC6000 has ‘wordlength’ of 60 bits. Scalar types Array types the first term is computed by the compiler w=a+(i-l)*s Record types: reside only within one PSU if it is represented as packed. If it is not packed its size will be the size of the largest possible variant. Data types … Powerset types The set operations of PASCAL are realized by the conventional bit-parallel logical instructions ‘and ‘ for intersection, ‘or’ for union File types The data transfer between the main store buffer and the secondary store is performed by a Peripheral Processor (PP).
    [Show full text]
  • Entry Point Specification
    EMV® Contactless Specifications for Payment Systems Book B Entry Point Specification Version 2.6 July 2016 © 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Contactless Book B Entry Point Specification version 2.6 Legal Notice The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • VMS CRA Y Station Now Available It Is Now Possible to Submit Jobs Functions Closely
    VMS CRA Y Station Now Available It is now possible to submit jobs Functions closely. It is implemented as a to the CRAY-1 from UCC's VAX/VMS The VMS station provides these series of commands entered in system. functions: response to the system's $ A CRAY-1 running the cos oper­ prompt. The commands look like ating system requires another -It submits jobs to the CRAY-1, VMS commands: they have pa­ computer to act as a "front-end" and returns output as a file un­ rameters and /qualifiers; they fol­ system. You prepare jobs and der the user's VMS directory. low much the same syntax and data on the front-end system, us­ -It transfers files between the interpretation rules (for example, ing whatever tools that system machines using the cos AC­ wild cards are handled correctly); provides, then submit the files as QUIRE and DISPOSE commands. and they prompt for required a batch job to the CRAY for proc­ The source of an ACQUIREd file parameters not present on the essing. Output is returned to the can be disk or tape; the desti­ command line. You can always front-end system for viewing. nation of a DISPOSEd file can recognize a station command, The software that runs on the be disk, tape, printer, or the though, because it always begins front-end machine to provide this VMS batch input queue. with the letter C. For example, communication is called a -At your option, it sends bulle­ the station command to submit a "station." tins to the terminal chronicling job to the CRAY is CSUBMIT.
    [Show full text]
  • Tyson Kopczynski
    www.it-ebooks.info Tyson Kopczynski Windows® PowerShell UNLEASHED 800 East 96th Street, Indianapolis, Indiana 46240 USA www.it-ebooks.info Windows® PowerShell Unleashed Editor-in-Chief Copyright © 2007 by Sams Publishing Karen Gettman All rights reserved. No part of this book shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, Senior Acquisitions or otherwise, without written permission from the publisher. No patent liability is Editor assumed with respect to the use of the information contained herein. Although every Neil Rowe precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions. Nor is any liability assumed for Development Editor damages resulting from the use of the information contained herein. Mark Renfrow International Standard Book Number: 0-672-32953-0 Managing Editor Library of Congress Cataloging-in-Publication Data Gina Kanouse Kopczynski, Tyson. Project Editor Microsoft PowerShell unleashed / Tyson Kopczynski. George E. Nedeff p. cm. ISBN 0-672-32953-0 Copy Editor 1. Microsoft Windows (Computer file) 2. Operating systems (Computers) I. Title. Lisa M. Lord QA76.76.O63K66 2007 Senior Indexer 005.4’46—dc22 Cheryl Lenser 2007008894 Proofreader Printed in the United States of America Water Crest First Printing: Publishing 10090807 4321 Contributing Authors Trademarks Pete Handley, Mark All terms mentioned in this book that are known to be trademarks or service marks Weinhardt, and have been appropriately capitalized. Sams Publishing cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the Josh Tolle validity of any trademark or service mark.
    [Show full text]
  • Openshift Container Platform 3.11 CLI Reference
    OpenShift Container Platform 3.11 CLI Reference OpenShift Container Platform 3.11 CLI Reference Last Updated: 2021-04-12 OpenShift Container Platform 3.11 CLI Reference OpenShift Container Platform 3.11 CLI Reference Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Ascii, Baudot, and the Radio Amateur
    ASCII, BAUDOT AND THE RADIO AMATEUR George W. Henry, Jr. K9GWT Copyright © 1980by Hal Communications Corp., Urbana, Illinois HAL COMMUNICATIONS CORP. BOX365 ASCII, BAUDOT, AND THE RADIO AMATEUR The 1970's have brought a revolution to amateur radio RTTY equipment separate wire to and from the terminal device. Such codes are found in com­ and techniques, the latest being the addition of the ASCII computer code. mon use with computer and line printer devices. Radio amateurs in the Effective March 17, 1980, radio amateurs in the United States have been United States are currently authorized to use either the Baudot or ASCII authorized by the FCC to use the American Standard Code for Information serial asynchronous TTY codes. Interchange(ASCII) as well as the older "Baudot" code for RTTY com­ munications. This paper discusses the differences between the two codes, The Baudot TTY Code provides some definitions for RTTY terms, and examines the various inter­ facing standards used with ASCII and Baudot terminals. One of the first data codes used with mechanical printing machines uses a total of five data pulses to represent the alphabet, numerals, and symbols. Constructio11 of RTTY Codes This code is commonly called the Baudot or Murray telegraph code after the work done by these two pioneers. Although commonly called the Baudot Mark Ull s,.ce: code in the United States, a similar code is usually called the Murray code in other parts of the world and is formally defined as the International Newcomers to amateur radio RTTY soon discover a whole new set of terms, Telegraphic Alphabet No.
    [Show full text]
  • HP Openvms Utility Routines Manual
    HP OpenVMS Utility Routines Manual Order Number: BA554-90019 June 2010 This manual describes the OpenVMS utility routines, a set of routines that provide a programming interface to various OpenVMS utilities. Revision/Update Information: This manual supersedes the HP OpenVMS Utility Routines Manual, OpenVMS Alpha Version 8.3. Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.4 Hewlett-Packard Company Palo Alto, California © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP 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. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ZK4493 The HP OpenVMS documentation set is available on CD. This document was prepared using DECdocument, Version 3.3-1B. Contents Preface ............................................................ xvii 1 Introduction to Utility Routines 2 Access Control List (ACL) Editor Routine 2.1 Introduction to the ACL Editor Routine ........................... ACL–1 2.2 Using the ACL Editor Routine: An Example ....................... ACL–1 2.3 ACL Editor Routine . ........................................ ACL–2 ACLEDIT$EDIT ...........................................
    [Show full text]
  • Command Line Interface Overview
    Command Line Interface Overview Note The ASR 5000 hardware platform has reached end of life and is not supported in this release. Any references to the ASR 5000 (specific or implied) or its components in this document are coincidental. Full details on the ASR 5000 hardware platform end of life are available at: https://www.cisco.com/c/en/us/products/collateral/wireless/asr-5000-series/eos-eol-notice-c51-735573.html. This chapter describes the numerous features in the command line interface (CLI). It includes information about the architecture of the CLI, its command modes and user privileges, how to obtain help within the CLI, and other key items. The operating system (StarOS™) controls the overall system logic, control processes, and the CLI. The CLI is a multi-threaded user interface that allows you to manipulate, configure, control and query the hardware and software components that make up the system and its hosted services. In addition, the CLI can host multiple instances of management and service configuration sessions. This allows multiple users to simultaneously access and manage multiple hosted services. This section provides the following information about the CLI: • CLI Structure, on page 1 • CLI Command Modes, on page 2 • CLI Administrative Users, on page 2 • CLI Contexts, on page 7 • Understanding the CLI Command Prompt, on page 8 • CLI Command Syntax, on page 9 • Entering and Viewing CLI Commands, on page 9 • Obtaining CLI Help, on page 13 • Exiting the CLI and CLI Command Modes, on page 14 • IP Address Notation, on page 15 • Alphanumeric Strings, on page 16 CLI Structure CLI commands are strings of commands or keywords and user-specified arguments that set or modify specific parameters of the system.
    [Show full text]
  • 1 Introduction to C – Part I
    1 Introduction to C – part I In this class, we will be employing the modern “C” language which is com- 1 monly used for scientific programming . “C” is closely related to C++ which is an Object Oriented language. It turns out that, while occasionally useful, the Object Oriented properties of C++ are not required for most types of scientific programming. In addition, acquiring a working knowledge of C++ can involve quite a steep learning curve. The object of this class is to get you up to speed as rapidly as possible in a powerful and versatile programming language (we have about three weeks to do that!) and then to introduce you to a number of numerical techniques useful and essential for work in physics and engineering. As it turns out, many software programming pack- ages, such as MathCad and IDL, have syntaxes that are very similar to “C”, and so learning “C” is an excellent entry point for a host of other program- ming environments. Some of you will already have a working knowledge of C or C++. If you don’t, the following three chapters will get you started. Otherwise, consider them a quick refresher. Read: The C Programming Language: Chapter 1. 1.1 Computer Memory and Variables Basically speaking, a computer program is a series of statements that manip- ulate data stored in the computer’s memory and yields a (hopefully useful) result. One can think of the memory of a computer as a series of boxes, each of which can contain one piece of data (a number, a character, etc.).
    [Show full text]