Jump to NetCOBOL

NeoBatch

  1. What products are required to support NeoBatch?

    Answer: SQL Server 2000 or later is required to support the NeoBatch catalog.

  2. Do I need to make changes to my JCL to make it work with NeoBatch?

    Answer: One of the main design goals of NeoBatch was to minimize the amount of manual effort needed to migrate your JCL applications. If you have existing MVS JCL, you should find that the majority of your JCL requires absolutely no changes. With support for advanced JCL commands like PROCs, you can expect very little manual recoding. For a list of unsupported commands and parameters, please consult the NeoBatch documentation.

  3. Are there changes required to COBOL code to make the applications consistent with NeoBatch?

    Answer: NeoBatch executes many types of files as job steps. For example, a step could be a COBOL application, a .BAT file, or even something like the “dir” command. For your existing COBOL applications, if they are compiled and built with NetCOBOL for .NET or NetCOBOL for Windows, no code changes should be required.

  4. What performance should I expect from my batch jobs running under NeoBatch?

    Answer: Job performance varies tremendously depending on what the job is doing. Certain types of job steps, such as sorting, perform much faster off the mainframe. Given the myriad different mainframe configurations, we would be remiss to try to say precisely how fast your jobs would run on Windows. But suffice to say, all of our customers experience performance increases when migrating to appropriately sized hardware.

  5. Which databases can I use with NeoBatch?

    Answer: The NeoBatch catalog requires SQL Server 2000 or later.
    Applications can use any database that works with NetCOBOL for .NET. This can be any ODBC compliant database.

  6. Which job schedulers does NeoBatch support?

    Answer: NeoBatch provides a suite of command line tools for submitting jobs, cancelling jobs, purging sysout data, etc… Most job schedulers are capable of launching command-line programs and reacting to the result of the return codes provided. For advanced scheduling integration, we also provide an API with even more flexibility.