DOCSLIB.ORG

CM50S User Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CM50S User Manual L CM50S User Manual CM11-530 L Implementation CM50S CM50S User Manual CM11-530 Release 5.0 3/96 Copyright, Trademarks, and Notices © Copyright 1995 by Honeywell Inc. Revision 03 – March 15, 1996 While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice. Trademark Acknowledgments: TDC 3000 is a U.S. registered trademark of Honeywell, Inc. Other brand or product names are trademarks of their respective owners. About This Publication This publication provides information on the writing, installation, testing, and modification of Application Programs that execute in the CM50S (Rel 5.0) environment as an integral part of a TDC 3000X Process Control System. It does not, by itself, cover everything you need to know to develop advanced control schemes. Essential topics covered elsewhere include: • TDC 3000X System Concepts • TDC 3000X System Configuration • FORTRAN, "C," and Pascal Programming Languages A list of related publications is located in paragraph 1.3 of this publication. Users of previous CM50S releases will find a discussion of support for vintage interface routines at subsection 1.4 You should be aware that all programmatic interface calls to CM50S are grouped by programming language. Tab 2 precedes the FORTRAN calls (sections 9 through 12), Tab 3 precedes the Pascal calls (Sections 13 through 16), and Tab 4 precedes the C language calls (sections 17 through 20). NOTE This publication supports Release 5.0 of CM50S for OpenVMS VAX and OpenVMS AXP. NOTE Change bars in this publication are used to indicate the technical changes that were made at Release 5.0 CM50S User Manual 3/96 CM50S User Manual 3/96 Table of Contents 1 INTRODUCTION 1.1 DEC VAX Interface to TDC 3000X 1.2 DEC VAX Interface Architecture 1.3 References 1.3.1 Publications Found in the TDC 3000X LCN Bookset 1.4 Support for Vintage Interface Routines 1.5 Restrictions on Entity Name Lengths TAB 1 —GENERAL USE INFORMATION 2 CONCEPTS AND MECHANISMS 2.1 Exchanging Data with an LCN 2.1.1 Single Point Transfers 2.1.2 Data Definition Tables 2.1.3 Multi-Point List Transfers 2.1.4 Point List Transfers 2.1.5 Dynamic Indirection 2.2 User Program Characteristics 2.2.1 Data Acquisition Programs (DAPs) 2.2.2 Advanced Control Programs (ACPs) 2.2.3 Indirect Control Programs 2.2.4 Program Execution Control 2.2.5 Summary of Program Execution Options 2.2.6 ACP Execution Example 2.3 CG/PLNM Database 2.3.1 Advanced Control Interface Data Points (ACIDPs) 2.3.2 Calculated Results Data Points (CRDPs) 2.3.3 Resident Data Definition Tables 2.4 Operator Interfaces to Application Programs 2.4.1 Process Operator Interfaces 2.4.2 Computer Operator Interfaces 2.5 CM50S Programmatic Interface 2.5.1 Programmatic Interface Include Files 2.5.2 Programmatic Interface Flag Parameter 2.5.3 Linking Application Programs to CM50S 2.6 Implementation Steps 2.6.1 System Start Up 2.6.2 Prepare CG/PLNM-Resident Data Points 2.6.3 Prepare Data Definition Tables 2.6.4 Compile, Link, and Install Programs 2.6.5 Test and Modify Programs and DDTs 3 ACCESS AND SECURITY 3.1 User Access to CM50S 3.1.1 User Registration Requirements 3.1.2 Log In Procedures 3.1.3 Menu-Driven Operations 3.1.4 DCL Commands and Error Messages 3.2 Starting Up CM50S 3.2.1 Using the CM50S_MGR Account 3.2.2 Submitting a Start Up Request CM50S User Manual i 3/96 Table of Contents 3.3 Shutting Down CM50S 3.3.1 User Notification 3.3.2 User Specified Delay 3.3.3 User Friendly Termination 3.3.4 Commnad 3.4 Limiting Access to Functions 3.4.1 Restrictive Rights 3.4.2 Access Control Lists 3.5 ACP Security 3.5.1 ACIDPs 3.5.2 Limiting Triggers 3.5.3 Running Under Specified Accounts 3.5.4 Privileges and Quotas 3.5.5 ACP Installation Log 3.6 Sending Modified Files to the LCN 3.6.1 ASCII File Extensions 3.6.2 Customizing File Extension Control 4 CG/PLNM POINT PREPARATION 4.1 CG/PLNM Point Building Overview 4.2 Custom Data Segment Construction 4.2.1 Custom Data Segment Heading 4.2.2 Custom Data Segment Parameters 4.2.3 Custom Data Segment Example 4.2.4 Custom Data Segment Compilation Recommendation 4.3 ACIDP/CRDP Point Building 4.3.1 ACIDP Scheduling Recommendations 4.3.2 The ACCESSKEY Parameter 4.3.3 Support for Continuous Control 4.4 ACIDP and CRDP Displays 4.4.1 CG/PLNM Parameter Descriptions 4.5 CG/PLNM Database Displays 4.5.1 CG Database Display 4.5.2 Status of Computer Gateways Display 4.5.3 Resident DDT Summary Display 4.5.4 Calculated Results Data Points Display 4.5.5 ACIDP Detail Display 4.5.6 ACIDP Summary Display 4.5.7 LCN Configuration Display 5 PROGRAM INSTALLATION AND TESTING 5.1 Program Linking 5.2 ACP Operations Screen 5.2.1 ACP Operations Screen Fields 5.2.2 ACP Operations Screen Function Keys 5.3 Modify Program Connection with ACIDP Screen 5.3.1 Modify Program Connection with ACIDP Screen Data Fields 5.3.2 Modify Program Connection with ACIDP Screen Function Keys 5.4 ACP List Screen 5.4.1 ACP List Screen Fields CM50S User Manual ii 3/96 Table of Contents 5.4.2 ACP List Screen Function Keys 5.5 ACP Installation Screens 5.5.1 ACP Installation Screen 1 Fields 5.5.2 ACP Installation Screen 1 Function Keys 5.5.3 ACP Installation Screen 2 Fields 5.5.4 ACP Installation Screen 2 Function Keys 5.5.5 Use of DCL Within an ACP 5.6 ACP Installer Activity Log Screen 5.6.1 ACP Installer Activity Log Screen Fields 5.6.2 ACP Installer Activity Log Screen Function Keys 5.7 Test and Restricted Modes of ACP Operation 5.7.1 Test Mode Operation 5.7.2 Restricted Mode Operation 5.8 Recovery of an ACP From Abort State 6 DATA DEFINITION TABLES 6.1 Overview of DDT Preparation 6.2 DDT Operations Screen 6.2.1 DDT Operations Screen Fields 6.2.2 DDT Operations Screen Function Keys 6.3 Edit DDT Screens 6.3.1 DDT Table Entry Rules 6.3.2 Input DDT Data Entry Screens 6.3.3 Output DDT Data Entry Screens 6.3.4 History DDT Data Entry Screen 6.4 ACIDP-DDT Prefetch Screen 6.5 DDT Error Summary Display 6.6 DDT Detail Description Displays 6.6.1 Function Keys for DDT Detail Displays 6.6.2 Data Presentation Rules for DDT Detail Displays 6.6.3 DDT Display Screens for Input Tables 6.6.4 DDT Display Screens for Output Tables 6.6.5 DDT Display Screen for History Tables 6.7 DDT List Display 6.7.1 DDT List Screen Data Fields 6.7.2 DDT List Screen Function Keys 6.8 DDT Source File Preparation Rules 6.8.1 Data Type Records 6.8.2 Point Identification Records 6.8.3 Point Option Records 6.8.4 Description Record 6.8.5 DDT File Data Entry Rules 7 UTILITY OPERATIONS 7.1 Task Scheduler 7.1.1 Task Scheduler Operation 7.1.2 Scheduler Command Table File 7.1.3 Command Table Modification 7.1.4 Task Scheduler Menu 7.1.5 Scheduler DCL Command Files 7.2 Makeinc Utility CM50S User Manual iii 3/96 Table of Contents 7.2.1 Running the Makeinc Program 7.2.2 Makeinc Error Screen 7.2.3 Using the List Format 7.2.4 Using the Item and Typed Item Formats 7.3 LCN File Transfer Operations 7.3.1 File Transfer Menu 7.3.2 Read File from LCN 7.3.3 Write File to LCN 7.3.4 Catalog File LIst 7.3.5 File Attributes 7.3.6 Volume List 7.3.7 Retrieve Volumes 7.3.8 Copy File 7.3.9 Move File 7.3.10 Rename File 7.3.11 Create Directory 7.3.12 Delete Directory 7.3.13 Delete File 7.3.14 Dataout Status 7.3.15 Abort Transfer 7.3.16 CM Journal Access 7.3.17 Save File from LCN 7.3.18 Load LCN File from OpenVMS 8 DCL COMMAND INTERFACE 8.1 Using the Command Interpreter 8.1.1 Incorporating CM50S Commands into DCL 8.1.2 Options and Qualifiers 8.1.3 Help and Error Handling 8.2 Retrieving LCN Data 8.2.1 Viewing LCN Value 8.2.2 History Module Collection Rate 8.3 Manipulating ACPs 8.3.1 Activate an ACP 8.3.2 Deactivate an ACP 8.3.3 Install an ACP 8.3.4 Uninstall an ACP 8.3.5 Connect an ACP to an ACIDP 8.3.6 Disconnect an ACP 8.3.7 Change Program Mode of an ACP 8.3.8 Display Status of an ACP 8.3.9 Display List of ACPs 8.4 Manipulating DDTs 8.4.1 Build a DDT 8.4.2 Delete a DDT 8.4.3 Install a DDT as CG Resident 8.4.4 Remove a DDT from the CG 8.4.5 Connect a DDT to an ACIDP 8.4.6 Disconnect a DDT from an ACIDP 8.4.7 Modify the Prefetch Triggers for a DDT 8.4.8 Display Summary Information for a DDT 8.4.9 Display Detailed Information for a DDT 8.4.10 Display List of DDTs CM50S User Manual iv 3/96 Table of Contents 8.5 Transferring LCN Files 8.5.1 LCN File Read 8.5.2 LCN File Write 8.5.3 List LCN Filenames 8.5.4 List LCN File Attributes 8.5.5 List File Attributes to Dataout 8.5.6 List LCN Volumes 8.5.7 Listing LCN Volumes to Dataout 8.5.8 Copy LCN File 8.5.9 Move LCN Files 8.5.10 Rename LCN File 8.5.11 Delete LCN File 8.5.12 Directory Transactions 8.5.13 Dataout Request 8.5.14 Dataout Status 8.5.15 Abort File Transfer 8.5.16 CM Journal Access 8.5.17 LCN File Save 8.5.18 LCN File Load TAB 2—FORTRAN INTERFACE 9 FORTRAN LANGUAGE CONSIDERATIONS 9.1 CM50S Include Files 9.1.1 Include Files for Data Transfer Functions 9.1.2 Include Files for DDT and ACP Management 9.1.3 Programmatic Interface Flag Parameters 9.2 Calling Conventions 9.3 Compatibility of Application Program with its DDTs 9.4 Data Representations 9.5 Commonly Made Errors 9.6 Error Detection by Interface Functions 9.7 Summary of User-Program Interfaces 10 LCN DATA TRANSFERS (FORTRAN) 10.1 Multipoint (DDT) Data Transfers 10.1.1 DDT Get Data Interface 10.1.2 DDT Store Data Interface 10.1.3
Load more

