Learn how we’ve minimized the work required from programmers using Compuware Source Support best practices.
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.
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.
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.
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.
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.
Incremental development will soon be required for federal departments and agencies to receive adequate funding for projects, per the MGT Act if it is passed. Considering that, federal IT should follow these steps to becoming Agile.
When the Federal Government needs to be optimizing tax dollars for government systems, how does an effective CIO make the choice of when to migrate mainframe applications to the cloud?
Today’s visit from Chairman Chaffetz and Congressman Walberg exemplified the time commitment they have to investigating and understanding technology issues the Federal Government faces.
Rather than assuming all of the Federal Government’s older IT systems are outdated or obsolete, federal technologists must consider where they can improve existing systems that still function better than alternative platforms.
During the congresswoman’s visit, Compuware executives and employees showcased the company’s ability to modernize the mainframe with the Agile culture, processes and tools necessary for success in a constantly shifting digital age.
There’s no question the mainframe is the most powerful backend data transaction system for enterprises and, yes, our United States government.