CTM EM 800_FP1_ReleaseNotes

www.bmc.com

Control-M/Enterprise Manager 8.0.00.100 Release Notes

April 2013

2

Contents Introduction to the Control-M/Enterprise Manager Release Notes ....................................... 4

Control-M/EM ................................................................................................................. 5

Control-M/EM enhancements .......................................................................................................... 5 Control-M Conversion Tool included with Control-M/Enterprise Manager 8.0.00.100 ........................... 9 Control-M/EM corrected problems ................................................................................................. 10

BMC Batch Impact Manager corrected problems ............................................................. 23

Control-M/ Forecast corrected problems ......................................................................... 24

Control-M Self Service corrected problems ...................................................................... 25

Open issues and known problems .................................................................................. 27

Control-M/EM Compatibility ........................................................................................... 28

Control-M/EM client compatibility with Windows ............................................................................. 29 Control-M/EM server compatibility with Windows ............................................................................ 30 Control-M/EM server compatibility with UNIX/Linux ........................................................................ 31 Control-M/EM compatibility with Control-M components .................................................................. 32 Control-M/EM compatibility with third party software ...................................................................... 32 Control-M/EM integration with BMC products ................................................................................. 33 Control-M/EM language compatibility ............................................................................................. 34 Online help compatibility ............................................................................................................... 35

Product Distribution ...................................................................................................... 36

Obtaining installation files through EPD ......................................................................................... 36 Obtaining installation files using FTP .............................................................................................. 37 Obtaining installation files through the BMC sales representative ..................................................... 37

Installation .................................................................................................................. 38

Installation requirements .............................................................................................................. 38 Installing fix pack 1 on UNIX ......................................................................................................... 39 Installing fix pack 1 on Windows ................................................................................................... 40 Uninstalling fix pack 1 from UNIX .................................................................................................. 42

3

Uninstalling fix pack 1 from Windows ............................................................................................ 43

Support for Control-M 8.0.00.100 .................................................................................. 45

Levels of support .......................................................................................................................... 45 Related documentation ................................................................................................................. 45

4

Release Notes

Introduction to the Control-M/Enterprise Manager Release Notes BMC Software is releasing version 8.0.00 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 https://kb.bmc.com/infocenter/index?page=content&id=KA390161.

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.

5

Release Notes

Chapter

Control-M/EM The following topics describe enhancements and corrected problems for Control-M/EM 8.0.00 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 8.0.00 fix pack 1:

Tracking # Description

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

QM001766312 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 8.0.01 or higher must be installed in the same IOA environment where Control-M for z/OS is installed.

Prerequisites: INCONTROL version 8.0.01.

6

Release Notes


CAR00046522 Name: Track Changes


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.

CAR00044701 Name: Remote Browsing


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 8.0.00 fix pack 1, Control-M/Agent version 8.0.00 fix pack 1, and INCONTROL version 8.0.01.


7

Release Notes


QM001769199 The following Plug-ins have been updated or added to Control-M version 8.0.00 interface standards: DataStage, Databases, SAP R3, SAP DA, SAP BW, and Tandem.

CAR00041978 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 8.0.00 fix pack 1 and Control-M/Agent version 8.0.00 fix pack 1.


8

Release Notes


WCTM003289 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 8.0.00 fix pack 1 and INCONTROL version 8.0.01.

NOTE: You cannot check-in a workspace with jobs that belong to a Control-M/Server version 8.0.00 fix pack 1 with Exclude RBC mode enabled, if you are using a Control-M Workload Automation client version 8.0.00.

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


CAR00043260 Name: Renaming a Control-M/Server component


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.


9

Release Notes


CAR00044244 Name: Control-M Batch Discovery


The BMC Control-M Batch Discovery utility now supports BMC Remedy Action Request System(ARS) 7.6.04.

Service impact data is output to csv files for use with BMC Atrium Integrator version 7.6.04.

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.

CAR00047302 Name: Run as Dummy


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


CAR00047143 Control-M/Enterprise Manager now supports Windows Server 2012.

CAR00047144 Control-M/Enterprise Manager now supports Windows 8.

