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 <IBM-MAIN@LISTSERV.UA.EDU> 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 <robert.ah.pr...@gmail.com> 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 <robi...@dodo.com.au> 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 <robi...@dodo.com.au> >> > 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
