Volume 3 December 2005 IBM DEBUG TOOL NEWSLETTER. V6R1 PTF Preview. New Announcement:

Transcription

1 Volume 3 December 2005 IBM DEBUG TOOL NEWSLETTER New Announcement: V6R1 PTF Preview Debug Tool V6R1 can now be used with two new products that were recently announced by IBM: Websphere Developer Debugger for zseries V N06 IBM WebSphere Developer Debugger for zseries is a low-cost subset of WebSphere Developer for zseries functions, providing a workstation graphical interface to IBM Debug Tool for z/os and IBM Debug Tool Utilities and Advanced Functions. It is targeted at IBM zseries developers not requiring the full function of WebSphere Developer for zseries, which is focused on supporting the development of composite Service Oriented zseries Applications. WebSphere Developer Debugger for zseries V6.0.1, integrated with IBM Debug Tool for z/os V6.1 and IBM Debug Tool Utilities and Advanced Functions for z/os V6.1, provides Eclipse-based interactive source-level debugging capabilities for debugging compiled zseries applications. Its program debugging, testing, and analysis capabilities include the ability to let developers examine, monitor, and control the execution of application programs written in COBOL, PL/I, C, C++, and Assembler on a z/os system. WebSphere Developer Debugger, integrated with IBM Debug Tool and IBM Debug Tool Advanced Utilities, supports debugging of application programs that run in the following environments: CICS IMS DB2 WebSphere TSO JES/batch UNIX System Services Websphere Developer for zseries V L44 Allows cross-platform interactive testing, debugging, and deployment of JSP, servlets, EJB, and HTML files on local and remote Web application servers as well as CICS, IMS/DC and batch debugging of COBOL, PL/I, and assembler applications. 1

2 Usability: Support for the LISTLD option in the Load Module Analyzer (LMA) The Load Module Analyzer ISPF panels updated to support the CKVOLFPRS, LEINFO, LESCAN and LISTLD options Functionality: Support for JUMPTO LABEL JUMPTO Label specifying a statement label in a currently active block. Support for SET SAVE SETTINGS ONCE In addition to AUTO / NOAUTO options in SET SAVE SETTINGS, a new alternative option of ONCE is added. Without ONCE there was no way to save the settings, and in the saved settings file have SET SAVE SETTINGS NOAUTO. ONCE indicates that the SETTINGS are to be saved at the end of the current sessions, but are to be saved with a value of SET SAVE SETTINGS NOAUTO. Therefore, the settings get saved only ONCE. Tips and Hints Topics Debug Tool Terminal Interface Manager LIST Data by Section AT CHANGE WHEN Remote Debug Enhancements 2

3 Debug Tool Terminal Interface Manager You can debug batch programs interactively by using a full-screen mode through a VTAM terminal. Before you start this debugging session, contact your system administrator to verify that your system was customized to support this type of debugging session, and for instructions on how to access a terminal that supports this mode. You need to decide whether you want to use the new Debug Tool Terminal Interface Manager. The Debug Tool Terminal Interface Manager enables you to associate a user ID with a specific VTAM terminal, which removes the need to update your runtime parameter string whenever the VTAM terminal LU name changes. This section shows how to use the new Debug Tool Terminal Interface Manager. To start a debugging session with the Debug Tool Terminal Manager, do the following: 1. Start two terminal emulators. 2. At the first terminal emulator, log on to TSO. 3. Connect the second terminal emulator to a terminal LU that can handle fullscreen mode through a VTAM terminal and can start the Debug Tool Terminal Interface Manager, as shown below: 4. Provide your TSO user ID and password to the Terminal Interface Manager and press Enter. When you provide your user ID and password to the Terminal Interface Manager, you are not logging on TSO. You are only indicating that your user ID is to be associated with this terminal LU. 3

