Control-M Conversion Tool Release Notes May 2013

Transcription

1 Control-M Conversion Tool Release Notes May

2 Contents Introduction to Control-M Conversion Tool Release Notes... 3 What's new... 4 Control-M Conversion Tool compatibility... 4 Compatibility with Control-M components... 4 Control-M Conversion Tool language compatibility... 5 Product distribution... 6 Installation... 6 Open issues and known problems... 7 Enhancements and corrected problems in previous releases... 9 Enhancements... 9 Corrected problems Support for Control-M Conversion Tool Levels of support Related documentation Customer support

3 Introduction to Control-M Conversion Tool Release Notes BMC Software is releasing Control-M Conversion Tool version , a tool that allows you to convert the following scheduling environments to the Control-M environment. Distributed systems Autosys PeopleSoft Cron Microsoft Task Scheduler UC4 ORSYP Dollar Universe IBM Tivoli Workload Scheduler CA AutoSys Workload Automation CA Unicenter WLM (TNG) Tidal Software Enterprise Scheduler Mainframe systems CA Jobtrac TM The Control-M Conversion Tool enables you to perform consistent conversions that enable accurate evaluations and precision adjustments for optimal results. The tool outputs a draft file (in XML format) containing the converted scheduling environment for easy loading to Control-M Workload Automation. Up-to-date, essential installation and service information that becomes available after this product is released will be placed at Before installation, BMC recommends that you check the website for any up-to-date information and also to determine whether recent patches are available for this product. 3

4 What's new CAR (Cron/MS Task Scheduler only) Control-M Conversion Tool now informs about the number of jobs that are created during the automatic data collection. This version of the Conversion Tool creates tasks as part of any conversion using the Discovery functionality (Cron and MS Scheduler jobs). These tasks are added to the Active Jobs File and applied to your overall task count for the day in which the Discovery/Data Collection is being run. A warning message is displayed indicating the number of tasks that are created as part of the Discovery/Data Collection and you have the opportunity to cancel the Discovery/Data Collection at that time. Please be sure you understand the possible implications of this prior to proceeding with the Discovery/Data Collection. Control-M Conversion Tool compatibility Control-M Conversion Tool version can only be installed on computers that use the Windows operating system and that have Java 1.6 or later installed. Compatibility with Control-M components The XML draft file output of the Control-M Conversion Tool is compatible with the following Control-M components: Control-M/Enterprise Manager, FP1 and later Control-M/Server for UNIX and Microsoft Windows, and later Control-M for z/os, and later 4

5 Control-M Conversion Tool language compatibility The following languages are compatible with the Control-M Conversion Tool. Languages Level of support Basic ASCII W. European (Latin-1 character set) US English Defines special Western European characters used in English, Spanish, German, and French in most free-text fields and parameters. 5

6 Product distribution The following procedure describes how to obtain the installation files for the Control-M Conversion Tool version using EPD. 1. Click and follow the instructions on the EPD site until you reach the Download Licensed BMC Products page. 2. Select BMC Control-M Conversion. 3. Download and save the relevant.zip file to a temporary directory. Installation Before you begin Make sure you have downloaded the installation file for Control-M Conversion Tool version as described in Product distribution (on page 6). 1. Extract the ZIP file. 2. At the command prompt, run the Control-M Conversion Tool by running the following command: conversion.bat. 6

7 Open issues and known problems The following Control-M Conversion Tool issues and known problems remain open in this release. CAR (Cron and MS Task Scheduler) CAR CAR When the Converstion Tool installation folder name contains more than one sequential space, for example, <word><space><space><word>, the automatic data collection step fails. In the Conversion Report window, when you use the Find command and nothing is found, the project folder tree disappears from the left pane of the window. In the Validation Report window, the Next year button does not work when you are viewing the last two months of the year previous to the last year in the report. For example, if the validation report is from 2010 to 2015 and you are viewing a date in November or December of 2014, the Next year button does not work. CAR (Cron and MS Task Scheduler) CAR (Cron and MS Task Scheduler) After you select an agent s platform, when you refresh the Agents list your selection is not saved. If you complete all the steps in the Data Import phase, and you decide that you want to make a change to the project name or change the data that you imported, and go through all of the data import steps again, the information in the Success tab in the Results List screen may contain inaccurate information. CAR (Cron) CAR (MS Task Scheduler) CAR (MS Task Scheduler) CAR (MS Task Scheduler) In some instances of an escaped percent symbol (\%), the backslash symbol is not removed during the conversion process. Triggers may not appear correctly in the Assessment report. The submission time is not converted. When converting a task that has a one-time trigger and several actions to Control-M jobs in a folder, the scheduled time of the task is not set for the jobs in the folder. 7

