Control-M/Enterprise Manager Release Notes April 2013

Transcription

1 Control-M/Enterprise Manager Release tes April

2 Contents Introduction to the Control-M/Enterprise Manager Release tes... 4 Control-M/EM... 5 Control-M/EM enhancements... 5 Control-M Conversion Tool included with Control-M/Enterprise Manager Control-M/EM corrected problems BMC Batch Impact Manager corrected problems Control-M/ Forecast corrected problems Control-M Self Service corrected problems Open issues and known problems Control-M/EM Compatibility Control-M/EM client compatibility with Windows Control-M/EM server compatibility with Windows Control-M/EM server compatibility with UNIX/Linux Control-M/EM compatibility with Control-M components Control-M/EM compatibility with third party software Control-M/EM integration with BMC products Control-M/EM 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 Installation requirements Installing fix pack 1 on UNIX Installing fix pack 1 on Windows Uninstalling fix pack 1 from UNIX

3 Uninstalling fix pack 1 from Windows Support for Control-M Levels of support Related documentation

4 Release tes Introduction to the Control-M/Enterprise Manager Release tes BMC Software is releasing version fix pack 1 of Control-M/Enterprise Manager (Control-M/EM). 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 is available here 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. 4

5 Chapter Release tes Control-M/EM The following topics describe enhancements and corrected problems for Control-M/EM fix pack 1: Control-M/EM enhancements (on page 5) Control-M/EM corrected problems (on page 10) Control-M/EM enhancements The following table describes the enhancements of Control-M/EM fix pack 1: Tracking # Description CAR QM You can now delete a Control-M/Agent or a Remote Host using the CCMCLI command from the command line. For more information, see the Control-M Workload Automation Administrator Guide. Name: JCL Verify Enhancements Functionality and Benefits: You can now verify the JCL of Control-M for z/os jobs directly from the Planning and Monitoring interfaces of Control-M/EM by invoking Control-M/JCL Verify and reviewing its verification results. For more information, refer to the Control-M/JCL Verify User Guide. NOTE: To enable this feature, Control-M/JCL Verify or higher must be installed in the same IOA environment where Control-M for z/os is installed. Prerequisites: INCONTROL version

6 Release tes Tracking # Description CAR CAR Name: Track Changes Functionality and Benefits: In the Planning Domain, you can now easily know which modifications were made to the job definitions. There are four types of changes: Deleted, Modified, New and Unchanged. You can track the changes using two different views: graphic indications on the job nodes of the flow diagram and a List View of all changed jobs and the type of change. For more information, see the Control-M Workload Automation User Guide. Name: Remote Browsing Functionality and Benefits: A Browse button now exists for browsing and selecting scripts and binaries from Control-M/Agent and remote host file systems (Distributed) and members from MEMLIB or DOCLIB (Control-M for z/os). This greatly simplifies the settings of scripts and binaries during the job definition specification. Prerequisites: Control-M/Server version fix pack 1, Control-M/Agent version fix pack 1, and INCONTROL version For more information, see the Control-M Workload Automation User Guide. 6

7 Release tes Tracking # Description QM The following Plug-ins have been updated or added to Control-M version interface standards: DataStage, Databases, SAP R3, SAP DA, SAP BW, and Tandem. 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/Server version fix pack 1 and Control-M/Agent version fix pack 1. For more information, see the Control-M Workload Automation Administrator Guide. 7

8 Release tes Tracking # Description WCTM CAR 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/Server 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. 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. 8

9 Release tes Tracking # Description CAR CAR CAR Name: Control-M Batch Discovery Functionality and Benefits: The BMC Control-M Batch Discovery utility now supports BMC Remedy Action Request System(ARS) Service impact data is output to csv files for use with BMC Atrium Integrator version Changes in BMC Atrium CMDB can be analyzed to understand their impact on Control-M Services. For more information on integrating BMC Control-M data into BMC Atrium CMDB, see the Control-M Workload Automation Administrator Guide. Name: Run as Dummy Functionality and Benefits: Each job can now be marked with a Run as Dummy indication. This means that the job does not execute any script or command in the active environment. The job remains with it s original job type and data, however it run as jobs that belong to the job type Dummy, as long as Run as Dummy is selected. For more information, see the Control-M Workload Automation User Guide. Control-M/Enterprise Manager now supports Windows Server CAR Control-M/Enterprise Manager now supports Windows 8. Control-M Conversion Tool included with Control-M/Enterprise Manager The Control-M Conversion Tool version is installed automatically when you install Control-M/Enterprise Manager For more information, see the Control-M Conversion Tool version Release tes. 9

