Messages similar to these are appearing in the log.
0092023 13.11.21 IDMS DC171068 V82 RBE ERROR ON RETURN TO DIALOG DIALOG01 FROM PROGRAM PROGRAM1
19564560 F5F5F5F8 F4F50000 D9C2C55C D9C5C3D6 D9C4F0F3 40404040 40404040 40404040 *555845..RBE*RECORD03 *
...
195646A0 40404040 40404040 40404040 40404040 40404040 40404040 40404040 40404040 * *
...
CONTENTS THROUGH 19564FB7 SAME AS ABOVE LINE.
0092023 13.11.21 END OF SNAP
0092023 13.11.21 IDMS DC171067 V82 RBE AT <195646AC> WAS OVERLAYED ON LINK TO USER PROGRAM
0092023 13.11.21 IDMS DC466014 V82 Abort occurred in dialog DIALOG01 process DLG1-RP version 0001
0092023 13.11.21 IDMS DC466015 V82 At offset 31F0 source sequence number 00016000
0092023 13.11.21 IDMS DC466013 V82 Source line 00015900 DO.
0092023 13.11.21 IDMS DC466013 V82 Source line 00016000 LINK TO PROGRAM 'PROGRAM1' USING (RECORD01,
0092023 13.11.21 IDMS DC466013 V82 Source line 00016100 RECORD02,
What does this mean?
Release : All supported releases.
The ADS runtime system maintains dialog work records in storage in control blocks called RBBs and RBEs. When a dialog calls a cobol or assembler program and passes such a record to it, on return to ADS, the runtime system verifies that the RBE* eyecatcher in the control block has not been overwritten. It can do this because there is enough information in each RBE to know where the next one should start.
If it has been overwritten, message DC171068 is issued to identify the names of the involved dialog and program. The RBBs are snapped to the log, and then message DC171067 identifies the address at which ADS was expecting to see an RBE.
The most likely cause of this problem is that the program was compiled at a time when the record in the previous RBE (RECORD03 in the above example) was defined to be longer than it was at the time the dialog was compiled. Make sure that all involved programs using the same work record were compiled at times when the record had the same length.