VisualAge TeamConnection: Difference between revisions
Created page with "right A Software Configuration Management (SMC) client and server product from IBM, server functionality was only available for OS/2 but client support wa..." |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Image:VA.GIF|right]] | [[Image:VA.GIF|right]] | ||
A [[Software Configuration Management]] (SMC) client and server product from IBM, server functionality was only available for OS/2 but client support was also available for [[Microsoft Windows]] NT, [[Solaris]], [[HP-UX]] and [[AIX]], and from version 3 and onwards the system also had a web interface that allowed a degree of platform neutrality. | A [[Software Configuration Management]] (SMC) client and server product from IBM, server functionality was only available for OS/2 but client support was also available for [[Microsoft Windows]] NT, [[Solaris]], [[HP-UX]] and [[AIX]], and from version 3 and onwards the system also had a web interface that allowed a degree of platform neutrality. The product was quite novel when it was first introduced, while it had support for legacy code from systems and languages such as [[COBOL]], [[PL/I]] and [[IMS]] it was built around an object-oriented paradigm that mated extremely well with languages such as [[Smalltalk]], [[C++]] and [[Java]]. | ||
<!-- | <!-- | ||
| Line 14: | Line 14: | ||
Inclusion of DataDictionary in TeamConnection allows users to leverage and extend legacy assets from PL/I, COBOL and IMS | Inclusion of DataDictionary in TeamConnection allows users to leverage and extend legacy assets from PL/I, COBOL and IMS | ||
--> | --> | ||
==Versions== | ==Versions== | ||
* VisualAge TeamConnection Enterprise Server 3.06 | * VisualAge TeamConnection Enterprise Server 3.06 | ||
Revision as of 07:51, 7 February 2016
A Software Configuration Management (SMC) client and server product from IBM, server functionality was only available for OS/2 but client support was also available for Microsoft Windows NT, Solaris, HP-UX and AIX, and from version 3 and onwards the system also had a web interface that allowed a degree of platform neutrality. The product was quite novel when it was first introduced, while it had support for legacy code from systems and languages such as COBOL, PL/I and IMS it was built around an object-oriented paradigm that mated extremely well with languages such as Smalltalk, C++ and Java.
Versions
- VisualAge TeamConnection Enterprise Server 3.06
- Prerequisites (Server)
- IBM OS/2 4 or higher
- 256MB of memory
- Prerequisites (Client)
- IBM OS/2 Warp 4.0
- 64MB of Memory
- Microsoft Windows NT 4.0 SP4 or higher
- 64MB of Memory
- IBM AIX 4.2.1 or higher
- 256MB of Memory
- HP-UX 10.20 or higher
- 256MB of Memory
- SunSoft Solaris 2.5.1 or higher
- 256MB of Memory
Links
Publications
- VisualAge TeamConnection Enterprise Server - Keeping Your Build Process on a Short Leash - IBM Redbook SG245260 - 1998
License and availability
- Discontinued commercial software.