<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.ca.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>EXEC I/O Mainframe Blog</title><link>http://community.ca.com/blogs/execio/default.aspx</link><description>This blog is a  discussion of what&amp;#39;s new, stimulating and of general interest to the mainframe community.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP2 (Build: 20611.960)</generator><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.ca.com/PacificMainframeCommunity" /><feedburner:info uri="pacificmainframecommunity" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><image><link>http://www.ca.com</link><url>http://www.ca.com/images/global/logo_203076.gif</url><title>CA</title></image><item><title>The Mainframe Madness Returns</title><link>http://feeds.ca.com/~r/PacificMainframeCommunity/~3/jUWd-TcEVrQ/the-mainframe-madness-returns.aspx</link><pubDate>Thu, 11 Mar 2010 02:36:00 GMT</pubDate><guid isPermaLink="false">8d07cc69-a460-48f1-844d-25b05ba87317:4536</guid><dc:creator>Reg Harbeck</dc:creator><slash:comments>0</slash:comments><comments>http://community.ca.com/blogs/execio/archive/2010/03/10/the-mainframe-madness-returns.aspx#comments</comments><description>Mark your calendar! May is coming! And CA is continuing our tradition of May Mainframe Madness (aka MMM).

I blogged about our first annual MMM last year at http://community.ca.com/blogs/execio/archive/2009/05/01/let-the-mainframe-madness-begin.aspx. It was a great experience, and we&amp;#39;ve had lots of great feedback about it.

This year is going to be even better, with more new innovations,...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&lt;img src="http://feeds.feedburner.com/~r/PacificMainframeCommunity/~4/jUWd-TcEVrQ" height="1" width="1"/&gt;</description><feedburner:origLink>http://community.ca.com/blogs/execio/archive/2010/03/10/the-mainframe-madness-returns.aspx</feedburner:origLink></item><item><title>Getting Ready for SHARE</title><link>http://feeds.ca.com/~r/PacificMainframeCommunity/~3/VsyIGAN-juU/getting-ready-for-share.aspx</link><pubDate>Fri, 19 Feb 2010 01:19:00 GMT</pubDate><guid isPermaLink="false">8d07cc69-a460-48f1-844d-25b05ba87317:4446</guid><dc:creator>Reg Harbeck</dc:creator><slash:comments>0</slash:comments><comments>http://community.ca.com/blogs/execio/archive/2010/02/18/getting-ready-for-share.aspx#comments</comments><description>Wow, how time flies. We were just in Denver, it seems. Now, it&amp;#39;s already time to put the finishing touches on the presentations, make sure the trip&amp;#39;s booked and the registration&amp;#39;s taken care of, and get ready for SHARE in Seattle.

Over the past few months, I&amp;#39;ve gained new insights into SHARE, and a new level of appreciation for how the SHARE organization works.

After all, SHARE...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&lt;img src="http://feeds.feedburner.com/~r/PacificMainframeCommunity/~4/VsyIGAN-juU" height="1" width="1"/&gt;</description><feedburner:origLink>http://community.ca.com/blogs/execio/archive/2010/02/18/getting-ready-for-share.aspx</feedburner:origLink></item><item><title>Complexity...</title><link>http://feeds.ca.com/~r/PacificMainframeCommunity/~3/ROjPF-ZzgGs/complexity.aspx</link><pubDate>Thu, 11 Feb 2010 08:27:00 GMT</pubDate><guid isPermaLink="false">8d07cc69-a460-48f1-844d-25b05ba87317:4385</guid><dc:creator>Marcel Hartog</dc:creator><slash:comments>0</slash:comments><comments>http://community.ca.com/blogs/execio/archive/2010/02/11/complexity.aspx#comments</comments><category domain="http://community.ca.com/blogs/execio/archive/tags/complexity/default.aspx">complexity</category><category domain="http://community.ca.com/blogs/execio/archive/tags/cost/default.aspx">cost</category><category domain="http://community.ca.com/blogs/execio/archive/tags/Mainframe/default.aspx">Mainframe</category><category domain="http://community.ca.com/blogs/execio/archive/tags/savings/default.aspx">savings</category><category domain="http://community.ca.com/blogs/execio/archive/tags/Security/default.aspx">Security</category><description>I recently ran a number of seminars in EMEA. This gave me an opportunity to talk to many large mainframe users. And as always, it gives me a pretty good idea about the current state of IT. Even more than previous years, two issues are mentioned almost every time: Cost &amp;amp; Complexity.

