Setting additional Tivoli Workload Scheduler (TWS) rules

This procedure describes how to set additional Tivoli Work Scheduler (TWS) rules.

After you have imported your data, you can modify conversion rules by setting general rules and Field Editor rules. For more information about modifying setting and rules, see Modifying conversion settings. For more information about TWS recommended practices, see TWS recommended practices.

To set additional TWS rules:

1. From the Additional TWS Rules tab, in the General area type the General parameters for TWS.

   The following table describes the General parameters in the Additional TWS rules tab.

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

   Parameter	Description
   Keep active for	Determines the maximum number of days that a Control-M job can wait for execution after order date. Valid values: 0-99 (integer) Default: 1 NOTE: The Keep active for parameter has an effect on Control-M jobs only when the TWS parent container has the CARRYFORWARD attribute.
   First day of the week	Determines the first day of the week according to your work environment.
   Date format	Enables you to select the format for date input and display.
   Convert OPENS statement to File Watcher	Enables you to convert an OPENS Statement in TWS to Control-M File Watcher.

2. In the Standalone jobs area, select one of the following options.
   • Group all stand alone jobs in one folder: standalone jobs are grouped into one folder.
   • Create a different folder for each stand alone job: separate folders are created for each job.
3. In the Calendar area, specify the default names for calendars in this conversion project.
   • Work days calendar
   • Free days calendar
   • All days calendar
4. In the Scheduling Conversion area, select one of the options in Scheduling Conversion parameters for TWS.

   This table describes the Scheduling Conversion parameters for TWS rules. For more information, see Setting additional Tivoli Workload Scheduler (TWS) rules.

   Parameter	Description
   Use 'Exclude' RBCs (Control-M V8 FP1 or later)	Enables the Conversion Tool to convert TWS EXCEPT statements using the Rule Based Calendars feature added in Control-M V8 Fix Pack 1.
   Do not convert "EXCEPT" statements	Determines that except statements are not converted to Control-M (default). An Error message WRN6022 is issued for each statement that is not converted. TWS ON statements are converted to Control-M rule-based calendars.
   Convert "EXCEPT" statements to dummy jobs	Determines that a dummy job is created for each "EXCEPT" statement. The converted SMART folder depends on the condition(s) released by the dummy job(s). TWS "ON" statements are converted to Control-M rule-based calendars.
   Convert "ON" and "EXCEPT" statements to dummy jobs	Determines that a dummy job is created for any "ON" or "EXCEPT" statement. This dummy job derives scheduling definitions from the corresponding statement. The converted SMART folder depends on the conditions released by the dummy jobs, with an "OR" between conditions created from "ON" statements, and a logical "AND" between conditions created from "EXCEPT" statements. In addition to the dummy jobs, "ON" statements are converted to rule-based calendars (otherwise the SMART folders are not ordered).

5. To define the condition format in Control-M, in the Convert to format field, from the dropdown list, select one of the following condition format options:
   • {Job/Folder Name}_Status
   • {Job/Folder Name}-TO-{TargetJob:Job/Folder Name}
6. If you need to convert SAP data, click the SAP Editor - TWS tab. For more information, see SAP Editor rules for TWS.

   The following table describes the SAP editor rules for Tivoli Workload Scheduler (TWS) when selecting the SAP Editor -TWS tab.

   NOTE: Select the Enable SAP conversion check box to enable conversion of SAP jobs using the Control-M for SAP forms.

   Parameter	Description
   Job Count	-i = <account_name> SAP account name
   User	-user = the SAP job owner
   Job Class	-c = <class_name> SAP job class
   Job Name	-job = <job_name> the SAP job name

   NOTE: These parameters must appear in the DOCOMMAND in SAP. A job converts to a SAP job when the DOCOMMAND contains all the values in the SAP filter list. SAP jobs are converted to Task Type JOB. The set of conversion rules appears in the Conversion rules list. You can use these rules in future conversions.

7. If you need to convert PeopleSoft data, click the PeopleSoft Editor. For more information, see PeopleSoft Editor rules for TWS.

   The following table describes the PeopleSoft editor rules for Tivoli Workload Scheduler (TWS) in the PeopleSoft Editor tab.

   NOTE: Select the Enable PeopleSoft conversion check box to enable conversion of PeopleSoft jobs using the Control-M for PeopleSoft forms. If unchecked these jobs are converted to regular OS jobs in Control-M.

   Parameter	Description
   Process name	Defines the process name to be scheduled.
   Type	Defines the output destination type, specifying the file path, printer destination URL or email address.
   Run Control	Defines the Run control attributes that are associated with a process or job.
   Run Location	Identifies the name of the server to be used for running the process or job.

8. If you need to convert OS400 data, click the OS400 Editor. For more information, see OS/400 Editor rules for TWS.

   The following table describes the OS/400 editor rules for Tivoli Workload Scheduler (TWS) in the OS400 Editor tab.

   NOTE: Select the Enable OS400 conversion check box to enable conversion of OS/400 jobs using the Control-M for OS/400 forms. If unchecked these jobs are converted to regular OS jobs in Control-M.

   Parameter	Description
   Convert CALL commands to object type program	Enables the Conversion Tool to convert command line CALL <program> … to job type OS400 Program rather than OS/400 command line jobs. NOTE: Any TWS command line job that starts with the CALL command, the job type can be set to OS400 Program. The CALL command program name and the parameters are extracted from the command line into the appropriate job attributes.
   Keyword for SUBMIT	Enables TWS to submit the job to batch, including the submit jobs attributes.
   Keyword for DOCOMMAND	Enables TWS to run the command directly without submitting it to batch. There are no submit job attributes. Control-M submits the job to batch. For SUBMIT mode, the submit job attributes are extracted from the SUBMIT string. For DOCOMMAND mode, the default submit job attributes are used.

9. Click Next to start the conversion.

   A message appears confirming that conversion is in progress. The results appear in the Conversion Results window, as described in Conversion results.

   NOTE: The conversion rules are automatically saved after you run the conversion. The set of conversion rules appears in the Conversion rules list in the Run Conversion window. You can use these rules in future conversions.