Am 30.03.2012 14:45, schrieb Steve Comstock:
My notes seem to indicate that using LINK from Assembler to
a PL/I main creates a nested enclave, which I guess is what
you are seeing. I don't see anyway to call a PL/I main without
the main creating an enclave.
I also see this note:
"PL/I fetchable main cannot be dynamically called by COBOL, C,
C++, FORTRAN, nor LE-conforming Assembler"
do you recall where this note comes from? If this is really a restriction
confirmed by IBM books etc., I simply would accept it and don't try it
any more.
Maybe we find another solution to our problem; there is no absolute need
to call the test object within another enclave, if the test object is a
PL/1 main.
It's the way it works at the moment, but it could be changed; at least
I think so.
Perhaps CEEPIPI would work for you? (Apologies if this has
already been suggested.)
See above. The problem is that the existing enclave is damaged,
when we try to call the PL/1 main. It doesn't matter how the existing
enclave
has been constructed. So we didn't consider CEEPIPI so far. If the
nesting of the enclaves (with PL/1 mains) is indeed a problem, I would
prefer to terminate the first enclave before calling the PL/1 main. My
question
to you and to the list was, if there are experiences with this, that is,
if the
calling of PL/1 mains in a nested enclave is indeed a problem, or if it
could
be done, if the PL/1 main is called via LINK, for example. Anyway, I
will try it -
but not this week, because it's Friday afternoon now. Have a nice
weekend ...
and thank you so far.
Kind regards
Bernd
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
