Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Robin Vowels]

On 2022-11-21 05:46, Farley, Peter wrote:

Thanks to all for the PL/I advice, and yes, I do know they changed the
name from 1 to I a long time ago,


The language has always been called PL/I, from IBM's first LRM
C28-6571.
(after, of course, from earlier temporary names such as NPL)


but I didn't much like that rename
starting from when they did it.  What was wrong with using a plain
Arabic numeral?

Then again I use the Roman numeral III for my full name since I am the
third generation with that name (and my son is the IV'th).  We are all
sometimes a bit schizophrenic in our thinking.

Anyway, thanks again to all for the gentle advice.  Appreciated.

Peter


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Seymour J Metz]

Is that across the board or only when it is the parameter for OPTIONS(MAIN)?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Robert Prins [robert.ah.pr...@gmail.com]
Sent: Sunday, November 20, 2022 2:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on writing PL/I to use EXEC PARM/PARMDD

No it doesn't EPLI 5.3+ now gives a warning when you use "CHAR(100) VAR".
You should nowadays code "CHAT(*) VAR"!

RTFM!

On Sun, 20 Nov 2022 at 16:59, Robin Vowels  wrote:

> On 2022-11-21 02:29, Steve Smith wrote:
> > Not necessarily.
>
> My example code (which preceded) comes straight from the manual,
> and is required when main PROCEDURE statement is as I showed,
> namely,
> M: PROC (PARAM) OPTIONS (MAIN);
> DECLARE PARAM CHARACTER(100) VARYING;
>
> >  Assuming using an LE compiler, the EXECOPTS compile
> > option controls this.
>
> It doesn't.
> Read the manual.
> What I wrote applies then EXECOPS is not used.
>
> > On Sun, Nov 20, 2022 at 2:30 AM Robin Vowels 
> > wrote:
> >
> >> The string passed to the main procedure needs to start with
> >> a slash, because everything up to and including the slash
> >> is omitted when passed.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
Robert AH Prins
robert(a)prino(d)org
The hitchhiking grandfather 
<https://secure-web.cisco.com/1X45p2mu4c3WsOWBoGukxKIZa5PXBadYC-9agrgEuv2qg59rFccNTg4koDJGZSkx_fHfmVzAGrFE7FN1GyUlcV-x2V5irVc-N-wgn-z7TiEan_5plCDVZOXbqgptbPIwZ6AUJ7PzvJ0CEXCnTzVFlVnvMBtgS6m32hpjk0CBRmXVyot7sHiteuhTzpE2lpSVmiNw9OLk5svcF20HYGZGWmstqIX1b_nNR8ydWbDh_3pqMys1JyglmphgkVxU3xz6EZ4ajrSvzFEDi3iNrujrLdBSUXlmbzHWdy4x651bb4ZHR3C_rVg6MMf-T5DBLrZjBf81LxhgdUWWAmMl-JWTzLybSyEMsV2j9qyCQMQobBXW5pylYtjmHORGqivHLx8j6roQtAQ3ENltzu834Pi639ph-Mr8jvvk13Np-0U1ni3gCj5G6hyYoSzA94Q1J1XrJ/https%3A%2F%2Fprino.neocities.org%2Findex.html>
Some REXX code for use on z/OS
<https://secure-web.cisco.com/1Df9t6H1NMlJxhohoTak6hTB4SoL1m-9bMHw_Q1cQBIYtlIOvq49o7DB7eGMcPVfq3pmIetT4NNQvlttc6F6n4pc-hF4OD_EG33csbOAk2URaskwo4bSqAHqH1gfoVhy6rRuRm0EOj5-MmAe01ocix59bJiJeR6zPceqyZF4G7QS_juaZZ_HUHDD8fuqwwvO4-spejlRo0NgqfNzQxpFiy6Y2eVaThxFfNqCvPOoRtxxbl0ou_fDy6HW3HbmY7paOg_XCsrYPJrHeACpXh8rTIR1SjgwWLxxULj352adrHcIV7qluqoxhUOzxnj6wIwG-Z9rDS7z5GkFKJtkWKQ3N8LpvTSsqCv_KH1ZylxE7B_rzRdiDT5y-UDR-NfRbGPtHsuSscqonH-w9j4N9bnxdujvYvFb0AS4SYOOCMj9bI1tBbV7pixuH2DbUfjjh5Tcr/https%3A%2F%2Fprino.neocities.org%2FzOS%2FzOS-Tools.html>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Farley, Peter]

Thanks to all for the PL/I advice, and yes, I do know they changed the name 
from 1 to I a long time ago, but I didn't much like that rename starting from 
when they did it.  What was wrong with using a plain Arabic numeral?

