Barry Lichtenstein wrote:
The binder will simply discard the "private code" (unnamed) CSECT (section), if
it has text.
It never gets incorporated into the module being bound, so it should have no
effect on it.
Binder has behaved like this since near the beginning (early 90's, around when
PM3 format was introduced).
Thanks Barry!
My casual tests did show that the binder does not ignore the AMODE
of "private code" sections when they have text:
DC 'Some text'
AMODE 31
RMODE ANY
FOO CSECT
FOO AMODE 31
FOO RMODE ANY
BR 14
END FOO
will generate an AMODE 31/RMODE ANY load module, but
DC 'Some text'
AMODE 24
FOO CSECT
FOO AMODE 31
FOO RMODE ANY
BR 14
END FOO
seems to an AMODE 24/RMODE 24 load module... but,
AMODE 24
FOO CSECT
FOO AMODE 31
FOO RMODE ANY
BR 14
END FOO
seems to generate an AMODE 31/RMODE ANY load module.
- Dave R. -
--
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...@listserv.ua.edu with the message: INFO IBM-MAIN
