Comments (2)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 localhost commented Permalink

Depends on what you mean. Already in IMS (by which I mean pre IMS 10) are the following 64-bit items:<div>&nbsp;</div> * Allocation of OSAM database buffers above the 2Gb bar* Allocation of IMS log buffers above 2Gb bar (provided the OLDS blocksize is a multiple of 4k)* IRLM 2.2, which uses memory above the 2Gb bar<div>&nbsp;</div> In IMS 10 itself there is exploitation of 64-bit addressing by the RDDS extraction utility (presumably this is 64-bit because it is new).<div>&nbsp;</div> The biggest thing remaining is the ability to allocate VSAM buffers above the 2Gb bar, but that's out of IMS's hands. Customers with large databases who are serious about performance are probably already using OSAM.

2 localhost commented Permalink

Thanks Andrew.<div>&nbsp;</div> The original question was a touch ambiguous... Did you mean 64-Bit real or imaginary? :-) Um, virtual?<div>&nbsp;</div> As an example of the former Andrew was right to point out OSAM database buffers tolerated being placed above the 2GB REAL bar. This is similar to what other products had to do. So DB2 also had to supply PTFs to allow THEIR buffer pools to be backed by Real above the 2GB bar. (And for THEM placing the buffer pools in VIRTUAL above the 2GB bar had to await Version 8.)