The bigger restriction is that any variable name known to ISPF has to be 8
characters or less. So you'd have to squeeze the entirety of the compound name
into 8 characters.
I kind of like that I can *prevent* ISPF from seeing variables by using illegal
names.
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Seymour J Metz
Sent: Tuesday, February 7, 2023 10:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Fw: ISPF macro/script,
ISPF compound variables would cause problems for CLIST, EXEC and EXEC2, but
that might not be a bad thing. RFE?
________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Paul Gilmartin <0000042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, February 7, 2023 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISPF macro/script
On Tue, 7 Feb 2023 04:03:59 -0600, Willy Jensen wrote:
> ...
> /* Insert template */
> s='Template line 1'
> "line_after .zl = (s)"
> s='Template line 2'
> "line_after .zl = (s)"
>
> and so on and so forth
>
For some chores similar to this it's a crying shame that ISPF shuns
compound symbols:
/* Suppose the content to insert is in stem TemplateLine. */
do L = 1 to TemplateLine.0
address ISREDIT "line_after .zl = (TemplateLine.L)"
end L
--
gil
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
