Take it Easy with Atlas 3.0

Atlas, our Agile requirements and delivery platform, has cool new features and Frank thinks you should hear about them. Needless to say, it reminds him of The Eagles.

Frank has been standing up for devs long enough to know that delivering complex IT projects can be heavy lifting.

It’s the complexity of pulling stuff together. Uniting guys in different siloes. Keeping everyone in the loop in a way they all understand. As usual, 1970s country rock can teach us a lesson from history. Take the Eagles’ recording of the Long Run album. Frank’s legendary freeform cassette stacking system reckons it was their last studio album for decades – and it’s not surprising.

According to producer Bill Szymczyk – Frank never loses a game of rock Scrabble, thanks to Bill – the band was so fragmented that they were phoning in their contributions from all over the States. Glen Frey – RIP, man – worked from LA while the rest of the band were in Miami. The result wasn’t great. And happened next? Acrimony. Lawsuits. Beverly Hills Cop soundtracks. And no-one wants that. So, thank the Lord for Atlas.

Third versions things aren’t always great. Waiting for the Sun had one single worth hearing. Jaws 3 had us all cheering for the shark. Atlas 3.0 is different.

Woah! What’s Atlas anyway?

Atlas is our Agile requirements solution. It unites key people in a beautiful oneness. Technical and operations teams get together with business analysts on a platform that captures market trends and innovative stakeholder ideas. It’s like getting the Airplane, Jimi and Janis in one place.


So. Atlas 3.0. Tell us more.

Atlas 3.0 now integrates with Silk Central. With this powerful test management platform in your locker, strategically planning testing suites, defining test cases and executing quality management just got easier.


Atlas and Silk Central integrations keep testing efforts aligned with customer requirements. Transparency and control are your new friends. Users view test activity and results in every requirement area. Integration ensures test teams can view – and test tools stay in sync with – defined requirements as they evolve.

Atlas 3.0: Frank’s list of good stuff

  • Review and evaluate the results of evolving business needs: See how requirement versions have changed over the life of the project. Changing course isn’t something you do at the end.
  • Assess potential impact of new requirements: Every picture tells a story. Use Atlas to create the diagrams that identify the interdependencies. It means smarter decisions – and more realistic schedules – around new requirements.
  • Improve collaboration between business and development teams: Communicate and exchange ideas and concepts as application requirements develop. It’s kind of the opposite of late-period Eagles.
  • Assess Agile team progress in the context of customer expectations: Is development time aligned with defined requirements? Get a clear picture with Atlas 3.0.
  • Show related test count and status by requirement. Understand how test execution has changed over time, providing visibility to incremental test progress.
  • View the test status as Gantt charts. Assess test progress across all requirements.
  • Step into the Atlas Time Machine. Better understand the impact of changes in requirements and evaluate project status, to see how test status has changed between two points in time.
  • Version comparison: Compare differences between two versions of requirements, or list the items that have changed since the last access.

You want this

Well, if you are a customer on maintenance it’s already yours, my friend. Rock up to supportline.microfocus.com. Say Frank sent you.

Living in Non-Maintenance Palookaville? Fret not. You get to see how Atlas lightens the load by helping you gather, define, plan and track the agile delivery of your business needs, initiatives and related requirements. Try now. For Free.

Frank out.

Frank Profile

Is ‘innovation’ this year’s ‘solution’?

When last week’s funky phrase becomes a corporate cliché, writing for technology can be a metaphorical minefield. Here our Senior Copywriter, Steve Moore, attempts to rescue ‘the Micro Focus word’ from buzzword bingo.

This post regards many of the words I use every day as clichés. That’s the nature of IT – the lexicon moves on as quickly as the technology. I have no problem with ditching many of the usual suspects, listed below. But as one of them underpins everything we do at Micro Focus, I must ringfence it – and fast.

Delivery, Passion and Solutions

Have you noticed how we all ‘deliver’ things now? What was once the exclusive domain of the postal service now also applies to most of the people reading this blog. Customers generally just download the software we make. Yet we must still deliver it. Go figure.

