Net Cobol To

Overview Fujitsu Software's migration solutions give you the opportunity to: •

• •

•

Achieve Agile IT organizations - by migrating your COBOL applications off expensive mainframe environments to much more cost effective .NET platforms, in ways that position these applications for future enhancements in line with the latest technological developments. Reduce maintenance costs in the range of 60 to 90% - by using the much more price competitive Intel/Microsoft platforms and the highly productive environment and tools of Visual Studio .NET. Accelerate delivery of new application features - by the proven RAD capabilities of Visual Studio .NET (speeding development by up to 80%) and our migration of transaction-supporting applications to ASP.NET or WinForms so that these applications can be part of the latest developments. Retain program and programmer assets - Existing COBOL code is preserved and the value of both program and programmer is increased as they can achieve new results in the .NET environment. - Programming staff motivation is increased as they are provided with leading-edge development tools and are working in the mainstream of today's Internet-oriented technology.

These benefits put Agile IT in your future, summarized in the following diagram:

The 80/20 split of maintaining and enhancing before and after migration is used as an illustration. Each organization will have their own ratio of how resources are split. The main point is that migration can produce radical shifts in the maintaining/enhancing balance.

Reasons for Migrating to the .NET Platform Organizations use Fujitsu Software's migration to Windows/.NET for a variety of reasons including: • • • • • • •

The mainframe is consuming too large a proportion of their budget: - Business survival or competitiveness threatened. - Difficult to respond to market changes or opportunities. Their mainframe is old and needs to be replaced. Quoted cost of upgrading is too high so alternatives are being sought. They have too many different platforms, usually because of acquisitions, and need to consolidate. .NET is seen as an attractive option for at least some of the applications. The mainframe or operating system is being phased out (such as VSE) or has an uncertain future so applications have to be migrated to a different platform. They have experimented with J2EE and found that their programmers (particularly those experienced with its legacy systems) have not been productive in the J2EE environment. Some applications have already been replaced by packaged software on other platforms, leaving just a few applications on the mainframe - too few to justify its existence. They find that hardware and software coming from a single vendor creates limited technological innovation. They desire to use hardware and software from a healthier, more competitive market. This applies to both the developer tools and the program execution environments.

If your situation is close to any of the above, read on to discover how Fujitsu Software can help you find the right track. Migrations Generally our migrations start with a proof-of-concept project to demonstrate that the proposed solutions work for the customer and perform at or above their desired criteria. From the proof-of-concept we move to a pilot project in which a selected application is migrated and put into production. Following the successful completion of the pilot, the full migration is planned and can be performed in-house using our tools or, more commonly, by our consultants or SI (System Integrator) partners. There are several advantages to engaging our consultants or partners: • • • •

Your migration is performed by migration experts You don't have to wait for your staff to learn the details of the new platform before starting your migration. Your programmers can learn the new system while taking control of the application testing - by the time the system is released they are fully up-to-speed. Your staff continue to maintain and enhance your systems while the migration work proceeds - you don't have a migrate-or-enhance choice to make.

Our main migration offerings are described on the pages linked from the following list. However, if your migration needs do not appear to be covered, it is still worth contacting us as our consultants are always expanding the range of software we handle. • • •

Migrating CICS to Microsoft's .NET Framework MVS and DOS/VSE Batch to Windows Migrating IDMS, IMS or VSAM Data to SQL Databases

•

IBM, ICOBOL, Micro Focus dialects to NetCOBOL

Products Fujitsu Software's mainframe migration solutions are built on our NetCOBOL compilers, the NeoKicks, NeoBatch, and NeoSort products that are designed to speed the migration process while positioning the applications for future growth. EZ Source helps you analyze the application before migrating, as well as enhancing your maintenance operations after migrating. Full details of these products can be found on their product pages. Below are short overviews explaining how each product fits into our mainframe migration solutions. NetCOBOL for .NET NetCOBOL for .NET provides the foundation for migrating CICS applications to an exciting future. It is tightly integrated with Visual Studio .NET and generates standard, verifiable MSIL (Microsoft Intermediate Language) code so programs can take full advantage of the rich .NET Framework class libraries in a memory-safe manner. The integration with Visual Studio .NET provides a highly productive COBOL development environment. Features of NetCOBOL for .NET that make the biggest difference for developers coming from mainframes are: • • • • •

Immediate help and syntax checking provided by IntelliSense as code is entered Powerful interactive debugging enabling quick bug resolution and deeper program understanding Fast, visual interface design with Visual Studio's designers Greatly increased programming power with the thousands of classes and methods available in the .NET Framework Ability to take advantage of OO programming techniques

