Additional Settings

In the Conversion Tools, you must set the specific Additional Settings for each scheduler, as follows:

• Broadcom Appworx Additional Conversion Settings

• Broadcom Automic UC4 Additional Conversion Settings

• Broadcom AutoSys Additional Conversion Settings

• Broadcom JOBTRAC Additional Conversion Settings

• Broadcom Dollar Universe Additional Conversion Settings

• Broadcom Unicenter WLM (TNG) Additional Conversion Settings

• Broadcom Workload Automation DE (dSeries) Additional Conversion Settings

• Cron Additional Conversion Settings

• TWS Additional Conversion Settings

• JP1 Additional Conversion Settings

• Task Scheduler Additional Conversion Settings

• Redwood CPS Additional Conversion Settings

• Tidal CPS Additional Conversion Settings

• Zena Additional Conversion Settings

• Hadoop-Oozie Additional Conversion Settings

• SAP Additional Conversion Settings

Broadcom Appworx Additional Conversion Settings

The following table lists the Appworx Additional Conversion Settings:

Conversion Settings	Description
Node Default Platform	Defines the name of the default operating system for each node data.
First Day of the Week	Defines the first day of the week of your Control-M work environment.
Keep Active for	Defines the maximum number of days that a Control-M job can wait for execution after run date (default: 0). Valid values: 0-99 (integer).
Don't Convert AppWorx disabled events	Defines that disabled events in the AppWorx data is not converted to Control-M data.
Convert Appworx entities that don't reside under Process Flow	Defines that entities not under Process Flow in the Appworx data are converted to Control-M data.
CID<Unique number>@JOBA@JOBB	Determines how two jobs are connected by creating a unique event in the format: CID<Unique number>@JOBA@JOBB.
Delete Events	Determines to delete the event after the next job has finished running
JOBA@<Status>	Determines a dependence event between many jobs according to its end status. For more details see Events.

Broadcom Automic UC4 Additional Conversion Settings

The following table lists the Automic UC4 Additional Conversion Settings and UC4 Scripts Conversion Settings:

Conversion Settings	Description
General
Convert UC4 executable objects without scheduling reference	Converts objects that are not in any UC4 Schedule definitions, such as Post Script. For more information about converting UC4 jobs with Post Script, see Converting UC4 Scripts to Control-M.
First day of the week	Defines the first day of the week to your Control-M work environment.
Default UC4 Client Time Zone	Defines the time zone of the UC4 client server.
Convert 'Start' and 'End' tasks to Dummy jobs	Converts Start and End tasks to Control-M Dummy jobs. By default, Start and End tasks are ignored and not added to Control-M.
Set 'Adjust Event' to 'Y' in all folders to replace jobs that are not scheduled with Dummy jobs	Determines to replace unscheduled jobs with Dummy jobs by seting Adjust Event to Y in all folders.
Job/Folder Name Manipulation
Change prefix/suffix	Determines whether to use a character to indicate the location in the filename where characters were removed.
Truncate characters from the Beginning	Shortens a filename by truncating characters from the beginning of the name.
Truncate characters from the end	Shortens a filename by truncating characters from the end of the name.
Uniqueness Suffix Separator	Determines whether to use a character to separate the original filename from the numbers that are added to the end of the filename.
Event Name Convention
Delimiter	Determines which character is used to separate the prefix, suffix, or events.
Prefix	Determines the prefix used to separate the events.
Suffix	Determines the suffix used to separate the events.
Format	Defines the default format used for creating job dependencies.
Event name format that will be created	Displays the resulting format based on the changes made to the other options in the Event Name Convention area.
UC4 Scripts Conversion	Describes how to use UC4 scripts in Control-M. For more information, see Converting UC4 Scripts to Control-M.
Additional Conversion Options
Don't add Pre scripts into Control-M embedded script	Determines whether to convert the Pre script content into the Control-M Embedded Script field. A warning message about Pre Script content still appears in the Conversion Report. By default, the Conversion Tool converts the content of UC4 pre script into the Control-M embedded script field. If you do not want to convert UC4 Pre-Script and remove the warning message, set the appropriate rule in the UC4_scripts_conversion_to_ctm.xls file.
Don't add Post scripts into Control-M embedded script	Determines whether to convert Post script content into the Control-M embedded script field. A warning message about post script content still appears in the Conversion Report. By default, the Conversion Tool converts the content of UC4 Post Script into the Control-M Embedded script field. If you do not want to convert UC4 pre script and remove the warning message, set the appropriate rule in the UC4_scripts_conversion_to_ctm.xls file.
Convert UC4 scripts with '1' command into Control-M command line jobs	Determines whether to convert UC4 scripts, that contain only one command into Control-M OS Command jobs, if it they do not include UC4 scripting language keywords. By default, the Conversion Tool converts the content of UC4 Scripts into the Control-M embedded script fields.