Remember when everyone had to be ‘passionate’ about what they did? Financial markets. Plumbing. Fish. This company is “passionate about roofing” when ‘adequately qualified and experienced’ would seem preferable. Not sure I want a passionate roofer prowling my property with a hammer.

Although satirical magazine Private Eye no longer runs a dedicated Solutions column, everything apparently still needs a solution. Shoelaces. Cricket. Wardrobes. Funeral Solutions apparently “know the industry from the ground up” when the bulk of their business is surely in the opposite direction.

What makes a cliché?

The problem with delivery, passion and solutions isn’t the word itself, but a lack of context around it. Too often, organisations spend buzzwords like cheap currency, believing they add value when the reverse is true. Overuse can reduce messaging to little more than a string of meaningless phrases.

These guys and these people are “passionate” about their “solutions” – notepaper and boilers, respectively – and this blogger spotted a van promising delivery, solutions and passion in one hit. Sounds good. But the solution being passionately delivered remains unclear. A lack of context is the problem.

Take ‘solution’. If I followed this blog and stopped using the word, describing the Micro Focus Mainframe Solutions would be problematic. But aside from the fact it’s a proper noun I can also contextualise the word by referencing the hundreds of customers who use it to resolve genuine business challenges. So it’s a solution, all right.

But as these words are banished to copywriting Palookaville, the marketplace, like nature, will fill the vacuum with something else. My fear is that ‘innovation’ is next. And that cannot stand.

Leave innovation in isolation

I’m just finishing off the Micro Focus Tone of Voice guide. We use plenty of verbs – especially ‘innovate’ – to describe our work. We cannot annex the word, because it feels different to all of us, but we can contextualise – and own – our version of it.

Innovation to most IT consumers is the next iPhone, Shazam, Cortana or any number of sexy, interactive products. Personally, I am still amazed at how Google Maps is digitizing the world and that’s practically old school.

The different flavours of innovation

But that isn’t innovation, Micro Focus style. Strategically and culturally we’re closer to this business directory definition; “In business, innovation is when ideas are applied to further satisfy the needs and expectations of the customers”.

So our innovative software enables our customers, many in the financial world, to innovate in their own way. Our version of innovation is retuning 20-year-old COBOL or PL/I to behave in a completely new way. It is giving long-established applications a flexibility the original coders couldn’t possibly have imagined, but our customers need to compete in a perpetually-evolving marketplace.

Micro Focus technology bridges old and new, unifying our customers’ IT investments with emerging technologies to achieve low-risk innovation and meet increasingly complex business demands.

What innovation means to us

Some find the idea of modernizing long-established applications pretty innovative. To other customers, innovation is creating a mobile banking app or moving from clunky green screen monitors to interactive interfaces without changing a line of code; plenty of Silk Performer users think that keeping the company website upright no matter how big the load is pretty remarkable, while other customers in other areas would point to being able to make sense of the data generated by 50m connected devices.

All these customers will remark that liberating developers to work on new and exciting products is innovative in itself. It’s all good innovation and makes us, indisputably, an innovative company. But only by taking the customer perspective can we contextualise the word and justify using it. The key is providing the meaning that saves innovation from being the next ‘solution’.

To some, innovation is a cliché. To Micro Focus it is simply a way of capturing the way we deliver products to fit a continually-evolving IT landscape in a single word.

And now I’ve got that off my chest, I’m off to enjoy a nice, cool glass of my favourite sobriety solution

What does a good IT Skills strategy look like?

Jackie Anglin from Micro Focus reflects on a recent SHARE.org IT Skills webinar. In part 2 of this series Lonnie Emard – IT-ology President and David Rhoderick, Manager of IBM z Systems Competitive Project Office share their thoughts on what they heard.

My last blog recapped a Micro Focus IT Skills webinar, during which invited industry experts joined the Micro Focus team to debate the IT Skills issue. Here, Lonnie EmardIT-ology President and David Rhoderick, Manager of IBM z Systems Competitive Project Office, offer their thoughts on the discussion.

So, David and Lonnie, how does an organization build an appropriately skilled workforce?