Control-M Conversion Tool included with Control-M/Enterprise Manager 8.0.00.100 The Control-M Conversion Tool version 8.0.00.004 is installed automatically when you install Control-M/Enterprise Manager 8.0.00.100.

For more information, see the Control-M Conversion Tool version 8.0.00.004 Release Notes.

10

Release Notes

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 https://kb.bmc.com/infocenter/index?page=content&id=KA390163 in the Knowledge Base.

Tracking # Description Client installation required

CAR00043830 Memory utilization constantly increases on the GUI Server on Windows 64-bit when handling CTL requests.

No

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

No

CAR00046509 The randomness of user session tokens generated by the Control-M/EM server during client logon is inadequate.

No

CAR00047409

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.

No

CAR00046618 Control-M/EM API should accept leading zeros in the orderid parameter in all requests.

No

CAR00046717 After migrating Control-M/EM data from versions 6.3.01 and 6.4.01 to version 8.0.00, 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.

No

CAR00046775 The Control-M/EM API folder_info parameters are not supported in request_order_force when using schema 800.

No

11

Release Notes


CAR00046781 The Control-M/EM API variable_assignment parameters are not supported in request_order_force when using schema 800.

No

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

No

CAR00046616 Workload definitions cannot be migrated when you upgrade from Control-M/EM version 7.0.00 to version 8.0.00 if the default export mode is used.

No

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

No

CAR00046577 A Workspace check-in (sync stage) fails when the automatic sync is performed before the upload request is sent.

No

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

No

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

Yes

CAR00046454 The Timezone field is not updated in the Job Properties Window when navigating from job to job.

Yes

12

Release Notes


CAR00046852 Inconsistent names are used in different areas of the Control-M Workload Automation application, (for example: Mem Name and Member Name, Lib and Library).

Yes

CAR00046448 The date and time appear incorrectly throughout Control-M Workload Automation instead of adhering to local computer settings.

Yes

CAR00046456 You cannot add periods to a Periodic Calendar when you select Based on Calendar in the Job Properties Scheduling tab.

Yes

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

Yes

CAR00046463 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 0-9999 instead of 0-255.

Yes

CAR00046449 The Cyclic fields "Must Start" and "Must End" appear in the "Synopsis of Job" even if the Job is not defined as Cyclic

Yes

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

Yes

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

Yes

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

Yes

13

Release Notes


CAR00046531 The Save button is visible and enabled when you open a job that is not held by double-clicking it in the Monitoring domain.

Yes

CAR00046662 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

Yes

CAR00046693 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).

Yes

CAR00046667 The following error message might appear when you open the View Schedule window for multiple folders and jobs:

System.outOfMemoryException

Yes

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

Yes

CAR00046619 The "Export" and "Print" options are disabled in the menu list of the Quantitative Resources and Control Resources windows.

Yes

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

Yes

14

Release Notes


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

Yes

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

Yes

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

Yes

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

Yes

CAR00045035 When setting interval values in the "Find and Update" window of the Planning Domain, the right most character is truncated.

Yes

CAR00046508 The hotkeys shortcuts are missing in the "Map" and "List" views of the Planning Domain.

Yes

CAR00046236 Restored folders and jobs in the Planning Domain should be restored to a new workspace.

Yes

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

Yes

CAR00046453 All columns that hold Boolean values (true/false) in the List view of the Planning Domain should be represented by a check box.

Yes

15

Release Notes


CAR00046761 The most recently saved data of jobs and folders in the Planning Domain workspace are lost after closing and reopening the workspace..

Yes

CAR00046744 When using the advanced Find option in the Planning Domain, SMART folders are not found even when they meet the search criteria.

Yes

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

Yes

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

Yes

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

Yes

CAR00046735 When user loads a partial folder into a workspace in the Planning Domain, he shouldnt be able to drag and drop the folder or any items that belong to it.

Yes

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

Yes

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

Yes

CAR00046863 The Control-M/EM client might crash due to a large amount of incoming alerts that are received simultaneously.

Yes

16

Release Notes


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

Yes

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

Yes

CAR00046985 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".

Yes

CAR00046110 The hiding of empty SMART folders In the Monitoring Domain is not available at the user level under tools->options.

Yes