Converting UC4 Scripts to Control-M

This procedure describes how to convert UC4 scripts to Control-M compatible scripts. Broadcom Automic (UC4) uses its own scripting language, so you need to define how the Conversion Tool how to convert the scripts.

Before you begin

Ensure that you have successfully progressed through the Conversion Tool until you reach the UC4 Scripts Rule tab of the Conversion Settings window. For more information, see Converting to Control-M.

Begin

1. From the UC4 Scripts Rule tab, open the following file:

   UC4_scripts_conversion_to_ctm.xlsx

   This file contains the Conversion Tool automatic analysis of the UC4 scripts.

2. In the UC4_scripts_analysis tab, review the analysis to determine the optimal way to convert the scripts:

   • UC4 Script Pattern: Displays the UC4 script patterns found in the scripts.

   • UNC Script Content: Displays each script pattern instance when a script pattern+ is selected.

   • Number of UC4 Jobs use the Script Pattern: Displays the number of jobs that contain the script pattern.

3. In the UC4_scripts_conversion_to_ctm tab, fill in the Select conversion option 1 or select conversion option 2 columns. For column descriptions , see UC4_scripts_conversion_to_ctm Tab.

   In the Select conversion option 1 or Select conversion option 2 columns do any of the following:

   • If you select the Convert to Control-M If Action, define the value in XML format, as described in Adding an If Action XML Value.

   • If you select the Convert to Control-M Variables, define the value in XML format, as described in Adding a Control-M Variable XML Value.

4. Save the UC4 Scripts Conversion file, copy it, and move it to the directory where you loaded the files that you extracted from the Automic UC4 scheduler.

5. Re-open the Conversion Tool and run the conversion.

   The Conversion Tool uses the conversion rules in the file to convert the UC4 scripts to Control-M compatible scripts.

UC4_scripts_conversion_to_ctm Tab

The following table describes the information contained in the UC4_scripts_conversion_to_ctm tab in the UC4_scripts_conversion_to_ctm .xls file:

Name	Description
UC4 Script type	Indicates if the UC4 Script found belongs to the Pre/Post Script attributes. In the Select conversion option column the options vary according to Script Type.
UC4 Script Content	Contains the UC4 script detected in the Pre/Post-Script attribute.
Number of jobs use the script	Contains the number of UC4 Jobs that use the same script.
Type	Indicates the type of Control-M job to use when creating Control-M If Actions or Parameters data in Control-M client.
Select conversion option 1	Enables you to define how to convert UC4 Pre/Post Scripts into Control-M using one of the following options: Convert to Control-M If Actions (Post Script Type only) Convert to Control-M Variables (Pre Script Type only) Replace with another Script (Pre Script Type only) Don't Convert Script For more information about the Control-M options, see Control-M Options.
Conversion option 1 value	Defines the Conversion option value that is imported into Control-M
Select conversion option 2 (optional)	Defines an additional option in Control-M, as described in Select conversion option 1 in this table.
Conversion option 2 value (optional)	Defines an additional Conversion option value, as described in Conversion option value 1 in this table.

Control-M Options

The following table describes the Control-M options in the Select Conversion option column in the UC4 Script Conversion file.

Script Type	Control-M Option	Description
Post Script	Convert to Control-M If Actions	Converts UC4 Post Script to Control-M If Action. You must supply the Control-M If Action XML in the Conversion Option Value column, as described in Adding an If Action XML Value.
Post Script	Do not Convert Script	Does not convert UC4 Post Script to a Control-M embedded Script job and the Conversion Tool does not issue a warning message in the Conversion Report. Use this option if you decide that UC4 Script is not required in Control-M.
Pre Script	Convert to Control-M Variables	Converts UC4 Pre Script to a Control-M variable. You must supply the Control-M Variable XML in the Conversion Option Value column, as described in Adding a Control-M Variable XML Value.
Pre Script	Replace with another Script	Replaces a UC4 Pre Script with another script that does not use UC4 Scripting language. You must supply a replacement script in the Conversion Option Value column.
Pre Script	Do not Convert Script	Does not convert UC4 Pre script to a Control-M embedded Script job and does not issue a warning message in the conversion report. Use this option if you decide that UC4 Script is not required in Control-M.