8 CAR CAR CAR CAR CAR CAR (Tidal) CAR (UC4) CAR If an SCL definition includes both a DATE, (with an mmdd value, and with or without wildcards), and a Process period that is converted to Control-M DAYS (such as, QTRn or DAILY), the DATE value is overwritten instead of being appended to the scheduling criteria. Workaround: After the conversion process, edit the job in the Planning domain, and manually set the scheduling criteria according to DATE value in JobTrac. The &: characters in the INCLIB variable are not replaced by %%. This occurs when there is a " ' " character in the input file before the &: characters, for example, CYC='&:ABC'. Workaround: Open the <project_name>.jcl file located here: <Conversion_Dir>\workarea\datasources\<project_name>\CONVERSIONS\ <Conversion_Result_Name>\ Modify all the &: entries to %% In ADR tables, when ACT has the value DCNT, it is supported only when the Dataset Count (SCL column 71) has the value 1. In AMR tables, when ACT = RUN, there is no check to see if the triggered job is already in the Active Jobs file to prevent ordering it again. Only the first process period of a multiple process period is converted when any of the following periods is specified: end of month (EOM) a specific quarter (QTRx) SATURDAY Workaround: After the conversion process, edit the job in the Planning domain, and manually set the scheduling criteria according to process period values. When resolving a non-numeric variable, exception errors are printed to the log file. When a UC4 group entity (schedule or plan) is defined with an unsupported calendar relationship (NOT or AND), the message WRN8017 displays incorrect calendar lists. When there are two blank characters before the ProcessChainID in the command line (-n parameter), the Validity Check report displays the ProcessChainID as empty. 8

9 CAR When the SAP R3 command line contains multiple spaces between the parameters, the Run as User field is not resolved correctly. Enhancements and corrected problems in previous releases The following sections describe enhancements and corrected problems in previous releases for the Control-M Conversion Tool. Enhancements Release CAR CAR CAR The Control-M Conversion Tool now supports Autosys PeopleSoft jobs. In the Conversion Rules for Jobtrac, in the Additional JobTrac Rules tab, you now have the option to change the naming convention for in/out conditions. In previous versions, the default naming convention was "<sending job>_<receiving job>". Now you can choose between "<sending job>_ok" and "<sending job>_<receiving job>". During conversion, the MEMLIB is automatically hardcoded to "GENERAL", or "DUMMY", for dummy jobs. Now, the MEMLIB value can be configured prior to conversion by using the JobTrac Conversion Rules Field Editor, specifically the values for SCL member name, SCL library name, Location ID, and Business group. 9

10 Release CAR (MS Task Scheduler) CAR (Cron) The Control-M Conversion Tool can now find MS Task Scheduler job definitions located on all servers that are managed by Control-M, import the job definitions into Control-M, and then convert them into Control-M job definitions. The Control-M Conversion Tool can now find Cron job definitions located on all servers that are managed by Control-M, import the job definitions into Control-M, and then convert them into Control-M job definitions. For Cron and MS Task Scheduler conversion projects, the Conversion Tool uses the Control-M Agent (installed on the same machine as the Conversion Tool) to collect Cron or MS Task Scheduler data from available Agents and Remote Hosts (nodes). The Control-M Agent uses Control-M jobs and Agent utilities to collect the Cron or MS Task Scheduler data. The Control-M jobs execute a script file to collect data and a list of available hosts. The script file used depends on the host s platform: UNIX uses the script file, capturescriptunix.txt, and Windows uses the script file, capturescriptwindows.txt. To start the automatic collection of data, a job is submitted to the Agent s primary Control-M Server. Once a list of available hosts is created, in the Conversion Tool, you can select from which hosts you want to collect data. A job is then submitted to each selected host to retrieve the Cron or MS Task Scheduler data. 10

11 Before you begin a Cron or MS Task Scheduler conversion project, make sure that your environment meets the following prerequisite conditions. A Control-M Agent is installed and running on the same environment as the Conversion Tool. The Control-M Agent is connected to a Control-M Server (version or later), and that the Agent is available. The Control-M Server allows execution of the "ctmpsm" and "ctmcreate" utilities by the Agent. For more information, see Authorizing which Control-M Server utilities a Control-M Agent can request in the Administrator Guide. The two script files, "capturescriptunix.txt" and "capturescriptwindows.txt", have been copied from the Conversion Tool's script folder, <Conversion Home>/scripts/DataCollection, to the Control-M Server. Some terms were changed in Control-M Workload Automation version (V8). The following table lists the terminology changes from version to version that are relevant for this document. Version Version Table Owner Node User Daily AutoEdit Folder Run as User Host Order Method Variable Release CAR You can now load the Conversion Tool's draft files into Control-M V8. The Conversion Tool also includes Control-M V8 terminology in both the user interface and the online help files. Release CAR CAR Search and Filter capabilities are now available in conversion and assessment reports. All windows in the Conversion Tool can now be resized. 11

12 Release CAR (UC4) CAR CAR CAR CAR CAR The Control-M Conversion Tool now converts the UC4 scheduling environment to the Control-M environment. The exclude_calendar now converts to CONFCAL (confirmation calendar). When a scheduling stream uses the PROMPT keyword, the converted Control-M job waits for confirmation using the wait confirm functionality. A schedule with simple RUNCYCLE definition that contains a shifting functionality (+n) now converts to CONFCAL in Control-M. A schedule with a simple AT definition that contains a shifting functionality (+n) now converts to CONFCAL in Control-M. An option was added to the conversion rules to convert the OPENS statement to a File Watcher job in Control-M. Release CAR (Dollar Universe) The Control-M Conversion Tool can now convert the ORSYP Dollar Universe scheduling environment to the Control-M environment. Release CAR CAR Control-M Conversion Tool can now also convert the IBM Tivoli Workload Scheduler scheduling environment to the Control-M environment. The Control-M Conversion tool can now perform scheduling plan validation. The Validation phase of the Conversion Tool can now create the scheduling plan of the SMART folders and jobs in Control-M and compare it to the current plan or scheduling history when the source application is Autosys. For other vendors, you can view the Control-M scheduling plan and can perform manual or visual comparison with the current plan. To view the validation schedule panel, set your screen resolution to at least 1152x

13 CAR The Conversion report now opens on the View by action view (default), instead of View by message type view. Release CAR The Control-M Conversion Tool now provides an additional option in the Conversion rules to convert CA Jobtrac jobs to Control-M jobs. Release CAR (Unicenter WLM) CAR CAR Control-M Conversion Tool can now convert the CA Unicenter WLM (TNG) scheduling environment to the Control-M environment. The Conversion Tool now provides an additional option in the Conversion rules to convert Autosys File Watcher jobs to Control-M/CM for Advanced File Transfer jobs by default or to use the Control-M File Watcher utility. The Conversion Tool now provides an option to set the target Control-M/Server host name from the Conversion Tool wizard. The default value is the localhost. 13

