Transcript
Volume 6 April 2007
IBM DEBUG TOOL NEWSLETTER Service Information Currently Available PTFs Release Debug Tool for z/OS V7.1 Debug Tool for z/OS V6.1 Debug Tool for z/OS V5.1
English Component
Japanese Component
English DTUAF
UK24096
UK24098
UK24097
UK23252
UK20329
UK20517
UK23439
UK21402
UK21403
Japanese DTUAF
UK13488
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 7.1 IBM Debug Tool Version 7 Release 1 Mod 0 02/28/2007 01:02:00 PM Level: V7R1 PK39157 5655-R44 and 5655-R45: (C) Copyright IBM Corp. 1992, 2006
•
Version 6.1 IBM Debug Tool Version 6 Release 1 Mod 0 03/21/2007 09:19:00 AM Level: V6R1 PK41662 5655-P14 and 5655-P15: (C) Copyright IBM Corp. 1992, 2005
•
Version 5.1 IBM Debug Tool Version 5 Release 1 Mod 0 03/28/2007 06:20:00 AM Level: V5R1 PK37562 5655-M18 and 5655-M19: (C) Copyright IBM Corp. 1992, 2004
Tips and Hints Debugging IMS/TM Applications Adding Variables into the Monitor Window Put Down That Book The Service Station
1
Adding Variables into the Monitor Window Interested in adding a variable declared in you program to the monitor window, but can’t remember the variable’s name? Here is a way that can help you achieve this effortlessly. 1. Issue the List Names command to display all variables known to your program including variable in the COBOL Working Storage Section.
2. Overtype the variable name in the log with the MONITOR LIST command.
2
3. After pressing Enter, the overtyped command is added to the command line.
4. Pressing Enter the second time adds the variable to the monitor window. Notice the Monitor List HDLR-FC command at the bottom of the log.
3
5. Zoom so you can see the monitor window, and you see the variable now in the monitor window.
You can reduce the number of variables by using wild cards. For example, LIST NAMES ‘Z*’; displays only those variables that start with the letter Z. Note that you need to enclose the string in single quotes.
Only the variables whose names start with Z are listed.
4
You can also minimize your typing by creating your own short commands with the SET EQUATE command. This command can be placed in your preference file so it is always available in your debugging session. 1. Type SET EQUATE ML = ‘Monitor List’;
2. Use the short command to add a new variable to the monitor window by overtyping on the log.
5
Note that the command is logged as if the long version of the command was used.
3. Zoom to restore the original window setup and you can see the variable LVAR in the monitor window.
6
Another way to achieve the same result is to assign the MONITOR LIST command to a PF key and use the PF key in the source window.
1. Assign the MONITOR LIST command to a PF key as follows: SET PF5 = MONITOR LIST; Or use the short command as follows: SET PF5 = ML;
7
2. Scroll the source window until you see the variable you want to monitor, and then place the cursor on the variable name. In this example, note that the definition for PF5 changed from FIND to ML and that the cursor is positioned over variable LVAR1.
3. After pressing PF5, you can see that the variable LVAR1 is now in the monitor window.
8
Debugging IMS/TM Applications using Debug Tool with Debug Tool Utilities and Advanced Functions This article covers how an IMS programmer can set up his program or transaction for use with Debug Tool.
Specifying the LE Runtime options for IMS/TM There are two ways that a programmer can specify the Language Environment (LE) options so that Debug Tool is started when the IMS/TM transaction is run. 1. Debug Tool Utilities & Advanced Functions option 4.1 Manage LE Runtime Options in IMS 2. Debug Tool Utilities & Advanced Functions option 6 Manage TEST Run-time Option Data Set Both of these options require a specific version of CEEBXITA. Option 1 requires the following: •
The IMS Version of CEEBXITA – DFSBXITA be link-edited with LE module CEEBINIT
•
IMS Version 8, or later
•
IMSPlex installed
•
IMS Single Point of Control is contained in the IMSPlex
•
Debug Tool Version 5, or later
•
Language Environment.
Option 2 requires the following: •
Debug Tool version of CEEBXITA – EQADICXT be link-edited with your program
•
Debug Tool Version 7, or later
•
Language Environment.
Option 1 – Manage LE Runtime Options in IMS Option 1 uses Debug Tool Utilities and Advanced Functions option 4.1 – Manage LE Runtime Options in IMS. This option provides Debug Tool Utilities and Advanced Functions an interface to pass the LE Options to IMS Single Point of Control (SPOC).
9
On the 4.1 panel, the first item you must enter is the IMSPlex ID.
Once you enter the IMSPlex ID and press Enter, you see the selection panel to Edit LE Runtime Options in IMS.
To begin, press F4 to create a new entry. The Panel shows E to edit an entry, C to copy an entry, and D to delete an entry; however you must use F4 to create a new entry.
10
Once you press F4, you see the Create LE Runtime Options Entry panel.
On this panel, you enter all of the necessary LE options although they are not all currently visible on this panel. First, you see the IMSPlex ID, which was entered on the previous panel and the IMSPlex member (which was optional). Next are the Qualifiers: Trancode, Program, Lterm and Userid. You can enter any combination of these 4 items from 1 of them to all 4 of them. If you are the only one using the transaction you’re debugging, you could enter only the Trancode and leave the others blank. If others might be using the same Trancode, then you can further qualify it by specifying the Lterm you are using or the Userid you are using.
11
On the following panel, just the Trancode, iapmdi26, is entered. The Test Options, Prompt Level, and Preference File are fine with the defaults listed so they are left as is.
Next, page down to see more options. Here you select the debug session type that is used. You can select Full-screen mode, Full-screen mode using Debug Tool Terminal Information Manager, or Remote debug mode. Finally, you can enter other LE runtime options.
12
For this example, Full-screen mode is chosen with the LU Name of the debug terminal.
Pressing Enter and then End (F3) takes you back to the previous panel. You now have an entry for this transaction. It is ready to be debugged using Debug Tool.
13
If two people working on a transaction, you could enter the following:
Transaction IAPMDI26 started on the IMS terminal that USER01 is using starts the debug session on terminal T1305. The same transaction started on the IMS terminal that USER02 is using starts the debug session on terminal T1306. Once the LE runtime options are defined, you can start your transaction provided you started the transaction / program and assigned it to the appropriate class.
14
Finally, the debug session starts in the session specified above on the Modify LE Runtime Options panel.
Option 2 – Manage Test Runtime Options Data Set Option 2 uses Debug Tool Utilities and Advanced Functions option 6 - Manage TEST Run-time Option Data Set. This option provides Debug Tool Utilities and Advanced Functions an interface to pass LE Options to IMS using the Debug Tool version of the LE CEEBXITA exit, EQADICXT. With this exit installed and available to your region, the Test Runtime Options are picked up from an Options Data Set that is specific to the Userid.
15
After selecting Option 6 in Debug Tool Utilities & Advanced Functions, you see the Manage Test Runtime Option Data Set panel with the default data set.
Pressing Enter takes you to the next panel. Since the data set has not been allocated yet, the Allocate TEST Runtime Option Data Set panel is displayed.
Page down (if necessary) to see the rest of the Panel.
16
Press Enter to allocate the data set. Once the data set is allocated you can edit the options.
First on the panel is the list of test program names. You can enter up to 8 different program names. The wild card character “*” may be used.
17
Next on the panel is the list of Test Options. Enter the test options that you wish Debug Tool to use. Page down to see the session options. For this example, Fullscreen mode is chosen with the LU Name of the debug terminal.
Pressing Enter and END (F3) returns you to the Manage Test Runtime Option Data Set panel. You have finished creating and editing the data set.
18
You can edit the data set directly, but may find it is easier to fill in the blanks using Debug Tools Utilities & Advanced Functions, as above.
Next, you must link-edit the EQADICXT version of CEEBXITA with your program. A sample job to tailor and assemble EQADICXT can be found in the hlq.SEQASAMP library member EQADICXT. //LKED EXEC PGM=HEWL, // PARM='LIST,XREF,LET,RENT,MAP' //SYSLIB DD DSN=IMSBLD.I10ATS18.CRESLIB,DISP=SHR // DD DSN=SYS1.MACLIB,DISP=SHR // DD DSN=hlq.SEQAMOD,DISP=SHR // DD DSN=CEE.V1R8Z.SCEERUN,DISP=SHR // DD DSN=CEE.V1R8Z.SCEELKED,DISP=SHR //RESLIB DD DSN=IMSBLD.I10ATS17.CRESLIB,DISP=SHR //SYSLMOD DD DSN=CODEFVT.IMSTEST.EQADICXT.LOAD,DISP=SHR //SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024, // SPACE=(1024,(200,20)) //SYSPRINT DD SYSOUT=* //OBJECT DD DISP=SHR,DSN=CODEFVT.IMSTEST.OBJECT //SYSLIN DD * INCLUDE OBJECT(EQADICXT) REPLACE CEEBXITA INCLUDE OBJECT(IAPMDI26) ORDER IAPMDI26 ENTRY DLITCBL NAME IAPMDI26(R) /*
19
Finally, run the transaction from your IMS terminal.
And the debug session starts in you selected session.
20
Conclusion As you have seen, you can start debugging sessions for IMS/TM transactions using either of two options. The implementation in your enterprise may dictate which you choose if only one has been implemented. If your enterprise has an IMSPlex defined on your system, then you could use either option. Without the IMSPlex, you have to use Option 2. The Customization Guide includes useful information about how to configure and use full-screen mode with a VTAM terminal. Chapter 5, “Enabling debugging in full-screen mode with a VTAM terminal” is divided into two sections: •
The first section describes the tasks a user needs to complete to use fullscreen mode with a VTAM terminal without a terminal interface manager, then it describes the step-by-step instructions on how to configure this set up and shows an example.
•
The second section describes how to use full-screen mode with a VTAM terminal when you are using a terminal interface manager. The information is organized in the same manner as in the first section: describing the tasks a user needs to complete, step-by-step instruction on configuration, and then examples.
21
Put Down That Book Did you know there are lots of information resources available on ibm.com to help you quickly find the information you are looking for? If you haven’t explored ibm.com lately, let me guide you through some of the best “sellers” in our vast library.
LookAt Many z/OS and OS/390 products contribute to LookAt, a messages retrieval tool accessible through ibm.com. To use LookAt, do the following steps: 1. Open up a web browser. 2. Go to the following URL: http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/ 3. Follow the instructions on screen to retrieve the messages you are looking for. The LookAt web site provides information on its great features, including a “mobile edition” of LookAt. (Imagine all those messages in the palm of your hand!) Try it out.
Information Centers Books are becoming information units, available through information centers. The Debug Tool books are part of the IBM System z Enterprise Development Tools & Compilers information center. This information center includes books from COBOL, PL/I, WebSphere Developer Debugger for System Z, and other related products. Check it out at http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp Here’s a tip: Move your mouse pointer so that it hovers over a result. A little pop-up appears, indicating which product area the result comes from. This hover help can help you decide whether a link will take you to the information you are looking for.
I’ll take it to go, please For those of you familiar with BookManager, did you know you could download software to your Windows laptop or desk top computer that can read BookManager books? It’s called the IBM Softcopy Reader for Windows and its available for free! Just go to http://www.ibm.com/software/applications/office/bkmgr/softcopyread.html and in the “Download” box, click on “Softcopy Reader for Windows”. Follow the directions and you’ll soon be reading “books” on your “windows”.
Let me hear you say… Found a mistake? Are we missing something? We want to hear your comments and suggestions! The Reader Comment Forms, which can be found near the end of each book, are available on-line.
22
The Service Station There are a couple of things we would like to remind you to do so we can make your service experience a smooth and quick one.
Before you stop by We have a document available on ibm.com that describes the information you need to gather before contacting us. Please review the document at URL http://www1.ibm.com/support/docview.wss?rs=615&context=SSGTSD&dc=DB520&dc=D600&dc =DB530&dc=D700&dc=DB500&dc=DB540&dc=DB510&dc=DB550&q1=must+gather &uid=swg21254711&loc=en_US&cs=utf-8&lang=en.
While your problem is being serviced When you send us program dumps or other documentation through our FTP site, remember to follow the instructions at http://www1.ibm.com/support/docview.wss?rs=431&uid=swg21154524 so that we can quickly route your information to the proper personnel. If you send us information through email, please remember to copy
[email protected] (by putting the e-mail address in the cc: part of your e-mail) and write your subject line in the following manner: PMR #pmr_number – document(s) attached, as requested
23
Contributing Authors: Francisco Anaya, Elizabeth Spangler, Patricia Ramirez, and Jim McIntosh Editor: Elizabeth Spangler © Copyright IBM Corporation 2005 IBM Corporation Department DQZA Route 100 Box 100 Somers, NY USA, 06877 Printed in the (United States of America) 05-04 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 10504-1785 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.
24
