Service Information. English Component

Transcription

1 Volume 18 December 2011 IBM DEBUG TOOL NEWSLETTER Currently Available PTFs Release Service Information English Component Japanese Component Korean Component Debug Tool for z/os V11.1 UK74780 UK74781 UK74782 Debug Tool for z/os V10.1 UK74162 UK74163 UK74164 Debug Tool for z/os V9.1 UK64796 UK64240 UK64242 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: IBM Debug Tool Version 11 Release 1 Mod 0 12/13/ :16:00 PM Level: V11R1 PM W45: Copyright IBM Corp. 1992, 2010 IBM Debug Tool Version 10 Release 1 Mod 0 11/23/ :02:00 AM Level: V10R1 PM V50: Copyright IBM Corp. 1992, 2009 IBM Debug Tool Version 9 Release 1 Mod 0 04/22/ :20:00 AM Level: V9R1 PM U27: Copyright IBM Corp. 1992, 2008 Tips and Hints Debug Tool Startup Profile (DTSP) Plug-in Filters for Debug Tool LE User Exit LangX COBOL 1

2 Debug Tool Startup Profile (DTSP) Plug-in The Debug Tool Startup Profile (DTSP) plug-in is an Eclipse-based GUI to create and manage debugging profiles for the following environments: IMS (TM and BTS), DB2 (stored procedures), and Batch. It provides the same function as option 6 (Debug Tool User Exit Data Set) of the Debug Tool Utilities, allowing you to manage the Language Environment User Exit dataset, typically in the form of &USERID.DBGTOOL.EQAUOPTS. The DTSP plug-in is part of Debug Tool V11 offering. Host Customization The following steps must be performed by a system administrator of the z/os system. 1. Install the Problem Determination Tools Common Components Server. The Problem Determination Tools Common Components Server is a Java application. You must copy the required executable to an HFS directory prior to running the server. Review the comments in the job IPV.SIPVSAM1(IPVGSVRI) to learn how to install the Problem Determination Tools Common Components Server. Remember to first create the HFS directory on the target UNIX System Services system before running this job. 2. Install and configure the Debug Tool extension for the Problem Determination Tools Common Components. You must install and configure the Debug Tool extension for the Problem Determination Tools Common Components to enable communication between the DSTP Profile view and your z/os system. To install and configure the Debug Tool extension for the Problem Determination Tools Common Components, do the following steps: 1. Create an HFS directory on the target UNIX System Services system. If you want to use the same directory you created in step #1 above, you can run the following: <DebugTool_HLQ>.SEQASAMP(eqawndex). 2. Add a classpath variable in the job IPVGSVRJ for each file using the name in the "Name in HFS directory" column. Member Name Name in HFS Directory EQANDCOM org.eclipse.equinox.common_3.4.0.jar EQANDEXT DebugToolProvider.jar EQANDWRK org.eclipse.ui.workbench_3.4.2.jar For example: export IPV_HOME=/usr/lpp/ipv150 export DT_COMMON=org.eclipse.equinox.common_3.4.0.jar export DT_PROD=DebugToolProvider.jar export DT_WORKB=org.eclipse.ui.workbench_3.4.2.jar CLASSPATH="$CLASSPATH":"${IPV_HOME}/${DT_COMMON}" CLASSPATH="$CLASSPATH":"${IPV_HOME}/${DT_PROD}" CLASSPATH="$CLASSPATH":"${IPV_HOME}/${DT_WORKB}" 3. Run the Problem Determination Tools Common Components Server. The Problem Determination Tools Common Components Server listens for requests coming from the DSTP Profile view on a TCP/IP port you specify in the job IPV.SIPVSAM1(IPVGSVRJ). Review the comments in the job IPV.SIPVSAM1(IPVGSVRJ) to learn how to run the Problem Determination Tools Common Components Server. Remember to give the user ID associated with this job READ access to the RACF FACILITY class called BPX.SERVER. The IPVGSVRJ job is shown below. Notice that the port number (8003 as an example) chosen by the system administrator is highlighted in red. 2

