Operating System User's Mannal ~Zilog 03-0072-01 Revision a September 1978

Total Page:16

File Type:pdf, Size:1020Kb

Operating System User's Mannal ~Zilog 03-0072-01 Revision a September 1978 t_ .' Operating System User's Mannal ~Zilog 03-0072-01 Revision A September 1978 Copyright © 1978 by Zilog, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Zilog. Zilog assumes no responsibility for the use of any circuitry other than circuitry embodied in a Zilog product. No other circuit patent licenses are implied. zaO-RIO Operating System User's Manual September 1978 TABLE OF CONTENTS CHAPTER 1 - INTRODUCTION AND OVERVIEW • 1 1.1 INTRODUCTION •• 1 1.2 SYSTEM OVERVIEW 3 1.2.1 Hardware Configuration • • • • • • 3 1.2.2 File Systems • • • • • • • . • • 3 1.2.3 System Initialization •••.••• 6 1.2.4 Commands • • .• .•..••• 7 1.2.5 I/O • • • . • • • • • . • • • • • . 7 CHAPTER 2 - RIO EXECUTIVE 9 2.1 SYSTEM INITIALIZATION 9 2.2 FILE NAME CONVENTIONS · 10 2.3 MEMORY MANAGEMENT . • • . 12 2.3.1 MEMMGR • . 13 2.4 COMMAND STRING INTERPRETATION · 13 2.5 ERROR HANDLING • • . 15 2.6 PROGRAM EXECUTION OF COMMANDS · 15 CHAPTER 3 - 1/0 STRUCTURE • · 16 3.1 OVERVIEW . • · 16 3.2 I/O REQUESTS - SYSTEM CALLS · 17 3.3 THE 'ASSIGN' I/O REQUEST ••• • 19 - i - 3.4 STANDARD RIO I/O DEVICES • • • 21 3.4.1 ZDOS . • • • . 21 3.4.2 DFS . 21 3.4.3 NULL . • • • . 21 3.4.4 CON . • • • . • • • • • 22 3.4.5 PCON • 27 3.4.6 FLOPPY • • • • • • • • • • 27 3.4.7 DISK • • • • • • 27 CHAPTER 4 - PROGRAM INTERFACE • • 28 4.1 PROGRAM LOCATION • • • • • 28 4.2 PARAMETER STRING ADDRESS · 29 4.3 PROGRAM STACK SPACE • • • 29 4.4 PROGRAM TERMINATION - ERROR HANDLING ••. 29 4.5 SYSTEM CALLS - SYSTEM ENTRY POINT •. 30 4.6 INTERRUPT STATUS • • • • 31 4.7 I/O UNIT UTILIZATION • • . • • • 31 4.8 PROGRAM EXAMPLES . ... .. • 32 CHAPTER 5 - RIO COMMANDS • • 33 5.1 ACTIVATE · • 35 5.2 ALLOCATE · • 37 5.3 BRIEF . • • 39 5.4 CAT • • • 40 5.5 CLOSE • • 44 5.6 COMPARE • • 45 5.7 COpy • • 47 5.8 COPY.DISK • • • • 49 - i i - 5.9 COPYSD 51 5.10 DATE 53 5.11 DEACTIVATE 54 5.12 DEALLOCATE 55 5.13 DEBUG 56 5.14 DEFINE 60 5.15 DELETE 63 5.16 DISK. FORMAT 67 5.17 DISK. REPAIR 70 5.18 DISK. STATUS 72 5.19 DISPLAY 74 5.20 DO 75 5.21 DUMP 79 5.22 ECHO 80 5.23 ERROR 81 5.24 ERRORS 82 5.25 EXTRACT 83 5.26 FORCE 84 5.27 FORMAT 85 5.28 HELP 88 5.29 IMAGE 89 5.30 INITIALIZE 90 5.31 LADT 91 - iii 5.32 MASTER • 92 5.33 r·10VE • 93 5.34 PAUSE. • . • 98 5.35 RELEASE . • • • 99 5.36 RENAME 100 5.37 RESTORE TABS 102 5.38 SAVE TABS . 103 5.39 SET • • • 104 5.40 STATUS 109 5.41 VERBOSE III 5.42 XEQ • . 112 5.43 EXPRESSION EVALUATION . 113 CHAPTER 6 - ZDOS •• • . 114 6.0 ZDOS OPERATION 114 6.1 INITIALIZE 122 6.2 ASSIGN .•• • 123 6.3 OPEN 125 6.4 CLOSE • . 132 6.5 REWIND 134 6.6 READ BINARY • • 135 6.7 WRITE BINARY 137 6.8 WRITE CURRENT • 139 6.9 DELETE •• • . 140 - iv - 6.10 DELETE REMAINING RECORDS · · · · · 142 6.11 ERASE . · · · · · · · · · · · 143 6.12 READ AND DELETE · · · · · · 145 6.13 READ CURRENT · · · · · · · · · 147 6.14 READ PREVIOUS · · · · · · · 149 6.15 READ DIRECT · · · · · · · · · · · · 151 6.16 SKIP FORWARD · · · · · · · · · · · · · 153 6.17 SKIP BACKWARD · · · · · · · · · 155 6.18 SKIP TO END · · · · · · · · · · · · 157 6.19 RENAME · · · · · · · · 158 6.20 UPDATE . · · · · · · · · · · · 160 6.21 SET ATTRIBUTES · · · · 162 6.22 QUERY ATTRIBUTES · · · · · · · · · 164 CHAPTER 7 - DFS · · · · · · · · · · · · · 166 7.1 ZILOG DISK CONTROLLER · · · · · · · · · 166 7.2 DFS OPERATION · · · · · · · · · · · 168 7.3 SOFTWARE ORGANIZATION · · · · · · · 171 7.4 DFS ALLOCATION · · · · · · · · · · · 172 7.4.1 Sector 0 Format 172 7.4.2 DFS Allocation Algorithm· · · · · 173 7.5 THE BARE DISK CONTROLLER • • • • · ,174 7.6 CONTROLLER BOOTSTRAP OPERATION. • . 177 7.7 SYSTEM BOOTSTRAPPING on the MCZ-1/35 179 - v - APPENDICES APPENDIX A - RIO/ZDOS/DFS Error Codes APPENDIX B - RIO Command Syntax Summary APPENDIX C - RIO System Constants APPENDIX D - Converting Files to RIO Format APPENDIX E - Altering Default RIO APPENDIX F - I/O Request Vector Format and I/O Request Codes APPENDIX G - Program Examples APPENDIX H - Internal Command Table Contents APPENDIX I - RIO Memory Manager APPENDIX J - Descriptor Record of Procedure Type File APPENDIX K - ZDOS/DFS Command Summary - vi - PREFACE This manual provides an introduction and user's manual for the RIO operating system used with Zilog's Micro (ZDS). Detailed description is provided for system features, including the bootstrap process, the RIO Executive, default console drivers, I/O structure, program interface, and the Zilog Floppy Disk File System, ZDOS, and the Zilog Hard Disk File System, DFS. Other pertinent documentation with which the reader may want to become familiar includes: zaO-MCZ PROM User's Manual zaO-ZDS PROM User's Manual zaO-RIO Relocating Assembler and Linker User's Manual zaO-RIO Text Editor User's Manual This manual makes use of the following conventions of notation: Optional portions of a modifier are enclosed in brackets, []. The symbol for logical or, 'I " is used if either option can be issued. STATUS [0 I 1 ••• 7] means the command can be issued as STATUS 0, STATUS 1, .•• STATUS 7, or simply as STATUS. Parameters which can be repeated zero or more times are enclosed in parentheses and followed by an asterisk - e.g., (filename)*. Parameters which can be repeated as necessary but must appear at least once are enclosed in parentheses and followed by a plus sign - e.g., (filename)+. - vii - All memory addresses and constants referring to memory allocation are given in hexadecimal. Unless so specified, other constants are given in decimal. Hexadecimal constants are also indicated by an 'H' immediately following the hex digits, e.g., 4FH. - viii - CHAPTER 1 INTRODUCTION AND OVERVIEW 1.1 INTRODUCTION The zao Operating System with Relocatable Modules and I/O Management, or RIO, is a general-purpose computing system designed to facilitate the development and integration of user's programs into a production environment. RIO is available on various Zilog hardware configurations including the zao Micro Computer System (MCZ-l) series and the zao Development System (ZDS). The zao Development System provides extensive hardware debugging aids to assist the engineer/programmer in ZaO-based hardware/software system design. The user has a choic~ between a modest environment with a minimum of system support or an enhanced environment which provides access to an assortment of system support utilities including the Zilog Floppy Disk File System, ZDOS, and the Zilog Hard Disk File System, DFS. In the modest environment, the user has access to 3K (lK=1024) bytes of dedicated read-only memory which contains a program debugger with file manipulation capability, a floppy disk driver which supports up to eight disk drives, and a basic console driver with provision for paper tape operation. In the enhanced environment, the user also has access to the RIO Executive, ZDOS, DFS, and a collection of disk-resident software including a text editor, macro assembler, and linker. The RIO Executive provides standardized I/O management permitting device independent program development and utilization of alternate or multiple file systems. ZDOS provides a versatile floppy disk based file system with variable record length files; up to 16 concurrently active files; management of user-defined scratch files which are automatically deallocated after use; and support of up to eight disk drives for over 2.5 megabytes of on-line storage. The hard disk file system, - 1 - DFS, supplies similar features on 10 megabyte high speed disks. The text editor, macro assembler and linker give the user full support in program development, minimizing assembly time with relocatable modules while allowing com­ plex memory overlay structures. In addition, a console driver is provided which allows user definition of character delete and line delete symbols, automatic insertion of any number of line feeds, and automatic echo mode to accommodate a wide r~nge of console devices. - 2 - 1.2 SYSTEM OVERVIEW 1.2.1 HARDWARE CONFIGURATION The RIO Operating System is designed to operate with the 4K PROM in either the Zilog Micro Computer System (MCZ) or Development System (ZDS). A minimum configuration of 32K (lK=1024) of random access memory, one disk drive, and a console device is required. The MCZ 1/20 Zilog Micro Computer System is equipped with two floppy disk drives. The left drive is designated drive '2' and the right drive is designated drive '0'. The Zilog Development System (ZDS) also has two drives, but the designations are 'I' and '0' for left and right, respectively. The MCZ 1/35 uses hard disk cartridge and fixed platter drives. The usual configuration consists of one fixed platter and one c?rtridge drive, designated '0' and 'I', respectively. The system will support up to 8 drives. 1.2.2 FILE SYSTEMS For systems using floppy disks, ZDOS controls the organization and allocation of the sectors on a diskette. While the basic unit of disk allocation is the sector, the fundamental structure within ZDOS is the 'file'. A file consists of zero or more sectors of data which contain logically-related information. Each file has a set of attributes including a name of from one to thirty-two characters, a set of (possibly null) properties, a type, a subtype, and a record length. The smallest amount of information that can be read from or written to the disk is the contents of one sector, but more efficient operation can often be achieved by grouping from one to thirty-two contiguous sectors (a complete track) into one unit which is then read or written together.
Recommended publications
  • IODF Explorer
    The Input/Output Definition File (IODF) is a critical Control Point in the management of the IBM z/Series Platform. IODF Explorer Release 4.0 USER GUIDE Contact us for additional information: NewEra Software Technical Support 800-421-5035 [email protected] www.newera.com Rev: 2009-04-24 IODF Explorer 4.0 ¾ Copyright, Trademark and Legal Notices Copyrights This Getting Started Guide and the related Software Product(s) are protected under a Copyright dated 2009 by NewEra Software, Inc. All rights are reserved. License Agreement This Getting Started Guide describes the installation and operation of Image FOCUS, its environment and applications. It is made available only under the terms of a license agreement between the licensee and NewEra Software Inc. No part of this Guide or the related Software Product(s) may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose, without the express written permission of NewEra Software, Inc. Trademarks and Copyrights of Others The following products and/or registered trademarks of International Business Machines Corporation are referenced in this document: MVS, VM, RACF, z/OS, SYSPLEX, JES, VTAM, TSO, ISPF, ICKDSF, DFSMSdss, DF/DSS, and others. 2 NewEra Software, Inc. ‐ Image Control Environment (ICE) Applications IODF Explorer 4.0 ¾ Technical Support Information NewEra Software is dedicated to providing the highest level of technical Around-the-clock- support support to meet our customers’ growing needs. In order to meet these needs, NewEra provides around‐the‐clock technical support, 7 days a week, 24 hours a day.
    [Show full text]
  • Hardware Configuration Definition User's Guide
    z/OS Version 2 Release 3 Hardware Configuration Definition User's Guide IBM SC34-2669-30 Note Before using this information and the product it supports, read the information in “Notices” on page 443. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-02-16 © Copyright International Business Machines Corporation 1994, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures..................................................................................................... xiii List of Tables.....................................................................................................xxiii About this document.......................................................................................... xxv Who this document is for..........................................................................................................................xxv Related information.................................................................................................................................. xxv How to use this document.......................................................................................................................xxvi How this document is organized............................................................................................................. xxvi How to read syntax diagrams................................................................................................................
    [Show full text]
  • Avaya Call Management System Software Installation, Maintenance, and Troubleshooting for Linux®
    Avaya Call Management System Software Installation, Maintenance, and Troubleshooting for Linux® Release 18.0.2 February 2018 © 2018 Avaya Inc. All Rights Reserved. CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE Notice SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR While reasonable efforts have been made to ensure that the information in this USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON document is complete and accurate at the time of printing, Avaya assumes no BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE liability for any errors. Avaya reserves the right to make changes and INSTALLING, DOWNLOADING OR USING THE SOFTWARE corrections to the information in this document without the obligation to notify (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END any person or organization of such changes. USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE Documentation disclaimer APPLICABLE AVAYA AFFILIATE ("AVAYA"). "Documentation" means information published in varying mediums which may Avaya grants You a license within the scope of the license types described include product information, operating instructions and performance below, with the exception of Heritage Nortel Software, for which the scope of specifications that are generally made available to users of products. the license is detailed below. Where the order documentation does not Documentation does not include marketing materials. Avaya shall not be expressly identify a license type, the applicable license will be a Designated responsible for any modifications, additions, or deletions to the original System License.
    [Show full text]
  • Bash Scripts #4 Input/Output + Oneliners
    Bash Scripts #4 Input/Output + Oneliners By: Deepayan Patra & Sam Yong (Pixel) Pet Tax Sam’s doggo Yoshi How to Become a Bash Expert Bash as a full-fledged scripting language STEP 3 Bash as a data STEP 2 processing language Learn to browse files and run programs STEP 1 01 03 Unix Process Communication More Scripting Everything is a file! How to use pipes and more to stream info! 02 04 Scripting w. I/O Redirect Oneliners How programs talk to each other! One line programs to make Bash so easy! 01. Unix Process Comm. (it’s I/Opening) Unix as a 2-layered API ● C functions ○ for “real” system programming ● Shell commands ○ subset of C functionality ○ for scripting and interactive use Unix as a 2-layered API ● C functions (15-213) ○ for “real” system programming ● Shell commands (GPI) ○ subset of C functionality ○ for scripting and interactive use Unix process interacts with the world ● stdin ● stdout ● args ● stderr ● env Process ● exitcode ● fs ● fs ● network ● network We can script some of these ● stdin ● stdout ● args ● stderr ● env Process ● exitcode ● fs ● fs ● network ● network Input & Output (streams) ● stdin - standard input (file descriptor = 0) ○ raw_input, scanf ● stdout - standard output (file descriptor = 1) ○ print, printf ● stderr - standard error (file descriptor = 2) ○ fprint(stderr) Arguments ● args - command line arguments ● Scripts can access arguments with ○ $# = number of arguments given to the script (different from “argc” in C, which includes program name) ○ $1 = first argument, $2 = second argument, … ● e.g. $ echo Hello World ○ $# = 2 ○ $1 = Hello ○ $2 = World ○ $0 = echo DEMO Environment Variables ● A list of key-value pairs DEMO ● Essentially the shell’s global variables ● Any program can use these variables ○ Access a VAR by $VAR ● printenv - prints currently set environment variables Exit Code ● All programs exit with some code ● This is determined by the programmer ● In general, exit 0 means success ● Anything else indicates some error/failure ● Process can access last executed program’s exit code DEMO 02.
    [Show full text]
  • Dell EMC SC Series Best Practices with Vmware Vsphere 5.X–6.X
    Best Practices Dell EMC SC Series: Best Practices with VMware vSphere Abstract This document provides best practices for integrating VMware® vSphere® 5.x- 7.x hosts with Dell EMC™ SC Series storage. May 2021 2060-M-BP-V Revisions Revisions Date Description July 2016 Initial release: Combined vSphere 5.x and 6.x best practice documents, added SCOS 7.1 updates September 2016 Minor revisions and corrections October 2016 Changed Disk.AutoremoveOnPDL to reflect current VMware guidance January 2017 Updated for vSphere 6.5 changes; added appendix D summarizing all host settings February 2017 Updated Linux guest disk timeout recommendations in section 4.7.2 April 2017 Updated iSCSI login timeout recommendation July 2017 Updated SAS driver info in 4.2.3, Added auto UNMAP requirements in 16.3.5 April 2018 Updated to provide vSphere 6.7 guidance October 2018 Minor revisions and corrections December 2018 Added SAS front-end lsi_msgpt3 module parameter recommendation in 4.2.3 March 2019 Modified SATP claim rules in section 6.9.1 and appendix D July 2019 Minor revisions and corrections (VMFS3.EnableBlockDelete=1) September 2019 Claim rule syntax corrections April 2020 vSphere 7.0 additions December 2020 Minor clarifications January 2021 Esxcli command syntax change for DelayedAck in appendix D.1 May 2021 Updated section 4.2.3 with additional KB articles for SAS FE connectivity Acknowledgments Author: Darin Schmitz The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.
    [Show full text]
  • Developing Programs Using the Hardware Abstraction Layer, Nios II
    6. Developing Programs Using the Hardware Abstraction Layer January 2014 NII52004-13.1.0 NII52004-13.1.0 This chapter discusses how to develop embedded programs for the Nios® II embedded processor based on the Altera® hardware abstraction layer (HAL). This chapter contains the following sections: ■ “The Nios II Embedded Project Structure” on page 6–2 ■ “The system.h System Description File” on page 6–4 ■ “Data Widths and the HAL Type Definitions” on page 6–5 ■ “UNIX-Style Interface” on page 6–5 ■ “File System” on page 6–6 ■ “Using Character-Mode Devices” on page 6–8 ■ “Using File Subsystems” on page 6–15 ■ “Using Timer Devices” on page 6–16 ■ “Using Flash Devices” on page 6–19 ■ “Using DMA Devices” on page 6–25 ■ “Using Interrupt Controllers” on page 6–30 ■ “Reducing Code Footprint in Embedded Systems” on page 6–30 ■ “Boot Sequence and Entry Point” on page 6–37 ■ “Memory Usage” on page 6–39 ■ “Working with HAL Source Files” on page 6–44 The application program interface (API) for HAL-based systems is readily accessible to software developers who are new to the Nios II processor. Programs based on the HAL use the ANSI C standard library functions and runtime environment, and access hardware resources with the HAL API’s generic device models. The HAL API largely conforms to the familiar ANSI C standard library functions, though the ANSI C standard library is separate from the HAL. The close integration of the ANSI C standard library and the HAL makes it possible to develop useful programs that never call the HAL functions directly.
    [Show full text]
  • Montezuma Micro CP/M*
    SYSTEM PROGRAMMER'S GUIDE for the TRS-80 Model 4/4P using Montezuma Micro CP/M* 2.2 \ZcfV t?roHJIc 1*01 stTil O<£i***JL Oir 4 TABLE OF CONTENTS 1. INTRODUCTION 1 2. THE SYSTEM PARAMETER BLOCK 3 3. I/O USING THE IOBYTE ..5 4. THE KEYBOARD DRIVER 9 5. THE VIDEO DISPLAY DRIVER .....11 6. THE PARALLEL PRINTER DRIVER 13 7. THE SERIAL PORT DRIVER 16 8. THE MEMORY DISK DRIVE 17 9. DISK I/O 19 9.1. The Floppy Disk Driver 19 9.2. DPB Extensions 19 9.3. DCB Definitions . 21 9.4. Using the Disk Driver 22 9.5. EXBIOS - Extending the BIOS 23 9.6. The Hard Disk Driver 23 10. CP/M BOOTS 25 10.1. The Cold Boot 25 10.2. The Warm Boot 25 11. PITFALLS AND TRAPS .27 11.1. INTERRUPTS : 27 11.2. FEATURES UNIQUE TO THE Z80 27 11.3. RAM USAGE 28 12. INDEX 29 13. THE LISTING 31 Montezuma Micro CP/M" System Programmer's Manual 1. INTRODUCTION All of the information in this manual is copyrighted by Montezuma Micro, including the source code listings. The purpose of this manual is to provide you with the information necessary to modify the BIOS of your own copy of CP/M". Much like the service manual for a car, this document will show you how the BIOS works, and how you can use your own options with it. It will NOT teach you how to use CP/M and it will NOT teach you how to write assembly language programs for use with CP/ M.
    [Show full text]
  • Linux Tape Backup with Mt and Tar Command Howto by VIVEK GITE on APRIL 19, 2006 · 30 COMMENTS · Last Updated at JUNE 3, 2009
    Linux Tape Backup With mt And tar Command Howto by VIVEK GITE on APRIL 19, 2006 · 30 COMMENTS · last updated at JUNE 3, 2009 Magnetic tape is a non-volatile storage medium consisting of a magnetic coating on a thin plastic strip. Nearly all recording tape is of this type, whether used for video, audio storage or general purpose digital data storage using a computer. How do I make backup using tapes under Linux operating systems? Linux (and other Unixish system) use mt command to control magnetic tape drive operation. You need to use mt command while working with tape drive. It allows you to reading and writing to tape. The default tape drive under Linux is /dev/st0 (first SCSI tape device name). You can read more about tape drives naming convention used under Linux here. Following paragraph summaries command you need to use control tape drive for backup/restore purpose. Rewind tape drive:# mt -f /dev/st0 rewindBackup directory /www and /home with tar command (z - compressed):# tar -czf /dev/st0 /www /homeFind out what block you are at with mt command:# mt -f /dev/st0 tellDisplay list of files on tape drive:# tar -tzf /dev/st0Restore /www directory:# cd / # mt -f /dev/st0 rewind # tar -xzf /dev/st0 wwwUnload the tape:# mt -f /dev/st0 offlineDisplay status information about the tape unit:# mt -f /dev/st0 statusErase the tape:# mt -f /dev/st0 eraseYou can go BACKWARD or FORWARD on tape with mt command itself: (a) Go to end of data:# mt -f /dev/nst0 eod(b) Goto previous record:# mt -f /dev/nst0 bsfm 1(c) Forward record:# mt -f /dev/nst0 fsf 1Replace /dev/st0 with your actual tape drive name.
    [Show full text]
  • Gl615 Linux for Unix Administrators Rhel7 Sles12
    EVALUATION COPY Unauthorized Reproduction or Distribution Linux for Unix AdministratorsProhibited Student Workbook EVALUATION COPY Unauthorized Reproduction GL615 LINUX FOR UNIX ADMINISTRATORS RHEL7 SLES12 or Distribution The contents of this course and all its modules and related materials, including handouts to audience members, are copyright ©2017 Guru Labs L.C. No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including, but not limited to, photocopy, photograph, magnetic, electronic or other record, without the prior written permission of Guru Labs. This curriculum contains proprietary information which is for the exclusive use of customers of Guru Labs L.C., and is not to be shared with personnel other than those in attendance at this course. This instructional program, including all material provided herein, is supplied without any guarantees from Guru Labs L.C. Guru Labs L.C. assumes no liability for damages or legal action arising from Prohibited the use or misuse of contents or details contained herein. Photocopying any part of this manual without prior written consent of Guru Labs L.C. is a violation of federal law. This manual should not appear to be a photocopy. If you believe that Guru Labs training materials are being photocopied without permission, please email [email protected] or call 1-801-298-5227. Guru Labs L.C. accepts no liability for any claims, demands, losses, damages, costs or expenses suffered or incurred howsoever arising from or in connection with the
    [Show full text]
  • Appendix A. Caché Objectscript Reference
    Appendix A. Caché ObjectScript Reference Commands Command Description Break[:cond] Interrupt execution of the current routine for debugging purposes. Break[:cond] [status] Activate or deactivate user interrupts. Close[:cond] device[:parameter] Close the device, make it available again for other users and, possibly, set the device characteristics. CONTINUE[:cond] End the current execution of the code block of a For, WHILE, or Do/WHILE loop and check the condition to determine whether a further iteration follows. Do[:cond] Invoke a subroutine or code block and continue the Do[:cond] {…} WHILE expression program processing with the next command after com- pletion. Do[:cond] entryref[(parameter)] Invoke a subroutine, pass the optional parameter and [:cond] continue the program processing with the next com- mand after completion. Else Execute the following commands only if the value of $Test is 0. Else {…} Execute the following code block only if none of the preceding If and ElseIf conditions were true. ElseIf expression {…} Execute the following command block only if none of the preceding If and ElseIf conditions were true and expres- sion is true. For Execute the remainder of the line or the following code For {…} block until a Quit or Goto command ends the loop. For variable=expression[,...] Repeat the execution of the following commands in the For variable=expression[,...] {…} routine line or the following code block for different For variable=start:increment:[end] values of a local variable. For variable=start:increment:[end] {…} Goto[:cond] Resume the normal execution of a routine that was interrupted with the Break command. Goto[:cond] location[:cond] Continue the program execution at another line or in another routine.
    [Show full text]
  • Maintaining and Troubleshooting Avaya Call Management System
    Maintaining and Troubleshooting Avaya Call Management System Release 19.0 Issue 1 June 2019 © 2019 Avaya Inc. OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT All Rights Reserved. EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA Notice CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL While reasonable efforts have been made to ensure that the information in this ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE document is complete and accurate at the time of printing, Avaya assumes no SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR liability for any errors. Avaya reserves the right to make changes and USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON corrections to the information in this document without the obligation to notify BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE any person or organization of such changes. INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END Documentation disclaimer USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A "Documentation" means information published in varying mediums which may BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE include product information, operating instructions and performance APPLICABLE AVAYA AFFILIATE ("AVAYA"). specifications that are generally made available to users of products. Avaya grants You a license within the scope of the license types described Documentation does not include marketing materials. Avaya shall not be below, with the exception of Heritage Nortel Software, for which the scope of responsible for any modifications, additions, or deletions to the original the license is detailed below.
    [Show full text]
  • Unix Large File Processing Secrets .DUVWHQ 6HOI 30 6TXDUHG ,QF 6DQ )UDQFLVFR &$
    Unix Large File Processing Secrets .DUVWHQ 6HOI 30 6TXDUHG ,QF 6DQ )UDQFLVFR &$ ABSTRACT To most SAS programmers working in the UNIX environment, large file processing is synonymous with the historical maximum file size limit of 2 gigabytes. Though this is a significant concern, there are additional dimensions to managing and working with large quantities of data. Large file processing is any job large enough that you think twice before typing submit. The term is applied here to any situation where a task is constrained by physical resources, including: system file size limits, system storage or workspace limits, total processing time, CPU availability, and process contention with other users. The weapons which can be applied to these are programmer time and skill. Ultimately, pushing the limits of the envelope is a question of balancing these factors. This paper identifies several techniques for large file processing on Unix, including: • Recent SAS and OS large file support enhancements. • Efficiency techniques. • Sorting data. • Working to and from tape • Advanced data coding methods of the world still focuses on measuring inputs, and not product. Think about your program and what you need out of it. Figure LARGE FILE SUPPORT out, within reason, the best way to accomplish this. Remember SAS and OS Enhancements that there are usually several equivalent methods available. The Unix maximum file size limit exists because of the limited After a reasonable enhancement in program efficiency has been file addressing space allowed by a 32 bit integer. Methods for achieved, it’s generally best to forego further improvements. overcoming this limit are described in Tom Truscott’s 1996 Remember: efficiency improvements only go so far.
    [Show full text]