Re: Missing New z16 Instructions
The new extended mnemonics for existing instructions are
just to make it easier for programmers, as usual, once
they can rely on having the appropriate level of HLASM.
I have been asked more than once why there isn't an LFI
instruction and had to point users to I
ler List On Behalf
Of Jonathan Scott
Sent: Wednesday, May 11, 2022 7:42 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Missing New z16 Instructions
The new extended mnemonics for existing instructions are
just to make it easier for programmers, as usual, once
they can rely on having the appropri
Hi Gil,
There is no need, when disassembling code, for z/XDC's JZ/JE choice
to be perfect.
It just looks at the immediately prior few instructions and makes a
decision base on what it sees.
It the specific case of AL/SL, yeah it's kinda a toss-up. I chose to
consider them to be
On May 10, 2022, at 13:06:21, Gary Weinhold wrote:
>
> I think VM/370 (CP or CMS, perhaps both) used to rely on the CC after a
> calls to internal routines.
>
> As a debugger, since it's tracing the instructions, I wouldn't be
> surprised if it knew exactly which instruction set the CC.
>
I
I think VM/370 (CP or CMS, perhaps both) used to rely on the CC after a
calls to internal routines.
As a debugger, since it's tracing the instructions, I wouldn't be
surprised if it knew exactly which instruction set the CC.
On 2022-05-10 2:29 p.m., Paul Gilmartin wrote (snipped):
What if
On May 10, 2022, at 11:58:40, David Cole wrote:
>
> At 5/8/2022 07:14 AM, Jonathan Scott wrote:
>> >LFI for IILF, LLGFI for LLILF
>> >SLLHH, SLLHL, SLLLH, SRLHH, SRLHL, SRLLH
>> >
>> >As they are all extended mnemonics, they are not normally used
>> >by debugging tools. They are not used by the
At 5/8/2022 07:14 AM, Jonathan Scott wrote:
>LFI for IILF, LLGFI for LLILF
>SLLHH, SLLHL, SLLLH, SRLHH, SRLHL, SRLLH
>
>As they are all extended mnemonics, they are not normally used
>by debugging tools. They are not used by the HLASM disassembler.
>
>Jonathan Scott, HLASM
>IBM Hursley, UK
Jonathan, thank you!
Am 08.05.22 um 13:14 schrieb Jonathan Scott:
HLASM APAR PH39324 mentions new op-codes ...
The following mnemonics are new extended mnemonics for existing
instructions and are listed in the new very helpful Appendix J
of z/Architecture Principles of Operation.
1.
> HLASM APAR PH39324 mentions new op-codes ...
The following mnemonics are new extended mnemonics for existing
instructions and are listed in the new very helpful Appendix J
of z/Architecture Principles of Operation.
1. Alternative mnemonics for existing instructions which fit
into more than
HLASM APAR PH39324 mentions new op-codes
but
neither POP nor shortref have some of them. The missing mnemonics are
LFI
LLGFI
SLLHH
SLLHL
SLLLH
SRLHH
SRLHL
SRLLH
While I can fantasize about what they do, I have no idea of the real
op-code.
Can someone (with the PTF applied) please
Now that POPS-13 is out:
I see and understand LBEAR and STBEAR.
But I wounder why RP did not get a non-bear destruction brother of RPY
like LPSWE did with LPSWEY.
Martin
Peter,
I still have no exact idea what both instructions do (waiting for the
book of books) , but your stmt
>> Both LBEAR and STBEAR are created for OS's other than z/OS
let me hope that both where for ALSO not for the little stepbrother z/VSE.
And now I can even visualise
Both LBEAR and STBEAR are created for OS's other than z/OS.
Could z/OS use them constructively? Possibly. If by "constructive" we
positively balance functional benefit over performance cost.
Could an application use STBEAR constructively? Possibly. Probably more likely
to be of constructive
Ed,
after I wrote back to Dave- just what you said occurred to me too. In
some cases It might be nice to find out "how was I called" or from where
(and thus reading the bear and not location 110).
And maybe the two (LBEAR and STBEAR) are just two flavors of the very
same- one against
On 4/17/2022 1:12 AM, Martin Trübner wrote:
what would LBEAR do other than a LG Rn,X'110' ?
Martin, X'110' is not the BEAR. The BEAR is a special register that
holds the last Breaking Event Address (BEA). X'110' is simply the place
where the BEAR is automatically stored when an interrupt
You are correct, I reversed L and ST in my thought
> -Original Message-
> From: IBM Mainframe Assembler List l...@listserv.uga.edu> On Behalf Of Seymour J Metz
> Sent: Sunday, April 17, 2022 1:48 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: Re: the BEAR (was: Ne
List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Martin Trübner [mar...@pi-sysprog.de]
Sent: Sunday, April 17, 2022 4:12 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: the BEAR (was: New z16 Instructions)
Dave,
what would LBEAR do other than a LG Rn,X'110' ?
and what is STBEAR good
A.EDU
> Subject: the BEAR (was: New z16 Instructions)
>
> Dave,
>
>
> what would LBEAR do other than a LG Rn,X'110' ?
>
>
> and what is STBEAR good for? to falsify the original?
>
>
> I wait for the POP to describe them in more detail
>
>
> Martin
--->
On Sat, Apr 16, 2022 at 8:33 PM Paul Gilmartin <
0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote:
> On Apr 16, 2022, at 17:32:03, Steve Smith wrote:
> ...
> Do any mnemonics use numeric digits? Is it IBM's intention never
> to use digits in mnemonics? (But at one time IBM seemed
.
If the POP manual is not available, where can one find the new instructions ?
-- Original Message --
From: Martin Trübner
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: the BEAR (was: New z16 Instructions)
Date: Sun, 17 Apr 2022 10:12:07 +0200
Dave,
what would LBEAR do other
Dave,
what would LBEAR do other than a LG Rn,X'110' ?
and what is STBEAR good for? to falsify the original?
I wait for the POP to describe them in more detail
Martin
Am 16.04.22 um 23:47 schrieb Gibney, Dave:
It seems problematic to do a STBEAR, but I can see the utility of LBEAR.
On Apr 16, 2022, at 17:32:03, Steve Smith wrote:
>
> Another alternative is to OPSYN delete the new instructions that conflict.
> I think that will work: I rtfm, but not tested.
>
A group I worked with did that and also used OPTABLE, partly to ensure
That our code worked with downlevel customer
Another alternative is to OPSYN delete the new instructions that conflict.
I think that will work: I rtfm, but not tested.
Personally, I think adding :MAC would just be more work. You might as well
rename the macro.
While I really find gratuitous usage of national character prefixes to be
ugly,
fe
> Sent: Saturday, April 16, 2022 1:23 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: New z16 Instructions
>
> [EXTERNAL EMAIL] DO NOT CLICK links or attachments unless you recognize
> the sender and know the content is safe.
>
> We just applied this APAR to our system
On Apr 16, 2022, at 14:22:59, Ed Jaffe wrote:
>
> We just applied this APAR to our systems:
>
> https://www.ibm.com/support/pages/apar/PH39324
>
... which links to a "Fix Readme" with recommendations
for dealing with possible clashes between 30 new
instruction mnemonics and customer-defined
We just applied this APAR to our systems:
https://www.ibm.com/support/pages/apar/PH39324
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
26 matches
Mail list logo
