IBM Control Center Release Notes 6.0.0.2

Content

Release Notes contain last-minute changes and other important product information. Read this document before installing and upgrading to IBM® Control Center.

This document describes the V6.0.0.2 release.

System requirements

System requirements changed significantly after Sterling Control Center version 5.3. If you are upgrading from version 5.3 or prior, use the system estimation tools in Determining engine and database requirements prior to upgrading. For information about configuring databases for use by IBM® Control Center, see Overview of IBM Control Center databases. For more information about hardware and software compatibility for IBM® Control Center, see Detailed system requirements.

Important: Support for the HP-UX platform has been removed from IBM Control Center V6.0.

Some IBM® Control Center functionality applies only to specific server types. See Functionality by server type in this document.

See Determining engine and database requirements for information about determining configurations for the IBM® Control Center engine.


Required operating system patches

IBM Control Center uses the IBM Cognos® Business Intelligence server V10.2.2.8 as the reporting engine. Install required operating system patches for the Cognos Business Intelligence server before you install IBM Control Center. Required patches can be found at Cognos Business Intelligence 10.2.2 Supported Software Environments.

Important: Go to the Cognos Business Intelligence server web site for required libraries. In addition to those listed, the following libraries are also required in a Linux® environment: libstdc++.so.6, libX11.so.6, libXau.so.6, and libXdmcp.so.6. Contact your Linux system administrator for more information.

Mobile Application

IBM® Sterling Control Center Mobile 1.1 was removed from the Apple App Store on 08/12/2015 and is no longer available for download. If you already have a copy of the mobile application, you can continue to use it with IBM® Control Center V6.0 and earlier. To submit a request for a mobile app with specific features or on a specific platform, please enter a Request for Enhancement.

APAR fixes

For information about fixes for IBM® Control Center, see Fix Central.


Contacting IBM Software Support

If you encounter a problem with this product that cannot be resolved using the information outlined in the documentation, contact IBM® Software Support. See Contacting IBM Software Support.


Migrate data from MySQL databases

IBM® Control Center V6.0 and later does not support MySQL as a database type. You must migrate your MySQL database to one of the databases supported by IBM® Control Center: DB2, Oracle, SQL Server 2008, or SQL Server 2012. See Migrating data from MySQL databases.


Migrate existing EVENTS data to Sterling B2B Integrator tables

During the upgrade process for Sterling Control Center releases prior to V5.4.2, IBM® Control Center creates tables to capture Sterling B2B Integrator activity. If you have data that was collected from Sterling B2B Integrator prior to upgrading to IBM® Control Center V6.0.0.2 and you are upgrading from a Sterling Control Center release prior to V5.4.2, run the convertB2BData utility to migrate your existing data to the Sterling B2B Integrator tables. This utility migrates data previously stored in the EVENTS table to where it is stored now in the following tables: Sterling File Gateway activity (FG_STATS_LOG), protocol activity (AF_STATS_LOG), and business process activity (BP_STATS_LOG).

Important: Run the migration utility after you upgrade IBM® Control Center, while the engine is stopped. Do not run Sterling B2B Integrator or Sterling File Gateway reports for data that was collected before the upgrade until you have migrated your data. Depending on the volume of your data, the migration utility can take several hours to complete the migration process. It is recommended that you run the migration utility on a test or development environment before you run it with production data. See Migrating EVENTS table data to Sterling B2B Integrator activity tables.


General considerations

IBM® Control Center has the following general considerations:

• The typical time to install and configure IBM® Control Center V6.0.0.2 is one hour or less.
• IBM® Control Center can run in a virtual machine environment provided that enough resources (memory, processing power, and storage) are allocated to the virtual machine.
• If the console loses connectivity to the engine, it attempts to reconnect to the engine every 30 seconds until it reconnects or until you exit the console.
• If you are upgrading the engine and have not stopped and restarted the browser, or refreshed the browser, confirm that the IBM® Control Center engine is included in the browser list of trusted sites.
• When you are configuring IBM® Control Center by using the configCC utility, if you answer Yes to support globalization on your database, your database size can increase significantly.
• The version of Sterling Connect:Direct Browser User Interface that is embedded within Sterling Control Center uses the same keystore and truststore files as Sterling Control Center. If you want to use a different keystore and truststore file, use the stand-alone version of Sterling Connect:Direct Browser User Interface.

Tuning the engine for data visibility groups

When you use data visibility groups (DVGs), the IBM® Control Center engine keeps separate active alerts, handled alerts, and completed processes caches for each DVG that is defined. To optimize overall engine performance for DVG usage, consider tuning the engine. See Tuning the engine for data visibility groups.


Known limitations

IBM® Control Center has the following limitations:

