Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
How to capture ASRA program thru HANDLE ABEND

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS
View previous topic :: :: View next topic  
Author Message
himanshu verma

New User


Joined: 07 Apr 2008
Posts: 3
Location: mumbai

PostPosted: Thu Apr 15, 2010 3:02 pm    Post subject: How to capture ASRA program thru HANDLE ABEND
Reply with quote

Hi,

I have a CICS module and i am trying to capture the ASRA abend (occured in the cobol statement) thru the HANDLE ABEND comand but it is not going to the label defined in the handle condition.

Does this command handles the above mentioned scenario also or it only handles the CICS command abends?

Thanks, icon_rolleyes.gif
Back to top
View user's profile Send private message

Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2504
Location: Atlanta, Georgia, USA

PostPosted: Thu Apr 15, 2010 4:23 pm    Post subject: Reply to: How to capture ASRA program thru HANDLE ABEND
Reply with quote

When you define your HANDLE ABEND LABEL, to capture an ASRA (as well as many other abends), the logic will be driven to the LABEL name which you've specified. But, I'm not a big fan of this HANDLE.

Instead, just let it abend normally and review the Transaction Dump and accompanying TRACE Table.

Your Tech Support folks should be able to assist you regarding the Batch JOB, which prints the Dump. You should also familiarize yourself in Debugging, a lost art form.

By allowing the Dump to be raised without the HANDLE ABEND, you'll get a snapshot of what happened at the time of the ABEND and this is what you want.

Invoking a HANDLE ABEND and/or an ASSIGN ABCODE, always alters the internals (such as the EIB), because the EIB may provide valuable information and possibly, be a key component which caused the ASRA in the first place.

You need to recompile your program, specifying the options LIST,NOOFFSET which will generate the Assembler expansion, because you will need this for Debugging.

Bill
Back to top
View user's profile Send private message
Rogerio Ferreira Coelho

New User


Joined: 13 Jun 2007
Posts: 11
Location: Sao Paulo - Brazil

PostPosted: Sat May 01, 2010 12:48 am    Post subject:
Reply with quote

You need use these commad, and some arithimetic to solve the ASRA offset:
EXEC CICS ASSIGN ABCODE (WS-DUMP-ABCODE)
ASRAINTRPT(WS-DUMP-ASRAINTRPT)
ASRAKEY (WS-DUMP-ASRAKEY)
ASRAPSW (WS-DUMP-ASRAPSW)
PROGRAM (WS-DUMP-PGRMID)
END-EXEC.

EXEC CICS HANDLE ABEND CANCEL END-EXEC.

EXEC CICS INQUIRE PROGRAM(WS-DUMP-PGRMID)
LOADPOINT(WS-DUMP-LOAD-POINT)
END-EXEC.
Back to top
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1243
Location: Israel

PostPosted: Sat May 01, 2010 6:01 pm    Post subject:
Reply with quote

Bill O'Boyle wrote:
But, I'm not a big fan of this HANDLE.
I agree with you, Bill.

/RANT ON
I was very surprised, when I started my current work, to see that the company policy is to use HANDLE ABEND in all sub-programs.
These programs are supposed to issue a DUMP and return to the calling program with a non-zero return code.
The main program then terminates with a message like "unable to complete the transaction".

When this happens, the ABEND is not accounted in CICS (the transaction terminates normally, after all), but when I tried to explain this to my bosses, they just refused to understand!
Oh well! Less ABENDS, less pressure from above...
/RANT OFF
Back to top
View user's profile Send private message
valyk

Active User


Joined: 16 Apr 2008
Posts: 104
Location: South Carolina

PostPosted: Mon May 03, 2010 6:31 pm    Post subject:
Reply with quote

Marso wrote:
Bill O'Boyle wrote:
But, I'm not a big fan of this HANDLE.
I agree with you, Bill.

/RANT ON
I was very surprised, when I started my current work, to see that the company policy is to use HANDLE ABEND in all sub-programs.
These programs are supposed to issue a DUMP and return to the calling program with a non-zero return code.
The main program then terminates with a message like "unable to complete the transaction".

When this happens, the ABEND is not accounted in CICS (the transaction terminates normally, after all), but when I tried to explain this to my bosses, they just refused to understand!
Oh well! Less ABENDS, less pressure from above...
/RANT OFF


This is the same sort of non-sense that goes on at my shop. Our application areas are 'graded' by their abends. So of course they avoid abends like the plague. They will issue HANDLE ABENDS, and then abend with a blank return code. Apparently their upper management doesn't care if their application recieves an abend with a blank abend code. It's almost like if you can see the abend code, then an abend didn't happen...

Upper management doesn't understand that in some circumstances recieving an abend is acceptable...
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts How to write Rexx program to size and... sreejeshcs CLIST & REXX 14 Thu Oct 12, 2017 7:26 am
No new posts Accessing CICS tran with map from JCL... navdeepaggarwal CICS 5 Tue Oct 03, 2017 6:15 pm
No new posts Writing a file using online program grvtomar PL/I & Assembler 3 Fri Jun 30, 2017 1:06 pm
No new posts pre-compiler for program in an HFS Pedro DB2 0 Fri Jun 23, 2017 11:13 pm
No new posts Compiling program in endeavor for tra... RALAKKAL Compuware & Other Tools 4 Mon Jun 05, 2017 8:27 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us