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


  1.  Home
  2. MIDRANGE-L
  3. September 2005

Re: WHAT was IBM THINKING?!?!?, Re: QSYGETPH API

"Shannon O'Donnell" <sodonnell@xxxxxxxxxxxxxxxxx> wrote:
Take one step back on the holier than thou attitude there Doug. Not all of us have gone to V5R3 yet and have therefore had any need to read the memo to users for that release yet.
And indeed, for commercial development, it's usually to one's advantage to stay *several* releases back from current, so that customers aren't forced to upgrade. Up until this week, we didn't even have a V5 box in the building, and the one we now have does not have development tools on it.
Most of the time, unless you use undocumented hacks (and that is NOT the reason why we use MI in all our products, and use tens of thousands of lines of it in QuestView), doing your development a few releases back has no downside.
I wonder if it's possible to subscribe to the memo-to-users series?
And as to what happens when you don't deal with the API change, and use real passwords, it boils down to one of two things, depending on how your application is coded:
1. Starting with V5R3, it will keep everybody out, whether they have the right password or not.
2. Starting with V5R3, it will let everybody in whether they have the right password or not.
The former is an inconvenience; the latter is a security breach at least as bad as the one IBM was apparently trying to close up.
The logical way to make a QSYGETPH call work universally is to try it first the old way, and monitor for the error code V5R3 returns if the extra parameters are missing, and if that error code is returned, then try it the V5R3 way. 

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.