• Subject: Call Stack Entry does not exist -- CPF8E25
  • From: bvining@xxxxxxxxxxxx
  • Date: Fri, 19 Dec 97 13:51:29 CST


One of the debugger developers suggests that PTF MF17841 (Apar SA70085)
should address your problem.

Bruce Vining

>I have an irritating problem which is driving me crazy.  I am on V3R2
>and latest cum ptf 97322.
>When you use debug on a program with many modules, I am able to use the
>F11 to display variables on the CL modules but not on the ILE RPG
>modules.  It gives me "Call Stack Entry does not exist" which is
>CPF8E25.   It will let me step with F10.  I have recompiled all the
>modules, recreated the program and still no luck.  Used the DSPPGM and
>DSPMOD to verify the modules and source files.  I have tried creating
>the modules with DBGVIEW(*LIST) to no avail (I usually do
>DBGVIEW(*SOURCE)) .  I have also tried OPTIMIZE(*BASIC) and
>OPTIMIZE(*FULL) to no avail. (I usually do OPTIMIZE(*NONE)).  This
>started happening after the latest cum tape 97322.  What gives?  It is
>pretty random.  Once it happens in a program, it does not go away.  I
>have also cleared QRPLOBJ to avoid wrong object being debugged.   I now
>have to create a program for each of the modules to debug.  This is
>insane.  (or is this IBM's way of taking revenge on poor V3R2 people
>:-(( ).  No I am not calling IBM with their new feature. No support line
>Thank You.
>Dave Mahadevan.. mailto:mahadevan@fuse.net

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].