• IBM Control Center 6.0.0.2 does not support validating the Init Parm options that are introduced with IBM Sterling Connect Direct V5.3.
• In Internet Explorer 10, the frame line does not display correctly in the Active Alerts, Current Activity, Environmental Health, and Quality Scorecard widgets when you are saving or printing a snapshot. To correct this issue:

1. From the Tools menu, click Internet Options.

2. Click Reset to reset the Internet Explorer settings.

3. Click the Advanced tab.

4. In the Settings list, in Advanced Graphics settings, select the Use software rendering instead of GPU rendering check box.

• Before you install or upgrade IBM® Control Center, you must activate the Workload Manager (WLM) policy when you are creating DB2® databases on the z/OS® operating system. If you do not activate the WLM policy for DB2 z/OS, you can get a SQL Execution error when you run the configCC utility.
• IBM® Control Center cannot monitor Sterling B2B Integrator servers using IPv6. You must specify an IPv4 address or a DNS name for the connection.
• The context-sensitive Help in the IBM® Control Center console provides definitions for new fields added with this release. However, some console fields do not have context-sensitive Help. To access the complete product documentation, click the console Help button, which goes to IBM Control Center in IBM Knowledge Center.
• For a web console session, if you change the sort options by clicking the column headers, sorting is not persisted if you leave that page by going to another page and then returning. To resolve this issue, click the column header to re-sort.
• When you access the web console, you might notice that portions of the UI are not visible in high contrast mode, to avoid this issue, do not use high contrast mode.
• In viewing the Completed Files Transfers list, the wheel on the mouse does not scroll the list in the locked column areas. To resolve this issue, move the mouse to the right side (unlocked column area) and use the mouse wheel to scroll the list.
• When you update an email address in the configCC utility, the system wide administrator email address is not updated automatically. To resolve this issue, use the IBM® Control Center console or web console to access the existing actions that are configured for email notification and manually change the email address.
• When you click Monitor > Completed Processes and press Ctrl + - and Ctrl + + to change the resolution ratio, sometimes some columns may not display the alignment after you change the ratio multiple times. You can resolve this issue by either reverting back to the original resolution, manually resizing the column width, or clicking the refresh button.
• Daylight Saving Time rules for Brazil are not correct for 2009 and beyond. The fix for SR 1367170 addresses this problem by allowing the user to add or update time zone definitions. See Changing engine settings after installation for help configuring time zone definitions.
• At peak volume, the number of events processed per second may decrease, which can be caused by an additional database operation during event processing.
• IBM® Sterling Connect:Direct for UNIX V4.2.0.2 has configuration parameters not supported by IBM® Control Center V6.0.0.2.
• The following issues are caused by Gridx limitations:
• When you select Monitor > Completed Processes and refresh the page, the following message displays: "No items to display.” This message may display when the data is being loaded from the server side.
• When you click Monitor > Completed Processes (Active Alerts/ Handled Alerts/ Queued Processes) and change the resolution ratio from 1024 x 768 to a higher one, a grey box may display in the left corner of your screen.
• On the Solaris platform, the following message can appear when you run configCC.sh, runEngine.sh, exportConfig, runDataCollector, stopEngine, setUserKey, or any script that starts a Java process:
  
  Java HotSpot (TM) Server VM warning: PICL (libpicl.so.1) is missing. Performance will not be optimal.
  
  IBM Control Center performance is not degraded, however JIT Complier optimizations cannot be used. For more information about this message, visit the VM warning: PICL (libpicl.so.1) is missing page on the Oracle website.

Known limitations for Cognos

• The Report Studio feature of Cognos Business Intelligence V10.2.2.8 that is integrated with IBM® Control Center V6.0.0.2 does not work with Internet Explorer 9 with HTTPS. You can run reports and see the output in the Cognos Viewer, but you cannot open the report in Report Studio. This limitation is due to a bug in Cognos Business Intelligence V10.2.2.8. Report Studio in IBM® Control Center V6.0.0.2 does work with FireFox HTTP, FireFox HTTPS, and Internet Explorer 10 and 11.
• If you open a Cognos report in the Excel 2002 format by using a later version of Excel, you can get a warning that the file format does not match the file extension. When asked if you still want to open the file, click Yes to continue viewing your report. The document is not impacted by the warning.
• While viewing or downloading a Cognos report, if you select View in Excel Options > View in CSV Format, the file that is downloaded shows an .xls extension instead of .csv.
  See Modify Properties for the CSV Output Format for information that explains how to change the CSV properties.
