Can’t see overlay screen in debug

35 pts.
Program Debugging
I have HEADER, DETAILS & FOOTER screen, where DETAILS & FOOTER screen are set overlay. My pgm as below: WRITE HEADER WRITE FOOTER EXFMT DETAILS DOW NOT *IN03 EXFMT DETAILS ENDDO When i debug the pgm, only the 1st time i call the pgm i can see all 3 screen,but not 2nd times onwards. I was wondering how to display the overlay screen during debug. Is KEEP or ASSUME helps? Thank you.

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’m using RPGLE and I using STRDBG to debug the pgm.
I set the OVERLAY using SDA.

I’m using client access. During debugging the pgm, first time go into the loop is OK, which means all the screen can display, but not the 2nd time in the loop, bcoz only have EXFMT DETAILS but not WRITE HEADER (HEADER is the only screen that is not OVERLAY). I dont want to overwrite anything in the HEADER and FOOTER screen, thats y i only put EXFMT DETAILS in the loop.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • JennyMack
    Hi there Esteh400, Would you mind providing a little more information? What system are you using? Thanks, Jenny Community Manager
    4,280 pointsBadges:
  • philpl1jb
    This would be as/400 rpg or RPGLE Need to know is it RPG or RPGLE, what debugger are you using? Is it through Green Screen? Client Access? When you say the second call, are you ending the program and calling it from the same session or do you mean the second time the exfmt command is run in a sincle run of the program? Phil
    54,090 pointsBadges:
  • philpl1jb
    Haven't experienced that, and I don't use keep or asume.
    54,090 pointsBadges:
  • TomLiotta
    It's pretty clear that the system is an AS/400 or a successor; the sample programming is RPG IV. And DDS display files aren't used anywhere else. Still, the amount of info is too small. At least two more elements are needed. First, we can't guess what the DDS is like for the FOOTER and DETAIL records. Nor do we have any info on what parameters were used to create the DSPF. (RSTDSP(*NO)? DFRWRT(*YES)?) Second, as Phil noted, the meaning of "not 2nd times onwards" has multiple possibilities. Any interpretation has to take into account all the variations in DDS and creation. I'll add another item to the list -- debug. Does the question mean that the missing FOOTER happens during a debug session? If so, then the whole meaning of the question changes. Debug of a display problem should always be done after OVRDSPF DEV(<2nd-session>) so that the display file isn't interfered with by debug displays. Tom
    125,585 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: