Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
what is tsq?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS
View previous topic :: :: View next topic  
Author Message
johnsingh

New User


Joined: 11 May 2005
Posts: 22

PostPosted: Sat Aug 27, 2005 12:11 pm    Post subject: what is tsq?
Reply with quote

hi,

what is tsq? please, explain it.

thanking avanced.
Back to top
View user's profile Send private message

priyesh.agrawal

Senior Member


Joined: 28 Mar 2005
Posts: 1452
Location: Chicago, IL

PostPosted: Sat Aug 27, 2005 12:27 pm    Post subject: Re: what is tsq?
Reply with quote

Hi John,

TSQ stands for Temporary Storage Queue.

TSQ are used to pass data between different tasks of a transition.
This is referred by 8 characters ID. And do not occupy main memory.
TSQ is not read destrcutive, measn data is there after read also.
Even after completing the transaction TSQ are not deleted.

This is just an introduction over TSQ. You should browse thru the forum to know more about TSQ.

http://ibmmainframes.com/search.php?search_keywords=TSQ

Regards,

Priyesh.
Back to top
View user's profile Send private message
prasanth_thavva

New User


Joined: 28 Jul 2005
Posts: 86
Location: Chennai

PostPosted: Tue Aug 30, 2005 9:42 am    Post subject: what is tsq? please, explain it.
Reply with quote

hi priyesh.agrawal,

TSQ-- i am extending the topic ...
Temporary Storage Queue is used for Message Switching..
Quote:
We can store it on VSAM file by defining it in TST Temporary Storage Table.. Instead of Vsam file operation most of the CICS applications are using TSQ's only...It is 8 Byte filed which it contais Terminal Id and TransactionID.. each of 4 Bytes... from EIBTERM>>EIBTRANS we can build this TSQID.. Dont need to define it its automatically created when ever you use in ur applications
...

Bye
All d best
Back to top
View user's profile Send private message
sendil

New User


Joined: 30 Jun 2005
Posts: 27

PostPosted: Tue Aug 30, 2005 3:33 pm    Post subject:
Reply with quote

TSQ stands for TEMPORARY STORAGE QUEUE .It is a queue of stored records . We dont have any control table entry for this queue. In real time application queue name may be (terminal id + task-id). TSQ can beaccessed by any transaction with in the same region.
The following commands are available in TSQ,

WRITEQ TS,
READQ TS,
DELETEQ TS



Thanks
sendil
Back to top
View user's profile Send private message
johnsingh

New User


Joined: 11 May 2005
Posts: 22

PostPosted: Mon Sep 05, 2005 4:08 pm    Post subject:
Reply with quote

hi all,

Thanks for yours valuable comment.
Back to top
View user's profile Send private message
small_world

New User


Joined: 22 Jul 2005
Posts: 24
Location: pune

PostPosted: Tue Sep 06, 2005 4:40 pm    Post subject: tsq
Reply with quote

Hello aggarwal,
tsq-transaction queue is used for transfer of data.MQ message queueing is an e.g. of tsq.In MQ we normally pass message through a channel.There are mainly two queue managers: sending queue and receiving queue. on the sending side we put data and also close queue and on the receiving side the main operation done is get message queue. channels can be of any number .some of the messages may be encrypted, so no same channel can be used for sending all the different messages. There are different types of queues (just like a dataset).
Local queue-real queue (size can be set) remote queue has pointer to local queue. Remote means logical pointers to different location.
For transmitting mess from remote queue to local queue, we should know the: transmission queue name and local queue name. .if the program does not get the mess they will be put in dead channel. You should get back to check for local mess.

Then there is the remote queue, transmission queue, Initiation queue, and dynamic queue, alias queue.
Then there is the cluster queue and distributed queue. For cluster there is no need to build separate channel for each and every queue.

Message queue is not synchronous. Our application programs make it synchronous.
If one queuing manager dies the mess is lost as far as distributed processing is concerned. there is no problem for clustered processing.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:


Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us