In
<[EMAIL PROTECTED]>,
on 05/19/2005
   at 03:59 PM, Peter Hunkeler <[EMAIL PROTECTED]> said:

>I didn't say R1, I said standard OS parameter list.

The standard OS PLIST on z/OS is one word long and he needs two.

>But isn't it true that with the MAIN option, PL/1 expects the
>oposite:  Environment not set up and parameter list not conforming
>to PL/1 internal rules since it might be a non-PL/1 program (e.g.
>the OS) calling the MAIN routine?

Yes, except as modified by other options.


>    When NOEXECOPS is specified, the MAIN procedure can have one of
>    the following as parameters:
> 
>       A single parameter that is a VARYING CHARACTER string. 
>        The parameter passes as is, and a descriptor is set up. 
>       Other parameters (such as, more than one parameter or a
>        single 
>        parameter that is not a VARYING CHARACTER string).  The
>        parameter list passes as is, and no descriptors are set up.
>        The caller of the PL/I MAIN procedure must know what is
>        expected by the  procedure, including any required
>        descriptors. 

>The BYADDR option in Enterprise PL/1 would be a solution

Yes. I believe that he can also use the old ILC support.

>The net seems to be you can't pass more that one argument from REXX
>to  PL/1 at the OS PL/1 V2R3 level.

Why? From the text you quoted, it sounds straightforward as long as he
codes the PL/I to match what the REXX is doing. 

-- 
     Shmuel (Seymour J.) Metz, SysProg and JOAT
     Atid/2        <http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

----------------------------------------------------------------------
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

Reply via email to