Control-M/Server for UNIX and Microsoft Windows Release Notes April 2013

Transcription

1 Control-M/Server for UNIX and Microsoft Windows Release Notes April

2 Contents Introduction to Control-M/Server for UNIX and Microsoft Windows Release Notes... 3 Control-M/Server enhancements... 4 Control-M/Server corrected problems... 6 Control-M/Server compatibility Control-M/Server compatibility with Windows Control-M/Server compatibility with UNIX/Linux Control-M/Server compatibility with Control-M components Control-M/Server integration with BMC products Control-M/Server language compatibility Online help compatibility Product Distribution Obtaining installation files through EPD Obtaining installation files using FTP Obtaining installation files through the BMC sales representative Installation Installing fix pack 1 on UNIX Installing fix pack 1 on Windows Uninstalling fix pack 1 from UNIX Uninstalling fix pack 1 from Windows Starting the SQL server Support for Control-M Levels of support Related documentation

3 Chapter Release Notes Introduction to Control-M/Server for UNIX and Microsoft Windows Release Notes BMC Software is releasing version fix pack 1 of Control-M/Server for UNIX and Microsoft Windows (Control-M/Server). These release notes provide information about the enhancements and resolved problems in this release. The information in this document supplements and supersedes information in the Control-M Workload Automation manuals. 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 Control-M/Server enhancements The following table describes Control-M/Server enhancements for version fix pack 1. Tracking # Description CAR CAR CAR Name: Network Load-Balancer Functionality and Benefits Control-M now supports network load-balancing routers (for example, BigIP), where the job is submitted to a virtual hostname and then routed to one of the nodes participating in the load balancing group. To enable the feature the Control-M/EM system parameter EnableLoadBalancerRouter must be set to true, and the CMS (Configuration Manager Server) must be recycled. Prerequisites: Control-M/EM version fix pack 1 and Control-M/Agent version fix pack 1. For more information, see the Control-M Workload Automation Administrator Guide. Name: Renaming a Control-M/Server component. Functionality and Benefits: You can now rename a Control-M from the CCM using a friendly GUI and a few simple steps. The new name is automatically applied to all Control-M/Server name occurrences in the Control-M/EM database definition. In case of any naming mismatches of depending entities, you are prompted directly to the point of the miss-match to enable easy resolution. For more information, see the Control-M Workload Automation Administrator Guide. Control-M/Server downtime during the new day procedure is reduced. SYSTEM ordering works in the background before the new day procedure enters information into a set of temporary database tables. This performance improvement is enabled when the configuration parameter NEWDAY_MODE is set to a value of 1 or above (default). This enhancement requires approximately 30% additional database space. 4

5 Tracking # Description CAR Control-M/Server now supports Windows Server WCTM Name: Exclude RBC (Rule Based Calendar) Functionality and Benefits You can now exclude dates from the schedule using the Exclude RBC feature. For example, specific dates, such as holidays, can be excluded from a schedule. In the Planning Domain, you can now easily define scheduling criteria when a job, sub folder or SMART folder should not be ordered (Excluded). This makes it simple and intuitive to set and manage both Include/Exclude RBC scheduling criteria from a single user interface point. Prerequisites: Control-M/EM version fix pack 1, and INCONTROL version NOTE: You cannot check-in a workspace with jobs that belong to a Control-M/Server version fix pack 1 with Exclude RBC mode enabled, if you are using a Control-M Workload Automation client version NOTE: If this feature was disabled during the fix pack installation, you need to change RBC names that start with! and run the enable_exclude_rbc.pl perl script from the <scripts> directory. In Control-M/Server for z/os, the default value for EXCLURBC is N, and you need to verify that no RBC, both at Control-M hierarchy and in each SMART folder, starts with!. Afterwards, change the value to Y. For more information, see the Control-M Workload Automation User Guide. 5

