I just created IBM RFE 153397 to fix the CEEDUMP process. It does not
currently print the LE Stack frame storage of LE conforming assembler
programs in the Traceback list. I would appreciate all of your votes.
After going through the process of creating an RFE, maybe I understand
why this ha
s the additional information.
On 8/8/2021 7:08 PM, Larry Slaten wrote:
We are in the process of migrating from COBOL V4.2 to V6.2. We are
using most if not all of the options that relate to testing (e.g. PC,
RULES, NC, SSR, etc.) when compiling for test environments.
Additionally we have NOTEST(DWARF
We are in the process of migrating from COBOL V4.2 to V6.2. We are
using most if not all of the options that relate to testing (e.g. PC,
RULES, NC, SSR, etc.) when compiling for test environments.
Additionally we have NOTEST(DWARF) set for both testing and production
compile options. Program
Thanks to everyone for their input. Since I was already using C/C++ I/0
functions to access a card file I thought that it would be simple enough
to setup the DD:SYSLIB and that it would actually point me to a DCB
address that I could use in my BLDL and LOAD macro(s). I ended up
defining the D
I am attempting to use the C/C++ FOPEN function to open a SYSLIB DD
pointing to a concatenation of executable libraries. Then extract the
DCB address so that I can use it to populate the LOAD and BLDL macro.
This would make it easier to keep the root program RENT. I realize that
I can code t
