DOCSLIB.ORG

Mainframe Migration and Upgrade Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mainframe Migration and Upgrade Guide Mainframe Migration and Upgrade Guide Version 6.0, November 2003 IONA, IONA Technologies, the IONA logo, Orbix, Orbix/E, Orbacus, Artix, Orchestrator, Mobile Orchestrator, Enterprise Integrator, Adaptive Runtime Technology, Transparent Enterprise Deployment, and Total Business Integration are trademarks or registered trademarks of IONA Technologies PLC and/or its subsidiaries. Java and J2EE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CORBA is a trademark or registered trademark of the Object Management Group, Inc. in the United States and other countries. All other trademarks that appear herein are the property of their respective owners. While the information in this publication is believed to be accurate, IONA Technologies PLC makes no warranty of any kind to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. IONA Technologies PLC shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the furnishing, performance or use of this material. COPYRIGHT NOTICE No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photocopying, recording or otherwise, without prior written consent of IONA Technologies PLC. No third party intellectual property right liability is assumed with respect to the use of the information contained herein. IONA Technologies PLC assumes no responsibility for errors or omissions contained in this book. This publication and features described herein are subject to change without notice. Copyright © 2001, 2003 IONA Technologies PLC. All rights reserved. All products or services mentioned in this manual are covered by the trademarks, service marks, or product names as designated by the companies who market those products. Updated: 27-May-2004 M3169 Contents List of Tables vii Preface ix Part 1 Migrating from 2.3.x Chapter 1 Introduction 3 Overview 4 C++ Applications 5 COBOL and PL/I Applications 6 Chapter 2 Upgrading from an Orbix 2.3.x-Based Solution 9 Chapter 3 C++ Migration Issues 13 C++ Client Migration 14 CORBA Object Location and Binding 15 Naming Service 16 Object-String Conversion 18 resolve_initial_references() 19 Client-Side CORBA Compliancy 20 Callback Objects 22 Orbix-Specific APIs 23 CORBA::Environment Parameter 24 Dynamic Invocation Interface (DII) 25 C++ Server Migration 26 BOA to POA Migration 27 Activation Modes 29 Object/Servant Lifecycles 30 Creating Object References Without Servants 32 Orbix Filters and CORBA 2.3 Alternatives 33 Connection Management 36 iii CONTENTS Exception-Safe Servant Implementations 38 Opaques 39 Orbix 6.x IDL Compiler Output 40 Chapter 4 COBOL Migration Issues 41 Name Mapping Issues 43 Fully Qualified Level 01 Data Names 44 Operation and Level 88 Data Names 48 IDL Constant Definitions Mapped to Fully Qualified Names 52 Derived Interface Names and Fully Qualified Names 57 Numeric Suffixes for Data Names 60 160-Character Limit for String Literals 61 Maximum Length of COBOL Data Names 66 Copybook Names Based on IDL Member Name 69 Introduction to IDL Member Name Migration Issues 70 IDL Member Name Different from its Interface Names 72 More than One Interface in an IDL Member 74 Length of IDL Member Names 76 Name Scoping and the COBOL Compilers 77 Same Container Name Used More than Once 78 Same Fieldname Used More than Once 85 Typecode Name and Length Identifiers 87 Comparing Compiler Output 88 IDL Member Name Different from its Interface Name 89 More than One Interface in an IDL Member 92 Reserved COBOL and OMG Keywords 96 Reserved COBOL Keywords for Module or Interface Names 97 Use of Result as an Argument Name in IDL 98 OMG Mapping Standard for Unions and Exceptions 100 Error Checking and Exceptions 102 COBOL-Specific Issue Relating to Error Checking 103 Error Checking Generation at Runtime for Batch Servers 105 Nested Unions in IDL 106 Mapping for Arrays 111 Working Storage data Items and Group Moves 113 Mapping for IDL type Any 115 CORBA Copybook Additions 117 Parameter Passing of Object References in IDL Operations 118 iv CONTENTS CORBA Object Location and Binding 119 Migration Overview and Example 120 The Naming Service 122 Object-String Conversion 124 API Migration Issues 125 Deprecated APIs 126 ORBEXEC and USER Exception parameters 127 ORBSTAT 128 ORBALLOC 129 COBOL IMS Server Migration Issues 131 Server Mainline Program Requirement for IMS Servers 132 The Linkage Section for IMS Servers 136 Access to the Program Communication Block for IMS Servers 142 Error Checking Generation at Runtime for IMS Servers 145 COBOL IMS Client Migration Issues 146 The Linkage Section for IMS Clients 147 Error Checking Generation at Runtime for IMS Clients 149 Extra Copybooks in Orbix 6.x for IMS Clients 150 COBOL CICS Server Migration Issues 152 Server Mainline Program Requirement for CICS Servers 153 Access to the EXEC Interface Block Data Structure 158 Error Checking Generation at Runtime for CICS Servers 159 COBOL CICS Client Migration Issues 160 Error Checking Generation at Runtime for CICS Clients 161 Extra Copybooks in Orbix Mainframe 6.x 162 Miscellaneous 163 Chapter 5 PL/I Migration Issues 165 Fully Qualified Level 1 Data Names 167 Maximum Length of PL/I Data Names 170 IDL Constant Definitions Mapped to Fully Qualified Names 174 Typecode Name and Length Identifiers 177 Include Member names Based on the IDL Member name 178 IDL Member names Different from Interface Names 181 More than One Interface in an IDL Member 183 Reserved PL/I Keywords for Module or Interface Names 185 Orbix PL/I Error Checking 186 v CONTENTS CORBA Object Location and Binding 187 Migration Overview and Example 188 Naming Service 190 Object-String Conversion 192 CORBA Include Member Additions 193 API Migration Issues 194 Deprecated APIs 195 PODSTAT in Orbix 6.x 196 PODEXEC and User Exception parameters 197 Server Accessor (Z Member) 198 PL/I IMS Server Migration Issues 204 Server Mainline Module 205 Access to the Program Communication Block 210 PL/I IMS Client Migration issues 212 Program Communication Block Definitions Modifications 213 DLIDATA Include Member Modifications 216 Error Checking Generation at Runtime for IMS Clients 217 PL/I CICS Server Migration Issues 218 Server Mainline Program Requirements for CICS Servers 219 Access to the EXEC Interface Block Data Structure 224 PL/I CICS Client Migration Issues 225 Miscellaneous 226 Chapter 6 Common Migration Issues 227 IDL Fixed Type Definitions 228 IDL Defined in Fixed Block Data Sets 229 Administrative Tools 230 Diagnostic Output 232 Use of the Orbix Protocol 234 imsraw and cicsraw IDL changes 235 vi CONTENTS Part 2 Migrating from 5.x Chapter 7 Upgrading from Mainframe Edition 5.x 239 Chapter 8 Orbix Mainframe Configuration 243 Index 249 vii CONTENTS viii List of Tables Table 1: Migration Possibilities for OS/390 4 Table 2: POA Policy Types and Their Values for Callback Objects 22 Table 3: C++ Compiler Output Comparison for OS/390 USS 40 Table 4: COBOL Compiler Output for IDL Constant Definitions 52 Table 5: COBOL Compiler Output for GRID IDL Member 75 Table 6: COBOL Mapping Changes for IDL Data Types 113 Table 7: Deprecated COBOL APIs and Their Replacements 126 Table 8: ORBALLOC and Mapping Changes for IDL Data Types 129 Table 9: Extra Copybooks that ship with Orbix 6.x 150 Table 10: Extra Copybooks that ship with Orbix 6.x 162 Table 11: PL/I Compiler Output for IDL Constant Definitions 174 Table 12: PL/I Compiler Output Comparison GRID Include Member Names 181 Table 13: PL/I Compiler Deprecated IDL Generated Members and Their Replacements 184 Table 14: Deprecated PL/I APIs and Their Replacements 195 vii LIST OF TABLES viii Preface Overview This guide describes the issues that surround the migration of Orbix for OS/390 applications from earlier IONA mainframe solutions to an Orbix Mainframe 6.x solution. The bulk of this guide (Part 1) focuses on migrating from Orbix 2.3.x-based solutions, because much fewer changes are required to migrate from Orbix E2A Mainframe Edition 5.x. Part 2 describes Orbix E2A Mainframe Edition 5.x migration issues. This guide describes migration issues relating specifically to COBOL and PL/I applications in a native OS/390 environment, and to C++ applications in both a native OS/390 and UNIX System Services environment. Support If you need help with this or any other IONA products, contact IONA at [email protected]. Comments on IONA documentation can be sent to [email protected]. Audience This guide is intended for application programmers who want to migrate their Orbix for OS/390 applications from earlier IONA mainframe solutions to an Orbix Mainframe 6.x solution. It is assumed that the reader is familiar with the basic concepts of CORBA 2.3. Related Documentation Orbix Mainframe 6.0 documentation includes the following related guides: • CORBA Programmer’s Guide, C++ • CORBA Programmer’s Reference, C++ • COBOL Programmer’s Guide and Reference • PL/I Programmer’s Guide and Reference ix PREFACE • CORBA Administrator’s Guide • IMS Adapters Administrator’s Guide • CICS Adapters Administrator’s Guide • Mainframe CORBA Concepts Guide • Mainframe Security Guide • Mainframe Management Guide For the latest version of all IONA product documentation, see the IONA web site at: http://www.iona.com/support/docs Organization of this Guide This guide is divided into two main parts as follows: Part 1, “Migrating from 2.3.x” Chapter 1, “Introduction” This chapter introduces the main differences between the Orbix 2.3.x-based IONA mainframe solutions and Orbix Mainframe 6.x. It also summarizes the main migration impact involved. Chapter 2, “Upgrading from an Orbix 2.3.x-Based Solution” This chapter outlines the requirements for upgrading from an Orbix 2.3.x-based IONA mainframe solution to Orbix Mainframe 6.x.
Load more

