DOCSLIB.ORG

A Syllabus for Introducing MBA Students to Procedural And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Syllabus for Introducing MBA Students to Procedural And View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by AIS Electronic Library (AISeL) Association for Information Systems AIS Electronic Library (AISeL) Americas Conference on Information Systems AMCIS 1999 Proceedings (AMCIS) December 1999 A Syllabus for Introducing MBA Students to Procedural and Object-oriented Programming (Object Rexx) Rony Flatscher Vienna University of Economics and Business Administration Follow this and additional works at: http://aisel.aisnet.org/amcis1999 Recommended Citation Flatscher, Rony, "A Syllabus for Introducing MBA Students to Procedural and Object-oriented Programming (Object Rexx)" (1999). AMCIS 1999 Proceedings. 195. http://aisel.aisnet.org/amcis1999/195 This material is brought to you by the Americas Conference on Information Systems (AMCIS) at AIS Electronic Library (AISeL). It has been accepted for inclusion in AMCIS 1999 Proceedings by an authorized administrator of AIS Electronic Library (AISeL). For more information, please contact [email protected]. A Syllabus for Introducing MBA Students to Procedural and Object-oriented Programming (Object Rexx) Rony G. Flatscher Vienna University of Economics and Business Administration, Austria Department of Management Information Systems choice of Abstract Electronic Commerce (lecture, 2 Electronic Finance (lecture, 2 hours) hours) MBA students are exposed to information systems Business Process Modelling (lecture, 2 hours) which can be controlled by the means of macro-languages and are faced with a new type of information systems choice of which employ the object-oriented paradigm (e.g. SAP, „ISD“: Information Systems „SPET“: Solving Problems with Development with CASE (lecture, Enduser Tools (lecture, 2 hours, 1999). With no idea about (procedural and) especially 2 hours, optional introduction) optional introduction) object-oriented concepts, it is impossible for such students ISD - Application (pro-seminar, 2 SPET - Application (pro-seminar, to comprehend and evaluate the new breed of ERP sys- hours) 2 hours) tems with OO-interfaces and the ongoing developments in at least two lectures („Electives“) out of the realm of „business objects“ (e.g. OMG BODTF, IS in Finance and Accounting; IS in Marketing; IS in Commerce; Com- 1999). Therefore, in the summer-semester 1999 an ex- puter Law; IT Market and Information Management; Electronic Money, perimental lecture was introduced, which teaches MBA Payment Systems and Security students the fundamental concpets of procedural and ob- MIS (seminar, 2 hours) ject-oriented concepts. To allow them to experiment and build hand-on experience a language was chosen that is Figure 1: MIS-Classes at WU (as of 1999-01). known for its simple and easy syntax, yet powerful object Due to the business-oriented nature of the University, model: Object Rexx. The devised syllabus, which teaches there was no need in the past years to teach object- the fundamental concepts of procedural and object- oriented concepts in order for the students to understand oriented programming is layed out and explained in this 1 and evaluate business-related information systems like article. ERP. Yet, in the past years the initiatives of OMG to devise object-oriented standards for business objects with MBA Students the implementation of the BODTF („Business Object At the WU there are over 25,000 MBA students who Domain Task Force“) has led - among other things - to a learn the fundamentals of business administration. The competition between ERP vendors like SAP and Baan, curriculum and the structure of the studies were layed out which offered their BO-solutions to OMG for standardi- at an IAIM conference. (Flatscher, 1993) Basically, the zation.2 studies are divided into two parts, each lasting a minimum It is this particular situation which makes it important of two years. It is in the second part of the studies, where for MBA-students to learn about object-oriented princi- MBA students are allowed to choose up to two specialized ples, because otherwise they are unable to comprehend the fields of Business Administration like „Tourism“, „Fi- BO frameworks offered by ERP-vendors, let alone as- nance“ or „Management Information Systems“. For suc- sessing them. With other words, the marriage between cessfully studying MIS a minimum of 12 hours must be business adminstration domain knowledge and informa- taken followed by a comprehensive written and oral ex- tion technology (IT) is not possible for the students any- amination. Figure 1 sketches the available MIS-classes as more, once object-oriented IT gets applied. of January 1999. This uneasy situation led to the creation of a new (elective) MIS-class for the summer semester 1999, which attempts to teach the object-oriented paradigm with the help of an easy to learn programming language. The pro- gramming language should allow the students to apply what they learn, experiment further with the taught con- cepts and build experience on their own. In this context it is felt very important that a language be chosen, which is rather easy to learn: Rexx was built with this intention from the ground up and Object Rexx carried this idea 565 further into the object-oriented world, built on a powerful Object-Oriented Concepts object model. (Cowlishaw, 1984, 1990, 1994; Flatscher, The descriptions for the weeks 6 through 15 introduce 1996, 1997) Of course, the fundamental procedural and the most important object-oriented concepts. object-oriented concepts taught can be transferred to most other programming languages. For this class Object Rexx3 Week 6: Classes, methods, attributes, messages was chosen due to its simple syntax, which should allow („twiddle“ = tilde ‘~’), scopes, creation (instantiation) of the students to concentrate on the concepts rather than the objects. This class introduces the basic concepts of the syntax or peculiarities of a specific programming language object-oriented paradigm starting out with a discussion of like C++ or Java4. ADT’s (abstract data types). Object Rexx is backwardly compatible to (procedural) Rexx and retains its easy syn- It is expected that students electing the class „Intro- tax. Internally any statement is transposed to its OO-form duction into the procedural and object-oriented program- before execution. ming (Object Rexx)“ will be able to learn the planned object-oriented concepts and as a result become able Week 7: Inheritance, specializing, scopes, concurrent among other things to comprehend and follow the devel- execution. The concept of the classification tree and its opments of business objects. applications are introduced as well as concurrency issues with respect to invocation of methods on the same object The Devised Syllabus at different levels of the classification tree and of different objects at the same level. In this section the contents of the concepts which Week 8: Object Rexx classes and examples. An over- ought to be taught each week are documented. view of the built-in classes and their application is given with examples stressing different issues like message- Procedural Concepts invocations, definition of alarms, usage of monitors. The descriptions for the weeks 1 through 5 introduce Week 9: Object Rexx collection classes and examples. the procedural concepts. An overview of the built-in collection classes and their Week 1: Overview of the class, accepting of students, application is given together with examples. history of Rexx, latest developments: ANSI Rexx, Object Week 10: Class methods, class attributes, class ‘Class’ Rexx, NetRexx (Java). This installment explains the in- (Object Rexx’ metaclass). The concept of ‘metaclass’ is tention of the author of Rexx, Mike F. Cowlishaw, to introduced and explained. Of the Object Rexx metaclasses create a „human centric“ programming language which the founding class ‘Class’ is explained. results in a simple and easy to learn syntax (Cowlishaw, Week 11: The big picture (Object Rexx class hierarchy 1994). and its instantiation), definition of classes and methods at Week 2: Minimal Rexx program, interactive program- runtime, ‘one-off’ objects. The important role of the ming („RexxTry.cmd“), variables, constants, comments, classes ‘Object’ and ‘Class’ are re-iterated, the methods statements, blocks, selections, iterations. The basic build- for reflection explained and the logic of setting up a run- ing blocks of a typical procedural programming language time system for representing the classification tree itself is are explained. introduced. Week 3: Labels, procedures, functions, searching order Week 12: Coupling with the help of the Object Rexx for functions/procedures, scopes. The concepts of subrou- environment, ‘.local’- and ‘.environment’- tines and (depending on time even recursive) functions directories. The runtime system sets up environments for together with the scopes and their effects are introduced modules and sessions for keeping objects available for and discussed. retrieval. It is possible to couple different routines, meth- Week 4: Built-in Rexx-functions, „stem“ variables, ods and modules via these environments. „Rexx utility“ functions („RexxUtil“). „Stems“ can be Week 13: Object Rexx Utilities ‘ORX7’ and ‘ORX8’ regarded as asscociative arrays, whose index can be any (Flatscher 1996, 1997). A set of miscellaneous utility (compound) string. Some utility functions use numeric modules, routines, classes and programs for Object Rexx indices as subscripts to stems by convention and need to are introduced and some of them are explained
Load more

