how will the PL/1 interface to the C package be presented to the users? As
source code, or precompiled?
I've had no time so far to look at the distribution that Z.A. presents on
his website, if it is source code that still has to be compiled on z/OS or any
other format. If it is C source code - and the COBOL interface maybe COBOL
source code - then you should also distribute your PL/1 solution as source code.
But in this case, you should IMO not require a current release. That's why I
would suggest a C glue function which builds a PL/1 compatible interface that
can be handled by very old PL/1 compilers, too.
When you do this, you don't even need to distribute PL/1 source code, nor
executables. Only some C glue code, and a description, how to use this modified
interface to the original C package from some "vintage" PL/1.
Am 26.02.2014 18:52, schrieb D.J.:
> Hi, Bernd.
> I'm glad this all makes perfect sense to you....:-) and it does to me
> now, as well after you have explained it.....many thanks.
> Yes the options are indeed implemented in the PL/I caller as bit strings
> that are AND-ed together.
> I'm planning on writing the glue code using the new z/OS PL/I
> compiler....it will take as parameters the needed stings and integers
> using a parameter list that the old PL/I compiler on z/VM can create
> (that is to say all parameters are passed in via BYADDR) and then call
> the C routines, passing the parameters to it via BYVALUE/BYADDR as needed.
> Thanks again.