CAR00046738 In the Monitoring Domain, z/OS jobs cannot be restarted from a specific step.

Yes

CAR00047000 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).

Yes

CAR00046746 The projection is missing the red text that indicates the job estimated start time has passed.

Yes

CAR00046676 Double-click does not work on all components in the Control-M/Configuration Manager (CCM).

Yes

CAR00046011 The Bypass Select option becomes grayed out when more than one job is selected.

Yes

CAR00047073 After the New Day procedure executes, jobs in SMART folders become orphaned and are displayed

Yes

17

Release Notes


outside their SMART folders.

CAR00046915 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 "None", the new value is lost after saving and then reopening the job properties.

Yes

CAR00046734 In the Planning Domain and the Forecast Domain, the "View Schedule" option is missing from the context menu.

Yes

CAR00047043 When entities are located using the "Find" option In the Planning Domain, new entities that are created afterward may not be found.

Yes

CAR00046663 The Control-M Server column in the "Problematic jobs" tab of the Analysis Viewpoint in the Monitoring Domain is always empty.

Yes

CAR00046673 Folders in the Planning Domain remain "read only" even after all jobs are loaded.

Yes

CAR00046921 Clicking the "Print" button in the "Validation Report" view of the Planning Domain, opens "Export to File" instead of "Print".

Yes

CAR00047162 The condition link between two scheduled entities in the Monitoring Domain doesn't become green when the source scheduling entity shows "ended OK".

Yes

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

Yes

CAR00047160 Control-M now supports .NET 4.5 framework. Yes

CAR00047165 When importing an XML draft that was originally created in Control-M version 7.0.00 to the Planning Domain, the "Created On" field is empty for all jobs in the draft when viewing the job in Synopsis mode.

Yes

18

Release Notes


CAR00047168 Variables are not displayed in Job properties when they are created from applications plug-ins.

Yes

CAR00047173 Control-M Workload Automation fails to execute for users that don't have administration privileges.

Yes

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

Yes

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

Yes

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

Yes

CAR00047201 When using Find & Update in the Planning Workspace, if "Find" is used before "Update", the update takes 6 times longer to complete than expected.

Yes

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

No

CAR00046896 Upload requests sent during execution of the New Day procedure fail and the synchronization message is empty.

No

CAR00046860 The GUI server may crash if the user fails to log in using LDAP.

No

19

Release Notes


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

No

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

No

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

No

CAR00045645 Memory leaks occur in the Control-M/EM API during requests and responses.

No

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

No

CAR00047191 In the Control-M/Configuration Manager (CCM), User authorization LDAP parameters cannot be defined for a user even when LDAP authorization is enabled.

Yes

CAR00045313 Reporting Facility and Report CLI - Managed Servers report may take a very long time to be generated in large Control-M environments

Yes

CAR00045814 Job execution reports generated by the Reporting Facility require a large amount of time in an Oracle database environment.

Yes

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

Yes

20

Release Notes


CAR00047221 An exception may occur when running the Control-M client via the command line and using multiple xml files.

Yes

CAR00047213 In the Planning Domain Start page, "Load folder and jobs" doesn't display jobs correctly after clicking refresh.

Yes

CAR00047135 The "Log" and "Statistics" tabs in Job properties of the Monitoring Domain do not have an option to export information to a file.

Yes

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

Yes

CAR00047084 In the Planning Domain, when adding "Notifications after job completion" in the "Actions" tab, if you chose the "TSO User" Destination option, you cannot specify a destination parameter beginning with "T-".

Yes

CAR00045008 ORB configuration does not show the "virtual publisher host" parameter if it is defined in the config.xml file together with "listen port range".

Yes

CAR00047239 When importing jobs with a user defined time zone in the Planning Domain, the Timezone field is cleared without any message being issued.

Yes

CAR00047237 Job synopsis and properties is missing run information place holders in the Monitoring Domain.

Yes

CAR00047245 When the user tries to login to a Workload Automation client from the command line and is unsuccessful, the login window is not displayed.

Yes

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

Yes

21

Release Notes


CAR00047295 When running the Export procedure during an upgrade to Control-M/EM version 8.0.00, if the exported data contains DO_FORCE_JOB entries, the Export script hangs and fails to complete.

