| Feature
Summary |
|
Detail
of Feature |
|
Benefit
of Feature |
Multi-pane, configurable interface |
|
The job manager organizes the display of information into panes, similar
in style to many other Windows tools such as Microsoft’s Visual
Studio. The user can select which panes are visible and how they are
arranged in the Job Manager Window.
|
|
Each operator or developer can arrange the information display in
a manner that works best for them, so that they feel they have the
information they need right at their finger tips. |
| Designed
for production use |
|
The NeoBatch
Job Manager was designed to be convenient to use in production situations.
This not only applies to the user interface but also to the underlying
architecture that separates the NeoBatch Server, which executes the
jobs, from the NeoBatch Client that is part of the Job Manager and
starts the jobs on the server.
|
|
NeoBatch
works well for you where it matters most – in the day-to-day
execution and management of your batch jobs. |
| Control
from the server or client |
|
You can set up
the NeoBatch Job Manager so that it works from either the server on
which the batch jobs are executing or any client connected to the
server.
|
|
Gives
a practical setup for managing batch jobs. |
| Catalog
Import Wizard |
|
The Catalog Import
Wizard guides you through the steps of adding items to the NeoBatch
catalog.
|
|
Makes
it easy to add items to the catalog. |
| My
Jobs pane for frequently used jobs |
|
As
production job catalogs can grow quite large a “My Jobs”
pane is provided so that users can select and organize the jobs they
use most frequently.
|
|
Enhances
operator and developer productivity. |
| Document
Viewer pane |
|
The
Document Viewer pane provides views of the execution results and output.
One of the views is the Console pane that shows similar information
to that provided on the mainframe console.
The output from each job uses a different color for easy identification
when multiple jobs are running concurrently.
From the Console pane you can also select the JCL job you’d
like to update and select output reports to view.
|
|
Provides
familiar and useful view of batch job progress and results for those
involved with both sides of the batch migration. |
| SDK
version supports local execution and debugging of scripts and COBOL |
|
The
developer’s version of NeoBatch supports debugging of both scripts
and COBOL code (by integrating with the Visual Studio debugger) and
works with a NeoBatch server installed on the developer’s computer.
|
|
With
developer and operator working with very similar interfaces, the developer
can see what the operator will see.
Ability to debug both script and code is important in analyzing bugs.
|
| Performance
Monitor pane |
|
Gives
a graphical display of various performance statistics such as:
- Processor
usage
- # of jobs
queued
- # of running
jobs
- # of steps
per second
- Average time
per job
- Average time
per step
|
|
Makes
it easy to monitor critical performance statistics.
|
Feature
Summary |
|
Detail
of Feature |
|
Benefit
of Feature |
Supported statements |
|
/*
//
//*
CNTL/ENDCNTL
DD (and see Special DD statements below)
EXEC
IF/THEN/ELSE/ENDIF
INCLUDE
JCLLIB
JOB
PROC/PEND
SET
|
|
Most common JCL jobs can be migrated to the NeoBatch batch migration
software with very little effort |
| Supported
Special DD statements |
|
JOBLIB
SYSIN
STEPLIB
With some programmer
configuration the following special statements can be readily migrated:
SYSABEND
SYSCHK
SYSCKEOV
SYSMDUMP
SYSUDUMP
|
|
Most
common JCL jobs can be migrated to the NeoBatch batch migration software
with very little effort |
| JCL
parsing |
|
NeoBatch’s
JCL conversion ensures that all JCL processed is correct. |
|
Experience
with legacy migration projects has shown that surprisingly many JCL
jobs contain incorrectly formed statements. Although we hope that
the jobs have been executing as intended on the mainframe it is best
to identify such errors and confirm that the jobs are coded correctly
to achieve the desired results.
|
| Major
utilities supported |
|
Supports
IDCAMS
IEBGENER
IEFBR14
SORT
IKJEFT01(for database connections)
|
|
Enables
file setup and maintenance using established jobs and procedures. |
Feature
Summary |
|
Detail
of Feature |
|
Benefit
of Feature |
Production design |
|
NeoBatch has been designed with the primary goal of providing highly
reliable and efficient execution of batch jobs. |
|
Provides confidence that your batch jobs will execute as intended
and can be relied upon to continue performing the critical functions
they perform today.
|
| Server
farm support |
|
NeoBatch
has explicit support for executing batch jobs on server farms, enabling
multiple jobs to be executed simultaneously on the available servers.
Specific features include:
- Option to
use Kerberos security instead of the standard Active Directory
- Assign initiators
to servers or processors within servers
- Assign initiators
to load-balanced URLs
- Use multiple
characters to define classes (the mainframe uses single letters
for job classes, whereas with server farm support it may make
more sense to use server names for classes or other meaningful
names that reflect the target or function of the job class)
|
|
Helps
you take advantage of scale out server models in which numerous batch
jobs can be executed simultaneously without contending for time on
the same processor. |
| Job
execution |
|
The converted JScripts, that now represent the intended operation
of the batch jobs, are interpreted by NeoBatch and run under the control
of a Job Server Manager. This architecture allows you to manage the
number of jobs that can execute simultaneously.
|
|
Having
a Windows-targeted architecture gives you the most appropriate controls
for your batch jobs in this environment. |
| JCL
parsing |
|
Before being converted/executed JCL is parsed to ensure that it is
valid.
|
|
Provides
a useful check that JCL has been migrated or edited correctly |
| Conditional
processing |
|
Conditional processing Return codes and program failures are checked
so that the appropriate branches can be taken in the JCL. Both IF-THEN-ELSE
and COND are supported.
|
|
Basic
JCL features required for successful batch processing. |
Sort
|
|
NeoBatch integrates with NeoSort to provide high performance sorts
that can take advantage of multi-processor architectures to provide
the fastest sorts on extremely large files.
NeoBatch ensures that the majority of DFSORT options are supported
by mapping them to the equivalent NeoSort functions. Syncsort commands
are supported to the extent that they match the DFSORT commands.
|
|
Sorting
is a frequently used function in batch jobs so having a high performance
sort engine is essential. Manually converting DFSORT commands to work
with another sort utility is a difficult task. |
| Integrates
with job schedulers |
|
The NeoBatch batch migration software is designed so that it can easily
be used with job schedulers such as ActiveBatch® or AutoSys®.
All job execution information can be specified in the command line
or in configuration files.
Success or failure results are communicated by return codes that can
be examined by the job scheduler.
|
|
The
majority of batch jobs are executed regularly at set times so integration
with schedulers is a must for a JCL engine like NeoBatch. |
Abends
|
|
Users are alerted when an abend occurs and can use the detailed information
provided by NetCOBOL to analyze why the abend occurred.
Backs out files that have been allocated when an abend occurs.
|
|
Helps
you take prompt action to rectify problems that cause or are caused
by abends. |
Print
spooling
|
|
NeoBatch supports a pluggable and customizable interface for print
spooling support as well as general support for Windows printing.
Since batch environments often have very specific needs, this interface
offers excellent customization.
|
|
This
feature enables users to quickly add custom print spooling behavior,
such as support for FTP, multiple printers, email, etc. |
| SYSOUT |
|
The
output to SYSOUT is presented in the console pane so that it can browsed.
|
|
This
allows local or remote operators to view the job results. |
| Executes
COBOL batch programs |
|
As
you would expect, NeoBatch executes COBOL batch programs, taking advantage
of hooks in the NetCOBOL runtime system to provide mainframe-compatible
print file layouts and correct program termination codes NeoBatch
supports both NetCOBOL for .NET and NetCOBOL for Windows.
|
|
Provides
high performance, reliable and compatible execution of mainframe-originating
code. |
| Executes
programs written in other languages |
|
Any
Windows executable (.EXE, COM DLL, BAT, CMD, WSH, VBS, JS) can be
executed from the batch jobs. |
|
Gives
an opportunity for organizations that have expertise in other programming
languages to integrate those skills with the existing COBOL legacy
or, if appropriate, to use other languages to access new Windows-based
technologies.
|
APIs
|
|
NeoBatch
provides interfaces that can be invoked from programs for those
who need to tailor certain behaviors or access system information.
Interfaces include:
- ISecurity
- IDbConnector
- IPrintHandler
- ISysout
|
|
Gives
you the ability to tailor systems precisely to your needs. |
| Job
and system logs |
|
NeoBatch
provides logs of similar form to those provided on the mainframe.
The can be viewed using the Document Viewer.
|
|
Provides
the information and form familiar to those who review and analyze
batch job execution. |
| Debugging
support |
|
NeoBatch
integrates with both the NetCOBOL for Windows and NetCOBOL for .NET
source code debugging tools. When debugging batch jobs the source
code can be viewed under the control of the debuggers. |
|
Greatly
speeds the debugging process compared to many of the debugging methods
available on the mainframe. |
Feature
Summary |
|
Detail
of Feature |
|
Benefit
of Feature |
Native character set
|
|
NeoBatch legacy migration supports datasets whose character data items
have been converted to an ANSI Code Page (ACP) i.e. ASCII or a local
variant.
Currently NeoBatch does not support Unicode.
|
|
As Windows is an ASCII environment it makes sense to use ASCII data
(and not attempt to support EBCDIC data in the ASCII environment).
This ensures excellent performance and predictable behavior.
|
| Catalog
Manager |
|
Datasets
are managed using the same names used on the mainframe, using the
NeoBatch Catalog Manager.
|
|
Ensures application compatibility and familiarity in the new environment.
|
| Generation
Data Groups (GDG) |
|
Supports
the MVS JCL generation data group versioning system for datasets (up
to 9999 generations) |
|
Continue
to benefit from the well-proven file versioning system that you use
with your mainframe JCL.
|
|
File locking support |
|
The NeoBatch file support includes the ability to lock files, with
automatic detection of deadlocks
|
|
Helps
set up batch systems with highly parallel job execution.
File locking support, with automatic detection of deadlocks
|
| Relational
data |
|
Relational
data NeoBatch supports:
- SQL Server
- UDB
- Oracle
- Any ODBC
compliant database
|
|
Facilitates
moving data from DB2 and Oracle on the mainframe |
