Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration-z/Architecture-Architecture-Mode and ESA/390-Compatibility-Mode Facilities #336

Open
s390guy opened this issue Nov 29, 2020 · 2 comments
Assignees
Labels
Discussion Developers are invited to discuss a design change or solution to a coding problem. Enhancement This issue does not describe a problem but rather describes a suggested change or improvement. Related This issue is closely related to another issue. Consider this issue a "sub-issue" of the other.

Comments

@s390guy
Copy link
Contributor

s390guy commented Nov 29, 2020


Note: this issue is closely related to issue #78: "z14 z/Architecture-only mode (CZAM)".


At one level this is really an ASMA question. But ASMA should do what Hercules does. So, here goes...

At one level it is simply about implementing a new PSW format. But it also puts a stake in the ground relative to ESA/390 support. The PoO suggests these two facilities might be installed separately. But, my understanding is that in practice they will both be present.

We have as near as I can tell merged ESA/390 and zArch in Hercules. ESA/390 is now on a Z box. There is no ability to actually have an ESA/390 machine not on a z box. Now we will need to separate them going forward. I truly believe the ESA/390 Compatibility Mode is also temporary. Not even sure how you get into that mode on a real machine.

I am trying to catch up with ASMA. I am looking at the 2017 PoO when these two facilities were introduced. That is part of why I am asking.

Has anyone thought about the implications?

Harold Grovesteen

@s390guy s390guy added the Discussion Developers are invited to discuss a design change or solution to a coding problem. label Nov 29, 2020
@Fish-Git
Copy link
Member

Configuration-z/Architecture-Architecture-Mode

Also known as "CZAM", for which, FYI, a GitHub Issue already exists: "z14 z/Architecture-only mode (CZAM)" #78

ESA/390-Compatibility-Mode Facilities

Which, FYI, is already listed in our existing "MISSING Facilities support" #77 GitHub Issue.

Has anyone thought about the implications?

Not really, no. Haven't had any time!   :(

We simply have too much on our plate as it is. Deciding which facility should be worked on next (i.e. which facility takes priority over other facilities) is difficult. As for myself, I tend to choose the ones I personally feel might be the quickest and easiest to complete (*), leaving the trickiest most difficult ones for later (i.e. ones that would likely require much discussion among all of us developers).

But the question whether I have spent much thought on how to implement the two specific facilities you mentioned? (CZAM and 390-Compatibility)

Nope. Not really. Sorry.   :(

BUT ... I'd nevertheless be very interested in hearing others thoughts on the subject, should you wish to discuss it! So I guess it's good that you asked the question, Harold! Thank you!   :)


(*) Such as Facilities 58 and 61 for example (Miscellaneous Instructions Facility 2 and 3), which I've had coded for quite some time now, but which, oddly, causes z/OS (2.4?) to fail to IPL for some as-yet-unknown reason (the cause of which I haven't had any time to look into due to TXF taking priority).

@Fish-Git Fish-Git added the Related This issue is closely related to another issue. Consider this issue a "sub-issue" of the other. label Dec 3, 2020
@Fish-Git Fish-Git added the Enhancement This issue does not describe a problem but rather describes a suggested change or improvement. label Dec 12, 2020
@s390guy s390guy self-assigned this Mar 2, 2021
@s390guy
Copy link
Contributor Author

s390guy commented Feb 11, 2023

The file "CZAM_300-CM" has been uploaded to the hercules-390 groups.io file section. This file describes what is involved in each of the facilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Developers are invited to discuss a design change or solution to a coding problem. Enhancement This issue does not describe a problem but rather describes a suggested change or improvement. Related This issue is closely related to another issue. Consider this issue a "sub-issue" of the other.
Projects
None yet
Development

No branches or pull requests

2 participants