4 5. A Telnet Solicitor Logon panel is displayed on the second terminal emulator session. The terminal is now ready to start a Debug Tool full-screen mode through a VTAM terminal. 6. On your TSO session, edit the PARM string of your batch job so that you specify the TEST run time option, as in the following example: TEST(,,,VTAM%USRT0010:*) Place a slash (/) before or after the parameter, depending on your programming language. In this example, USRT010 is the TSO user ID of the user debugging the program. The example below shows a TSO EDIT session with all lines excluded except the JOB CARD and the PARM statement which shows the VTAM%USRT010 specification. 4

5 7. Submit the batch job. 8. A full-screen mode debugging session is displayed on the second terminal. Interact with it in the same way you with any other full-screen mode debugging session. 9. After you exit Debug Tool, a Telnet Solicitor Logon panel is displayed on the second terminal emulator session: 5

6 10. If you want to restart the debugging session, then do the following steps: a. Stop and restart the terminal emulator session to re-invoke the Terminal Interface Manager or enter EQASESSM in the Application field and press Enter to re-invoke the Terminal Interface Manager. b. Provide your user ID and password to the Terminal Interface Manager, then press Enter. c. Go back to step 5. 6

7 Some potential for some confusion exists when you see the Telnet Solicitor Logon panel. This panel appears in two situations: 1. When you logon to the Debug Tool Terminal Information manager and the session is ready for debugging. 2. After the Debug Tool Session has ended. Note that at this point there is no connection between this session and Debug Tool. The following convention may alleviate some of this confusion: Do not leave the terminal at the Telnet Solicitor Logon panel after ending a Debug Tool session. Rather, immediately start the Debug Tool Terminal Interface Manager and log on. If you follow this convention, you can be assured that the session is logged on to the Debug Tool Terminal Information Manager and ready for a debug session. 7

8 LIST Data by Section Previously, there was no way to list all the variables, and their values, defined in the COBOL File Section, Working-Storage Section, Local-Storage Section, or Linkage Section other than specifying each variable separately by name. This enhancement to the LIST command provides a more straight forward approach without the need to remember variable names. LIST Expression Syntax: >> LIST expression ; >< _TITLED <_, _UNTITLED_ _(_expression_ ) _TITLED _* FS WSS LOS LS To display the values of all the variables defined in the COBOL File Section, Working- Storage Section, Local-Storage Section, or Linkage Section, issue the LIST TITLED FS; or LIST TITLED WSS; or LIST TITLED LOS; or LIST TITLED LS; command. These LIST commands cause Debug Tool to display the name and current value of all variables defined in the File Section, Working-Storage Section, Local-Storage Section, or Linkage Section respectively. For example, if you want to display the variables in the COBOL Working-Storage Section, issue the following command: LIST TITLED WSS; Use these commands carefully. Listing sections containing large data items takes a great deal of storage. 8

