Hi all,

Building a development team environment during your mainframe modernization journey is getting easier and easier with tools doing more and more on the customization front. However, it is important to note that in order to successfully create a reliable and dynamic development team environment on an alternative platform other than the mainframe you will need to know exactly what projects and related applications to modernize. Starting with small projects is always a good way to begin your journey.

Remember that the steps here are a guideline only and you can always adapt to what your goal is and the requirements of your project. Let’s being our journey!

Understanding the mainframe application

One of the most important factors during your modernization journey is to grow the knowledge you have regarding your existing mainframe applications. Over the years, legacy mainframe applications have accumulated a considerable amount of critical business functions that differentiate organizations from each other. Common sub-routines were created and data was stored in many different storage types, realizing the complex logic flows and other requirements that allow mainframe applications to successfully support the business to this day. It is also true that with the legacy systems evolution over time, many of the "business functions" are left untouched because they simply work. Once that happens, much of the knowledge won't get transferred to other developers or business analysts. Additionally, in order to create a flexible and adaptive development environment, it should include customizations to execute\\debug mainframe applications as if they were on the mainframe, such as access to the right load libraries, databases, files, OLTP customizations, etc. Thus, acquiring better knowledge of the application you want to modernize is key to the entire process.

Now, don't be alarmed if you are wondering how this task can be achieved. We know that by the time you would complete the task of knowledge gathering for medium to large mainframe applications, your work will be already somewhat outdated. To alleviate this risk , there are great products that will help you automate the process of gathering and centralizing your mainframe application knowledge. Micro Focus has Enterprise Analyzer that will help analyze your mainframe applications and quickly produce all the knowledge you need in order to understand which resources you will need to customize when building your development team environment.

With Micro Focus Enterprise Analyzer, you will see the critical business functions associated with the application you wish to modernize, programs and sub-routines associated, complexity level, files and databases, etc.

Hang on to all that great information, as you will be using the information to take many decisions when customizing the team development environment.

Customizing your Micro Focus Development Environment based on your Mainframe

Now that you know how your mainframe application is composed, and all the programs, sub-routines, JCLs, databases, OLTP customizations necessary to build your team development environment, some important decisions will need to take place.

1.      File transfer

How would like to have your file transferred to our team development environment? There are several options, I will list some and you will probably have other alternatives as well. Select what fits better for your environment

• File Transfer Protocol (FTP)

This is the transfer methodology used by default because of its availability on most systems. It can easily transfer ASCII/Text files and has the capability to transfer record sequential files in binary mode.

To transfer VSAM, key-sequenced-data-sets (KSDS) require the file to be converted to a sequential file (using IDCAMS and REPRO). The sequential file is then transferred to the target system in binary format. The received file is then used as the base for conversion with the output file being created as a Micro Focus Keyed-Index File. The EBCDIC to ASCII conversion can also be performed at the same time.

• Mainframe Access (MFA)

A solution provided by Micro Focus, MFA provides the simplest method for transferring files from a z/OS mainframe to the Micro Focus Development Environment. The “File Format” conversion is handled by the MFA transfer process. The file transfer may be a simple “Drag-and-Drop” task from the IDE (Eclipse or Visual Studio 2010) interface or an automated, batch process executed from a Windows command line.

2.      Source Control and the Software Development Life Cycle (SDLC)

For controlled and managed development environment source control has a big play to ensure revision and versioning control. I won’t get into why everyone should use a reliable source control solution because that is beyond the goal of this article, but how the source control integrates with SDLC.

Here are some types of SCM available:

• In-House or manual

Found usually in smaller shops, where version and revision control can be done manually. It is also interesting to mention, that some larger development sites have adopted their own solutions due to the adaptation implemented to their own processes over the years, making it difficult to substitute with a more generic solution.

Regardless, Micro Focus Development Environment setup offers lots of flexibility to adapt to the many levels of integration required.

• Established Mainframe Based

The majority of customers are found in this category. They have adopted SCM software and processes that are driven from the mainframe in a centralized fashion, and they wish to keep as it is and other development environment must adapt to the existing process. Some SCM software solutions are CA-Endevor, CA-Librarian, CA-Panvalet, IBM SCLM, Serena Changeman ZMF, and ISPW.

One of the most popular is CA-Endevor, and if that is your solution, Micro Focus Mainframe Access (MFA) software, a mainframe side component of EDTE – fully supports the Endeavor API interface, adhering to any Endevor managed workflow process.

• Established LAN based

The LAN based solution define organizations that have moved away from expensive mainframe based SCM tools and processes. Final deployment is done in the SDLC where a mainframe build is triggered from the LAN based process. Examples of such software include Borland StarTeam, Subversion (SVN), CVS, Microsoft Team Foundation Server and Visual SourceSafe, IBM Rational Clearcase, CA Software Change Manager (CCC/Harvest).