10 Release tes Control-M/EM corrected problems The following table describes the problems that were reported in earlier releases of Control-M/EM and have been corrected. The list of corrected problems is also available here in the Knowledge Base. Tracking # Description Client installation required CAR CAR CAR CAR CAR CAR CAR Memory utilization constantly increases on the GUI Server on Windows 64-bit when handling CTL requests. The Control-M/EM database user password is exposed by the use of the ps -ef command when concurrent sqlplus sessions are activated on HP with Oracle. The randomness of user session tokens generated by the Control-M/EM server during client logon is inadequate. The Control/EM executable running on IBM-AIX platform attempts to set the datasize process limit from the application. In IBM-AIX this behaviour is deprecated and using these settings might cause unexpected behaviour. Before installing this fix pack the administrator must verify that the datasize limit is set to unlimited for the Control-M/EM account, either on.cshrc or /etc/security/limits. Control-M/EM API should accept leading zeros in the orderid parameter in all requests. After migrating Control-M/EM data from versions and to version , Viewpoints containing filters and collections for the Cyclic field of jobs, do not open. In these environments, users that also have active jobs view filter authorizations on cyclic jobs, cannot view these jobs anymore. The Control-M/EM API folder_info parameters are not supported in request_order_force when using schema

11 Release tes Tracking # Description Client installation required CAR CAR CAR CAR CAR CAR CAR The Control-M/EM API variable_assignment parameters are not supported in request_order_force when using schema 800. Control-M/EM with LDAP configuration has added support to LDAP nested groups. A user who logs into Control-M/EM with LDAP credentials does not need to be a direct member of one of the LDAP groups that are mapped to Control-M/EM. Control-M/EM now checks the descendants of the LDAP groups mapped to Control-M/EM. If the user is a member of one or more of the descendant groups, the user is authorized in Control-M/EM, and inherits the combined authorizations of all of the parental groups. Workload definitions cannot be migrated when you upgrade from Control-M/EM version to version if the default export mode is used. The migrate_dc process might fail when Control-M/EM is working with a Sybase Database and the old Control-M/Server data contains an invalid folder/job name. A Workspace check-in (sync stage) fails when the automatic sync is performed before the upload request is sent. Definition changes that are made using sweep, CLI, and updatedef might not be identified by the definition cache. If a folder was renamed (updatedef) the automatic sync cannot delete the old folder from Control-M/Server remotely. Periodically, you cannot see the Control-M/Server or the whole folder in the right pane of job properties until you perform the Rearrange option when you drag and drop a z/os job in a workspace. CAR The Timezone field is not updated in the Job Properties Window when navigating from job to job. 11

12 Release tes Tracking # Description Client installation required CAR CAR CAR CAR Inconsistent names are used in different areas of the Control-M Workload Automation application, (for example: Mem Name and Member Name, Lib and Library). The date and time appear incorrectly throughout Control-M Workload Automation instead of adhering to local computer settings. You cannot add periods to a Periodic Calendar when you select Based on Calendar in the Job Properties Scheduling tab. The Member Name and Member Library are not visible in the General section when you select a Command job type in the Job Properties pane. CAR When specifying a Control-M for zos job as non cyclic, the Maximum Rerun field in the Scheduling tab of the job properties pane accept values between instead of CAR CAR CAR The Cyclic fields "Must Start" and "Must End" appear in the "Synopsis of Job" even if the Job is not defined as Cyclic The tab title of a Viewpoint appears as All Jobs instead of the specific Viewpoint name in the Monitoring and History domains when Neighborhood View Point is open. A z/os job or folder accepts Latin1 characters in the fields of the job properties that do not support non-english characters in the Planning domain. CAR In the Monitoring domain, when holding a job from within the properties window itself, using the "Modify Job" button, and then making changes and saving them, the job is not set to free. 12

13 Release tes Tracking # Description Client installation required CAR The Save button is visible and enabled when you open a job that is not held by double-clicking it in the Monitoring domain. CAR The Order Date field is disabled and the "Elapsed Minutes" field is not visible when you hold a Control-M for z/os job and open its properties by double clicking on it in the Monitoring domain CAR CAR CAR CAR CAR In the Folders Manager section, when viewing a schedule of a SMART folder and a job with RBC, the Scheduling section is missing and not working as expected (As View scheduling under Analysis Tab). The following error message might appear when you open the View Schedule window for multiple folders and jobs: System.outOfMemoryException In the aftrermath of an EM client disconnection from the EM GUI, the list of Control-M/ Servers in the "Control-M Communications Status" window might not be refreshed automatically. Also, when the "Refresh" button is used, it might stick. The "Export" and "Print" options are disabled in the menu list of the Quantitative Resources and Control Resources windows. In the planning domain, changes are not saved in Control-M/Server and the GUI Server if only the order of Variables/Resources/Conditions is rearranged and no other changes are made. 13

