IBM DEBUG TOOL NEWSLETTER

Transcription

1 Volume 15 May 2010 IBM DEBUG TOOL NEWSLETTER Currently Available PTFs SERVICE INFORMATION Release Debug Tool for z/ OS V10.1 Debug Tool for z/ OS V9.1 Debug Tool for z/ OS V8.1 English Component Japanese Component Korean Component UK54741 UK54639 UK54640 UK55067 UK55068 UK55069 English DTUAF UK56785 UK55904 UK55905 UK55906 Japanese DTUAF To determine your current Debug Tool service level, issue the following command using the Mainframe Interface (MFI): CALL %VER; You should get the following output showing the release and PTF: Version 10.1 IBM Debug Tool Version 10 Release 1 Mod 0 02/26/ :51:00 AM Level: V10R1 PM V50: Copyright IBM Corp. 1992, 2009 Version 9.1 IBM Debug Tool Version 9 Release 1 Mod 0 03/10/ :29:00 PM Level: V9R1 PM U27: Copyright IBM Corp. 1992, 2008 Version 8.1 IBM Debug Tool Version 8 Release 1 Mod 0 05/07/ :05:00 PM Level: V8R1 PM S17 and 5655-S16: Copyright IBM Corp. 1992, Announcements Availability of the IBM Problem Determination Tools Eclipse Plug-ins Application Performance Analyzer Plug-in Debug Tool Plug-in Fault Analyzer Plug-in IBM Debug Tool Plug-in for Eclipse V README General Information Downloading the Debug Tool Plug-in Installing the Debug Tool Plug-in Getting Started Using the Debug Tool Plug-in The DTCN Plug-in 1

2 Availability of the IBM Problem Determination Tools Eclipse Plug-ins Introduction The IBM Problem Determination Tools V10 plug-ins, when used with an Eclipse-based platform like CICS Explorer, provide easy access through a graphical user interface (GUI) on the workstation to the power of the host IBM Problem Determination Tools Application Performance Analyzer for z/os, Debug Tool for z/os, and Fault Analyzer for z/os. The GUI provides a workstation based alternative to the z/os ISPF interface. As well as providing existing application developers and system programmers with productivity gains when compared with the traditional "green screen" interface, the new interface can also lower the learning curve for inexperienced z/os developers, by providing an Eclipse-based interface to the z/os tool that is likely to be quicker, easier and more familiar for them to pick up and use. The plug-ins are available for download to properly licensed IBM Problem Determination Tools V10 customers for Application Performance Analyzer and Fault Analyzer, and V9 and V10 customers for Debug Tool. Figure 1: The three Problem Determination Tools plug-ins shown in CICS Explorer Debug Tool Plug-in IBM Debug Tool Plug-in for Eclipse V9 and V10, when used with an Eclipse-based platform like CICS Explorer, debugs z/os-based load modules running on IBM z/os, including load modules that run in a subsystem such as CICS, DB2 or IMS. The plug-in GUI interface provides a debugging capability similar to that of the ISPF interface, allowing you to do the following tasks: Set and clear breakpoints at a specific line Set and clear breakpoints for an error or warning-level error that is based on Language Environment severities Run to a breakpoint Step into a procedure 2

3 Step over a procedure View variable values and change them as you step through the code View variable values in the context of a larger area of storage View the call stack Figure 2: Debug Tool plug-in in CICS Explorer Application Performance Analyzer Plug-in IBM Application Performance Analyzer Plug-in for Eclipse V10, when integrated with Application Performance Analyzer for z/os and CICS Explorer, encompasses both the Observation Request and Reporting functions, including the R02 screens list, detail views, edit functions and reports for the observation. The plug-in GUI can be used to submit new observation requests and to navigate the performance analysis reports generated from observation requests. The plug-in GUI can display and provide functions to multiple components of Application Performance Analyzer at the same time. The major views in the plug-in GUI include: STC View, which lists all active started tasks Observations List View, which lists all observations Observation Detail View, which provides details of an observation Reports List View, which lists all reports for an observation Report View, which displays an individual report 3

4 Figure 3: Application Performance Analyzer plug-in in CICS Explorer Fault Analyzer Plug-in IBM Fault Analyzer Plug-in for Eclipse V10, when integrated with Fault Analyzer for z/os and CICS Explorer, provides access to problem reports for diagnosing mainframe application errors and abends. Key features include: An interface to manage views and multiple fault history files The ability to browse fault entries that were created during real-time analysis of abending programs A browser for browsing the dump storage associated with a fault entry A source listing of abending programs, using side files 4

5 Figure 2: Fault Analyzer plug-in in CICS Explorer File Manager and Rational Developer for System z Rational Developer for System z contains an Eclipse-based GUI that can be used with File Manager for z/os. For More Information IBM Problem Determination Tools family web page IBM Problem Determination Tools plug-ins web page IBM CICS Explorer web page Rational Developer for System z web page 5

