Posted: Tue Sep 13, 2005 5:00 am Post subject: DFHTU630 CICS Trace Utility Program
Hi Friends,
I need your kind suggestion and help in tackling the following problems.
1) My primary objective is to convert the Quasi Re-entrant statements within my source module to Thread safe. In order to identify the statements within my source programs that are Quasi Reentrant or Thread Safe I ran the CICS TRACE utility called DFHTU630. Even though the Trace utility DFHTU630 notifies me that the following statements in the source program are Quasi Reentrant or Thread safe, I am not able to compare them with the statements in my source program. Can you all please tell me how to handle this ? It will be good if you can send me any documents regarding how to read the output from the CICS TRACE utility DFHTU630.
2) How can we prevent the CICS statements from shifting from Thread safe mode to Quasi Reentrant mode or vice versa?
2) How can we prevent the CICS statements from shifting from Thread safe mode to Quasi Reentrant mode or vice versa?
CICS introduced the concept of Open Transaction Environment(OTE) .OTE introduces a new class of TCB called an open TCB, which can be used by threadsafe applications. An open TCB is characterized by the fact it is assigned to a CICS task for the life of the CICS task and multiple OTE TCBs may run concurrently in CICS. A threadsafe application is defined as a program which uses appropriate serialization techniques, such as compare and swap or enqueue, when accessing any shared resource(s). It must be capable of running concurrently on multiple TCBs, and must not rely on quasi-reentrancy to serialize access to shared resources and storage.
Posted: Thu Sep 22, 2005 9:36 am Post subject: DFHTU630 Trace Utility Program
Hi Kolusu,
I am really thankful to you for the help.The link which you provided me was really useful. I was able to understand more on Threadsafe concept and was able to relate some of the Trace Output entries. But my problem is still not solved.
I am pasting a part of the CICS Trace Output which I got here.
CICS OUTPUT - SHORT Format
____________________________
In the above Trace Output, the TCB ID with L8000 denotes a Threadsafe statement within the actual source program and that with QR denotes a Non-Threadsafe program. My objective is to analyse this CICS Trace output and find out the corresponding statements in the actual source program that are Threadsafe and that are non Threadsafe. ie, I should be able to relate one L8000 TCB ID with the corresponding Program statement. I couldn't proceed on this in any way. I tried all the available resources you had send me as well some other materials I obtained from internet. But I am not satisfied.
Can you please help me in interpreting the corresponding statements in the source program ? Can you please provide me some tips on How to identify the program statements based on this CIS Trace? It will be great, if you can guide me on this.
In the above Trace Output, the TCB ID with L8000 denotes a Threadsafe statement within the actual source program and that with QR denotes a Non-Threadsafe program.
The QR in your trace is a LINK command. LINK command is threadsafe when it is used to link to a program in a local CICS region. It is non-threadsafe when it is used to link to a program in a remote CICS region. So check that.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