David“Look for people who can really make a long-term difference to the company – and think about who’s leaving in the next five years. That equates to about 10,000 hours, or the amount of time it takes to become expert in a particular skill. Also, look at the way tools are evolving. We don’t need green-screen programmers – we need people who can understand which tools to use for the right job and then use them effectively.”

LonnieAt Blue Cross – BCBS of South Carolina is a big partner of IBM and Micro Focus – we realized that an organization who would do the right things to create talent acquisition development and retention programs around COBOL and around mainframe, around enterprise systems, is that in the future we couldn’t solve this problem by ourselves. 

The Blue Cross model is about creating the strategy that Derek mentioned, understanding what you’re about and appreciating your skills and talents. Certainly, most of the large companies still running enterprise systems and IBM servers must pass down a set of knowledge and skills for repurposing as a ‘master and apprentice’ model. That worked tremendously well for us. At the same time, what we do internally has to be complemented with greater external access and reach.”

To the second question: “How does technology play its part in the IT skills challenge?”

David“The mainframe is evolving in parallel with the wider business picture: mobile technology, Internet of Things, new workloads that mesh with the mainframe. We at IBM are active in connecting new technologies to the backend. People find new technologies like JSON easy to do. We’ve had web services, we’ve had XML, all of these newer, open standard capabilities. It should be easy for someone familiar with this style of programming to work with a mainframe. And clearly there are very strong, sophisticated DevOps tools.” 

LonnieWhen technology is this expansive it can become confusing and complex. Everybody wants a ‘one size fits all’ answer to every technology solution in every industry and that’s just not realistic. So part of what we’re doing is to change the message out in the community.  An example is cutting a COBOL video to prove young people are not thinking, “Hey, [I] don’t want to work in that environment!”

“I understand what we’re trying to accomplish with IT. That’s our goal. I’s not about having a computer science degree, but being applied in all facets of the business. Now you’ve got somebody who’s legitimately impactful in their work. That’s the kind of skills challenge I think we’re seeing. The answer is to put that interdisciplinary piece together.” 


The last question focused on the long term solution. Derek asked “Doesn’t the skills issue highlight the gap between skills being taught in schools and those demanded in the commercial world?”

David“Well I think, first of all, the solution is a long-term view of your IT strategy. Clearly a long-term mainframe strategy is crucial for any company – – banks, insurance companies, whoever – still anticipating huge, growing volumes of transactions and queries with the need to be increasingly responsive and agile. 

My advice is to have a long-term strategy for hiring, and to work with universities.  As Lonnie said, it is crucial that the people consuming the skills are brokering and collaborating with the sector producing them, along with parties like IBM who try to make it all happen.”

Lonnie“That has been the magic behind the collaboration of ITology – companies must understand where they’re headed and what that means in terms of an alignment of skills.  We’ve found a resonance that almost every job has a technology underpinning. The messages we talked about earlier are key to this whole thing in terms of a long-term solution.”


In summary

It was a terrific to get such valuable insights from industry experts. Do you agree with their comments?  To listen to the full webinar, go here.  For more information on the Enterprise skills question, visit our page.

DevOps and Organizational Culture

In the Micro Focus blog series on DevOps, Derek Britton looked the bottlenecks of low collaboration, inefficient development and lengthy testing cycles and how they can be overcome with a pragmatic, technological solution. Here, he turns his attention to that most indiscernible of obstacles: corporate culture.

Letting it breathe

In the Micro Focus blog series on DevOps, I looked the bottlenecks of low collaboration, inefficient development and lengthy testing cycles and how a pragmatic technological solution can overcome them. Here my attention turns to that most indiscernible of obstacles: corporate culture.


It has been said that 2016 could be the year DevOps came of age. It continues to gain mindshare including large enterprise accounts. Gartner projects a quarter of the Global 2,000 will have adopted DevOps this year, growing by 21%. Reflecting growing popularity, SHARE in March 2016 has its own DevOps track: “DevOps in the Enterprise”. SHARE has also added a DevOps discussion to its “EXECUforum” agenda, entitled “DevOps: Cultural Mindset”. (We are delighted to join luminaries from IBM, Compuware and CA on the panel).