No

CAR00047296 The Upgrade validation procedure from Control-M/EM version 7.0.00 to version 8.0.00 does not allow the "/" character in the scheduling table name fields of the database.

No

CAR00047316 When performing an upgrade to Control-M/EM version 8.0.00, 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

No

CAR00047410 When LDAP is used with SSL encryption on Linux or Solaris, attempting to connect to the LDAP server may fail.

No

CAR00047424 Promote CTM fails if it encounters an invalid job or table name containing a 0 before the first illegal character (?*/ or space).

No

CAR00047299 The "Run in restart mode" and "Reset Job before run" checkboxes do not set job attributes correctly for DataStage jobs.

Yes

CAR00047465 The default checkbox values in the DataStage plug-in are not set when creating a new job.

Yes

CAR00047487 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).

Yes

22

Release Notes


CAR00046764, CAR00046765, CAR00046763, CAR00046766, CAR00042718, CAR00046670

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.

No

CAR00047572 When the Control-M/Server component is older than version 8.0.00, and the synchronization mode is Update Control-M/Server Only, automatic synchronization may not always work.

No

CAR00044701 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 8.0.00.100, and INCONTROL version 8.0.01 or above installed.

No

CAR00047293 In the planning domain, the Start day of the week is not displayed properly in the folder level RBC of a SMART folder.

No

CAR00047604 The Application Form field appears to be truncated at the ? character in requests from Control-M Workload Automation when defining a job.

Yes

23

Release Notes

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 https://kb.bmc.com/infocenter/index?page=content&id=KA390169 in the Knowledge Base.


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

No

CAR00046519 The completed late time of a service appears incorrect in a history report in the Reporting Facility.

No

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

No

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

No

CAR00047406 The BIM server running on IBM-AIX platform attempts to set the datasize process limit from the application.



No

24

Release Notes

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 https://kb.bmc.com/infocenter/index?page=content&id=KA390170 in the Knowledge Base.


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

No

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

No

CAR00047409




No

CAR00047226 Memory leaks occur in the Control-M/Forecast server during reloading node group information

No

25

Release Notes

Chapter

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 https://kb.bmc.com/infocenter/index?page=content&id=KA390167 in the Knowledge Base.


CAR00046687, CAR00046688 , CAR00046711, CAR00046778, CAR00046876, CAR00046875, CAR00046878, CAR00046877, CAR00046874

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.

No

CAR00046620 Some labels in SelfService (SLS) Language Preferences are not translated from English to a specified language (e.g. French, Spanish or German).

No

CAR00045881 The Job log in Self Service (SLS) is not updated for dummy jobs when the job status is "Ended Ok"

No

CAR00045185 The Control-M Self Service, Jobs View, General tab, now shows the execution time zone in the Additional Information section.

Yes

CAR00045573 Services related to Control-M Self Service display a time that is one hour off.

Yes

CAR00045589 An unhandled exception is issued when z/OS jobs return an invalid date string.

Yes

CAR00045580 When viewing a Control-M Self Service job flow, conditions from one date are mixed with the job flow from another date.

Yes

26

Release Notes


CAR00047409




No

CAR00045123 In some situations, SLS is not able to recognize the GUI server, making it impossible to log in to the SLS web.

Yes

CAR00045582 The History View does not work for Self Service items when jobs are in a SMART folder that is not part of the service.

No

27

Release Notes

Open issues and known problems The following table describes issues that remain open in this release:


CAR00047819 (Linux only) The Naming Service process might hang and reach high CPU usage due to a memory configuration.

For a workaround, see https://kb.bmc.com/infocenter/index?page=content&id=KA394432.

28

Release Notes

Chapter

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 8.0.00, 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 KA390545 in the Knowledge base.

29

Release Notes

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 64

x86 x86_64 Windows Vista Enterprise

Edition

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

30

Release Notes

Operating System Bits Compatible Processors

Windows Server 2008 R2 Standard Edition

64 x86_64

Windows Server 2008 R2 Enterprise 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


32 64

x86 x86_64

Microsoft SQL Server 2005, 2008, 2008 R2, 2012.

