|
|
Distributed Job Manager
consists of CLCL a full-function job control
language, CLCL is an interpreter and has a
high-level user interface, which allows user to
define how the Job Control
programs are created, managed, and executed. |
|
Through the
use of the high-level interface, user can cause the CLCL
programs to be automatically analyzed, documented, standardized, or
converted. Interface virtually eliminates all CLCL syntax related
errors and provides significantly quicker development,
implementation, and maintenance for the Batch related Software.
Several of our clients that have very sophisticated
batch processing participated in the beta testing of the Distributed
Job Manager. They had realized up to 80% savings (time reduction) in
enhancement and maintenance and up to 70% saving in development for
Job Control Programs.
Downsizing, internet,
business to business transactions, data warehousing and all other
good stuff is upon us. We can safely say that revolution in data
processing is well underway and it will continue for the foreseeable
future.
Very few companies still do major developments on
Mainframe. Most of them either migrating or already using PC’s and
UNIX or NT servers to take care of their data processing needs.
And even though majority of the companies are
operating in the client-server environment, one core thing
remains the same: they still have and will continue to have
batch processing. We would even say that batch processes/ jobs are
probably the most important part of almost any business and we will
be very hard pressed to name even one company or industry (of any
significance, excluding software development) that do not have batch
processing in its core. We can list banking, finance, manufacturing,
insurance and so on.
Mainframe world have well defined infrastructure to
create, execute and maintaine jobs
(MVS/JCL on IBM mainframes, WCL on Unisys, WIFL on
AS-400 , etc.)
Thousand of programmers knew these programming
languages and used them on the regular basis, even though some of
these languages are not very straightforward, therefore there were
little issues with development and maintenance of the Job control
Programs.
Currently client/server environment does not
have single uniformed job control language.
Job control programs are written either in Unix shell,
DOS bat, C , etc.
Lack of client/server JCL prolongs development,
creates nightmare in maintenance, portability, and training.
Our research indicates that US companies are spending
8-10 billion dollars per year to develop and maintain their batch
jobs. | 
