Introduction to the IBM application development tools for z/OS and OS/390 / [Sylvie Delahaye, Sergei Litvak, Wilfried Van Hecke].

Format:

Book

Author/Creator:

Delahaye, Sylvie.

Contributor:

Litvak, Sergei.

Hecke, Wilfried van.

Series:

IBM redbooks.

Redbooks

Language:

English

Subjects (All):

Application software--Development.

Application software.

z/OS.

Physical Description:

1 online resource (540 p.)

Edition:

1st ed.

Other Title:

Application development tools for z/OS and OS/390

Place of Publication:

[San Jose, Calif.?] : IBM International Technical Support Organization, 2002.

Language Note:

English

System Details:

text file

Summary:

This IBM Redbooks publication describes the IBM Application Development Tools for z/OS and OS/390 and includes scenarios that show how to use the tools to recognize, locate, and fix errors in application programs. Part 1 describes the five program products that make up the suite and product integration : -> IBM Fault Analyzer -> IBM File Manager -> IBM Debug Tool -> IBM Application Monitor -> IBM Workload Simulator. Part 2 walks you through detailed scenarios that demonstrate how the tools can be used in a practical, day-to-day manner. Part 3 contains code samples, reports and listings, and examples that are too large to include in the chapters.

Contents:

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Become a published author

Comments welcome

Part 1 The IBM Application Development Tools for z/OS and OS/390

Chapter 1. Application development tools for z/OS and OS/390

1.1 General background

1.2 Products used during the making of this redbook

1.3 IBM Fault Analyzer

1.3.1 Fault history file

1.3.2 Supported languages

1.3.3 Product requirements

1.3.4 User exits

1.3.5 Latest software update

1.4 IBM File Manager

1.4.1 Three features

1.4.2 Online processing

1.4.3 Enhanced batch processing

1.4.4 Latest software upgrades

1.5 IBM Debug Tool

1.5.1 Full-screen debugging

1.5.2 Debugging tasks

1.5.3 Recently available features

1.6 Application Monitor

1.6.1 Overview

1.6.2 Functions

1.6.3 Interface

1.7 Workload Simulator

1.7.1 Simulated resources

1.7.2 Physical and logical configurations

1.7.3 Scripts

1.7.4 WSim output

1.7.5 WSim Test Manager

1.8 Summary

Chapter 2. Introducing File Manager

2.1 Start by validating your software levels

2.1.1 PTF information

2.2 Useful examples of how to use File Manager

2.2.1 Conventions used

2.2.2 How to perform a global find and replace in a PDS

2.2.3 How to create one VSAM file using another as a model

2.2.4 How to initialize a VSAM file with low-value records

2.2.5 How to split a single file into constituent record types

2.3 Useful batch utilities

2.3.1 Replace a string in a specific location in a file

2.3.2 Copy selected variably blocked records to another file

2.3.3 Search for a string in all members of a PDS

2.4 Template processing

2.4.1 It really does remember the copybook

2.4.2 How to process COPY REPLACING statements

2.4.3 How to build a template for multi-record file layouts.

2.4.4 System programmer notes

2.4.5 Look out for your PF keys

2.4.6 How to quickly locate a record in browse

2.4.7 What to do when a copybook fails to compile

2.4.8 Record structure defined in source application program

2.4.9 Watch out for that bad disposition

2.5 Copybook and include

2.6 Product updates

2.6.1 Multiple Find with Version 3

2.6.2 QSAM allocation using a model

2.6.3 Work with VTOC

2.6.4 Get information about a load module

2.6.5 Dynamic template

2.6.6 Compare data sets using templates

2.6.7 Edit related tables

2.6.8 Load IMS database

Chapter 3. Introduction to Debug Tool and Debug Tool Utilities and Advanced Functions V3.1

3.1 Start by validating your software levels

3.1.1 APAR information

3.2 What you need to prepare your application program

3.2.1 A description of the TEST compile option

3.2.2 Required files

3.2.3 Link-edit options

3.2.4 Defining run-time options using CEEUOPT

3.2.5 Sample batch compile job

3.2.6 Compile and link your program by using Debug Tool utilities

3.2.7 Summary

3.3 What are the Debug Tool user interfaces

3.3.1 Batch mode user interface

3.3.2 Main frame interface (MFI)

3.3.3 Remote debugger interface

3.3.4 Summary

3.4 What it takes to debug your application program

3.4.1 A description of the TEST run-time option

3.4.2 How to determine your site's run-time options

3.4.3 What else is required

3.4.4 Debug Tool's supporting files

3.4.5 Batch invocation

3.4.6 Testing an application in TSO

3.4.7 Testing an application using DTSU

3.4.8 Testing multiple step batch applications

3.4.9 DB2 application program considerations

3.4.10 DB2 stored procedures considerations

3.4.11 IMS application program considerations

3.4.12 CICS application program considerations.

3.4.13 Unix System Services programs considerations

3.5 The primary interface for Debug Tool

3.5.1 Review of screen areas

3.5.2 Descriptions of frequently used commands

3.5.3 Descriptions of some interesting commands

3.5.4 Finishing a Debug Tool session

3.5.5 Recording how many times each source line runs

3.6 New features of Debug Tool

3.6.1 Playback support (COBOL)

3.6.2 Automonitor support

3.6.3 Support for optimized code (COBOL)

3.6.4 Enhancements for TSO allocation commands

3.6.5 Assembler support

3.7 Dynamic Debug and separate debug file

3.7.1 Dynamic Debug

3.7.2 Separate debug file