Adding an If Action XML Value

This procedure describes how to add an If Action XML to the Conversion option value column in the UC4 Script Conversion file.

Begin

1. From the Control-M Planning domain, create a job.

2. Create an If Action, by adding the If Action parameters, as necessary, {as described in If Actions in Control-M Parameters.

3. Export the selected jobs to an XML file, by doing one of the following:

   • Select the entities to export.

   • Select Export, and select Export Selected Entities.

   • To export the workspace, click Export.

4. Click Save.

5. Open the XML file that you saved in step 4, and copy and paste the If Action into the Conversion option value 1 and/or 2 columns in the UC4 Script file.

   Copy only the relevant part of the XML as in the following example:

   Exported XML:

   <?xml version="1.0" encoding="utf-8"?>

   <!--Exported at 18-09-2017 15:35:47-->

   <DEFTABLE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Folder.xsd">

   <FOLDER DATACENTER="CTM-Server1" VERSION="900" PLATFORM="UNIX" FOLDER_NAME="Folder#2" FOLDER_ORDER_METHOD="SYSTEM" TYPE="1" ENFORCE_VALIDATION="N">

   <JOB MEMNAME="a" JOBNAME="OS_Job#1" CREATED_BY="amir" RUN_AS="a" CRITICAL="0" TASKTYPE="Job" CYCLIC="0" INTERVAL="00001M" MEMLIB="a" CONFIRM="0" RETRO="0" MAXWAIT="0" MAXRERUN="0" AUTOARCH="1" MAXDAYS="0" MAXRUNS="0" DAYS="ALL" JAN="1" FEB="1" MAR="1" APR="1" MAY="1" JUN="1" JUL="1" AUG="1" SEP="1" OCT="1" NOV="1" DEC="1" DAYS_AND_OR="O" SHIFT="Ignore Job" SHIFTNUM="+00" SYSDB="1" IND_CYCLIC="S" RULE_BASED_CALENDAR_RELATIONSHIP="O" APPL_TYPE="OS" MULTY_AGENT="N" USE_INSTREAM_JCL="N" CYCLIC_TOLERANCE="0" CYCLIC_TYPE="C" PARENT_FOLDER="Folder#2">

   <ON STMT="*" CODE="NOTOK">

   <DOACTION ACTION="OK" />

   <DOMAIL URGENCY="R" DEST="[email protected]" SUBJECT="Job Failed" ATTACH_SYSOUT="D" />

   </ON>

   </JOB>

   </FOLDER>

   </DEFTABLE>

    

   Relevant XML:

   <ON STMT="*" CODE="NOTOK">

   <DOACTION ACTION="OK" />

   <DOMAIL URGENCY="R" DEST="[email protected]" SUBJECT="Job Failed" ATTACH_SYSOUT="D" />

   </ON>

Adding a Control-M Variable XML Value

This procedure describes how to add a Control-M Variable XML to the Conversion option value column in the UC4 Script Conversion file.

Begin

1. In Control-M client, from the Planning domain, create a job.

2. Create the Control-M Variable, by adding the variables as necessary, as described in Variables in Control-M Parameters.

3. Export the selected jobs to an XML file, by doing one of the following:

   • Select the entities to export.

   • Select Export, and select Export Selected Entities.

   • To export the workspace, click Export.

4. Click Save.

5. Open the XML file that you saved in step 4, and copy and paste the Control-M Variable XML into the Conversion option value 1 and/or 2 columns in the UC4 Script Conversion file.

   Copy only take the relevant part of the XML as in the following example:

   Exported XML:

   <?xml version="1.0" encoding="utf-8"?>

   <!--Exported at 18-09-2017 15:35:47-->

   <DEFTABLE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Folder.xsd">

   <FOLDER DATACENTER="CTM-Server1" VERSION="900" PLATFORM="UNIX" FOLDER_NAME="Folder#2" FOLDER_ORDER_METHOD="SYSTEM" TYPE="1" ENFORCE_VALIDATION="N">

   <JOB MEMNAME="a" JOBNAME="OS_Job#1" CREATED_BY="amir" RUN_AS="a" CRITICAL="0" TASKTYPE="Job" CYCLIC="0" INTERVAL="00001M" MEMLIB="a" CONFIRM="0" RETRO="0" MAXWAIT="0" MAXRERUN="0" AUTOARCH="1" MAXDAYS="0" MAXRUNS="0" DAYS="ALL" JAN="1" FEB="1" MAR="1" APR="1" MAY="1" JUN="1" JUL="1" AUG="1" SEP="1" OCT="1" NOV="1" DEC="1" DAYS_AND_OR="O" SHIFT="Ignore Job" SHIFTNUM="+00" SYSDB="1" IND_CYCLIC="S" RULE_BASED_CALENDAR_RELATIONSHIP="O" APPL_TYPE="OS" MULTY_AGENT="N" USE_INSTREAM_JCL="N" CYCLIC_TOLERANCE="0" CYCLIC_TYPE="C" PARENT_FOLDER="Folder#2">

   <VARIABLE NAME="%%A" VALUE="Local" />

   <VARIABLE NAME="%%\\Banai\Amir" VALUE="Pool" />

   <VARIABLE NAME="%%\BB" VALUE="Global" />

   </JOB>

   </FOLDER>

   </DEFTABLE>

    

   Relevant XML:

   <VARIABLE NAME="%%A" VALUE="Local" />

   <VARIABLE NAME="%%\\Banai\Amir" VALUE="Pool" />

   <VARIABLE NAME="%%\BB" VALUE="Global" />

Broadcom AutoSys Additional Conversion Settings

The following table lists the AutoSys Additional Conversion Settings tab:

Conversion Settings	Description
General
Source Command	Defines the command used to source the script defined in the profile field of your source scheduler.
Convert unscheduled boxes to Run Method="ON_DEMAND"	Determines to convert unscheduled boxes to the USERDAILY="ON_DEMAND" checkbox. By default, Control-M runs the jobs automatically. This option enables to run the jobs on demand.
Event
Event pattern that will be created.	Determines the event format.
Remove job's events after job's completion	Determines to remove the job's events after the job has completed.
File Watcher Type
MFT	Determines to convert File Watcher jobs to MFT jobs.
Ctmfw utility	Determines to use the Control-M File Watcher utility (and not MFT).
SAP	Determines to convert SAP jobs using the Control-M SAP forms.
PeopleSoft	Determines to convert SAP jobs using the Control-M PeopleSoft forms.
Text File Reading and Monitoring Job Type	Converts Autosys Text File Reading and Monitoring jobs to Control-M FWText jobs. The Control-M FWText job supports the following fields: text_file_filter text_file_name text_file_filter_exists The following fields are permanently set as follows: monitor_mode: NOW text_file_mode: LINE Related links: FWText job Download Importing job from file

Broadcom JOBTRAC Additional Conversion Settings

The following table lists the Broadcom JOBRTAC Rules Additional Conversion parameters:

Parameter	Description
Convert DS jobs	Defines the Distributed Systems (DS) job when you select the Convert DS jobs checkbox.
Events	Determines dependencies between jobs.
Start Day of the Week	Determines the start day of the week for scheduling.
New Day time	Determines the value in the New Day time value specified in CTMPARM field.
Customize Control-M jobname	Defines the Alternate JCL member name as the jobname
SCL libraries processing	Enables you to process each SCL library separately.

The following table lists the Broadcom JOBRTAC Rules Additional Conversion parameters in the Mainframe Editor:

Parameter	Description
SCHED TAB – Scheduling Table Library	Defines the Control-M scheduling table that stores job definitions. Default: CTM.SCHEDULE
OVERLIB – JCL Over Lib	Defines the value as OVERLIB for converted jobs. Default: CTM.OVERLIB You must verify that the JCL Overlib Library is allocated in the Mainframe.
INCLIB – Control-M Include Library	Defines the value as INCLIB for converted jobs. Default: CTM.INCLIB
JCLLIB – Alternate Memname	Defines the value of an additional Memname, which is used for saving converted jobs. Default: CTM.JCLLIB You can use the JCL Library for alternate members allocated during Control-M installation. You must verify that the Control-M JCL Library for alternate members is allocated in the Mainframe.
CTODSN – Control-O rule library	Defines the Control-O rules library containing Dataset and messages triggering events for ADR, AMR and SCS. Default: CTM.CTODSN.
IOAENV - Library full path	Defines the name of the IOA/Control-M production environment’s IOAENV library.
CMEM – CMEM rule library	Defines the CMEM rules library containing Job Arrival events for RESOURCE file conversion. Default: CTM.CMEM. You must verify that the CMEM rules library is allocated in the Mainframe.
Control-O run JCL library	Defines the JCL library name containing JCL files running from Control-O rules. Default: CTM.CTO.JCL. You can use the Control-O JCL library allocated during Control-O installation. You must verify that Control-O run JCL library is allocated in the Mainframe.
JOB CARD - Job card for output JCL	Enables you to use job cards for the output JCL that is created to run at the end of the conversion to return the converted data to the appropriate files.
Number of Directory Blocks	Defines the number of directory blocks allocated to the converted JCL library. This should must be the same as the number of directory blocks in the original Jobtrac JCL library.
MAXCC	Defines the Maximum condition code for OK status. Valid values: 0-4095 (integers).
Sysout From Class	Defines a blank space or single character to specify the Sysout class.
Sysout To Class	Defines a blank space or single character to specify the Sysout class. The Sysout is moved to the end of the job. Default: ‘*’.
Sysout option	Defines the Sysout action when a job finishes. Valid Values: Release Delete None

Broadcom Dollar Universe Additional Conversion Settings

The following table lists the Dollar Universe Additional Conversion Settings:

Conversion Settings	Description
UPROCs with Task but Without a Session
Convert all UPROCS without a Session into a Single Control-M SaaS folder	Determines to convert all UPROCs that have a task but do not have a session into one Control-M folder containing all UPROCs. This option is relevant only when the Convert UPROCs that do not have a session is selected.
Convert each UPROC without a Session into a Single Control-M SaaS folder	Determines to convert each UPROC that does not have a session into its own Control-M folder.
UPROCs without scheduling
Convert UPROCS without scheduling	Determines to convert UPROCS without scheduling to Control-M data.
Other Information
Date Format	Determines the format for date input and display
Area	Determines the Control-M folder name, built in the format: <AREA>_<SESSION>_<MU> from the following options: EXP SIM INT APP
Priority Conversion
Convert equal priorities	Determines to convert Dollar Universe jobs even when multiple jobs have the same priority value. If all Dollar Universe jobs use the same value, this degrades the performance of Control-M. To avoid this effect, you can choose to not convert priorities according to the priority conversion option that you select.
Don't convert priorities if all equal	Determines to not convert Dollar Universe jobs when multiple jobs have the same priority value. Irrespective of the option chosen, if not all priorities are equal, the priorities will be converted as usual.
HDP Options
Append events for viewing links between jobs in Control-M	Determines to append events that provide the ability to view the flow between jobs in the Planning and Monitoring domains in Control-M client.
Notify destination name for ctmorder script	Defines the name of the destination file in your environment which is necessary for adding a Notification destination in Control-M client.
Event
{Job/Folder Name}_Status	Determines the format of the event.
{Job/Folder Name}TO-TargetJob:Job/Folder Name}	Determines the format of the event.
Delete Events	Determines to delete the event after the next job has finished running.