6 Control-M/Server corrected problems The following table describes the problems that were reported in earlier releases of Control-M/Server and have been corrected. The list of corrected problems is also available at Tracking # Description BMPM BMPM BMPM BMPM BMPM The ctmpsm utility ignores zoom and save security restrictions when trying to add or delete an in or out condition of a job. The ctmpsm utility ignores security restrictions when trying to remove a table. When running the ctmrpln daily report utility, the application field is truncated to 15 characters, the group field to 15 characters, and the description field to 28 characters. Blanks are incorrectly truncated from variable expressions containing the %%BLANK variable. A HostId can be added to a HostGroup, which has already been deleted. BMPM The ctmexdef utility truncates on-statements and code fields to 30 characters. CAR CAR CAR CAR CAR Jobs defined with Days D*P<period identity> are scheduled to run only on the first 255 days of the period. The secondary database used for mirroring can be corrupted when ordering jobs that use control resources. The ctmpsm utility ignores security restrictions when trying to add a calendar. The ctmcreate utility should prevent creating a SMART folder, sub folder name, or job name where the name contains one or more of the following characters: single quotation marks / $ *? Where there are large scheduling folders and many uploads, upload requests and the ctmdefine utility may fail. When this problem occurs, the Control-M/EM user receives the following error message: CTM5301 SERVER INTERNAL ERROR TYPE from accept_sch 6

7 Tracking # Description CAR CAR CAR CAR CAR CAR CAR After updating from versions / to version , the User daily and Ordering process can become slow due to invalid values in the database, which reference scheduling group tags Id s that do not exist. When a Control-M/Agent is connected through a transient connection and uses a different name from the name used in Control-M/Server, unnecessary warnings appear in the Network Process log. The following warning message is issued in this situation: NS: WARNING: agent XXX is configured with a wrong logical name: YYY. Please use ctmagcfg to fix this inconsistency. The warning correctly appears when Control-M/Agent is connected through a persistent connection. A SMART folder may remain in executing state even after all the jobs in the group have ended. In rare scenarios, mirroring database becomes damaged. It may occur when mirroring is enabled, and more than one of the Control-M/Server processes or utilities perform actions in the mirror database. The following error messages may appear in the Control-M/Server logs: :34:45.90 U_CTMPSM983228: User 'ctmsrv' unable to open/read tmp file:./tmp/x6almb, errno= :34:46.17 U_CTMPSM983228: checkerr(structlogin=20ae6860) - Error, ORA-01005: null password given; logon denied :34:46.17 U_CTMPSM983228: DB_GetDBproc() - Failed in OCISessionBegin (MIRROR) :34:46.17 U_CTMPSM983228: CTM6001 -> DB_GL_mirrordb_mark_nouse: ERROR occured. marking mirror db as unused!! Cyclic jobs that fail to submit and end in RETRY SUBMIT state are not resubmitted immediately. The job waits until the next cyclic time. Unable to add, edit, or delete shout destinations from Control-M Configuration Manager when Control-M/Server uses Sybase database. The ctmexdef utility does not export the value of the INTERVAL attribute of a job when that job is not cyclic. 7

8 Tracking # Description CAR CAR CAR CAR CAR CAR CAR Jobs fail to be submitted because the control resource they require seems to be unavailable. This happens when the control resource is reserved for critical jobs only. (Microsoft Windows only) User daily job ends OK but no jobs are ordered, because of a CTMUDLY database error. On rare occasions, a job is post processed, but the exclusive control resource is not released. When a job s Shout to Program runs for a long time, occasionally, submission and post processing of jobs can be delayed. In order to minimize delay, a time limit is now set for the Shout to Program, which is determined by SHOUT_TO_PROGRAM_TIMEOUT parameter in <Control-M Server home directory>/ctm_server/data/config.dat file. This parameter can also be modified in Control-M Configuration Manager. By default, if the job's shout to program does not complete after 20 seconds, job processing continues, without waiting for the program to end. The job's log will display the message ID 5228: SHOUT TO <shout to program logical name> STILL RUNNING. [JOB SMART table Sub table] PROCESSING CONTINUES. The job's SHOUT_TO_PROGRAM_TIMEOUT parameter is ignored by the ctmshout utility, so there is no time limit. Valid values for the parameter: 0-2^31 seconds (0 means no time limit (the processing of the job waits until the shout to program completes)). Default value: 20 seconds The Control-M/Server migration warning fix process WRN703 (for fix warning 703) might fail in case the job name contains the following characters: [ - ]with the message: Invalid [ ] range in regex When updating the definition folders and the user decides to truncate the active folders, Control-M Workload Automation is not synchronized with Control-M/Server, and old jobs are still displayed in Control-M Workload Automation. (Oracle only) Cannot run copy_mirror -n1 as batch (copy data from primary database to mirror database in non-interactive mode). 8