14 Release tes Tracking # Description Client installation required CAR When using the "Upper Case" option for Control-M z/os, the Planning Domain does not check that z/os fields contain upper case characters only. CAR When the emdef defcal utility sends an existing calendar definition with a different year specification to the Control-M/ EM database, the entire definition is overwritten instead of simply adding the new year to the existing calendar definition. CAR CAR CAR CAR CAR When moving from map view to list view in the Planning Domain workspace, the selected parent node in the list view does not appear selected in the tree view. When updating auto edit variables in the "Find and Update" window of the Planning Domain, the same variables are also updated in the CM forms. When setting interval values in the "Find and Update" window of the Planning Domain, the right most character is truncated. The hotkeys shortcuts are missing in the "Map" and "List" views of the Planning Domain. Restored folders and jobs in the Planning Domain should be restored to a new workspace. CAR CAR When creating a SMART folder from a created template in the Planning Domain, the "Application" and "Sub-Application" fields are not saved in the template. and as a result are not present in the SMART folder. All columns that hold Boolean values (true/false) in the List view of the Planning Domain should be represented by a check box. 14

15 Release tes Tracking # Description Client installation required CAR CAR The most recently saved data of jobs and folders in the Planning Domain workspace are lost after closing and reopening the workspace.. When using the advanced Find option in the Planning Domain, SMART folders are not found even when they meet the search criteria. CAR Users with no authorizations can still access and edit Service properties in the "Services Definitions" window in the Planning Domain or in the Tools Domain. CAR CAR When trying to edit and restore a SMART folder from the "Versions Manager" window in the Planning Domain, the SMART folder is restored but the last changes are lost. The Planning Domain allows a user with only browse authorization to create jobs in a workspace and "save" and "check in" the workspace. When this happens, the application might hang. CAR When user loads a partial folder into a workspace in the Planning Domain, he shouldn t be able to drag and drop the folder or any items that belong to it. CAR CAR CAR When the user creates an illegal hierarchy (for example, a folder in the first level) in the View Point Manager of the Monitoring Domain, the application crashes. In the Planning Domain Properties window, when duplicating any existing condition with 'Delete condition after job ends' selected and renaming it, the Out-condition is removed. The Control-M/EM client might crash due to a large amount of incoming alerts that are received simultaneously. 15

16 Release tes Tracking # Description Client installation required CAR CAR CAR CAR CAR When a z/os SMART folder containing an RBC definition is loading into the Planning Domain, a validity error message is generated when clicking the "Validation" button. When the user opens the Properties window in the Planning Domain, changes to SMART folder Application and Sub Application fields are not updated to the new values in both the folder and its Jobs. In any application, the last state of a window (attached or detached) does not get saved. After reopening the window, the state is always "attached". The hiding of empty SMART folders In the Monitoring Domain is not available at the user level under tools->options. In the Monitoring Domain, z/os jobs cannot be restarted from a specific step. CAR In the config.xml file, only the values under the "Default scope" are used, even when new values are defined in other scopes (for example, GUI, GSR). CAR The projection is missing the red text that indicates the job estimated start time has passed. CAR Double-click does not work on all components in the Control-M/Configuration Manager (CCM). CAR The Bypass Select option becomes grayed out when more than one job is selected. CAR After the New Day procedure executes, jobs in SMART folders become orphaned and are displayed 16

17 Release tes Tracking # Description Client installation required outside their SMART folders. CAR CAR CAR When opening a z/os job using double click in the Planning Domain, and then setting the "Order on Months" tab in the "Scheduling" option to "ne", the new value is lost after saving and then reopening the job properties. In the Planning Domain and the Forecast Domain, the "View Schedule" option is missing from the context menu. When entities are located using the "Find" option In the Planning Domain, new entities that are created afterward may not be found. CAR CAR The Control-M Server column in the "Problematic jobs" tab of the Analysis Viewpoint in the Monitoring Domain is always empty. Folders in the Planning Domain remain "read only" even after all jobs are loaded. CAR CAR CAR Clicking the "Print" button in the "Validation Report" view of the Planning Domain, opens "Export to File" instead of "Print". The condition link between two scheduled entities in the Monitoring Domain doesn't become green when the source scheduling entity shows "ended OK". When Control-M Workload Automation is configured to work in SSL mode, non-ssl clients trying to connect cause memory leaks in the Naming Service. CAR Control-M now supports.net 4.5 framework. CAR When importing an XML draft that was originally created in Control-M version to the Planning Domain, the "Created On" field is empty for all jobs in the draft when viewing the job in Synopsis mode. 17