9 AT CHANGE WHEN Command Previously, in order to stop when a specific condition is met, you must combine the AT CHANGE command with the IF command. This enhancement adds a condition evaluation as part of the AT CHANGE command. AT CHANGE Syntax: >> AT CHANGE > _every_clause_ > reference command ; >< WHEN condition _%STORAGE ( address )_ _, length_ <_, _( reference ) _%STORAGE ( address ) _, length_ reference A valid Debug Tool reference in the current programming language. condition A valid Debug Tool conditional expression. %STORAGE A built-in function that provides an alternative way to select an AT CHANGE subject. address The starting address of storage to be watched for changes. This must be a hex constant: o o o o 0x in C H in COBOL (using either double (") or single (') quotes) PX constant in PL/I X in assembler or disassembly length The number of bytes of storage being watched for changes. This must be a positive integer constant. The default value is 1. command A valid Debug Tool command. Debug Tool gains control when either the program or a Debug Tool command changes the specified variable value or storage location. If the WHEN clause and its corresponding condition are specified then Debug Tool evaluates the condition. Debug Tool stops and executes the commands associated with the breakpoint only if the condition is true. If you use the AT CHANGE with a conditional expression, every time the variable changes the condition is evaluated. If the condition is true, Debug Tool stops and executes the command associated with the breakpoint. 9

10 For example, to stop when a variable reaches a value that is greater than 200 use the following command: AT CHANGE MYVAR WHEN MYVAR > 200 ; In this case, MYVAR > 200 is the condition to be evaluated. Every time the value of MYVAR changes the condition MYVAR > 200 is evaluated. Changes to MYVAR itself do not trigger the AT CHANGE. Only when MYVAR changes and the condition MYVAR > 200 is true does the AT CHANGE trigger. 10

11 Remote Debug Enhancements WebSphere Developer Debugger for zseries and Websphere Developer for zseries are powerful, easy-to-use workstation interfaces to the unique functions provided by IBM Debug Tool or IBM Debug Tool Utilities and Advanced Functions. Developers can execute a broad range of capabilities needed for debugging, such as stepping, setting breakpoints, and detecting and diagnosing errors in programs that are running remotely. With the debugger's distributed design, users can debug programs running remotely on other systems available with TCP/IP access from or to a developer's workstation. With this debugger, developers can control the execution of programs by setting compiled language-specific breakpoints, suspending execution, stepping through code, and examining and changing the contents of variables. The debugger operates from the Eclipse workbench and contains views and functionality specific to debugging compiled language applications. With the Eclipse-based views, developers can monitor variables, expressions, registers, memory, and application modules. Functionality that is geared specifically to debugging compiled language applications includes: Viewing source in the editor Choosing from multiple breakpoint types, such as line, entry, address, watch, and load Specifying exception types at which the debugger will stop program execution, such as run, and step into and over a procedure Monitoring and updating storage, memory maps, registers, variables, and expressions. To edit a breakpoint: 1. Open a debug session and set a line breakpoint. In this example, a breakpoint is set at line

12 2. Open the edit breakpoint panel. This panel allows you to add, remove or edit a conditional expression for the breakpoint. In this case, we are adding WK-SEARCH-TYPE = "P" as a condition. 3. Back in our debug session, we stopped at line 180, and we see that our condition is valid. In the local variable pane, WK-SEARCH-TYPE is equal to P. 12

13 4. Open another edit breakpoint panel. In this panel, we change the line number to line Back in the debug session, we see that the breakpoint indicator moved from line 180 to 199, and the entry in the breakpoint panel is updated. 13

14 Service Information Debug Tool V6R1: Debug Tool Base PID: 5655-P14 Debug Tool Utilities and Advanced Functions (AFS) PID: 5655-P15 Program APAR Number PTF Number PTF Date DT Base PK14572 UK /06/2005 DTU&AF PK14577 UK /06/2005 DT JPN PK15093 UK /07/2005 DTU&AF JPN PK15090 UK /07/2005 Debug Tool V5R1: Debug Tool Base PID: 5655-M18 Debug Tool Utilities and Advanced Functions (AFS) PID: 5655-M19 Program APAR Number PTF Number PTF Date DT Base PK12158 UK /15/2005 DTU&AF PK14451 UK /15/2005 DT JPN PK00799 UK /26/2005 Debug Tool V41: Debug Tool Base PID: 5655-L24 Debug Tool Utilities and Advanced Functions (AFS) PID: 5655-L23 Program APAR Number PTF Number PTF Date DT Base PK02447 PK05285 UK /10/2005 DTU&AF PQ98515 UQ /21/2005 DT JPN PK03524 UK /10/

15 Debug Tool V3R1: Debug Tool Base PID: 5655-H32 Debug Tool Utilities and Advanced Functions (AFS) PID: 5655-J18 Program APAR Number PTF Number PTF Date DT Base PQ99574 UK /25/2005 DTU&AF PQ98492 UQ /27/2005 DT JPN PQ95259 UQ /27/2005 Note that you can use the CALL %VER command to show the latest APAR number for the Debug Tool Base that is actually installed on your system. 15

16 Contributing Authors: Francisco Anaya, Jesse Jackson, Jim McIntosh, Beth Flint Editor: Beth Flint Copyright IBM Corporation 2005 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. 16