9 Tracking # Description CAR CAR CAR CAR CAR Occasionally, when the update export fails, it mistakenly reports that it ends successfully. As a result, the update import phase can fail because data was not exported (such as missing AGPRM directory). Control-M/Server might hang and stop running jobs when disconnected from Control-M/EM and running on MSSQL with a Mirror server. Inconsistencies between UNIX and Windows in the way a debug is turned on/off for utilities. In UNIX you need to set two environment parameters and in Windows you need to open the registry and update the parameters. Zoom & Save authorization may fail if the new host group lacks proper authorization after Zoom& Save changes. In a Windows server environment, mail timeouts are calculated incorrectly resulting in very long timeout periods being implemented. 9

10 Tracking # Description CAR In rare scenarios, submission of time zone jobs fail and end NOTOK with the message: INVALID TIME ZONE STATUS CHANGED TO FAILED TO SUBMIT JOB STATE CHANGED TO Failed to submit Additionally, one of the following messages may be generated in the log: SL: SL_REC_check_time: GM_TIME_calculate_TZval_adjustment working with predefined daylight saving is not supported. SL: SL_REC_check_time: GM_TIME_calculate_TZval_adjustment Unknown time zone format: (GMT+01:00) FROM :00 TO :00 (GMT+02:00), length: 3 SL: SL_REC_check_time: GM_TIME_calculate_TZval_adjustment Unknown time zone format: (GMT+01:00) FROM :00 TO :00 (GMT+02:00), length: 4 CAR CAR CAR When the product changes to suspend mode during the ordering process, sub folder jobs are partially ordered during system user daily. Duplicate variable names are being removed when ordering a folder. When a Control-M/Agent on the local machine is unavailable for more than a few minutes, Agents remain in an unavailable or discovery state. 10

11 Tracking # Description CAR CAR CAR CAR CAR When the job name or file name is long, an error is reported in Control-M/EM API order-force response, even when the operation was successful. The following error message is received: <ctmem:job> <ctmem:error_list ctmem:highest_severity="error"> <ctmem:error ctmem:major="100" ctmem:minor="6" ctmem:severity="error"> <ctmem:error_message>entry not found 90', orderno='00004s' </ctmem:error_message> </ctmem:error> </ctmem:error_list> </ctmem:job> Control-M/Server download slows down when many jobs exist in the active jobs database. When the configuration parameter NEWDAY_MODE is set to a value of 1 or above (default 1), download speed enhancement is enabled. The following parameters control various aspects of the download process: DOWNLOAD_THREADS: Specifies the number of threads that would handle the download process where parallel download is enabled. DOWNLOAD_CACHE_SIZE: Specifies the number of jobs is cached in memory to speed up the download. When you increase the number of jobs it causes the product to consume more memory. The Control-M/Sever (CE process) cannot start when machine is using Internet Protocol Version 6. Entities of a folder/sub folder might not be submitted according to their priority after their Parent Folder starts to execute. A New Control-M utility, dbu_fsync_switch, changes PostgreSQL database fsync mode and may affect database performance. Recycle the database to take effect. Values: ON, OFF Default: OFF 11

12 Tracking # Description CAR CAR CAR CAR (PostgreSQL Dedicated only) Control-M/Server generates an X-Alert if database archiving is not enabled (as recommended by BMC). This Alert frequency is controlled by the ARCHIVING_CHECK_INTERVAL_DAYS configuration parameter (set to 0 to disable warning). Default: 7 days Control-M/Server also issues an X-Alert if Hot backup has not been performed for more than 4 days. This warning threshold is controlled by the NO_BACKUP_WARNING_DAYS configuration parameter (set to 0 to disable warning) Default: 4 days. For more information, see: KA in the Knowledge Base. Control-M/Server remains in a downloading state when the Control-M/EM machine or database is slow. Control-M/Server may fail to start where one of the semaphore IDs is occupied by another user. The following message appears in debug level 0: sem_op:failed in semop semaphore id<sem id> errno=13 Permission denied (Unix only) In rare cases, when another Control-M/Server is installed on the same machine, using an oracle database, Control-M/Server or Control-M/Server Configuration Agent (CA) fails to start. 12

