Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RPGLE Debug Problem, Source does not prompts

213 views
Skip to first unread message

Ammar Farooq

unread,
Dec 2, 2003, 5:26:53 AM12/2/03
to
Hi
I have RPGLE programs (V5R1), compiled with DBGVIEW(*All) option.
I have tried all possible options for Debug:
UPDPROD(*YES)
OPMSRC(*YES)
DSPMODSRC(*YES)
But all in vain. I have tried both batch and interactive modes for
debug, but no source shown when program is run.

The process I use is :
*Compile the RPGLE program with DBGVIEW(*ALL) option.
*STRDBG PGM(Name), UPDPROD(*YES), OPMSRC(*YES), DSPMODSRC(*YES)
*The source of the program is shown initially, and I put the
breakpoints at start and at all necessary point required
*Then I call Program ABC, which after calling many other programs (not
aware of), calls my program (as it shows the DSPLY msg written by me
in the same program). But the source is not shown or the source does
not stops at the breakpoints inserted.
* I have used the Batch mode also, by using the Start service program,
but no result.

Thanks in advance for your time

Regards
Ammar Farooq

Dr. Ugo Gagliardelli

unread,
Dec 2, 2003, 6:20:18 AM12/2/03
to
Ammar Farooq wrote:

> Hi
> I have RPGLE programs (V5R1), compiled with DBGVIEW(*All) option.
> I have tried all possible options for Debug:
> UPDPROD(*YES)
> OPMSRC(*YES)
> DSPMODSRC(*YES)
> But all in vain. I have tried both batch and interactive modes for
> debug, but no source shown when program is run.

There were some WDS PTF to fix that.
--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda
Spamers iros a la mierda/Spamers allez vous faire foutre
Spammers loop schijten/Spammers macht Euch vom Acker

Barbara Morris

unread,
Dec 2, 2003, 10:32:50 AM12/2/03
to
Ammar Farooq wrote:
> ...

> The process I use is :
> *Compile the RPGLE program with DBGVIEW(*ALL) option.
> *STRDBG PGM(Name), UPDPROD(*YES), OPMSRC(*YES), DSPMODSRC(*YES)
> *The source of the program is shown initially, and I put the
> breakpoints at start and at all necessary point required
> *Then I call Program ABC, which after calling many other programs (not
> aware of), calls my program (as it shows the DSPLY msg written by me
> in the same program). But the source is not shown or the source does
> not stops at the breakpoints inserted.
> ...

Whenever this happens to me, it's because a different version of my
program is being called. If your program is stopping at the DSPLY, you
have a chance to do a DSPJOB (Sys-req option 3) and check your call
stack (option 11) to see exactly what program is being called.

The usual reasons for a different program being called are
- the call to your program is not library-qualified, and a different
program is first in the library list
- same situation, but even though your debugged program is first
in the library list, the program that calls it has already called
the program in a different library, and it wants to keep calling
that same one (to solve this problem, just sign off and start again)
- the call to your program is library-qualified, and you are trying
to debug a program in a different library (to solve this, you might
have to make a temporary version of the calling program to get it
to call your program

Thad Rizzi

unread,
Dec 2, 2003, 11:58:26 AM12/2/03
to
"Dr. Ugo Gagliardelli" <do...@spam.please> wrote in message news:<bqhsi9$sh6$4...@panco.nettuno.it>...

> Ammar Farooq wrote:
>
> > Hi
> > I have RPGLE programs (V5R1), compiled with DBGVIEW(*All) option.
> > I have tried all possible options for Debug:
> > UPDPROD(*YES)
> > OPMSRC(*YES)
> > DSPMODSRC(*YES)
> > But all in vain. I have tried both batch and interactive modes for
> > debug, but no source shown when program is run.
> There were some WDS PTF to fix that.


If it is a ILE program try changing OPMSRC(*YES) to OPMSRC(*NO).

Ammar Farooq

unread,
Dec 3, 2003, 1:24:59 AM12/3/03
to
Barbara Morris <bmo...@ca.ibm.com> wrote in message news:<3FCCB0A2...@ca.ibm.com>...

Well, thanks all of you for your kind suggestions. But the situation
is that
* The breakpoints are inserted properly
* There is only one program on the system (no duplicate) and only that
program is being executed (confirmed due to the msgs it is writing)
plus no library-qualified path
* OPMSRC(*NO) also tried, but in vain
* The DSPLY command I am using is writing in a MSGQ , so not
displaying on the screen, rather in the MSGQ
* Plus the program does prompts , when it is called alone, i.e., when
I pass dummy parameters , and call the program XYZ only. (I have
source only of XYZ)
* The ABC program after calling many other programs calls the XYZ but
it does not prompts on the breakpoint when called from ABC.

So, pls consider the above factors and then see where am I making
mistake.
The dummy parameters cant be used for checking the program as, the
parameters have huge data structures, I used the dummy paramteres of 2
chars each, just to make sure that there is problem in the program or
something else.

Looking forward to hear soon

Thanks again for your time.

Regards
Ammar Farooq

Joep Beckeringh

unread,
Dec 3, 2003, 7:26:54 AM12/3/03
to
Ammar,

1. Is the program running in the same job that you issued STRDBG in? If it
is, then why don't you DSPLY to the screen?
2. Did you check that it is the program that is running, as Barbara
suggested, through DSPJOB?

Other suggestions:
- Set a breakpoint in *INZSR
- DSPLY to the screen; call the program; when the DSPLY is executed go to a
command line (e.g. with the attention key) and then issue STRDBG. It should
take you right to the executing line.

Joep Beckeringh

"Ammar Farooq" <ammar...@yahoo.com> schreef in bericht
news:1d4eafdf.03120...@posting.google.com...

Terence

unread,
Dec 3, 2003, 8:34:06 AM12/3/03
to
ammar...@yahoo.com (Ammar Farooq) wrote in message news:<1d4eafdf.03120...@posting.google.com>...


First thing is get rid of OPMSRC(*YES). That tells the debugger you
are debugging RPG-III source and not ILE. I think its ignored for
ILE programs, but take it out just in case.

0 new messages