Well, it's still early days yet. So far I've only managed to do a sequential load of a database, in which all of the segments have been stored in the ISAM (VSAM) file. What will happen if and when DL/I decides that it needs to write something into the OSAM file, who knows? All that has happened to the OSAM file up to now is that DL/I has opened it and closed it, that's all - nothing has been written to OSAM (the OSAM file that I've defined is not a VSAM file, by the way, it's a regular old MVS disk dataset). Whatever happens from here, I don't expect it to be easy - every step along the way so far has involved one or more abends, followed by debugging, followed (usually) by going back and changing the starter macros in some way.
?
My main problem is going to be finding the time to push this along further from here. If I can make progrees, I'll report it here.
?
?
?