13 Tracking # Description CAR CAR CAR CAR CAR Error messages may be issued after upgrading Control-M/Server to version as follows: (Windows only) When uploading or downloading a folder, calendar or a rule base calendar, the action fails and the following error message is issued: CTM4022 Internal Error occurred and the request failed (look for the log of CS<pid>) (Unix only) One of the following may occur: Upload of new folder, calendar or rule base calendar succeeds even though it exists in the Control-M/Server and it was upgraded from the previous Control-M/Server. Upload of folder, calendar or rule base calendar fails with an incorrect error message, when the Control-M/Server and Control-M/EM are synchronized, and both were upgraded from previous versions. The following error message is issued: CTM5705 [FOLDER CALENDAR Rule-Based Calendar] <name> PREVIOUSLY MODIFIED BY CONTROLM. REQUEST REJECTED When Control-M/Server runs in debug level 4, files that are internally created in the product's tmp directory are copied to proclog before being deleted. A cyclic job might run earlier than its specified interval, when setting its interval from attribute to TARGET. Jobs, SMART Folders, and sub folders' statistics are collected when they finish running. As a result, statistic clean up during the new day procedure is done too quickly. When the job completes and statistics are updated, the old statistics are now deleted in the same operation, reducing the time it takes for new day clean up. Control-M/Server fails to start when running on Windows 32bit operating system with more than 10,000 jobs defined in its database. 13

14 Tracking # Description CAR CAR CAR CAR Control-M/Server sends alerts to Control-M/EM when it is unable to resolve variables during job submission, although Control-M/Server's system parameter CTM_VARIABLE_SHOUT_ON_ERROR_URGENCY is set to N to suppress these alerts. Control-M/EM fails to add the alerts to the database, and therefore the alerts are not displayed in the Alert Window. Database error message appears in the gateway log. Updating the Agent's Check Interval attribute from the Control-M Configuration Manager fails when Control-M/Server runs on Linux. BufferUnderflowException might appear in the CE log file when you perform a request on a job using a Control-M/Server utility (such as: hold a job via ctmpsm, ctmwhy <order ID>), and in accordance with Control-M/Server security, you are not allowed to do so. For example: [WARNING],"2012/12/29 12:03:44.104","The following IPC GTW message from U_CTMPSM caused an exception when converted to EM message: DCE 0,120343,U_CTMPSM ,0,GTW,0,I ",T@6,com.bmc.ctms.ctmce.ServicesManager,handleIpcGtwMsg,com.bmc.ctms.ctmce.ServicesManager,"java.nio.BufferUnderflowException at java.nio.heapbytebuffer.get(heapbytebuffer.java :139) at java.nio.bytebuffer.get(bytebuffer.java:687) at com.bmc.ctms.infra.comm.dsect.dsectencoderdecod er.setsimplefieldbytes(dsectencoderdecoder.java :423) When Control-M/Server uses Oracle, SMART/Sub folders remain in executing state even though of all its sub folders have ended. 14

15 Chapter Release Notes Control-M/Server compatibility Control-M/Server can be installed on Windows and/or UNIX computers and works together with other products in the Control-M scheduling solution (for example, Control-M/EM and Control-M/Agent). The following lists the operating systems and other pre-installation requirements for Control-M/Server: Control-M/Server compatibility with Windows (on page 15) Control-M/Server compatibility with UNIX/Linux (on page 16) Control-M/Server compatibility with Control-M components (on page 17) Control-M/Server integration with BMC products (on page 18) Control-M/Server language compatibility (on page 19) NOTE: Before installing Control-M Workload Automation , you must check that you have Java version 1.6 operating system patches/packages prerequisites on your computer. You can do so by running the latest check_req utility. You may also need additional operating system patches/packages. For more details, see the Knowledge article KA in the Knowledge base. Control-M/Server compatibility with Windows The following table lists the supported Microsoft Windows operating systems and databases for Control-M/Server. Operating System Bits Compatible Processors Database servers Windows Server 2012 Standard Edition 64 x86_64 Microsoft SQL Server 2008, 2008 R2, 2012 A BMC-supplied PostgreSQL server and client Windows Server 2008 Standard Edition x86 x86_64 Microsoft SQL Server 2005, 2008, 2008 R2, 2012 A BMC-supplied PostgreSQL server and client Windows Server 2008 Enterprise Edition 15