Broadcom Unicenter WLM (TNG) Additional Conversion Settings

The following table lists the Unicenter WLM (TNG) Additional Conversion Settings:

Conversion Settings	Description
General
Date Format	Determines the WLM date format for your conversion project.
Applicability-Application Separator	Defines a separator character that converts WLM grouping to Control-M hierarchy format. PROD#SET1 where the separator is #, the Control-M Application entity is set to PROD and the Sub-Application is set to SET1.
Resources	Determines the following target Control-M resource types: Auto Lock Resource Resource Pool If you select Auto it automatically selects a target Control-M resource type.
PRIOR handling	Determines the following events: Prev: Sets the event to a previous scheduling date. Dummy job: Creates the event the following day.
Event Date for Everyday Job	Determines the generated Control-M in or event dates for everyday jobs. This setting is only available when PRIOR handling is set to Prev. Any: Enables the subsequent job to be set with an event date, so the event is deleted when the job ends. Prev: Enables the subsequent job to be set with an event date, so that the event is not deleted when the job ends. For both options, the predecessor job sets the event to Run Date.
Keep active for	Defines the maximum number of days a job can wait for execution after run date. Valid value: Integer between 1 and 99. This parameter influences Control-M jobs only if the WLM job definition BACKLOG value is set to YES.
First Day of the Week	Determines the first day of the week of your work environment.
Event Name Convention
Delimiter	Defines the character to separate the prefix, suffix, or events.
Prefix	Defines the prefix to separate the events.
Suffix	Defines the suffix to separate the events.
Format	Determines the default format used for creating job dependencies. The default format has 2 different conventions: JOBA-TO-JOBB JOBA-ENDED-<Status>
Event name format that will be created	Determines the resulting format based on the changes made to the other options in the Event Name Convention area.
Delete Events	Determines to delete the event after the next job has finished running. Jobs which trigger more than one job may cause some successor jobs not to be triggered.
Calendar
All Days Calendar Name	Defines the name of the calendar that runs every day.
Holidays Calendar Name	Defines the name of the holiday calendar.
Number of Year	Determines the number of years the calendars are used. This sets the range of dates for the Control-M calendars.
Trigger Jobs Conversion (DSCLOSEU)
Enable	Determines to activate the conversion of WLM trigger jobs. The Control-M File Watcher utility is used for the conversion of trigger jobs.
Interval	Determines the interval time in seconds between each file check. Valid value: An integer between 1 and 99.
Time Stop	Defines the stop time in the format, "hh:mm" to end file watching.
Station ID and Owner Table	Defines name of the station and person who has permissions to execute File Watcher jobs for each station. You can use wildcards for both the Station ID and Owner fields: * for any word, and ? for any character.
Create File Watcher job per trigger	Determines to enable you to create a file watcher job per trigger. If you want to create a file watcher job per station leave the check box unchecked.
Parameter Configuration	Determines to enable the mapping of WLM parameters to Control-M parameters.
SAP	Determines to convert SAP jobs to Control-M.
Tandem	Determines to run TACL scripts as TACL jobs in Control-M.