DevOps, as the name suggests, is a technical approach to a necessary business change, namely building new services faster for the business. Put another way, DevOps is a process change, a means to an end. Changing to embrace DevOps affects a number of disparate organizational elements, from IT groups to business, user and customer communities. Clearly, there are important cultural questions in terms of how the organization is ready to embrace DevOps. Culture is widely recognized as being at least as important as strategy. As one report observed, “Changing the culture and mind-set of people is not easy.”

Cultural Barriers to Adoption

Adopting DevOps may flounder for a variety of cultural reasons.

Why are we doing this? While establishing an agile-based methodology in the IT organization makes a lot of sense and, according to history, yielded impressive early results, the parent organization may often be ignorant of the new process. In fact, the business may still expect product roadmap milestones to be planned and met on an annualised basis as part of a traditional regimented plan-build-deliver cycle, unaware of the new dynamic. For IT, breaking down Portfolio and Product plans into Epic and then Iterations is -with a group of trained professionals working together –both viable and valuable. However, ensuring such plans are agreed and acted upon by the consumers of the technology (whether internal users or sales/marketing/customer representatives) is much, much harder, especially when the reason for the change is not clear outside IT. So while like-minded technicians might flock towards DevOps, end-users won’t subscribe to what is probably perceived as extra work for them. They just want results, working apps, not more work. They can’t see the benefit of change.


Moving from big to small. DevOps espouses more rapid, incremental deliveries and a tighter feedback cycle to resolve difficulties and achieve customer satisfaction more quickly. That switch requires the shift from large-scale orchestrated deliveries to more frequent, smaller-scale incremental efforts. The change in dynamics mean there will be greater coordination required by more people on a more regular basis, and a certain level of disentanglement of both application sets and job functions. As one observer put it, successful adoption will require teams to “Embrace the Chaos”. But chaotic it will be, and for larger, more-established, more hierarchical organizations, or those who preside over larger (sometimes referred to as monolithic) systems, that chaos will be most keenly felt.

We don’t have the bandwidth. Restricted infrastructure resources, a problem sometimes faced in large organizations with many parallel work streams is another genuine concern. In some organisations, the change from one model to another might just feel too big. One of the most common bottlenecks is the inability to undertake rapid test cycles as part of a process of continuous integration. With autonomous teams and no restrictions on test environments, as DevOps will need, rapid testing sounds viable. However in a more traditional, regimented IT world, where resources are allocated as part of a planned-for, charged-for system, “just running some tests” is not as simple as that. It might take days, if not longer, to commission a test environment and a very real budget to manage.

Cultural Change – Practicality and Transparency

DevOps is a major upheaval, a major change program. Such change programs need to be clearly outlined, understood, and measurable. So how might DevOps promote wider cultural acceptance?

Get Out There. Failure to involve all stakeholders in a major change program will result in inevitable resistance. Ignorance of why the change is being made will hamper progress. Establishing a clear vision across the organization of why there is a new approach to software deliveries is the fundamental cornerstone of its adoption. To that end, stakeholders need to hear that the reason for the new approach is that the organization is trying to improve the quality of the technology service, and is therefore aiming to deliver more frequently to determine faster feedback, and course-correct. Such a vision is predicated by a top-down C-level sponsorship. After all, the “end game” is new services and customer satisfaction or some other tangible strategic business benefit: DevOps is merely a vehicle to achieve that. Explained this way, especially in the always-on digital age, it is wholly appropriate and acceptable for the supplier to seek to engage more frequently with their users. In a business context in vision, the purpose of DevOps becomes far more tangible and sensible to non-IT stakeholders.

Get Amongst IT. Similarly, for teams responsible for delivering software, from the development, QA and operations functions, previous functional silos and hierarchy no longer apply so readily. But transitioning to a team-oriented structure may take time. Some organizations are borrowing ideas from Agile by establishing functional teams which are temporary for the duration of a major release, or epic, etc. Additionally, many IT organizations are driving internal change with the help of a senior DevOps champion. One organization I know has chosen their new CIO specifically because of their DevOps experience and vision.

