|
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:
- 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.
- Import your
datasets and jobs to NeoBatch using the NeoBatch import wizard
- As on the
mainframe you may need to set up your datasets using special batch
jobs – particularly if you are using Generation Data Groups.
- Compile
your COBOL programs, making any syntax adjustments necessary to
work with the NetCOBOL compiler.
- 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.
White paper:
Batch
Applications - The Hidden Asset
If your batch
jobs are tightly integrated with CICS transactions, see Migrating
CICS to ASP.NET.
|
