@Peter, thank you for the direct answer. Yes, I would consider an "ARCH level," a "ZS- number" or a "marketing architecture number" such as 13 to be a great answer to my need. As you move your emphasis more from assembler to compiled languages an ARCH number rather than "op code bits" would be a good idea IMHO.
Catching the S0C1 is more complicated than it sounds. There is kind of a chicken and egg problem. The code is 95% in C++. I am trying to avoid starting in assembler and calling the C main, which would however make this problem trivial. I have a recovery routine and it works perfectly, knock on wood. But setting it up and setting up the things it depends on requires code, there is a problem (not insurmountable, but not easy -- see companion thread) with compiling some modules at one ARCH level and some at another, and so the C++ code S0C1s long before it gets its recovery routine set up. (FWIW, it S0C1ed trying to display its initial "hello" and version number message.) Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Relson Sent: Thursday, November 26, 2015 6:12 AM To: [email protected] Subject: Re: Straightforward way to determine hardware architecture level? To answer your question directly: no there is no such way. Could there be, in the future? Sure. If z/OS base control program were to provide it, it might not be the compiler ARCH value but might be the machine generation number (which happens to be +2 over the compiler ARCH level) -- e.g., z13 happens to be "13" (not a big stretch). If LE or a compiler area were to provide it, then it would more likely be the number that they use. The problem that you wrote that you were challenged with solving was " couldn't we put out a better message than S0C1?"" And the answer is for the most part "yes", without requiring an answer to the question you posed: field the PIC 1 in recovery and deal with it in a nicer way than you currently do (such as a message, a unique abend/reason code pair that you document for your product, whatever). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
