Closed as program error.
If an operational dump is generated (SERRC_RETURN or SERRC_EXIT) by an application then the Toolkit 1) Displays message 'execution may have stopped between statements' 2) Displays popup 'the following exception has occurred' ...... Select which action to take etc etc 3a) If we select the default 'Step exception handler' then the next source line is displayed provided the exception is SERRC_RETURN. 3b) If the operational dump is SERRC_EXIT then if the option 'retry exeception' is selected then the user can examine the situation to ascertain the cause of the exception. If a control dump is generated by an application then the Toolkit 1) Displays message 'application terminated' This means that if a control dump occurs then the application A) May not be aware that it has occured. B) Cannot examine the situation to ascertain why the control dump occurred.
APAR NUMBER: PJ31255 PRODUCT: TPF4 FUNCTIONAL AREA: DEBUG TOOL SUPPORT SHIPPED IN PUT: 21 ABSTRACT: Debug on System Error enhancement - stop on all system errors APAR CONTENTS: FEATURE TYPE STATUS NAME Base Copy Changed source/cp/base/cudu40.cpy Base CPP Changed source/rt/base/cud1ev.cpp PREREQUISITE APARS: To be applied in order listed. Base Copy Changed source/cp/base/cudu40.cpy PJ25981(10) PJ26008(10) PJ26600(11) PJ26784(12) PJ26923(12) PJ26951(13) PJ27383(13) PJ27441(14) PJ27563(14) PJ27871(15) PJ27905(15) PJ28235(16) PJ28649(17) PJ28765(17) PJ29121(18) PJ29282(18) PJ29315(18) PJ29326(18) PJ29570(19) PJ29573(19) PJ30282(20) PJ30796(20) PJ30832(20) PJ31041(20) PJ31278(21) PJ31678(21) Base CPP Changed source/rt/base/cud1ev.cpp PJ28649(17) PJ28809(17) PJ29585(18) PJ29709(19) PJ29844(19) PJ29858(19) PJ29891(19) PJ29592(19) PJ30127(19) PJ30139(19) PJ30221(20) PJ30282(20) PJ30805(20) PJ31041(20) PJ31517(21) PJ31678(21) COMMENTS: Prior to this APAR debug on system error would only capture dumps that were taken in debuggable code. (That is, real time segments that are not marked as NODBUG).
SOLUTION: With PJ31255 applied, Debug on System Error will trap all ECB-related system errors. For dumps that occur outside of a real-time segment, the debugger will stop at the instruction causing the error so the user may investigate the dump. Following this however the dump will still be taken in the ECB when the user resumes execution, regardless of any changes the user might make while the debugger is stopped. For all dumps that occur within real-time debuggable code the behavior will remain as before. DEPENDENCIES SEGMENTS TO BE ASSEMBLED OR COMPILED: ccvage.asm SEGMENTS TO BE LINK EDITED: cud140.exe (Shipped in Tar File) cps040.exe COREQS: None. MIGRATION CONSIDERATIONS: None. UPDATED INFORMATION UNITS: None. See your IBM representative if you need additional information. DOWNLOAD INSTRUCTIONS: http://www.ibm.com/software/htp/tpf/pages/maint.htm -- END APAR PJ31255
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
CUDU40 CUD1EV CCVAGE CUD140 CPS040
Fixed component name
Fixed component ID
Applicable component levels