Recommended publications
  • Programming Paradigms & Object-Oriented
    4.3 (Programming Paradigms & Object-Oriented- Computer Science 9608 Programming) with Majid Tahir Syllabus Content: 4.3.1 Programming paradigms Show understanding of what is meant by a programming paradigm Show understanding of the characteristics of a number of programming paradigms (low- level, imperative (procedural), object-oriented, declarative) – low-level programming Demonstrate an ability to write low-level code that uses various address modes: o immediate, direct, indirect, indexed and relative (see Section 1.4.3 and Section 3.6.2) o imperative programming- see details in Section 2.3 (procedural programming) Object-oriented programming (OOP) o demonstrate an ability to solve a problem by designing appropriate classes o demonstrate an ability to write code that demonstrates the use of classes, inheritance, polymorphism and containment (aggregation) declarative programming o demonstrate an ability to solve a problem by writing appropriate facts and rules based on supplied information o demonstrate an ability to write code that can satisfy a goal using facts and rules Programming paradigms 1 4.3 (Programming Paradigms & Object-Oriented- Computer Science 9608 Programming) with Majid Tahir Programming paradigm: A programming paradigm is a set of programming concepts and is a fundamental style of programming. Each paradigm will support a different way of thinking and problem solving. Paradigms are supported by programming language features. Some programming languages support more than one paradigm. There are many different paradigms, not all mutually exclusive. Here are just a few different paradigms. Low-level programming paradigm The features of Low-level programming languages give us the ability to manipulate the contents of memory addresses and registers directly and exploit the architecture of a given processor.
    [Show full text]
  • A Feature Model of Actor, Agent, Functional, Object, and Procedural Programming Languages
    Accepted Manuscript A feature model of actor, agent, functional, object, and procedural programming languages H.R. Jordan, G. Botterweck, J.H. Noll, A. Butterfield, R.W. Collier PII: S0167-6423(14)00050-1 DOI: 10.1016/j.scico.2014.02.009 Reference: SCICO 1711 To appear in: Science of Computer Programming Received date: 9 March 2013 Revised date: 31 January 2014 Accepted date: 5 February 2014 Please cite this article in press as: H.R. Jordan et al., A feature model of actor, agent, functional, object, and procedural programming languages, Science of Computer Programming (2014), http://dx.doi.org/10.1016/j.scico.2014.02.009 This is a PDF file of an unedited manuscript that has been accepted for publication. As a service to our customers we are providing this early version of the manuscript. The manuscript will undergo copyediting, typesetting, and review of the resulting proof before it is published in its final form. Please note that during the production process errors may be discovered which could affect the content, and all legal disclaimers that apply to the journal pertain. Highlights • A survey of existing programming language comparisons and comparison techniques. • Definitions of actor, agent, functional, object, and procedural programming concepts. • A feature model of general-purpose programming languages. • Mappings from five languages (C, Erlang, Haskell, Jason, and Java) to this model. A Feature Model of Actor, Agent, Functional, Object, and Procedural Programming Languages H.R. Jordana,∗, G. Botterwecka, J.H. Nolla, A. Butterfieldb, R.W. Collierc aLero, University of Limerick, Ireland bTrinity College Dublin, Dublin 2, Ireland cUniversity College Dublin, Belfield, Dublin 4, Ireland Abstract The number of programming languages is large [1] and steadily increasing [2].
    [Show full text]
  • Rexx Programmer's Reference
    01_579967 ffirs.qxd 2/3/05 9:00 PM Page i Rexx Programmer’s Reference Howard Fosdick 01_579967 ffirs.qxd 2/3/05 9:00 PM Page iv 01_579967 ffirs.qxd 2/3/05 9:00 PM Page i Rexx Programmer’s Reference Howard Fosdick 01_579967 ffirs.qxd 2/3/05 9:00 PM Page ii Rexx Programmer’s Reference Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2005 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 0-7645-7996-7 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 1MA/ST/QS/QV/IN 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, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, e-mail: [email protected]. LIMIT OF LIABILITY/DISCLAIMER OF WARRANTY: THE PUBLISHER AND THE AUTHOR MAKE NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE ACCURACY OR COM- PLETENESS OF THE CONTENTS OF THIS WORK AND SPECIFICALLY DISCLAIM ALL WAR- RANTIES, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE.
    [Show full text]
  • The Machine That Builds Itself: How the Strengths of Lisp Family
    Khomtchouk et al. OPINION NOTE The Machine that Builds Itself: How the Strengths of Lisp Family Languages Facilitate Building Complex and Flexible Bioinformatic Models Bohdan B. Khomtchouk1*, Edmund Weitz2 and Claes Wahlestedt1 *Correspondence: [email protected] Abstract 1Center for Therapeutic Innovation and Department of We address the need for expanding the presence of the Lisp family of Psychiatry and Behavioral programming languages in bioinformatics and computational biology research. Sciences, University of Miami Languages of this family, like Common Lisp, Scheme, or Clojure, facilitate the Miller School of Medicine, 1120 NW 14th ST, Miami, FL, USA creation of powerful and flexible software models that are required for complex 33136 and rapidly evolving domains like biology. We will point out several important key Full list of author information is features that distinguish languages of the Lisp family from other programming available at the end of the article languages and we will explain how these features can aid researchers in becoming more productive and creating better code. We will also show how these features make these languages ideal tools for artificial intelligence and machine learning applications. We will specifically stress the advantages of domain-specific languages (DSL): languages which are specialized to a particular area and thus not only facilitate easier research problem formulation, but also aid in the establishment of standards and best programming practices as applied to the specific research field at hand. DSLs are particularly easy to build in Common Lisp, the most comprehensive Lisp dialect, which is commonly referred to as the “programmable programming language.” We are convinced that Lisp grants programmers unprecedented power to build increasingly sophisticated artificial intelligence systems that may ultimately transform machine learning and AI research in bioinformatics and computational biology.
    [Show full text]
  • Creating Java Applications Using Netrexx
    SG24-2216-00 Creating Java Applications Using NetRexx September 1997 IBML International Technical Support Organization SG24-2216-00 Creating Java Applications Using NetRexx September 1997 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix B, “Special Notices” on page 273. First Edition (September 1997) This edition applies to Version 1.0 and Version 1.1 of NetRexx with Java Development Kit 1.1.1 for use with the OS/2 Warp, Windows 95, and Windows NT operating systems. Because NetRexx runs on any platform where Java is implemented, it applies to other platforms and operating systems as well. SAMPLE CODE ON THE INTERNET The sample code for this redbook is available as nrxredbk.zip on the ITSO home page on the Internet: ftp://www.redbooks.ibm.com/redbooks/SG242216 Download the sample code and read “Installing the Sample Programs” on page 4. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1997. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures . xi Tables . xv Preface . xvii How This Document is Organized ................................ xviii The Team That Wrote This Redbook ...............................
    [Show full text]
  • REXX Parsing for Today’S Slides and Other Webinars Visit: PARSE Forms
    REXX Parsing For today’s slides and other webinars visit: www.themisinc.com/webinars PARSE Forms PARSE ARG template Parameters passed to program or subroutine PARSE EXTERNAL template Read from Terminal (TSO/E, VM only) PARSE NUMERIC template Current NUMERIC settings (TSO/E, VM only) PARSE PULL template Remove data from REXX STACK PARSE SOURCE template Information about the current program PARSE VALUE expression WITH template Information comes from expression PARSE VAR name template Parse one variable into other variables PARSE VERSION template Information about the REXX interpreter General Rules for Parsing • Parsing processes the data string from left to right • If there is more data than defined variables, the last variable receives ALL the remaining data • If there are more variables than data, the remaining variables are set as null • A period (.) may be used as a “placeholder” to bypass setting a variable PARSE VAR Keyword PARSE [UPPER] VAR origin template Use designated variable as input to template PARSING Example origin_data = ‘This is the original data’ PARSE VAR origin_data var1 var2 var3 var1 = This var2 = is var3 = the original data PARSING Example #2 origin_data = ‘This is the original data’ PARSE VAR origin_data var1 . var3 var1 = This var3 = original data PARSING Example #3 origin_data = ‘This is the original data’ PARSE VAR origin_data var1 var2 var3 . var1 = This var2 = is var3 = the PARSING Example #4 origin_data = ‘This is the original data’ PARSE VAR origin_data var1 “the” var3 . var1 = This is var3 = original NOTE: The placeholder (.) removes the last bit of data as space-delimited. Parsing Example Evaluate the following PARSE template: • What will dsn and member contain? dsname = "'SYS1.PROCLIB(JES2)'" PARSE VAR dsname "'" dsn '(' member ')' .
    [Show full text]
  • The Design of the REXX Language
    The design of the REXX language by M. F. Cowlishaw One way of classifying computer languagesis by two (consciously or otherwise) to be easy to compile or classes: languages needing skilled programmers, and easy to interpret, it is designed (with the help of personal languages usedby an expanding population of general users. REstructured extended executor feedback from hundreds of users) to be easy to use. (REXX) isa flexible personal language designed with particular attention to feedback from its users. It has Three major factors affect the usability of a language. proved to be effective and easyto use, yet it is suffi- First, the basic concepts of a language affect its ciently general and powerfulto fulfil theneeds of many demanding professional applications.REXX is system syntax, grammar, and consistency. Second, the his- and hardware independent,so that it has been possi- tory and development of a language determine its ble to integrate it experimentally into several operating function, usability, and completeness. Third, but systems. Here REXX isused for such purposes as com- quite independently, the implementation of a lan- mand and macro programming, prototyping, educa- guage affects its acceptability, portability, and distri- tion, and personal programming. This paper introduces REXX and describes the basic design principles that bution. This paper introduces REXX and then dis- were followed in developingit. cusses basic concepts and developmental history as applied to the design of the REXX language. There are several experimental implementations of the REXX language within IBM for both large and small machines. One of these, by the author, has omputer languages may be classified in many become a part of the Virtual Machine/System Prod- ways.
    [Show full text]
  • A Formal Component-Based Software Engineering Approach for Developing Trustworthy Systems
    A FORMAL COMPONENT-BASED SOFTWARE ENGINEERING APPROACH FOR DEVELOPING TRUSTWORTHY SYSTEMS MUBARAK SAMI MOHAMMAD A THESIS IN THE DEPARTMENT OF COMPUTER SCIENCE AND SOFTWARE ENGINEERING PRESENTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY (COMPUTER SCIENCE) CONCORDIA UNIVERSITY MONTREAL´ ,QUEBEC´ ,CANADA APRIL 2009 °c MUBARAK SAMI MOHAMMAD, 2009 CONCORDIA UNIVERSITY School of Graduate Studies This is to certify that the thesis prepared By: Mr. Mubarak Sami Mohammad Entitled: A Formal Component-Based Software Engineering Approach for Developing Trustworthy Systems and submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy (Computer Science) (Computer Science) complies with the regulations of this University and meets the accepted standards with re- spect to originality and quality. Signed by the final examining committee: Chair Dr. External Examiner Dr. Nicholas Graham External to Program Dr. Jamal Bentahar Examiner Dr. Joey Paquet Examiner Dr. Juergen Rilling Supervisor Dr. Vasu Alagar Co-supervisor Dr. Olga Ormandjieva Approved Chair of Department or Graduate Program Director 20 Dr. Robin A.L. Drew, Dean Faculty of Engineering and Computer Science Abstract A Formal Component-Based Software Engineering Approach for Developing Trustworthy Systems Mubarak Sami Mohammad, Ph.D. Concordia University, 2009 Software systems are increasingly becoming ubiquitous, affecting the way we experience the world. Embedded software systems, especially those used in smart devices, have be- come an essential constituent of the technological infrastructure of modern societies. Such systems, in order to be trusted in society, must be proved to be trustworthy. Trustworthiness is a composite non-functional property that implies safety, timeliness, security, availability, and reliability.
    [Show full text]
  • Comparative Studies of Programming Languages; Course Lecture Notes
    Comparative Studies of Programming Languages, COMP6411 Lecture Notes, Revision 1.9 Joey Paquet Serguei A. Mokhov (Eds.) August 5, 2010 arXiv:1007.2123v6 [cs.PL] 4 Aug 2010 2 Preface Lecture notes for the Comparative Studies of Programming Languages course, COMP6411, taught at the Department of Computer Science and Software Engineering, Faculty of Engineering and Computer Science, Concordia University, Montreal, QC, Canada. These notes include a compiled book of primarily related articles from the Wikipedia, the Free Encyclopedia [24], as well as Comparative Programming Languages book [7] and other resources, including our own. The original notes were compiled by Dr. Paquet [14] 3 4 Contents 1 Brief History and Genealogy of Programming Languages 7 1.1 Introduction . 7 1.1.1 Subreferences . 7 1.2 History . 7 1.2.1 Pre-computer era . 7 1.2.2 Subreferences . 8 1.2.3 Early computer era . 8 1.2.4 Subreferences . 8 1.2.5 Modern/Structured programming languages . 9 1.3 References . 19 2 Programming Paradigms 21 2.1 Introduction . 21 2.2 History . 21 2.2.1 Low-level: binary, assembly . 21 2.2.2 Procedural programming . 22 2.2.3 Object-oriented programming . 23 2.2.4 Declarative programming . 27 3 Program Evaluation 33 3.1 Program analysis and translation phases . 33 3.1.1 Front end . 33 3.1.2 Back end . 34 3.2 Compilation vs. interpretation . 34 3.2.1 Compilation . 34 3.2.2 Interpretation . 36 3.2.3 Subreferences . 37 3.3 Type System . 38 3.3.1 Type checking . 38 3.4 Memory management .
    [Show full text]
  • Programming Languages
    Lecture 19 / Chapter 13 COSC1300/ITSC 1401/BCIS 1405 12/5/2004 Lecture 19 / Chapter 13 COSC1300/ITSC 1401/BCIS 1405 12/5/2004 General Items: Computer Program • Lab? Ok? • Read the extra credits • A series of instructions that direct a computer to perform tasks • Need to come to class • Such as? Who is the programmer? • Have a quiz / no books / use notes -> What is the big idea • School is almost over • Programming language is a series of rules for writing the instructions • • There are hundreds of computer programs – need-based! Reading Materials: Programming language • - Two basic types: Low- and high-level programming languages Miscellaneous: o Low-level: Programming language that is machine-dependent ° Must be run on specific machines o High-level: Language that is machine-independent ° Can be run on different types of machines Programming Language Low Level High Level Machine Assembly Language Language Procedural Nonprocedural Remember: Ultimately, everything must be converted to the machine language! Object Oriented F.Farahmand 1 / 12 File: lec14chap13f04.doc F.Farahmand 2 / 12 File: lec14chap13f04.doc Lecture 19 / Chapter 13 COSC1300/ITSC 1401/BCIS 1405 12/5/2004 Lecture 19 / Chapter 13 COSC1300/ITSC 1401/BCIS 1405 12/5/2004 Categories of programming languages o Nonprocedural language -> Programmer specifies only what the - Machine language program should accomplish; it does not explain how o Only language computer understands directly - Forth-generation language - Assembly language o Syntax is closer to human language than that
    [Show full text]
  • IBM Tivoli Netview for Z/OS Programming: PL/I and C, Describes How to Write Command Processors and Installation Exit Routines for the Netview Product Using PL/I and C
    IBM Tivoli NetView for z/OS Version 6 Release 1 Programming: PL/I and C SC27-2860-00 IBM Tivoli NetView for z/OS Version 6 Release 1 Programming: PL/I and C SC27-2860-00 Note Before using this information and the product it supports, read the information in “Notices” on page 317. This edition applies to version 6, release 1 of IBM Tivoli NetView for z/OS (product number 5697-NV6) and to all subsequent versions, releases, and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1997, 2011. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ....................................xi About this publication .............................xiii Intended audience .................................xiii Publications ...................................xiii IBM Tivoli NetView for z/OS library .........................xiii Related publications ...............................xv Accessing terminology online ............................xv Using NetView for z/OS online help .........................xvi Using LookAt to look up message explanations ......................xvi Accessing publications online ............................xvii Ordering publications ..............................xvii Accessibility ..................................xvii Tivoli technical training ...............................xvii Tivoli user groups ................................xviii Downloads ...................................xviii Support information................................xviii
    [Show full text]
  • Open Source - Who Cares and Why?
    Open Source - Who Cares and Why? Al Williams Session 8480 SHARE 103, New York, NY August 20, 2004 http://lily.garden.et-test.psu.edu/~alw/whyopen.pdf Agenda What is Open Source? What is it being used for? Who is using Open Source? Open Source Myths? What does this mean? What is Open Source? Open Source Is Application, program, or utility where The computer instructions (code, source) are provided with the program Licensed in such a way that it can be improved, enhanced, or localized freely Isn’t necessarily zero cost Popular revolution - some good work being done More lengthly definition at http://www.opensource.org Open Source Initiative The Open Source Initiative is now a California public benefit (not-for- profit) corporation Prompted by Netscape source code availability press release: http://wp.netscape.com/newsref/pr/newsrelease558.html http://www.opensource.org/ It’s Free, Right? Lots of software is free to download Not necessarily cost-free Need to have programmers to support yourself Need to have infrastructure to participate in development Can be resold by vendors who add value May need to pay for support from a vendor Some free software isn’t open source If You Want Free Software Free Software Foundation Open Source and Free http://www.fsf.org New Idea? No, our operating systems used to be source maintained HASP CMS We were familiar with source management SHARE has a history of sharing improvements in this area (mods) Perhaps Open Source is a new opportunity for us Circle of Life? Twenty-four years ago our favorite vendor extolled the value of Object Code Only control your system programmers reduce maintenance cost improve security and reliability Now Open Source is in (again) control your destiny share development effort match your business needs support “Open Standards” How is it Developed? Several formal projects (Foundries) What’s a Foundry? Foundries provide a place for end-users, developers and other interested parties to communicate, discuss new ideas, and learn about new software and technologies which may benefit them.
    [Show full text]