| View previous topic :: View next topic |
| Author |
Message |
deepa12
Beginner
Joined: 05 Apr 2005
Posts: 131
Topics: 64
Location: chennai
|
 Posted: Mon Oct 16, 2006 12:24 am Post subject: to decide between -table or file |
 |
|
e.g. There is a CICS environment
I have to define a new entity Can it be a table or file
I have to consider the size,
if i dont need alternate indices & its relation to other tables in the application then can i use it as a file ? E.g. an interface file coming into the system
what can the max ksds size be in that case
What is a normally recommended SEGMENTED TABLE SIZE
What are the parameters to be considered & their ranges for using a FILE and for using a table?
_________________
_________________
deepa |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12376
Topics: 75
Location: San Jose
|
|
| Back to top |
|
|
deepa12
Beginner
Joined: 05 Apr 2005
Posts: 131
Topics: 64
Location: chennai
|
| Posted: Tue Oct 17, 2006 7:37 am Post subject: |
|
|
Thanks a lot
1.
I also want to know the advantages of VSAM over DB2 or why would we prefer to use VSAM than DB2 Tables
Can you point me to an appropriate link
What i can think of is
Pgm does not need to jump to a different address space to do I-O
VSAM is more close to OS
It is also faster as long as it is primary key based and random access
i think But may be this again depends on the volume of data
what is the Max Key size allowed for KSDS
2. i want to know when we prefer simple, segmented, partitioned table spaces i.e advantage , disadvantage, what van be their max limits for optimum performance
_________________
deepa |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