A BMC-supplied PostgreSQL 9.0.4 server and client.

Windows Server 2008 Enterprise Edition

Windows Server 2008 R2 Standard Edition

64 x86_64 Microsoft SQL Server 2005, 2008, 2008 R2, 2012.


Windows Server 2008 R2 Enterprise Edition


64 x86_64 Microsoft SQL Server 2008, 2008 R2, 2012

A BMC-supplied PostgreSQL 9.0.4 server and client

31

Release Notes

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 7.1 6.1 5.3

(Update 9)

64

Power An Oracle 11 database server. Sybase Adaptive Server

Enterprise15.0.2 and later, using the ISO1 character set.


HP-UX 11.31 (Update 3)

11.23 (B.11.23.0806)

Itanium

Oracle Solaris

11 10

(Update 7)

9 (Update 9)

SPARC

Red Hat Enterprise Linux Server

6 5(Update

1)

x86_64

SUSE Linux Enterprise Server

11 10

Oracle Enterprise Linux Server

6 5

An Oracle 11 database server. A BMC-supplied PostgreSQL

8.3.7 server and client.

32

Release Notes

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 8.0.00 7.0.00 6.4.01 6.3.01

Control-M/Agent See Control-M/Server compatibility with Control-M components

BMC Batch Discovery 8.0.00

BMC Batch Impact Manager 8.0.00

Control-M/Forecast 8.0.00

Control-M Self Service 8.0.00

Control-M for z/OS 8.0 xx 7.0.xx 6.3.xx

Control-M/EM version 8.0.00 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 9 8 7

Mozilla Firefox 3.6 and higher

Google Chrome 4 and higher

33

Release Notes


Apple Safari 4.0.4 and higher

Web server Any web server that supports Java Servlet API 1.2.

.NET Framework

(Full Profile)

4.0

Microsoft Silverlight 4.0.50826.0 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 7.3 7.1

BMC Atrium CMDB 2.0

34

Release Notes

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) The following languages are now supported:

Traditional Chinese Simplified Chinese Japanese Korean

Western European (Latin-1 character set)

Special Western European characters used in English, Spanish, German, and French can be specified in most free-text fields and parameters.

Basic ASCII US English

35

Release Notes

Chapter

Online help compatibility The following table lists the supported browsers for the Online help:


Internet Explorer 9 8 7

Mozilla Firefox 4.0 3.6 3.5

Chrome 21.0.1180.75

36

Release Notes

Chapter

Product Distribution The following procedures describe how to obtain the installation files for Control-M/Enterprise Manager version 8.0.00 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 https://webapps.bmc.com/epd/ https://webapps.bmc.com/epd 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 : If you downloaded it to your computer, transfer it to a UNIX computer using binary ftp mode to an intermediate location:

b. CD into:

c. Extract the compressed tar file with the following command:

uncompress c / | tar xf For example : uncompress c /tmp/DROST.8.0.00_Linux-x86_64.tar | tar xf If you have do not have an uncompress command, use zcat instead of uncompress c:

zcat / | tar xf Windows: Do one of the following:

o Download and save the .iso file to a temporary directory, and then burn it onto a DVD. o Download and save the relevant .zip file to a temporary directory.

37

Release Notes

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/PANFT.8.0.00.100/Unix

Windows:ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Enterprise_Manager/8.0.00/PANFT.8.0.00.100/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.8.0.00.100__INSTALL.BIN file that is relevant to your UNIX system or PANFT.8.0.00.100.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

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 http://www.bmc.com/corporate/contacts-locations/

38

Release Notes

Chapter

Installation The installation files for Control-M/EM version 8.0.00 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 8.0.00 fix pack 1:

Operating system Disk space requirements

AIX 900 MB

HP-Itanium 1200 MB

Oracle Solaris 500 MB

Red Hat 350 MB

SUSE 350 MB

Windows-32 bit 1100 MB

Windows-64 bit 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).

39

Release Notes

Installing fix pack 1 on UNIX This procedure describes how to install Control-M/EM version 8.0.00 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 8.0.00 is installed. 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 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 Stop Control-M/EM Configuration Agent o Stop Control-M Configuration Server o Stop CORBA naming service

