REXX (REXX or Rexx) has been around since the early 80s. I first came across it in the mid-80s, when sites were beginning to use it with VM and CMS as a powerful replacement for EXECs. I thought it would be interesting to take a look at this venerable, but still powerful tool in the system programmer’s toolkit.
Amazingly, REXX wasn’t written as an IBM project, it was written by IBMer Mike Cowlishaw in his own time in Assembler. It was designed as a macro or scripting language and was based on PL/I. It first saw the light of day at SHARE in 1981, and became a full IBM product in 1982.
IBM has implemented REXX on VM, MVS, VSE, CICS, AIX, and AS/400s, and on subsequent products. There are even versions available for Java, Windows, and Linux. A compiled version for CMS became available in 1987 and was written by Lundin and Woodruff.
REXX was so popular that versions were developed for other platforms, including Unix, Solaris, Apple Mac OS X, OpenVMS, and lots of others. There’s also NetRexx, which compiles to Java byte code, and ObjectREXX, which is an object-oriented version of REXX.
In 2005, Open Object Rexx (ooRexx) was announced. It has a Windows Script Host (WSH) scripting engine. So code can be written for Windows. It also has a command line Rexx interpreter.
Those of you who use the ZEN family of products from William Data Systems will be interested to know that ZEN Rexx, formerly available with ZEN’s AUTOMATION component, has now been made available to all WDS customers through the base ZEN component.
ZEN’s Rexx support comprises: a ZEN Rexx Interface; a ZEN Rexx Function Pack; and a command interface. The ZEN Rexx Interface provides support for running Rexx programs under ZEN in a similar way to running Rexx programs under TSO or Netview. You can also run ZEN Rexx programs using a Modify (F) command from the z/OS console. Under ZEN, Rexx programs can be run from the ZEN Profile at initialization time, from the Command Facility and System Log panels, or from a user-defined ZEN menu item.
The ZEN Rexx Function Pack provides extensions to standard REXX through which users can communicate directly with ZEN. The command interface enables users to issue commands from their ZEN Rexx programs and get any responses back. This means that commands provided by their WDS ZEN components can be issued from a ZEN Rexx program, as well as any z/OS, VTAM, or other product command.
REXX may have had humble beginnings, with Mike Cowlishaw working in his own time, but it has gone on to conquer the world (metaphorically) and is now in regular use, in different incarnations, on just about every platform imaginable, including your smartphone and tablet.
Showing posts with label ZEN. Show all posts
Showing posts with label ZEN. Show all posts
Sunday, 9 March 2014
Sunday, 11 December 2011
Sunk without trace
There was a time when using the trace facility was really the final strategy. You’d perhaps have tried everything else to find what was going wrong first. And when nothing seemed to have worked, you’d equip yourself with all the necessary manuals – and that could be quite a few – and run the trace and start the hard job of interpreting the results. And then try to fix the problem. Those days are long gone thanks to more modern software tools, but, to many people, the memories linger on!
I recently bumped into William Data Systems’ Tony Amies, who took the time to show me some of the things he was working on. And one of those things was making trace much, much, more user friendly.
Tony showed me WDS’s ZEN product, which, as you may know, allows lots of network monitoring information to be collated and viewed from anywhere using a browser. Information can appear as coloured boxes, which once you clicked on them display more-and-more information in a clever drill-down manner. Fairly quickly, you can identify the component that has exceeded some predetermined threshold.
WDS has a number of products in the ZEN family and you can use buttons on the browser to switch between them – giving you information about different aspects of performance. ZIM the ZEN IP MONITOR can detect error conditions, then ZEN TRACE and SOLVE (ZTS – which used to be called EXIGENCE) can be used to start, stop, and view traces. Now that has got to be so much easier than in the Old Days!
Tony showed how a TCP trace could be carried out in seconds, explaining that there were lots of commands embedded in it. Tony explained how network tracing can be so difficult. For example, using Enterprise Extender, which allows SNA applications to run over TCP networks, results in encapsulated messages. Tony demonstrated software that was able to look inside the message to see what was there – in terms of different types of header. He then explained how this works with FMH5, UDP, IP, APPN, HPR, and more. He explained that sites using the Cisco load balancing GRE tunnelling protocol can also be opened to see the true header for the message. All very clever stuff – and no manuals in sight.
In fact, on a number of occasions a right mouse click on some information in the display would produce a pop-up box explaining exactly what some term or other actually meant. So there was no need for any manuals. The display could show delays, highlight response time problems, and the TCP window size.
Tony also showed me a piece of software that drew a diagram of a Sysplex Distributor – which shows the IP addresses and links on a mainframe system. The software also highlighted where there were issues. And, like the rest of the software we looked at, you could drill down to find exactly where any problem were. In fact, Tony was sure that this would allow customers to identify potential issues before their users did. Behind the scenes, information from netstat and other commands were being used to drive the display.
We talked about customers being able to build business service views of what was going on their system and how useful that would be for each of their customers. That kind of bespoke requirement wasn’t something that Tony could necessarily build into the software, but all it requires is a knowledge of REXX to make it happen. And most z/OS sites have at least one person who code in REXX.
Lastly, we talked about problem resolution when you have two or more systems that don’t seem to be talking to each other. Currently, you need to log into each system and run traces to find out which of the systems has the problem. Tony plans to implement a ‘grouptrace’ feature that allows the user to tell the software to run a trace on these two (or more) systems. The results will come back from both systems and be visible from the browser. The results will be displayed in timestamp order and it will be possible to see on which of the systems the problem is. As easy that.
Too often we’d be sunk without a trace facility. Now we have an example of a way to be able to use trace across multiple systems and simply click to drill down to identify the problem.
I recently bumped into William Data Systems’ Tony Amies, who took the time to show me some of the things he was working on. And one of those things was making trace much, much, more user friendly.
Tony showed me WDS’s ZEN product, which, as you may know, allows lots of network monitoring information to be collated and viewed from anywhere using a browser. Information can appear as coloured boxes, which once you clicked on them display more-and-more information in a clever drill-down manner. Fairly quickly, you can identify the component that has exceeded some predetermined threshold.
WDS has a number of products in the ZEN family and you can use buttons on the browser to switch between them – giving you information about different aspects of performance. ZIM the ZEN IP MONITOR can detect error conditions, then ZEN TRACE and SOLVE (ZTS – which used to be called EXIGENCE) can be used to start, stop, and view traces. Now that has got to be so much easier than in the Old Days!
Tony showed how a TCP trace could be carried out in seconds, explaining that there were lots of commands embedded in it. Tony explained how network tracing can be so difficult. For example, using Enterprise Extender, which allows SNA applications to run over TCP networks, results in encapsulated messages. Tony demonstrated software that was able to look inside the message to see what was there – in terms of different types of header. He then explained how this works with FMH5, UDP, IP, APPN, HPR, and more. He explained that sites using the Cisco load balancing GRE tunnelling protocol can also be opened to see the true header for the message. All very clever stuff – and no manuals in sight.
In fact, on a number of occasions a right mouse click on some information in the display would produce a pop-up box explaining exactly what some term or other actually meant. So there was no need for any manuals. The display could show delays, highlight response time problems, and the TCP window size.
Tony also showed me a piece of software that drew a diagram of a Sysplex Distributor – which shows the IP addresses and links on a mainframe system. The software also highlighted where there were issues. And, like the rest of the software we looked at, you could drill down to find exactly where any problem were. In fact, Tony was sure that this would allow customers to identify potential issues before their users did. Behind the scenes, information from netstat and other commands were being used to drive the display.
We talked about customers being able to build business service views of what was going on their system and how useful that would be for each of their customers. That kind of bespoke requirement wasn’t something that Tony could necessarily build into the software, but all it requires is a knowledge of REXX to make it happen. And most z/OS sites have at least one person who code in REXX.
Lastly, we talked about problem resolution when you have two or more systems that don’t seem to be talking to each other. Currently, you need to log into each system and run traces to find out which of the systems has the problem. Tony plans to implement a ‘grouptrace’ feature that allows the user to tell the software to run a trace on these two (or more) systems. The results will come back from both systems and be visible from the browser. The results will be displayed in timestamp order and it will be possible to see on which of the systems the problem is. As easy that.
Too often we’d be sunk without a trace facility. Now we have an example of a way to be able to use trace across multiple systems and simply click to drill down to identify the problem.
Sunday, 8 May 2011
Mainframe chatter
Mark Lillycrop, Director of Arcati Ltd, and I were asked to take part in CA’s May Mainframe Madness. We were part of a ‘Scheduled Chat’ in their ‘House of Mainframe’ section on 5 May. It was enjoyable chatting to other mainframe professionals and it was very interesting the direction the conversation took.
Clearly, there were two main strands to the conversation. One was the difficulty of convincing (converting?) non-mainframers of the potential of the mainframe. The second was the success of z/Linux at installations.
Looking at z/Linux success first, Murray Theriault told us: “I think what sold it for me was the idea that I could put up 100 z/Linux machines on the same box and have a very small footprint, not to mention no power costs”. Similarly, Marie Kennard added: “Same here – the app we’re putting onto zLinux currently runs on dozens of boxes, most of which are reaching EOL and needed replacing”. Someone else reminded the group about Aliantz in Australia, saying that they’d “flipped their whole farm to z/Linux in a weekend with little to no outtage”. This led CA’s Reg Harbeck to comment: “zLinux seems to be taking over a decade to become an overnight sucess...”
So it appears that z/Linux is making headway in those sites that already have a mainframe and Linux servers. And it’s definitely the case that the arguments for doing so are irrefutable. Moving some of the applications or even all of them from other Linux platforms is a positive step and the sites doing so are going to see huge benefits in terms of performance, reliability, and, of course, cost savings both in man-power and outages.
But even the success stories seem to be the result of a battle between mainframers and management whose model of computing and whose expectations are the result of using Microsoft Windows. A lot of the hour long discussion was spent on how to get managers in organizations that have mainframes to appreciate what they have, and to understand how to exploit the mainframes potential. The truth is that there’s an even bigger battle to be fought and that’s to get IT people and IT managers at non-mainframe sites to appreciate the opportunities that a mainframe brings.
During the discussion it was said that ‘good news’ mainframe stories don’t make much of an appearance in the IT press. If they did, that would be one way that people would get to hear about mainframes. Mark suggested that many people view mainframes as: “Old, expensive, and your dad’s technology”. And yet, anyone who takes money out of an ATM (hole-in-the-wall) machine is probably linking to IMS on a mainframe. They just don’t know it. The press were not only blamed for sins of omission, but also sins of commission – for printing the same old stories containing the same old wrong assumptions about mainframes.
I reminded the chat room about William Data Systems ZEN product family and how users can control their network from the latest iPad gizmo, or get reports on their smartphones about what’s going on on their network. And, obviously, there was a lot of talk about cloud computing and mainframes – and how they go together like “peas and carrots” (well Forest Gump would have said that if he’d been logged in!). The point is that mainframes aren’t “your dad’s technology”, they very much embrace the very latest technologies and do it in a way that is secure and comes with all the benefits of years of successful operation in banks and airlines, etc.
I did think to run a competition, at this point but I don’t have a prize to give out. However, I would be interested in hearing people’s ideas of how managers and staff at mainframe sites and the rest of the IT world who aren’t mainframers can be convinced of the importance and proven-reliability of mainframes. You can e-mail me at trevor@itech-ed.com with your comments and I’ll put them together in a future blog.
Other topics that we discussed during our hour included the importance of virtual meetings with the current financial constraints when organizations are less-and-less keen to fund travel/hotels/food etc for people to attend. We looked at green computing and how this issue will most-likely grow in importance with future regulation. The fact that the word ‘legacy’ is actually a compliment. (How many of you have printers that don’t work with Vista or Windows 7, and just have to live with it?) And we suggested names for the next version of z/OS including z/2020 and z/Cloud.
All-in-all it was an enjoyable ‘Scheduled Chat’ in the ‘House of Mainframe’. Good luck CA for the rest of the month of mainframe madness.
Clearly, there were two main strands to the conversation. One was the difficulty of convincing (converting?) non-mainframers of the potential of the mainframe. The second was the success of z/Linux at installations.
Looking at z/Linux success first, Murray Theriault told us: “I think what sold it for me was the idea that I could put up 100 z/Linux machines on the same box and have a very small footprint, not to mention no power costs”. Similarly, Marie Kennard added: “Same here – the app we’re putting onto zLinux currently runs on dozens of boxes, most of which are reaching EOL and needed replacing”. Someone else reminded the group about Aliantz in Australia, saying that they’d “flipped their whole farm to z/Linux in a weekend with little to no outtage”. This led CA’s Reg Harbeck to comment: “zLinux seems to be taking over a decade to become an overnight sucess...”
So it appears that z/Linux is making headway in those sites that already have a mainframe and Linux servers. And it’s definitely the case that the arguments for doing so are irrefutable. Moving some of the applications or even all of them from other Linux platforms is a positive step and the sites doing so are going to see huge benefits in terms of performance, reliability, and, of course, cost savings both in man-power and outages.
But even the success stories seem to be the result of a battle between mainframers and management whose model of computing and whose expectations are the result of using Microsoft Windows. A lot of the hour long discussion was spent on how to get managers in organizations that have mainframes to appreciate what they have, and to understand how to exploit the mainframes potential. The truth is that there’s an even bigger battle to be fought and that’s to get IT people and IT managers at non-mainframe sites to appreciate the opportunities that a mainframe brings.
During the discussion it was said that ‘good news’ mainframe stories don’t make much of an appearance in the IT press. If they did, that would be one way that people would get to hear about mainframes. Mark suggested that many people view mainframes as: “Old, expensive, and your dad’s technology”. And yet, anyone who takes money out of an ATM (hole-in-the-wall) machine is probably linking to IMS on a mainframe. They just don’t know it. The press were not only blamed for sins of omission, but also sins of commission – for printing the same old stories containing the same old wrong assumptions about mainframes.
I reminded the chat room about William Data Systems ZEN product family and how users can control their network from the latest iPad gizmo, or get reports on their smartphones about what’s going on on their network. And, obviously, there was a lot of talk about cloud computing and mainframes – and how they go together like “peas and carrots” (well Forest Gump would have said that if he’d been logged in!). The point is that mainframes aren’t “your dad’s technology”, they very much embrace the very latest technologies and do it in a way that is secure and comes with all the benefits of years of successful operation in banks and airlines, etc.
I did think to run a competition, at this point but I don’t have a prize to give out. However, I would be interested in hearing people’s ideas of how managers and staff at mainframe sites and the rest of the IT world who aren’t mainframers can be convinced of the importance and proven-reliability of mainframes. You can e-mail me at trevor@itech-ed.com with your comments and I’ll put them together in a future blog.
Other topics that we discussed during our hour included the importance of virtual meetings with the current financial constraints when organizations are less-and-less keen to fund travel/hotels/food etc for people to attend. We looked at green computing and how this issue will most-likely grow in importance with future regulation. The fact that the word ‘legacy’ is actually a compliment. (How many of you have printers that don’t work with Vista or Windows 7, and just have to live with it?) And we suggested names for the next version of z/OS including z/2020 and z/Cloud.
All-in-all it was an enjoyable ‘Scheduled Chat’ in the ‘House of Mainframe’. Good luck CA for the rest of the month of mainframe madness.
Sunday, 24 April 2011
Network management issues
I want to know what’s going on on my network – what do I do? Well this seemingly simple question has a complicated answer, which is historical and all to do with the separate worlds of the mainframes and everyone else coming together to give us our current complicated environment. Just to summarize, mainframes used SNA and VTAM to communicate and everyone else used TCP/IP. Sometime in the 1990s, all this came together. In addition, we now have people on iPads and smartphones using our networks – in fact, we can have people on iPads and smartphones controlling our networks!
So, in terms of software, what are our choices for network management?
IBM has Tivoli OMEGAMON XE for mainframe networks, which allows you to monitor VTAM and TCP/IP networks and identify problems within those networks.
CA has its CA NetMaster Network Management for TCP IP and CA NetMaster Network Management for SNA products, which allow users to “proactively manage” their network. And there are a number of other more specialized products including CA NSM NetMaster Option, which lets you “manage your mainframe networks from CA Unicenter Network and Systems Management”.
SDS has Vital Signs for IP and Vital Signs for VTAM, which are both monitoring software.
William Data Systems has a whole range of products including ZEN OSA MONITOR for OSA performance monitoring and management, ZEN IP MONITOR (IMPLEX) for IP performance monitoring and management, ZEN EE MONITOR (FERRET) for APPN/HPR and EE monitoring and management, ZEN TRACE and SOLVE (EXIGENCE) for network problem determination, ZEN FTP CONTROL (FTPALERT) for audited FTP monitoring and management, ZEN EE SECURITY (APIAS) for secure EE deployment across any network, and ZEN AUTOMATION for automating network and operational tasks.
In fact, William Data Systems has just release Version 4.7 of ZEN TRACE and SOLVE, which includes more customer-suggested z/OS network tracing and solution capabilities to help busy z/OS network support people do more in less time – they claim.
If you are plagued by mainframe network issues, you may well be interested in the new features they’ve incorporated into ZEN TRACE and SOLVE V4.7, including:
So, in terms of software, what are our choices for network management?
IBM has Tivoli OMEGAMON XE for mainframe networks, which allows you to monitor VTAM and TCP/IP networks and identify problems within those networks.
CA has its CA NetMaster Network Management for TCP IP and CA NetMaster Network Management for SNA products, which allow users to “proactively manage” their network. And there are a number of other more specialized products including CA NSM NetMaster Option, which lets you “manage your mainframe networks from CA Unicenter Network and Systems Management”.
SDS has Vital Signs for IP and Vital Signs for VTAM, which are both monitoring software.
William Data Systems has a whole range of products including ZEN OSA MONITOR for OSA performance monitoring and management, ZEN IP MONITOR (IMPLEX) for IP performance monitoring and management, ZEN EE MONITOR (FERRET) for APPN/HPR and EE monitoring and management, ZEN TRACE and SOLVE (EXIGENCE) for network problem determination, ZEN FTP CONTROL (FTPALERT) for audited FTP monitoring and management, ZEN EE SECURITY (APIAS) for secure EE deployment across any network, and ZEN AUTOMATION for automating network and operational tasks.
In fact, William Data Systems has just release Version 4.7 of ZEN TRACE and SOLVE, which includes more customer-suggested z/OS network tracing and solution capabilities to help busy z/OS network support people do more in less time – they claim.
If you are plagued by mainframe network issues, you may well be interested in the new features they’ve incorporated into ZEN TRACE and SOLVE V4.7, including:
- The new “Peek” function, which provides in-flight viewing of active IP traces. This means that it is now possible to view an active trace while it is still running, tracking its progress ‘in-flight', and then stopping it when the condition being sought in the trace is detected. This can save considerable CPU costs and user time.
- Traces originally captured in OSAENTA, libpcap, or Sniffer format can now be imported into ZTS. This can make network problem solving both faster and easier.
- As well as being able to accept commands from the operator console, ZEN TRACE and SOLVE now adds the ability to issue any commands (including ZTS commands) from JCL. When combined with the capabilities provided by the new import features, this enables different trace formats to be automatically imported into ZTS for analysis. This greatly simplifies the whole network problem solving process.
- Tracing of IPv6 is now faster and easier with the provision of improved Flow display text descriptions for recognizable packet contents, as well as the capability to search using IPv6 format addresses.
- Tracing packets in large Sysplex environments is inherently complex, but ZEN TRACE and SOLVE v4.7 now makes it easier by providing improved facilities for expanding encapsulated data used by Sysplex protocols such as GRE and VIPA Route. Being able to view and expand encapsulated payload data is a vital tool for rapid problem diagnosis in large Enterprise networks.
If you’re finding network management is an issue, it might well be worth a look.
Sunday, 27 February 2011
Blending mainframe technology with Apple, Blackberry, and Android – makes you think!
I don’t know whether you’re going to be at the SHARE conference in Anaheim (California) from 27 February to 4 March, but one of the interesting things to see is the William Data Systems stand (booth 211).
They are showing how their ZEN z/OS network management suite of product integrates with popular smart phone technology – Apple, Blackberry, and Android. What you’ll see is ZEN monitoring z/OS networks and then reporting the results to a mobile device. The user can then evaluate what’s happening on the mainframe and take appropriate action immediately. As a consequence, z/OS support staff can get on with their lives and be out and about, but still be able to monitor their mainframes and react to alerts.
The company say that this mobile technology extends ZEN’s whistle-blower ability to monitor SyslogD, filter the results by many criteria, launch automation commands or REXX procedures, and transmit the important alerts to mobile devices, all in real-time. I think this sounds pretty impressive and I was lucky enough to have a demonstration of the technology a few ago.
Originally the technology was restricted to iPhone and iPad users, but now it’s extended to the other ‘smart’ technologies that organizations use.
Their press release mentions SyslogD. In fact, this is probably the most useful resource that many IT departments ignore or only refer to long after they should. Having this kind of information on your phone seems almost futuristic.
Anyway, if you are at Anaheim, take a look.
On a completely different topic… I was pleased to receive the following e-mail during the week:
“On behalf of IBM, it is with great pleasure to recognize you as a 2011 IBM Information Champion. We would like to thank you for your leadership and contributions to the Data Management community. You continue to be among a very small group to be chosen for this recognition. Congratulations.”
This makes three years in a row.
If you’re interested, you can find out more about the Information Champion programme here (www-01.ibm.com/software/data/champion/)
They are showing how their ZEN z/OS network management suite of product integrates with popular smart phone technology – Apple, Blackberry, and Android. What you’ll see is ZEN monitoring z/OS networks and then reporting the results to a mobile device. The user can then evaluate what’s happening on the mainframe and take appropriate action immediately. As a consequence, z/OS support staff can get on with their lives and be out and about, but still be able to monitor their mainframes and react to alerts.
The company say that this mobile technology extends ZEN’s whistle-blower ability to monitor SyslogD, filter the results by many criteria, launch automation commands or REXX procedures, and transmit the important alerts to mobile devices, all in real-time. I think this sounds pretty impressive and I was lucky enough to have a demonstration of the technology a few ago.
Originally the technology was restricted to iPhone and iPad users, but now it’s extended to the other ‘smart’ technologies that organizations use.
Their press release mentions SyslogD. In fact, this is probably the most useful resource that many IT departments ignore or only refer to long after they should. Having this kind of information on your phone seems almost futuristic.
Anyway, if you are at Anaheim, take a look.
On a completely different topic… I was pleased to receive the following e-mail during the week:
“On behalf of IBM, it is with great pleasure to recognize you as a 2011 IBM Information Champion. We would like to thank you for your leadership and contributions to the Data Management community. You continue to be among a very small group to be chosen for this recognition. Congratulations.”
This makes three years in a row.
If you’re interested, you can find out more about the Information Champion programme here (www-01.ibm.com/software/data/champion/)
Sunday, 28 November 2010
Who cares about SyslogD on a mainframe?
Unix System Services (USS) on a mainframe basically allows Unix applications to run and communicate. Running under USS is Syslog Daemon or SyslogD. This is an important system component because it’s part of z/OS’s Intrusion Detection and prevention Services (IDS). SyslogD receives detailed event messages, such as security violations, as well as messages from many other communications services such as FTP and AT-TLS, plus messages from routers, switches, and other network-based devices.
So, in the event of a hacker trying to log-on to your mainframe, how would you know? And when would you know? Surprisingly, many sites appear to ignore the information written to SyslogD completely! While other sites look at what has happened, perhaps a minute ago, perhaps an hour ago, perhaps yesterday!
What you probably need is some way to be alerted about what’s happening now. And, as this is 2010, you probably want the alert to come through to your mobile phone. And you then want to be able to jump on any browser, see where the trouble lies, and fix it. What are the chances of there being software that does that?
Well, let me confirm that it does exist and I’ve seen it.
WDS (www.willdata.com) has rather nice mainframe-based HTTP server software that front-ends their mainframe monitoring products. It’s called ZEN and it allows users of their products to access information through a browser – almost any browser. Their products are called ZEN EE Security, ZEN IP Monitor, or similar, but are perhaps better known by their old names of Ferret, Implex, etc. The products can monitor APPN, EE, FTP, IP, SNA, OSA, and USS. Each of these programs effectively has a DLL that allows them to plug in to the HTTP server. This can then respond to messages by ignoring them, sending a command, running a REXX EXEC, or sending an e-mail. It’s completely automated and configurable to what the users want. ZEN can also run utilities such as PING, TRACEROUTE, and NSLOOKUP commands. And, in addition to input from WDS’s programs and SyslogD, it also receives network messages and ECMS console contents.
For the end user, working from a browser, windows can be opened and closed, resized, refreshed, whatever. The windows can show number data and regularly-updated graphical displays. In fact, a variety of different graphs can be monitored in different windows at the same time, allowing end-users to monitor what’s going on in real-time. The drawing of the graphs is all handled in JavaScript (JSON, in fact), and AJAX is used so only the parts of the display that change are sent from the server to the browser, which speeds up communication considerably. It’s possible to drill-down through the alert information on screen, for example, to one particular type of alert, on a particular day, during a particular time range.
Now, the type of display I want on, say, a 17 inch laptop screen is not the same as on a 3 inch smart phone screen. You might think this would be a bit of a fly in the ointment. The truth is that WDS has a solution to even this problem.
Looking to the future, what else could we ask them to do with their excellent end-user interface? Might it not make sense to automate the monitoring of other things and use the browser-based interface to see what’s going on? Is there a way this could be done for, say, other Linux boxes? We’ll have to wait and see.
But whatever software monitor you choose, and however you choose to display it, it makes sense to ensure that SyslogD is not being ignored.
So, in the event of a hacker trying to log-on to your mainframe, how would you know? And when would you know? Surprisingly, many sites appear to ignore the information written to SyslogD completely! While other sites look at what has happened, perhaps a minute ago, perhaps an hour ago, perhaps yesterday!
What you probably need is some way to be alerted about what’s happening now. And, as this is 2010, you probably want the alert to come through to your mobile phone. And you then want to be able to jump on any browser, see where the trouble lies, and fix it. What are the chances of there being software that does that?
Well, let me confirm that it does exist and I’ve seen it.
WDS (www.willdata.com) has rather nice mainframe-based HTTP server software that front-ends their mainframe monitoring products. It’s called ZEN and it allows users of their products to access information through a browser – almost any browser. Their products are called ZEN EE Security, ZEN IP Monitor, or similar, but are perhaps better known by their old names of Ferret, Implex, etc. The products can monitor APPN, EE, FTP, IP, SNA, OSA, and USS. Each of these programs effectively has a DLL that allows them to plug in to the HTTP server. This can then respond to messages by ignoring them, sending a command, running a REXX EXEC, or sending an e-mail. It’s completely automated and configurable to what the users want. ZEN can also run utilities such as PING, TRACEROUTE, and NSLOOKUP commands. And, in addition to input from WDS’s programs and SyslogD, it also receives network messages and ECMS console contents.
For the end user, working from a browser, windows can be opened and closed, resized, refreshed, whatever. The windows can show number data and regularly-updated graphical displays. In fact, a variety of different graphs can be monitored in different windows at the same time, allowing end-users to monitor what’s going on in real-time. The drawing of the graphs is all handled in JavaScript (JSON, in fact), and AJAX is used so only the parts of the display that change are sent from the server to the browser, which speeds up communication considerably. It’s possible to drill-down through the alert information on screen, for example, to one particular type of alert, on a particular day, during a particular time range.
Now, the type of display I want on, say, a 17 inch laptop screen is not the same as on a 3 inch smart phone screen. You might think this would be a bit of a fly in the ointment. The truth is that WDS has a solution to even this problem.
Looking to the future, what else could we ask them to do with their excellent end-user interface? Might it not make sense to automate the monitoring of other things and use the browser-based interface to see what’s going on? Is there a way this could be done for, say, other Linux boxes? We’ll have to wait and see.
But whatever software monitor you choose, and however you choose to display it, it makes sense to ensure that SyslogD is not being ignored.
Sunday, 10 October 2010
Managing mainframes from your phone
William Data Systems has come up with a clever way of managing your mainframe network from an iPhone. Now as soon as you see the word iPhone, you probably think it’s an app and you’re going to have to get all your users synchronizing with iTunes before they can use it or update it. The truth is, it’s a much cleverer idea than that!
Let’s start at the beginning, WDS (William Data Systems) has a z/OS network management suite called ZEN, which has a number of really useful components that you can find out more about from their Web site (www.willdata.com). Their customers wanted an easy way to keep up-to-date with what was happening with their networks. And one thing everyone has these days is a mobile (cell) phone – so why not come up with a way of monitoring the network from your phone?
What WDS did, was to utilize the browser on iPhones – Safari, the same one that comes as standard on Macs – and allow users to monitor and manage their mainframe networks from there.
Now because Safari is an integral part of the iPhone, the technology works for all iPhone users. As I said at the beginning, there’s no problem of resynchronizing every user by getting them to plug their phones into iTunes. There’s no fuss about accessing the App Store. It’s all there on the browser.
As more-and-more companies are asking for z/OS network monitoring and management to be done remotely when needed using a single mobile device that support people would be carrying with them, this solution seems to tick all the boxes. If a problem is found, then the techie can find a laptop and fix it, or use the phone to call the service centre and get someone there to fix it. Either way, the problem is solved, perhaps before users have begun to notice. Interestingly, the solution can be used from an iPad. In that case, the screen is big enough for a techie to actually use instead of a laptop – and solve the problem immediately.
What if your organization doesn’t use iPhones? What if you’ve rolled out Blackberrys? Well in that case, WDS has a solution available. If your organization uses Symbian or Android (or anything else), then WDS are developing a solution for your smart phone right now.
It may all seems like something from a 1990s sci fi film, but monitoring your z/OS network from your mobile phone is a solution that’s available now.
And finally, as a mainframe professional, I am hoping that you will be willing to complete the annual user survey at www.arcati.com/usersurvey11. If the company you work for is a vendor, consultant, or service provider, then please ensure their information is included in the vendor information form at www.arcati.com/vendorentry.
Let’s start at the beginning, WDS (William Data Systems) has a z/OS network management suite called ZEN, which has a number of really useful components that you can find out more about from their Web site (www.willdata.com). Their customers wanted an easy way to keep up-to-date with what was happening with their networks. And one thing everyone has these days is a mobile (cell) phone – so why not come up with a way of monitoring the network from your phone?
What WDS did, was to utilize the browser on iPhones – Safari, the same one that comes as standard on Macs – and allow users to monitor and manage their mainframe networks from there.
Now because Safari is an integral part of the iPhone, the technology works for all iPhone users. As I said at the beginning, there’s no problem of resynchronizing every user by getting them to plug their phones into iTunes. There’s no fuss about accessing the App Store. It’s all there on the browser.
As more-and-more companies are asking for z/OS network monitoring and management to be done remotely when needed using a single mobile device that support people would be carrying with them, this solution seems to tick all the boxes. If a problem is found, then the techie can find a laptop and fix it, or use the phone to call the service centre and get someone there to fix it. Either way, the problem is solved, perhaps before users have begun to notice. Interestingly, the solution can be used from an iPad. In that case, the screen is big enough for a techie to actually use instead of a laptop – and solve the problem immediately.
What if your organization doesn’t use iPhones? What if you’ve rolled out Blackberrys? Well in that case, WDS has a solution available. If your organization uses Symbian or Android (or anything else), then WDS are developing a solution for your smart phone right now.
It may all seems like something from a 1990s sci fi film, but monitoring your z/OS network from your mobile phone is a solution that’s available now.
And finally, as a mainframe professional, I am hoping that you will be willing to complete the annual user survey at www.arcati.com/usersurvey11. If the company you work for is a vendor, consultant, or service provider, then please ensure their information is included in the vendor information form at www.arcati.com/vendorentry.
Monday, 30 August 2010
Getting your money’s worth
If you’re looking for value for money, then you can’t do much better than attend the 9th annual UK 2010 Guide Share Europe Conference to be held on 2 and 3 November at Whittlebury Hall, Northamptonshire – if you’re using your sat nav, it’s NN12 8QH. This will be the largest UK GSE conference in their history and boasts 13 streams on the Tuesday and a whopping 14 streams on the Wednesday. You can get more information at www.gse.org.uk/tyc/Email01.html. Registration is now open.
Secondly, there’s now a Version 2.0 available of ZEN, the cost saving z/OS network management suite from William Data Systems. This new version includes enhancements that enable many more companies running z/OS to improve on and completely replace NetView or NetMaster. WDS claims that for some customers, managing networks with ZEN has reduced their annual cost of ownership by as much as 50%. ZEN customers pay for only the functionality they need, which reduces annual costs compared with users of other products who pay for functionality that they don’t use.
ZEN V2’s new Automation component includes a full REXX function pack. This provides facilities for users to totally automate their management of z/OS network environments and create customized ZEN displays and alerts.
ZEN provides a browser interface that is intuitive and customizable to individual user’s needs. ZEN also provides “green screens”, which more traditional users continue to benefit from. You can find out more at www.willdata.com.
And if you want something that’s absolutely free… you can find a summary of my recent interview with Stephen Ibaraki from the Canadian Information Processing Society (CIPS) at stephenibaraki.com/cips/v610/trevor_eddolls_2010.html. And if that whets your appetite, you can listen to the complete podcast at www.stephenibaraki.com/audio/Trevor_Eddolls_2010.mp3.
Secondly, there’s now a Version 2.0 available of ZEN, the cost saving z/OS network management suite from William Data Systems. This new version includes enhancements that enable many more companies running z/OS to improve on and completely replace NetView or NetMaster. WDS claims that for some customers, managing networks with ZEN has reduced their annual cost of ownership by as much as 50%. ZEN customers pay for only the functionality they need, which reduces annual costs compared with users of other products who pay for functionality that they don’t use.
ZEN V2’s new Automation component includes a full REXX function pack. This provides facilities for users to totally automate their management of z/OS network environments and create customized ZEN displays and alerts.
ZEN provides a browser interface that is intuitive and customizable to individual user’s needs. ZEN also provides “green screens”, which more traditional users continue to benefit from. You can find out more at www.willdata.com.
And if you want something that’s absolutely free… you can find a summary of my recent interview with Stephen Ibaraki from the Canadian Information Processing Society (CIPS) at stephenibaraki.com/cips/v610/trevor_eddolls_2010.html. And if that whets your appetite, you can listen to the complete podcast at www.stephenibaraki.com/audio/Trevor_Eddolls_2010.mp3.
Subscribe to:
Posts (Atom)