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




Can anybody explain why it is that even though the QZHBCGI
service program moved from QTCP to QHTTPSVR, programs
bound to it specifically in QTCP on a V4R2 box still
somehow manage to find it in QHTTPSVR on V4R4 and later
boxes, even though neither QTCP nor QHTTPSVR is in the
library list?

The library list is irrelevant if you have them bound specifically to QTCP, that should be the only library they attempt to look in.

I suspect that IBM has added code to "fix" this problem by changing the library when you restore the program in order to make it easier for customers to move forward with new releases. (Though, this is only a guess, I never had a V4R2 box, having skipped from V3R2 to V4R5.)


And can someone explain why, contrary to the above
behavior, programs bound to (for example) the ZLIB service
program specifically in the ZLIB library can't find it
anywhere else, even if there IS a ZLIB service program in
the library list?

If it's bound speicifcally to the ZLIB library, that'll be the only place it looks for the file. If you want it to use the *LIBL, then specify *LIBL when you bind it instead of ZLIB. The program will remember that you said *LIBL and use that to find the *SRVPGM from that point on.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.