This useful interface to the definition databases of TWS
for zOS performs mass changes, cloning and/or maintenance
in batch mode. Productivity is increased by minimizing
dialog usage.
Especially useful in test environments, TWS/BatchAD allows
you to move definitions from test to production and vice
versa. While transferring data, all fields can be modified.
Example: "Copy all applications created today by
user P390G by changing all workstations P* to T*"
TWS/BatchAD is easy to install and use. Users do not need
any programming knowledge. TWS/BatchAD works using easy-to-understand
control statements. TWS/BatchAD is normally used in batch
mode. You can also use TWS/BatchAD in REXX or CLIST functions
and integrate it into command line programs or dialog
systems.
Examples:
You
want all operations AB*300* to have a new start
time, 16:00.
You
want all applications STA* to become PENDING.
You
want to assign all operations of applications XYZ%%%%100PG
and the workstation CPUA two tape units.
You
want all operations with the workstation DB2* to
get a special resource DB2.UPDATE.
You
want to rename the run cycle names BONUS98 to BONUS99
in all applications.
You
want all jobs %%KONTO* to have a new workstation,
CPUX. In addition, you want this
modification
to be performed automatically in all external predecessor
definitions pointing to these jobs.
You
want to rename all applications T* to P*. In addition,
you want this modification to be performed
automatically
in all external predecessor definitions pointing
to these applications.
You
want all external predecessor definitions pointing
to deleted jobs to be removed to avoid *NOTFND*.
You
want a special resource to be inserted automatically
into the RD file (TWS Dialog 1.6).
You
want to export all applications and variable tables
called TEST*, change the first four characters
from
TEST to PROD, and import the new applications and
variable tables into another TWS.
