Andre, Kevin, and everyone:
When IMS/360 first came out, there was no "IMS/DB" -- there was only the batch DL/1 (IMS/DB) component... the IMS/DB/DC (data communications) came later, after IMS had transitioned from a TYPE II program to a full-fledged IBM "program product."? ?(APL\360, CICS and IMS were, IIRC, the first three IBM software products to be packaged and licensed as "program products.")
We now have INTERCOMM, that can act as an IMS/DC or CICS replacement, and has a "database interface" so that it could be made to work with DL/1, if we can get that going.? :-)? ? INTERCOMM is a part of the MVS-TK5 distribution.? ?INTERCOMM was a popular alternative to CICS in the early days.
You must run the DL/1 job in a V=R (ADDRSPC=REAL) address space, because OSAM used channel end appendages, since that old version of DL/1 was meant for MVT ... V=R gives you much closer compatibility with MVT with regard to things like use of channel programs and channel end appendages, etc.
Also, it should not be a problem to run the DL/1 in a V=R region, while INTERCOMM is running in a normal V=V region, as the INTERCOMM database interface is designed to work with separate jobs and provides an SVC to provide for inter-region communications.
Hope that helps,
Mark S. Waterbury
