In <5011b406.8020...@bcs.org.uk>, on 07/26/2012
at 10:17 PM, CM Poncelet said:
>I did not say they had.
You implied it.
>I said "it is just as easy, and quicker, to put strings in quotes."
In the context of whether or not to use an ADDRESS statement.
>Yes, I know that. But "ISREDIT ..." i
Shmuel Metz (Seymour J.) wrote:
In <500f6f1d@bcs.org.uk>, on 07/25/2012
at 04:59 AM, CM Poncelet 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 need, or lack of need,
In <500f6f1d@bcs.org.uk>, on 07/25/2012
at 04:59 AM, CM Poncelet 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 need, or lack of need, for quotes has nothing to do with wheth
In <9251321842665626.wa.paulgboulderaim@listserv.ua.edu>, on
07/24/2012
at 10:39 AM, Paul Gilmartin 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 have different s
Shmuel Metz (Seymour J.) wrote:
In <500e6b77.2090...@bcs.org.uk>, on 07/24/2012
at 10:31 AM, CM Poncelet 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 around them.
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
In <500e6b77.2090...@bcs.org.uk>, on 07/24/2012
at 10:31 AM, CM Poncelet 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 around them.
Address ISREDIT does not in general req
Shmuel Metz (Seymour J.) wrote:
In <500bf711.2040...@bcs.org.uk>, on 07/22/2012
at 01:50 PM, CM Poncelet said:
Unless I misunderstand what you mean by 'CALL-like', REXX is
calling ISREDIT
No, REXX is calling ISPEXEC, which in turn is calling ISREDIT. To call
ISREDIT directly, chan
In <500bf711.2040...@bcs.org.uk>, on 07/22/2012
at 01:50 PM, CM Poncelet said:
>Unless I misunderstand what you mean by 'CALL-like', REXX is
>calling ISREDIT
No, REXX is calling ISPEXEC, which in turn is calling ISREDIT. To call
ISREDIT directly, change the operand of the ADDRESS statement a
ungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> För CM Poncelet
> Skickat: den 22 juli 2012 14:50
> Till: IBM-MAIN@LISTSERV.UA.EDU
> Ämne: Re: REXX ISPF edit FIND failing
>
> Paul Gilmartin wrote:
>
> >On Fri, 20 Jul 2012 0
Yes, you are right - I overlooked that. Identical commands could produce
different results if ISPLINK sent them to Clist instead of REXX, or vice
versa. Thanks for noticing.
Paul Gilmartin wrote:
On Sun, 22 Jul 2012 13:50:25 +0100, CM Poncelet wrote:
Same
question as earlier: Do identical
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 t
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 :
...
TSO Clist edit macros have been around long before REXX appeared (around
1989-90) and ISREDIT was meant to
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
--
inding everything up to the single &.
Thanks for you, and everyone's help
From: "Shmuel Metz (Seymour J.)"
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 Li
In
,
on 07/19/2012
at 07:47 AM, John Mattson said:
>Shmuel ! I sent my original source, and it was REXX.
It's ISPF that interprets the ampersamds, not REXX. Try turning on the
ISPF trace and see if anything pops out.
>Having a few spare moments, I quickly converted the REXX to CLIST
>and a
In
,
on 07/19/2012
at 07:25 AM, John Mattson 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 look at the example I sent before and try it yourself.
Alas, I don't have access to a z s
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 :
>...
>TSO Clist edit macros have been around long before REXX appeared (around
>1989-90) and ISREDIT was meant to be called in Clist, n
I did explain that ISREDIT follows Clist rules when processing &'s, in
my earlier posting, methinks :
Original Message
Subject: Re: REXX ISPF edit FIND failing
Date: Thu, 19 Jul 2012 06:46:37 +0100
From: CM Poncelet
Organization: L! Logic Integration
To
l of all this is: Do not assume ISREDIT commands will work
the same in REXX as in clists, or ISPF. I find this very annoying, how
about your folks?
From: Skip Robinson
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 02:26 PM
Subject:Re: REXX ISPF edit FIND failing
Sent by:
fore variable names to avoid substitution of variable
names also applies to REXX EXECs.
Thomas Ambros
Operating Systems and Connectivity Engineering
518-436-6433
From: Paul Gilmartin
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/19/2012 12:35
Subject:Re: REXX ISPF edit FIND failing
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
ALL 'DISP=SHR,DSN=&&PDQ.ALC.UNVLIB(&&UCMIN)' "
>L> "ISREDIT F ALL 'DISP=SHR,DSN=&&PDQ.ALC.UNVLIB(&&UCMIN)'"
14 *-* "ISREDIT F ALL 'DISP=SHR,DSN=&&PDQ.ALC.UNVLIB(&&MY)'
SN=&&PDQ.ALC.UNVLIB(&&UCMIN)' "
>L> "ISREDIT F ALL 'DISP=SHR,DSN=&&PDQ.ALC.UNVLIB(&&UCMIN)'"
14 *-* "ISREDIT F ALL 'DISP=SHR,DSN=&&PDQ.ALC.UNVLIB(&&MY)' "
&g
mands should work as a REXX. I'll let IBM sort it out.
From: "Shmuel Metz (Seymour J.)"
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
In
<9b26bc6a6df52d44
M
Subject: Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List
In
,
on 07/18/2012
at 01:26 PM, John Mattson said:
>Thanks to all, I now have something that works, sort of, but there
>is really something wrong with ISPF here.
Not from what you
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 develop
In
<9b26bc6a6df52d4483dd73b1fe7b4b0658b83d6...@uspho-mxvs07.amer.thermo.com>,
on 07/18/2012
at 10:37 AM, "Hardee, Chuck" 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 any ISPF variable, which
In
,
on 07/18/2012
at 01:26 PM, John Mattson said:
>Thanks to all, I now have something that works, sort of, but there
>is really something wrong with ISPF here.
Not from what you have written. Try what Tom suggested[1] and add SCAN
OFF to your macro.
[1] Don't bother with the SCAN ON unles
N=MSYS$UCMD$REMOTE&PDQR$(&SYSTEM$' "
>> >L> "ISREDIT F ALL P'DISP=SHR,DSN=MSYS$UCMD$REMOTE&PDQR$(&SYSTEM$' "
>>
>> +++ RC(4) +++
>>
>>
>>
>> From: John Mattson/Epson
>> To: IBM Mainframe D
y don't they work the same way in ISREDIT? Beats me, that's for
sure.
From: Lizette Koehler
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
Thanks to everyone! I ha
I have opened Service Request 19768 227 000 on this. I will keep you
updated when IBM comes up with something on it.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu wit
k.har...@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
Lizette Koehler
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
>
>Thanks to everyone! I have kept plugging at this and tried all your
>suggestions.
>Here is what I see so
From: John Mattson
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 01:34 PM
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List
While I am at it...
WHY the Ampersand "&SYSTEM" WORKS in the find,
but if you use &PDQR rather th
e.g. 'A+7'
FEX A[=]# Finds 'A' followed by an equal sign followed by any number;
e.g. 'A=7'.
Dave Salt
SimpList(tm) - try it; you'll get it!
http://www.mackinney.com/products/program-development/simplist.html
> Date: Wed, 18 Jul 2012 1
>
>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.REMOTE&PDQR.(&SYSTEM)'"
>
>2) For some strange reality THIS works
>"
Lizette
-Original Message-
>From: John Mattson
>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 rat
27;DISP=SHR,DSN=MSYS$UCMD$REMOTE$PDQR$(&SYSTEM$' "
8 *-* "ISREDIT F ALL P'DISP=SHR,DSN=MSYS$UCMD$REMOTE&PDQR$(&SYSTEM$' "
>L> "ISREDIT F ALL P'DISP=SHR,DSN=MSYS$UCMD$REMOTE&PDQR$(&SYSTEM$' "
+++ RC(4) +++
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.REMOTE&PDQR.(&SYSTEM)'"
2) For some strange reality THIS works
"ISREDIT F
18, 2012 11:31 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: REXX ISPF edit FIND failing
>
>You need to be careful with your picture string components.
>It didn't work with your suggested string below and in looking at the rules
>for pictures, the "." (period) repr
s
Operating Systems and Connectivity Engineering
518-436-6433
From: "Hardee, Chuck"
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 14:35
Subject:Re: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List
You need to be careful with your picture st
fic
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
chuck.har...@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 1:49 PM
To: IBM-MAIN@L
ot;
The equal signs equate to any char.
The $ equate to any special char (& . , etc...)
This might make it work better
Lizette
-Original Message-
>From: John Mattson
>Sent: Jul 18, 2012 9:47 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: REXX ISPF edit FIND failing
>
>I
JCL. I change a string containing that variable during DR adjustments of
the VTAM proc.
Thomas Ambros
Operating Systems and Connectivity Engineering
518-436-6433
From: Thomas Berg
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 13:27
Subject: SV: REXX ISPF edit FIND
ustments of
the VTAM proc.
Thomas Ambros
Operating Systems and Connectivity Engineering
518-436-6433
From: Thomas Berg
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 07/18/2012 13:27
Subject: SV: REXX ISPF edit FIND failing
Sent by:IBM Mainframe Discussion List
The problem is t
You will see in the trace that &PDQR was not substituted.
If this was a CLIST, I would agree with you, but this is REXX and REXX doesn't
use "&" in it's variable names.
Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Se
--
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Hardee, Chuck
Sent: Wednesday, July 18, 2012 1:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX ISPF edit FIND failing
I know this doesn't help, but I've hit this problem before but can't rem
Regards,
Thomas Berg
___
Thomas Berg Specialist AM/SM&S SWEDBANK AB (publ)
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> För John Mattson
> Skickat: de
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mark Zelden
Sent: Wednesday, July 18, 2012 1:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX ISPF edit FIND failing
On Wed, 18 Jul 2012 11:58:48 -0500, Mark Zelden wrote:
>
>Add "FIRST" to th
On Wed, 18 Jul 2012 11:58:48 -0500, Mark Zelden 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 - z/OS, OS
On Wed, 18 Jul 2012 09:47:35 -0700, John Mattson
wrote:
>I have a little dataset which contains
>//REMOTE DD DISP=SHR,DSN=MSYS.UCMD.REMOTE&PDQR.(&SYSTEM)
>//REMOTE DD DISP=SHR,DSN=MSYS.UCMD.REMOTE&PDQR.(SYSTEM)
>//REMOTE DD DISP=SHR,DSN=MSYS.UCMD.REMOTE&PDQR(SYSTEM)
>//SYSINDD DISP
I have a little dataset which contains
//REMOTE DD DISP=SHR,DSN=MSYS.UCMD.REMOTE&PDQR.(&SYSTEM)
//REMOTE DD DISP=SHR,DSN=MSYS.UCMD.REMOTE&PDQR.(SYSTEM)
//REMOTE DD DISP=SHR,DSN=MSYS.UCMD.REMOTE&PDQR(SYSTEM)
//SYSINDD DISP=SHR,DSN=&PDQ.ALC.UNVLIB(&UCMIN)
X/MYSCRIPT DD DISP=SHR,DS
53 matches
Mail list logo