18 Release tes Tracking # Description Client installation required CAR CAR CAR CAR CAR CAR CAR CAR Variables are not displayed in Job properties when they are created from applications plug-ins. Control-M Workload Automation fails to execute for users that don't have administration privileges. When trying to change an embedded script by using "Script Editor" button on a checked out job in the Planning Domain, the subsequent check in fails. An error message is issued indicating that the job did not change. When using the Tools-Options-Advanced menu in Workload Automation to change the value of time between reconnections, the change is not reflected in the Workload Automation client. When recycling GUI server in the CCM,the default of 5 retries for "Max reconnection retries" and 5 seconds for "Seconds between attempts" is not sufficient for the recycle process to complete, The new defaults are 10 retries and 10 seconds. When using Find & Update in the Planning Workspace, if "Find" is used before "Update", the update takes 6 times longer to complete than expected. The Version manager filter may not return tables even when tables match all of the filter criteria. This happens when using regular expressions in one of the filter fields. Upload requests sent during execution of the New Day procedure fail and the synchronization message is empty. CAR The GUI server may crash if the user fails to log in using LDAP. 18

19 Release tes Tracking # Description Client installation required CAR CAR CAR CAR Control-M Net Report counts only the daily reruns of MVS jobs. The run count of single execution jobs for a given day and the first run count for jobs that ran more than once are omitted. When an asterisk is used as part of the filter specification in the Planning Domain "Load from EM" command, the specified Control-M/EM folders take a long time to load and may increase the amount of memory required. Control-M/EM lacks the ability to use short LDAP user login IDs to authenticate Control-M/EM users against LDAP. As a result, Control-M z/os authentications fail if the Control-M z/os security system uses short LDAP user login ID protocol for authorization and security. Memory leaks occur in the Control-M/EM API during requests and responses. CAR Control-M/EM users who are authenticated against LDAP are not able to log in if their default search privileges for the login directory are revoked. CAR CAR CAR In the Control-M/Configuration Manager (CCM), User authorization LDAP parameters cannot be defined for a user even when LDAP authorization is enabled. Reporting Facility and Report CLI - Managed Servers report may take a very long time to be generated in large Control-M environments Job execution reports generated by the Reporting Facility require a large amount of time in an Oracle database environment. CAR When a user tries to save a job as a template in the Planning Domain working in an environment that was installed by Web Launch, the operation fails and an error message is generated. 19

20 Release tes Tracking # Description Client installation required CAR CAR CAR An exception may occur when running the Control-M client via the command line and using multiple xml files. In the Planning Domain Start page, "Load folder and jobs" doesn't display jobs correctly after clicking refresh. The "Log" and "Statistics" tabs in Job properties of the Monitoring Domain do not have an option to export information to a file. CAR Changing the preset path from the "File -> Options" menu doesn't affect preset "load" or "save" specifications in the "Find And Update" window if they were checked previously. CAR CAR CAR CAR CAR CAR In the Planning Domain, when adding "tifications after job completion" in the "Actions" tab, if you chose the "TSO User" Destination option, you cannot specify a destination parameter beginning with "T-". ORB configuration does not show the "virtual publisher host" parameter if it is defined in the config.xml file together with "listen port range". When importing jobs with a user defined time zone in the Planning Domain, the Timezone field is cleared without any message being issued. Job synopsis and properties is missing run information place holders in the Monitoring Domain. When the user tries to login to a Workload Automation client from the command line and is unsuccessful, the login window is not displayed. A SMART-Fold hierarchy in the Planning Domain cannot contain Sub-Folders with the same name even when they are specified under separate hierarchical levels. 20

21 Release tes Tracking # Description Client installation required CAR When running the Export procedure during an upgrade to Control-M/EM version , if the exported data contains DO_FORCE_JOB entries, the Export script hangs and fails to complete. CAR The Upgrade validation procedure from Control-M/EM version to version does not allow the "/" character in the scheduling table name fields of the database. CAR CAR CAR When performing an upgrade to Control-M/EM version , importing to an Oracle database fails when the value of Control-M/EM system parameter "AuditHistoryDays" does not have a value of 1 (default) or 7 When LDAP is used with SSL encryption on Linux or Solaris, attempting to connect to the LDAP server may fail. Promote CTM fails if it encounters an invalid job or table name containing a 0 before the first illegal character (?*/ or space). CAR CAR The "Run in restart mode" and "Reset Job before run" checkboxes do not set job attributes correctly for DataStage jobs. The default checkbox values in the DataStage plug-in are not set when creating a new job. CAR Special characters (for example, é à ç ä ö ß ) are not supported when loading values in the Job Properties window for Application Plug-in jobs (for example, SAP, AFT, Databases). 21