14 Corrected problems The following corrected problems were reported in previous releases of the Control-M Conversion Tool. The list of corrected problems is also available under the following solutions in the Knowledge Base: : KA : KA : KA : KA : KA : KA : KA : KA : KA Release Heading # CAR (Cron & MS Task Scheduler) CAR CAR (SAP) CAR When the installation folder name contains spaces, the automatic data collection step fails. Workaround: Copy the Control-M Conversion Tool to a folder whose name does not contain spaces. This issue may result in the creation of the file, X:\Program. The existence of this file may cause unexpected behavior in some applications. See for more information. During conversion, jobs that do not belong to any table are placed in a "StandAloneJobs" folder. Some of the jobs in this folder do not have any scheduling criteria and should only be ordered when needed or "on-demand". However, even though some or all of the jobs are "on-demand" jobs the StandAloneJobs folder is set to be ordered every day (UserDaily=SYSTEM). The same is true for SMART folders. During conversion, the SAP Account field is not mapped to the Run As field in Control-M V8. During conversion, the version specified for a condition is ignored, and the version of the defining job is used instead. 14

15 Heading # CAR CAR (Autosys, Jobtrac, and Unicenter WLM) In SCLs when defining the command line for Jobtrac DS jobs, if the command line contains more than 32 characters, and several lines are used in the definition, blank spaces are not added when the command line sections are joined together. During conversion, the cyclic interval for Autosys, Jobtrac, and Unicenter WLM jobs is converted in the wrong format, and as a result, is ignored in Control-M V8. Release CAR CAR CAR CAR CAR CAR (Autosys & TWS) CAR CAR CAR If you are using V8 mode, and you want to edit a Control-M field in the Fields Editor tab of the Conversion Rules window, when you click the > icon to add a parameter to the field's value, the Field list is unavailable. During conversion, messages might be appended to converted job descriptions. This could cause a job description to exceed the 4,000 character limit, and result in validation errors when loading the converted data to Control-M/EM. If you cancel the importing data process, it can take several minutes for the cancellation process to finish. In the Fields Editor tab of the Conversion Rules window, the Edit button is active even though a field has not been selected. In the Fields Editor tab of the Conversion Rules window, when you select a field, click Edit, and then close the editor, the field that you selected in the Fields Editor tab is no longer selected. In the online help, in the Validation section, there are no instructions how to extract the forecast report from Autosys and TWS. Quotes are removed when converting command line parameters to variables. After conversion, the attribute, std_in_file, is not surrounded by quotes. This can cause the command to fail. Conversion fails when the length of the MU attribute of a depcon is less than five characters. 15

16 CAR (Dollar Universe) CAR CAR CAR CAR (Unicenter WLM) CAR (Unicenter WLM) CAR (Unicenter WLM) When the last condition in a formula is not converted, the ending parenthesis is not added to the conditions list. The data is validated during the conversion process. However, when loading the draft file(s) to Control-M V7, a message appears indicating there are validation errors but the message doesn't contain specific information about the errors. Quantitative and control resources do not appear in the action report. In schedule files, the Conversion Tool does not identify the colon (used to separate attributes from the job list) when there are other characters on the same line as the colon. OUTCONDs may not be generated if the physical Host ID is different from the logical CPU name that is defined in TWS. During conversion, Unicenter WLM incorrectly converts the CRITKEYS="MNTHD#L" keyword. For example, it converts the month days to "DL" instead of "L1". During conversion, Unicenter WLM incorrectly converts the CRITKEYS="mmm AND WORKDM01" keywords. For example, it converts the month days to "ALL,L1". When the original JOBSET ID contains a comma, the draft file fails to load to Control-M Workload Automation, and the error, "Encountered an improper argument" appears. Release CAR If you import a draft file into Control-M V8, and the MAXRERUN attribute value is empty, the error, "The MAXRERUN attribute is invalid" appears. Release CAR OUT conditions may not be generated if the physical Host ID is different from the logical CPU name defined in TWS. 16

