TWS/BatchCP is an add-on to TWS for zOS. It is designed
to help you in the automation of your production planning
and control. It modifies multiple occurrences, operations,
special resources, and external and internal dependencies
in batch mode.
TWS/BatchCP increases the productivity of your employees
by automating repetitive tasks. It helps you avoid manual,
error-prone TWS dialog input. TWS/BatchCP is useful for
testing purposes. Set date fields (input arrival date
of predecessors, occurrences, deadlines) to any date in
the future. Generate JCL for any date in the future. Simulate
TWS variable substitution.
With
TWS/BatchCP, users do not need any programming knowledge.
TWS/BatchCP works with easy-to-understand control statements.
TWS/BatchCP is normally started in batch mode. However,
TWS/BatchCP can also be used, for example, in REXX programs
and can therefore be integrated into any existing application.
Examples:
You
want to know which operations are waiting for a
special resource or which operations have been
active
for more than one hour.
At
the end of the year you want all operations XYZ*
to be planned with one tape unit instead of three
tape units.
You
want all operations of applications XXX12345 to
have a special resource, A.B.C.
You
want to delete all operations with owner A*. Missing
external dependencies are to be replaced automatically.
You
want all time jobs with a start time between 16:00
and 17:00 to have a new start time of 18:00.
You
want all operations with the job name AB*300 to
be set to MANUAL HOLD.
You
want all applications A* that are not complete to
be set to COMPLETE.
At
the end of the month you want the job BOOK to have
additional dependencies to the jobs CORREX
and
BILATIS.
You
want a job to run every 10 minutes. As opposed to
TWS, recurring jobs are easy to implement
with
TWS/BatchCP.
You
want to create the JCL for a day in the future by
resolving all TWS variables. You want to sort
this
JCL by planned start time. The JCL can then be used
as input for any JCL checker.
