DOCSLIB.ORG

Generation of a Java Front End for a Standalone CICS Application Accessed Through Mqseries & Securing CICS with RACF

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Generation of a Java Front End for a Standalone CICS Application Accessed Through Mqseries & Securing CICS with RACF UNIVERSITY OF LEIPZIG Department of Computer Science Generation of a Java front end for a standalone CICS application accessed through MQSeries & Securing CICS with RACF Diplomarbeit – Master Thesis Submitted by Tobias Busse 1st Examiner: Prof. Dr.-Ing. W. G. Spruth Born: 1976/07/14 2nd Examiner: Peter Missen Subject: Computer Science Matr.Nr.: 7952583 Leipzig, August 2004 EXECUTIVE SUMMARY This master thesis deals with the design, programming, implementation and presentation of on-line business ap- plications for IBM's On-Line Transaction Processing (OLTP) system called Customer Information Control Sys- tem (CICS). According to the book “Designing and Programming CICS Applications” published by John Hor- swill [HOR00] we explain two out of many feasible procedures to present the functionality of CICS resp. CICS business applications. As the main result, we create for each of both procedures a business application representing a little clip of a bank customer account program. These applications access a database-like file stored on an Operating System/390 (OS/390) server to create, read, update, and delete customer accounts. Both use CICS not only as a transaction processing system but also as an application server that manages business applications 24 hours a day for 7 days a week. The difference between the two business applications are the data transfer and information dis- play methods. The first procedure describes how to create a business application that uses the legacy 3270 inter- face to inquire a customer record stored on the OS/390-server and how to display the information on a 3270 ter- minal screen (also called as the green screen). In contrast, the second business application uses message queuing provided by IBM's Message Oriented Middleware (MOM) product MQSeries to transfer the request data to and the response data from the customer account file between CICS and the Java Virtual Machine (JVM). This JVM runs on a WINDOWS2000 client, whereas MQSeries has to run on both – the OS/390-server and the WIN- DOWS2000 client. For this procedure, the so-called MQSeries CICS Bridge – an interface between CICS and MQSeries on the OS/390-server – is installed and activated. It is also described how to use the Message Queue Interface (MQI) that connects MQSeries and JAVA on the client computer system. Hence, the business logic component is used by both sample applications, but they differ in the presentation logic components. The programs of the business logic component, written in the programming language CO- BOL, are responsible for the data transfer to and from the customer account file to update or read it, for the busi- ness calculations, and for the error handling. The presentation logic component of the first business application – the CICS application NACT – is also written in COBOL and use the Basic Mapping Support (BMS) to set up the 3270 interface. In the second business application called the MQSeries CICS application MQNACT the pro- grams of the presentation logic component are written in JAVA. Additionally, this master thesis describes the security management of CICS using IBM's External Security Manager (ESM) Resource Access Control Facility (RACF). The main part of this procedure is to allow only au- thorised terminal users an access to an existing CICS address space, including some CICS default user IDs as for example the CICS Region User ID (CRU), and the Default CICS User ID (DCU). Furthermore, the authorised user should/may use only those CICS resources for which a permission exists. Securing CICS resources is ex- plained on the examples of the CICS Transactions Security mechanism and the CICS Command Security mech- anism. “There is no human on the world from whom you cannot learn something.” (Albert Schweitzer) Acknowledgements My thanks goes to Prof. Dr. Wilhelm G. Spruth who gave me the best support and who never despaired on my English writing. I wish to thank Peter Missen, head of the CICS User Group at IBM Hursley UK, for helping, for redacting this text, and, of course, for working with the CICS User Group. My technical thanks goes to Dr. Paul Herrmann who always sustained the functionality of the JEDI OS/390-server. Many thanks goes also to: Nils Michaelsen for his encouragement in my work, Ulrike Kirsch (IBM Leipzig Germany) for her support on MQSeries, Sandro Varges (IBM Mainz Germany) for his support on CICS (“Haeh, What is a CSD, Sandro?” ), Thomas Renner (IBM Leipzig Germany) for his support on RACF and JCL, Ingo Karge who provided for me a desk at the IBM Leipzig location, the CICS User Group, especially to Paul …, James Taylor, and Kevin ..., and to everyone at IBM Leipzig. I would also like to thank my family for their constant support. For my lovely butterfly Ivonne Lange, the sun should always shine. Thanks for your support, for your lovely cooking, for your understanding in my work and for your +encouragement. Together we will fight the future! TABLE OF CONTENTS List of Figures ................................................................................................... xi List of Tables .................................................................................................... xv List of Listings .................................................................................................. xvii List of Abbreviations ........................................................................................ xix Notices .............................................................................................................. xxi 1 Introduction to OS/390 23 1.1 Introduction .................................................................................................................... 23 1.2 History of OS/390 ........................................................................................................... 24 1.3 OS/390 in general .......................................................................................................... 27 1.4 OS/390 V2R7 ................................................................................................................. 30 2 Introduction to CICS 33 2.1 Introduction .................................................................................................................... 33 2.2 History of CICS .............................................................................................................. 34 2.3 CICS in general .............................................................................................................. 36 3 The Initial Architecture of the CICS Business Applications 39 4 The CICS Business Application NACT 41 4.1 Introduction .................................................................................................................... 41 4.2 Uploading the files ......................................................................................................... 42 4.3 The NACT COBOL programs and their commands ...................................................... 49 4.3.1 Overview .................................................................................................................. 49 4.3.2 The presentation logic component ........................................................................... 49 4.3.3 The business logic component ................................................................................ 54 4.3.4 Other commands that control the programs ............................................................ 56 4.3.5 Excursion: Storing exchange data – When to use the COMMAREA? ..................... 57 4.3.5.1 Overview ............................................................................................................ 57 4.3.5.2 Temporary Storage – queuing and scratchpad facility ...................................... 59 4.3.5.3 Transient Data – queuing facility ........................................................................ 60 4.3.5.4 COMMAREA – a scratchpad facility .................................................................. 60 4.3.5.5 Common Work Area, Transaction Work Area, and Terminal User Area – other Generation of a Java front end for a standalone CICS application accessed through MQSeries & viii Securing CICS with RACF scratchpad facilities .......................................................................................................... 67 4.4 Storing the data – account file, locking file, and name file ............................................. 68 4.4.1 File description ......................................................................................................... 68 4.4.2 Installing the storing data ......................................................................................... 70 4.5 The CICS resource definitions ....................................................................................... 74 4.5.1 Overview .................................................................................................................. 74 4.5.2 Setting up the CICS resources ................................................................................. 74 5 The MQSeries CICS Business Application MQNACT 81 5.1 Introduction .................................................................................................................... 81 5.2 Messaging and Queuing ................................................................................................ 83 5.2.1 Overview .................................................................................................................
Load more