Broadcom Workload Automation DE (dSeries) Additional Conversion Settings

The following table lists the Workload Automation DE Additional Conversion Settings:

Conversion Settings	Description
General
First Day of the Week	Determines the first day of the week of your Control-M work environment.
Notifications Urgency	Determines the urgency for converted job notifications. Select the urgency for notifications set by Control-M.
Events
JOBA-JTO-JOBB	Determines how two jobs are connected by creating a unique event in the format: JOBA_JOBB.
Cleanup Events	Determines to delete the event after the next job has finished running.
JOBA-ENDED-<Status>	Determines a dependence event between many jobs according its end status. For more details, see Events.

Cron Additional Conversion Settings

The following table lists the Cron Additional Conversion Settings:

Conversion Settings	Description
General
First Day of the Week	Determines the first day of the week of your Control-M work environment.
Action:Mail Generation	Determines email job notification behavior: Never Only if $MAILTO was defined in crontab: Sends email notifications to the email address that is defined in the $MAILTO variable in crontab. If this option is selected, it overrides any email address that you may have entered in the default email address field. For All Jobs: Sends email notifications to the email address that you enter. You can also enter variables as part of the email address. {User}@domain.com.

TWS Additional Conversion Settings

The following table lists the TWS Additional Conversion Settings:

