On 11/22/2011 8:54 AM, Shmuel Metz (Seymour J.) wrote:
In<[email protected]>, on 11/22/2011
at 05:41 AM, Steve Comstock<[email protected]> said:
Hmm. Try changing your alias to:
ALIAS MSTSTE(MSTST1)
That won't do what he asked for. He needs an ALIAS statement for each
INCLUDE PLIOBJ
SETSSI 00000040
ALIAS MSTSTE
ALIAS MSTSTE1
NAME MSTST(R)
There's also the issue that he only has OPTIONS(MAIN) on one of the
three entry points. I don't believe the any current PL/I supports
multiple main entry points.
Well, you're totally right about the OPTIONS(MAIN) point. So I
set up a calling routine:
pmaina: proc options(main);
dcl mstst entry external;
dcl mstste entry external;
call mstst;
call mstste;
end pmaina;
Then I compiled the OP's original program and ran two tests:
1. with LKED.SYSIN consisting of:
ALIAS MSTSTE
ALIAS MSTSTE1
NAME MSTST(R)
result of running pmaina:
====> MSTST ENTRY POINT
====> MSTST1 ENTRY POINT
2. with LKED.SYSIN consisting of:
ALIAS MSTSTE(MSTST1)
NAME MSTST(R)
result of running pmaina:
====> MSTST ENTRY POINT
====> MSTST1 ENTRY POINT
So either way, the binder control statements work.
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-355-2752
http://www.trainersfriend.com
* To get a good Return on your Investment, first make an investment!
+ Training your people is an excellent investment
* Try our tool for calculating your Return On Investment
for training dollars at
http://www.trainersfriend.com/ROI/roi.html
----------------------------------------------------------------------
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
