IBM dev ops serves up fresh IBM z/OS Explorer Aqua
JoeWinchester 110000DQA0 Comments (3) Visits (3529)
IBM Explorer for z/OS Aqua - read more about it here - and start to use it from our download site. To learn more about the new Remote System Explorer perspective read about its capabilities here. There is a lot you can do (as a teaser here is a rich JCL editor over data sets ) that is now part of the z/OS Explorer (and its family of products that includes CICS Explorer).
Sorry for the "read all about it intro" that is links to other material, but I sort of wanted to get folks to look around some of the other blogs and sites that IBM is using to deliver great content for System z tooling, and I wanted to give a shout out to the IBM z/OS Explorer Aqua - a release that I was lucky enough to work on last year and is proving popular with customers. One thing we did for this release was talk to customers, not just after we GA'd the release (which we now have done) but beforehand to do some design thinking, ask them what their problems were, and see what we could do to help.
One of the things that has frustrated IBM's customers on System z is that there are a number of different tools we provide, each with their own capabilities (CICS Explorer to administer and work with CICS regions and CICS plexes - Debug Tool for developers to set breakpoints and step through running code as well as perform code coverage, ...). Many of these tools were developed independently of each other within IBM, each to serve a particular purpose, yet it became apparently that customers saw value in aggregating the tools together for scenarios such as "create a debug profile against a CICS transaction so I can debug its programs". The Eclipse tooling framework that underpins many of IBMs tools allows plugins to be installed into the same environment as long as the plugins follow certain rules. The rules are that they sit nicely on the software stack version that the underlying platform is based on, and they don't introduce conflicting plugins to the shell that will collide with the same plugins, but different versions, from other plugins.
Solving this problem became the focus of the IBM Explorer for z/OS Aqua, so named to convey the fact that it is an aggregation and grouping of compatible tools, similar to how some operating system vendors use words with sequential alphabet characters for their releases. We have a single composite update site URL
We did have a composite site beforehand, but instead of stitching together different sites and products created independently that would move independently and often intr
We have a number of other ideas we're working on to move our tooling forward so it can better serve the needs of z/OS system programmers and developers. What we'd really like to do is hear from folks who have ideas and input, what we are doing right, what we are doing wrong, and what pain points people are finding in their organizations preventing them from moving forward. We have design partnership programs where we can come and chat to people face to face, get folks on phone calls, provide drops of blueprints and early software, and hopefully make sure that each time we drop new publicly available software it is a better fit and finish.
Please let us know what you like and don't like about IBM Explorer for z/OS Aqua, as well as where you'd like us to take application developer and system programmer tooling in the future, and help us to help all the great System z shops out there. That way we can build the future together.