• Issue: When you are running Cognos configured with DB2 10.5 in Oracle compatibility mode, you might receive the following error:
  
  CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.
  CM-CFG-5114 An error occurred while locking the content store database. Cause: Assignment of a NULL value to a NOT NULL column "TBSPACEID=4, TABLEID=5, COLNO=0" is not allowed.. SQLCODE=-407, SQLSTATE=23502, DRIVER=3.69.24  Stack trace: com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: Assignment of a NULL value to a NOT NULL column "TBSPACEID=4, TABLEID=5, COLNO=0" is not allowed.. SQLCODE=-407, SQLSTATE=23502, DRIVER=3.69.24
       at com.ibm.db2.jcc.am.gd.a(Unknown Source)
       at com.ibm.db2.jcc.am.gd.a(Unknown Source)
       at com.ibm.db2.jcc.am.gd.a(Unknown Source)
       at com.ibm.db2.jcc.am.yo.b(Unknown Source)
       at com.ibm.db2.jcc.am.yo.c(Unknown Source)
       at com.ibm.db2.jcc.t4.bb.l(Unknown Source) 
      at com.ibm.db2.jcc.t4.bb.a(Unknown Source)
      at com.ibm.db2.jcc.t4.p.a(Unknown Source) 
      at com.ibm.db2.jcc.t4.wb.b(Unknown Source)
      at com.ibm.db2.jcc.am.zo.qc(Unknown Source) 
      at com.ibm.db2.jcc.am.zo.b(Unknown Source) 
      at com.ibm.db2.jcc.am.zo.ic(Unknown Source) 
      at com.ibm.db2.jcc.am.zo.executeUpdate(Unknown Source) 
      at com.cognos.cm.dbstore.CMPreparedStatementBase.executeUpdate(CMPreparedStatementBase.java:264) 
      at com.cognos.cm.dbstore.StatementProxy.executeUpdate(StatementProxy.java:321) 
      at com.cognos.cm.dbstore.CMDbConnection.executeUpdate(CMDbConnection.java:585)
      at com.cognos.cm.dbstore.CMDbStoreMultipleCMsUtil.checkCMLockConsistency(CMDbStoreMultipleCMsUtil.java:1027)
      at com.cognos.cm.dbstore.CMDbStoreFactory.initContentIndependentBeforeLock(CMDbStoreFactory.java:2021)
       at com.cognos.cm.dbstore.CMDbStore.initializeContentIndependentBeforeLock(CMDbStore.java:4370)
       at com.cognos.cm.server.CMServlet.initializeContentStoreContentIndependentBeforeLock(CMServlet.java:2122) 
      at com.cognos.cm.server.CMServlet.init(CMServlet.java:1881)
      at com.cognos.cm.server.ContentManager.start(ContentManager.java:436) 
      at com.cognos.cm.server.ContentManagerLifecycleHandler.start(ContentManagerLifecycleHandler.java:65)
      at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:88) 
      at com.cognos.pogo.services.DispatcherServices.startInitialService(DispatcherServices.java:418)
  at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:404)
       at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:803)
       at com.cognos.pogo.util.threads.SafeThread.safeRun(SafeThread.java:70) 
       at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.jav 
  
  Resolution:
  1. To check whether DB2 is running in Oracle compatibility mode, enter the following command: db2set -all.
  If you see the registry variable DB2_COMPATIBILITY_VECTOR=ORA, then DB2 is running in Oracle compatibility mode.
  
  2. If DB2 is running in Oracle compatibility mode, then stop the IBM Control Center engine.
  
  3. Disable DB2 from running in Oracle compatibility mode by entering the following command:
  db2set DB2_COMPATIBILITY_VECTOR= . Press Enter.
  
  4. Verify that DB2 is not running in Oracle compatibility mode by entering the following command: db2set -all.
  If you do not see the registry variable DB2_COMPATIBILITY_VECTOR=ORA, then Oracle compatibility mode is successfully disabled.
  
  5. To restart DB2, enter the following command: db2stop force.

6. Then, enter the following command: db2start.

7. Start the IBM Control Center engine.

Upgrading from V5.4.1 iFix2 or V5.4.2.1 iFix3 to V6.0.0.2 on DB2 z/OS

If you are using Cognos workspace in the web console, you must complete the installation steps before and after you upgrade from V5.4.1 iFix2 or V5.4.2.1 iFix3 to V6.0.0.2. If you do not complete these steps during the upgrade process, the Cognos workspace might not start.

1. Complete the following steps before the installation:
a. Stop the IBM Control Center engine
b. Run NC_DROP_DB2.sql in Cognos/schemas/delivery/zosdb2 of the installation directory.
c. Run dropTablespace_db2zOS.sql in Cognos/schemas/content/zosdb2 of the installation
directory.

2. Complete the following steps after the installation:

a. Run configCC.
b. Run tablespace_db2zOS.sql in Cognos/schemas/content/zosdb2 of the installation directory.
c. Run NC_CREATE_DB2.sql in Cognos/schemas/delivery/zosdb2 of the installation directory.
d. Start the IBM Control Center engine.

