×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
All right, this is just plain weird.
I compile things under V4 all the time, that call APIs only available in
more recent releases, and when they're moved to a box with the required
APIs, they've always worked perfectly.
Until now.
A program (that calls QMHOLHST) compiles just fine under V4 or V6.
Obviously, it can't actually run on the V4 box, but it compiles just
fine there (and I'd prefer having it compiled there, for reasons related
to distribution version control).
If I compile it under V6, and run it under V6, it works just fine.
If I compile it under V4, and run it under V6, it fails. Quietly. The
call to QMHOLHST produces no exceptions, but neither does it produce any
results.
Other than a few details of sizes, the only difference between the
V4-compiled version and the V6-compiled version, at least that shows up
in a DSPPGM, is that the V6-compiled version shows
Teraspace storage enabled PEP . . . . . . . . : *YES
Teraspace storage enabled modules . . . . . . : *ALL
while the V4-compiled version shows
Teraspace storage enabled PEP . . . . . . . . : *NO
Teraspace storage enabled modules . . . . . . : *NONE
Is that it? Is the Teraspace issue what's causing the API to fail?
--
JHHL
midrange.com
