|
View previous topic :: View next topic
|
| Author |
Message |
Vijay Subramaniyan
New User
Joined: 06 Jul 2011
Posts: 14
Location: india
|
|
|
|
Hi ,
My client has 65 million accounts to be processed. The accounts count may increase while the batch runs daily . My requirement is such that I need to display the reporting history for the last two reporting periods on a CICS screen,for a particular account. Hence I need to save the details for every account that comes in batch .
Which one is preferrabe in this case ? VSAM or a DB2 table ? Is there anything that lies as a problem of using a Table for this (CPU consumption, or some overheads ) ? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
since ...
we do not belong to Your client/organization,
we do not know anything about the client application design
we do not know anything about Your client/organization standards
we do not ....
we do not ....
we do not ....
and since, from Your profile ...
spending time giving advice un such a problem at the end will result in a waste of time for everybody !
and furthermore we will be doing at no charge
the work for which Your organization is getting paid for
ask Your colleagues!  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Which one is preferrabe in this case ? VSAM or a DB2 table ? Is there anything that lies as a problem of using a Table for this (CPU consumption, or some overheads ) ? |
As this appears to be something "long-term" you might consider implementing both and running some performance tests that reflect the "real work" to be done.
As Enrico mentioned, we know basically nothing about the client environment, so specific suggestions will be less likely. |
|
| Back to top |
|
|
|
|
