Allan, yes, that's a pretty good summary of why you'd probably have to be insane to try to get IMS/360 DL/I (especially what appears to be a beta version) working on MVS.
?
Which I suppose is where I come in. Looks like a nice little project to me, especially as there's no pressure or a given target date. I can take as much time as I like.
?
As far as the OSAM DCB is concerned, I imported an MVT copy of SYS.1.MACLIB into MVS, and used it for the IMSGEN, PSBGEN, and DBDGEN. Has worked fine so far.
?
The OSAM SVC was no problem. For convenience, I copied it into SYS1.LPALIB as SVC 233, an unused Type 4 slot on TK4-, and it's working fine. It's a very small piece of code that, as far vas I can see, should run as any SVC type.
?
The matter of the OSAM channel-end appendage and the IEAAPP00 SYS1.PARMLIB member was straightforward to address. I created the IEAAPP00 member with some help from the good folk on this forum.
?
At that point, DL/I loaded up a database with new main segments. But, as I had expected, in the next test the load of dependent segements into the OSAM file failed because the OSAM DEB had been GETMAINed from the wrong subpool (from subpool zero, when in MVS it should be subpool 230). The offending module is DFSIOS10, but the source code that we have is incomplete. So my next task is to use a disassembler (as supplied to me by the ever-helpful Jay Moseley) to make changes to that module. No doubt there will be more problems to solve after that. I think this little project is going to give me something interesting to do for some time yet.
?
Regards, JJ
?
P.S. Is there is user guide available anywhere for RECV370? Darned if I can remember how to use it. Thanks.
