RTIMOUT parm in CICS

Norman Real · New User Joined: 31 Aug 2008 Posts: 4 Location: Singapore

Hi, we updated RTIMOUT parm of our CICS transaction profile to force AZCT abend when transaction is idle for 10 minutes. In the program's abend handler, we issue an abend when AZCT is issued. How can we go about forcing the transaction to sign out of cics and return to session manager after the abend?

Thanks.

Bill O'Boyle · Posted: Tue Oct 20, 2009 5:32 am

Is a user-written DFHPEP being invoked?

The DFHPEP commarea will contain the current and original abend-code, along with other information, such as the complete snapshot of the user's DFHEIBLK.

However, you can't sign-off a transaction. You can only sign-off a user.

With that, I'm unsure what you're referring to with the following -

Norman Real · New User Joined: 31 Aug 2008 Posts: 4 Location: Singapore

Hi Bill, no it's not a user-written DFHPEP. Sorry, what I meant was sign off the user and terminate the transaction (as if issuing a CESF LOGOFF).

Bill O'Boyle · Posted: Wed Oct 21, 2009 5:42 am

You can code EXEC CICS ASSIGN ABCODE in your program/transaction and if the user is still signed-on, then after obtaining the ABCODE and it's the one you're looking for, issue an EXEC CICS SIGNOFF.

Or, instead of the signoff, you could try an EXEC CICS ISSUE DISCONNECT.

If you're using CA-Top Secret, I believe they offer a programmable interface which you LINK-TO and issue a SIGNOFF.

Not sure about RACF or ACF2.

Bill

Norman Real · New User Joined: 31 Aug 2008 Posts: 4 Location: Singapore

Thanks Bill, will try out your suggestion then feedback how it goes

Norman Real · New User Joined: 31 Aug 2008 Posts: 4 Location: Singapore

Hi Bill, the solution we implemented is issuing the following commands in this order :

EXEC CICS SET TERM RELEASED
EXEC CICS ABEND
EXEC CICS RETURN

Immediately after idle timeout is hit, transaction ends and exits from CICS.

In the IBM manual, it mentioned that AZCT should be handled by issuing an ABEND to clear the TCTTE entries (?).

Initially the code was implemented without issuing the ABEND, after a few AZCT abends in the system, CICS would automatically restar and ATNB abends were issued as well. Any idea why repeated AZCT/ATNB abends caused the CICS to go down? TIA.

harish5002 · New User Joined: 21 Jul 2010 Posts: 23 Location: chennai

Hi,

I am very new for CICS. We are facing AZCT in CICS. I need to provide reason for the abend. Finally i got the information from this forum. I like this forum very much.

We are using the following command at the begging of CICS program.

EXEC CICS ABEND
CANCEL
ABCODE('TWAL')
END-EXEC.

Still we are facing the abend AZCT. Can u please suggest how to find the reason for this abend and how to avoid this problem. It will very very helpful. Please help me how to proceed.

Thanks in advance.....

Bill O'Boyle · Posted: Wed Feb 22, 2012 6:37 pm

Before issuing this user-abend, save the current DFHEIBLK in WS (length=85), along with an eyecatcher, so you can find it easily in the transaction-dump.

This will preserve the last API results and could give you information which may lead you to the reason for issuing this user-abend.

I'm not a big fan nor an advocate of user-abends.

Speak with your CICS Sysprog and/or Tech Services personnel about printing the transaction-dump as well as setting up a Trace using IBM transaction CETR.

You can also walk the transaction through CEDF, although this may be considered "Old School", you'll find that it works as advertised.

Mr. Bill

harish5002 · New User Joined: 21 Jul 2010 Posts: 23 Location: chennai

Thanks Bill.....

I think we are doing the same as below:

EXEC CICS ASSIGN
TWALENG(CICS-TWA-LENGTH)
END-EXEC.

is it fine or we need to code any other than this.