• Trial simulation and resolution of JCL with TWS variables during any JCL edit from the AD, LTP or CP, verifying production JCL and eliminating OJCV errors during batch execution.
• Pre-substitution of JCL variable values at any point in time for an unlimited number of jobs, instead of submit time, saving significantly on job setup time.
• JCL variable coding aide (edit macro) that simplifies variable coding while reducing errors.
Working with TWS JCL variables in a more secure way
Testing TWS variables in JCLs through substitution avoids costly errors resulting in downtime. The trial setup function of Setup Mode allows you to simulate variable substitutions for jobs in applications from within ISPF, or in batch, without submission. Substitution and resolution can be derived from the TWS AD, LTP or CP. When based on the AD users can also specify any input arrival date and time. Based on explicit or generic filtering one or more applications may be selected for simulation.
The real setup function of Setup Mode allows you to pre-substitute, or “prime”, your variables at any point in time, for an unlimited number of jobs, rather than only at submission time. This saves significant amounts of time during the job setup phase.
The IBM Redbook Maximizing your OPC/TWS Throughput states as follows: “Preliminary stage JCL: Move as much JCL as possible to the JS file before it reaches a ready state, using a program interface staging program. If severe problems are encountered it may be necessary to do this manually. The preferred method is to use an OPC PIF program.”
The VAR Edit macro of Setup Mode provides support for users in coding of TWS supplied variables providing a “pointand and shoot” method of creating variables. This method reduces the risk of errors while speeding up the definition process.
• Reduced downtime resulting from OJVC errors
• Increased reliability
• Enhanced performance during TWS job submission
• Significant time savings working with job variables
Load / unload
• Explicitly or generically unload any or all TWS for z/OS base definitions in a standardised sequential format allowing for mass changes, application cloning, introduction into a change/configuration management process and archiving.
• Perform mass deletions removing resources no longer utilised.
Export and Import all TWS definitions
TWSeasy Load/Unload Mode allows you to unload or load any or all TWS for z/OS base definitions. Base definitions are unloaded into standard batchloader format files (where supported by IBM) or into a standardised sequential format. Users have the ability to generically filter on many different fields to qualify what will be unloaded. Users can even qualify applications and then specify that all resources associated with those applications be downloaded as well.
TWSeasy Load/Unload supports the unloading and loading of the following base definitions:
• Application Definitions
• Operator Instructions
• JVL Variable Tables
• Special Resources
Mass changes can be performed on partial or whole strings of the base definitions using literal values or variables. Specific application parameters can actually be mass changed directly within the AD database, without an unload/load process. Based on these features, users can clone subsets of base definitions with their resources and easily port them to other TWS systems; for example, moving applications and resources from TEST to PROD or visa versa.Mass deletions can also be performed removing unused resources.
Because the base definitions are now in a sequential format they can be introduced into any change and configuration management solution or archival process.
• Easy and fast application cloning
• Support for the unloading/loading of ALL base definitions
• Time savings in dealing with base definitions
• Integration into change management process
• Archiving of TWS definitions
Application Definition and Planning
• Define and schedule jobs within TWS for z/OS from one screen simplifying the process and extending accessibility of TWS across the organisation.
• Automate dynamic ad-hoc batch jobs.
Simplified submission of TWS ad-hoc jobs
Application Definition and Planning (ADP) Mode greatly extends the accessibility of TWS for z/OS across your organisation without increasing the workload on production personnel. Users who have little or no experience with TWS for z/OS, such as system programmers, database administrators and application developers, can define and plan applications in an easy and fast manner through one ISPF screen, without having to work with TWS for z/OS online. Specific fields like Application Id, Entry Op No and Exit Op no can be pre-populated further simplifying the definition process.
ADP Mode can also be used by production control personnel that want to define and plan an ad-hoc application using only one screen.
Automated generation of dynamic TWS ad-hoc Jobs
Applications can be defined and planned both in dialog and in batch. Using TWSeasy ADP in batch allows for the generation of dynamic ad-hoc jobs. For example a database utility could run and generate ad-hoc jobs through ADP Mode that will compress the appropriate databases.
• Extended TWS for z/OS usability to personnel outside production control
• Enhanced productivity of TWS for z/OS users
• Reduced training costs for new TWS for z/OS users
• Reduced errors through simplified user interface
• Easy submission of ad-hoc jobs
• Automation of dynamic ad-hoc jobs