NeoKicks™ NeoKicks is designed for migrating CICS applications to the .NET environment, providing a similar system architecture while enabling the applications to take maximum advantage of the modern interfaces and technologies provided by the .NET Framework. You can convert BMS maps into ASP.NET Web page or WinForms interfaces, yet preserve mainframe style keyboard input. This often allows companies to transform one of the most inflexible parts of their application architecture to a modern, agile architecture. NeoKicks integrates with Visual Studio .NET and NetCOBOL for .NET to provide a highly productive maintenance and enhancement environment for CICS applications. NeoBatch™ NeoBatch is the long term solution for migrating mainframe JCL to the Windows/.NET environment. It executes JCL under the control of the NeoBatch Job Manager in a manner that is highly compatible with mainframe batch job execution. You can choose to maintain your batch jobs as JCL or have them transformed to Microsoft® JScript® as a route to greater .NET/Windows® operating system integration in the future. Features such as the NeoBatch catalog manager, support for generation data groups (GDGs), IEBGENR, IBR14, IDCAMS, NeoSort integration for DFSORT® and Syncsort® commands, highly usable console window and mainframe print file support, make NeoBatch one of the best options for the future of your batch jobs. NeoSort™ NeoSort is a specially packaged version of Nsort™, the world’s fastest sort program, that integrates with NeoBatch to support IBM® DFSORT® commands within migrated JCL jobs. Because NeoSort takes advantage of all the hardware made available to it – such as multiple processors, multiple disks, and memory – it can deliver exceptionally fast sorts of even your largest files. With NeoSort you can improve the performance of your batch sort jobs by migrating to the .NET platform. EZ Source™ EZ Source is an application analysis and understanding tool. It analyses all components of mainframe applications (COBOL source, screens, database definitions, JCL etc), populates a relational database repository and provides a variety of reports and graphical views that can be used to explore the application. Because EZ Source provides a "Missing Components Report" that identifies any resources that are required to complete the analyzed applications, using EZ Source is a good first step to ensure that your migration plans include all parts. Once you know you have all the pieces you can then use EZ Source to check for any challenges in the code so that you have an accurate estimate of the work involved in the migration project. Services

Often organizations seek assistance in making the move from mainframe to Windows server as the migration effort is seen as a one-time process, requiring specialist skills that are not required for the organization's regular IT work. Fujitsu Software provides training; consulting and mentoring services in the area of mainframe migrations that can help start larger projects or perform smaller migration projects. Fujitsu Software also partners with a number of system integrators that offer specialized migration services and who are capable of handling projects of any size.

Migrating CICS to ASP.NET This page provides highlights that should help you determine if you want to explore the migration in more detail with Fujitsu Software. Fujitsu Software's solution for migrating CICS applications to the .NET Framework uses Fujitsu's NeoKicks product. This provides tools that process the CICS COBOL and BMS source files to produce programs and forms that work with NeoKicks services within the .NET Framework. The services provide a similar environment to mainframe CICS so that application architectures are preserved, as illustrated in the following two diagrams, and explained below:

Figure 1: Standard CICS Architecture Figure 2: NeoKicks Architecture Execution-time support: At the core of both CICS and NeoKicks are the services they provide to the application programs. NeoKicks provides a similar environment to mainframe CICS in which users can enter transactions, causing the application programs to be loaded which then invoke services, initially coded using EXEC CICS statements. The main differences are that NeoKicks is executing within the .NET Framework and may have a slightly different plug-in component architecture. Pseudo-conversational model: The architecture of ASP.NET Web pages (Web forms) is very similar to that of mainframe CICS. Users are given the impression they are having a continuous conversation with an application program, but in actual fact the programs relinquish control when information is sent to the user and are essentially restarted, with some kind of session state provided to indicate the stage reached in the processing, when the user takes an action that sends information back to the server. NeoKicks provides equivalent functions to SEND and RECEIVE MAP along with maintaining CICS-compatible communications and storage

