Why do you want to load a KSDS in to storage instead of just doing random access on the file? Or am I misunderstanding? ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Steve Thompson <[email protected]> Sent: Thursday, October 18, 2018 1:01 PM To: [email protected] Subject: Re: COBOL 64bit
We have run into a situation, quite recently, where we would love to have COBOL 6.2 to be doing 64bit storage because we need to load a large table (actually, we want to load a data set into storage). Assume that this data set is a VSAM KSDS. And assume that we do random access of the records, and that those records contain pricing and rules for same. [Shades of PacBell circa 1992 when they had to load into a data space and use access registers to get the CO-CO billing table in memory] The only way there is to write ALC code to effect a local/same address space, data base using ATB storage and have the COBOL code get to it by calling the ALC code that handles it all. Then it was pointed out that this also needed to be done in the CICS address spaces. IBM missed the boat with ESA and COBOL back then, and now, I think they are missing the boat with COBOL NOT being able to provide large storage spaces. This is yet another example of some processing style/type that we have been doing with our mainframes and just like Client Server, and Parallel Sysplex (Ok, Geographically Diverse Sysplex), some marketing person came up with the name of what we (customers) have been doing. Is it possible to get them to catch up with their customers this time? Regards, Steve Thompson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