Build Bridges. There may appear to be no straightforward resolution to incumbent resource availability (be it related to people, hardware or software), and this is where pragmatism and practicality comes to the fore. Previously accepted practices and platforms may not be as fixed as might first appear. There are a variety of technical solutions available to improving development, testing and efficiency of collaboration for mainframe teams. They can realistically achieve far greater frequency and reach a wider variety of users by exploiting new technical solutions. (One example is Micro Focus’ solution, here).

DevOps bandwidth


Larger organizations have every opportunity to embrace DevOps by taking the cultural aspect of change as seriously as the underlying technical and operational approach they are aiming to use. Practical and pragmatic solutions exist to overcome fundamental operational roadblocks; a comprehensive and transparent cultural change program will also be needed to promote widespread adoption. As a recent ComputerWorld headline put it “Culture is Key to DevOps Success”.

Find Micro Focus at booth #525 at SHARE or visit our dedicated DevOps resources if you can’t attend the event in person.

Achieve peak performance at #MFSummit2016

The inaugural Micro Focus cross-portfolio summit opens this week. Andy King, General Manager for UK and Ireland offers his insights as to what to expect from the program.

This is a big week for myself and Micro Focus. On Wednesday, I raise the curtain on the future of our new company and our products for the customers who want us to take them into tomorrow.

Since the 2014 merger with the Attachmate Group, we have become one company operating two product portfolios across six solution areas. The single aim is to meet our customers’ mission-critical IT infrastructure needs with enterprise-grade, proprietary or open source solutions.

But what does that mean in reality? We are all about to find out.

#MFSummit2016: Current challenge, future success is our first cross-portfolio conference. The format mixes formal sessions and face-to-face opportunities, informative overviews with deep-dive, issue-specific questioning. It is a first chance to check out the roadmaps, and share experiences with our experts.

The focus is firmly on interaction; product specialists and fellow customers will be there to discuss your business and IT change issues. Set your itinerary to get maximum value from the day. The 12 sessions are split into three broad themes.


Build. Operate. Secure.

Whether your IT issues span every area of build, operate and secure, or are confined to one or two, Micro Focus has it covered with a diverse range of products and solutions that will help to meet the challenges of change. I’ve selected three sessions to illustrate the point.


Dave Mount, UK Solutions Consulting Director presents an Introduction to Identity, Access and Security. Dave’s view is that understanding and managing identity enables better control of internal and external threats. He illustrates how our solutions can help our customers better understand and manage these threats. Find out how from 11 to 11.30pm.


From 1.30 to 2.20 pm David Shepherd, Solutions Consultant, Micro Focus and Stephen Mogg, Solutions Consultant SUSE discuss how Micro Focus and SUSE could help customers meet escalating storage requirements and costs with secure, scalable, highly-available and cost-effective file storage that works with your current infrastructure. If that would help you, then check out The Race for Space: File Storage Challenges and Solutions.


Immediately after that, our COBOL guys, Scot Nielsen, Snr Product Manager and Alwyn Royall, Solutions Consultant, present Innovation and the Next Generation of COBOL Apps. It’s a demo-led look at the future that show the way forward for modernising COBOL application development and deployment in new architectures. So if you are ready for new innovation from older applications, get along to see that between  2.20 to 3.10 pm.

Networking opportunities?

Of course. Whether you are enjoying refreshments, post-event drinks – or your complementary lunch – alongside industry representatives, product experts and customers, visiting the pods for demos or roadmap walkthroughs, then the whole day is a refreshingly informal way to resolve your technical questions or business challenges. Alternatively, ask your question of the expert panel at the Q & A session at 3.45 to 4.15 pm.

PH House

In summary

Our promise to delegates is that after a visit to #MFSummit2016 they will be in a better position to navigate the challenges of business and IT change.

Wherever you are in your IT strategy, Micro Focus solutions enable our customers to innovate faster with less risk and embrace new business models. #MFSummit2016 is our opportunity to show you which solutions will work for you, where – and how.

Sounds attractive? You’ll really like our stylish venue, Prince Philip House. It is handy for Piccadilly, Charing Cross and St James’s Park Tube stations. Attendance is free, but book here first.

I’ll be speaking from 9.30. See you there?

