Converting TWS to Control-M

This procedure describes the recommended practices for converting TWS jobs to Control-M.

To convert TWS jobs to Control-M:

1. Before converting jobs, it is recommended that you do the following:
   • A full scan of all scripts run by TWS to look for occurrences of TWS command lines, executables and variables within the scripts.
   • Identify any external interfaces to things such as monitoring and alerting tools, reporting tools, help desk incident management tools and CMDB’s.
   • A Precursory Scan of the TWS environment. If you have amended the .jobmanrc file to perform pre-execution actions, check if anything has been modified in the .jobmanrc file.

   EXAMPLE: A popular example of modification to the .jobmanrc is to provide the ability of job-step level restarts for UNIX and Windows jobs. The .jobmanrc file should be checked for this added feature. Users will typically be requested to use the ‘conman rr jobname step=restart-step-name’ command.

   • Create TWS variables. These are equivalent to Control-M variables and can be embedded in the job definition or script. These can be found in the Parms.txt file

   EXAMPLE:

   $PARM

   PROD_E_SCR "c:\schedules\e-commerce\filecopy.txt"

   EXAMPLE: Conversion to Control-M Server for Windows:

   ctmvar -ACTION SET -VAR "%%%%\PROD_E_SCR" –VAREXPR “C:\schedules\e-commerce\filecopy.txt”

2. In the Conversion Tool, it is recommended that you do the following:
   • From the Conversion Settings window, in the General tab in the Job Type Conversion area, select Convert all jobs to Control-M command line jobs. For more information, see Setting General rules.
   • From the Additional TWS Rules tab, select the following:
     • In the General field, select Convert OPENs statements to Control-M File Watcher.
     • In the Scheduling Conversion field, select 'Exclude' RBC's (Control-M V8 FP1 or later).

   NOTE: This converts calendars to Rule Based Calendars and places logical names as far as possible. For example ON “MO,TU,WE,TH,FR” converts this to “Weekdays”

   • If SAP jobs are identified, from the SAP Editor - TWS tab, type the SAP parameters as required.
   • If PeopleSoft jobs are identified, from the PeopleSoft editor tab, type the Peoplesoft parameters are required.

   For more information, see Setting additional Tivoli Workload Scheduler (TWS) rules

   NOTE: You may wish to see the schedules in a slightly different way in the Planning Domain in Control-M. Using the Field Editor on the Application and Sub_Application fields enables slightly different views after conversion. It is worth experimenting with these if you do not like the default view. For more information, see Setting Control-M field values.

3. After the conversion, from the Conversion Results window, in the Actions tab, click Generate Scripts to add automatically Quantitative resources, Global variables or Node Groups. For more information, see Generating scripts for Control-M/Server.

   EXAMPLE: Batch file to load Quantitative Resources:

   $RESOURCE

   PROD-NPDS01B#TSMPBKP 4 "For NDA backups"

   PROD-ONNM001A#TSMPBKP 4 "TSM prod backups so not too many run at the same time"

   PROD-DTCAH05A#FTFRES1 1 "Prevents FTF_WKLY clashing with FTF"