Then again I use the Roman numeral III for my full name since I am the third 
generation with that name (and my son is the IV'th).  We are all sometimes a 
bit schizophrenic in our thinking.

Anyway, thanks again to all for the gentle advice.  Appreciated.

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert Prins
Sent: Sunday, November 20, 2022 2:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on writing PL/I to use EXEC PARM/PARMDD

Oops fat finger, "CHAR(*) VAR"

On Sun, 20 Nov 2022 at 19:16, Robert Prins 
wrote:

> No it doesn't EPLI 5.3+ now gives a warning when you use "CHAR(100) VAR".
> You should nowadays code "CHAT(*) VAR"!
>
> RTFM!
>
> On Sun, 20 Nov 2022 at 16:59, Robin Vowels  wrote:
>
>> On 2022-11-21 02:29, Steve Smith wrote:
>> > Not necessarily.
>>
>> My example code (which preceded) comes straight from the manual,
>> and is required when main PROCEDURE statement is as I showed,
>> namely,
>> M: PROC (PARAM) OPTIONS (MAIN);
>> DECLARE PARAM CHARACTER(100) VARYING;
>>
>> >  Assuming using an LE compiler, the EXECOPTS compile
>> > option controls this.
>>
>> It doesn't.
>> Read the manual.
>> What I wrote applies then EXECOPS is not used.
>>
>> > On Sun, Nov 20, 2022 at 2:30 AM Robin Vowels 
>> > wrote:
>> >
>> >> The string passed to the main procedure needs to start with
>> >> a slash, because everything up to and including the slash
>> >> is omitted when passed.
--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Robert Prins]

Oops fat finger, "CHAR(*) VAR"

On Sun, 20 Nov 2022 at 19:16, Robert Prins 
wrote:

> No it doesn't EPLI 5.3+ now gives a warning when you use "CHAR(100) VAR".
> You should nowadays code "CHAT(*) VAR"!
>
> RTFM!
>
> On Sun, 20 Nov 2022 at 16:59, Robin Vowels  wrote:
>
>> On 2022-11-21 02:29, Steve Smith wrote:
>> > Not necessarily.
>>
>> My example code (which preceded) comes straight from the manual,
>> and is required when main PROCEDURE statement is as I showed,
>> namely,
>> M: PROC (PARAM) OPTIONS (MAIN);
>> DECLARE PARAM CHARACTER(100) VARYING;
>>
>> >  Assuming using an LE compiler, the EXECOPTS compile
>> > option controls this.
>>
>> It doesn't.
>> Read the manual.
>> What I wrote applies then EXECOPS is not used.
>>
>> > On Sun, Nov 20, 2022 at 2:30 AM Robin Vowels 
>> > wrote:
>> >
>> >> The string passed to the main procedure needs to start with
>> >> a slash, because everything up to and including the slash
>> >> is omitted when passed.
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
>
> --
> Robert AH Prins
> robert(a)prino(d)org
> The hitchhiking grandfather 
> Some REXX code for use on z/OS
> 
>


-- 
Robert AH Prins
robert(a)prino(d)org
The hitchhiking grandfather 
Some REXX code for use on z/OS


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Robert Prins]

No it doesn't EPLI 5.3+ now gives a warning when you use "CHAR(100) VAR".
You should nowadays code "CHAT(*) VAR"!

RTFM!

On Sun, 20 Nov 2022 at 16:59, Robin Vowels  wrote:

> On 2022-11-21 02:29, Steve Smith wrote:
> > Not necessarily.
>
> My example code (which preceded) comes straight from the manual,
> and is required when main PROCEDURE statement is as I showed,
> namely,
> M: PROC (PARAM) OPTIONS (MAIN);
> DECLARE PARAM CHARACTER(100) VARYING;
>
> >  Assuming using an LE compiler, the EXECOPTS compile
> > option controls this.
>
> It doesn't.
> Read the manual.
> What I wrote applies then EXECOPS is not used.
>
> > On Sun, Nov 20, 2022 at 2:30 AM Robin Vowels 
> > wrote:
> >
> >> The string passed to the main procedure needs to start with
> >> a slash, because everything up to and including the slash
> >> is omitted when passed.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Robert AH Prins
robert(a)prino(d)org
The hitchhiking grandfather 
Some REXX code for use on z/OS


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Robin Vowels]

On 2022-11-21 02:29, Steve Smith wrote:

Not necessarily.


My example code (which preceded) comes straight from the manual,
and is required when main PROCEDURE statement is as I showed,
namely,
M: PROC (PARAM) OPTIONS (MAIN);
   DECLARE PARAM CHARACTER(100) VARYING;


 Assuming using an LE compiler, the EXECOPTS compile
option controls this.


It doesn't.
Read the manual.
What I wrote applies then EXECOPS is not used.

On Sun, Nov 20, 2022 at 2:30 AM Robin Vowels  
wrote:



The string passed to the main procedure needs to start with
a slash, because everything up to and including the slash
is omitted when passed.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Steve Smith]

Not necessarily.  Assuming using an LE compiler, the EXECOPTS compile
option controls this.

sas

On Sun, Nov 20, 2022 at 2:30 AM Robin Vowels  wrote:

> The string passed to the main procedure needs to start with
> a slash, because everything up to and including the slash
> is omitted when passed.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on writing PL/I to use EXEC PARM/PARMDD

[Robin Vowels]

The string passed to the main procedure needs to start with
a slash, because everything up to and including the slash
is omitted when passed.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN