Top Secret U0743 Abend in CICS
search cancel

Top Secret U0743 Abend in CICS

book

Article ID: 191201

calendar_today

Updated On:

Products

Top Secret Top Secret - LDAP WEB ADMINISTRATOR FOR TOP SECRET

Issue/Introduction

During initialization of one of the CICS regions, a U0743 Abend in module CAKSMSEV occurred. 
Below is the symptom dump from the log of the CICS region:

IEA995I SYMPTOM DUMP OUTPUT  093                                        
  USER COMPLETION CODE=0743 REASON CODE=00000007                        
 TIME=03.10.12  SEQ=01977  CPU=xxxx  ASID=nnnn                          
 PSW AT TIME OF ERROR  070C1000   908D798C  ILC 2  INTC 0D              
   ACTIVE MODULE           ADDRESS=00000000_108D7570  OFFSET=0000041C   
   NAME=CAKSMSEV                                                        


This is the only occurrence of this abend and it only occurred in one region.  

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

The U0753 abend occurred in CAKSMSERV at offset +x'3DC' with a reason code 7.                                                              
                                                                            
This issue has been already seen in the past and for some undetermined reasons and evidences due to a lack of appropriated clues and elements no diagnostic could be done.                                                   
                                                                            
ENF calls TSS twice when CICS region starts and then ends up with an abend and CICS can't start.                                                       
                                                                            
On next start, CICS region comes up and runs fine.                          
                                                                            
It has been noticed that this issue very rarely occurs and every time the second CICS start is fine.  

The paper dump does not contain the areas of storage that are needed to help us determine what is causing the error.                                       
                                                                            
The only thing that can done is to set a slip trap in order to catch a system dump on next occurrence as follows:                                         
                                                                            
SLIP SET,C=U0743,JOBNAME=cicsjobname,SDATA=(psa,csa,sqa,lsqa,sum,trt,rgn),ID=TSS,ML=1,END