Question & Answer
Question
Why am I getting a U4093 abend when introducing COBOL V6.1 code into our CICS Environment? We are running Compuware's Xpediter/CICS product.
I am currently running CICS Transaction Server for z/OS (CICS TS) V5.1 on z/OS V2.1 and we are beginning to introduce COBOL V6.1 code into our environment. I have an application that runs daily in each of our CICS regions that has been failing with U4093 abends sporadically since we added some Cobol 6 modules into the call chain. The problem does not happen all the time but it seems pretty certain that the problem only occurs when COBOL 6 programs are involved. The Error Message I see is:
+CEE1000S z/OS INTERNAL ABEND. ABCODE = 4093 REASON = 00000034
I have tried to do some initial analysis to figure out this problem, and one thing that I noticed is that in one of the COBOL modules called when the transaction runs I see a reference to a Xpediter module (DBUGCXI) in the eyecatcher. Not sure if this is relevant however.
*}.q.}...DBUGCXI *
*.........K.&....*
*.K..CEE......J..*
*................*
*................*
*CEEEV005........*
*.........J......*
*............2013*
*0913093400090300*
eventually we see:
*IGZCEV5 ........*
*..........U.....*
*............2016*
*0527091300020100*
*..UI38246.......*
Could the root of the problem be the fact that somehow Xpediter is calling old COBOL or LE modules? I just installed a new version of Xpediter.
Answer
Per the error message you are getting an 4093 abend with a reason code of x'34'
The U4093 is a general LE abend.
U4093 (X'FFD')
Explanation: Abend issued during initialization when errors were detected
The reason code means:
X'34' (52) A language-specific event handler returned to initialization
with a feedback code, causing immediate termination.
Discussions with Compuware Xpediter support has provided an explanation of what you are seeing and the cause of the problem.
In regards to Xpediter and it's relationship to this problem, if you are using a FORCE option to stop Xpediter, it can cause this kind of abend. The FORCE option deallocates storage making an address (pointer) to this area invalid leading to the 4093 abends. If you remove the FORCE option you should no longer see the abends.
The problem might not occur if all COBOL programs running under the transaction that is abending are compiled with the SAME Enterprise COBOL compiler, either COBOL V6 or COBOL V4. In this case, the application mixes Enterprise COBOL V6 with COBOL V4. Xpediter's LE event handler for COBOL V6 is LEIEV004 (module DBUGLEI) and for COBOL V4 is LEIEV005 (module DBUGLEI). In your description of the problem you showed that you have a reference to a ****V005 module (in the eyecatcher) . So it appears that you are running an older version of Xpediter, not the newer version that you thought you were running.
When the COBOL V6 program is about to start, LE will pass control to Xpediter's LE event handler LEIEV004. Later, when the COBOL V4 program is about to start, LE will pass control to LEIEV005.
If both COBOL programs are compiled with the same compiler, then LE will only pass control to Xpediter LE event handler (once) when the 1st program is about to start. LE will not subsequently pass control to Xpediter when the 2nd COBOL program is about to start (because the 2nd program is compiled using the same Compiler and hence the same LE event handler).
If you run XPOF FORCE after the 1st COBOL program is started but before the 2nd program is started, LE will not pass control to Xpediter on the 2nd program. So, the 4093 abend will not occur even if Xpediter storage is released and re-used as a result of XPOF FORCE.
The bottom line is this:
Xpediter's LE event handler supports Enterprise COBOL V6.
The root cause of the problem is using XPOF FORCE.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
20 July 2021
UID
dwa1379717