|
View previous topic :: View next topic
|
| Author |
Message |
cvishu
Active User
Joined: 31 Jul 2007
Posts: 136
Location: india
|
|
|
|
After looking at what is use of TDQ and TSQ I still have questions...
| srinivas.u wrote: |
hi,
TDq -> if you want some processing should happen depending on the data that you have read from the screen for example.
user wants to print the screen, take the information write it to a TDQ
this will trigger a transaction which does the printing.
Trigger level tells n indicates, after nth record is written to a TDQ it should trigger the transaction associated with it.
TDQ has to be defined prior to use.
let me know if you need more with examples. |
I can understand the usage of TSQ , but could you explain TDQ with any other example , i still am not clear where TDQ would be better than TSQ ?
Thanks |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
You felt the need to revive a topic after almost 5 and 1/2 years?
A TDQ can point to a sequential file -- so if you want to retain the data past CICS shut down, for example, you could use an extrapartition TDQ (which is what a sequential file TDQ is called) to save the data. |
|
| Back to top |
|
|
cvishu
Active User
Joined: 31 Jul 2007
Posts: 136
Location: india
|
|
|
|
| Robert Sample wrote: |
You felt the need to revive a topic after almost 5 and 1/2 years?
|
My Google search brought up the page an i just posted my query 
Anyways thanks for the reply , just one confusion , i thought TDQ dont occupy physical memory , so when you say sequential file , i am a little confused.
could you explain a liitle elobrate..sorry if i sound dumb |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
There are intrapartition TD queues and extrapartition TD queues. I recommend you click the manuals link at the top of the page, find the CICS Language Reference and Programming Guide manuals and read up on them.
As far as TDQ not occupying physical memory, the manual specifically states in section 4.8.1:
| Quote: |
| "Intrapartition" refers to data on direct-access storage devices for use with one or more programs running as separate tasks. Data directed to or from these internal queues is referred to as intrapartition data; it must consist of variable-length records. All intrapartition transient data destinations are held as queues in the same VSAM data set, which is managed by CICS. An intrapartition destination requires a resource definition containing information that locates the queue in the intrapartition data set. Intrapartition queues can be associated with either a terminal or an output data set. When data is written to the queue by a user task, the queue can be used subsequently as input data by other tasks within the CICS region. All access is sequential, governed by read and write pointers. Once a record has been read, it cannot be read subsequently by another task. Intrapartition data may ultimately be transmitted upon request to the terminal or retrieved sequentially from the output data set. |
So they are taking physical space and CICS is using memory for buffering the data. |
|
| Back to top |
|
|
pkmurali
Warnings : 1
Active User
Joined: 15 Dec 2005
Posts: 271
|
|
|
|
Robert,
One of my CICS program performs WRITEQ (TDQ) which writes the data into SPOOL. What is the set up required to write the TDQ? Is there any set up required in DCT? Please suggest.
Thanks,
Murali. |
|
| Back to top |
|
|
|
|
