Using IBM Application Development Tools for z/OS and OS/390
This IBM Redbooks publication introduces the IBM Application Development Tools for z/OS and OS/390. The first chapter provides a high level overview of each of the products, suitable for any person that requires an introduction to these capabilities. The remainder of the book delivers more technical...
| Autor principal: | |
|---|---|
| Autor Corporativo: | |
| Otros Autores: | , |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
[S.l.] :
IBM, International Technical Support Organization
c2004.
|
| Edición: | 1st ed |
| Colección: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626887406719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Application development tools for z/OS and OS/390
- 1.1 Background
- 1.2 Products used during the development of this redbook
- 1.3 Getting started
- 1.4 File Manager
- 1.4.1 Overview
- 1.4.2 Major functions
- 1.5 IBM Fault Analyzer
- 1.5.1 Overview
- 1.5.2 Major functions
- 1.6 IBM Debug Tool and Utilities
- 1.6.1 Overview
- 1.6.2 Major functions
- 1.7 Application Monitor
- 1.7.1 Overview
- 1.7.2 Major functions
- 1.8 Workload Simulator
- 1.8.1 Overview
- 1.8.2 Major functions
- 1.9 Summary
- Chapter 2. Introducing File Manager
- 2.1 What can File Manager be used for?
- 2.1.1 Performance guidelines
- 2.1.2 Conventions used
- 2.1.3 A simple copy
- 2.1.4 Selective copying
- 2.1.5 How to perform a global find and replace in a PDS
- 2.1.6 How to create one VSAM file using another as a model
- 2.1.7 How to initialize a VSAM file with low-value records
- 2.1.8 How to populate this newly created file
- 2.1.9 How to split a single file into constituent record types
- 2.1.10 Replace a string in a specific location in a file
- 2.1.11 Copy selected variably blocked records to another file
- 2.1.12 Search for a string in all members of a PDS
- 2.1.13 Multiple Find
- 2.1.14 QSAM allocation using a model
- 2.1.15 Work with VTOC
- 2.1.16 Get information about a load module
- 2.1.17 Dynamic template
- 2.1.18 Compare data sets using templates
- 2.1.19 Working with DB2
- 2.1.20 Working with IMS
- 2.2 Template processing
- 2.2.1 It really does remember the copybook
- 2.2.2 Using the SELECT command in template edit
- 2.2.3 How to process COPY REPLACING statements
- 2.2.4 How to build a template for multi-record file layouts
- 2.3 Hints and tips.
- 2.3.1 System programmer notes
- 2.3.2 Look out for your PF keys
- 2.3.3 What to do when a copybook fails to compile
- 2.3.4 Record structure defined in source application program
- 2.3.5 Watch out for that bad disposition
- 2.4 Copybook and include
- Chapter 3. Introduction to Fault Analyzer
- 3.1 Start by validating your software levels
- 3.1.1 Fault Analyzer software level
- 3.2 How Fault Analyzer works
- 3.3 Preparing your programs for Fault Analyzer
- 3.3.1 Compiler options
- 3.4 Introduction to Fault Analyzer main screen
- 3.4.1 Content of Fault Entry List panel
- 3.4.2 Customization of Fault Entry List panel
- 3.5 Using FA to analyze an abend
- 3.5.1 Interactive reanalysis
- 3.5.2 Synopsis section
- 3.5.3 Point of failure section
- 3.5.4 Events section
- 3.5.5 System-wide information section
- 3.5.6 Abend job information
- 3.5.7 Options in effect section
- 3.5.8 Batch reanalysis
- 3.5.9 Real-time report
- 3.5.10 The fast-path for solving this dump
- 3.5.11 DB2 related information
- 3.5.12 CICS related information
- 3.5.13 IMS related information
- 3.6 Some very useful functions
- 3.6.1 Adding user title to a fault entry
- 3.6.2 Creating user notes in a dump
- 3.6.3 DSECT mapping
- 3.7 Customizing Fault Analyzer
- 3.7.1 User options file
- 3.7.2 Notification when program abends
- 3.7.3 Placing abends in different history files
- 3.8 Analyzing a CICS system dump
- Part 1 Application Monitor
- Chapter 4. Introduction to Workload Simulator
- 4.1 Overview
- 4.1.1 General process
- 4.1.2 WSim installation
- 4.1.3 Resources WSim can simulate
- 4.1.4 Testing with WSim
- 4.2 System configuration
- 4.2.1 Physical configurations
- 4.2.2 Logical configurations
- 4.3 Script preparation
- 4.3.1 Network definition statements
- 4.3.2 Message generation decks.
- 4.3.3 Options for creating message generation decks
- 4.3.4 Testing scripts
- 4.4 WSim output
- 4.5 Operating WSim
- 4.5.1 Initializing, starting, and stopping a network
- 4.5.2 Changing and resetting network parameters
- 4.6 WSim Test Manager
- 4.6.1 WTM operating modes
- 4.6.2 WTM utilities
- 4.6.3 Testcases
- 4.6.4 Testgroups and testcycles
- 4.6.5 Schedules
- 4.6.6 Output reports
- 4.6.7 Model scripts
- Chapter 5. Using Application Monitor
- 5.1 Why does an application developer need a profiler?
- 5.1.1 During application development
- 5.1.2 During application test
- 5.1.3 During application service
- 5.1.4 During application maintenance
- 5.1.5 Other uses
- 5.2 Some things to remember when using Application Monitor
- 5.3 Basic functionality
- 5.3.1 Analyzing an active job
- 5.3.2 Analyzing a specified job
- 5.3.3 Scheduling a deferred monitoring request
- 5.3.4 Analyzing historical data
- 5.3.5 Named sets: what they are and why they can help
- 5.4 Some available reports
- 5.4.1 Program reports
- 5.4.2 Delay Analysis reports
- 5.4.3 Data Set Analysis reports
- 5.4.4 CICS reports
- 5.4.5 DB2 reports
- 5.4.6 IMS reports
- 5.5 Things to remember when using Application Monitor
- Chapter 6. Setting Defaults for Application Monitor
- 6.1 Setting default values
- 6.2 Default sampling parameters panel
- 6.3 Default data set names panel
- Chapter 7. A Quick Application Monitor Tour: Active and post analysis
- 7.1 Using Application Monitor to monitor a running task
- 7.2 Analyzing an active job
- 7.3 Analyzing historical data
- 7.3.1 Specifying how you want to analyze the historical data
- 7.3.2 Analyzing historical data as one large segment
- 7.3.3 Analyzing historical data as multiple intervals
- 7.3.4 Analyzing a subset of the historical data
- Chapter 8. Application Monitor and COBOL
- 8.1 Overview.
- 8.2 Setting up the defaults for the analysis run
- 8.3 Analyzing the job
- 8.4 Available reports
- 8.5 Program reports
- 8.5.1 Instruction Analysis report
- 8.5.2 Statement Analysis report
- 8.6 Delay Analysis reports
- 8.7 Data Set Analysis reports
- Chapter 9. Application Monitor and PL/I
- 9.1 Overview
- 9.2 Setting the defaults
- 9.3 Analyze a specified job
- 9.4 Program reports
- 9.5 Delay Analysis reports
- 9.6 Data Set Analysis report
- Chapter 10. Application Monitor and CICS
- 10.1 Overview
- 10.2 Setup
- 10.3 Analyzing a CICS region and transaction
- 10.3.1 Available reports
- 10.3.2 Data Set Analysis report
- 10.3.3 Delay Analysis report
- 10.3.4 CICS specific reports
- 10.3.5 Program reports
- 10.4 History files and historical data analysis
- Chapter 11. Application Monitor: Generating reports in batch
- 11.1 Overview
- 11.2 The JCL - SFBIJCL(FBIBATCH)
- Part 2 Debug Tool
- Chapter 12. Introducing the Debug Tool debugger interfaces
- 12.1 Batch mode user interface
- 12.2 Main frame interface
- 12.2.1 Review of screen areas
- 12.3 WebSphere Studio Enterprise Developer
- 12.4 IBM Distributed Debugger/VisualAge Remote Debugger
- 12.5 Matching interfaces to supported environments
- Chapter 13. Specifying the TEST runtime option in Debug Tool
- 13.1 Anatomy of the TEST runtime option
- 13.1.1 Specifying file names in the TEST runtime option
- 13.1.2 Recommended allocations for command and preference files
- 13.1.3 Sample runtime options
- 13.2 Specifying the TEST runtime option
- 13.2.1 Defining runtime options using CEEUOPT
- 13.2.2 Specifying the TEST runtime option on the command line
- 13.2.3 Specifying the TEST runtime option on JCL
- Chapter 14. Some useful Debug Tool commands
- 14.1 Descriptions of frequently used commands
- 14.2 Descriptions of some interesting commands.
- 14.3 Finishing a Debug Tool session
- Chapter 15. Debug Tool and debugging PL/I
- 15.1 Preparing a PL/I program for debugging
- 15.1.1 Notes on preparing a PL/I V2R3 program for Debug Tool
- 15.1.2 Notes on all other PL/I compilers
- 15.2 A quick run through the program
- 15.3 A quick test using the MFI debugger
- 15.4 A debug session with the remote debugger
- Chapter 16. Debug Tool and debugging COBOL
- 16.1 Preparing IBM Enterprise COBOL for z/OS and OS/390 using Debug Tool Utilities
- 16.2 Manage and use Debug Tool setup files
- Chapter 17. Debug Tool and debugging C/C++
- 17.1 Preparing a C or C++ program for debugging
- 17.2 Using the MFI debugger
- 17.3 Using the remote debugger
- 17.4 Using the ctest() function to start the debugger
- 17.4.1 Using the ctest() function
- 17.4.2 Specifying runopts when using ctest()
- 17.4.3 Example
- Chapter 18. Using Debug Tool under UNIX System Services
- 18.1 Common considerations for all languages
- 18.1.1 Specifying the TEST runtime option
- 18.1.2 Special considerations for running DLL applications from the shell
- 18.2 Using C/C++ and Debug Tool under USS
- 18.2.1 Compiling a C/C++ application
- 18.2.2 Debugging a USS application
- Chapter 19. Using Debug Tool with IMS
- 19.1 Traditional methods of debugging under IMS
- 19.2 Debugging with IMS V8 and above
- 19.2.1 Linking an application to allow the managing of runtime options
- 19.2.2 A tour of the new DTU IMS facilities
- 19.2.3 Precedence of the information on the LE Runtime Options panel
- Chapter 20. Using Debug Tool with CICS
- 20.1 CICS application program considerations
- 20.2 Invoking Debug Tool
- Chapter 21. Using Debug Tool with DB2
- 21.1 Compiling for DB2 and Debug Tool
- 21.2 Invoking a DB2 application using the TEST runtime option
- 21.3 Using DTSU to invoke your DB2 application.
- 21.4 DB2 stored procedures considerations.