17 CAR (Dollar Universe) Conversion fails when the length of a depcon MU attribute is less than five characters. Release CAR CAR CAR CAR CAR CAR (Unicenter WLM) CAR CAR CAR CAR The user is prompted to save conversion rules changes even when no changes have been made. If multiple conversion files are created by the conversion tool, only the first one is loaded when the user selects Load converted data to Control-M. If the conversion result files are not stored in a folder, the files do not appear in the Conversion Results area in the Loading to Control-M screen. The Validation Report window can now be resized. In the Validation Report window, the current day is now highlighted in yellow and can be easily located. Support of TNG SAP parameters is expanded. Also, in the Conversion Rules window, the SAP Editor WLM tab and the fields table was removed, and the Enable SAP Conversion check box was moved to the Additional WLM Rules tab. The Enable SAP Conversion check box is selected by default. The Host ID parameter now uses the physical name of the CPU in converted jobs. When a SAP job s command line ends with "+r", the conversion fails. For SAP jobs, the command line format, <name>=<value>, is now supported. When a job condition expression contains nested parenthesis that are either in the beginning or the end of the condition, the conversion fails. Now the conversion is successfully completed but the nested part of the condition does not convert. 17

18 Release CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR The validation report shows that all jobs in a SMART folder are scheduled, but the SMART folder itself is not scheduled. In the Validation screen, some entries appear twice instead of once. When importing conversion XML data files, the PARENT_FOLDER field is set to the wrong value. When the DOCOND name contains '<' or '>' symbols, the draft XML validation fails. Autosys conditions in the JIL that have the symbols "&" or " " included in their definition are not converted if there is no space before or after the symbol. When the not_running resource is assigned to a box level, the resource does not convert to a Control-M SMART or sub folder. For variables, the name of the variable is converted instead of the value of the variable. The Control-M Conversion Tool only provided basic support for SAP jobs. Now there is full support for Autosys SAP jobs using the SAP interface. If a job in a table does not have scheduling definitions, it defaults to run all of the time. Now the job inherits the scheduling definitions of the parent table. Start times in folders are not converted. When a variable ends with a parenthesis ')<blank>' or contains a parenthesis such as a date specific line, "var=value,(<date>[,date])", evaluation fails. A job that has a control resource defined as exclusive converts as both exclusive and shared. 18

19 CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR When converting UDEF dates, the date, February 29th, is identified as an invalid date. Converted jobs have In or Out condition text in lowercase letters. Now the text is changed to uppercase letters. In the Capturing Data screen, the field, Variable definitions, was changed to Parameter definitions. For jobs that have no scheduled day or month, a default value is entered (month, all-yes and days, all-yes). Now they remain empty when no scheduling parameter is specified. Tables that are set to ON REQUEST or DRAFT are set to the Order Method system (run the relevant jobs every day) after conversion. Now the Order Method parameter is empty. Dummy jobs that contain more than 64 characters, are converted as invalid (generated invalid error). Now the names of the dummy jobs are truncated. When converting parameters to Control-M variables, extra quotes appear around the variable. The AT statement is considered part of the RUNCYCLE definition. When Schedule contains OPENS and CARRYFORWARD statements, the Assisting job created from the OPENS statement does not contain Maxwait. When there is only one OPENS statement in the schedule level, evaluation fails. If the "-user" scriptname variable is not specified, the job is not converted to a Control-M SAP job. After conversion, variables appear in the wrong order. 19

20 CAR CAR CAR (Dollar Universe) CAR (Tidal) CAR (Tidal) CAR (Tidal) When a scriptname variable has a space at the end, an empty variable is created during conversion. Now the extra space is ignored, and an empty variable is not created. The CARRYFORWARD parameter value does not properly convert to the Control-M parameter, MAXWAIT. The daily launch window (the time of day to schedule the job) is not converted. Now the Control-M Conversion Tool converts the daily launch window, using the first scheduled time to start the job. The conversion process doesn't finish. When the job "WORKING_DIR" contains one character, evaluation fails. When a job uses a calendar that doesn't exist in the EVNTMST file, evaluation fails. Release CAR (Unicenter WLM) CAR (Unicenter WLM) When using the Conversion Tool to convert Unicenter WLM jobs, the Days calendar field might remain empty in a Control-M job and a validity check error might appear in Control-M/Desktop. This occurs if CRITKEYS, in the Unicenter WLM job definition, is set to FOMWORK and a calendar was not specified. When using the Conversion Tool to convert Unicenter WLM jobs, if a Unicenter WLM calendar depends on an external calendar with two different actions, one of the following results might occur: If the last application of the dependency on the external calendar is not with the Off action, but instead with either the On or Invert action, the Control-M calendar will not be correctly converted, but an ERR0003 error message might not be issued to indicate the problem. If the last application of the dependency on the external calendar is with the Off action, the Control-M calendar could be correctly converted, but an ERR0003 error message might be issued, incorrectly indicating a problem, and preventing the calendar from being converted. 20

