Agreed.
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of robi...@dodo.com.au
Sent: Tuesday, June 25, 2019 7:44 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ltorg question
On 2019-06-26 11:47, Mike La Martina wrote:
>
On 2019-06-26 11:47, Mike La Martina wrote:
Floating point is stored in double words.
Floating-point can also be stored in a word (i.e., single precision).
Most of the time the nominal
value is 0, which looks the same in hex and Floating Point.
The FD notation seems weird to me. But it
Someone wrote:
> Thought it was a double word
> As in DS D
It is a doubleword, specifically a long (64 bit) floating point type.
And yes,
DS D
and
DS 0D
are commonly used when floating point is not intended.
And as Fortran programmers would know, E is the short (32 bit)
Floating point is stored in double words. Most of the time the nominal
value is 0, which looks the same in hex and Floating Point.
The FD notation seems weird to me. But it takes care of alignment.
-Original Message-
From: IBM Mainframe Assembler List
DS D defines a floating point field. 4110 is a normalize
floating point 1.
Use FD for a fixed 64-bit integer.
LTORG is irrelevant. Works the same as a literal or as a DC.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
Thanks
> On Jun 25, 2019, at 9:01 PM, Mike Hochee wrote:
>
> Hey Joe,
>
> The 'D' (floating point constant type) and F (fixed point constant type)
> have been around forever. Somewhere between 95-2002 IBM added the
> type-extension subfield to the DC instruction. As of 2004, D became a
Thought it was a double word
As in DS D
> On Jun 25, 2019, at 9:01 PM, Mike Hochee wrote:
>
> Hey Joe,
>
> The 'D' (floating point constant type) and F (fixed point constant type)
> have been around forever. Somewhere between 95-2002 IBM added the
> type-extension subfield to the DC
Hey Joe,
The 'D' (floating point constant type) and F (fixed point constant type) have
been around forever. Somewhere between 95-2002 IBM added the type-extension
subfield to the DC instruction. As of 2004, D became a valid type-extension,
which clarifies characteristics of the type, so in
I see the following literal
41101403=D'1'
Shouldn't it of translated to
0001
And the same for -4
C1401406=D'-4'
Shouldn't it of translated to
To
FFFC
thanks
Both my estate and setrp are below the bar however I didn't notice any
difference in the expansion of the setrp macro when processing a setrp for
amode 31 bit and for amode 64 bit
Meaning when I had retaddr=(R4) in amode 31 the setrp code expanded to a ST R4
and the same when I had it
You can’t retry to rmode64 code. You have to have a stub code below the bar to
retry to and have the stub enter your rmode64 code.
Chuck Arney
> On Jun 25, 2019, at 3:16 PM, Joseph Reichman wrote:
>
> Would any one know the parms on the SETRP when retrying 64 bit code It tred
>
>
>
> I
Would any one know the parms on the SETRP when retrying 64 bit code It tred
I tried SETRP RC=4,RETADDR=(R4),RETREGS=64,DUMP=NO,RETRYAMODE=64 and I saw
the same ST R4 without the RETRYAMODE64 PARAMTER was hoping to see STG
In an instance where the IPL fails due to an ALS related issue, what would
the wait state code be and would there be any system messages generated?
Did this get answered?
The wait state code and wait state reason depend on which ALS was not met.
-- 07B reason 1E is "not even a z9" (you won't
13 matches
Mail list logo
