DOCSLIB.ORG

IBM Z/OS Debugger V14.1.7 User's Guide Specifying TEST Run-Time Option with #Pragma Ending a CICS Debugging Session That Was Runopts in C and C++

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Z/OS Debugger V14.1.7 User's Guide Specifying TEST Run-Time Option with #Pragma Ending a CICS Debugging Session That Was Runopts in C and C++ IBM z/OS Debugger IBM User's Guide Version 14.1.7 SC27-4642-05 IBM z/OS Debugger IBM User's Guide Version 14.1.7 SC27-4642-05 Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page 581. Sixth Edition (June 2019) This edition applies to IBM z/OS Debugger, Version 14.1.7 (Program Number 5724-T07 with the PTF for APAR | PH07787), which supports the following compilers: v AD/Cycle C/370 Version 1 Release 2 (Program Number 5688-216) v C/C++ for MVS/ESA Version 3 (Program Number 5655-121) v C/C++ feature of OS/390 (Program Number 5647-A01) v C/C++ feature of z/OS Version 1 (Program Number 5694-A01) v C/C++ feature of z/OS Version 2 (Program Number 5650-ZOS) v OS/VS COBOL, Version 1 Release 2.4 (5740-CB1) - with limitations v VS COBOL II Version 1 Release 3 and Version 1 Release 4 (Program Numbers 5668-958, 5688-023) - with limitations v COBOL/370 Version 1 Release 1 (Program Number 5688-197) v COBOL for MVS & VM Version 1 Release 2 (Program Number 5688-197) v COBOL for OS/390 & VM Version 2 (Program Number 5648-A25) v Enterprise COBOL for z/OS and OS/390 Version 3 (Program Number 5655-G53) v Enterprise COBOL for z/OS Version 4 (Program Number 5655-S71) v Enterprise COBOL for z/OS Version 5 (Program Number 5655-W32) v Enterprise COBOL for z/OS Version 6 Release 1 and 2 (Program Number 5655-EC6) v High Level Assembler for MVS & VM & VSE Version 1 Release 4, Version 1 Release 5, Version 1 Release 6 (Program Number 5696-234) v OS PL/I Version 2 Release 1, Version 2 Release 2, Version 2 Release 3 (Program Numbers 5668-909, 5668-910) - with limitations v PL/I for MVS & VM Version 1 Release 1 (Program Number 5688-235) v VisualAge PL/I for OS/390 Version 2 Release 2 (Program Number 5655-B22) v Enterprise PL/I for z/OS and OS/390 Version 3 (Program Number 5655-H31) v Enterprise PL/I for z/OS Version 4 (Program Number 5655-W67) v Enterprise PL/I for z/OS Version 5 Release 1 and 2 (Program Number 5655-PL5) This edition also applies to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters. You can access publications online at www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss You can find out more about IBM z/OS Debugger by visiting the following IBM Web sites: v IBM Debug for z Systems: https://www.ibm.com/us-en/marketplace/debug-for-z-systems v IBM Developer for z Systems: https://www.ibm.com/us-en/marketplace/developer-for-z-systems v IBM Z Open Development: https://www.ibm.com/us-en/marketplace/z-open-development v IBM Z Open Unit Test: https://www.ibm.com/us-en/marketplace/z-open-unit-test © Copyright IBM Corporation 1992, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document ........ xiii IBM z/OS Debugger Utilities: z/OS Debugger Who might use this document ........ xiii JCL Wizard ............. 10 Accessing z/OS licensed documents on the Internet xiii Starting IBM z/OS Debugger Utilities .... 10 How this document is organized ....... xiv Terms used in this document ........ xvii Chapter 2. Debugging a program in How to read syntax diagrams ....... xviii full-screen mode: introduction .... 11 Symbols .............. xviii Compiling or assembling your program with the Syntax items ............. xix proper compiler options .......... 11 Syntax examples ........... xix Starting z/OS Debugger .......... 12 How to send your comments ........ xx The z/OS Debugger full screen interface .... 13 Stepping through a program......... 14 Summary of changes........ xxiii Running your program to a specific line..... 14 Setting a breakpoint ........... 15 IBM z/OS Debugger as a component xxix Displaying the value of a variable ....... 15 Displaying memory through the Memory window 17 Changing the value of a variable ....... 17 Part 1. Getting started with z/OS Skipping a breakpoint ........... 18 Debugger ............. 1 Clearing a breakpoint ........... 18 Recording and replaying statements ...... 18 Chapter 1. z/OS Debugger: overview .. 3 Stopping z/OS Debugger.......... 19 z/OS Debugger interfaces .......... 4 Batch mode.............. 5 Part 2. Preparing your program for Full-screen mode ............ 5 debugging ............ 21 Full-screen mode using the Terminal Interface Manager............... 5 Remote debug mode........... 6 Chapter 3. Preparing to remote debug IBM z/OS Debugger Utilities ......... 7 in standard mode .......... 23 IBM z/OS Debugger Utilities: Job Card .... 7 IBM z/OS Debugger Utilities: Program Chapter 4. Planning your debug Preparation .............. 7 session .............. 25 IBM z/OS Debugger Utilities: z/OS Debugger Choosing compiler options for debugging .... 26 Setup File .............. 8 Choosing TEST or NOTEST compiler suboptions IBM z/OS Debugger Utilities: IMS TM Debugging 8 for COBOL programs .......... 27 IBM z/OS Debugger Utilities: Load Module Choosing TEST or NOTEST compiler suboptions Analyzer............... 8 for PL/I programs ........... 35 IBM z/OS Debugger Utilities: z/OS Debugger Choosing TEST or DEBUG compiler suboptions User Exit Data Set ........... 8 for C programs ............ 41 IBM z/OS Debugger Utilities: Other IBM Choosing TEST or DEBUG compiler suboptions Application Delivery Foundation for z Systems for C++ programs ........... 46 tools ................ 8 Understanding how hooks work and why you IBM z/OS Debugger Utilities: JCL for Batch need them .............. 50 Debugging .............. 8 Understanding what symbol tables do and why IBM z/OS Debugger Utilities: IMS BTS Debugging 9 saving them elsewhere can make your IBM z/OS Debugger Utilities: JCL to Setup File application smaller ........... 51 Conversion .............. 9 Choosing a debugging mode ........ 52 IBM z/OS Debugger Utilities: Delay Debug Profile 9 Debugging in browse mode ........ 54 IBM z/OS Debugger Utilities: IMS Transaction Choosing a method or methods for starting z/OS and User ID Cross Reference Table ...... 9 Debugger ............... 57 IBM z/OS Debugger Utilities: Non-CICS Debug Choosing how to debug old COBOL programs .. 60 Session Start and Stop Message Viewer .... 9 Creating deferred breakpoints for COBOL and PL/I IBM z/OS Debugger Utilities: z/OS Debugger programs ............... 61 Code Coverage ............ 9 IBM z/OS Debugger Utilities: z/OS Debugger Deferred Breakpoints .......... 9 © Copyright IBM Corp. 1992, 2019 iii Chapter 5. Updating your processes so Creating and storing debugging profiles with you can debug programs with z/OS CADP ................ 101 Debugger ............. 63 Starting z/OS Debugger for non-Language Environment programs under CICS ...... 102 Update your compilation, assembly, and linking Passing runtime parameters to z/OS Debugger process ................ 63 for non-Language Environment programs under Compiling your program without using IBM CICS ............... 102 z/OS Debugger Utilities ......... 63 Compiling your program by using IBM z/OS Debugger Utilities ........... 65 Chapter 11. Preparing an IMS program 105 Compiling a Enterprise PL/I program on an HFS Starting z/OS Debugger under IMS by using or zFS file system ........... 66 CEEUOPT or CEEROPT .......... 105 Compiling your C program with c89 or c++ .. 67 Managing runtime options for IMSplex users by Compiling a C program on an HFS or zFS file using IBM z/OS Debugger Utilities ...... 106 system ............... 67 Setting up the DFSBXITA user exit routine ... 106 Compiling a C++ program on an HFS or zFS file system ............... 68 Chapter 12. Specifying the TEST Update your library and promotion process ... 68 runtime options through the Make the modifications necessary to implement Language Environment user exit ... 109 your preferred method of starting z/OS Debugger . 69 Editing the source code of CEEBXITA ..... 110 Modifying the naming pattern....... 110 Chapter 6. Preparing a LangX COBOL Modifying the message display level .... 111 program .............. 73 Modifying the call back routine registration .. 112 Compiling your OS/VS COBOL program .... 73 Activate the cross reference function and Compiling your VS COBOL II program ..... 74 modifying the cross reference table data set Compiling your Enterprise COBOL program ... 74 name ............... 112 Creating the EQALANGX file for LangX COBOL Comparing the two methods of linking CEEBXITA 112 programs ............... 74 Linking the CEEBXITA user exit into your Link-editing your program ......... 76 application program ........... 113 Linking the CEEBXITA user exit into a private copy Chapter 7. Preparing an assembler of a Language Environment runtime module ... 113 program .............. 77 Creating and managing the TEST runtime options data set ............... 114 Before you assemble your program ...... 77 Creating and managing the TEST runtime Assembling your program ......... 77 options data set by using Terminal Interface Creating the EQALANGX file for an assembler Manager (TIM) ............ 115 program ............... 78 Creating and managing the TEST runtime Assembling your program and creating options data set by using IBM z/OS Debugger EQALANGX .............. 79 Utilities .............. 117 Link-editing your program ......... 80 Restrictions for link-editing your assembler program .............. 80 Part 3. Starting z/OS Debugger 119 Chapter 8. Preparing a DB2 program 81 Chapter 13. Writing the TEST run-time Processing SQL statements ......... 81 option string............ 121 Linking DB2 programs for debugging ..... 83 Special considerations while using the TEST Binding DB2 programs for debugging ..... 84 run-time option ............ 121 Defining TEST suboptions in your program .. 121 Chapter 9. Preparing a DB2 stored Suboptions and NOTEST ........ 121 procedures program ......... 85 Implicit breakpoints .......... 122 Primary commands file and USE file .... 122 Chapter 10. Preparing a CICS program 89 Running in batch mode ......... 122 Starting z/OS Debugger at different points .. 122 Link-editing EQADCCXT into your program ... 89 Session log ............. 123 Creating and storing a DTCN profile ...... 90 Precedence of Language Environment runtime Displaying a list of active DTCN profiles and options ..............
Load more

