Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TSQ vs. Commarea

Status
Not open for further replies.

lalala21

Programmer
Apr 16, 2003
1
US
When should I consider using a TSQ rather than the Commarea?
 
A commarea will only exist to pass data between tasks and can be set so when ending a transaction to display a map to it is avaiable when the transaction starts after the map. Commareas should not normally exceed 32K.

When a TSQ is created it remains in existance until it is deleted or the cics system is shut. The data is avaiable to any trnsaction that knows its name. S it could be used to hold global parameters what are loaded at cics start up to reduce file access etc. if you are using a TSQ to hold information relatin to a particular task or termaial you must have a naming convenetion to support that. You only have a finite abount of TSQ space to so you delete unwanted TSQ's.

in earlier versions of CICS TSQ were not supported on a sysplex for recovery and so may not be suitable, but this can be managed in older versions of cics depending on the nature of the system. New versions of CICS (I think starting TS1.3) have a system for dealing with this.

It not a black and white answer and will depend on what data you are storing, why, how much and for how long. If you can post this information I maybe ale to help more

bye

FFF
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top