|
View previous topic :: View next topic
|
| Author |
Message |
nani556
Currently Banned
New User
Joined: 10 Jul 2010
Posts: 7
Location: banglore
|
|
|
|
Hi,
I have a question that why we will not use flat files in cics.why we use VSAM files in CICS?
Pease help me. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Is there some reason you replied to a completely unrelated topic? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
One reason is that sequential files imply "single user" - CICS is multiple users. QSAM files are a poor use of resources in a CICS environment.
VSAM files are to support multiple users. |
|
| Back to top |
|
|
Ajay Baghel
Active User
.jpg)
Joined: 25 Apr 2007
Posts: 206
Location: Bangalore
|
|
|
|
Hi Dick,
Is that because of STRNO which is allowed for VSAM in FCT ?
Thanks
Ajay |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
From the CICS Programming Guide:
| Quote: |
3.2.7 Efficient sequential data set access
CICS provides a number of different sequential processing options. Temporary storage and intrapartition transient data queues (already discussed in "Temporary storage" in topic 3.1.6.6 and in "Intrapartition transient data" in topic 3.1.6.7) are the most efficient to use, but they must be created and processed entirely within CICS.
Extrapartition transient data is the CICS way of handling standard sequential (QSAM/BSAM) data sets. It is the least efficient of the three forms of sequential support listed, because CICS has to issue operating system waits to process the data sets, as it does when handling BDAM. Moreover, extrapartition transient data sets are not recoverable. VSAM ESDSs, on the other hand, are recoverable within limitations, and processing is more efficient. The recovery limitation is that records added to an ESDS during an uncompleted UOW cannot be removed physically during the backout process, because of VSAM restrictions. They can, however, be flagged as deleted by a user exit routine. |
|
|
| Back to top |
|
|
|
|
