× 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.



Something weird I just noticed, compiling an updated port of ZLIB using the supplied REXX script:

It seems that the CL front-end programs for the "minizip" utility suite in the package call QtmhGetEnv, in the QZHBCGI *SRVPGM. As shipped, the REXX script expects QZHBCGI to be in QHTTPSRV. On V4R2 (only our V4R2 box has a fully functional C compilation environment), this *SRVPGM is in QTCP, and the QHTTPSRV library doesn't exist, and so the REXX script has to be altered accordingly.

On V4R4 and later, the *SRVPGM is in QHTTPSRV, and NOT in QTCP.

Yet the CL programs compiled under V4R2, and bound to the *SRVPGM in QTCP are somehow successfully finding it in QHTTPSRV. Not being all that familiar with service program binding, I'm not entirely sure what to make of this. On another, related occasion, I found that binding a program to the ZLIB/ZLIB *SRVPGM keeps the program from finding the ZLIB *SRVPGM anywhere else, even if it's in the library list; conversely, neither QTCP nor QHTTPSRV are normally in the library list on any of these boxes.

Can anybody tell me what's going on here? So far, this project has been giving me nothing but weirdness. Weirdness in 9-track Dolby stereo.

I've also posted this query to the BBS of "UZAEMON," the fellow who was good enough to port ZLIB to OS/400.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.