... see below...
Don Poitras wrote:
Paul Gilmartin wrote:
On Thu, 16 Apr 2009 09:36:25 -0400, Don Poitras <[email protected]> wrote:
I guess you're saying that you need to use the binder to create Program
Objects. I think it would be difficult for an ISV to create their own.
I'm not sure why they would want to. There's certainly enough documented
info to create objects that can be directly read by the binder without
pre-linking.
--
Don Poitras - zSeries R & D - SAS Institute Inc. - SAS Campus Drive
mailto:[email protected] (919)531-5637 Fax:677-4444 Cary, NC 27513
Ahem... Guess what ISV's C compiler requires a pre-linker.
-- gil
We never sold a compiler that produced GOFF output. Doesn't mean it
can't (or hasn't) been done.
When operating in IBM (LE) compatibility mode, Dignus
compilers produce GOFF output...
Which does let you move the object to the mainframe and
go through the normal LE linking (i.e. directly use the
binder.)
But - if you wanted to do a cross-platform link, you
can't produce Program Objects... our cross-platform
linker can produce load modules (PDS) only. The cross-linker
produces a TSO TRANSMIT file which can be RECEIVE'd to
recreate the load-module.
Of course, as was suggested, you can create a combined
object deck (GOFF, XSD and/or ESD) which is easily
moved to the mainframe and then give that to the binder
to make a PDSE/uss-housed program object. So, all your
"autocall" resolution can happen on the cross-platform host,
which at least lets you know if you have an potential
link-time issues before touching the mainframe.
- Dave Rivers -
--
[email protected] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