22 Release tes Tracking # Description Client installation required CAR , CAR , CAR , CAR , CAR , CAR CAR CAR CAR CAR Incorrect information may be displayed in the job waiting info tab, for example, under the following circumstances: A job is waiting for a Control resource. Nested entities of jobs and sub folders awaiting Information may not include job ancestors. Jobs that have 'FROM TIME' and/or 'TO TIME' may not display correct messages. When the Control-M/Server component is older than version , and the synchronization mode is Update Control-M/Server Only, automatic synchronization may not always work. A Browse button is now offered for browsing and selecting scripts/binaries and doc files from the file system of the agent/remote host. To enable this feature, ensure that Control-M/Server, Control-M/Agent have fix pack , and INCONTROL version or above installed. In the planning domain, the Start day of the week is not displayed properly in the folder level RBC of a SMART folder. The Application Form field appears to be truncated at the? character in requests from Control-M Workload Automation when defining a job. 22

23 Release tes BMC Batch Impact Manager corrected problems The following table describes the problems that were reported in earlier releases of BMC Batch Impact Manager and have been corrected. The list of corrected problems is also available here in the Knowledge Base. Tracking # Description Client installation required CAR CAR CAR CAR A BIM service might change its status to "Will not Complete" if the service contains a SMART folder that includes a cyclic job that fails in one of the runs. The completed late time of a service appears incorrect in a history report in the Reporting Facility. BMC Batch Impact Manager might incorrectly estimate that a service will be late when there are jobs that have an ODATE that is before the ODATE of the Control-M/Server and also contains Time Zone and Time Window. These jobs do not have to be part of the service to cause the service to be late. BMC Batch Impact Manger might not respond for a long period of time, when there are many assumptions (Forecast/BIM Rules) and many jobs influenced by the assumptions. CAR The BIM server running on IBM-AIX platform attempts to set the datasize process limit from the application. In IBM-AIX this behaviour is deprecated and using these settings might cause unexpected behaviour. Before installing this fix pack the administrator must verify that the datasize limit is set to unlimited for the Control-M/EM account, either on.cshrc or /etc/security/limits. 23

24 Release tes Control-M/ Forecast corrected problems The following table describes the problems that were reported in earlier releases of Control-M/Forecast and have been corrected. The list of corrected problems is also available here in the Knowledge Base. Tracking # Description Client installation required CAR CAR CAR CAR Control-M/Forecast now supports the SCHED_NEGATIVE_SCOPE parameter of Control-M/Server.Jobs can be forecasted incorrectly on days defined with negative values (-n, -Dn, -Ln, DnPi, or -LnPi) in the scheduling rules. This problem might occur when the month days and weekday job attributes include complex rules that contain both negative and positive values, and SCHED_NEGATIVE_SCOPE is set to 0 in Control-M Server. The Control-M/Forecast CTL command "USERDAILY_ORDER" is available for showing and validating z/os user daily information automatically downloaded from CTM for z/os version 700 and higher. The Control/EM executable running on IBM-AIX platform attempts to set the datasize process limit from the application. In IBM-AIX this behaviour is deprecated and using these settings might cause unexpected behaviour. Before installing this fix pack the administrator must verify that the datasize limit is set to unlimited for the Control-M/EM account, either on.cshrc or /etc/security/limits. Memory leaks occur in the Control-M/Forecast server during reloading node group information 24

25 Chapter Release tes Control-M Self Service corrected problems The following table describes the problems that were reported in earlier releases of Control-M Self Service and have been corrected. The list of corrected problems is also available here in the Knowledge Base. Tracking # Description Client installation required CAR , CAR , CAR , CAR , CAR , CAR , CAR , CAR , CAR CAR CAR CAR CAR CAR CAR Incorrect information may be displayed in the job waiting info tab, for example, under the following circumstances: A job is waiting for a Control resource. Nested entities of jobs and sub folders awaiting Information may not include job ancestors. Jobs that have 'FROM TIME' and/or 'TO TIME' may not display correct messages. Some labels in SelfService (SLS) Language Preferences are not translated from English to a specified language (e.g. French, Spanish or German). The Job log in Self Service (SLS) is not updated for dummy jobs when the job status is "Ended Ok" The Control-M Self Service, Jobs View, General tab, now shows the execution time zone in the Additional Information section. Services related to Control-M Self Service display a time that is one hour off. An unhandled exception is issued when z/os jobs return an invalid date string. When viewing a Control-M Self Service job flow, conditions from one date are mixed with the job flow from another date. 25

