The issue is when someone has a compound or long ISPF script name and someone else wants to use CLIST, EXEC or EXEC2 for another script in the same application. I see discouraging use of those older languages for new scripts as a good thing, but others might not se it that way.
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Tuesday, February 7, 2023 12:31 PM To: [email protected] Subject: Re: ISPF macro/script, On Tue, 7 Feb 2023 16:48:29 +0000, Seymour J Metz wrote: >ISPF compound variables would cause problems for CLIST, EXEC and EXEC2, but >that might not be a bad thing. RFE? > I would not presume to suggest that the syntax of ISPF variables be extended; rather the relatively modest extension to script variable names. The entire string between '(' and ')' should be passed ASIS to (e.g.) IRXEXCOM and any errors reported. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
