View previous topic :: View next topic
|
Author |
Message |
srinivas.u
New User
Joined: 07 Jun 2004 Posts: 19
|
|
|
|
hi,
what is use of TDQ AND TSQ
why usig thid\s two queues
what is difference between symbolic map and physical map |
|
Back to top |
|
|
rick
New User
Joined: 18 Jun 2004 Posts: 59 Location: Chennai
|
|
|
|
Hi,
I do have answers for symbolic and physical maps,
Symbolic map shows how the variables r defined
physical map is the load module to be displayed as screen
..::RiCk::.. |
|
Back to top |
|
|
NILESHK2302
New User
Joined: 13 Feb 2004 Posts: 14 Location: hyd
|
|
|
|
HI ,
regarding TSQ & TDQ........
its like they are temporary storages for holding up ur records that need to be proccessed.. they are not physically stored mostly thats the cocept of temporary storage.....the processing is also much faster for the queues as they are available readily in main memory when the application recollects them.........
theres a big difference between TSQ & TDQ.........in TDQ.. the record is deleted from the queue once it is read but whereas it does not happen with TSQs.............
give a reading on CICS Handbook - Kageyama..
8) |
|
Back to top |
|
|
jz1b0c
Active User
Joined: 25 Jan 2004 Posts: 160 Location: Toronto, Canada
|
|
|
|
srinivas.u wrote: |
hi,
what is use of TDQ AND TSQ
why usig thid\s two queues
what is difference between symbolic map and physical map |
TSq -> Its like a scratch pad, This will not go to permanant memory
unless you explicitly specify.
This is used if you have page up/page down logic in your CICS
screens.
Program A calling Program B which selects db2 rows, So in
program B you can write all your rows fetched to a TSQ and
come back to program A, now you can read these rows from TSQ
rather than going to Db2 every time.
If you have large amount of data to be passed between to tasks
of a transaction you can use TSQ.
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. |
|
Back to top |
|
|
|