UniVerse compatibility can be determined by knowing the machine class. If
the machine classification is the same then the object code will be
compatible. Unless the actual run machine has changed, then object code
should remain upwardly compatible.
The object code gets compile-time information buried in it, rather than
run-time behavior. For instance, if a program is compiled in a Pick style
account, with no particular $OPTIONS values specified, then COMMON
allocation and array DIM behave the same way, even if run from an
Information style account. Of course, dimension styles can be controlled
with statements such as $OPTIONS {-}STATIC.DIM.
The machine classification comes from a series of bits describing such
things as byte order, floating point number representation, and the like.
The Digitial RISC chips for instance maintained the same byte order as the
Intel CISC chips, but used a different floating point representation, so
resulted in different machine classifications. Most RISC machines use the
other main byte order from the Intel chips.
The utility, fnuxi, and change the object code for the machine
classification.
A way to check is to use VLIST. VLIST BP FRED, will contain lines like:
Object Level : 5
Machine Type : 11
Mark A. Baldridge
Principal Consultant
North American Lab Services
DB2 Information Management, IBM Software Group
(508) 524-5666
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