Recommended publications
  • Cloud Enabling CICS
    Front cover Cloud Enabling IBM CICS Discover how to quickly cloud enable a traditional IBM 3270-COBOL-VSAM application Use CICS Explorer to develop and deploy a multi-versioned application Understand the benefits of threshold policy Rufus Credle Isabel Arnold Andrew Bates Michael Baylis Pradeep Gohil Christopher Hodgins Daniel Millwood Ian J Mitchell Catherine Moxey Geoffrey Pirie Inderpal Singh Stewart Smith Matthew Webster ibm.com/redbooks International Technical Support Organization Cloud Enabling IBM CICS December 2014 SG24-8114-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2014) This edition applies to CICS Transaction Server for z/OS version 5.1, 3270-COBOL-VSAM application. © Copyright International Business Machines Corporation 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii IBM Redbooks promotions . ix Preface . xi Authors. xii Now you can become a published author, too! . .xv Comments welcome. .xv Stay connected to IBM Redbooks . xvi Part 1. Introduction . 1 Chapter 1. Cloud enabling your CICS TS applications . 3 1.1 Did you know?. 4 1.2 Business value . 4 1.3 Solution overview . 5 1.4 Cloud computing in a CICS TS context. 6 1.5 Overview of the cloud-enabling technologies in CICS TS V5 . 11 1.5.1 Platform overview . 12 1.5.2 Application overview . 13 Chapter 2. GENAPP introduction. 15 2.1 CICS TS topology . 16 2.2 Application architecture. 17 2.2.1 GENAPP in a single managed region.
    [Show full text]
  • The Operating System Handbook Or, Fake Your Way Through Minis and Mainframes
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme MVS Table of Contents Chapter 22 MVS: An Introduction.................................................................................... 22.1 Batch Jobs..................................................................................................................1 22.2 Interacting with MVS................................................................................................3 22.2.1 TSO.........................................................................................................................3 22.2.2 ISPF........................................................................................................................3 22.2.3 CICS........................................................................................................................4 22.2.4 Other MVS Components.........................................................................................4 22.3 History........................................................................................................................5 Chapter 23 Getting Started with MVS............................................................................... 23.1 Starting Up.................................................................................................................6 23.1.1 VTAM.....................................................................................................................6 23.1.2 Logging On.............................................................................................................6
    [Show full text]
  • Big Blue in the Bottomless Pit: the Early Years of IBM Chile
    Big Blue in the Bottomless Pit: The Early Years of IBM Chile Eden Medina Indiana University In examining the history of IBM in Chile, this article asks how IBM came to dominate Chile’s computer market and, to address this question, emphasizes the importance of studying both IBM corporate strategy and Chilean national history. The article also examines how IBM reproduced its corporate culture in Latin America and used it to accommodate the region’s political and economic changes. Thomas J. Watson Jr. was skeptical when he The history of IBM has been documented first heard his father’s plan to create an from a number of perspectives. Former em- international subsidiary. ‘‘We had endless ployees, management experts, journalists, and opportunityandlittleriskintheUS,’’he historians of business, technology, and com- wrote, ‘‘while it was hard to imagine us getting puting have all made important contributions anywhere abroad. Latin America, for example to our understanding of IBM’s past.3 Some seemed like a bottomless pit.’’1 However, the works have explored company operations senior Watson had a different sense of the outside the US in detail.4 However, most of potential for profit within the world market these studies do not address company activi- and believed that one day IBM’s sales abroad ties in regions of the developing world, such as would surpass its growing domestic business. Latin America.5 Chile, a slender South Amer- In 1949, he created the IBM World Trade ican country bordered by the Pacific Ocean on Corporation to coordinate the company’s one side and the Andean cordillera on the activities outside the US and appointed his other, offers a rich site for studying IBM younger son, Arthur K.
    [Show full text]
  • The Advent of Recursion in Programming, 1950S-1960S
    The Advent of Recursion in Programming, 1950s-1960s Edgar G. Daylight?? Institute of Logic, Language, and Computation, University of Amsterdam, The Netherlands [email protected] Abstract. The term `recursive' has had different meanings during the past two centuries among various communities of scholars. Its historical epistemology has already been described by Soare (1996) with respect to the mathematicians, logicians, and recursive-function theorists. The computer practitioners, on the other hand, are discussed in this paper by focusing on the definition and implementation of the ALGOL60 program- ming language. Recursion entered ALGOL60 in two novel ways: (i) syn- tactically with what we now call BNF notation, and (ii) dynamically by means of the recursive procedure. As is shown, both (i) and (ii) were in- troduced by linguistically-inclined programmers who were not versed in logic and who, rather unconventionally, abstracted away from the down- to-earth practicalities of their computing machines. By the end of the 1960s, some computer practitioners had become aware of the theoreti- cal insignificance of the recursive procedure in terms of computability, though without relying on recursive-function theory. The presented re- sults help us to better understand the technological ancestry of modern- day computer science, in the hope that contemporary researchers can more easily build upon its past. Keywords: recursion, recursive procedure, computability, syntax, BNF, ALGOL, logic, recursive-function theory 1 Introduction In his paper, Computability and Recursion [41], Soare explained the origin of computability, the origin of recursion, and how both concepts were brought to- gether in the 1930s by G¨odel, Church, Kleene, Turing, and others.
    [Show full text]
  • IBM Global Services: a Brief History
    IBM Global Services: A Brief History IBM Corporate Archives May 2002 2405SH01 2 OVERVIEW Background In 1991 IBM was a $64.8 billion company, of which less than $6 billion was derived from non-maintenance services. Ten short years later, the business of information technology (IT) services alone generated more than 40 percent of IBM’s $86 billion in sales and had become the single largest source of revenue in IBM’s portfolio. How did that happen? It was partly the result of old-fashioned hard work and serious commitment: growing customer by customer; building disciplined management and financial systems; and investing to hire and train experts in everything from IT consulting to systems architecture and Web services. IBM used its financial strength to fund the expensive push into outsourcing, and the company placed informed bets on the future in areas such as IT utility services (“e-business on demand”) and hosted storage. But most important, the success of IBM Global Services came from something very simple: a clear understanding of customers’ needs. IBM saw that technology and business were converging to create something new and challenging for every kind of enterprise. And IBM had the deep experience in both areas to help its customers bring them together most effectively. The following pages offer a brief look at the history and growth of the organization that is today IBM’s top revenue generator. Definitions What are “services?” In the IT world, that broad term has encompassed dozens of offerings and meanings, including consulting, custom programming, systems integration (designing, building and installing complex information systems), systems operations (in which a vendor runs part or all of a company’s information systems), business innovation services (such as supply chain management), strategic outsourcing, application management services, integrated technology services (such as business recovery), networking services, learning services, security services, storage services and wireless services.
    [Show full text]
  • Lynn Conway Professor of Electrical Engineering and Computer Science, Emerita University of Michigan, Ann Arbor, MI 48109-2110 [email protected]
    IBM-ACS: Reminiscences and Lessons Learned From a 1960’s Supercomputer Project * Lynn Conway Professor of Electrical Engineering and Computer Science, Emerita University of Michigan, Ann Arbor, MI 48109-2110 [email protected] Abstract. This paper contains reminiscences of my work as a young engineer at IBM- Advanced Computing Systems. I met my colleague Brian Randell during a particularly exciting time there – a time that shaped our later careers in very interesting ways. This paper reflects on those long-ago experiences and the many lessons learned back then. I’m hoping that other ACS veterans will share their memories with us too, and that together we can build ever-clearer images of those heady days. Keywords: IBM, Advanced Computing Systems, supercomputer, computer architecture, system design, project dynamics, design process design, multi-level simulation, superscalar, instruction level parallelism, multiple out-of-order dynamic instruction scheduling, Xerox Palo Alto Research Center, VLSI design. 1 Introduction I was hired by IBM Research right out of graduate school, and soon joined what would become the IBM Advanced Computing Systems project just as it was forming in 1965. In these reflections, I’d like to share glimpses of that amazing project from my perspective as a young impressionable engineer at the time. It was a golden era in computer research, a time when fundamental breakthroughs were being made across a wide front. The well-distilled and highly codified results of that and subsequent work, as contained in today’s modern textbooks, give no clue as to how they came to be. Lost in those texts is all the excitement, the challenge, the confusion, the camaraderie, the chaos and the fun – the feeling of what it was really like to be there – at that frontier, at that time.
    [Show full text]
  • Key Themes in Histories of IBM
    James W. Cortada Change and Continuity at IBM: Key Themes in Histories of IBM IBM has been the subject of considerable study by historians, economists, business management professors, and journalists. This essay surveys the various writings on the company, placing their contributions in a roughly chronological account of the company’s history, from its early days in tabulating through to its dominance of global markets in computing. The essay includes well-known studies of IBM in addition to more obscure accounts. It emphasizes the need to consider the com- pany’s culture along with its technological and managerial changes in order to grasp the reasons for its longevity. Keywords: IBM, Thomas J. Watson Sr., Thomas J. Watson Jr., Arthur K. (Dick) Watson, Herman Hollerith, IBM World Trade Corporation his essay provides a guide to the voluminous writings on IBM by Thistorians and by others whose work is useful to historians, including IBM employees and management and technology experts. This is a global history and looks at sources in English and in other lan- guages. To do so, it also traces briefly the continuities and discontinuities in IBM’s strategy and culture over time, and highlights key events in its history.1 1 For general works on IBM, see Robert Sobel, I.B.M., Colossus in Transition (New York, 1981); Saul Engelbourg, International Business Machines: A Business History (New York, 1976); James W. Cortada, Before the Computer: IBM, NCR, Burroughs, and Remington Rand and the Industry They Created, 1865–1956 (Princeton, N.J., 1993); Emerson W. Pugh, Building IBM: Shaping an Industry and Its Technology (Cambridge, Mass., 1995).
    [Show full text]
  • 13347 CICS Introduction and Overview
    CICS Introduction and Overview Ezriel Gross Circle Software Incorporated August 13th, 2013 (Tue) 4:30pm – 5:30pm Session 13347 Agenda What is CICS and Who Uses It Pseudo Conversational Programming CICS Application Services CICS Connectivity CICS Resource Definitions CICS Supplied Transactions CICS Web Services CICS The Product What is CICS? CICS is an online transaction processing system. Middleware between the operating system and business applications. Manages the user interface. Retrieves and modifies data. Handles the communication. CICS Customers Banks Mortgage Account Reconciliations Payroll Brokerage Houses Stock Trading Trade Clearing Human Resources Insurance Companies Policy Administration Accounts Receivables Claims Processing Batch Versus Online Programs The two ways to process input are batch and online. Batch requests are saved then processed sequentially. After all requests are processed the results are transmitted. Used for order entry processing such as warehouse applications. Online requests are received randomly and processed immediately. Results are transmitted as soon as they are available. Response time tends to be sub-second. Used for applications – such as: Credit Card Authorization. Transaction Processing Requirements Large volume of business transactions to be rapidly and accurately processed Multiple users, single/sysplex or distributed With potentially: – A huge number of users – Simultaneous access to data – A large volume of data residing in multiple database types – Intense security and data integrity controls necessary The access to the data is such that: – Each user has the perception of being the sole user of the system – A set of changes is guaranteed to be logically consistent. If a failure occurs, any intermediate results are undone before the system becomes available again – A completed set of changes is immediately visible to other users A Business Transaction A transaction has a 4-character id.
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • Introduction-To-Mainframes.Pdf
    Mainframe The term ‘MainFrame’ brings to mind a giant room of electronic parts that is a computer, referring to the original CPU cabinet in a computer of the mid-1960’s. Today, Mainframe refers to a class of ultra-reliable large and medium-scale servers designed for carrier-class and enterprise-class systems operations. Mainframes are costly, due to the support of symmetric multiprocessing (SMP) and dozens of central processors existing within in a single system. Mainframes are highly scalable. Through the addition of clusters, high-speed caches and volumes of memory, they connect to terabyte holding data subsystems. Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS — Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input-output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation.
    [Show full text]
  • Session Abstracts
    zSeries Expo featuring z/OS, z/VM, z/VSE and Linux on zSeries Sept. 19-23, 2005 Session Abstracts Session categories are arranged into these topic areas: Keynote Session General Sessions: · zSeries Technology and the on demand Data Center Back to the Basics: · z/OS, zSeries, z/VM, Linux on zSeries and z/VSE z/OS Sessions: L z/OS System Software and Parallel Sysplex L WLM and z/OS Performance Management L WebSphere for z/OS, CICS, DB2, Networking, and Security z/VM Sessions: Basics Networking and Connectivity General Interest System Management Security Performance Linux on zSeries Sessions: Basics l General Interest Installation l Networking Applications and Application Development User Experiences l Systems Management and Performance *Storage z/VSE Sessions: Basics Connectors General Interest Key to session prefix: A - Keynote G – zSeries Technology and the on demand Data Center B - Back to the Basics Z - z/OS System Software and Parallel Sysplex P - WLM and z/OS Performance Management W - WebSphere for z/OS, CICS, DB2, Networking, and Security V - z/VM and Virtualization L - Linux on zSeries E - z/VSE Q - ISV (Vendor) Sessions Keynote A01 zSeries: Defining the direction of enterprise computing José Castaño, Manager, zSeries Software Strategy, IBM Systems and Technology Group In the overall enterprise, zSeries is a server as well as a platform that can participate in a heterogeneous environment. This presentation will discuss the positioning of zSeries for new workloads and IBM plans and zSeries direction. José will discuss why data serving and OLTP (existing and new) belong on zSeries and how it complements the rest of the enterprise.
    [Show full text]
  • Items for the Library of Congress
    Items for the Library of Congress Item Name of item Box #/ Description/Comments No. 1 NPR program on occasion of Draper Prize (about 5 min) 1 Tape cassette 2 Photos from Draper Prize ceremony 1 Names on back of some photos 3 Think magazine article, 8/79 1 Great photos by Erich Hartmann 4 Blackboard notes, ’70 & ’71 1 Polaroid photos of work on coloring families of sets 5 Presentation at D. Univ. award, Univ. of York, England 1 2 pages 6 Old IBM memos ’53-‘82 1 Mostly about Fortran & customers 7 Interview done by Saphire of me, 12/15/67 1 Transcripts of 2 tapes, 32 + 22 pages 8 Retirement dinner – photos 1 1991 dinner in San Jose 9 Computer System Design and ANS Control Techniques Oct 1955 paper, IBM 1 Look-ahead decoder. Machine design. Confidential. 10 FORTRAN by JW Backus and WP Heising 1 Aug 1964 paper, IEEE Trans on computers 11 Software: will engineering replace witchcraft? By Eric J Lerner 1 May ’80 article about functional programming 12 Computers: emphasis on software by Robert Bernhard 1 Jan ’80, on software problems 13 Photos of Nat’l Medal of Science award ceremony 1 Pres Ford 14 Remarks at 40th anniversary dinner 1 Sept? 1990 – 40 years at IBM 15 IRI Achievement Award Address 11/83 1 Industrial Research Inst. (IRI) The talk was about tolerating many failures in doing research. 16 “Draper Prize Lecture” Boston Museum of Science + photos 1 5/10/94. 17 Lecture notes for History of Programming Languages Conf + slides 1 HOPL (1) L.A.
    [Show full text]