Paul is right that the lack of documentation is hostile
to cross-linking; that's why our cross-linker only provides
support for building "old style" load modules (in a TSO transmit file.)
And, we have mentioned this particular impediment to IBM at
almost every possible moment.
But - we do have facilities in our pre-linker that allow
SMP/E to go ahead. Function we added at the request of
customers to be able to proceed with that.... "highly hostile"
is a good way to describe it though... but, I wanted to make
sure it was clearly "doable."
- Dave Rivers -
Paul Gilmartin wrote:
On Wed, 15 Apr 2009 09:16:58 +0200, Vernooy, C.P. - SPLXM wrote:
AFAIK the format is OCO, so not documented anywhere, which also means that if
you found out the format, it might change at any moment.
It's highly unlikely that the format will change in such a way as to
invalidate archival program objects; it's more likely that it will
change in a way not supported by reverse-engineered APIs.
There are APIs for extracting information from program objects. It
is my understanding that AMBLIST uses those APIs rather than parsing
program objects itself. (Will AMBLIST process program objects
in Unix files?)
The proprietary status of Program Management information is an
impediment to ISVs supplying cross compilers. For example,
IBM's C compiler avoids any need for a prelinker by using
undocumented Program Management facilities. AFAIK, all C
compilers from ISVs require a prelinker step which, in turn,
is highly hostile to processing performed by SMP/E.
-- gil
--
riv...@dignus.com 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
