Mish mash-ups

Everyone’s talking about mash-ups, even some people sitting near me in the pub the other day. And everyone has seen what clever things you can do with Google Earth and some other high-profile mash-up sites. But has anyone seen a mash-up using mainframe data? And would it add business value?

But what is a mash-up? That’s the first problem – actually defining the term because it’s been used for slightly different things. Some mash-ups simply display data in a different way, while others combine information or capabilities from two or more separate sources to deliver new functions and insights.

And how do you create a mash-up? Well that’s up to you. At the moment, there is no standard way to build mash-ups – everyone has choice and flexibility. However, they are typically built on a Web-oriented architectures like REST (REpresentational State Transfer) or SOAP (Simple Object Access Protocol), and leverage lightweight simple integration techniques like AJAX (Asynchronous JAvaScript and XML – itself and acronym for eXtended Mark-up Language), RSS (Really Simple Syndication), and JSON (JavaScript Object Notation). The result should be the fast creation of rich desktop-like Web applications.

Typically, "widgets" and "feeds" (probably) from independent sources are mashed together, but do not change when mashed. A Web feed is data formatted in XML and used to provide users with frequently-updated content. Content distributors syndicate a Web feed, thereby allowing users to subscribe to it. Making a collection of Web feeds accessible in one spot is known as aggregation, which is performed by an Internet aggregator (of course!).

A widget is a small program or piece of dynamic content that can be easily placed into a Web site. Widgets are given different names by different vendors, eg gadgets, blocks, flakes. Widgets can be written in any language (Java, .NET, PHP, etc) and can be as simple as an HTML fragment. Widgets can be non-visual, and often encapsulate an API. "Mashable" widgets pass events, so that they can be wired together to create something new.

IBM, of course, has mash-up software. This includes Lotus Mashup, Infosphere mashupHub, and WebSphere smash.

Going back to my original questions, mash-ups can include mainframe data, and can take data from that most efficient but complicated beast, IMS. It’s perfectly possible to convert an IMS asset into an IMS RESTful service, which has the ability to consume and be consumed by other Web 2.0 services. IMS customer could then remix and mash-up their data rapidly with IBM Info 2.0 tools to extend their business logic without the need to write a single line of code.

Alternatively, by publishing an IMS RESTful Service to the Web 2.0 community, this opens up the possibility of third parties generating creative mash-ups that could benefit both third-party developers as well as the original IMS service provider. The third-party developer would now have IMS assets available to them. While, the IMS service provider could benefit from new business opportunities and increased partnership on the Web. And this answers my second question – it would add business value.

Some of the information in this week’s blog was taken from a recent presentation given by Jenny Hung from IBM’s IMS Development Division to the Virtual IMS Connection (www.virtualims.com) virtual user group meeting. A copy of Jenny’s presentation is available for members to download from the Virtual IMS Connection Web site.

Hello – is anybody there?

When I was a youngster and first learned how to operate a mainframe, first learned how to load tapes, and change removal disks, first learned how to stick paper tape together again after a ripping time, and first learned how to hold a deck of cards up my arm without dropping it, everyone else was similarly aged. And we had fun.

And then we stopped being operators and started being programmers, managers, trainers, and writers. And we still had fun – but not so much because we had mortgages and children, etc.

And then we became very senior personnel and started talking about pension plans and setting up trusts so the right people benefited from our hard-earned money and possessions.

And in the meantime, mainframes stopped being interesting to the rest of the world, who thought working on Unix and Solaris, or Linux and Windows was much more fun. And people trained in COBOL and Fortran started sitting together in the staff canteen because there were so few of them and everyone else wrote in Java, C++, Python, etc, etc.

But the mainframes continued improving, and large organizations continued making do with fewer staff, and ran their important business on the mainframes – confident in their continuing success.

However, for a long time now, those mainframers have begun to retire, or to get less demanding jobs that have reliable hours and a short commute.

So what reminded me of this skills shortage? CA recently released a study by InfoPro of 270 senior IT execs from Fortune 2000 companies. The study found that 80 percent had mainframe staff who were eligible for retirement now or over the next couple of years.