Make sure you understand the SDLC implemented in your organization as to use that information to properly customize the integration of your SCM and Micro Focus Development Environment.

3.      Integrating SCM with Micro Focus Development Environment

When integrating your SCM with Micro Focus Development Environment, there two main topics you need to consider:

1. Synchronization

The proper synchronization between the SCM and the Micro Focus Development Environment will enable developers to carry on the same SDLC process with functions like creation, source availability, build and execution in addition to editing, compilation, debugging and testing. Proper folder and source members customizations will need to take place for the synchronization to happen.

1. IDE developer access

Working with your IDE of choice (Eclipse or Visual Studio) will require that functions like check-in and check-out are executed. When working with Enterprise Developer, the source code will need to be saved into the Enterprise Developer project. See how:

• Mainframe vendor supported

Micro Focus Mainframe Access (MFA) provides Drag and Drop interface support in EDTE for the most used mainframe SCM solutions such as Panvalet and Endevor (for a full list see the MFA User Guide on the SupportLine website). This means that you can check out and check in code directly within the EDTE IDE, providing a complete integrated environment.

• Mainframe non-vendor supported

For the SCMs not supported directed by Enterprise Developer \\ MFA,  there are options such as the use of TSO and ISPF to check items in and out of the SCM control. As a long term solution, you might consult Micro Focus technical services and/or partners for a more customized solution and additional options.

• LAN based

LAN based SCM systems are often the simplest to deal with since GUI software is normally already available to perform all necessary actions on the source members under SCM control. Some are integrated, or have plug-ins, into the EDTE Visual Studio or Eclipse IDEs which allows them to gain access to and perform SCM functions on SCM stored items. This is the fastest way to allow developers access to SCM controlled items, providing capabilities for common SCM tasks like checking in, checking out, and viewing differences.

4.      Software Build solutions

Software Build solutions are responsible for compiling the source code into load modules. Depending on whether you have adopted a mainframe vendor or LAN based supported SCM for the Micro Focus Development environment, they would be integrated into the MFA Compare and Synchronize Monitor (SyncMon) process, ensuring the required concatenated load module path is kept synchronized. See the four methods available to achieve this within Enterprise Developer:

1. COBOL command line compile (available in all IDE and platforms)
2. UNIX/Linux Make files (UNIX/Linux)
3. MSBuild in Visual Studio (Windows only)
4. Ant in Eclipse (multi-platform)

5.      Application Lifecycle Management (ALM)

Application lifecycle management is the main umbrella that encapsulates everything that is part of the application lifecycle, from the initial conception of an idea through development, governance, and maintenance and does not end until the application is retired. ALM tools exists to facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management. Because of the integration level of Eclipse and Visual Studio, the Micro Focus Development Environment can be incorporated into the ALM process.

6.      Standard Directory Structure

The standard directory structure is the location where the source code will reside outside of the main SCM system. Creating a folder directory structure on the PC must be done wisely and it will greatly complement the integration of EDTE with the source code, data and any future synchronization needs with other systems of identical or similar configuration.

Here are the key elements designed to create a flexible and consistent environment:

1. Windows Development Workspace.
2. Enterprise Server region.
3. Source Control Reference Structure.
4. Compiler directive files.
5. Enterprise Server Region Data files.
6. Location of compiled code.
7. Project Templates.
8. Creation of Projects.

Micro Focus Development environment makes available EDBaselineSetup tool, created using AutoIT to drive scripts to create and directory structure and deploy the configuration files.

Because of the importance of this section, a separate article will be created to discuss in more detail the standard directory structure.

7.      Building the Baseline

Building the baseline project on top of the directory structure and integrating it with the SCM, requires several steps as you can see:

1. Creating an ED TE Project Template
2. Configuring the Region, including
   1. Importing the default configuration
   2. Exporting & Importing CICS CSD and/or IMS Stage 1 GEN
   3. Setting up listeners
   4. Defining database (XA) definitions
   5. Etc
3. Identifying the Required Source Code
4. Performing the Initial Source Code download
5. Implementing Member Typing procedure (if necessary)
6. Performing Initial Mass Compile
7. Resolving any issues found

This baseline when built forms the project file collecting all the information and the intelligence for the program being edit and debugged, making the development environment with Micro Focus Enterprise Developer an effective and easy to use tool for the everyday development tasks from analysis, generation, editing, compilation, debugging, and testing.

As a continuation to the standard directory structure, building a baseline is an important section that will put together the environment for the developer and as such it deserves an article that talks in details specifically about it. More to come.

Next: Setting up the Micro Focus Development Environment