Rational Developer for System z, Version 7.6

Debugging a local CICS transaction with TXSeries

To prepare for debugging, follow these steps to locate the process ID for your CICS® application server:

  1. In the TXSeries® Administration tool, click Subsystem > CICS Terminal.
  2. When you are prompted, select the correct CICS server for your CICS region.
  3. Enter the following in the CICS terminal:
    CEMT INQUIRE TASK

    The output of this command will be the process ID for your CICS application server. You will attach to this process for the purpose of debugging.

Note: This document describes the process for debugging a COBOL CICS transaction. The process for debugging a PL/I CICS transaction is similar. The only difference is that the name of the PL/I program will be PROGRAM_NAME.IBMPLI (where PROGRAM_NAME is the name of your program) instead of TIMEZONE.IBMCOB.
First you must make a "new copy" of the program. This unloads TIMEZONE.IBMCOB from the CICS application server. Open a local terminal for your CICS region and type the following:

CEMT SET PROGRAM(TIMEZONE) NEW

Note: Make sure you type CEMT in all capital letters. Otherwise, the command will not work.

Attaching to CICS servers.

  1. Open the z/OS® Projects perspective.
  2. From the Run pull-down menu, select Debug.
  3. Select Attach to a Running Process and click New.
  4. Select the Main tab. In the Project field, select the project you are working with.
  5. Click Browse next to the Process ID input field. Minimize any Windows® console windows that appear.
  6. Select the first "cicsas.exe" process listed. Click OK.
  7. Click Debug.
  8. Minimize any Windows console windows that appear.
  9. If a pop-up window appears with the message "No error message text available" click OK.
  10. Important: Repeat these steps with new debug configurations until you have attached to all the running instances of cicsas.exe.
Establishing a breakpoint on the load of the CICS executable program. (In this case, TIMEZONE.IBMCOB.)
  1. Select the first running cicsas.exe process that you have attached to.
  2. Right-click in the Breakpoints view. Select Add Breakpoint, then Load.
  3. Enter TIMEZONE.IBMCOB for the library name. Click Finish.
Resuming the cicsas.exe processes.
  1. Expand the first running cicsas.exe process listed, if it is not already expanded. Right-click the line of text that starts with "State:".
  2. Select Resume.
  3. Repeat these steps for all the cicsas.exe processes that you are attached to.
Running the transaction.
  1. When the CICS terminal starts, type: TMZN
  2. Press Control (the 3270 terminal Return key).
  3. The CICS terminal execution should stop. (No arrow or time is displayed.)
Selecting the module.
  1. Select the Modules view.
  2. Find and expand TIMEZONE.IBMCOB.
  3. Expand TIMEZONE.OBJ.
  4. Expand TIMEZONE.cbl.
  5. Under TIMEZONE.cbl, you should see a picture of two gears next to TIMEZONE. Double click the picture. The TIMEZONE.cbl source is displayed.
Changing to the preprocessed source.
  1. Right-click the display of the TIMEZONE.cbl source code. Select Change Text File.
  2. Select the TIMEZONE.ppr file from the BuildOutput subdirectory of your project.
  3. Click OK. A preprocessed version of your COBOL source file is displayed with all the EXEC CICS lines expanded.
Setting the breakpoint.
  1. In the TIMEZONE.cbl source, set a breakpoint at the first executable line of COBOL source.
  2. From the Run pull-down menu, select Resume. You can now step through and debug your program.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)