IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search Log in to check your private messages Log in
 

Unable to debug a linked CICS program using expeditor tool


IBM Mainframe Forums -> Compuware & Other Tools
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
moumi das
Warnings : 1

New User


Joined: 21 Dec 2009
Posts: 10
Location: Kolkata

PostPosted: Thu May 23, 2013 2:48 pm
Reply with quote

I am trying to debug a CICS program say B . Program A links program B . When i am invoking the transaction, Program A is invoked and when the control goes to the line where i call B , control comes out immediately with a error return code .
I have tried using INTERCEPT and SOURCE commands but both the commands takes the control inside the program and comes out of B program immediately .
Please let me know how can we debug the Program B step by step ?
Back to top
View user's profile Send private message
enrico-sorichetti

Senior Member


Joined: 14 Mar 2007
Posts: 10697
Location: italy

PostPosted: Thu May 23, 2013 5:08 pm
Reply with quote

wow....

two misses out of two shots ...

expeditor is not an IBM tool
nothing related to DB2 in the question

icon_cool.gif

Use [URL] BBCode for Links
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8568
Location: Dubuque, Iowa, USA

PostPosted: Thu May 23, 2013 5:56 pm
Reply with quote

You did not post nearly enough information to provide complete help. However, I can tell you that if program B is written in a language for which your site did not purchase Xpediter language support from Compuware (such as Assembler, for example) then the behavior you are seeing is normal and expected for such a case.

If your site did purchase Xpediter for the language program B is written in, then it is possible that program B was not compiled to allow use of Xpediter (in which case you need to recompile program B).

For anything else, you will need to work with your site support group since they understand your environment and know how Xpediter was installed and the languages it supports at your site. Only someone working at your site is going to be able to help you get the debug of program B working -- assuming that it turns out to be possible to use Xpediter on program B, of course.
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Thu May 23, 2013 10:26 pm
Reply with quote

When you use SOURCE, you still have to set a breakpoint.

So, when you get stopped inthe calling program, THEN do the SOURCE command, then scroll down and place a breakpoint on the first good line.

It may be that the subroutine is not available in the DDIO file. Was it compiled in a way that makes it appear there? We currently use Debug Tool, and all of our SCLM compiles build the SYSDEBUG as needed. When we used Expeditor, we had to recompile especially for debugging. The debug compile had extra steps to write to a DDIO file. If that's what you do, then the subroutine will also need to recompiled that way.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> Compuware & Other Tools

 

Search our Forum:

Similar Topics
Topic Forum Replies
No new posts How to get RBA value from CICS EVENT CICS 4
No new posts REXX/CLIST tool for BCSR and EDSR CLIST & REXX 2
This topic is locked: you cannot edit posts or make replies. Sample CICS Webservices Program CICS 1
No new posts Calling Rexx program from Cobol CLIST & REXX 12
No new posts How to define transaction that trigge... CICS 2

Back to Top