Recommended publications
  • MANNING Greenwich (74° W
    Object Oriented Perl Object Oriented Perl DAMIAN CONWAY MANNING Greenwich (74° w. long.) For electronic browsing and ordering of this and other Manning books, visit http://www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact: Special Sales Department Manning Publications Co. 32 Lafayette Place Fax: (203) 661-9018 Greenwich, CT 06830 email: [email protected] ©2000 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Library of Congress Cataloging-in-Publication Data Conway, Damian, 1964- Object oriented Perl / Damian Conway. p. cm. includes bibliographical references. ISBN 1-884777-79-1 (alk. paper) 1. Object-oriented programming (Computer science) 2. Perl (Computer program language) I. Title. QA76.64.C639 1999 005.13'3--dc21 99-27793 CIP Manning Publications Co. Copyeditor: Adrianne Harun 32 Lafayette
    [Show full text]
  • Java/Java Packages.Htm Copyright © Tutorialspoint.Com
    JJAAVVAA -- PPAACCKKAAGGEESS http://www.tutorialspoint.com/java/java_packages.htm Copyright © tutorialspoint.com Packages are used in Java in order to prevent naming conflicts, to control access, to make searching/locating and usage of classes, interfaces, enumerations and annotations easier, etc. A Package can be defined as a grouping of related types classes, interfaces, enumerationsandannotations providing access protection and name space management. Some of the existing packages in Java are:: java.lang - bundles the fundamental classes java.io - classes for input , output functions are bundled in this package Programmers can define their own packages to bundle group of classes/interfaces, etc. It is a good practice to group related classes implemented by you so that a programmer can easily determine that the classes, interfaces, enumerations, annotations are related. Since the package creates a new namespace there won't be any name conflicts with names in other packages. Using packages, it is easier to provide access control and it is also easier to locate the related classes. Creating a package: While creating a package, you should choose a name for the package and include a package statement along with that name at the top of every source file that contains the classes, interfaces, enumerations, and annotation types that you want to include in the package. The package statement should be the first line in the source file. There can be only one package statement in each source file, and it applies to all types in the file. If a package statement is not used then the class, interfaces, enumerations, and annotation types will be placed in the current default package.
    [Show full text]
  • Quick Start Guide for Java Version 5.0
    Quick Start Guide for Java Version 5.0 Copyright © 2020 Twin Oaks Computing, Inc. Castle Rock, CO 80104 All Rights Reserved Welcome CoreDX DDS Quick Start Guide for Java Version 5.0 Nov 2020 Welcome to CoreDX DDS, a high-performance implementation of the OMG Data Distribution Service (DDS) standard. The CoreDX DDS Publish-Subscribe messaging infrastructure provides high-throughput, low-latency data communications. This Quick Start will guide you through the basic installation of CoreDX DDS, including installation and compiling and running an example Java application. You will learn how easy it is to integrate CoreDX DDS into an application. This Quick Start Guide is tailored for Java applications, and the examples differ slightly for other languages. Installation First things first: get CoreDX DDS onto your development system! Here’s what you need to do: 1. Once you have obtained CoreDX DDS from Twin Oaks Computing (or from the Eval CD), unpack the appropriate distribution for your machine somewhere on your system. We’ll refer to this directory throughout this guide as COREDX_HOME. For example, on a UNIX system this command will extract the distribution into the current directory: gunzip –c coredx-5.0.0-Linux_2.6_x86_64_gcc5-Release.tgz | tar xf – CoreDX DDS is available for multiple platform architectures, and multiple platform architectures of CoreDX DDS can be installed in the same top level (COREDX_TOP) directory. The directory structure under COREDX_TOP will look like: 2. If you are using an evaluation copy of CoreDX DDS, follow the instructions you received when you downloaded the software to obtain an evaluation license.
    [Show full text]
  • Importance of DNS Suffixes and Netbios
    Importance of DNS Suffixes and NetBIOS Priasoft DNS Suffixes? What are DNS Suffixes, and why are they important? DNS Suffixes are text that are appended to a host name in order to query DNS for an IP address. DNS works by use of “Domains”, equitable to namespaces and usually are a textual value that may or may not be “dotted” with other domains. “Support.microsoft.com” could be considers a domain or namespace for which there are likely many web servers that can respond to requests to that domain. There could be a server named SUPREDWA.support.microsoft.com, for example. The DNS suffix in this case is the domain “support.microsoft.com”. When an IP address is needed for a host name, DNS can only respond based on hosts that it knows about based on domains. DNS does not currently employ a “null” domain that can contain just server names. As such, if the IP address of a server named “Server1” is needed, more detail must be added to that name before querying DNS. A suffix can be appended to that name so that the DNS sever can look at the records of the domain, looking for “Server1”. A client host can be configured with multiple DNS suffixes so that there is a “best chance” of discovery for a host name. NetBIOS? NetBIOS is an older Microsoft technology from a time before popularity of DNS. WINS, for those who remember, was the Microsoft service that kept a table of names (NetBIOS names) for which IP address info could be returned.
    [Show full text]
  • Bigraphical Domain-Specific Language (BDSL): User Manual BDSL Version: V1.0-SNAPSHOT
    >_ Interpreter CLI BDSL BDSL User Manual BDSL v1.0-SNAPSHOT 1 Bigraphical Domain-specific Language (BDSL): User Manual BDSL Version: v1.0-SNAPSHOT Dominik Grzelak∗ Software Technology Group Technische Universit¨at Dresden, Germany Abstract This report describes Bigraphical DSL (BDSL), a domain-specific language for reactive systems, rooted in the mathematical spirit of the bigraph theory devised by Robin Milner. BDSL is not only a platform-agnostic programming language but also a development framework for reactive applications, written in the Java program- ming language, with a focus on stability and interoperability. The report serves as a user manual mainly elaborating on how to write and execute BDSL programs, further covering several features such as how to incorporate program verification. Moreover, the manual procures some best practices on design patterns in form of code listings. The BDSL development framework comes with a ready- to-use interpreter and may be a helpful research tool to experiment with the underlying bigraph theory. The framework is further in- tended for building reactive applications and systems based on the theory of bigraphical reactive systems. This report is ought to be a supplement to the explanation on the website www.bigraphs.org. The focus in this report lies in the basic usage of the command-line interpreter and mainly refers to the features available for the end-user, thus, providing a guidance for taking the first steps. It does not cover programmatic implementation details in great detail of the whole BDSL Interpreter Framework that is more suited to developers. Acknowledgment This research project is funded by the German Research Foundation (DFG, Deutsche Forschungsgemeinschaft) as part of Germany's Excel- lence Strategy { EXC 2050/1 { Project ID 390696704 { Cluster of Ex- cellence "Centre for Tactile Internet with Human-in-the-Loop" (CeTI) of Technische Universit¨at Dresden.
    [Show full text]
  • Java: Odds and Ends
    Computer Science 225 Advanced Programming Siena College Spring 2020 Topic Notes: More Java: Odds and Ends This final set of topic notes gathers together various odds and ends about Java that we did not get to earlier. Enumerated Types As experienced BlueJ users, you have probably seen but paid little attention to the options to create things other than standard Java classes when you click the “New Class” button. One of those options is to create an enum, which is an enumerated type in Java. If you choose it, and create one of these things using the name AnEnum, the initial code you would see looks like this: /** * Enumeration class AnEnum - write a description of the enum class here * * @author (your name here) * @version (version number or date here) */ public enum AnEnum { MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY } So we see here there’s something else besides a class, abstract class, or interface that we can put into a Java file: an enum. Its contents are very simple: just a list of identifiers, written in all caps like named constants. In this case, they represent the days of the week. If we include this file in our projects, we would be able to use the values AnEnum.MONDAY, AnEnum.TUESDAY, ... in our programs as values of type AnEnum. Maybe a better name would have been DayOfWeek.. Why do this? Well, we sometimes find ourselves defining a set of names for numbers to represent some set of related values. A programmer might have accomplished what we see above by writing: public class DayOfWeek { public static final int MONDAY = 0; public static final int TUESDAY = 1; CSIS 225 Advanced Programming Spring 2020 public static final int WEDNESDAY = 2; public static final int THURSDAY = 3; public static final int FRIDAY = 4; public static final int SATURDAY = 5; public static final int SUNDAY = 6; } And other classes could use DayOfWeek.MONDAY, DayOfWeek.TUESDAY, etc., but would have to store them in int variables.
    [Show full text]
  • Learning from Examples to Find Fully Qualified Names of API Elements In
    Learning from Examples to Find Fully Qualified Names of API Elements in Code Snippets C M Khaled Saifullah Muhammad Asaduzzaman† Chanchal K. Roy Department of Computer Science, University of Saskatchewan, Canada †School of Computing, Queen's University, Canada fkhaled.saifullah, [email protected] †[email protected] Abstract—Developers often reuse code snippets from online are difficult to compile and run. According to Horton and forums, such as Stack Overflow, to learn API usages of software Parnin [6] only 1% of the Java and C# code examples included frameworks or libraries. These code snippets often contain am- in the Stack Overflow posts are compilable. Yang et al. [7] biguous undeclared external references. Such external references make it difficult to learn and use those APIs correctly. In also report that less than 25% of Python code snippets in particular, reusing code snippets containing such ambiguous GitHub Gist are runnable. Resolving FQNs of API elements undeclared external references requires significant manual efforts can help to identify missing external references or declaration and expertise to resolve them. Manually resolving fully qualified statements. names (FQN) of API elements is a non-trivial task. In this paper, Prior studies link API elements in forum discussions to their we propose a novel context-sensitive technique, called COSTER, to resolve FQNs of API elements in such code snippets. The pro- documentation using Partial Program Analysis (PPA) [8], text posed technique collects locally specific source code elements as analysis [2], [9], and iterative deductive analysis [5]. All these well as globally related tokens as the context of FQNs, calculates techniques except Baker [5], need adequate documentation or likelihood scores, and builds an occurrence likelihood dictionary discussion in online forums.
    [Show full text]
  • Magic Tcl Tutorial #4: Simulation with IRSIM
    Magic Tcl Tutorial #4: Simulation with IRSIM R. Timothy Edwards Space Department Johns Hopkins University Applied Physics Laboratory Laurel, MD 20723 This tutorial corresponds to Tcl-based Magic version 7.2 Tutorials to read first: Magic Tutorial #1: Getting Started Magic Tutorial #2: Basic Painting and Selection Magic Tutorial #4: Cell Hierarchies Magic Tutorial #8: Circuit Extraction Magic Tutorial #11: Using IRSIM and RSIM with Magic Commands introduced in this tutorial: irsim , getnode, goto graphnode, watchnode, unwatchnode movenode, watchtime, unwatchtime, movetime (plus the standard IRSIM command set) Macros introduced in this tutorial: (None) 1 IRSIM Version 9.6 In version 9.6, IRSIM has been redesigned to work under the Tcl interpreter, in the same manner as Magic version 7.2 does. Like Magic version 7.2, section of Tcl as an interpreter is specified at compile-time, along with various use options. The “make” method has been rewritten to match the one which Magic uses, so IRSIM can be compiled and installed in a similar manner: make config make tcl make install-tcl –1– March22,2003 MagicTclTutorial#4:SimulationwithIRSIM Tcl-based IRSIM, like its non-interpreter version, can be run as a standalone product, and will simulate a circuit from a .sim format file. However, it is specifically designed to be operated in conjunction with magic, with methods for providing feedback directly into the layout from the simulation, and vice versa. There are a number of cross-application commands, detailed below, which belong to neither Magic or IRSIM, but are applicable when both are running in the Tcl interpreter at the same time.
    [Show full text]
  • Advanced Tcl E D
    PART II I I . A d v a n c Advanced Tcl e d T c l Part II describes advanced programming techniques that support sophisticated applications. The Tcl interfaces remain simple, so you can quickly construct pow- erful applications. Chapter 10 describes eval, which lets you create Tcl programs on the fly. There are tricks with using eval correctly, and a few rules of thumb to make your life easier. Chapter 11 describes regular expressions. This is the most powerful string processing facility in Tcl. This chapter includes a cookbook of useful regular expressions. Chapter 12 describes the library and package facility used to organize your code into reusable modules. Chapter 13 describes introspection and debugging. Introspection provides information about the state of the Tcl interpreter. Chapter 14 describes namespaces that partition the global scope for vari- ables and procedures. Namespaces help you structure large Tcl applications. Chapter 15 describes the features that support Internationalization, includ- ing Unicode, other character set encodings, and message catalogs. Chapter 16 describes event-driven I/O programming. This lets you run pro- cess pipelines in the background. It is also very useful with network socket pro- gramming, which is the topic of Chapter 17. Chapter 18 describes TclHttpd, a Web server built entirely in Tcl. You can build applications on top of TclHttpd, or integrate the server into existing appli- cations to give them a web interface. TclHttpd also supports regular Web sites. Chapter 19 describes Safe-Tcl and using multiple Tcl interpreters. You can create multiple Tcl interpreters for your application. If an interpreter is safe, then you can grant it restricted functionality.
    [Show full text]
  • Aras Innovator 12 Package Import Export Utilities
    Aras Innovator 12 Package Import Export Utilities Document #: 12.0.02019053801 Last Modified: 1/3/2020 Aras Innovator 12 Package Import Export Utilities Copyright Information Copyright © 2020 Aras Corporation. All Rights Reserved. Aras Corporation 100 Brickstone Square Suite 100 Andover, MA 01810 Phone: 978-806-9400 Fax: 978-794-9826 E-mail: [email protected] Website: https://www.aras.com Notice of Rights Copyright © 2020 by Aras Corporation. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. Aras Innovator, Aras, and the Aras Corp "A" logo are registered trademarks of Aras Corporation in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. Notice of Liability The information contained in this document is distributed on an "As Is" basis, without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non- infringement. Aras shall have no liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this document or by the software or hardware products described herein.
    [Show full text]
  • Magic Tcl Tutorial #4: Simulation with IRSIM
    Magic Tcl Tutorial #4: Simulation with IRSIM R. Timothy Edwards Space Department Johns Hopkins University Applied Physics Laboratory Laurel, MD 20723 This tutorial corresponds to Tcl-based Magic version 7.2 Tutorials to read first: Magic Tutorial #1: Getting Started Magic Tutorial #2: Basic Painting and Selection Magic Tutorial #4: Cell Hierarchies Magic Tutorial #8: Circuit Extraction Magic Tutorial #11: Using IRSIM and RSIM with Magic Commands introduced in this tutorial: irsim , getnode, goto graphnode, watchnode, unwatchnode movenode, watchtime, unwatchtime, movetime (plus the standard IRSIM command set) Macros introduced in this tutorial: (None) 1 IRSIM Version 9.6 In version 9.6, IRSIM has been redesigned to work under the Tcl interpreter, in the same manner as Magic version 7.2 does. Like Magic version 7.2, section of Tcl as an interpreter is specified at compile-time, along with various use options. The “make” method has been rewritten to match the one which Magic uses, so IRSIM can be compiled and installed in a similar manner: make config make tcl make install-tcl –1– April14,2006 MagicTclTutorial#4:SimulationwithIRSIM Tcl-based IRSIM, like its non-interpreter version, can be run as a standalone product, and will simulate a circuit from a .sim format file. However, it is specifically designed to be operated in conjunction with magic, with methods for providing feedback directly into the layout from the simulation, and vice versa. There are a number of cross-application commands, detailed below, which belong to neither Magic or IRSIM, but are applicable when both are running in the Tcl interpreter at the same time.
    [Show full text]
  • What Is Object-Oriented Perl?
    This is a series of extracts from Object Oriented Perl, a new book from Manning Publications that will be available in August 1999. For more information on this book, see http://www.manning.com/Conway/. What is object-oriented Perl? Object-oriented Perl is a small amount of additional syntax and semantics, added to the existing imperative features of the Perl programming language. Those extras allow regular Perl packages, variables, and subroutines to behave like classes, objects, and methods. It's also a small number of special variables, packages and modules, and a large number of new techniques, that together provide inheritance, data encapsulation, operator overloading, automated definition of commonly used methods, generic programming, multiply-dispatched polymorphism, and persistence. It's an idiosyncratic, no-nonsense, demystified approach to object-oriented programming, with a typically Perlish disregard for accepted rules and conventions. It draws inspiration (and sometimes syntax) from many different object-oriented predecessors, adapting their ideas to its own needs. It reuses and extends the functionality of existing Perl features, and in the process throws an entirely new slant on what they mean. In other words, it's everything that regular Perl is, only object-oriented. Using Perl makes object-oriented programming more enjoyable, and using object- oriented programming makes Perl more enjoyable too. Life is too short to endure the cultured bondage-and-discipline of Eiffel programming, or to wrestle the alligators that lurk in the muddy semantics of C++. Object-oriented Perl gives you all the power of those languages, with very few of their tribulations. And best of all, like regular Perl, it's fun! Before we look at object orientation in Perl, let’s talk about what object orientation is in general..
    [Show full text]