No great surprise there, but it does highlight quite a serious problem. So is there an answer? Unfortunately, there are lots of answers! First the good news, autonomic management of mainframes is getting better, which means that it’s easier to tell the mainframe how to perform and then the machine will reliably get on and perform according to the instructions given. This means that less-skilled people can be used to run the mainframe and its major components like IMS, CICS, DB2, etc. Also the interfaces are looking more Windows-like, which makes communicating with the mainframe easier for “the youngsters” than in the “green screen” days.

There have also been moves by IBM to train youngsters to be able to program mainframes – so well done to them any other organizations doing the same. And, perhaps as an aside, it might be a good idea for more organizations to retrain their own IT staff to understand the workings of a mainframe.

The third alternative is the not so good news. It is to get rid of the mainframes altogether and migrate applications and data to mid-range machines.

So, from a blogger’s point of view: option one means that there will be fewer people reading this; option two means that youngsters will be able to read this but won’t because it’s not on Facebook or I should have made a video of me saying the words and put it on Youtube; and option three means that no-one at all will be reading it. So, depressingly, none of them are very positive from my perspective!

Anyway, if you are still using a mainframe, make sure you fill in the user survey at www.arcati.com/usersurvey09 - time is running out. The Arcati Mainframe Yearbook 2009 will be out in early January.

Even more CSS tips

As I said about a month ago, while I’ve been designing Web sites recently – to W3C standards I might add – I have put together some CSS tips that I’d like to share with you.

10 If you are using numbered lists or bullet points
Remember to define the style.

CSS
li {
font-family: arial;
font-size: 10pt;
color: green;
}

11 Format pseudo classes in the right order - Lord Voldemort Hates Apples
Text rollover effects won’t work correctly in all browsers unless they are in the correct order in the CSS.

CSS
a:link { color: red; }
a:visited { color: yellow; }
a:hover { color: green; }
a:active { color: blue; }

12 Place an image permanently in the bottom left-hand corner of a Web page

CSS
body {
margin:10px 10px 0px 10px;
padding:0px;
background: #f5f5dc url("es.gif") no-repeat fixed left bottom;
}

13 Drawing a green line

HTML
<hr />

CSS
hr {
border: 0;
width: 80%;
color: green;
background-color: green;
height: 5px;
}

14 Making an orange XML or RSS buttons or other icons without using an image

HTML
<a class="feed" href="http://h1.ripway.com/t_eddolls/teblog.xml">FEED</a>

CSS
.feed {
border:1px solid;
border-color:#FC9 #630 #330 #F96;
padding:0 3px;
font:bold 10px arial;
color:#FFF;
background:#F60;
text-decoration:none;
margin:4px;
}

15 Centering text in a paragraph

HTML
<p style="TEXT-ALIGN: center">

16 Positioning within a container
In the example below, the … (or whatever) appear exactly 200px from the left and 150px from the top of the container box.

HTML
<div id="container"><div id="navigation">...</div></div>

CSS
#container
{
position: relative;
}
#navigation
{
position: absolute;
left: 200px;
top: 150px;
}

17 Making links more exciting

CSS
a.ttt {
font-family: arial;
font-size: 10pt;
text-decoration: none;
color: red;
cursor: pointer;
}
a.ttt:visited {
color: gold;
}
a.ttt:hover {
color: navy;
background-color: red;
font-style: italic;
cursor: pointer;
}
a.ttt:active {
background-color: navy;
color: red;
}

HTML
<a class="ttt" href="http://www.itech-ed.com/">hello world</a>

More hints and tips next time.

By the way: anyone looking for an experienced technical writer or Web designer can contact me at trevor@itech-ed.com. Also, if you haven’t completed the mainframe user survey yet, go to www.arcati.com/usersurvey09. And if you’re a vendor, then you need to complete the form at www.arcati.com/vendorentry - and there are still Yearbook sponsorship opportunities available.

The Sun shines out of mainframes

Earlier this month, IBM and Sun Microsystems announced that a mainframe version of Sun’s OpenSolaris operating system was available for download. The announcement wasn’t completely unexpected because it had been demonstrated in November 2007.

The port of the OpenSolaris operating system to the mainframe was made possible by a company called Sine Nomine Associates, which is also developing a Java software port to the mainframe.

Solaris you’ll recall already runs off Sparc platforms and can be found on x86-based machines.

