Talk:RETAIN
 | This article has not yet been rated on Wikipedia's content assessment scale. |
joke? (y/n)
- No, this is not a joke. It could probably use a better article, but there really is an internal IBM tool called RETAIN, and it really has been around just about forever. Since so many people are used to using it, it sticks around. One thing it's used for is tracking customer problems. Dave6 19:56, 11 Dec 2004 (UTC)
Historical Information Added (only a limited beginning)
editI have just posted an update to this "stub" article. I was deeply involved in the development of RETAIN and its applications during my IBM career, from 1970 to 1993, so the information provided here is as correct as my memory allows. I was, at one time, designated as "Chief Architect" of the RETAIN system, during a period in which we attempted, with scant success, at replacing its antiquated architecture with a new one. I intend to post some general description of both the genius, and stifling limitations, of the unusual architectural framework upon which RETAIN was built. This framework no doubt stands as the principle impediment that exists to replacing the RETAIN system, now well into its fourth decade. I believe that this history could be very instructive to many people both inside and outside of IBM.
I am now retired from IBM, but still working in the software industry. A full history of RETAIN would require someone else to fill in how the system has been modified in the years since 1993, including its current functions of feeding data to IBM web servers. Still, RETAIN is probably one of the most outstanding examples of a "legacy mainframe system" in existence.
Some updated RETAIN information.
editRETAIN has evolved over the years to become a data server more than a application server. As the needs of the various business units varied it became impossible to build a user application that supported these varied needs. The mainframe 3270 platform that the RETAIN applications runs under became less desirable as the web applications became more prevelant. The architecture evolved to support "services" using a standard well documented API written in JAVA. The RETAIN Toolkit now provides the various client applications in IBM access to the RETAIN data and business processes by executing these services.
The basic architecture of RETAIN has remained unchanged over the years with the occasional update to support new hardware and software features that were not forseen when RETAIN was first developed. Jbarnes4868 (talk) 16:51, 31 August 2011 (UTC)