|
View previous topic :: View next topic
|
| Author |
Message |
jdeeponline
New User
Joined: 08 Sep 2009
Posts: 27
Location: Charlotte
|
|
|
|
I want to extract EIB data for a CICS task. I want to know if every command in CICS (Every time I use EXEC CICS) a corresponding set of EIB information is generated or not.
I am assuming that whenever I issue a CICS command I can use the corresponding EIB by referring directly to the EIB variables. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| If you use CEDF to trace through a transaction, you will note that the EIB data is maintained continuously. Some of the data changes every command, some of it only at certain times. The EIB data can be accessed at any time, though, in your program. |
|
| Back to top |
|
|
jdeeponline
New User
Joined: 08 Sep 2009
Posts: 27
Location: Charlotte
|
|
|
|
| So there is no specific command to procure the EIB data. It is just a associated parameter(s) that comes along with a CICS command. Is that correct? |
|
| Back to top |
|
|
Binop B
Active User
Joined: 18 Jun 2009
Posts: 407
Location: Nashville, TN
|
|
|
|
Hi jdeep,
 What do u mean by
| Quote: |
| So there is no specific command to procure the EIB data |
As Robert mentioned, you can always use or procure the EIB variables in the program. Elaborating more on Robert's point, if its for debugging purposes using CEDF is the easiest way to know how the EIB variables have changed during the course of a transaction. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| If you look at a CICS compile, you will note that the EIB is inserted into your program by the preprocessor. You have no control over this -- you get the EIB whether you want it or not. hence my statement that these variables are constantly available. You can reference them without having to address them, or doing anything to make them available. |
|
| Back to top |
|
|
jdeeponline
New User
Joined: 08 Sep 2009
Posts: 27
Location: Charlotte
|
|
|
|
Thanks Robert.
| Quote: |
| If you look at a CICS compile, you will note that the EIB is inserted into your program by the preprocessor. You have no control over this -- you get the EIB whether you want it or not. |
If the program's preprocessor assigns these values, then I am assuming the EIB values will stay constant throughout the program, no matter how many times I use "EXEC CICS" statements.
Is that correct? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
with one exception ...
| Quote: |
| The EXEC CICS ASKTIME command is used to update the EIBDATE and EIBTIME fields with the current date and time. These fields contain either the date and time at which the current CICS task started or the date and time at which the latest ASKTIME command was executed whichever is the more recent. |
|
|
| Back to top |
|
|
jdeeponline
New User
Joined: 08 Sep 2009
Posts: 27
Location: Charlotte
|
|
|
|
That should be fine.
I am looking for EIBTASKN which is created for all CICS tasks. What I couldn't ensure was, whether each "EXEC CICS" in the program would be considered a separate and new CICS task and hence, lead to a new EIBTASKN everytime, or if it is set at the time of preprocessing of the program itself and remain the same as long as the program is in control. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| There's a new task number every time you do EXEC CICS START but using LINK or XCTL will not change the task number. |
|
| Back to top |
|
|
|
|
