Dear Listerr
I am trying to create multiple entry point for single PL/1 Load module. My
source is
MSTST : PROC OPTIONS (MAIN) REORDER;
DEFAULT RANGE(*) STATIC;
PUT SKIP LIST('> MSTST ENTRY POINT');
It is possible, but I do not recommend that you attempt to construct
an OPTIONS(MAIN) procedure that has multiple entry points.
You may, however, construct a multiple entry-point subroutine easily,
and some of these entries may be functions. Consider the skeletal
multiple-stack manager
skadmin:
Dave,
The example I posted addressed only the OP's question about how
syntgactically to construct a multiple-entry PL/I procedure.
Your C counter-example is comprised of many C functions, as many as
there are entries.
PL/I differs from C in making much that C embeds implicitly in code
explicit i
On 11/22/2011 1:19 AM, Munif Sadek wrote:
Dear Listerr
I am trying to create multiple entry point for single PL/1 Load module. My
source is
MSTST : PROC OPTIONS (MAIN) REORDER;
DEFAULT RANGE(*) STATIC;
PUT SKIP LIST('> MSTST ENTRY POINT');
END;
MSTSTE: PROCEDURE;
M
John Gilmore wrote:
It is possible, but I do not recommend that you attempt to construct
an OPTIONS(MAIN) procedure that has multiple entry points.
You may, however, construct a multiple entry-point subroutine easily,
and some of these entries may be functions. Consider the skeletal
multiple-s
In <4ecb9897.6080...@trainersfriend.com>, on 11/22/2011
at 05:41 AM, Steve Comstock 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 0040
ALIAS MSTSTE
ALIAS MSTSTE1
On 11/22/2011 8:54 AM, Shmuel Metz (Seymour J.) wrote:
In<4ecb9897.6080...@trainersfriend.com>, on 11/22/2011
at 05:41 AM, Steve Comstock 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 P
[top posting]
Sorry, I forgot to mention that I pulled
the OPTIONS(MAIN) off the OP's code for
running my tests.
On 11/22/2011 10:24 AM, Steve Comstock wrote:
On 11/22/2011 8:54 AM, Shmuel Metz (Seymour J.) wrote:
In<4ecb9897.6080...@trainersfriend.com>, on 11/22/2011
at 05:41 AM, Steve Comst
I think you'll find that multiple entry points are NOT permitted for a
PL/I Main Program; only for a subroutine, where the PL/I environment
vis-a-vis save areas, error handling, etc. are already established.
Rick
--
In <4ecbdad9.8070...@trainersfriend.com>, on 11/22/2011
at 10:24 AM, Steve Comstock said:
> call mstst;
> call mstste;
You left out
call mstste1
>So either way, the binder control statements work.
See above.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; se
On 11/22/2011 2:56 PM, Shmuel Metz (Seymour J.) wrote:
In<4ecbdad9.8070...@trainersfriend.com>, on 11/22/2011
at 10:24 AM, Steve Comstock said:
call mstst;
call mstste;
You left out
call mstste1
So either way, the binder control statements work.
See above.
The OP didn't
Thanks Rick
Thats exactly what I am finding out.. It does not matter what Linkage editor
statements I use (Thanks Steve) I cannot create multiple entry points in a
PL/1 load module and make them independent runnable unit.
If I am not asking for too much, can someone please provide a working
e
On 11/23/2011 8:29 PM, Munif Sadek wrote:
Thanks Rick
That’s exactly what I am finding out.. It does not matter what Linkage editor
statements I use (Thanks Steve) I cannot create multiple entry points in a
PL/1 load module and make them independent runnable unit.
1. You're welcome.
2. I'm co
13 matches
Mail list logo