areas so that the structure of your COBOL CICS applications doesn't have to change. The design of the .NET Framework also makes it possible for NeoKicks to support Windows Forms at the front end of NeoKicks applications - still working in a pseudo-conversational manner with the back-end application logic. Separate interface and application logic definitions: With CICS applications interfaces are defined using BMS macros and the application logic is contained in the COBOL code. NeoKicks mirrors this separation by converting the BMS macros to Web or Windows forms, with these forms being driven by the migrated COBOL programs in the pseudo-conversational manner described in the preceding paragraph. "EXEC CICS" translated to service calls: On the mainframe the CICS translator converts EXEC CICS statements into calls to "DFHEI1" with parameters indicating the required function and passing the necessary data. Similary the NeoKicks preprocessor invoked by the NeoKicks Project Wizard, converts EXEC CICS statements into calls to "NKServices" (actually INVOKE statements as the NeoKicks services are methods of .NET classes) with parameters indicating the required function and passing the necessary data. The only difference is that whereas you invoke the CICS translator before every compile on the mainframe, you are more likely to use the NeoKicks preprocessor just once when setting up your NeoKicks project. You enhance your NeoKicks converted COBOL code by either coding the NKService INVOKE statements directly or by using other .NET Framework class library functions. Separate configuration files: Both CICS and NeoKicks provide utilities to set up information required at runtime such as transaction ID to program mapping and data file information. For CICS the setup information is stored in files such as the FCT and PCT. For NeoKicks the information is stored in the application's .config file. Links to database and file systems provide transactional support: By integrating with a COBOL file system and database system both CICS and NeoKicks are able to provide commit and rollback transaction support. DPL simlar to Web services: The CICS Distributed Program Link (DPL) is a similar concept to Web services, just that the latter has been designed for general consumption on the Internet. NeoKicks makes it easy to migrate CICS programs designed to work with DPL to Web services within the .NET Framework. Because the CICS architecture maps so conveniently into the .NET Framework, with the help of NeoKicks, migrating your CICS applications to .NET and giving them a new life in that environment is a very straightforward process.

Migration Processes The basic steps involved in migrating a CICS application to NeoKicks are: 1. Start Visual Studio .NET and invoke the NeoKicks Wizard by creating a new project and selecting the NeoKicks Project Wizard template. 2. Point the Wizard to your COBOL and BMS source files, and select other configuration options offered in the Wizard dialogs. 3. After completing the information requested by the Wizard, it preprocesses your COBOL source, converting EXEC CICS statements to invoke NeoKicks services, converts the BMS maps into ASP.NET Web forms or Windows forms, and sets up a Visual Studio .NET solution ready for you to start working on your converted application. 4. Data is migrated to new database structures ? usually with little change required to VSAM or SQL procedural statements. 5. If necessary syntax adjustments are made to ensure the programs compile successfully with NetCOBOL. Our consultants are familiar with the details of these steps so can quickly transform CICS applications into NeoKicks, Web-based or Winforms-based applications.

User Interfaces Our CICS migration solution provides two big benefits in the user interface arena: • •

The migrated interfaces look identical to the original interface but are now made up of GUI controls. When you and your users are ready you can switch to a GUI look and feel and start enhancing the interfaces with new gadgets.. Considerable effort has been made to preserve the keystroke interactions so that users will hardly notice any difference when

their screens are switched from the old to the new. You can see how screen layouts are maintained in the following before and after snapshots:

Figure 3: Example CICS application interface before transformation

Figure 4: Example CICS application interface after transformation as an ASP .NET page

Figure 5: Example CICS application interface after transformation as a Windows Form

Further Information NeoKicks and NetCOBOL for .NET are described fully on their product pages. If any CICS migration also requires the migration of associated batch jobs, see MVS and DOS/VSE Batch to Windows. Email [email protected] if you have any specific questions or would like someone to call you to discuss migration options.

Migrating MVS/DOS/VSE Batch to Windows If you are considering moving CICS applications to an Intel/Windows-type server or whether you can take all your applications off an IBM mainframe, it is highly likely that you will have batch jobs that need to be migrated. Many batch jobs perform mission-critical tasks that need to be executed within a limited time window. Consequently any software that is going to run your batch jobs day-in and day-out needs to be highly reliable and fast. Most batch jobs are made up of three elements: • • •

JCL jobstreams (and associated PROCS and invoked utilities like IDCAMS) Sort steps (part of the JCL jobstreams) Batch COBOL programs

Sorts are listed separately as they are often a major part of the process so need to be performed in a highly efficient manner. The combination of NeoBatch, NeoSort and NetCOBOL for .NET provides the speed and reliability required for migrating MVS batch jobs. In addition the design of NeoBatch provides an excellent route for on-going enhancements that take advantage of new technologies added to the Windows environment. Migrations from DOS or VSE require an initial conversion to MVS JCL using 3rd party services.