21 CAR CAR CAR CAR CAR CAR CAR CAR CAR CAR The application attribute is not converted to Control-M when running an Autosys conversion. The max_run_alarm and min_run_alarm parameters are converted with incorrect values when running an Autosys conversion. Exact text searches might fail when run on conversion reports. This occurs because Non-ASCII characters are used in report messages when running a conversion. The character '.' is not used to concatenate String (or variable) to variable in converted jobs. For example, "${varname}sundry_string" should be converted to Control-M "%%varname. sundry_string". However, the string is converted to "%%varnamesundry_string". The $${var_name} format for variable usage in the JIL file is not recognized when converting from Autosys to Control-M. %%JOBNAME variable is used in jobs that are converted from Autosys to Control-M. However, it was expected that after the conversion from Autosys to Control-M that the variable would be %%AUTO_JOB_NAME. A message is not issued for the "Lookback conditions" unsupported feature when converting from Autosys to Control-M. Runcycle names that exceed 20 characters are truncated to 20 characters when they are converted to Control-M Rule Based Calendar names. Message INF6103 is issued, reporting the original TWS name and the truncated name. In cases where truncation results in duplicate Control-M Rule Based Calendar names, both names are renamed. For example, if the TWS schedule is defined with two runcycle names about_twenty_characters and about_twenty_characters2, they will both be truncated to about_twenty_charact and message INF6103 is issued. To preserve unique naming, the Control-M Rule Based Calendar names are renamed to about_twenty_chara_0 and about_twenty_chara_1. In cases where the format for the specific date entry in runcycle uses a two digit year a message is not issued, even though the definition was not converted. PeopleSoft jobs with Type option are converted with a single quote [ ' ']. However, the expected results, when converting from TWS to Control-M, is to have PeopleSoft jobs with Type option without single quotes. 21

