After you’ve worked through our suggested steps for migrating your COBOL programs to COBOL Version 5.2 or 6.1, it’s time to begin an initial rollout. Here's how.
Moving to a proprietary mainframe Cloud to cut costs is clearly a masquerade for forcing adopters into a rigid, top-down set of point products owned by monolithic vendors who then commandeer complete control of your mainframe environment
During our Bonita Springs CAC, there were plenty of opportunities to observe and listen to mainframe customers’ enthusiasm for new ideas around culture, processes and tools to help advance the mainframe.
Topaz for Total Test automatically creates and executes COBOL program stubs, allowing you to simplify testing efforts through program isolation.
Helping programmers improve COBOL code testing is an absolute necessity considering mainframe programs tend to be the oldest and most important parts of the business.
Here is an overview of the types of performance optimization available in COBOL Versions 5 and 6 and how to identify and use these new COBOL optimization features.
SHARE is the ideal industry conference in that it offers over 500 technical sessions for you to choose from. Here are the top six sessions we attended at SHARE San Jose, based on my colleagues’ and my own experience.
As a first-time attendee to SHARE, the week can feel a bit Doctor Seussian. Based on my experience, here’s some advice to future first-time SHARE attendees.
After hearing about Compuware’s two-platform IT approach, the SHARE organization took interest and asked Keith Sisson to share Compuware’s story and the company's experience with the mainframe at SHARE San Jose 2017.
There is something palpable about the first day of SHARE. Interested in speaking with any of us from Compuware? Stop at booth #407 in the Technology Exchange Expo.
In “Mainframe programming and the modern developer," analyst Daniel Howard writes about his change of perspective regarding the ease of mainframe programming with Compuware Topaz and Topaz Workbench,
Using Abend-AID’s industry unique fault metadata analytics, you can leverage Abend-AID to shift mainframe problem resolution left in the DevOps lifecycle.
A large percentage of COBOL migration problems are data related, so thorough testing is crucial to discovering them. The testing you do now will save you from countless hours of debugging, potentially losing revenue and disappointing your customers.
For companies seeking a flexible guide to Agile transformation, Compuware’s new eBook “10 Steps to True Mainframe Agility” provides them with a proven and phased approach leading to enterprise DevOps success.
As nimble startup competitors gain market traction, it’s imperative that larger companies begin implementing enterprise DevOps to modernize their culture, processes and tools.
Deciding which COBOL release you want to migrate to first and then following through with a stable migration requires a well-researched and carefully considered plan. Here we present the similarities and differences between the two latest versions of COBOL.
The best way to optimize your COBOL programs is to migrate them to the latest version of COBOL. The first part of that strategy involves roadmap planning.
ISPW’s integration of automatic, graphical Impact Analysis is another example of how source code management can be made much more simple and Agile by automating certain aspects of the tool.
Before executing a COBOL to Java on z/OS conversion, there are several unrecognized pitfalls companies should be aware of that render possible savings to be of no consequence.
Companies can improve their legacy code and ensure less risk by moving away from manual processes and using automated unit testing on the mainframe for multiple benefits.