Federal IT Modernization doesn’t have to be taxing

Ed Airey examines the recent and untimely IRS systems outage, the speedy recovery and the agency’s future aspirations of modernization– all just in time for tax season.

IRS Offline?

Did you catch the big IRS announcement? On 2 February and less than 12 weeks before the US tax filing deadline, a temporary but comprehensive computer systems outage took out many of its tax processing platforms. No 2015 tax returns could be filed electronically, a problem potentially impacting 27 million taxpayers. Additionally, refunds from 2015 returns would be delayed.

IRS tax payment processing systems are now back online and the agency has promised that the US taxpayer will feel minimal impact when they e-file their 2015 tax returns. While the delays amounted to no more than 24 hours, everyone is keen to find out what happened – and why?


Who’s to blame?

The agency blamed an underlying hardware failure preventing the processing of electronically submitted, e-file returns. IRS commissioner John Koskinen indicated that all ‘other IRS services’ were available and most taxpayers would receive their refunds within the usual 21 day period after electronic submission.  Helpful comments for sure – less useful was the Where’s My Refund’ web inquiry feature that went offline when most needed.

But the outage still leaves many questions unanswered. Was this event preventable? Are older IT systems truly to blame?  How does the IRS avoid a similar event in the future?

Fact and Fiction

Fact: Hardware failures occur in every sector.  In many cases, mitigation rather than prevention is the watchword. So, did the IRS have no disaster recovery or failover systems? Not according to IRS officials; these systems continue run on isolated, older computing platforms running application programming languages such as COBOL. Funding cuts have delayed most application modernization projects and some media outlets and a few IRS officials have blamed the agency’s continued use of ‘older’ and ‘outdated’ technologies such as COBOL.

Unfortunately, their fact is mostly fiction. Take online or mobile banking. Most of us want to interact with our bank when we want on our preferred device.  But have normal banking practibces significantly changed your banking providers’ processes just because you’re interacting with them digitally?  Not really. Core banking processes are regulated and rarely change. While your bank has provided a new way for you to interact with their services, the backend processes are generally the same.

The same is true of booking an airline ticket.  Behind the mobile interfaces of Expedia, Travelocity, and Kayak is a core airline booking system that manages ticketing across the various airline carriers.  We experience the colourful overlay of a core system which has been in place for decades.


And what do banking apps and airline booking systems have in common?  They both leverage core business applications written in that multi-decades old programming language, COBOL.

Yes, COBOL – the original programming language remains one of the most portable, flexible and scalable languages in the industry, particularly where high volume transaction and data processing is required at rapid speed. There are few viable alternatives. Perhaps this why the IRS continues to rely on its COBOL applications – they work, and work very well.


The Move to Modernize

So, could COBOL, really be a contributing factor to the IRS’ system availability issues?  No. Blaming the programming language is as convenient as it is unhelpful What’s needed is a comprehensive modernization strategy that blends core strength, namely the current business rules and application logic, with next gen technology and platforms. This enables faster innovation with less risk. The IRS has a successful application portfolio – a suite of feature-rich, high performant transaction processing applications built for scale, speed and precision – to move into the future.

They could easily be ported to new platforms including distributed environments, .NET, the Java Virtual Machine or even the Cloud. This would provide new channels and enable a greater elasticity to meet increased future demand or negate unexpected IT failures. The IRS’ application investment could be extended for decades to come.

It’s been done before

Check out the COBOL modernization initiative at the US Small Business Administration, an agency now well positioned for future growth and leverage next gen technology. Or how about the City of Miami or Marin County, CA who have also undertaken similar COBOL application modernization projects? Modernizing core business systems is can be straightforward and almost risk-free and it all begins with a strategy geared towards leveraging past success and unique attributes.

Innovation Awaits

So, what’s next for the IRS?  With all systems now back online, its busy processing returns and issuing tax refund payments. But is the agency prepared for its next outage?  Will they have the modernization plan needed to mitigate foreseen and unexpected challenges?  There are many paths to modernization, but only one approach will truly enable the IRS and others to modernize core business systems while preparing for the future.

It’s time to turn yesterday’s investment into tomorrow’s new innovation.

SHARE-ing is caring

SHARE began as the first-ever enterprise IT community user group back in 1955 and is still going strong. The upcoming San Antonio event looks certain to be another great success. Here’s a sneak preview of the event and agenda.


Since 1955 SHARE has provided education, networking opportunities and influence for the Enterprise Information Technology Community. It’s still voluntary and for 61 years its mission has remained steadfast; at its core it’s all about professional networking, Mainframe technology, education, professional growth and growing a strong community of like-minded technologists. And just like Mainframe technology, it’s moved with the times – check out the cool new look website complete with Social Media integration and you’ll see what I mean.

SHARE new look

The Dev is in the detail. Mainframe and COBOL AppDev

As proud members of the Mainframe and COBOL community Micro Focus has maintained a steady presence at SHARE events over the years. We’re now a bigger company that boasts SUSE Linux in our portfolio but does that make the event any less important for us? Absolutely not –both Micro Focus and SUSE will be at upcoming San Antonio event in March.


We’ve spoken a lot recently about the digital age and how (and often contrary to popular perception) this is underpinned by so-called ‘legacy’ technology. SHARE provides a great opportunity to explore modern Enterprise computing challenges and how the mainframe world continues to meet them head on. This year SHARE has its own dedicated DevOps track, signalling the importance of this discipline as a topic in the ongoing Mainframe debate.  My colleague Ed Airey is looking forward to hosting his DevOps session ‘The Dev is in the detail: Appdev, DevOps and the IBM Mainframe’ and hopes to see many delegates join in to discuss how that discipline is shaping up. In his own words Ed explains: “We always look forward to the SHARE event as a highlight in the mainframe calendar. We are delighted not only to participate in the sessions and the exhibition hall, but also to present our mainframe solution to the SHARE community. Our focus this year on DevOps is in step with growing interest in this topic from the SHARE delegates”

Skills, Education, Rockhopper and Emperor

IT Skills too will be high on the agenda, after all Skills and Education is a core SHARE mission that we jointly spoke about on an IT skills webinar recently.  This year as a bigger Micro Focus we are particularly excited to be going as the value of Linux for enterprise workloads and new app innovation is sure to be the talk of the town.

Linux, at SHARE, has become a consistent topic of interest for its delegates.  IBM’s recent LinuxOne announcement and continued investment in Linux systems will certainly capture attention as well.  The SUSE team will be highlighting their recent capabilities including expanded enterprise grade scalability for core applications. For Enterprise IT shops interested in understanding how to implement Linux for new Mainframe app innovation, SHARE San Antonio won’t disappoint.

mainframe techies

Is it just for the Mainframe and COBOL Developer community?

Absolutely not.  The increasingly popular EXECUforum takes place for industry and commercial executives to come together, discuss key challenges and solutions, and share experiences too. IT Decision makers, Analysts and visionaries will all be there discussing challenges like Big Data, Analytics, Mobile, Skills, Productivity and the highly relevant DevOps methodology.  Micro Focus panellist Derek Britton comments; We are delighted to join the EXECUforum discussion panel this year. Our clients are driving towards DevOps as a means for improved application delivery, and we are helping them in a variety of ways to accelerate their implementation. We are only too pleased to be part of the discussion at SHARE”

San Antonio here we come…

We’re hoping many of our Mainframe and COBOL friends will be going too. Our brilliant #DevDay events are an ongoing testament to the value that face-to-face events bring to the Enterprise Tech community. Please stop by our booths to say hello to the Micro Focus and SUSE team who will be very keen to hear about your experiences. We’d also be honoured to see you at our sessions:

Our SUSE specific sessions:

What’s New with SUSE Linux Enterprise Server for z Systems (see session details and add to your agenda here)

SUSE Manager at Large Scale (see session details and add to your agenda here)

DevOps specific sessions:

The Dev is in the detail: Appdev, DevOps and the IBM Mainframe (see session details and add to your agenda here)

DevOps:  Cultural Mindset (see the EXECUForum agenda here)

See you there, whether you’re planning to attend for a day, or the whole week…..

CVuJ_79UkAA1OOO.jpg large