6 IBM Debug Tool Plug-in for Eclipse V README General Information System Requirements and Prerequisites: The following minimum hardware levels are required to run CICS Explorer and are therefore applicable to Debug Tool Plug-in for Eclipse V : CPU - Intel Pentium 4 or equivalent. RAM MB in addition to the operating system requirements. Hard disk MB available space. One of the following levels of Windows operating system software is required to install CICS Explorer and is therefore applicable to Debug Tool Plug-in for Eclipse V : Microsoft Windows XP 32-bit Microsoft Windows Vista 32-bit Microsoft Windows Server bit Microsoft Windows Server bit The following levels of software required to install the Debug Tool Plug-in for Eclipse V : CICS Explorer (for Windows) V , or later Debug Tool for z/os Version 9.1 or later The Debug Tool Plug-in for Eclipse V is available in the following national languages: English Japanese Korean Restrictions and Limitations: CICS Explorer displays, by default, the Outline View. You cannot use this view, but you can close the view. Downloading Debug Tool Plug-in The Debug Tool Plug-in for Eclipse V can be downloaded from the Problem Determination Tools Plug-in website. The download file is called cn0d.zip. Installing Debug Tool Plug-in The following steps are required in order to install the Debug Tool Plug-in for Eclipse V into CICS explorer. 1. Extract all the contents of cn0d.zip to any writable directory of your choice, for example, C:/DebugTool. 2. Start CICS Explorer. 3. In the action bar click "Help" -> "Software Updates". 4. Click "Available Software". 5. Click "Add Site". 6. Click "Local". 7. Navigate to the directory storing the extracted files. 8. Click "OK". 9. Click "OK". 6

7 10. CICS Explorer displays a list of features you can install. Select the "Debug Tool Plugin" check box. 11. Click "Install". 12. Click "Next". 13. Accept the feature license agreement and click "Finish". 14. After CICS Explorer installs the Debug Tool Plug-in for Eclipse V , you are asked if you want to restart CICS Explorer. Click "Yes". After CICS Explorer restarts, read "Getting Started Using Debug Tool Plug-in for Eclipse V " for instructions how to display the "Getting Started" help topic. Getting Started has instructions how to start debugging your applications. Getting Started Using Debug Tool Plug-in The topic "Getting Started" describes the steps you must do to start debugging your applications with the Debug Tool Plug-in for Eclipse V To open the topic: 1. In CICS Explorer, click "Help" -> "Help Contents". 2. Expand "Debug Tool Plug-in for Eclipse". 3. Click "Getting started". You can find more information about how to use Debug Tool Plug-in for Eclipse V in the help of CICS Explorer. 1. Click "Help" -> "Help Contents". 2. Expand the topic "Debug Tool for z/os client for Eclipse". 7

8 The DTCN Plug-in Since the DTCN plug-in is not part of the Debug Tool plug-in, the following sections describe how to get and install the DTCN plug-in along with necessary host customization. Debug Tool provides an API that communicates with the DTCN profile manager so you can create, retrieve, update, or delete profiles in the DTCN profile repository. Refer to the Debug Tool API User s Guide and Reference available online to find out more about the API. Where do I get the DTCN plug-in? Ask the system administrator for the name of the Debug Tool installation library. The binary form of the DTCN plug-in is located in <DebugTool_HLQ>.SEQABIN(eqacdplg). Transfer the file, in binary format, from your z/os system to your workstation and rename it to one of the following: For Debug Tool V10* - com.ibm.pdt.debugtool.profile_1.0.0.jar For Debug Tool V9* - com.ibm.pdt.debugtool.profile_0.9.0.jar *For Debug Tool versions installed before May, How do I install the DTCN plug-in? Move the above jar file into the one of the following locations: Rational Developer for System z - C:\Program Files\IBM\SDP\plugins CICS Explorer - CICS_Explorer_Install_Directory\dropins Eclipse - Eclipse_Install_Directory\dropins Restart the Eclipse-based application. If you installed a previous version of this plug-in, specify the clean option when you restart the Eclipse-based application. For example, using the DOS command prompt, enter cicsexplorer.exe clean to restart CICS Explorer. How do I customize the host? The following screen shot shows the TCPIPservice created using the CEDA DEF TCPIPSERVICE(service-name) GROUP(group-name) command. 8

9 Open the DTCN preferences by clicking on Window > Preferences. Out of the box, the preferences page is as follows: Enter the four fields host name, port number (check with the CICS or system administrator), user id, and password, then click on the Test Connection button. Verify that the Connection tested OK message appears at the top of the window. 9

10 Click on Window > Show View > Other... to select the DTCN profiles view as seen below. Once inside the DTCN profiles view, right mouse click to select any action as shown below. For illustration purposes, let us edit the VIKRAM2 DTCN profile. On the Profiles Management screen, click the Next button. 10

11 Enter HELO as the transaction to be debugged, then click the Finish button. The DTCN Profiles view is refreshed and HELO appears in the transaction column as seen below. 11

12 Contributing Authors: Joe Devine, Patricia Ramirez, and Elizabeth Spangler Editors: Elizabeth Spangler and Francisco Anaya Copyright IBM Corporation 2010 IBM Corporation Department DQZA Route 100 Box 100 Somers, NY USA, Printed in the (United States of America) All Rights Reserved References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates. All Statements regarding IBM s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any performance data contained in this document were determined in various controlled laboratory environments and are for reference purposes only. Customers should not adapt these performance numbers to their own environments as system performance standards. The results that may be obtained in other operating environments may vary significantly. Users of this document should verify the applicable data for their specific environment. 12