So how does it work? Well it doesn’t just sit on the big iron like z/OS, it makes use of z/VM. Using z/VM allows many virtual OpenSolaris images to run simultaneously. Now VM itself has had a bit of a chequered history at IBM, with efforts at times to remove it, and other periods when its development was really rather ignored. Which all seems rather strange with hindsight when nowadays everything can be virtualized – even your laptop at home! I’ve always been a big fan of VM – in fact I wrote two books about it many years ago. (Archivists might be able to find you a copy of VM Performance Management and Introduction to VM.)

So porting OpenSolaris to a mainframe is an interesting technical challenge, but why should non-techies care? The answer is the ability to do more with less. Mainframes are very good at maximizing asset usage and exceptional system performance figures. Moving to a single mainframe probably allows the removal of numerous smaller servers and a “green” benefit of less heat produced and less energy utilized. It also helps to reduce costs and possibly even reduce headcount.

This is good for Solaris users, but it’s also good for IBM. IBM needs a way to get new people to buy mainframes, so encouraging banks etc to upgrade to a mainframe has got to be good for them. Obviously the current economic climate isn’t good for banks! However, history shows these downturns in the economy pass within two or three years. IBM is playing the long game and hopes that when companies do have money to spend they (IBM) will be the organization the money is spent with.

There must be some organization out there that is working on a port of Windows server to VM. It would be really interesting to hear about that. Or perhaps the Microsoft code is so buggy and convoluted it’s an impossible task, even for the excellent z/VM.

And finally, don't forget about the Arcati Mainframe Yearbook 2009. Last year's issue is still available at www.arcati.com/newyearbook08. The annual user survey of mainframe usage is at www.arcati.com/usersurvey09 - please let us know how you use your mainframe. And vendors, consultants, or service providers, can get a free entry in the vendor directory section by completing the form at www.arcati.com/vendorentry. Plus there are advertising and sponsorship opportunities.

Mainframes on a cloud

I know what a mainframe is, but what is a cloud? I'll avoid any references to white fluffy things and get straight to a definition of sorts. Cloud computing gets its name from the way network diagrams have been drawn for years. There was always a bit somewhere that was drawn as a cloud. That way no-one had to worry to much about what was going on in that bit. Well now the cloud has come centre stage. It's still a way of glossing over the details of whatever infrastructure exists underneath though.

Wikipedia suggests that Cloud computing is "a style of computing in which IT-related capabilities are provided 'as a service', allowing users to access technology-enabled services from the Internet without knowledge of, expertise with, or control over the technology infrastructure that supports them". 

Wikipedia goes on to say, "according to a 2008 paper published by IEEE Internet Computing 'Cloud Computing is a paradigm in which information is permanently stored in servers on the Internet and cached temporarily on clients that include desktops, entertainment centers, table computers, notebooks, wall computers, handhelds, sensors, monitors, etc.'"

Which is all very nice, but what has it got to do with mainframes? Well the answer is Micro Focus. Micro Focus offers tools for mainframe users to migrate off a mainframe to, usually, a Windows platform. The theory goes that it allows programs to be updated and make use of modern technology at a much lower price than staying on the mainframe. Mainframers often argue that migrating applications to other platforms leads to poor performance or an extensive rewrite of the code, which in turn can lead to errors. They also argue that there can be problems when scaling these migrated applications on the new platform. And there is also the problem of off mainframe applications sharing data with mainframe apps. But I digress.

Micro Focus has a long history of migrating COBOL applications to Windows and .NET. Now it is focus on Windows Azure Services Platform cloud. Micro Focus is hoping that COBOL will become a standard cloud computing programming language - like Ruby and Python. Micro Focus are saying that because COBOL is designed to run in large computing environments, it is an ideal programming language for cloud computing. They are also suggesting that cloud computing could make a good substitute for IMS and CICS systems.

Now, as a died-in-the-wool mainframer, I'm not going to recommend that anyone migrates their applications off the mainframe. However, it is interesting to think that cloud computing could be integrated into the Enterprise computing environment in much the same way as distributed processing has been. And if younger programmers learn COBOL for cloud computing, it would be only a short step for them to be able to become CICS programmers - which would solve the problem of where the next generation of COBOL programmers are going to come from. I certainly applaud the efforts of Micro Focus to make COBOL a standard cloud computing programming language.

And finally, don't forget about the Arcati Mainframe Yearbook 2009. Last year's issue is still available at www.arcati.com/newyearbook08. The annual user survey of mainframe usage is at www.arcati.com/usersurvey09 - please let us know how you use your mainframe. And vendors, consultants, or service providers, can get a free entry in the vendor directory section by completing the form at www.arcati.com/vendorentry. Plus there are advertising and sponsorship opportunities.

