Shmuel Metz (Seymour J.) wrote:
In 500f6f1d@bcs.org.uk, on 07/25/2012
at 04:59 AM, CM Poncelet ponce...@bcs.org.uk said:
Yes I know that. ADDRESS ISREDIT, on its own, is sufficient to
cause all commands that follow it to be interpreted as ISREDIT
ones (without quotes
The
In 9251321842665626.wa.paulgboulderaim@listserv.ua.edu, on
07/24/2012
at 10:39 AM, Paul Gilmartin paulgboul...@aim.com said:
And remembering that Rexx considers lower case characters special.
Not quite, but the default value of an uninitialized variable is the
upper case name.
Do these
On Tue, 24 Jul 2012 08:39:35 -0400, Shmuel Metz (Seymour J.) wrote:
Address ISREDIT does not in general require quotes either. The quotes
are only needed because you want constants with special characters.
And remembering that Rexx considers lower case characters special.
Had you wanted, e.g.,
Shmuel Metz (Seymour J.) wrote:
In 500e6b77.2090...@bcs.org.uk, on 07/24/2012
at 10:31 AM, CM Poncelet ponce...@bcs.org.uk said:
OK. But I do not *have* to code ISPEXEC CONTROL ERRORS RETURN.
The rest is mostly ISREDIT ... apart from pure REXX instructions
which do not need quotes
Paul Gilmartin wrote:
On Fri, 20 Jul 2012 07:31:09 +0100, CM Poncelet wrote:
I did explain that ISREDIT follows Clist rules when processing 's, in
my earlier posting, methinks grin:
...
TSO Clist edit macros have been around long before REXX appeared (around
1989-90) and ISREDIT was
On Sun, 22 Jul 2012 13:50:25 +0100, CM Poncelet wrote:
Same
question as earlier: Do identical command strings issued to ISREDIT
from CLIST and CALL have identical effect?
I would expect the ISREDIT effects of REXX/Clist v. ISPLINK calls to be
identical, because the command strings in the call
On Fri, 20 Jul 2012 15:55:28 -0700, John Mattson wrote:
Shmuel ! Its amazing how much you contribute without access to a z
system. Hope my memory and research is that good when we go off zOS
(we're being SAPonified).
So, are you on a slippery slope?
-- gil
I did explain that ISREDIT follows Clist rules when processing 's, in
my earlier posting, methinks grin:
Original Message
Subject:Re: REXX ISPF edit FIND failing
Date: Thu, 19 Jul 2012 06:46:37 +0100
From: CM Poncelet ponce...@bcs.org.uk
Organization: L! Logic
In
ofc799207c.54ac2d90-on88257a40.004f10aa-88257a40.004f4...@ea.epson.com,
on 07/19/2012
at 07:25 AM, John Mattson john_matt...@ea.epson.com said:
Shmuel ! A previous reply also suggested SCAN OFF. I tried it,
Did you try it with your original FIND, or with the FIND that used
picture?
Please
to the single .
Thanks for you, and everyone's help
From: Shmuel Metz (Seymour J.) shmuel+...@patriot.net
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/20/2012 10:25 AM
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
In
9b26bc6a6df52d4483dd73b1fe7b4b0658b83d6...@uspho-mxvs07.amer.thermo.com,
on 07/18/2012
at 10:37 AM, Hardee, Chuck chuck.har...@thermofisher.com said:
Uh, I don't think so.
You're thinking CLIST not REXX.
I doubt it. What he wrote was 'The problem is that ISPF/ISREDIT
evaluates/substitutes
On Thu, 19 Jul 2012 10:19:28 +0100, Rupert Reynolds wrote:
There is no need to send edit commands via ISPEXEC anyway:-)
What was the rationale for making the initial host command environment
when an edit macro is entered TSO rather than the obvious ISREDIT?
Was it merely that the ISPF
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
In
ofc169f9df.8de870ec-on88257a3f.006f4f36-88257a3f.00705...@ea.epson.com,
on 07/18/2012
at 01:26 PM, John Mattson john_matt...@ea.epson.com said:
Thanks to all, I now have
should work as a REXX. I'll let IBM sort it out.
From: Shmuel Metz (Seymour J.) shmuel+...@patriot.net
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/19/2012 07:17 AM
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Systems and Connectivity Engineering
518-436-6433
From: John Mattson john_matt...@ea.epson.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/19/2012 10:49
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Shmuel ! I sent
DD DISP=SHR,DSN=PDQ.ALC.UNVLIB(MY)
Thomas Ambros
Operating Systems and Connectivity Engineering
518-436-6433
From: John Mattson john_matt...@ea.epson.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/19/2012 10:49
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM
On Thu, 19 Jul 2012 09:12:54 -0700, John Mattson wrote:
And the grand prize goes to Tom Ambros
Yes, use DOUBLE AMPERSANDS in REXX and the FINDs work properly.
So simple when we finally see it. Many thanks to everyone.
So is the behavior of EDIT different when identical command
strings are
applies to REXX EXECs.
Thomas Ambros
Operating Systems and Connectivity Engineering
518-436-6433
From: Paul Gilmartin paulgboul...@aim.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/19/2012 12:35
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List
: Skip Robinson jo.skip.robin...@sce.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 02:26 PM
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
I have found that the ISPF development folks are pretty responsive
On Wed, 18 Jul 2012 11:58:48 -0500, Mark Zelden m...@mzelden.com wrote:
Add FIRST to the end of the find or a TOP command in-between the find.
Never mind... I didn't see the ALL in the find command. I usually put that
at the end and missed it.
--
Mark Zelden - Zelden Consulting Services -
ALL P'DISP=SHR,DSN=MSYS$UCMD$REMOTEPDQR$(SYSTEM$'
L ISREDIT F ALL P'DISP=SHR,DSN=MSYS$UCMD$REMOTEPDQR$(SYSTEM$'
+++ RC(4) +++
From: John Mattson/Epson
To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 01:26 PM
Subject:Re: REXX ISPF edit
Mattson john_matt...@ea.epson.com
Sent: Jul 18, 2012 1:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX ISPF edit FIND failing
While I am at it...
WHY the Ampersand SYSTEM WORKS in the find,
but if you use PDQR rather than $PDQR it fails is just madness.
7 *-* ISREDIT F ALL P'DISP=SHR,DSN
Thanks to everyone! I have kept plugging at this and tried all your
suggestions.
Here is what I see so far.
1) There is no reason syntactically that this should not work
ISREDIT F ALL 'DISP=SHR,DSN=MSYS.UCMD.REMOTEPDQR.(SYSTEM)'
2) For some strange reality THIS works
ISREDIT F
...@mindspring.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 02:18 PM
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Thanks to everyone! I have kept plugging at this and tried all your
suggestions.
Here is what I see so
...@thermofisher.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Wednesday, July 18, 2012 5:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX ISPF edit FIND failing
Thanks to everyone! I have kept plugging
25 matches
Mail list logo