3.7.3 Advantages

3.7.4 How this helps application programmers

3.8 Making debugging more comfortable

3.8.1 INSPSAFE

3.8.2 INSPPREF

3.8.3 INSPCMD

3.8.4 INSPLOG

3.8.5 Copy into the command line

3.8.6 What if I forgot the correct command syntax

3.9 Hints and tips

3.9.1 I only have 12 PF keys

3.9.2 Pitfalls

3.9.3 Systems programmer notes

3.9.4 Customer concerns

3.9.5 How to point to a debug file or listing

Chapter 4. Introduction to Debug Tool Coverage Utility

4.1 Start by validating your software levels

4.2 Overview

4.2.1 What does DTCU require

4.2.2 Running DTCU consists of the following steps

4.3 Using DTCU

4.3.1 Starting the DTCU ISPF dialog

4.3.2 Modifying your DTCU defaults

4.3.3 Compiling the program to be measured

4.3.4 Setting up your control file

4.3.5 Create the setup JCL

4.3.6 Create JCL to start a monitor session

4.3.7 Create JCL for a report

4.3.8 What did we generate up to now

4.3.9 Perform the setup step

4.3.10 Perform the link step

4.3.11 Start the monitor session

4.3.12 Start your program

4.3.13 Display statistics online

4.3.14 Stop the monitor

4.3.15 Create the summary report.

4.3.16 Create the summary report and annotated listing report

4.3.17 Use of the monitor panel

4.3.18 Fast Path

4.4 Restrictions

4.4.1 CICS

4.4.2 Other environments

4.4.3 Unix System Services

4.5 Installation

4.5.1 Systems programmer notes

Chapter 5. How to compile old COBOL

5.1 Start by validating your software levels

5.2 Overview

5.2.1 What do the conversion tools need

5.2.2 What steps are required

5.3 Setting up for convert and compile

5.3.1 Define your global options

5.3.2 COBOL convert and compile option

5.3.3 Convert old 68/74 COBOL to 85 COBOL

5.4 Summary

Chapter 6. Introduction to Fault Analyzer

6.1 Start by validating your software levels

6.1.1 PTF information

6.2 How Fault Analyzer works

6.2.1 The fault history file

6.2.2 Supported application environments

6.2.3 A summary of real-time analysis

6.3 Preparing your programs for Fault Analyzer

6.3.1 Compiler options

6.3.2 What is a side file

6.3.3 How to create a side file

6.4 Using FA to re-analyze an abend

6.4.1 Interactive re-analysis

6.4.2 Synopsis section

6.4.3 Point-of-failure section

6.4.4 Events section

6.4.5 System-wide information section

6.4.6 Batch re-analysis

6.4.7 Specifying listings to Fault Analyzer in re-analysis

6.5 Using FA to analyze CICS system dumps

6.5.1 How to select a system dump data set for FA analysis

6.5.2 Analyzing a CICS system dump

6.6 How to set up and customize Fault Analyzer

6.6.1 Invocation exits

6.6.2 CICS set-up

6.6.3 Batch set-up

6.6.4 User exits

6.7 Options available to customize Fault Analyzer

6.7.1 How to specify these options

6.7.2 Order of precedence

6.7.3 User-options file (IDIOPTS)

6.8 Hints and tips

6.8.1 Systems programmer notes

6.8.2 Place abends in different fault history file.

6.8.3 Send a notification when a program abends

6.8.4 Send an e-mail when a program abends

Chapter 7. Introducing Application Monitor

7.1 Special notices

7.2 Check the installation

7.2.1 Check the defaults

7.2.2 Monitoring a job using Application Monitor online

7.2.3 Monitoring a job in absentia

7.2.4 Batch analysis of a recorded session

7.3 DB2 support

7.3.1 Using the IVP sample

7.3.2 Using SPUFI

7.3.3 Using File Manager DB2

7.3.4 Results in Application Monitor

7.3.5 Explain and plan

7.4 CICS Support in Version 1.1 with PTF

Chapter 8. Introduction to Workload Simulator

8.1 Overview

8.1.1 General process

8.1.2 WSim installation

8.1.3 Resources WSim can simulate

8.1.4 Testing with WSim

8.2 System configuration

8.2.1 Physical configurations

8.2.2 Logical configurations

8.3 Script preparation

8.3.1 Network definition statements

8.3.2 Message generation decks

8.3.3 Methods for message generation decks creation

8.3.4 Testing scripts

8.4 WSim output

8.5 Operating WSim

8.5.1 Initializing, starting, and stopping a network

8.5.2 Changing and resetting network parameters

8.6 WSim Test Manager

8.6.1 WTM operating modes

8.6.2 WTM utilities

8.6.3 Testcases

8.6.4 Testgroups and testcycles

8.6.5 Schedules

8.6.6 Output reports

8.6.7 Model scripts

Chapter 9. Implementing the tools in your environment

9.1 File Manager components

9.1.1 Templates

9.1.2 File associations

9.1.3 Steps toward integration

9.2 Debug Tool components

9.2.1 Load modules

9.2.2 Listings

9.2.3 Side files

9.2.4 Source files

9.2.5 Steps toward integration for COBOL

9.2.6 Steps toward integration for VisualAge PL/I and C/C++

9.3 Fault Analyzer components

9.3.1 Listings

9.3.2 Side files

9.3.3 Output file size comparison.

9.3.4 Steps toward integration.

Notes:

"December 2002."

"SG24-6887-00."

Includes bibliographical references (p. 503-506) and index.

OCLC:

560315754