Gentle Listers;
I am trying to write a Rexx routine that takes in 3 arguments. First is DSN,
second is Member name, third is a string of text. The string of text is the
concatenation of lines delimited by a ";". (ex. "line1;line2;line3").
This code fails:
Write_Member:
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of George Shedlock
Sent: Monday, August 26, 2013 2:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Rexx Execio to PDS
Gentle Listers;
I am trying to write a Rexx routine that takes in 3 arguments. First is DSN
> 04A data set opened for output used all space available to or on the
> current volume, and no more volumes were available.
>Change the JCL to specify more volumes.
Won't work for a PDS(E).
They can't span volumes.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
ERV.UA.EDU
>Subject: Rexx Execio to PDS
>
>Gentle Listers;
>
>I am trying to write a Rexx routine that takes in 3 arguments. First is DSN,
>second is Member name, third is a string of text. The string of text is the
>concatenation of lines delimited by a ";&qu
On Mon, 26 Aug 2013 14:21:18 -0400, George Shedlock wrote:
>Gentle Listers;
>
>I am trying to write a Rexx routine that takes in 3 arguments. First is DSN,
>second is Member name, third is a string of text. The string of text is the
>concatenation of lines delimited by a ";". (ex. "line1;line2;l
I would suggest that you read up on EXECIO * DISKW and stems
You will figure it out if you look at the file that got the E37
On Mon, 26 Aug 2013 14:21:18 -0400 George Shedlock
wrote:
:>Gentle Listers;
:>
:>I am trying to write a Rexx routine that takes in 3 arguments. First is DSN,
second is M
>PDS cannot spanned volumes, PDSE maybe??? (I forget but maybe not)
Neither.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv
On 2013-08-26 13:41, Lizette Koehler wrote:
> First, there is a REXX Newsgroup that might be more helpful.
>
> To sign up - if you have not done so - go to the bottom of this webpage:
> http://www2.marist.edu/htbin/wlvindex?TSO-REXX
>
>
> Second, why use EXECIO instead of ISPF LM functions?
>
On Mon, 26 Aug 2013 22:43:46 +0300, Binyamin Dissen wrote:
>I would suggest that you read up on EXECIO * DISKW and stems
>
>You will figure it out if you look at the file that got the E37
>
Kind of a snarky RTFM, but I suppose I was similarly Socratic in my followup.
So, I RTFM; Title: z/OS V1R1
>When EXECIO writes an arbitrary number of lines from a list of
>compound variables, it stops when it reaches a null value or an
>uninitialized variable (one that displays its own name).
>** * Top of Data
>01 First line
>02 S.2
>0
On 2013-08-26 17:03, Gerhard Adam wrote:
>>When EXECIO writes an arbitrary number of lines from a list of
>>compound variables, it stops when it reaches a null value or an
>>uninitialized variable (one that displays its own name).
>
>> ** * Top of Data
Yes, but you took that description out of context since you excluded the
additional qualifier of being an uninitialized variable. The original
statement never made the claim that simply displaying its own name was a
sufficient condition. It was descriptive of the case of being an uninitialized
The problem is
outstem.=0
which sets an infinite number of instances of outstem.x to the non-null
value "0" for all "x". DISKW from a stem variable does not stop based
on a count in outstem.0, it stops when the first null outstem.n value
for n=1, 2, ... is found, which is "never" in this case.
And although this change would not be needed for the code to work, for
consistency and to actually use the outstem.0 value as a constraint the
EXECIO should probably be changed to
"EXECIO" outstem.0 "DISKW Pdsout (STEM outstem. FINIS"
That way the code could even be re-executed without having to Dr
On Mon, 26 Aug 2013 21:27:42 -0500, Joel C. Ewing wrote:
>And although this change would not be needed for the code to work, for
>consistency and to actually use the outstem.0 value as a constraint the
>EXECIO should probably be changed to
>"EXECIO" outstem.0 "DISKW Pdsout (STEM outstem. FINIS"
>T
Hello George,
your code is right except your inititialyze for 'outstem.=0'. This initialyze
the complete stem 'outstem.' with '0' and than the execio tries to write many
(I do not know how much) lines to your output file.
When you initialyze only 'outstem.0=0' for computing your stem counter yo
On Tue, 27 Aug 2013 01:51:54 -0500, Karl-Heinz Doppelfeld wrote:
>
>your code is right except your inititialyze for 'outstem.=0'. This initialyze
>the complete stem 'outstem.' with '0' and than the execio tries to write many
>(I do not know how much) lines to your output file.
>
>When you initial
In , on 08/26/2013
at 02:21 PM, George Shedlock said:
> "EXECIO * DISKW Pdsout (STEM outstem. FINIS"
The * is not equivalent to outstem.0 and the description of FINIS
suggest that you may want it in a separate EXECIO invocation.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Ati
On Mon, 26 Aug 2013 17:14:58 -0400, Shmuel Metz (Seymour J.) wrote:
>
> ... the description of FINIS
>suggest that you may want it in a separate EXECIO invocation.
>
Can you explain? I've never had a problem with it.
-- gil
--
To All:
First, the output dataset was created immediately prior to executing the
exec. It was defined as a standard FB 80 PDS of 10 cylinders with 30 directory
blocks. For testing, my code only was generating 3 lines of output into a
single member in that PDS.
Lizette:
I am using EXECIO i
DU
Subject: Re: Rexx Execio to PDS
To All:
First, the output dataset was created immediately prior to executing the
exec. It was defined as a standard FB 80 PDS of 10 cylinders with 30 directory
blocks. For testing, my code only was generating 3 lines of output into a
single member in that PDS
In <4868602893006577.wa.paulgboulderaim@listserv.ua.edu>, on
08/26/2013
at 04:47 PM, Paul Gilmartin said:
>It should probably be stressed that EXECIO, unlike most Rexx
>utilities does not "[substitute] the values of any simple symbols in
>the tail" as described in 2.4.3,
Unlike? How many
On Tue, 27 Aug 2013 08:45:22 -0400, George Shedlock wrote:
>
>Paul:
> You have noted one of the subtle differences in the way that Execio works
>in the CMS vs TSO environments. It seems that in CMS, the "EXECIO *" stops
>after the stem runs out. In TSO, it continues on forever resulting in my o
In <8482246969138410.wa.karlheinz.doppelfeldfi...@listserv.ua.edu>, on
08/27/2013
at 01:51 AM, Karl-Heinz Doppelfeld
said:
>your code is right except your inititialyze for 'outstem.=0'. This
>initialyze the complete stem 'outstem.' with '0'
That's only an issue due to the * for line count. H
On Tue, 27 Aug 2013 09:02:03 -0400, Shmuel Metz (Seymour J.) wrote:
> on 08/26/2013 at 04:47 PM, Paul Gilmartin said:
>
>>It should probably be stressed that EXECIO, unlike most Rexx
>>utilities does not "[substitute] the values of any simple symbols in
>>the tail" as described in 2.4.3,
>
>Unli
George,
The first Parse in the original loop is a useful technique. No
complaints there, only about the 2nd parse that changes t, outstem.t and
outstem.0 in one statement. The original
...
do forever
parse var MyArg thisword ';' MyArg
if thisword='' then leave
thisword = Left
In <8027846442974110.wa.paulgboulderaim@listserv.ua.edu>, on
08/27/2013
at 07:36 AM, Paul Gilmartin said:
>Can you explain?
Never mind; the text that I was looking at only applies if the line
count is 0. Sorry for the mistake.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Ati
In <9390988258167395.wa.paulgboulderaim@listserv.ua.edu>, on
08/27/2013
at 08:33 AM, Paul Gilmartin said:
>I'm most familiar with "address SYSCALL".
Address is a keyword statement, not a REXX utility.
>That's one.
No.
>That's one. But, right back at you: how many utilities, other than
28 matches
Mail list logo
