Putting it all together

I was chatting to Tony Amies, product architect at William Data Systems, about the best way to get information from a mainframe (and about what’s happening on that mainframe) out to someone who has access to a browser. He had a number of nifty techniques that I’d like to share with you.

Assuming you want to get the information from your mainframe to a browser, your first really big decision is do you want to go with two-tier architecture, or do you want to go with three-tier architecture? Tony’s advice was that two-tier was enough.

That leads to the second really important decision to be made, which is where should the processing take place? You’ve got to look at what needs to be done and then make a choice about which platform does that work best on. So, for example, and perhaps quite obviously, if you want to monitor what’s going on with IP, FTP, or EE (Enterprise Extender) on your mainframe, you want that processing to take place on the mainframe. That all seems fairly easy!

But what do you want to do with your results from those different monitors (and indeed any other monitoring software you have running)? Do you want to look like mission control and have a 3270 screen for each monitor that’s running. Now, I remember how impressed visitors used to be when they saw something like that, but if my plan is to get the information to laptop or tablet device running a browser, then I probably need to consolidate the different feeds first. And, again, I want to do that on the mainframe, in the same LPAR (Logical PARtition) that the monitors are running in. It makes sense because much less work has to be done than if I choose to send that data somewhere else for processing.

If you’re familiar with WDS products, you know about their ZEN monitor for their other products. They’re written in Assemble and C and they use a little DLL inside each product that talks to a DLL in ZEN and you can see a nice display of what’s going on – on everything. As a side note, using the DLLs allows the products to talk to each other, so that if the IP monitor spots something, then the IP trace tool can be used to investigate further.

So, using the two-tier architecture, ZEN is logically split into two parts. One part is mainframe friendly and one part is Web friendly. Associated with the Web-friendly part of ZEN are the necessary JavaScript libraries and JQuery libraries, and the usual HTML bits. If you’ve not come across JQuery before, it’s like a lot of clever JavaScript that’s been already written that you can use to make your Web site look very modern. Lots of sites use the jQuery lightBox plugin to show photos.

There’s always a problem with busy Web pages in that lots of information has to come from the server to the browser, resulting in lots of network traffic – and if you’re monitoring your mainframe’s network from a browser there can be even more. So the first technique they’ve used is AJAX (Asynchronous JavaScript and XML), which means that only the parts of the Web page that have changed are sent, the rest of the page stays the same. They also use JSON (JavaScript Object Notation) as a lightweight data-interchange format.

But there’s always an issue with any User Interface and that’s how to separate the actual user interface itself from the business logic behind it. In technical terms, these are known as the view model and the data model. To make this work as effectively as possible, they’re using MVVM (Model View ViewModel), which is a framework or architectural pattern coming originally from Microsoft, but now extended to include JavaScript MVVM. You can get a clearer idea of the sorts of things they’ve done – and perhaps the sorts of things you could do from knockoutjs.com. The site describes itself as “simplifying dynamic javaScript UIs by applying the Model-View-ViewModel (MVVM) pattern”. The WDS developers also familiarized themselves with prototypejs.org, a site describing itself as “a foundation for ambitious web user interfaces”. They go on to say: “Prototype takes the complexity out of client-side web programming”.

For WDS, basically an object is requested from the browser by the user. This goes up to ZEN. Using JSON, a data object comes down and binds with the layout defined in the MVVM skeleton. As a user, you see dynamically updated information in your browser. If one new value affects other values, those other values are automatically update appropriately.

I’m not endorsing WDS’s products, I’m saying that they have very effectively made use of the very latest technology at the browser end to make their product work very efficiently. I’m suggesting that the two-tier architecture with really clever stuff on the browser side is definitely worth taking a look at.

Change is the only constant!

“Any change, even a change for the better, is always accompanied by drawbacks and discomforts.” So said Arnold Bennett the novelist, playwright, critic, and essayist, who lived from 1867 to 1931. Winston Churchill’s take on the subject was: “There is nothing wrong with change, if it is in the right direction”. And Harold Wilson, who was also a British Prime Minister said: “He who rejects change is the architect of decay.”

This week I want to talk a little bit about change – or, more particularly, change management. We’re all so use to change these days we perhaps forget that there are ways of carrying out change in an organization that work – and, of course, ways of performing change that lead simply to chaos! There’s hardly a new leader, whether in government or within an organization that doesn’t feel making a few changes will stamp his or her mark on that organization (or country or whatever).

So what is change management? Well, Wikipedia informs us that: “change management is a structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state. Change management (or change control) is the process during which the changes to a system are implemented in a controlled manner by following a pre-defined framework/model with, to some extent, reasonable modifications.”

In terms of mainframes, you might be looking at products such as the CA Endevor or ChangeMan. The CA Web site tells us: “CA Endevor Software Change Manager automates your entire development process, adapting to specific business requirements while ensuring consistency and complete control, protecting your software assets, and maintaining application integrity”. Integration with IBM Rational Developer for System z improves productivity, accelerates time-to-delivery, and ensures the auditability of all programmer activities. Serena’s Web site says: “Serena ChangeMan ZMF, Change Management for Mainframe Systems, protects your corporate assets – and in the process, lets your programmers get more done in less time. Serena ChangeMan ZMF controls every code change in your mainframe environment. It guarantees source-to-load integrity and ensures that only successfully tested programs make it into production. ChangeMan ZMF reduces maintenance costs and regression errors by moving code through an automated mainframe life-cycle with strict accountability and quality assurance at every step. It can support developer communication and perform regression analyses as part of the most thorough concurrent development available. With ChangeMan ZMF, application code is easier to find, modify, and deploy.”

Many of the change management products that Google can find claim to adopt ITIL (Information Technology Infrastructure Library) models. ITIL, as I’m sure you know, provides a source of best practice for a range of IT tasks. It claims on its Web site to be: “the only consistent and comprehensive documentation of best practice for IT Service Management. Used by thousands of organizations around the world, a whole ITIL philosophy has grown up around the guidance contained within the ITIL books and the supporting professional qualification scheme.”

But suppose you’re looking for a Software Change Management (SCM) product, a version and release management tool for the enterprise, and an application deployment tool not just for the mainframe but also for your distributed platforms. The choice is usually to buy three pieces of software. Interestingly, ISPW – the organization, www.ispw.com – has a product called ISPW that does just that.

On their Web site, they inform us that: “ISPW is a DB2-based all-in-one SCM solution that manages z/OS and distributed applications in one seamless solution. It has a z/OS based server and three thin-client interfaces:

• A traditional 3270 interface for mainframe developers
• A browser for supervisors and approvers
• An Eclipse-based client for mainframe and distributed users.

User friendliness and productivity are ISPW strengths, along with a unique tools integration capability.”

I also discovered at the beginning of the month that ISPW has partnered with RSM to market and support the product in the UK. The press release also says about ISPW (the product that is): “ISPW allows programmers to work from their platform of choice and eliminate many common sources of error in the process. Advantages for complex IT installations include:

• Exposing ALL change components to standard audit and approval processes
• Expedited traceable implementation and roll-back procedures
• Automatic inclusion in corporate disaster recovery processes
• Improved project management through early conflict resolution and comprehensive visibility
• Reduced cost, via time and effort savings, without the need to retrain or modify procedures.”

Which all seems to make ISPW an interesting product, and well worth a second look.