Conversion Settings	Description
General
Keep active for	Determines the maximum number of days that a Control-M job can wait for execution after the run date. Valid values: 0-99 (integer) Default: 1 The Keep active for parameter effects 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 of your Control-M work environment.
Date Format	Determines the format for date input and display.
Convert OPENS statement to File Watcher	Converts an OPENS Statement in TWS to Control-M File Watcher.
Standalone Jobs	Determines whether to group all standalone jobs in one folder, or to create a different folder for each standalone job
Calendar	Defines the default names for calendars of the following types: Work days calendar Free days calendar All days calendar
Event
Event pattern that will be created	Determines the event syntax
Remove job's events after job's completion	Determines whether to remove events after job completion.
Scheduling Conversion
Use ExcludeRBCs	Enables the Conversion Tool to convert TWS EXCEPT statements using the Rule Based Calendars.
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 folder depends on the event(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 folder depends on the events released by the dummy jobs, with an OR between events created from ON statements, and a logical AND between events created from EXCEPT statements. In addition to the dummy jobs, ON statements are converted to Rule Based Calendars (otherwise the folders are not run).
SAP Editor - TWS
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
PeopleSoft Editor	Settings in this tab are available after selecting the Enable PeopleSoft conversion checkbox. If unselected, PeopleSoft jobs are converted to regular OS jobs in Control-M.
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	Defines the name of the server to be used for running the process or job.
OS400 Editor	Settings in this tab are available after selecting the Enable OS400 conversion checkbox. If unselected, OS/400 jobs are converted to regular OS jobs in Control-M.
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. For 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.

JP1 Additional Conversion Settings

The following table lists the JP1 Additional Conversion Settings:

Conversion Settings	Description
Events
CID<Unique number>@JOBA-TO-JOBB	Determines how two jobs are connected by creating a unique event in the format: CID<Unique number>@JOBA@JOBB. Select the Cleanup events checkbox to delete the event after the next job has finished running.
CID<Unique number>@JOBA-ENDED-<Status>	Determines the events between many jobs according to its end status. For more details, see Events.

Task Scheduler Additional Conversion Settings

The following table lists the Task Scheduler Additional Conversion Settings:

Conversion Settings	Description
General
Ignore disabled tasks	Causes disabled tasks to be ignored during conversion.
Ignore disabled triggers	Causes disabled triggers to be ignored during conversion.
Job/Folder Name Manipulation
Change prefix/suffix	Determines the character used to indicate the location in the filename where characters were removed. Select one of the following options to shorten a filename that is too long: Truncate characters from the beginning Truncate characters from the end
Uniqueness suffix separator	Determines the character used to separate the original filename from the numbers that are added to the end of the filename.

Redwood CPS Additional Conversion Settings

The following table lists the Redwood CPS Additional Conversion Settings:

Conversion Settings	Description
General Information
Keep active for	Determines the maximum number of days that a Control-M job can wait for execution after the run date. Valid values: 0-99 (integer) Default: 1
First Day of the Week	Determines the first day of the week of your Control-M work environment.
Standalone Jobs	Determines whether to group all standalone jobs in one folder, or to create a different folder for each standalone job

Tidal CPS Additional Conversion Settings

This procedure describes how to set additional Tidal Software Enterprise Scheduler (Tidal) rules.

Begin

1. From the Conversion Tool, click the General tab area and select one of the following options:

   • Remove job's in conditions after job's completion: Removes each In Condition for every Control-M entity in the Control-M conditions, which prevents irrelevant jobs (instances) from running.

   • Do not convert Tidal disabled jobs (Inactive jobs): Ignores all disabled Tidal jobs, which are not converted to Control-M.

     If a Tidal job group is disabled, its children are ignored, regardless of whether they are disabled.

   • First day of the week: Defines the first day of the week of your Control-M environment.

2. Click Next.

Tidal Variables Mapping

The following sections describe how the Conversion Tool converts Tidal time and date variables into Control-M, together with examples:

• Tidal Time and Date Format Mapping

• Variable Resolution Examples

Tidal Time and Date Format Mapping

The following describes the Tidal time and date formats that are converted to Control-M variables.

Tidal format	Control-M Variable
d	%%NUMBER%%DD
dd	%%DD
ddd	Not supported
dddd	Not supported
j	%%SHORT_JULDAY %%SHORT_JULDAY=%%JULDAY %%MINUS 0
jj	%%SHORT_JULDAY %%SHORT_JULDAY=%%JULDAY %%MINUS 0
jjj	%%JULDAY
m	%%NUMBER%%MM
mm	%%MM
mmm	%%MMM%%MM
mmmm	%%MMMM%MM
yy	%%YY
yyyy	%%YYYY
fm	Not supported
fmm	Not supported
q	Not supported
fq	Not supported
fyy	Not supported
fyyy	Not supported
h	%%H%%HH
hh	%%HL%HH
H	%%NUMBER%%HH
HH	%%HH
AM/PM	%%AP%%HH
mm	%%MM as a substring of %%TIME
ss	%%SS

The following table lists the global time and date variables in Control-M.

Variable	Value
%%AP00 - %%AP11	AM
%%AP12 - %%AP23	PM
%%H00	12
%%H01-%%H12	1-12
%%H13 - %%H23	1-11
%%HL00	12
%%HL01-HL%%HL12	01-12
%%HL13-%%%HL23	01-11
%%MMM01	Jan
%%MMM02	Feb
%%MMM03	Mar
%%MMM04	Apr
%%MMM05	May
%%MMM06	Jun
%%MMM07	Jul
%%MMM08	Aug
%%MMM09	Sep
%%MMM10	Oct
%%MMM11	Nov
%%MMM12	Dec
%%MMMM01	January
%%MMMM02	February
%%MMMM03	March
%%MMMM04	April
%%MMMM05	May
%%MMMM06	June
%%MMMM07	July
%%MMMM08	August
%%MMMM09	September
%%MMMM10	October
%%MMMM11	November
%%MMMM12	December
%%NUMBER00	0
%%NUMBER01	1
%%NUMBER02	2
%%NUMBER03	3
%%NUMBER04	4
%%NUMBER05	5
%%NUMBER06	6
%%NUMBER07	7
%%NUMBER08	8
%%NUMBER09	9
%%NUMBER10	10
%%NUMBER11	11
%%NUMBER12	12
%%NUMBER13	13
%%NUMBER14	14
%%NUMBER15	15
%%NUMBER16	16
%%NUMBER17	17
%%NUMBER18	18
%%NUMBER19	19
%%NUMBER20	20
%%NUMBER21	21
%%NUMBER22	22
%%NUMBER23	23
%%NUMBER24	24
%%NUMBER26	25
%%NUMBER26	26
%%NUMBER27	27
%%NUMBER28	28
%%NUMBER29	29
%%NUMBER30	30
%%NUMBER31	31

Variable Resolution Examples

The following examples describe the date and time system variables, date variables with offset and Julian dates.

 

Zena Additional Conversion Settings

The following table lists the Zena Additional Conversion Settings:

Conversion Settings	Description
General
First Day of the Week	Determines the first day of the week of your Control-M work environment.
Keep active for	Determines the maximum number of days that a Control-M job can wait for execution after the run date. Valid values: 0-99 (integer) Default: 3
Events
JOBA-JTO-JOBB	Determines how two jobs are connected by creating a unique event in the format: JOBA_JOBB.
Cleanup Events	Determines to delete the event after the next job has finished running.
JOBA-ENDED-<Status>	Determines a dependence event between many jobs according its end status. For more details, see Events.

Hadoop-Oozie Additional Conversion Settings

The following table lists the Hadoop-Oozie Additional Conversion Settings:

Conversion Settings	Description
General
First Day of the Week	Determines the first day of the week of your Control-M work environment.
Keep active for	Determines the maximum number of days that a Control-M job can wait for execution after the run date. Valid values: 0-99 (integer) Default: 3
Events
JOBA-JTO-JOBB	Determines how two jobs are connected by creating a unique event in the format: JOBA_JOBB.
Cleanup Events	Determines to delete the event after the next job has finished running.
JOBA-ENDED-<Status>	Determines a dependence event between many jobs according its end status. For more details, see Events.

SAP Additional Conversion Settings

The following table lists the SAP Additional Conversion Settings:

Parameter	Description
General
Default Connection Profile	Defines the connection profile name, which appears in the Connection Profile field in the Job Properties pane in Control-M. By adding a Default account value, the connection profile is automatically added to a Control-M for SAP R/3 job. You still need to define the connection profile in the Control-M Configuration Manager (CCM).
Default Target Server	Defines the default target server. The default value appears in the Exec. Target field in the Job Properties pane in Control-M client. If unspecified, SAP determines a parameter value during runtime. To change the target server to group, after loading the converted data into Control-M, in Control-M client use the find and update feature to search for the target server and replace it with group.
Set Starting Event from Event ID and Parameters	Converts the SAP job Event ID and EVENT param to the After event parameter in the Start Event field in the Job Properties pane in Control-M. When the check box is selected, if the Event ID is SAP_END_OF_JOB, a Control-M event is created between the predecessor and the successor jobs.
Include periodic values	Determines whether SAP periodic values are converted to Control-M cyclic values.
Convert SAP planned start date/time to Control-M SAP jobs	Converts SAP application jobs start date and/or time to Control-M for SAP start date and/or time.
Job Mode
Copy	Copies an existing job in SAP, which enables you to set the job count setting from the drop-down list.
Create	Creates a new SAP job.