Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Trying to document a weird condition in CICS

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

Active User


Joined: 13 Jun 2012
Posts: 177
Location: United States

PostPosted: Fri Aug 30, 2019 11:19 pm    Post subject: Trying to document a weird condition in CICS
Reply with quote

I have an condition that causes a user to get locked out of CICS. It doesn't happen very often and I know how to correct it. But, I need to document what causes it and I am having a hard time with that.

The symptoms are a user is prevented from accessing CICS because they are already signed on at a different terminal. They could stay in this state until CICS is restarted, if I did not intervene. I can identify the user in the CICS tables, find the task that is being held and kill the task or terminal. No other users are impacted.

When I kill the task (or terminal) I get an abend and dump that shows the transaction is in a DB2 program and I can tell it is running under the Open API TCB (L8) as a TRUE exit. All of our CICS transactions are Psuedo-conversational, so there is no way it could have returned a screen and held on to the terminal session. There is no evidence of LOSTERM exit being driven, so the user did not break the connection before getting a response.

The only conclusion I can draw is the TCB either never got posted or it was posted under the wrong key. I can't come up with a good reason for why or how this could happen.
Back to top
View user's profile Send private message

John Poulakos

Active User


Joined: 13 Jun 2012
Posts: 177
Location: United States

PostPosted: Fri Dec 06, 2019 8:43 pm    Post subject:
Reply with quote

I determined the problem was caused by a recursive error in DB2. When this occurs, the enclave backward chain is broken and DB2 posts completion under the wrong storage key. (See CICS TRUE exit). The fix is to kill the task.
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 trigger enter key automatically call ... Ziko13 CICS 16 Fri Apr 03, 2020 2:53 pm
No new posts Can I use EXEC CICS START instead of ... smenjoge CICS 1 Sat Mar 21, 2020 1:41 am
No new posts Navigation program in CICS Ziko13 CICS 11 Fri Mar 06, 2020 2:30 pm
No new posts CICS Performance statistics ragava_b CICS 3 Mon Feb 17, 2020 12:38 pm
No new posts Using ICETOOL set return code as per ... Bhuvana Narasimhan DFSORT/ICETOOL 4 Fri Jan 24, 2020 12:58 pm

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