26 Release tes Tracking # Description Client installation required CAR CAR CAR The Control/EM executable running on IBM-AIX platform attempts to set the datasize process limit from the application. In IBM-AIX this behaviour is deprecated and using these settings might cause unexpected behaviour. Before installing this fix pack the administrator must verify that the datasize limit is set to unlimited for the Control-M/EM account, either on.cshrc or /etc/security/limits. In some situations, SLS is not able to recognize the GUI server, making it impossible to log in to the SLS web. The History View does not work for Self Service items when jobs are in a SMART folder that is not part of the service. 26

27 Release tes Open issues and known problems The following table describes issues that remain open in this release: Tracking # Description CAR (Linux only) The Naming Service process might hang and reach high CPU usage due to a memory configuration. For a workaround, see

28 Chapter Release tes Control-M/EM Compatibility Control-M/EM can be installed on Windows and UNIX computers and works together with other products in the Control-M scheduling solution (for example, Control-M/Server and Control-M/Agent). The following lists the operating systems and other pre-installation requirements for Control-M/EM: Control-M/EM client compatibility with Windows (on page 29) Control-M/EM server compatibility with Windows (on page 30) Control-M/EM server compatibility with UNIX/Linux (on page 31) Control-M/EM compatibility with Control-M components (on page 32) Control-M/EM compatibility with third party software (on page 32) Control-M/EM integration with BMC products (on page 33) Control-M/EM language compatibility (on page 34) 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. 28

29 Release tes Control-M/EM client compatibility with Windows The following table lists the Windows operating systems that are compatible with Control-M/EM client. Operating System Bits Compatible Processors Windows XP Professional 32 Windows Vista Enterprise Edition 64 x86 x86_64 Windows Vista Business Edition Windows Vista Ultimate Edition Windows 7 Enterprise Edition Windows 7 Business Edition Windows 7 Professional Edition Windows 7 Ultimate Edition Windows 8 Enterprise Windows 8 Pro Windows 8 Windows Server 2008 Standard Edition Windows Server 2008 Enterprise Edition 29

30 Release tes Operating System Bits Compatible Processors Windows Server 2008 R2 Standard Edition 64 x86_64 Windows Server 2008 R2 Enterprise Edition Windows Server 2012 Standard Edition Control-M/EM server compatibility with Windows The following table lists the Windows operating systems that are compatible with Control-M/EM server. Operating System Bits Compatible Processors Database servers Windows Server 2008 Standard Edition x86 x86_64 Microsoft SQL Server 2005, 2008, 2008 R2, A BMC-supplied PostgreSQL server and client. Windows Server 2008 Enterprise Edition Windows Server 2008 R2 Standard Edition Windows Server 2008 R2 Enterprise Edition Windows Server 2012 Standard Edition 64 x86_64 Microsoft SQL Server 2005, 2008, 2008 R2, A BMC-supplied PostgreSQL server and client. 64 x86_64 Microsoft SQL Server 2008, 2008 R2, 2012 A BMC-supplied PostgreSQL server and client 30

31 Release tes Control-M/EM server compatibility with UNIX/Linux The following table lists the UNIX/Linux operating systems that are compatible with Control-M/EM server. Operating System Version Bits Compatible Processors Database server AIX Power An Oracle 11 database server (Update 9) HP-UX (Update 3) (B ) Itanium Sybase Adaptive Server Enterprise and later, using the ISO1 character set. A BMC-supplied PostgreSQL server and client. Oracle Solaris Red Hat Enterprise Linux Server SUSE Linux Enterprise Server (Update 7) 9 (Update 9) 6 5(Update 1) SPARC x86_64 Oracle Enterprise Linux Server 6 5 An Oracle 11 database server. A BMC-supplied PostgreSQL server and client. 31

32 Release tes Control-M/EM compatibility with Control-M components The following table lists the Control-M components that are compatible with Control-M/EM. Control-M Version Control-M/Server Control-M/Agent See Control-M/Server compatibility with Control-M components BMC Batch Discovery BMC Batch Impact Manager Control-M/Forecast Control-M Self Service Control-M for z/os 8.0 xx 7.0.xx 6.3.xx Control-M/EM version fix pack 1 is compatible with all supported versions of Application Plug-ins and options for application-specific products that were available before this release. Control-M/EM compatibility with third party software The following table lists third party software that is compatible with Control-M/EM. Third party software Version Internet Explorer Mozilla Firefox Google Chrome 3.6 and higher 4 and higher 32

