Download Datasheet
NeoBatch by Alchemy Solutions
Execute JCL on Windows®
Drastically reduce batch processing times. NeoBatch moves mainframe JCL batch jobs and sort processes to high-performance, economical Windows® servers. The stand-alone application lets you execute, monitor and manage jobs through an easy-to-use graphical interface.
System Requirements
There are three types of installations available for NeoBatch. Each requires a different license. The Server and Developer installations and registrations must be performed with local Administrator privileges.
- The Server edition allows a system to act as a NeoBatch server for other remote (Client and SDK) systems. A server can also operate in SDK mode for debugging purposes. NeoBatch version 2.0 and higher supports a variety of NeoBatch server configurations:
- Single NeoBatch server with the SQL Server database on the same computer.
- Server farm with multiple NeoBatch servers load balanced using a job scheduler, with the SQL Server database on a different computer.
- Server farm with multiple NeoBatch servers load balanced using a network load balancer, with the SQL Server database on a different computer.
- The Developer (SDK) installation allows a system to operate in local mode, where the system is its own server. It cannot act as a NeoBatch server for other remote client (Client and SDK) systems, and the SQL Server database must reside on the local system. An SDK installation can act as a client by connecting to and executing jobs on Server installations.
- The Client installation allows a system to connect to a NeoBatch server. Client installations cannot execute jobs locally – they can only connect to and execute jobs on server installations.
Developer (SDK) Edition
Hardware requirements (minimum)
- Intel® Pentium® 4 or higher, or AMD equivalents
- 1 GB RAM recommended (minimum)
Software Requirements
- Microsoft® Windows XP® with Service Pack 2 or higher, Windows Vista®, Windows 7, Windows Server® 2003 R2, or Windows Server 2008 R2
- Microsoft SQL Server® 2005 Developer’s Edition, or SQL Server 2008 Developer’s Edition, installed on the local system.
- Microsoft Windows PowerShell version 2.0 or higher is required to run PowerShell jobs. (PowerShell is not required to run JScript jobs.)
- Fujitsu NetCOBOL® for .NET, Microsoft .NET Framework, and Microsoft Visual Studio® (for developing .NET COBOL programs) in any of the following valid version combinations:
| NetCOBOL for .NET |
.NET Framework |
Visual Studio |
| NetCOBOL for .NET version 4.1 |
.NET Framework 4 |
Visual Studio 2010 |
| NetCOBOL for .NET version 4.0 |
.NET Framework 3.5 |
Visual Studio 2008 |
| NetCOBOL for .NET version 3.1 |
.NET Framework 3.0 |
Visual Studio 2005 |
| NetCOBOL for .NET version 3 |
.NET Framework 2.0 |
Visual Studio 2005 |
*Visual Studio Shell is bundled with NetCOBOL for .NET; other editions of Visual Studio must be purchased separately.
- Fujitsu NetCOBOL for Windows version 8 or higher (if developing native Win32 COBOL programs)
- Microsoft Message Queuing (MSMQ)
- Alchemy Solutions NeoData or Pervasive® Btrieve® Workgroup edition or higher (optional)
Notes:
- The Developer installation and registration must be performed with local Administrator privileges.
- The Alchemy Solutions NeoData product has the ability to emulate VSAM file access mechanisms for data stored in SQL Server, and requires the Fujitsu NetCOBOL for .NET Runtime.
- Btrieve and the NetCOBOL file system are supported data access mechanisms for COBOL indexed files. Relational database access is supported using ODBC drivers supported by NetCOBOL for .NET. The Fujitsu NetCOBOL for Windows runtime or compiler is required only if you will be using indexed files and Btrieve is not installed.
Client Edition
Hardware requirements (minimum)
- Intel Pentium 4 or higher, or AMD equivalents
- 1 GB RAM recommended (minimum)
Software Requirements
- Microsoft Windows XP with Service Pack 2 or higher, Windows Vista, Windows 7, Windows Server 2003 R2, or Windows Server 2008 R2.
- Microsoft .NET Framework version 2.0 or later
- Microsoft Message Queuing (MSMQ)
Server Edition
Hardware requirements (minimum)
- Intel Pentium 4 or higher, or AMD equivalents
- 1 GB RAM recommended (minimum)
Software Requirements
- Microsoft Windows Server 2003 R2
with Microsoft Internet Information Services (IIS) 6.0
-or-
Microsoft Windows Server 2008 R2
with IIS 7.0 or higher and IIS 6 Management Compatibility tools, including IIS 6 Metabase Compatibility, installed
- Microsoft SQL Server 2005, or SQL Server 2008
- Microsoft Windows PowerShell version 2.0 or higher is required to run PowerShell jobs. (PowerShell is not required to run JScript jobs.)
- Fujitsu NetCOBOL for .NET runtime and Microsoft .NET Framework (with the ASP.NET 2.0 web service extension enabled in IIS) in any of the following valid version combinations:
| NetCOBOL for .NET |
.NET Framework |
| NetCOBOL for .NET version 4.1 |
.NET Framework 4 |
| NetCOBOL for .NET version 4.0 |
.NET Framework 3.5 |
| NetCOBOL for .NET version 3.1 |
.NET Framework 3.0 |
| NetCOBOL for .NET version 3 |
.NET Framework 2.0 |
Note: The NetCOBOL for .NET v3.1 or later External File Handler (x64) is required for the 64-bit edition of NeoBatch.
- Microsoft Message Queuing (MSMQ)
- Alchemy Solutions NeoData or Pervasive® Btrieve® Workgroup edition or higher (optional)
Notes:
- The Server installation and registration must be performed with local Administrator privileges.
- The Alchemy Solutions NeoData product has the ability to emulate VSAM file access mechanisms for data stored in SQL Server, and requires the Fujitsu NetCOBOL for .NET Runtime.
- Btrieve and the NetCOBOL file system are supported data access mechanisms for COBOL indexed files. Relational database access is supported using ODBC drivers supported by NetCOBOL for .NET. The Fujitsu NetCOBOL for Windows Runtime or compiler is required only if you will be using indexed files and Btrieve is not installed.
Request Pricing