3 //******************************************************************** //* * //* IPVGSVRJ JOB * //* * //* CAUTION: THIS IS NEITHER A JCL PROCEDURE NOR A COMPLETE JOB. * //* BEFORE USING THIS JOB, YOU WILL HAVE TO MAKE THE FOLLOWING * //* MODIFICATIONS: * //* * //* 1. Change the JOB parameters to meet your system requirements * //* 2. Change #proclocation to the data set which contains the * //* JVMPRC50 JCL procedure. * //* Depending on your Java level, you may need to use a different * //* JZOS Java launcher. * //* 3. Change #usspath to the required z/os UNIX directory * //* which has the IBM Problem Determination Tools Common Server * //* code in it. * //* This should be the same as set in job IPVGSVRI * //* 3. Change #javapath to the required z/os UNIX directory * //* for Java. Note this needs to be Java 31-bit, version 1.5 or * //* later. * //* 4. Change #portnumber to the TCP/IP port number for the IBM * //* Problem Determination Tools Common Server to listen on. * //* * //******************************************************************** //* PROCLIB JCLLIB ORDER=#proclocation //IPVSRV EXEC PROC=JVMPRC50,VERSION='50', // JAVACLS='com.ibm.pdtools.common.server.PDToolsServer', // ARGS='8003 /IPV150/ipvlog.conf' //STDENV DD PATH='/IPV150/STDENV.txt' Workstation Customization Follow one of the following two steps, manual or automatic (Eclipse p2 install), to get the DTSP plug-in up and running on the workstation. Manual 1. Transfer, in binary format, the following dataset from the z/os system: <DebugTool_HLQ>.SEQABIN(EQACDPLG) 2. Rename the file to com.ibm.pdt.debugtool.profile_2.0.3.jar. 3. Move that file to the specified directory of any of the following Eclipse-based applications: CICS Explorer CICS_ Explorer_install_directory\dropins Eclipse Eclipse_install_directory\dropins Rational Developer for System z/os C:\Program Files\IBM\SDP\plugins 3

4 Automatic (Eclipse p2 install) 1. Download the Debug Tool Plug-in V from the following URL: 2. Extract all the contents of DT_plugin_V11100.zip to a writable directory of your choice, for example, C:/Eclipse/PlugIns/DebugTool v Start CICS Explorer. 4. In the action bar,click "Help -> Install New Software". 5. Click "Add". 6. The "Add Repository" window should open. 7. Click "Local". 8. Navigate to the directory storing the extracted files. 9. Click "OK". 10. Click "OK". 11. CICS Explorer displays a list of features you can install. Select the "IBM Debug Tool Plug-in IBM Debug Tool Plug-in for Eclipse", the "IBM Debug Tool Plug-in -> Debug Perspective for Eclipse 3.6" and (optionally) one of the DTCN and DTSP Plug-ins for Debug Tool (depending on the installed version of Debug Tool). 4

5 12. Click "Install". There may be a security warning for unsigned content. Click "OK" if this message appears. 13. Click "Next". 14. Accept the feature license agreement and click "Finish". 15. CICS Explorer installs the Debug Tool Plug-in for Eclipse V When you are asked if you want to restart CICS Explorer; click "Yes". DTSP plug-in installed in CICS Explorer 1. If you haven't already, restart your Eclipse-based application. If you installed a previous version of either plug-in, specify the -clean option when you restart your Eclipse-based application. 2. Specify the settings needed to establish a connection between the DTSP profile view and the z/os system by doing the following steps: 1. Click on Window>Show view>others Type in "DTSP" in the text box at the top of the window. 3. Select DTSP Profile and click OK. 4. Click on Window>Preferences. 5. Click on Debug Tool>DTSP (non-cics) in the list. The default settings are shown in the screen-shot below. 5

6 6. Fill in all of the fields. Make sure you enter the port number given to you by the system administrator. 7. Click on Test Connection. If you see a message that indicates the test was successful, click on OK to close the Preferences window. Otherwise, review the information you entered, correct any mistakes, and retry the connection test. You can also review the trace file, debugtool.dtsp.trace found in the \.metadata folder on your workspace. 3. Within the DTSP profile view, you can right mouse click and refresh the view as seen below. 4. Select the profile hlq.dbgtool.eqauopts and double-click to see the wizard on the following page. 6

