| It should be easy to find the corresponding Rdb numbers. What are
these numbers, though? the "maximums" for the line items? For example,
assuming they are the maxs: (I know they are not "typicals")
Number of bytes in a a record 32,766 bytes
Rdb's SPD says 16K, as I recall, though the real max is 65K
Number of fields in a record format 8,000 fields
We say 2000.
Number of key fields in a file 120 fields
We don't have a practical limit
Size of key for physical and logical files 120 characters
254
Size of key for ORDER BY (SQL/400 and OPNQRYF) 256 characters
no practical limit, the real limit is around 32 or 64K
Number of records contained in a file 16,777,215 records*
no practical limit. 4 billion pages divided by the record length
(pages can vary though)
Number of bytes in a file 2,147,483,648 bytes
now that's a good one. We never thought about it and would have said,
"Duh, gee there's no limit there.)
Number of bytes in an access path 1,073,741,824 bytes
I think an access path is just an index. We wouldn't say those were
limited.
Number of keyed logical file built over a phys f 3,686 files
N/A. We're not hierarchical, we're relational. I know IBM calls
this relational. people will believe anyone who wears monogrammed
shirts.
Number of phys file members in a logical file mem 32 members
Same as above
Number of members that can be joined 32 members
Can join 32 relations in a view, if you really want to.
Size of a character or DBCS field 32,766 characters
I think the 16K vs 65K wishy washy answer gets repeated here.
Size of a zoned decimal or packed decimal field 31 digits
Do not currently have zoned or packed decimal.
ed
|
| Thanks, Ed
The information is very useful (and competitive!), but...
"It should be easy to find the corresponding Rdb numbers"
and
"now that's a good one. We never thought about it and would have said,
"Duh, gee there's no limit there.)"
don't quite correlate :-).
Peter
|
| On a related topic:
I'm competing against IBM on an opportunity to convert (downsize) a
customer from a 4381. The customer has seen several third-party
financials packages that run against Rdb and likes them.
She was already to go to her management and recommend our VAX/VMS, Rdb
solution (today is decision day), when the people in blue paid her a
visit. They told her that they/she could port her COBOL applications
from the 4381 to their proposed AS/400 "without changing any of the I/O
statements." (!)
I'm ready to call her and probe very gently along the lines:
1. the 4381 is a 16-bit architecture, the AS/400 32-bit
2. the AS/400's native application development language is RPG III,
yet the application to be ported is in COBOL
3. the AS/400 has a built-in relational database and the existing
application uses VSAM
How are they going to emulate VSAM with a relational database? Does
she think she's going to get the optimum, or even marginally efficient
performance with no conversion?
But I want to put as positive a spin on this as possible. How else
might I do that?
Thanks,
Bruce
|
| Bruce,
I'd be _very_ surprised if IBM could manage the .4. If their
application has terminals attached, then I'd guess it's using CICS,
which doesn't run on AS400... Thus you haave to change all your
screen IO for start ! As for ths database stuff, the AS400 file
system can look like flat files or like a relational database, so
the file IO stuff may be true ! But I doubt it provides the richness
of facilities that the VSAM does
Most of this appears to be FUD spreading, and making you're allies
life very awkward. For more info. try the KACIE::IBM notes file
(DIR/TITLE=400) yields a wealth of info. on the AS400 (try note
420m for start)
Let us know how you fare
Steve J
|
| Phew!
She recommended us to her management! Her manager (non-computer guy)
is out of town until Monday. I'm sure IBM has the first available
piece of time on his schedule to bend his ear.
We're not going to rest on our laurels, after all we've only been
recommended. The thing is that she has bet her integrity on her
recommendation (we surmise) so she should be very willing to work with
us and "open her kimono," as a former district manager, here, likes to
say.
She will probably tell us what she sees as our strengths and weaknesses
and for IBM, as well. Both the third-party financials packages she's
looking at for the VAX platform are promised to be Rdb-compatible
"within 12 months." We have proposed Rdb and CDD+ as part of the base
platform, and I think she perceived them as strengths (and why not!?).
Stay tuned...
-b
|