Recommended publications
  • Integrated Voice Evacuation System Vx-3000 Series
    SETTING SOFTWARE INSTRUCTIONS For Authorized Advanced End User INTEGRATED VOICE EVACUATION SYSTEM VX-3000 SERIES Tip In this manual, the VX-3004F/3008F/3016F Voice Evacuation Frames are collectively referred to as "VX-3000F." Thank you for purchasing TOA’s Integrated Voice Evacuation System. Please carefully follow the instructions in this manual to ensure long, trouble-free use of your equipment. TABLE OF CONTENTS 1. SOFTWARE OUTLINE ................................................................................... 3 2. NOTES ON PERFORMING SETTINGS .............................................. 3 2.1. System Requirements .......................................................................................... 3 2.2. Notes .................................................................................................................... 3 3. SOFTWARE SETUP ........................................................................................ 4 3.1. Setting Software Installation ................................................................................. 4 3.2. Uninstallation ....................................................................................................... 6 4. STARTING THE VX-3000 SETTING SOFTWARE ....................... 7 5. SETTING ITEMS ................................................................................................ 8 5.1. Setting Item Button Configuration ........................................................................ 8 5.2. Menu Bar .............................................................................................................
    [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]
  • 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]
  • Unix and Linux System Administration and Shell Programming
    Unix and Linux System Administration and Shell Programming Unix and Linux System Administration and Shell Programming version 56 of August 12, 2014 Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2009, 2010, 2011, 2012, 2013, 2014 Milo This book includes material from the http://www.osdata.com/ website and the text book on computer programming. Distributed on the honor system. Print and read free for personal, non-profit, and/or educational purposes. If you like the book, you are encouraged to send a donation (U.S dollars) to Milo, PO Box 5237, Balboa Island, California, USA 92662. This is a work in progress. For the most up to date version, visit the website http://www.osdata.com/ and http://www.osdata.com/programming/shell/unixbook.pdf — Please add links from your website or Facebook page. Professors and Teachers: Feel free to take a copy of this PDF and make it available to your class (possibly through your academic website). This way everyone in your class will have the same copy (with the same page numbers) despite my continual updates. Please try to avoid posting it to the public internet (to avoid old copies confusing things) and take it down when the class ends. You can post the same or a newer version for each succeeding class. Please remove old copies after the class ends to prevent confusing the search engines. You can contact me with a specific version number and class end date and I will put it on my website. version 56 page 1 Unix and Linux System Administration and Shell Programming Unix and Linux Administration and Shell Programming chapter 0 This book looks at Unix (and Linux) shell programming and system administration.
    [Show full text]
  • Secrets of Powershell Remoting
    Secrets of PowerShell Remoting The DevOps Collective, Inc. This book is for sale at http://leanpub.com/secretsofpowershellremoting This version was published on 2018-10-28 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. © 2016 - 2018 The DevOps Collective, Inc. Also By The DevOps Collective, Inc. Creating HTML Reports in Windows PowerShell A Unix Person’s Guide to PowerShell The Big Book of PowerShell Error Handling DevOps: The Ops Perspective Ditch Excel: Making Historical and Trend Reports in PowerShell The Big Book of PowerShell Gotchas The Monad Manifesto, Annotated Why PowerShell? Windows PowerShell Networking Guide The PowerShell + DevOps Global Summit Manual for Summiteers Why PowerShell? (Spanish) Secrets of PowerShell Remoting (Spanish) DevOps: The Ops Perspective (Spanish) The Monad Manifesto: Annotated (Spanish) Creating HTML Reports in PowerShell (Spanish) The Big Book of PowerShell Gotchas (Spanish) The Big Book of PowerShell Error Handling (Spanish) DevOps: WTF? PowerShell.org: History of a Community Contents Secrets of PowerShell Remoting ..................................... 1 Remoting Basics ................................................ 3 What is Remoting? ............................................ 3 Examining Remoting Architecture .................................. 3 Enabling
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • Computer Terminal Placement and Workflow in an Emergency Department: an Agent-Based Model Mollie R
    Computer terminal placement and workflow in an emergency department: An agent-based model Mollie R. Poynton, University of Utah, Salt Lake City, Utah, USA Vikas M. Shah, Department of Internal Medicine, Banner Good Samaritan Medical Center, Phoenix, AZ, USA Rhonda BeLue, The Pennsylvania State University, University Park, PA, USA Ben Mazzotta, Tufts University, Medford, MA, USA Heather Beil, University of North Carolina, Chapel Hill, NC, USA Saleha Habibullah, Kinnaird College for Women, Lahore, Pakistan I. INTRODUCTION Adequate analysis and consideration of workflow in relation to new systems/ technology implementation is essential in health care settings. Certainly, adequate analysis of workflow and exploration of potential unintended consequences seems essential prior to implementation of any new system or technology. However, typical analysis is limited to observation of pre- implementation workflow. Specialized settings such as emergency departments are of particular concern, because systems and technologies chosen for broad implementation in tertiary care facilities may not be appropriate. Severe unintended consequences, including increased mortality, were observed in one emergency department upon implementation of a computerized provider order entry (CPOE) system. 1 Agent-based modeling enables exploration of system behavior over a broad range of parameters, and so agent-based modeling may provide crucial pre-implementation insight into the impact of a new system/technology on workflow and/or outcomes. We developed a prototype agent-based model designed to simulate patient flow and provider workflow in an emergency department setting, relative to the number and placement of computer terminals, and explored the behavior of the system in response to various configurations. II. BACKGROUND AND SIGNIFICANCE A 2005 study by Han and colleagues found increased mortality after implementation of a CPOE system in the Pittsburgh Children’s Hospital emergency department (ED) and PICU (pediatric intensive care unit).
    [Show full text]
  • Luno Tools Run Command Documentation Page 1/6
    Luno Tools Run Command documentation Page 1/6 Luno Tools Run Command Description Run Command aims to be a user-friendly way to run command line applications, command line system calls and single line shell scripts. Setup 1. Build a working command outside Switch It is important to start with a command which achieves your task and which needs to work outside Switch. On Mac, this means you build and test the command in the Terminal App. On Windows, you build the command in “Command Prompt” (Cmd.exe) or “Windows Powershell”. By example, we can build a command which retrieves the permissions of one file and stores it in another file. On mac we can achieve this using the following command: ls -l /path/to/inputfile.txt > /path/to/outputfolder/filename.txt And on Windows Command Prompt using this command : icacls -l C:\path\to\inputfile.txt > C:\path\to\outputfolder\filename.txt If you have issues with your command at this stage (you don’t achieve the output you want, you have errors, …), then the issue is not related to the “Run Command” app itself. The people with the most knowledge about your issue are the people who are expert at the command line application, command line system call or shell script you are trying to use. Usually, there are help pages, support forums, support people specific for these applications who can help you. Alternatively, you can also ask help on the Enfocus forums. 2. Handle spaces correctly When working with these kinds of commands a space is used to separate different parts of the command, by example a space is placed between the command name and the path to the inputfile.
    [Show full text]
  • Computer Exemption Guidelines for Assessors and Property Owners
    Computer Exemption Guidelines for Assessors and Property Owners State law (sec. 70.11(39), Wis. Stats.), exempts computers, software, and electronic peripheral equipment from property taxation. *These items are frequently assessed as manufacturing personal property. Taxable/ Item Description Comments Exempt Central computer for Exempt Computer. Alarm/Security alarm/security system systems Various security system Taxable Equipment with embedded computerized components. sensory devices "All-in-one" Combination device If this equipment can only operate using a computer, it is exempt as an printer/scanner/ that includes an exempt Taxable electronic peripheral. fax/copier device Amusement devices Electronic pinball and Taxable Equipment with embedded computerized components. or arcade games video games Automated warehouse Racks and other Taxable Not connected to and operated by a computer. equipment mechanical equipment Electronic diagnostic Computer and connected electronic peripheral equipment that collect, Exempt Automotive diagnostic equipment analyze store and retrieve data. equipment Other diagnostic Taxable Mechanical or not connected to a computer. equipment Bank teller Automated teller Exempt Networked computer, terminal, or electronic peripheral equipment. machines/ATMs PC controlled equipment, networked Exempt Computers, electronic peripheral equipment Bowling and automatic PCs scoring equipment Pin setters, counters Taxable Equipment with embedded computerized components. and scoring equipment Car wash equipment Automated equipment Taxable Equipment with embedded computerized components. Scanner, scale, keyboard, register, computer, display Computer and electronic peripheral equipment - programmable electronic Cash Exempt register/Checkout screens, debit/credit device(s) that can interpret, measure, store, retrieve, and process data. system and card readers, check components swipe, printer, Mechanical - conveyor, Taxable Mechanical. tables, shelves All Copiers – Copiers networked, stand alone, Taxable Exemption does not apply to copiers.
    [Show full text]
  • Chronosync Manual for Macos
    ChronoSync Manual for macOS Econ Technologies, Inc. P.O. Box 195780 Winter Springs, FL 32719 www.econtechnologies.com copyright 2002-2018 If you can’t find the information you’re looking for in this manual, you should also refer to ChronoSync’s Help, located within the application, and our website in the Guides, Tech Notes, and Documentation sections. TABLE OF CONTENTS CHAPTER ONE.................................................................................................................. 8 Introduction .................................................................................................................................................. 8 Welcome to ChronoSync ........................................................................................................................... 9 CHAPTER TWO ............................................................................................................... 10 Basic Overview .......................................................................................................................................... 10 ChronoSync Documents .......................................................................................................................... 11 Synchronizer Tasks ............................................................................................................................. 11 Task Container .................................................................................................................................... 11 ChronoSync Organizer
    [Show full text]
  • Guide to Setting up a VMS System
    Guide to Setting Up a VMS System Order Number: AA-LA25A-TE April 1988 This manual provides system managers with the concepts and procedures needed to set up a VMS operating system for daily operation. Revision/Update Information: This is a new manual. Software Version: VMS Version 5.0 digital equipment corporation maynard, massachusetts April 1988 The information 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. Copyright ©1988 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid READER'S COMMENTS form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem VAX DEC/MMS IAS VAXcluster DECnet MASSBUS VMS DECsystem-10 PDP VT DECSYSTEM-20 PDT DECUS RSTS TM DECwriter RSX d a 0 9 ao ZK3385 HOW TO ORDER ADDITIONAL DOCUMENTATION DIRECT MAIL ORDERS USA &PUERTO RICO* CANADA INTERNATIONAL Digital Equipment Corporation Digital Equipment Digital Equipment Corporation P.O. Box CS2008 of Canada Ltd. PSG Business Manager Nashua, New Hampshire 100 Herzberg Road c/o Digital's local subsidiary 03061 Kanata, Ontario K2K 2A6 or approved distributor Attn: Direct Order Desk In Continental USA and Puerto Rico call 800-258-1710.
    [Show full text]
  • Macintosh Library Modules Release 2.4.1
    Macintosh Library Modules Release 2.4.1 Guido van Rossum Fred L. Drake, Jr., editor 30 March 2005 Python Software Foundation Email: [email protected] Copyright c 2001-2004 Python Software Foundation. All rights reserved. Copyright c 2000 BeOpen.com. All rights reserved. Copyright c 1995-2000 Corporation for National Research Initiatives. All rights reserved. Copyright c 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the end of this document for complete license and permissions information. Abstract This library reference manual documents Python’s extensions for the Macintosh. It should be used in conjunction with the Python Library Reference, which documents the standard library and built-in types. This manual assumes basic knowledge about the Python language. For an informal introduction to Python, see the Python Tutorial; the Python Reference Manual remains the highest authority on syntactic and semantic questions. Finally, the manual entitled Extending and Embedding the Python Interpreter describes how to add new extensions to Python and how to embed it in other applications. CONTENTS 1 Using Python on a Macintosh 1 1.1 Getting and Installing MacPython .................................. 1 1.2 The IDE ............................................... 2 1.3 The Package Manager ........................................ 3 2 MacPython Modules 5 2.1 macpath — MacOS path manipulation functions ......................... 5 2.2 macfs — Various file system services ............................... 5 2.3 ic — Access to Internet Config ................................... 8 2.4 MacOS — Access to Mac OS interpreter features .......................... 9 2.5 macostools — Convenience routines for file manipulation ................... 10 2.6 findertools — The finder’s Apple Events interface ...................... 10 2.7 EasyDialogs — Basic Macintosh dialogs ............................ 11 2.8 FrameWork — Interactive application framework ........................
    [Show full text]