33 Release tes Third party software Version Apple Safari and higher Web server Any web server that supports Java Servlet API 1.2..NET Framework (Full Profile) Microsoft Silverlight and higher Third Party notices, terms, and conditions pertaining to third party software can be found in the "ThirdParty" subdirectory of the Control-M installation. Control-M/EM integration with BMC products The following table lists BMC products that can integrate with Control-M/EM. BMC product Version BMC Remedy 7 BMC Service Impact Manager BMC Atrium CMDB

34 Release tes Control-M/EM language compatibility The following table lists the languages that are compatible with Control-M/EM. 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 34

35 Chapter Release tes Online help compatibility The following table lists the supported browsers for the Online help: Third party software Version Internet Explorer Mozilla Firefox Chrome

36 Chapter Release tes Product Distribution The following procedures describe how to obtain the installation files for Control-M/Enterprise Manager version fix pack 1, using EPD, FTP, or the BMC Sales Representative: Obtaining installation files through EPD (on page 36) Obtaining installation files using FTP Obtaining installation files through the BMC sales representative (on page 37) Obtaining installation files through EPD This procedure describes how to obtain the Control-M/Enterprise Manager 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. 36

37 Release tes Obtaining installation files using FTP This procedure describes how to obtain the Control-M/Enterprise Manager 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_Enterprise_Manager/8.0.00/PA NFT /Unix Windows:ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Enterprise_Manager/ /PANFT /Windows 2. Log in as a Control-M/EM user, and create a temporary directory (for example,temp_inst_dir). 3. Copy the required files, as follows: UNIX: Copy the PANFT _<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.iso or relevant.zip file 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/Enterprise Managerinstallation 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 37

38 Chapter Release tes Installation The installation files for Control-M/EM version fix pack 1 are available from the BMC FTP site, on the installation DVD, or through Electronic Product Distribution (EPD), as described in Product Distribution. The following procedures enable you to install and uninstall fix pack 1: Installing fix pack 1 on UNIX (on page 39) Installing fix pack 1 on Windows (on page 40) Uninstalling fix pack 1 from UNIX (on page 42) Uninstalling fix pack 1 from Windows (on page 43) These release notes provide procedures for installing fix pack 1 of Control-M/EM. To install the full Control-M Workload Automation solution, see the Control-M Installation Guide. To configure and deploy Web Launch packages to install this fix pack, see the Control-M Administrator Guide. Installation requirements The following table lists the disk space requirements for installing Control-M/EM fix pack 1: Operating system AIX HP-Itanium Oracle Solaris Red Hat SUSE Windows-32 bit Windows-64 bit Disk space requirements 900 MB 1200 MB 500 MB 350 MB 350 MB 1100 MB 1300 MB During the installation, additional space of the same sizes as in the previous table, is required in the temporary directory disk (%temp% Windows and /tmp on UNIX). 38

39 Release tes Installing fix pack 1 on UNIX This procedure describes how to install Control-M/EM version fix pack 1 on a UNIX computer. Before You Begin Ensure that you have met the following requirements: Korn Shell (KSH) is installed. Control-M/EM version is installed. Control-M/EM XML utilities are running. Ensure that the database server that contains the Control-M/EM database is up and running. To install fix pack 1 on UNIX: 1. Log in to a Control-M/EM client computer and in the Control-M Configuration Manager, shut down the following components: Gateway GUI Server GCS BIM Forecast Server Self Service Server (if applicable) 2. Log in to a Control-M/EM UNIX computer and shut down the Control-M/EM components, as follows: a. Type the following command: root_menu b. Type your Control-M/EM username and password. c. Press 1 - Activation Menu and then press the following commands: o o o Stop Control-M/EM Configuration Agent Stop Control-M Configuration Server Stop CORBA naming service 3. Shut down the Jetty Web Server by typing the following command (if applicable): stop_web_server 4. Do one of the following: If you obtained the installation files using FTP (see Obtaining installation files using FTP (on page 37)), navigate to the temporary directory that you created. If you obtained a DVD (using EPD or BMC Sales Representative), mount the installation DVD. 5. Install the fix pack with one of the following methods: To perform an interactive installation, type one of the following commands, and then press Y: 39

