Following the citation “One does not really know a science until one knows its history“, I’ve decided to provide such information for my area of interest: RTC Enterprise Extensions.
The story started in 2009 and I felt like providing such a recap could help both customers (and potentially business partners/colleagues from the field) when questioning a particular features “introduced at some point of time…. but when actually ?”
It shall be noted that the following information borrows a lot to a previous blog post from Robin Yehle Bobbitt. Robin covered versions 184.108.40.206 to 3.0.1. I’m extending to versions starting from 4.0 up to 4.0.4 versions.
The following picture is somewhat interactive: you could click any circle in it, consult a specific version and then click back on your browser, etc. Hope you enjoy it !
Version 220.127.116.11 (Q4 2009)
- z/OS file agent : made it possible to extract files from the SCM to PDS/Es.
- The mass import tool allowed you to import existing source from data sets into the SCM.
- Rational Build Agent allowed you to create build definitions that call out to existing host build facilities, or submit JCL.
- New build type, Antz build, provided full capabilities to build any z/OS related artifacts (via Apache Ant extensions for the z/OS environment).
- Support for RDz remote projects.
- Collaborative debugging with RDz and the IBM Debug Tool.
- Jazz Gateway for System z (now called REST Gateway) to simplify integration with existing host based SCMs. Allows simple REXX programs or any other exit to programmatically extract information, such as work item status, from the Jazz repository.
Version 3.0 (Q4 2010)
- RTCz : not a a separate product anymore. Instead, a “Developer for IBM Enterprise Platforms” license was required for full access to the z and Power capabilities.
- New “Team Area > Enterprise Extensions” node.
- ISPF client for “green screen” access to common SCM and build functions.
- Dependency build capability (for only building programs as necessary, i.e. based on change).
- Component promotion to move source and build outputs together through the development hierarchy (e.g. Dev->Test->QA->Prod).
- Shiplist-based packaging and deployment to gather your build outputs and deploy them to another runtime location.
Version 3.0.1 (Q2 2011)
- Work-item based promotion, packaging and deployment.
- Preview capabilities for dependency build and promotion.
- HFS file system support in the ISPF client.
Version 4.0 (Q2 2012)
- Sparse loading in ISPF client.
- Enhanced view, compare and conflict resolution in ISPF client.
- IBM i: dependency builds and work-item / component-based promotion and packaging.
- Dependency build report.
- More features around packages.
- Personal deployment.
Version 4.0.1 (Q4 2012)
- Build management in ISPF client.
- Builds and source control: patterns to control the naming of translator outputs.
Version 4.0.3 (Q2 2013)
- Work-item dissociation in the ISPF client.
- View/compare file content in the ISPF client.
- Build subsets configuration and settings.
- Dependency build automatically rebuilds main programs (when one or more statically linked subprograms are updated).
- Dependency build tuning and improved performance.
- ISPF client: pending changes view.
- Dependency build and promotion: usability and simulation.
- Good summary of enterprise features can be found here on jazz.net.
- Citation reference “One does not really know a science ….” (and background information) can be found here
Credit / Acknowledgment
Thanks for Robin Y. Bobbitt for letting me reuse some information contained in her previous blog post.