riginal Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: 15 August 2020 01:53
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Rexx detail, or things I dont do often enough
On Fri, 14 Aug 2020 23:29:21 +, Dymoke-Bradshaw, Lennie wrote:
>There is a
I dont do often enough
Gil wrote:
>... All I see is:
>Purpose
>Use the RECEIVE command to read onto a disk or directory one of the
> files
>or notes in your virtual reader. ...
>... no suggestion of RECEIVE from a SFS or MDFS file.
Oh, sorry. I missed th
Gil wrote:
>... All I see is:
>Purpose
>Use the RECEIVE command to read onto a disk or directory one of the files
>or notes in your virtual reader. ...
>... no suggestion of RECEIVE from a SFS or MDFS file.
Oh, sorry. I missed that you were asking about origin, not
I'm glad you asked, because I'm rusty and I recently used "parse source" to
get the name of the running Rexx file and then read it line-by-line.
(Regina Rexx, just for my own use. I wanted a model input file available
from comments in the source).
I think sourceline() is likely to be more
On Sun, 16 Aug 2020 12:20:10 -0400, Phil Smith III wrote:
>
>>z/OS TSO RECEIVE has the useful FROMDSN and FROMDD options. Has
>>CMS RECEIVE anything similar? But there are the Pipelines 64DECODE
>>and DEBLOCK NETDATA filters which should be useful for this. No
>>PIPELINES VMARC, AFAIK.
>
>Sure:
Paul Gilmartin wrote:
>z/OS TSO RECEIVE has the useful FROMDSN and FROMDD options. Has
>CMS RECEIVE anything similar? But there are the Pipelines 64DECODE
>and DEBLOCK NETDATA filters which should be useful for this. No
>PIPELINES VMARC, AFAIK.
Sure: RECEIVE >>
MAILABLE was also
On Sun, 16 Aug 2020 00:50:28 -0400, Phil Smith III wrote:
>http://www.vmworkshop.org/HENSLER/ includes my MAILABLE EXEC, which uses this
>technique to create self-extracting blobs wrapped in Rexx code to unpack them.
>Alas, it's VM-only, but it illustrates the idea.
>
>This was useful back in
http://www.vmworkshop.org/HENSLER/ includes my MAILABLE EXEC, which uses this
technique to create self-extracting blobs wrapped in Rexx code to unpack them.
Alas, it's VM-only, but it illustrates the idea.
This was useful back in the era when folks had a lot of problems getting EBCDIC
On 2020-08-14 19:56, Gibney, Dave wrote:
> I have this vague memory of being able to have data embedded inside a Rexx
> Exec. Some manner of data start and end delimiting lines and accessed via
> looping with PULL or PARSE. I know I can just PUSH or QUEUE data onto the
> stack, but that's not
On Fri, 14 Aug 2020 23:29:21 +, Dymoke-Bradshaw, Lennie wrote:
>There is a DATA ENDDATA pair that can be used in TSO CLIST processing.
>
What does that have to do with Rexx?
The CLIST Ref. says:
commands | subcommands
The data to be ignored and passed to TSO/E for execution.
I don't need it often, but it's pretty handy when I want to hard-code a table
of data for the program to use. If the values are static enough, it makes
sense to store them in the program's comments instead of in a separate dataset.
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/*
There is a DATA ENDDATA pair that can be used in TSO CLIST processing.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gibney, Dave
Sent: 14 August 2020 20:56
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Rexx detail, or things I dont do often enough
I
Opps. Forgot the sigl...
בתאריך שבת, 15 באוג׳ 2020, 0:31, מאת Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu>:
> On Fri, 14 Aug 2020 23:45:19 +0300, ITschak Mugzach wrote:
>
> >I once wrote an installer that behaved like a zip exec. I think it was
> >discussed here as well. The
On Fri, 14 Aug 2020 23:45:19 +0300, ITschak Mugzach wrote:
>I once wrote an installer that behaved like a zip exec. I think it was
>discussed here as well. The idea is like the sample code below that
>demonstrates reading panel from the program body for later saving it in a
>temporary file.
st On Behalf Of
ITschak Mugzach
Sent: Friday, August 14, 2020 3:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Rexx detail, or things I dont do often enough
I once wrote an installer that behaved like a zip exec. I think it was
discussed here as well. The idea is like the sample code below that
14, 2020 at 11:05 PM Gibney, Dave wrote:
>
>> I think this is what I was looking for. Couldn't find the source line
>> access in the fine manual.
>>
>> > -Original Message-
>> > From: IBM Mainframe Discussion List On
>> > Behalf Of Seymour J Metz
&g
2020 1:09 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Rexx detail, or things I dont do often enough
>
> ">>-SOURCELINE(--+---+--)---><
> '-n-'
>
> returns the line number of the final line in the progr
/mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Gibney, Dave
Sent: Friday, August 14, 2020 4:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Rexx detail, or things I dont do often enough
I think this is what I was looking for. Couldn't find the source line acce
L4kdSh4x5MLNKPALpw8c-
> yeSsg4Vf-GBrak71rQ$
>
>
>
> From: IBM Mainframe Discussion List on
> behalf of Gibney, Dave
> Sent: Friday, August 14, 2020 3:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Rexx detail, or things I dont d
@LISTSERV.UA.EDU
Subject: Rexx detail, or things I dont do often enough
I have this vague memory of being able to have data embedded inside a Rexx
Exec. Some manner of data start and end delimiting lines and accessed via
looping with PULL or PARSE.
I know I can just PUSH or QUEUE data onto the stack
I have this vague memory of being able to have data embedded inside a Rexx
Exec. Some manner of data start and end delimiting lines and accessed via
looping with PULL or PARSE.
I know I can just PUSH or QUEUE data onto the stack, but that's not what I
vaguely remember. Am I all wet, or just
21 matches
Mail list logo
