I agree with Rob and Binyamin in worrying about a design that imposes
non-swappability on someone else's address space.
I'll point out that in general TRANSWAP involves "swap in" and "don't
allow subsequent swap-out" and "wait for completion by ECB".
You can't do the wait for completion from an S
I do the okswap after I do a get from the cell pool
Thanks
> On Feb 24, 2020, at 8:43 AM, Peter Relson wrote:
>
> I agree with Rob and Binyamin in worrying about a design that imposes
> non-swappability on someone else's address space.
> I'll point out that in general TRANSWAP involves "
On Mon, 24 Feb 2020 at 08:43, Peter Relson wrote:
> The information provided so far does not show doing some sort of "OKSWAP"
> afterwards. It would be inappropriate to leave the space non-swappable.
Just as it would be inappropriate to make it swappable if it was
non-swappable to start with. Is
A trivial item, but this surprised me.
I wanted to parse out the string 'word3' using the period as a place holder.
The input could have a blank delimited string containing an embedded period
before the one I wanted to parse out. The Parse Var as coded didn't work.
Using the Parse Value as c
Why did it surprise you, and what does it have to do with the placeholders?
You'd get the same thing if you used three variable names instead of three
periods. The parse with works because it's using a different template on a
different value: try
parse Value myVar with . . . myVal '.' .
-
You mean like this?
*-* Parse Value myVar with . . . myVal2 '.' .
>>> "word1 word2 9.12 word3.ext"
>.> "word1"
>.> "word2"
>.> "9"
>>> ""
>.> "12 word3.ext"
But you're correct, variables result in the same behavior:
*-* Parse Value myVar with t1 t2 t3 myVal2 '.' .
>>> "word1 word2
On Mon, 24 Feb 2020 20:43:52 +, Ambros, Thomas wrote:
>A trivial item, but this surprised me.
>
>I wanted to parse out the string 'word3' using the period as a place holder.
>The input could have a blank delimited string containing an embedded period
>before the one I wanted to parse out.
To be fair, while the PL/X source is retained in comments to the assembler,
those macros are generated in way that allows them to be used in both
assemblies and PL/X compiles.
Wayne Driscoll
Rocket Software
Note - All opinions are strictly my own.
-Original Message-
From: IBM Mainframe
Isn't that the same, except for the choice of variable names?
For the type of source string that you're parsing, I'd probably break it into
words with a simple parse and then use a parse var foo bar '.' baz
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
__
You have "passed" your first period before your "'.'" in the parse
statement is actually interpreted.
For your data example:
myVar = 'word1 word2 9.12 word3.ext'
The correct parse is:
Parse Value myVar with . . myVal2 '.' .
Each period, or var name, in the parse "eats" one blank delimited word.
On Mon, 24 Feb 2020 18:08:48 -0500, Tony Thigpen wrote:
>You have "passed" your first period before your "'.'" in the parse
>statement is actually interpreted.
>
>For your data example:
>myVar = 'word1 word2 9.12 word3.ext'
>The correct parse is:
>Parse Value myVar with . . myVal2 '.' .
>
>Each pe
On Fri, 14 Feb 2020 10:52:07 -0800, Charles Mills wrote:
>...
>Agree with Lionel's recommendation. Even if the usage is going to be 90% C and
>10% HLASM you want to do the DSECT first and work from there.
>
I find it ironic that a weakly typed language such as assembler is a good
source for g
It's crude, but I have a similar goal, I just threw this D R,R and System Rexx
parse together.
/* rexx */
CmdResult=AXRCMD('D R,R','v.',10);
FSVO typed.
void * foo
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Monday, February 24, 2020 6
On Tue, 25 Feb 2020 00:58:26 +, Seymour J Metz wrote:
>FSVO typed.
>
>void * foo
>
So I can't do "foo -> member", but must "(type *) foo-> member". Ugh!
>
>From: Paul Gilmartin
>Sent: Monday, February 24, 2020 6:54 PM
>>...
>>Agree with Lionel's r
Have you ever seen me praising C? Vile imprecations don't count as praise.
(I will admit to defending the idiom for (;;) {code}) as an obvious do forever.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-M
Interesting. Seymours example came back with a blank.
I used PARSE VALUE MYVAR WITH . . . '.' . WORD3 '.' EXT .
On Tue, Feb 25, 2020 at 10:46 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 24 Feb 2020 18:08:48 -0500, Tony Thigpen wrote:
>
> >You have "pass
Hi all,
I've just published my latest endeavour on github: a free open source
disassembler in Rexx.
https://github.com/abend0c1/da
...it supports all instructions in the POPs including the latest z15 ones.
Could be handy if you have lost some source code over the years.
I'm pretty happy with i
18 matches
Mail list logo