After you complete these steps, the Cognos workspace loads. If you upgrade and Cognos workspace does not start, see Troubleshooting the workspace.

IBM Cognos cannot run reports on DB2 or Oracle.

A network failure might cause this issue. Restart your IBM Control Center engine so IBM Cognos can reconnect to DB2 or Oracle. There are log messages in Cognos\logs\pogo.log that provide more information about the issue.

The following log messages indicate a successful connection:

<<Date & Time Info>> INFO [core.ehcache.pogo.EhCacheDispatcherHandler] Timer-24: Registered mbean: com.cognos.pdc:type=pdcMbean

<<Date & Time Info>> INFO [core.ehcache.pogo.EhCacheDispatcherHandler] Timer-24: CacheManager 'PDC' STATUS_ALIVE

<<Date & Time Info>> INFO [core.ehcache.pogo.EhCacheDispatcherHandler] Timer-24: Cache: 'CAM_Grid.PassportMap' size=0, status=STATUS_ALIVE

The following are error messages that you might receive in the log:

<<Date & Time Info>> ERROR [om.cognos.pogo.reportservice.ProcessFacade] com.cognos.pogo.async.service.connection.bibustkserver.BIBusTKServerConnectionFactory-queryProcessManager-ProcessReaper: Query Service - V5DataServerProcessFacade.sendStop failure. java.io.IOException: Failed to send HTTP request or read HTTP response

<<Date & Time Info>> ERROR [ com.cognos.pogo.transport.PogoServlet] http-57300-5: error occured processing pogo request java.lang.NullPointerExceptionat com.cognos.pogo.handlers.performance.PerformanceIndicationHandler$PerformanceProfiler.access$100(PerformanceIndicationHandler.java:157)

<<Date & Time Info>> ERROR [contentmanager.coordinator.ActiveCMControl] Timer-24: DPR-CMI-4007 Unable to perform an active Content Manager election on the local IP node. For more information, see the dispatcher and Content Manager detailed logs. Ensure that the local Content Manager service is started. com.cognos.pogo.pdk.dom4j.Dom4jSoapFaultExceptionat com.cognos.pogo.pdk.dom4j.Dom4jEnvelopeFactory.createSoapFaultException(Dom4jEnvelopeFactory.java:91)

The following are messages that provide more information:

<<Date & Time Info>> DEBUG [contentmanager.coordinator.ActiveCMControl] Timer-613: Sending elect() command to CM

<<Date & Time Info>> DEBUG [contentmanager.coordinator.ActiveCMControl] Timer-659: Sending elect() command to CM

<<Date & Time Info>> DEBUG [contentmanager.coordinator.ActiveCMControl] Timer-993: Sending elect() command to CM

<<Date & Time Info>> DEBUG [contentmanager.coordinator.ActiveCMControl] Timer-325: Sending elect() command to CM

Functionality by server type

The following table lists IBM Control Center functionality broken down by server type:

Sterling Connect:Direct Platform and Release	Base Functionality	High Watermark Report	Process goes to Hold Queue	Process Interrupted Events	Push Licenses	Resolved Missing and Omitted Statistics
Sterling Connect:Direct for HP NonStop version 3.5	Yes	No	No	No	No	No
Sterling Connect:Direct for HP NonStop version 3.6	Yes	No	No	No	No	No
Sterling Connect:Direct for OpenVMS version 3.5	No	No	No	No	No	No
Sterling Connect:Direct for OpenVMS version 3.6	No	No	No	No	No	No
Sterling Connect:Direct for z/OS version 5.0	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Direct for z/OS version 5.1	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Direct for z/OS version 5.2	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Direct for i5/OS™ version 3.6	Yes	Yes	No	No	No	Yes
Sterling Connect:Direct for i5/OS version 3.7	Yes	Yes	No	No	No	Yes
Sterling Connect:Direct for UNIX version 4.0	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Direct for UNIX version 4.1	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Direct for Microsoft Windows version 4.5	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Direct for Microsoft Windows version 4.6	Yes	Yes	Yes	Yes	Yes	Yes
Sterling Connect:Enterprise for UNIX version 2.4	Yes	No	No	No	No	No
Sterling Connect:Enterprise for UNIX version 2.5	Yes	No	No	No	No	No
Sterling Connect:Enterprise for z/OS version 1.4	No	Yes	No	No	No	N/A
Sterling Connect:Enterprise for z/OS version 1.5	No	Yes	No	No	No	N/A
Sterling B2B Integrator version 5.0	Yes	Yes	No	No	No	N/A
Sterling B2B Integrator version 5.1	Yes	Yes	No	No	No	N/A
Sterling B2B Integrator version 5.2	Yes	Yes	No	No	No	N/A