16 Operating System Bits Compatible Processors Database servers Windows Server 2008 R2 Standard Edition Windows Server 2008 R2 Enterprise Edition 64 x86_64 Microsoft SQL Server 2005, 2008, 2008 R2, 2012 A BMC-supplied PostgreSQL server and client Control-M/Server compatibility with UNIX/Linux The following table lists the supported UNIX/Linux operating systems and databases for Control-M/Server. Operating system Version Bits Compatible processors Database servers AIX (Update 9) HP-UX (Update 3) 64 Power An Oracle 11 database server. Itanium Sybase Adaptive Server Enterprise and later, using the ISO1 character set A BMC-supplied PostgreSQL server and client (B ) Oracle Solaris 11 SPARC 10 (Update 7) 9 (Update 9) 16

17 Operating system Version Bits Compatible processors Database servers Red Hat Enterprise Linux Server SUSE Linux Enterprise Server 6 5 (Update 1) x86_64 Oracle Enterprise Linux Server 6 5 An Oracle 11 database server. A BMC-supplied PostgreSQL server and client. Control-M/Server compatibility with Control-M components The following table lists the versions of Control-M/EM and Control-M/Agents that are compatible with Control-M/Server. Component Version Control-M/Enterprise Manager Control-M/Agent for UNIX and Microsoft Windows Control-M/Agent for iseries (AS/400)

18 Component Version Control-M/Agent for MAPPER System for 2200 Control-M/Agent for OpenVMS Alpha, Itanium, and VAX Control-M/Agent for Tandem Guardian Control-M/Agent for UNISYS with the following fix packs: PANDB for Alpha PACOV for Itanium Control-M/WebAccess NOTE: The following items will not be supported by December 31, 2012: Control-M/Agent for UNIX and Microsoft Windows Control-M/Agent for iseries (AS/400) Control-M/Agent for UNISYS Control-M/Agent for UNISYS Control-M/Server integration with BMC products The following table lists third party software that is compatible with Control-M/Server. BMC product Version BMC Remedy 7 18

19 Control-M/Server language compatibility The following table lists the languages that are compatible with Control-M/Server. Language Level of support East Asian (CJK) Western European (Latin-1 character set) Basic ASCII The following languages are now supported: Traditional Chinese Simplified Chinese Japanese Korean Special Western European characters used in English, Spanish, German, and French can be specified in most free-text fields and parameters. US English 19

20 Chapter Release Notes Online help compatibility The following table lists the supported browsers for the Online help: Third party software Version Internet Explorer Mozilla Firefox Google Chrome 3.6 and higher 4 and higher 20

21 Chapter Release Notes Product Distribution The following procedures describe how to obtain the installation files for Control-M/Server for UNIX and Microsoft Windows version fix pack 1, using EPD, FTP, or the BMC Sales Representative: Obtaining installation files through EPD (on page 21) Obtaining installation files using FTP (on page 22) Obtaining installation files through the BMC sales representative (on page 22) Obtaining installation files through EPD This procedure describes how to obtain the Control-M/Server for UNIX and Microsoft Windows installation files through EPD. To obtain installation files via EPD: 1. Click and follow the instructions on the EPD site until you reach the Download Files page. 2. Do one of the following: UNIX: Do the following: a. Download and save the file into a temporary directory : <INST_TEMP_DIR> If you downloaded it to your computer, transfer it to a UNIX computer using binary ftp mode to an intermediate location: <UNIX_TAR_Z_LOCATION> b. CD into: <INST_TEMP_DIR> c. Extract the compressed tar file with the following command: uncompress c <UNIX_TAR_Z_LOCATION>/<InstallationFileName.tar.Z> tar xf For example : uncompress c /tmp/drost _linux-x86_64.tar tar xf If you have do not have an uncompress command, use zcat instead of uncompress c: zcat <UNIX_TAR_Z_LOCATION>/<InstalltionFileName.tar.Z> tar xf Windows: Do one of the following: o o Download and save the.iso file to a temporary directory, and then burn it onto a DVD. Download and save the relevant.zip file to a temporary directory. 21

