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

2022-11-20 Thread 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

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

2022-11-20 Thread Seymour J Metz
] 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 20

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

2022-11-20 Thread Farley, Peter
nt: 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

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

2022-11-20 Thread 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

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

2022-11-20 Thread 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 m

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

2022-11-20 Thread 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 compil

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

2022-11-20 Thread 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.

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

2022-11-19 Thread 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.