Yep.
I have some production customers still running on MP2000s and MP3000s. I
have to always take that into consideration. (Relatives came in with the
MP3000.)
Tony Thigpen
Seymour J Metz wrote on 05/07/2018 11:54 AM:
Keep in mind that some are still running OS/VS2 R3.8 under Hercules, so they
might want options to support *really* old architecture levels.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on behalf of
John McKown <john.archie.mck...@gmail.com>
Sent: Monday, May 7, 2018 9:44 AM
To: ASSEMBLER-LIST@listserv.uga.edu
Subject: Re: storing and restoring condition code
On Sun, May 6, 2018 at 2:39 PM, Seymour J Metz <sme...@gmu.edu> wrote:
Only in 24-bit mode.
If you do a macro, make it mode and architecture sensitive. I used to do
something similar for code that could be assembler either for S/360 or for
S/370; the macros only used, e.g., ICM, if they were assembling the 370
version..
Just tapping in here, perhaps incorrectly. I would _strongly_ suggest that
any HLASM code being written today use the SYSSTATE macro to specify it's
"environment" requirements. Ref:
https://secure-web.cisco.com/1XhrCofTaKBWD3zoY6GGkoO4f27Nf6hPPAAmJ1fixdDsEumNzj8AI-Vl9MvVFb9gHsP1sRKycghbXLBlFjt7qvndjg6DysTenm_KHlxfl-3Iegn_35QFoYMh--cgJwoMYHssKwRxkdEqNFXUstJc2CJUDuWzYEkrWu6pxVu2McJufJ_DHCNhHm82gW3eiC3l7pIPe4Xz9QrL8E57wF7-X2URXX71d0ybZ4r_a_6M_teG6eKUBbGqKzySzOSoHe13zv0Si8WMtt6My9b_kfSEln8hnHaRuysh2P9dW4LVpfjNlUZJnzz7qGOinq44xfzKf5ikXzhRaQ6_Q1pHix7904HSWX-8ilp5QYOu890HqRN8zhDZxlW0G3zgHJhcx4aHUIWGuMIUkiIGF9OtMwqoowKG8-671VPjkqxaYmg0l6C0NKN7ZW7Pw8qF3cCCjXpQv/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.ieaa900%2Fstate.htm
And any macros should use the macro variables set by that macro for their
internal processing. E.g. what AMODE to assume for instructions; whether to
use "base+index" or "relative" instructions; and so forth.
What got me onto this is that the default ARCHLVL=0 causes the other IBM
macros to use the "Branch On Condition" instruction instead of the "Branch
On Condition Relative" instruction. Yeah, that's probably well known, but
it messed me up until I read the above to try to understand why the IBM
macros didn't do what I was wanting.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
--
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.
Maranatha! <><
John McKown