22 Obtaining installation files using FTP This procedure describes how to obtain the Control-M/Server for UNIX and Microsoft Windows installation files using FTP. To obtain installation files using FTP: 1. Download the installation files from one of the following locations: UNIX: ftp://ftp.bmc.com/pub/control-m/opensystem/control-m_server_for_unix_and_microsoft_win dows/8.0.00/pactv /unix Windows: ftp://ftp.bmc.com/pub/control-m/opensystem/control-m_server_for_unix_and_microsoft_win dows/8.0.00/pactv /windows 2. Log on as a Control-M/Server user, and create a temporary directory (for example,temp_inst_dir). 3. Copy the required files, as follows: UNIX: Copy the PACTV _<platform>_INSTALL.BIN file that is relevant to your UNIX system or PANFT iso in binary mode from the FTP site to the temporary directory that you created. Windows: Copy the PACTV _<Windows_platform>.exe file that is relevant to your Windows system from the FTP site to the temporary directory that you created. 4. Type the following command for each copied installation file to ensure that the fix pack installation has the necessary authorizations (UNIX only): chmod +x <installation_file> Obtaining installation files through the BMC sales representative This procedure describes how to obtain the Control-M/Server for UNIX and Microsoft Windows installation files through the BMC sales representative. To obtain installation files through the BMC Sales representative: To obtain a product DVD, contact your BMC Sales Representative. Contact information is available on the BMC website see 22

23 Installation The installation files for Control-M/Server version are available from the BMC FTP site, on the installation CD, or through Electronic Product Distribution (EPD), as described in Product Distribution (on page 21). The following procedures enable you to install and uninstall fix pack 1: Installing fix pack 1 on UNIX (on page 23) Installing fix pack 1 on Windows (on page 24) Uninstalling fix pack 1 from UNIX (on page 26) Uninstalling fix pack 1 from Windows (on page 26) These release notes provide installation procedures of fix pack 1 for Control-M/Server. For detailed instructions regarding installation of Control-M/Server, see the Control-M Installation Guide. NOTE: Before installing Control-M Workload Automation , you must check that you have Java version 1.6 operating system patches/packages prerequisites on your computer. You can do so by running the latest check_req utility. You may also need additional operating system patches/packages. For more details, see the Knowledge article KA in the Knowledge base Installing fix pack 1 on UNIX This procedure describes how to install Control-M/Server version fix pack 1 on UNIX computers. Before You Begin Ensure that you have met the following requirements: Korn Shell (KSH) installed Control-M/Server version installed 120 MB of free hard disk space available (same amount on the /tmp directory) To install fix pack 1 on UNIX: 1. Log in as a Control-M/Server user and run the following utility: ctm_menu 2. Press 1 - Control-M Manager and then press the following commands: Stop Control-M/Server Configuration Agent Stop Control-M/Server NOTE: During Control-M/Server fix pack installation, you might be asked to shut Control-M/Agent embedded with the Server s installation in case the Agent is running agentless jobs on UNIX except Linux (not relevant if the Server is already upgraded with fix pack 1). 3. Verify the status of each process by pressing 1 - Check All. 23

24 The following output message appears: SQL Server is running. Control-M is not running. Control-M Server Configuration Agent is not running. NOTE: If the SQL server is not running, see Starting the SQL server (on page 28). 4. Do one of the following: If you obtained the installation files using FTP (see Obtaining installation files using FTP on page 22), navigate to the temporary directory that you created. If you obtained a CD (using EPD or the BMC Sales Representative), mount the installation CD. 5. Install the fix pack using one of the following methods: To perform an interactive installation, type one of the following commands, and then press Y: o o CD: <CD>/Unix/setup.sh FTP: <temp_dir>/setup.sh To perform a silent installation, type one of the following commands: o CD: <CD>/Unix/setup.sh -s o FTP: <temp_dir>/setup.sh -s NOTE: You can change the directory location where the temporary installation files are extracted. For example, when there is insufficient disk space in the /tmp directory. You can use the following sample path to extract the files to another directory: <cdmount>/unix/setup.sh -d <location> The <location> variable is the required location. Control-M/Agent information now resides on the Control-M/Server database. If this is the first fix pack you are installing for Control-M/Server version , BMC recommends that you perform a backup of the database after the fix pack is installed. 6. Start the Control-M/Server processes by running the following utility: ctm_menu 7. Press 1 - Control-M Manager and then press the following commands: Start Control-M/Server Configuration Agent Start Control-M/Server Installing fix pack 1 on Windows This procedure describes how to install Control-M/Server version fix pack 1 on Windows computers. Before You Begin Ensure that you have 60 MB of free hard disk space available (same amount on the %temp% directory) 24

