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



On Wed, May 28, 2008 at 3:44 PM, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:
Apps would need to re-certify on every new OS release. That would be
time-consuming and expensive.

Microsoft has been doing that since forever, so it is certainly possible.

At what point does code become 'legacy' and disqualify an application?
To say S36 or S/38 code is legacy is fine & would probably gain
consensus. What about pre-RISC OS/400 code? Pre-V5R1 code? Any code
not compiled under a currently supported-by-IBM OS release? Using the
5250 user interface? Using SNA communications?

I would say the code has to be compiled on a current release
(supported by IBM), and not use any technologies that are no longer
being improved (like 5250 or SNA communications or Twinax).

Or are there still IBM i ISVs that are actively selling 5250 user
interfaces to "new new" customers (That do not have an IBM i system
yet)?

Since we're talking about BPs and not just ISVs, what about a solution
that involves 'legacy' hardware? Say, anything that involves a modem. Or
twinax, non-redundant power, 10K RPM disks, or RAID cards with little to
no cache. FTM non-RAID setups.

Setups without disk protection are already unsupported as of POWER6.
Twinax has been killed for smaller customers, etc. pp.


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.