Surprising Speed Windows supporting hardware today provides highly competitive price-performance ratios. Combine a powerful server with NeoSort, NeoBatch and NetCOBOL, and you will likely be surprised at the speed with which your batch jobs execute – faster than they executed on the mainframe. Some companies report jobs running two to five times faster.

Migration Processes The basic steps involved in migrating a batch application to Windows are:

1. Download and convert your data files from EBCDIC to ASCII and from their mainframe structured formats to their NetCOBOL or PC database equivalents. Fujitsu’s Data Converter tool can be useful in this process with field-sensitive COBOL file conversions. 2. Import your datasets and jobs to NeoBatch using the NeoBatch import wizard 3. As on the mainframe you may need to set up your datasets using special batch jobs – particularly if you are using Generation Data Groups. 4. Compile your COBOL programs, making any syntax adjustments necessary to work with the NetCOBOL compiler. 5. Use NeoBatch Job Manager to submit your batch jobs and see the familiar output in the Console pane. Our consultants are familiar with the details of these steps so can quickly transform mainframe batch applications into fast, production-ready applications running in the Windows operating system.

Further Information NeoBatch and NetCOBOL for .NET are described fully on their product pages. If your batch jobs are tightly integrated with CICS transactions, see Migrating CICS to ASP.NET.

Migrating IDMS, IMS or VSAM Data to SQL Databases Together with our business partner, ATERAS (formerly Sophisticated Business Systems), Fujitsu provides you with the ability to migrate your IDMS, IMS or VSAM data to SQL databases in the Windows or .NET environments. IDMS migrations use the fully automated processes of ATERAS' DBShuttle™ technology. IMS and VSAM migrations require some configuration of the technology that is provided by Fujitsu and ATERAS engineers. Migrating to modern relational databases not only makes some migrations possible but can also be a great leap forward in functionality and future potential for your applications. This page provides an overview of the benefits and processes involved when you take advantage of these services.

Benefits For IDMS/IMS Database Migrations • • • • •

If you are already considering migrating your mainframe applications to the Windows or .NET environments these data migration solutions may be the key to formulating a successful migration path Move from a proprietary database system to a form that is common across many vendors Switch from needing vendor-specific skills to vendor-independent skills Benefit from the availability of flexible reporting options Be using database technology in the area that is receiving the greatest attention from database companies

For VSAM Data File Migrations VSAM data formats are supported in the Windows/.NET products but often companies are interested in migrating to SQL databases to: • • •

Consolidate VSAM data in a single database system rather than being spread across multiple files Consolidate data if the current system uses a mixture of data organizations - SQL database as well as VSAM data files Obtain the flexible reporting options and access to common SQL-related tools mentioned in the IDMS/IMS list

Migration Processes Generally Fujitsu is involved with IDMS/IMS/VSAM data migration/modernization projects as part of a total mainframe-to-Windows-server migration project. Such projects therefore require coordination between the code and data migration efforts. Each project has its own characteristics and influences whether the data modernization is performed before, after or at the same time as migrating the COBOL programs to Windows servers. Fujitsu assesses the situation, together with ATERAS, and recommends the best strategy for accomplishing your migration goals. Depending on the size of project and your preferences, we can train your engineers in the migration processes, have our consultants perform the migration, or recommend a system integrator with the appropriate skills.

Further Information See ATERAS' description of their solutions at their Website. Email [email protected] to have one of our representatives call you to discuss migration options.

Migrating from Other Dialects to NetCOBOL In order to provide functionality not provided by the COBOL standard, vendors have often implemented extensions to the COBOL standard syntax. Programs that use those extensions can be more difficult to migrate to another language as not all vendors support the same extensions. Fujitsu Software helps you migrate your COBOL applications to NetCOBOL with the following: • •

•

The NetCOBOL compiler supports many common IBM and Micro Focus COBOL extensions to the language such as "COMP-5" and 78 level items. We have contracted with Siber Systems, a company that has specialized in COBOL transformations, to create converters that transform IBM, Micro Focus and ICOBOL syntax into NetCOBOL equivalents. Because of the complexities of some of the conversions we only provide the ICOBOL converter with our consulting services. Offering consultants who are experienced in handling the language differences and in using the syntax converters.

As with other migrations, using our consultants is often the most expedient way of executing these migrations as your developers can stay focused on supporting your business while our consultants apply their COBOL migration knowledge.

Further Information The Dialect Converters are described fully on their product pages. Email [email protected] if you have any specific questions or would like someone to call you to discuss migration options.