3. Shut down the Jetty Web Server by typing the following command (if applicable):

stop_web_server


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:

40

Release Notes

o DVD: /Unix/PANFT.8.0.00.100_.setup.sh o FTP: /PANFT.8.0.00.100_.INSTALL_BIN

To perform a silent installation, type one of the following commands:

o DVD: /Unix/PANFT.8.0.00.100_.setup.sh -s o FTP: /PANFT.8.0.00.100__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: /Unix/PANFT.8.0.00.100_AIX_INSTALL.BIN -d

The 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:


root_menu



o Start Control-M/EM Configuration Agent o Start Control-M Configuration Server o Start CORBA naming service o 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 8.0.00 fix pack 1 on a Windows computer.

Before You Begin Ensure that you have met the following requirements:

41

Release Notes

Control-M/EM version 8.0.00 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


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.


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 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:

-e

42

Release Notes

8. Navigate to %temp%\PANFT.8.0.00.100 and type the following command:

silent.bat -i

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 to extract the files to another directory. Ensure that there is no space between -d and . Otherwise, the fix pack files are extracted to the default location: %temp%.

9. Start up the following Control-M/EM services:




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 8.0.00 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:


root_menu

43

Release Notes



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

To perform a silent uninstall, type the following:

$HOME/ctm_em /patches/remove_fp -f PANFT.8.0.00.100 -s

Uninstalling fix pack 1 from Windows This procedure describes how to uninstall Control-M/EM 8.0.00 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


4. Shut down the following Control-M/EM services:




Control-M Web Server (if applicable)

44

Release Notes

5. Uninstall the fix pack by using one of the following methods:

To perform an interactive uninstall, do the following:

6. From the Start menu, select Control Panel > Add/Remove Programs > Control-M/Enterprise Manager 8.0.00fix pack 1 .

7. Select Remove.

To perform a silent uninstall, do the following:

8. Navigate to the following directory:

\install\PANFT.8.0.00.100\

9. From a command line, type the following command:

uninstallSilent.bat

NOTE: If you are using either Windows 7, Windows Vista, or Windows Server 2008 operating systems, run the silent uninstall from a command prompt that was opened with administrator privileges.

45

Release Notes

Support for Control-M 8.0.00.100 These topics provide information about the following:

Levels of support (on page 45) Related documentation (on page 45)

Levels of support For more information about the latest support policies and guidelines, see the Customer Support page of the BMC website at http://www.bmc.com/support.

Related documentation To view the latest BMC documents, including documents in other languages, see the Customer Support website at http://www.bmc.com/support.

Notices, such as flashes, technical bulletins, and release notes, are available on the website.

You can subscribe to proactive alerts to receive e-mail messages when notices are issued or updated. For more information about proactive alerts, see the Customer Support website.

46

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 77042-2827, USA 713 918 8800 Customer Support: 800 537 1813 (United States and Canada) or contact your local support center.

Introduction to the Control-M/Enterprise Manager Release NotesControl-M/EMControl-M/EM enhancementsControl-M Conversion Tool included with Control-M/Enterprise Manager 8.0.00.100Control-M/EM corrected problems

BMC Batch Impact Manager corrected problemsControl-M/ Forecast corrected problemsControl-M Self Service corrected problemsOpen issues and known problemsControl-M/EM CompatibilityControl-M/EM client compatibility with WindowsControl-M/EM server compatibility with WindowsControl-M/EM server compatibility with UNIX/LinuxControl-M/EM compatibility with Control-M componentsControl-M/EM compatibility with third party softwareControl-M/EM integration with BMC productsControl-M/EM language compatibilityOnline help compatibility

Product DistributionObtaining installation files through EPDObtaining installation files using FTPObtaining installation files through the BMC sales representative

InstallationInstallation requirementsInstalling fix pack 1 on UNIXInstalling fix pack 1 on WindowsUninstalling fix pack 1 from UNIXUninstalling fix pack 1 from Windows

Support for Control-M 8.0.00.100Levels of supportRelated documentation

CTM EM 800_FP1_ReleaseNotes

Documents

Transcript of CTM EM 800_FP1_ReleaseNotes