Recommended publications
  • IBM Developer for Z/OS Enterprise Edition
    Solution Brief IBM Developer for z/OS Enterprise Edition A comprehensive, robust toolset for developing z/OS applications using DevOps software delivery practices Companies must be agile to respond to market demands. The digital transformation is a continuous process, embracing hybrid cloud and the Application Program Interface (API) economy. To capitalize on opportunities, businesses must modernize existing applications and build new cloud native applications without disrupting services. This transformation is led by software delivery teams employing DevOps practices that include continuous integration and continuous delivery to a shared pipeline. For z/OS Developers, this transformation starts with modern tools that empower them to deliver more, faster, with better quality and agility. IBM Developer for z/OS Enterprise Edition is a modern, robust solution that offers the program analysis, edit, user build, debug, and test capabilities z/OS developers need, plus easy integration with the shared pipeline. The challenge IBM z/OS application development and software delivery teams have unique challenges with applications, tools, and skills. Adoption of agile practices Application modernization “DevOps and agile • Mainframe applications • Applications require development on the platform require frequent updates access to digital services have jumped from the early adopter stage in 2016 to • Development teams must with controlled APIs becoming common among adopt DevOps practices to • The journey to cloud mainframe businesses”1 improve their
    [Show full text]
  • Tricore™ Tricore™ V1.6 Microcontrollers User Manual
    TriCore™ 32-bit TriCore™ V1.6 Core Architecture 32-bit Unified Processor Core User Manual (Volume 1) V1.0, 2012-05 Microcontrollers Edition 2012-05 Published by Infineon Technologies AG 81726 Munich, Germany © 2012 Infineon Technologies AG All Rights Reserved. Legal Disclaimer The information given in this document shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, Infineon Technologies hereby disclaims any and all warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual property rights of any third party. Information For further information on technology, delivery terms and conditions and prices, please contact the nearest Infineon Technologies Office (www.infineon.com). Warnings Due to technical requirements, components may contain dangerous substances. For information on the types in question, please contact the nearest Infineon Technologies Office. Infineon Technologies components may be used in life-support devices or systems only with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system or to affect the safety or effectiveness of that device or system. Life support devices or systems are intended to be implanted in the human body or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered.
    [Show full text]
  • PRE LIM INARY KDII-D Processor Manual (PDP-Ll/04)
    PRE LIM I N A R Y KDII-D Processor Manual (PDP-ll/04) The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this manual. Copyright C 1975 by Digital Equipment Corporation Written by PDP-II Engineering PREFACE OVE~ALt DESCRIPTION 3 8 0 INsT~UCTION SET 3~1 Introduction 1~2 Addressing ModIs 3.3 Instruction Timing l@4 In~truet1on Dtlcriptlonl le!5 Dlffer~ncei a,tween KOlle and KOllS ]0 6 Programming Diftereneel B~twlen pepita ).7 SUI L~tency Tim@1 CPu OPERlTING 5PECIFICATID~S 5 e 0 DETAILED HARDWARE DESC~ltTION 5.1 IntrOduction 5 m2 Data path Circuitry 5.2g1 General D~serlpt1on 5.2,,2 ALU 5,2 .. 3 Scratch Pad Mtmory 5.2,.3.1 Scratch P~d Circuitry 5.2.3.2 SCrateh P~d Addr~11 MUltlplex.r 5.2.3.3 SCrateh Pad Regilter 5 0 2 .. 4 B J:H'!qilil ter 5.2 .. 4.1 B ReQister CircuItry 5.2 .. 4.2 8 L~G MUltl~lex@r 5,2.5 AMUX 5.2.6 Pfoeellof statuI Word (PSW) 5.3 Con<Htion COd@i 5.3.1 G~neral De~erl~tlon 5.3.2 Carry and overflow Decode 5.3.3 Ayte Multiplexing 5.4 UNIBUS Addf@$5 and Data Interfaces S.4 g 1 U~IBUS Dr1v~rl and ~lee1Vtrl 5.4@2 Bus Addr~s~ Generation 5 8 4111 Internal Addrf$$ D@coder 5 0 4,.4 Bus Data Line Interface S.5 Instruet10n DeCoding 5.5,,1 General De~er1pt1nn 5;5.2 Instruction Re91lt~r 5.5,,3 Instruetlon Decoder 5.5.3 0 1 Doubl~ O~erand InltrYetions 5.5.3.2 Single Operand Inltruetlons 5,5.3.3 Branch In$truetionl 5 8 5.3 6 4 Op~rate rn~truet1ons 5.6 Auil11ary ALU Control 5.6.1 G~ntral Delcrlptlon 5.6.2 COntrol Circuitry 5.6.2.1 Double Op@rand Instructions 5.6.2.2 Singl@ nDef~nd Instruet10ns PaQe 3 5.7 Data Transfer Control 5,7,1 General Descr1ption 5,7,2 Control CIrcuItry 5,7,2,1 Procelsor Cloek Inhibit 5,7,2.2 UNIBUS Synchronization 5,7.2,3 BUs Control 5.7,2.4 MSyN/SSYN Timeout 5,7.2.5 Bus Error.
    [Show full text]
  • Global SCRUM GATHERING® Berlin 2014
    Global SCRUM GATHERING Berlin 2014 SESSION DESCRIPTION TABLE OF CONTENTS SESSION TIMETABLE Monday, September 22nd – AM Sessions WELCOME & OPENING KEYNOTE - 9:00 – 10:30 Welcome Remarks ROOM Dave Sharrock & Marion Eickmann Opening Keynote Potsdam I/III Enabling the organization as a complex eco-system Dave Snowden AM BREAK – 10:30 – 11:00 90 MINUTE SESSIONS - 11:00 – 12:30 SESSION & SPEAKER TRACK LEVEL ROOM Managing Agility: Effectively Coaching Agile Teams Bring Down the Performing Tegel Andrea Tomasini, Bent Myllerup Wall Temenos – Build Trust in Yourself, Your Team, Successful Scrum Your Organization Practices: Berlin Norming Bellevue Christine Neidhardt, Olaf Lewitz Never Sleeps A Curious Mindset: basic coaching skills for Managing Agility: managers and other aliens Bring Down the Norming Charlottenburg II Deborah Hartmann Preuss, Steve Holyer Wall Building Creative Teams: Ideas, Motivation and Innovating beyond Retrospectives Core Scrum: The Performing Charlottenburg I Cara Turner Bohemian Bear Scrum Principles: Building Metaphors for Retrospectives Changing the Forming Tiergarted I/II Helen Meek, Mark Summers Status Quo Scrum Principles: My Agile Suitcase Changing the Forming Charlottenburg III Martin Heider Status Quo Game, Set, Match: Playing Games to accelerate Thinking Outside Agile Teams Forming Kopenick I/II the box Robert Misch Innovating beyond Let's Invent the Future of Agile! Core Scrum: The Performing Postdam III Nigel Baker Bohemian Bear Monday, September 22nd – PM Sessions LUNCH – 12:30 – 13:30 90 MINUTE SESSIONS - 13:30
    [Show full text]
  • Debugging a Program
    Debugging a Program SunPro A Sun Microsystems, Inc. Business 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. Part No: 801-5106-10 Revision A December 1993 1993 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® and Berkeley 4.3 BSD systems, licensed from UNIX System Laboratories, Inc. and the University of California, respectively. Third-party font software in this product is protected by copyright and licensed from Sun’s Font Suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, Sun Microsystems, the Sun logo, SunPro, SunPro logo, Sun-4, SunOS, Solaris, ONC, OpenWindows, ToolTalk, AnswerBook, and Magnify Help are trademarks or registered trademarks of Sun Microsystems, Inc. UNIX and OPEN LOOK are registered trademarks of UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc. All other product names mentioned herein are the trademarks of their respective owners. All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Exceptions and Processes
    Exceptions and Processes! Jennifer Rexford! The material for this lecture is drawn from! Computer Systems: A Programmerʼs Perspective (Bryant & O"Hallaron) Chapter 8! 1 Goals of this Lecture! •#Help you learn about:! •# Exceptions! •# The process concept! … and thereby…! •# How operating systems work! •# How applications interact with OS and hardware! The process concept is one of the most important concepts in systems programming! 2 Context of this Lecture! Second half of the course! Previously! Starting Now! C Language! Application Program! language! service! levels! Assembly Language! levels! Operating System! tour! tour! Machine Language! Hardware! Application programs, OS,! and hardware interact! via exceptions! 3 Motivation! Question:! •# How does a program get input from the keyboard?! •# How does a program get data from a (slow) disk?! Question:! •# Executing program thinks it has exclusive control of CPU! •# But multiple programs share one CPU (or a few CPUs)! •# How is that illusion implemented?! Question:! •# Executing program thinks it has exclusive use of memory! •# But multiple programs must share one memory! •# How is that illusion implemented?! Answers: Exceptions…! 4 Exceptions! •# Exception! •# An abrupt change in control flow in response to a change in processor state! •# Examples:! •# Application program:! •# Requests I/O! •# Requests more heap memory! •# Attempts integer division by 0! •# Attempts to access privileged memory! Synchronous! •# Accesses variable that is not$ in real memory (see upcoming $ “Virtual Memory” lecture)! •# User presses key on keyboard! Asynchronous! •# Disk controller finishes reading data! 5 Exceptions Note! •# Note:! ! !Exceptions in OS % exceptions in Java! Implemented using! try/catch! and throw statements! 6 Exceptional Control Flow! Application! Exception handler! program! in operating system! exception! exception! processing! exception! return! (optional)! 7 Exceptions vs.
    [Show full text]
  • Providing Memory Performance Feedback in Modern Processors
    Informing Memory Operations: Providing Memory Performance Feedback in Modern Processors Mark Horowitz Margaret Martonosi Todd C. Mowry Michael D. Smith Computer Systems Department of Department of Electrical Division of Laboratory Electrical Engineering and Computer Engineering Applied Sciences Stanford University Princeton University University of Toronto Harvard University [email protected] [email protected] [email protected] [email protected] Abstract other purely hardware-based mechanisms (e.g., stream buffers [Jou90]) are complete solutions. Memory latency is an important bottleneck in system performance that cannot be adequately solved by hardware alone. Several prom- In addition to hardware mechanisms, a number of promising soft- ising software techniques have been shown to address this problem ware techniques have been proposed to avoid or tolerate memory successfully in specific situations. However, the generality of these latency. These software techniques have resorted to a variety of software approaches has been limited because current architectures different approaches for gathering information and reasoning about do not provide a fine-grained, low-overhead mechanism for memory performance. Compiler-based techniques, such as cache observing and reacting to memory behavior directly. To fill this blocking [AKL79,GJMS87,WL91] and prefetching [MLG92, need, we propose a new class of memory operations called inform- Por89] use static program analysis to predict which references are ing memory operations, which essentially consist of a memory likely to suffer misses. Memory performance tools have relied on operation combined (either implicitly or explicitly) with a condi- sampling or simulation-based approaches to gather memory statis- tional branch-and-link operation that is taken only if the reference tics [CMM+88,DBKF90,GH93,LW94,MGA95].
    [Show full text]
  • High Performance Computing Toolkit: Installation and Usage Guide | Appendix B
    IBM Parallel Environment Developer Edition High Performance Computing Toolkit Version 2 Release 1 Installation and Usage Guide SC23-7287-00 IBM Parallel Environment Developer Edition High Performance Computing Toolkit Version 2 Release 1 Installation and Usage Guide SC23-7287-00 Note Before using this information and the product it supports, read the information in “Notices” on page 255. This edition applies to version 2, release 1, modification 0 of the IBM Parallel Environment Developer Edition High Performance Computing Toolkit (HPC Toolkit) (product number 5765-PD2) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2008, 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ..............vii | Part 3. Using the IBM PE Developer | Edition graphical performance Tables ...............ix || analysis tools ...........21 About this information ........xi | Chapter 6. Using the hpctView Who should read this information .......xi Conventions and terminology used in this || application .............23 information ..............xi || Preparing an application for analysis ......24 Prerequisite and related information ......xii || Working with the application ........25 Parallel Tools Platform component .....xii || Opening the application executable ......25 How to send your comments ........xiii || Instrumenting the application ........28 || Running the instrumented application .....29 Summary of changes ........xv || Viewing performance data .........37 | Chapter 7. Using hardware Limitations and restrictions .....xvii || performance counter profiling.....41 || Preparing an application for profiling......41 Part 1. Introduction .........1 || Instrumenting the application ........41 || Running the instrumented application .....43 Chapter 1. Introduction to the IBM HPC || Viewing hardware performance counter data . 45 Toolkit ...............3 IBM PE Developer Edition components .....3 || Chapter 8.
    [Show full text]
  • Enabling Devops on Premise Or Cloud with Jenkins
    Enabling DevOps on Premise or Cloud with Jenkins Sam Rostam [email protected] Cloud & Enterprise Integration Consultant/Trainer Certified SOA & Cloud Architect Certified Big Data Professional MSc @SFU & PhD Studies – Partial @UBC Topics The Context - Digital Transformation An Agile IT Framework What DevOps bring to Teams? - Disrupting Software Development - Improved Quality, shorten cycles - highly responsive for the business needs What is CI /CD ? Simple Scenario with Jenkins Advanced Jenkins : Plug-ins , APIs & Pipelines Toolchain concept Q/A Digital Transformation – Modernization As stated by a As established enterprises in all industries begin to evolve themselves into the successful Digital Organizations of the future they need to begin with the realization that the road to becoming a Digital Business goes through their IT functions. However, many of these incumbents are saddled with IT that has organizational structures, management models, operational processes, workforces and systems that were built to solve “turn of the century” problems of the past. Many analysts and industry experts have recognized the need for a new model to manage IT in their Businesses and have proposed approaches to understand and manage a hybrid IT environment that includes slower legacy applications and infrastructure in combination with today’s rapidly evolving Digital-first, mobile- first and analytics-enabled applications. http://www.ntti3.com/wp-content/uploads/Agile-IT-v1.3.pdf Digital Transformation requires building an ecosystem • Digital transformation is a strategic approach to IT that treats IT infrastructure and data as a potential product for customers. • Digital transformation requires shifting perspectives and by looking at new ways to use data and data sources and looking at new ways to engage with customers.
    [Show full text]
  • Integrating the GNU Debugger with Cycle Accurate Models a Case Study Using a Verilator Systemc Model of the Openrisc 1000
    Integrating the GNU Debugger with Cycle Accurate Models A Case Study using a Verilator SystemC Model of the OpenRISC 1000 Jeremy Bennett Embecosm Application Note 7. Issue 1 Published March 2009 Legal Notice This work is licensed under the Creative Commons Attribution 2.0 UK: England & Wales License. To view a copy of this license, visit http://creativecommons.org/licenses/by/2.0/uk/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. This license means you are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must give the original author, Jeremy Bennett of Embecosm (www.embecosm.com), credit; • For any reuse or distribution, you must make clear to others the license terms of this work; • Any of these conditions can be waived if you get permission from the copyright holder, Embecosm; and • Nothing in this license impairs or restricts the author's moral rights. The software for the SystemC cycle accurate model written by Embecosm and used in this document is licensed under the GNU General Public License (GNU General Public License). For detailed licensing information see the file COPYING in the source code. Embecosm is the business name of Embecosm Limited, a private limited company registered in England and Wales. Registration number 6577021. ii Copyright © 2009 Embecosm Limited Table of Contents 1. Introduction ................................................................................................................ 1 1.1. Why Use Cycle Accurate Modeling .................................................................... 1 1.2. Target Audience ................................................................................................ 1 1.3. Open Source ..................................................................................................... 2 1.4. Further Sources of Information ......................................................................... 2 1.4.1.
    [Show full text]
  • Program Directory for IBM Enterprise COBOL for Z/OS
    IBM Program Directory for IBM Enterprise COBOL for z/OS V06.02.00 Program Number 5655-EC6 FMIDs HADB620, JADB621, JADB622, JADB62H for Use with z/OS Document Date: September 2017 GI13-4526-01 Note Before using this information and the product it supports, be sure to read the general information under 7.0, “Notices” on page 30. © Copyright International Business Machines Corporation 1991, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents 1.0 Introduction . 1 1.1 Enterprise COBOL Description ......................................... 1 1.2 Enterprise COBOL FMIDs ........................................... 4 2.0 Program Materials . 5 2.1 Basic Machine-Readable Material ....................................... 5 2.2 Optional Machine-Readable Material ..................................... 6 2.3 Program Publications . 6 2.3.1 Optional Program Publications ...................................... 7 2.4 Program Source Materials ........................................... 7 2.5 Publications Useful During Installation .................................... 7 3.0 Program Support . 8 3.1 Program Services . 8 3.2 Preventive Service Planning .......................................... 8 3.3 Statement of Support Procedures ....................................... 9 4.0 Program and Service Level Information ................................. 10 4.1 Program Level Information .......................................... 10 4.2 Service Level Information ..........................................
    [Show full text]
  • Chapter 3 Protected-Mode Memory Management
    CHAPTER 3 PROTECTED-MODE MEMORY MANAGEMENT This chapter describes the Intel 64 and IA-32 architecture’s protected-mode memory management facilities, including the physical memory requirements, segmentation mechanism, and paging mechanism. See also: Chapter 5, “Protection” (for a description of the processor’s protection mechanism) and Chapter 20, “8086 Emulation” (for a description of memory addressing protection in real-address and virtual-8086 modes). 3.1 MEMORY MANAGEMENT OVERVIEW The memory management facilities of the IA-32 architecture are divided into two parts: segmentation and paging. Segmentation provides a mechanism of isolating individual code, data, and stack modules so that multiple programs (or tasks) can run on the same processor without interfering with one another. Paging provides a mech- anism for implementing a conventional demand-paged, virtual-memory system where sections of a program’s execution environment are mapped into physical memory as needed. Paging can also be used to provide isolation between multiple tasks. When operating in protected mode, some form of segmentation must be used. There is no mode bit to disable segmentation. The use of paging, however, is optional. These two mechanisms (segmentation and paging) can be configured to support simple single-program (or single- task) systems, multitasking systems, or multiple-processor systems that used shared memory. As shown in Figure 3-1, segmentation provides a mechanism for dividing the processor’s addressable memory space (called the linear address space) into smaller protected address spaces called segments. Segments can be used to hold the code, data, and stack for a program or to hold system data structures (such as a TSS or LDT).
    [Show full text]