25 To install fix pack 1 on Windows: 1. Log in as a Control-M/Server administrator and run the following utility: ctm_menu 2. Press 1 - Control-M Manager and then press the following commands: Stop Control-M/Server Configuration Agent Stop Control-M/Server 3. Verify the status of each process by pressing 1 - Check All. The following output message appears: SQL Server is running. Control-M is not running. Control-M Server Configuration Agent is not running. 4. Do one of the following: If you obtained the installation files using FTP (see Obtaining installation files using FTP) navigate to the temporary directory that you created. If you obtained a CD (using EPD or BMC Sales Representative), insert the CD, and navigate to the Windows directory. 5. Install the fix pack using one of the following methods: To perform an interactive installation, double-click the <executable file> file and continue with the installation wizard, following the on-screen instructions until the completion of the installation. To perform a silent installation, open a command line and do the following: 6. Extract the fix pack files by typing the following command: <executable file> -e NOTE: If you are using Microsoft Windows Server 2008, run the silent installation from a command prompt that was opened with administrator privileges. 7. Navigate to %temp%\pactv and type the following command: silent.bat By default the files are extracted to %temp%. You can use -d<extractpath> to extract the files to another directory. Ensure that there is no space between -d and <extractpath>. Otherwise, the fix pack files are extracted to the default location: %temp%. Control-M/Agent information now resides on the Control-M/Server database. If this is the first fix pack you are installing for Control-M/Server version , BMC recommends that you perform a backup of the database after the fix pack is installed. 8. Start the Control-M/Server processes by running the following utility: ctm_menu 9. Press 1 - Control-M Manager and then press the following commands: Start Control-M/Server Configuration Agent 25

26 Start Control-M/Server Uninstalling fix pack 1 from UNIX This procedure describes how to uninstall Control-M/Server version fix pack 1 from UNIX computers. Before You Begin Ensure that all Control-M jobs have stopped. To uninstall fix pack 1 from UNIX: 1. Log in as a Control-M/Server user and run the following utility: ctm_menu 2. Press 1 - Control-M Manager and then press the following commands: Stop Control-M/Server Configuration Agent Stop Control-M/Server 3. Verify the status of each process by pressing 1 - Check All. The following output message appears: SQL Server is running. Control-M is not running. Control-M Server Configuration Agent is not running. NOTE: If the SQL server is not running, see Starting the SQL server (on page 28). 4. Uninstall the fix pack by using one of the following methods: To perform an interactive uninstall, type the following command, and then press Y: $HOME/patches/remove_fp -f PACTV To perform a silent uninstall, type the following command: $HOME/patches/remove_fp -f PACTV s 5. Start the Control-M/Server processes by running the following utility: ctm_menu 6. Press 1 - Control-M Manager and then press the following commands: Start Control-M/Server Configuration Agent Start Control-M/Server Uninstalling fix pack 1 from Windows This procedure describes how to uninstall Control-M/Server version fix pack 1 from Windows computers. 26

27 Before You Begin Ensure that all Control-M jobs have stopped. To uninstall fix pack 1 from Windows: 1. Log in as a Control-M/Server administrator and run the following utility: ctm_menu 2. Press 1 - Control-M Manager and then press the following commands: Stop Control-M/Server Configuration Agent Stop Control-M/Server 3. Verify the status of each process by pressing 1 - Check All. The following output message appears: SQL Server is running. Control-M is not running. Control-M Server Configuration Agent is not running. 4. Uninstall the fix pack by using one of the following methods: To perform an interactive uninstall, do the following: a. From the Start menu, select Control Panel > Add/Remove Programs > Control-M/Server fix pack 1. b. Select Remove. To perform a silent uninstall, do the following: c. Navigate to the following directory: <Control-M/Server home directory>\install\pactv \ NOTE: If you are using Windows Server 2008, run the silent installation from a command prompt that was opened with administrator privileges. d. From a command line, type the following command: uninstallsilent.bat 5. Start the Control-M/Server processes by running the following utility: ctm_menu 6. Press 1 - Control-M Manager and then press the following commands: Start Control-M/Server Configuration Agent Start Control-M/Server 27

28 Starting the SQL server This procedure describes how to start the SQL server for installations that use a dedicated or existing database. To start the SQL server for installations that use a dedicated or existing database: Do one of the following: To start the SQL server for installations that use a dedicated database, from the ctm_menu utility, type the following command: Control-M Manager > Start Database To start the SQL server for installations that use an existing (not dedicated) database, run an external command. 28

29 Support for Control-M These topics provide information about the following: Levels of support (on page 29) Related documentation (on page 29) Levels of support 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. 29

30 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. 30

31