| View previous topic :: View next topic |
| Author |
Message |
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
 Posted: Tue Aug 28, 2018 1:23 am Post subject: Capture IMS abend code 1041 |
 |
|
Is this possible at all. I'm deliberately (mis)testing an IMS batch program that performs DL/1 database calls. We have a database called DAT22 which is defined with an index databases DAT220.
I'm running Xpediter and have deliberately avoided allocating the DAT220 file. When I try and do a GU on DAT22, I crash with a U1041 abend which I understand is a catch-all abend for anything being wrong.
I can use the aa snap command in Xpediter and scroll through the program variables where I see
| Quote: |
02 DIBSTAT X(2) AI
02 DIBSEGM X(8) DAT220
|
which is neat and basically tells me what is wrong.
Even neater (if possible) would be to snap this so the user/developer doesn't have to use Fault Analyzer - they simply review SYSOUT (or whatever and the answer is there instead).
Is this doable ?
_________________
Michael |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12367
Topics: 75
Location: San Jose
|
| Posted: Tue Aug 28, 2018 10:25 am Post subject: |
|
|
misi01,
Unless I am gravely mistaken, don't you have a in house abend routine that you can call in case of errors?
If you don't have an in house abend routine, then you can call language environment CEE3ABD and get a dump too
| Code: |
01 W-CEE3ABD PIC X(08) VALUE 'CEE3ABD'.
01 W-ABEND-CODE PIC S9(9) COMP VALUE 16.
01 W-CLEAN-UP PIC S9(9) COMP VALUE 1.
IF IMS-STATUS-CODE NE SPACES
DISPLAY 'ERROR ENCOUNTERED ON IMS CALL'
DISPLAY 'CHECK FOR MISSING PARMS/INDEXES'
CALL W-CEE3ABD USING W-ABEND-CODE, W-CLEAN-UP
END-IF
|
_________________
Kolusu - DFSORT Development Team (IBM)
DFSORT is on the Web at:
www.ibm.com/storage/dfsort
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
| Posted: Wed Aug 29, 2018 2:43 am Post subject: |
|
|
Yes, we do have in house abend routines (Fault Analyzer).
My thought ws possibly to be able to return to the line AFTER the DL1 call and review the status code. If it's an "invalid" one, THEN I snap and abend.
As it is now, I never return to my Cobol program after the invalid DL1 call, I simply abend immediately with a 1041 abend.
_________________
Michael |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