22 CAR CAR CAR CAR CAR CAR CAR CAR (Tidal) Jobs are missing from the conversion draft and warning message WRN6018 is issued. This occurs when the TWS jobs are in the schedule file but are not in the '<CPU>#' format. Conditions for aliased jobs are not created correctly when converting from TWS to Control-M. Out conditions are not created if scheduled dependency is used when converting from TWS to Control-M. The warning message "The value ABENDPROMPT for the attribute RECOVERY cannot be converted" (WRN0005) is issued when converting TWS jobs when the ABENDPROMPT attribute is not used by TWS jobs. Control-M jobs and SMART folders that were converted from TWS schedules might not be scheduled correctly when TWS "EXCEPT" scheduling statements are used and because, in Control-M, the relationship between Rule Based Calendars (RBCs) is always OR. The keyword EVERYDAY is converted into a Calendar, instead of being converted into the scheduling keyword ANY. Jobs defined with file dependencies test only once for file dependencies before the job is executed, even if the file is not found. Control-M Conversion Tool fails to convert and evaluate data when running Tidal version 5.0. Release CAR CAR CAR The Autosys description is converted with commas (") from JIL to the job description during the conversion of Autosys data. Jobs that are defined with a single value under "start_times:" are converted to cyclic with specific times. The converted job is displayed as cyclic even though it will run only once. The Group field is not converted during the conversion of Autosys data. 22

23 CAR CAR CAR CAR CAR CAR The ' ' operator in the JIL 'condition' is converted as 'AND' instead of 'OR during the conversion of Autosys data. Converted jobs that used Autosys "run_calendar" will have the calendar under DAYSCAL even though they do not have any month day scheduling definitions Converted FileWatcher jobs fail and issue the following IOALOG message during the conversion of Autosys data: Failed to Load Back End Name 'FileWatch'. You cannot enter more than 4 characters in the Unit field. An error message is not issued if more than 4 characters are entered. Data capture fails during the conversion of Jobtrac data when contents of the RESOURCE file has asterisks [*]. Data capture fails during the conversion of Jobtrac data when the JCL files contain the word EXEC as a substring instead of inside a step command. Release CAR (Unicenter WLM) CAR When using the Conversion Tool to convert Unicenter WLM jobs, a Control-M dummy job is not created for a folder if the PRIOR handling conversion rule is set to Dummy and the predecessor is a JOBSET (PSET without a PJOB) definition. CA AutoSys Workload Automation jobs that are defined with a single time setting are converted to a cyclic job with a specific time in the Control-M environment. Release CAR CAR The Conversion Tool does not provide a summary of the scheduling data assessment report for existing data. A calendar name might not be valid in Control-M when the Conversion Tool does not truncate calendar names longer than thirty characters (length allowed by Control-M). 23

24 CAR CAR CAR CAR (Autosys and Tidal) CAR CAR CAR CAR CAR CAR CAR (Tidal) CAR (Tidal) The Conversion Tool does not issue an information message that the redirection operators are ignored for the Autosys std_out_file and std_err_file parameters. The Conversion Tool always overwrites the redirection operators. The Conversion Tool issues a warning message in the Evaluation report that the user should define a calendar manually even though it exists in the calendar definitions JIL file. Instead of using a default timezone, the Conversion Tool defines a Timezone for a Control-M job even though it is a local datacenter Timezone. Jobs with priorities that do not have dependencies might run in a different order as Autosys and Tidal priority definitions do not convert to the correct priorities in the Control-M/Server. Jobs might run at the wrong times if an Autosys job with two start time definitions converts to a cyclic job rather than a job with specific time sequences. The Autosys environment variables might not convert as Control-M variables for job task type command. Jobs might not convert if the Control-M job name default generation was changed in the Conversion rules. Jobs might not be ordered if an Autosys job is defined with weekdays:all. The jobs convert to Control-M without a WEEKDAYS definition. The default is set to create standalone jobs in separate SMART folders rather than one Control-M Scheduling folder. The Conversion Tool does not convert table conditions if an Autosys box was defined in JIL with the condition attribute. The converted folder will be submitted based on time/date criteria alone without any conditions. The data capture might take a long time since all tables are being exported from the Tidal database including irrelevant tables that do not contain scheduling data. The until time attribute in scheduling criteria of a SMART folder does not affect all jobs. Jobs might be submitted outside the time frame for the folder. 24

25 Support for Control-M Conversion Tool Levels of support BMC provides full support for Control-M Conversion Tool For more information about the latest support policies and guidelines, see the Customer Support page of the BMC website at Related documentation To view the latest BMC documents, including documents in other languages, see the Customer Support website at Notices, such as flashes, technical bulletins, and release notes, are available on the website. You can subscribe to proactive alerts to receive messages when notices are issued or updated. For more information about proactive alerts, see the Customer Support website. The following provide more information about Control-M. Administration Getting Started Installation Language and customization Messages Parameters Reporting Facility Control-M Self Service SSL Management Upgrade Using Control-M Workload Automation Utilities 25

26 Customer support If you have questions about a BMC product or have problems with a BMC product, see the support website at You can view or download product documents, find answers to frequently asked questions, and download products and maintenance. If you do not have access to the web, and you are in the United States or Canada, contact Customer Support at Outside the United States or Canada, contact your local BMC office or agent. 26

27 Copyright 2013 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. IBM Tivoli Workload Scheduler trademark or registered trademark is the trademark or registered trademark of International Business Machines Corporation in the United States, other countries, or both. Linux is the registered trademark of Linus Torvalds. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation. For the provisions described in the BMC License Agreement and Order related to third party products or technologies included in the BMC Product, see the "ThirdParty" subdirectory in the installation directory of this product. BMC SOFTWARE INC 2101 CITYWEST BLVD, HOUSTON TX , USA Customer Support: (United States and Canada) or contact your local support center. 27

28