It’s back!!

I used this attention-grabbing headline so I can tell you that the Arcati Mainframe Yearbook is back for another year – or it will be very soon. The celebrated Arcati Mainframe Yearbook is one of the very few vendor-independent sources of information for mainframe users. 

The Arcati Mainframe Yearbook has been the de facto reference work for IT professionals working with z/OS (OS/390) systems since 2005. It includes an annual user survey, an up-to-date directory of vendors and consultants, a media guide, a strategy section with papers on mainframe trends and directions, a glossary of terminology, and a technical specification section. Each year, the Yearbook is downloaded by 10 000 to 15 000 mainframe professionals. Last year’s issue is still available at www.arcati.com/newyearbook08.

At the moment, the compilers of the Yearbook are hoping that mainframers will be willing to complete the annual user survey, which is at www.arcati.com/usersurvey09. The more users who fill it in, the more accurate and therefore useful the survey report will be. All respondents before the 5th December will receive a PDF copy of the survey results on publication. The identity and company information of all respondents is treated in confidence and will not be divulged to third parties.

Anyone reading this who works for a vendor, consultant, or service provider, can ensure their company gets a free entry in the vendor directory section by completing the form at www.arcati.com/vendorentry. This form can also be used to amend last year's entry.

 

As in previous years, there is the opportunity for organizations to sponsor the Yearbook or take out a half page advertisement. Half-page adverts (5.5in x 8in max landscape) cost $500 (UK£250). Sponsors get a full-page advert (11in x 8in) in the Yearbook; inclusion of a corporate paper in the Mainframe Strategy section of the Yearbook; logo/link on the Yearbook download page on the Arcati Web site; a brief text ad in the Yearbook publicity e-mails sent to users. Price $1700 (UK£850).

 

So, get cracking and complete the user survey so it’s the most comprehensive survey ever.

The Arcati Mainframe Yearbook 2009 will be freely available for download early in January next year.

More CSS tips

As I said last time, while I’ve been designing Web sites recently – to W3C standards I might add – I have put together some CSS tips that I’d like to share with you over the next few weeks.

5 Dividing a Web page into parts

You can use CSS to divide a Web page into four parts - an area across the top, then underneath that an area on the left for buttons, an area in the middle for text, and an area on the right. 

CSS

#top {

position: absolute;

background: #ffffff; 

top:145px;

left:80px;

right:100px

}

#leftcontent {

position: absolute;

left:80px;

top:200px;

width:80px;

background: #f5f5dc; 

}

#centercontent1 {

position: absolute;

top:200px;

left:200px;

width: 35%; 

margin-left: 81px;

}

#rightcontent {

position: absolute;

right:0px;

top:500px;

width:30%;

background:#f5f5dc;

}

HTML

<div id="top">

</div>

<div id="leftcontent">

</div>

<div id="centercontent1">

</div>

<div id="rightcontent">

</div>

6 printing your page

You may want people to print a Web page as black text on a white background while at the same time having lots of fancy stuff on the page. You can achieve this by having a print stylesheet associated with the page.

HTML

<link rel="stylesheet" type="text/css" href="print.css" media="print">

or:

<style type="text/css" media="print"> @import url(print.css); 

</style>

You need to put appropriate styles in the print.css stylesheet.

7 Use "title" and "alt" attributes for images

With these encoded, screen readers can correctly parse your page.

HTML

<img src="myimg.gif" alt="me" title="me" />

8 Invisible text

Invisible text can be useful for people who use screen readers. It can also be useful where images contain text because search engines can’t “read” images.

CSS

position: absolute; left: -5000px

The text is positioned 5000px to the left of the left edge of the screen.

9 Drop cap

This adds a drop cap to the left of a block of text.

HTML

<span style="margin-right:6px; margin-top:5px; float:left; color:white; background:gold; border: 1px solid #000; font-size:80px; line-height:60px; padding-top:2px; padding-right:5px; font-family:arial;">H</span>ere is a drop cap with a gold background, white text, and a black border.

<div style="clear:both;"><br />

</div>

More hints and tips next time. 

By the way: anyone looking for an experienced technical writer or Web designer, contact me at trevor@itech-ed.com.