And it&amp;#39;s especially the latter that keeps coming back. Funny isn&amp;#39;t it? We live in an economy where...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&lt;img src="http://feeds.feedburner.com/~r/PacificMainframeCommunity/~4/ROjPF-ZzgGs" height="1" width="1"/&gt;</description><feedburner:origLink>http://community.ca.com/blogs/execio/archive/2010/02/11/complexity.aspx</feedburner:origLink></item><item><title>The Mainframe's Back and not Dissed!</title><link>http://feeds.ca.com/~r/PacificMainframeCommunity/~3/BINybbWBVbw/the-mainframe-s-back-and-not-dissed.aspx</link><pubDate>Sun, 31 Jan 2010 16:36:00 GMT</pubDate><guid isPermaLink="false">8d07cc69-a460-48f1-844d-25b05ba87317:4295</guid><dc:creator>Reg Harbeck</dc:creator><slash:comments>1</slash:comments><comments>http://community.ca.com/blogs/execio/archive/2010/01/31/the-mainframe-s-back-and-not-dissed.aspx#comments</comments><description>I remember, 15 or more years ago, seeing a photocopy in one of my colleagues&amp;#39; cubicles, with a picture of a dinosaur running rampant eating little PC-like creatures.

A few years later, I saw a similar graphic on some mainframe services buttons that were being given out.

The message on both? Mainframes: We&amp;#39;re Back and We&amp;#39;re... (insert word suggesting &amp;quot;in a mean mood&amp;quot;).

In...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&lt;img src="http://feeds.feedburner.com/~r/PacificMainframeCommunity/~4/BINybbWBVbw" height="1" width="1"/&gt;</description><feedburner:origLink>http://community.ca.com/blogs/execio/archive/2010/01/31/the-mainframe-s-back-and-not-dissed.aspx</feedburner:origLink></item><item><title>Modernizing, for modernizing’s sake?</title><link>http://feeds.ca.com/~r/PacificMainframeCommunity/~3/K9W8wIv6wHM/modernizing-for-modernizing-s-sake.aspx</link><pubDate>Fri, 29 Jan 2010 08:44:00 GMT</pubDate><guid isPermaLink="false">8d07cc69-a460-48f1-844d-25b05ba87317:4287</guid><dc:creator>Marcel Hartog</dc:creator><slash:comments>0</slash:comments><comments>http://community.ca.com/blogs/execio/archive/2010/01/29/modernizing-for-modernizing-s-sake.aspx#comments</comments><category domain="http://community.ca.com/blogs/execio/archive/tags/cost/default.aspx">cost</category><category domain="http://community.ca.com/blogs/execio/archive/tags/Mainframe/default.aspx">Mainframe</category><category domain="http://community.ca.com/blogs/execio/archive/tags/savings/default.aspx">savings</category><description>Many moons ago, most Mainframe applications went through an audit to see if they could be re-hosted on a platform that was cheaper, more flexible and more powerful.

It was a business decision because (on paper) the cost of running the migrated systems was looking great. Most IT people know what happened. We managed to &amp;quot;re-host&amp;quot; the applications that could be re-hosted, but at what...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&lt;img src="http://feeds.feedburner.com/~r/PacificMainframeCommunity/~4/K9W8wIv6wHM" height="1" width="1"/&gt;</description><feedburner:origLink>http://community.ca.com/blogs/execio/archive/2010/01/29/modernizing-for-modernizing-s-sake.aspx</feedburner:origLink></item></channel></rss>
