On 2015-04-27 14:23, Gary Weinhold wrote:
In a way it's not; a software package can be coded to check as it
initializes whether the hardware functionality it requires exists on the
platform. If it doesn't, it can end gracefully with an appropriate
message.
But my original question was looking for the easiest way to determine
what hardware functionality is actually required for a given set of
assembler programs developed on hardware that is relatively state of the
art with HLASM defaulting to the latest architecture level.
We deal with this situation by assessing the minimum hardware and
operating system levels that we should support in any given release of
our products. In other words, we never accept the HLASM defaults for the
OPTABLE or the ARCHLVL.
Here's what we do:
- install a usermod to change the default HLASM options to include
PROFILE=YES;
- include a ASMAPROF member in the macro library for each release of
our products.
The ASMAPROF member for each release sets the OPTABLE to be used for
that release, as well as the ARCHLVL and the OSREL. Thanks to
PROFILE=YES, the ASMAPROF member is always read and the settings we want
for the affected release are always used.
I understand that you asked the question about code that has already
been written, but it might be more useful to decide what machines and
operating systems you want to be able to support rather than seeing what
machines and operating systems support your compiles.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