40 Release tes o o DVD: <DVD>/Unix/PANFT _<Operating_System>.setup.sh FTP: <temp_dir>/panft _<operating_system>.install_bin To perform a silent installation, type one of the following commands: o DVD: <DVD>/Unix/PANFT _<Operating_System>.setup.sh -s o FTP: <temp_dir>/panft _<operating_system>_install.bin -s NOTE: You can change the location of the directory where temporary installation files are extracted. You might want to do this when there is not enough space left in the temporary /tmp directory. EXAMPLE: <DVDmount>/Unix/PANFT _AIX_INSTALL.BIN -d <location> The <location> variable is the required location. 6. Log in to a Control-M/EM UNIX computer and start up the Control-M/EM components, as follows: a. Type the following command: root_menu b. Type your Control-M/EM username and password. c. Press 1 - Activation Menu and then press the following commands: o o o o Start Control-M/EM Configuration Agent Start Control-M Configuration Server Start CORBA naming service Start Control-M Web Server 7. Log in to a Control-M/EM client computer and in the Control-M Configuration Manager, start up the following components: Gateway GUI Server GCS BIM Forecast Server Self Service Server Installing fix pack 1 on Windows This procedure describes how to install Control-M/EM version fix pack 1 on a Windows computer. Before You Begin Ensure that you have met the following requirements: 40

41 Release tes Control-M/EM version is installed. Ensure that no Control-M/EM XML utilities are running. Ensure that the database server that contains the Control-M/EM database is up and running. To install fix pack 1 on Windows: 1. Log in as an administrator. 2. Close the following applications: Control-M Workload Automation Reporting Facility Conversion Tool 3. From the Control-M Configuration Manager, shut down the following components, and then exit the Control-M Configuration Manager: Gateway GUI Server GCS BIM Forecast Server Self Service Server (if applicable) 4. Shut down the following Control-M/EM services: Control-M/Enterprise Manager Configuration Agent Control-M Configuration Server Control-M Naming Service for EM Control-M Web Server (if applicable) NOTE: If the Control-M Web Server is running as a process, stop it by using Windows services. 5. Do one of the following: If you obtained the installation files using FTP (see Obtaining installation files using FTP (on page 37)), navigate to the temporary directory that you created. If you obtained a DVD (using EPD or BMC Sales Representative), insert the DVD, and then navigate to the Windows directory. 6. Install the fix pack using one of the following methods: To perform an interactive installation, double-click the <executablefile> file and continue with the installation wizard, following the on-screen instructions until the installation is complete. To perform a silent installation, open a command line and do the following: 7. Extract the fix pack files by typing the following command: <executablefile> -e 41

42 Release tes 8. Navigate to %temp%\panft and type the following command: silent.bat -i <eminstancename> NOTE: If you are using Windows 7, Windows Vista, or Windows Server 2008 operating systems, run the silent installation from a command prompt that was opened with administrator privileges. NOTE: 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%. 9. Start up the following Control-M/EM services: Control-M/Enterprise Manager Configuration Agent Control-M Configuration Server Control-M Naming Service for EM Control-M Web Server 10. From the Control-M Configuration Manager, start up the following components: Gateway GUI Server GCS BIM Forecast Server Self Service Server Uninstalling fix pack 1 from UNIX This procedure describes how to uninstall Control-M/EM version fix pack 1 from a UNIX computer. To uninstall fix pack 1 from UNIX: 1. Log into a Control-M/EM client computer and in the Control-M Configuration Manager, shut down the following components, and then exit the Control-M Configuration Manager: Gateway GUI Server GCS BIM Forecast Server Self Service Server 2. Log in to a Control-M/EM UNIX computer and shut down the Control-M/EM components, as follows: a. Type the following command: root_menu 42

43 Release tes b. Type your Control-M/EM username and password. c. Press 1 - Activation Menu and then press the following commands: o Stop Control-M/EM Configuration Agent o Stop Control-M Configuration Server o Stop CORBA naming service o Stop Control-M Web Server 3. Uninstall the fix pack using one of the following methods: To perform an interactive uninstall, type the following: $HOME/ctm_em /patches/remove_fp -f PANFT To perform a silent uninstall, type the following: $HOME/ctm_em /patches/remove_fp -f PANFT s Uninstalling fix pack 1 from Windows This procedure describes how to uninstall Control-M/EM fix pack 1 from a Windows computer. To uninstall fix pack 1 from Windows: 1. Log on as an administrator. 2. Close the following applications: Control-M Workload Automation Reporting Facility Conversion Tool 3. From the Control-M Configuration Manager, shut down the following components, and then exit the Control-M Configuration Manager: Gateway GUI Server GCS BIM Forecast Server Self Service Server (if applicable) 4. Shut down the following Control-M/EM services: Control-M/Enterprise Manager Configuration Agent Control-M Configuration Server Control-M Naming Service for EM Control-M Web Server (if applicable) 43