Number of added instructions?

I'm doing a presentation and wanted to quickly mention how the mainframe architecture instruction set has grown. Does anyone happen to know the number of different unprivileged machine instructions there were in the early 370 days versus the latest soon-to-be-released z/Architecture instruction

Re: [SPAM] NSLOOKUP vs BPX1GHN

Assuming that PLIST points to a valid remote parameter list, I think that your best bet is to dump PLIST before the call to make sure it looks okay and to turn on Trace Resolver output with a //SYSTCPT DD SYSOUT=* I'm not sure how you're getting your base resolver files. Have a look at

Re: NSLOOKUP vs BPX1GHN

Sorry, this Subject was tagged with a [SPAM] notation on my end and I neglected to remove it before I replied. Gary -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER- l...@listserv.uga.edu] On Behalf Of Gary L Peskin Sent: Saturday, November 27, 2010 11:16 PM

Re: Assembler XPLINK parameters 3

Hi, Kirk -- Don't you need to bias R4 by adding +2048 (CEEDSAHP_BIAS) to it? In other words, isn't R4 really pointing to DSA - CEEDSAHP_BIAS? Gary -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER- l...@listserv.uga.edu] On Behalf Of Kirk Wolf Sent: Monday,

Re: BPAM multiple members/one DCB and EODAD exit?

Hi, Dave - As I read the docs, NOTE only works after a READ or WRITE. You'll get an invalid value if you use it after a FIND or POINT. Gary -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Thomas David Rivers Sent: Friday,

Re: BAKR Instruction

Hi, Paul -- In a BAKR R14,R15 instruction, the R14 value is the value to which the branched-to routine will return when it executes the PR. So your statement "Register 14 (operand 1) would contain the next sequential instruction" is correct if you're talking about the value of R14 _before_ the

Re: Scholarly Articles Evaluation Report Was Case Study: IBM SYSTEM/360/37 0 ARCHITECTURE (1987)

Hi, Paul -- This is now called the National Security Agency / Central Security Service. According to this web page https://www.nsa.gov/business/contacts/, you might try contacting the NSA/CSS Commercial Solutions Center at +1.240.373.4163 (i...@nsa.gov) and see if they know of such a report on

Re: Decimal Floating Point Numbers

Hi, Abe - In the version of the PoP that I'm looking at, it states that ". Except where otherwise indicated, ...DFP [is defined] in terms of the right-units view. So I think that's just a convention in the documentation. As far as LUV vs RUV, a given value is represented the same in a

Re: Decimal Floating Point Numbers

regards, Abe === Op 04/03/2024 om 09:08 schreef Gary L Peskin: > Hi, Abe - > > > > In the version of the PoP that I'm looking at, it states that ". Except where > otherwise indicated, ...DFP [is defined] in terms of the right-units view. So > I thin

Re: Decimal Floating Point Numbers

But you need to look at the bias for the exponent. Both views would be encoded the same. I guess I didn't explain this very well before but this example will help. For the short format, there are 7 significant digits. For the LUV, bias of the exponent is 95. For the RUV, bias of the

Re: Decimal Floating Point Numbers

- Biased Exp = 98 007E-4 - Biased Exp = 97 070E-5 - Biased Exp = 96 700E-6 - Biased Exp = 95 Which clearly shows that in the encoded format the RUV vs LUV is not relevant. Thanks a lot for helping me understand. Kind regards, Abe === Op 05/03/2024 om 18:19 schreef Gary L Peskin