When we debug using STRISDB, Debug screen is not opening instead we get the error screen.
2 posters
Page 1 of 1
When we debug using STRISDB, Debug screen is not opening instead we get the error screen.
Perhaps this issue with the Action Bar handler in CA 2E. As there is no source for the program YAABSLI it defaults to the terminal.
Using QUIT when the terminal is displayed will skip over debug of the program YAABSLI.
Using QUIT when the terminal is displayed will skip over debug of the program YAABSLI.
2e uses strdbg
In a model object list, option 16 (run) will start the function with STRDBG enabled,
When you are compiling in RPGLE as you should be, then the function will be in debug mode and you can set breakpoints and proceed.
If you want to use ISDB, then run the function outside the model, as normal.
When you are compiling in RPGLE as you should be, then the function will be in debug mode and you can set breakpoints and proceed.
If you want to use ISDB, then run the function outside the model, as normal.
yorkshireman- Posts : 2
Join date : 2013-01-15
Similar topics
» Debug a batch program1
» Debug a batch program
» How can I use STRISDB and STRDBG at the same time?
» How can previous screen be retained
» Pointer error
» Debug a batch program
» How can I use STRISDB and STRDBG at the same time?
» How can previous screen be retained
» Pointer error
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|