7 5. Click on Next >. Change the TEST Level from NONE to ERROR and click on the Finish button. 6. The DTSP Profile view shows the updates made to the Language Environment User Exit data set. 7

8 Filters for Debug Tool LE User Exit Currently the Debug Tool Language Environment (LE) user exit offers 2 pattern matching filters: user ID and main program name. Customers have asked for additional filters to better decide when a debug session should be started for a transaction. For example, In an environment where multiple IMS regions are active, a user runs a transaction and wants to start a debug session only when the transaction is running in a certain IMS region. A user has two transactions that have the same main program, but he wants to start a debug session for only one of the transactions. To address these situations, we added two optional filters, IMS subsystem ID and IMS transaction ID. The user can specify a value that must be matched before a debug session is started. To specify the filter values in a LE user exit data set, we have enhanced Debug Tool Utilities (DTU, ISPF application) and Debug Tool Startup Profile plug-in (DTSP) to allow the user to specify the values. The following is a set of steps for DTU. For DTSP, see the DTSP article in this newsletter. 1. Select 6 from DTU main panel and press Enter. 2. Provide a user exit data set name and press Enter. 8

9 3. Provide filter values and test options. Press F3 to save information in the data set. 9

10 LangX COBOL The term LangX COBOL refers to any of the following: Any program compiled using the IBM OS/VS COBOL compiler A program compiled using the IBM VS COBOL II compiler with the NOTEST option A program compiled using the IBM Enterprise COBOL compiler with the NOTEST option To debug a LangX COBOL program, you must complete the following steps: 1. Compile your program using the proper options. Program Compiler Options OS/VS COBOL VS COBOL II Enterprise COBOL 2. Create the EQALANGX file. For example the following JCL IBM OS/VS COBOL IBM VS COBOL II IBM Enterprise COBOL NOTEST SOURCE DMAP PMAP VERB XREF NOLST NOBATCH NOSYMDMP NOCOUNT NOTEST SOURCE MAP XREF LIST (or OFFSET) NOTEST SOURCE MAP XREF LIST //XTRACT EXEC PGM=EQALANGX,REGION=32M, // PARM='(COBOL ERROR LOUD' //STEPLIB DD DISP=SHR,DSN=hlq.SEQAMOD //LISTING DD DISP=SHR,DSN=userid.langxcompiler.listing //IDILANGX DD DISP=OLD,DSN=userid.EQALANGX takes the listing data set, userid.langxcompiler.listing, generated by the compiler and creates the EQALANGX debug file, userid.eqalangx. 3. Link-edit your program. Note that OS/VS COBOL programs are non-language Environment programs, even if you used Language Environment libraries to link them. VS COBOL II programs are non-language Environment programs when you link them with a non-language Environment library. VS COBOL II programs are Language Environment programs when you link them with the Language Environment library. Enterprise COBOL programs are always Language Environment programs. 4. Run your program. Start the program according to the program type as follows: Program Type Non-Language Environment Language Environment JCL EXEC //STEP1 EXEC PGM=EQANMDBG, // PARM='myprog,TEST(ERROR,*,;,*)/' //STEP1 EXEC PGM=myprog, // PARM='/ TEST(ERROR,*,;,*)' 10

11 Use the LOADDEBUGDATA (LDD) command to tell Debug Tool that a compile unit is a LangX COBOL compile unit and to load the debug information associated with that compile unit. For example, the command LDD myprog causes Debug Tool tries to locate the debug information in the data set userid.eqalangx(myprog) If Debug Tool finds this data set, you can begin to debug your LangX COBOL program. If Debug Tool does not find the data set, enter the SET SOURCE or SET DEFAULT LISTINGS command to tell Debug Tool where to find the debug information. 11

12 Contributing Authors: Vikram Manchala, Eric Lin, Elizabeth Spangler Editor: Elizabeth Spangler Copyright IBM Corporation 2011 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