IBM Support

5.1.1.6 Limitations and known issues for Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication

Preventive Service Planning


Abstract

This list provides information about limitations and known issues that you might encounter when you use IBM® Tivoli® Storage Productivity Center Version 5.1.1.6 or Tivoli® Storage Productivity Center for Replication Version 5.1.1.6.

Content

To access all of the support documentation, including alerts and APARs, go to the IBM Support Portal.

For the list of known issues for Tivoli Storage Productivity Center Version 5.1.1.5, see http://www.ibm.com/support/docview.wss?uid=swg21680422.

For information about the devices that are supported by Tivoli Storage Productivity Center Version 5.1.1.6, see the support matrix at https://www.ibm.com/support/docview.wss?uid=swg21386446.

Use the Tivoli Storage Productivity Center Version 5.1.1.1 information center and publications for Version 5.1.1.6

The Tivoli Storage Productivity Center publications and information center will not be refreshed for Tivoli Storage Productivity Center Version 5.1.1.6. To access the latest information center and publications for Version 5.1.1.6, see the Tivoli Storage Productivity Center Version 5.1.1.1 information center.


SSLv3 disabled with Tivoli Storage Productivity Center V5.1.1.6

Before you upgrade to Tivoli Storage Productivity Center V5.1.1.6, read and understand the information in this security bulletin: Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect Tivoli Storage Productivity Center October 2014 CPU.

SSLv3 (the legacy SSL protocol) has been disabled by default once you upgrade to Tivoli Storage Productivity Center 5.1.1.6 and higher. To maintain compatibility between Tivoli Storage Productivity Center and storage systems or devices that support only SSLv3, you must upgrade the storage systems and devices to a level that provides TLS support (if available) or manually enable SSLv3 in Tivoli Storage Productivity Center using a script after you upgrade. Information about using the script to enable SSLv3 is provided in the link in the security bulletin.

The Supported Hardware, Products and Platforms Interoperability Matrix Links support pages have been updated to reflect known compatibility considerations related to this security update.



Related Information: Security Bulletin: Multiple vulnerabilities impact DS8000 HMC.


Incorrect file name for Storage Resource agent service file in documentation
The Knowledge Center identifies the Storage Resource agent service data file as TPCServiceInfo.zip. The correct name of this file is TPCServiceFiles_sra.zip. This file is created when you collect service data for a specific Storage Resource agent.

This correction applies to two Knowledge Center topics:
Java errors occur when running the service tool on AIX and Linux servers
Running the Tivoli Storage Productivity Center service tool, service.sh, on Linux and AIX servers might generate java.io.IOException errors. For example, you might see:

java.io.IOException: Stream closed
    at java.io.BufferedReader.ensureOpen(BufferedReader.java:108)
    at java.io.BufferedReader.readLine(BufferedReader.java:303)
    at java.io.BufferedReader.readLine(BufferedReader.java:373)
    at com.tivoli.itsrm.tools.Service.CommandInformation$1.run(CommandInformation.java:59)

These errors can be ignored. After the service.sh script completes, the compressed file TPCServicesFiles.zip is created and can be sent to IBM Software Support.

Replication Manager tab does not display any Replication Manager launch points

In some cases, when you install Tivoli Storage Productivity Center V5.1.1.6, the Replication Manager page in the stand-alone GUI does not display any launch points. This is caused by a problem with the version of Tivoli Integrated Portal that installs with Tivoli Storage Productivity Center V5.1.1.6.


Web-based GUI pages display as blank

In some cases, web-based GUI panels display as blank. This can usually be resolved by clearing the browser cache and then refreshing the browser page.


Hover text for data points in charts does not display correctly

The web-based GUI provides a number of charts that show information about monitored resources. You can view these charts on the Details page for a specific resource. For example, to view charts for a storage system, click Storage Resources > Storage Systems, right-click on a storage system, and select View Details.

Charts that show information about historical storage usage contain data points. You can hover the mouse pointer over these data points to view additional information about storage usage at a point in time. On some charts, the hover text does not display correctly or the data point flickers on and off.

To correct the problem, move the mouse pointer away from the data point and then return to it.

PDF files do not export correctly in languages and locations with non-Latin 1 code pages

In the Tivoli Storage Productivity Center web-based and stand-alone GUIs, PDF files do not export correctly in languages and locations where non-Latin 1 code pages are used. When you try to export the file, the non-Latin 1 characters are stripped from the output.

The affected languages are:
  • Japanese
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Korean
  • Polish
  • Czech
  • Hungarian
  • Russian
When you export to CSV and HTML, the correct output is generated in all languages and locations.

You must use Tivoli Common Reporting to generate reports and export these reports as PDF files. For more information about exporting reports as PDF files, see Export Data in PDF Format.

Description column in the jobs log file does not display in the browser language

In the web-based GUI, the text in the Description column for the jobs log file is displayed in the language that is specified by the Tivoli Storage Productivity Center server, regardless of the language that is specified in the browser.

Some information messages on the jobs log panel do not link to the message help

On the panel to view job logs, some informational messages do not have a valid link to the messages help. When you click on the message link, you might see a help page that states:

The topic that you have requested is not available. The link may be wrong, or you may not have the corresponding product feature installed. This online help only includes documentation for features that are installed.

This problem occurs on all platforms, and the information message requires no further action.

Cluster data for a Storwize device is not available in Tivoli Storage Productivity Center after a Tier 3 or 4 recovery procedure

After a Tier 3 or 4 recovery procedure is performed on a SAN Volume Controller or Storwize storage system that was previously probed by Tivoli Storage Productivity Center, the cluster data is no longer available in the Tivoli Storage Productivity Center GUI. During these recovery procedures, the storage system is given a new cluster ID. Tivoli Storage Productivity Center is not aware of the new cluster ID that is associated with this device and cannot locate and gather data from the storage system.

To resolve this issue, complete one of the following steps:
  • Remove the storage system from Tivoli Storage Productivity Center and add the storage system again.
  • Run a discovery job and probe job to gather data on the storage system.

TPCInstallProgress.log file does not update to 100% after a successful silent mode installation

After you install Tivoli Storage Productivity Center in a multiple-server environment by using silent mode, the TPCInstallProgress.log file continues to display 99.55%, rather than updating to 100%.

However, the installation is complete, and you can ignore this message in the log file.

The Zone Identifier that is saved when you download some file extensions causes the security warning dialog box to be displayed

When you download files with .EXE, .ZIP, or .CAB file extensions, Internet Explorer also saves a Zone Identifier, which causes the "Open File - Security Warning" dialog box to be displayed. If you extract the files with the Windows built-in extractor utility, these Zone Identifiers remain. You do not experience this issue when you use a third-party zip utility, such as 7zip.

To resolve this issue, complete the following steps:
  1. Before you extract the Tivoli Storage Productivity Center archive files (disk1_part1 to part 6), open the Properties page for each archive.
  2. On the general page click Unblock. This removes the Zone Identifier.
  3. Extract the files by using the Windows built-in extractor utility.
  4. To determine whether the Zone Identifier was removed, run the dir /r setup.exe command on the affected file.

    If the Zone Identifier is active, you see the following output:
        11/11/2013  01:33 AM           149,384 setup.exe
                                                 26 setup.exe:Zone.Identifier:$DATA

    If the Zone Identifier was successfully removed, you see the following output:
        11/11/2013  01:33 AM           149,384 setup.exe

Starting the DB2 Control Center on AIX operating systems

In DB2® Version 9.5, to start the DB2 Control Center on the AIX operating system, run the db2cc command in a command window.

Installation hangs during Tivoli Integrated Portal installation if a reference to IBM Java Version 7 is found in the Windows path statement

If you have references to IBM Java Version 7 in your Windows path statement, the Tivoli Storage Productivity Center installation program will hang while installing Tivoli Integrated Portal. IBM Java 7 is not supported by Tivoli Storage Productivity Center Version 5.1 or later.

To resolve this issue, complete the following steps:
  1. Uninstall Tivoli Storage Productivity Center by using the instructions in the Uninstalling Tivoli Storage Productivity Center information center topic.
  2. Temporarily remove the reference to IBM Java Version 7 from your Windows path statement.
  3. Run the Tivoli Storage Productivity Center installation program again.
  4. Add the IBM Java Version 7 reference back to your Window path statement.
  5. Restart your Tivoli Storage Productivity Center server.

Always run the setenv command before running the srmcp command

The setenv command must be run before you run the srmcp command. Several information center and User's Guide topics do not include the instructions for running the setenv command before running the srmcp command.

To run the setenv command on Windows operating systems:

1. Go to the C:\Program Files\IBM\TPC\device\bin\w32-ix86 directory.
2. Run the setenv command.
3. Run the srmcp command from the same location.

On AIX or Linux operating systems:

1. Go to one of the following default directories:
    • /opt/IBM/TPC/device/bin/aix
    • /opt/IBM/TPC/device/bin/linux

2. Run the ./setenv.sh command.
3. Run the srmcp command from the same location.

Information center specifies an incorrect location for the stand-alone GUI logs

The information center topic Default log file locations specifies an incorrect location for the stand-alone GUI log files.

The correct location is:
  • On Windows operating systems:

  • TPC_installation_directory\data\log
  • On UNIX or Linux operating systems:

  • TPC_installation_directory/data/log

You can track the status and resolution of this problem by checking APAR IC90097.

Updated command for changing the DB2 password on the Data server

The command to change the DB2 password on the Data server has changed. TSRMsrv.zip has been replaced by TPC_Common.jar.

These are the updated commands:

On Windows operating systems:

C:\Program Files\IBM\TPC\data\config>\"program files"\ibm \tpc\jre\bin\java -classpath "\program files\ibm\tpc\data\server\lib\TPC_Common.jar" com.tivoli.itsrm.repository.Transform -p <new_password> repository.config

On AIX/Linux operating systems:

/opt/IBM/TPC/jre/bin/java -classpath "/opt/IBM/TPC/data/server/lib/TPC_Common.jar" com.tivoli.itsrm.repository.Transform -p <new_password> repository.config

This change affects the information center topic Changing the DB2 password for the Data server, which is also on page 216 in the IBM Tivoli Storage Productivity Center 5.1.1.1 User's Guide.

You can track the status and resolution of this problem by checking APAR IC91133.

Incorrect reference to Limited Edition in the information center and Tivoli Storage Productivity Center V5.1.1.1 User's Guide

The Product overview topic on page 11 of the Tivoli Storage Productivity Center 5.1.1.1 User's Guide and information center incorrectly references Tivoli Storage Productivity Center Limited Edition. This version of the product is no longer available.

Logging in to the Tivoli Storage Productivity Center stand-alone GUI by using a Windows domain account

To log in to the Tivoli Storage Productivity Center Version 5.1.1.6 stand-alone GUI by using a Windows domain account, complete the following steps:

1. Verify that your Windows domain user ID belongs to a Windows domain group (for example, Domain Administrator or Domain Users) by completing the following steps:
    1. Log in to the Windows domain controller computer and click Start > Active Directory users and computers > Domain DNS > Users.
    2. Right-click the Windows domain user ID and select Properties.
    3. On the Member of tab, if the Windows domain group is not listed, click Add.
    4. Add the Windows domain group and click OK.

2. Assign roles to the domain group by completing the following steps:
    1. Log in to the Tivoli Storage Productivity Center stand-alone GUI by using a local administrator user ID (for example, Administrator).
    2. Click Administrative services > Configuration > Role-To-Group mappings.
    3. On the role (for example, Productivity Center administrator or Tivoli Storage Productivity Center tape operator) that you want to assign, enter the Windows domain group (for example, Domain Administrator or Domain Users).
Restriction: Do not enter the domain_name (for example, TPC\) in front of the Windows domain group name.

The help for the web-based GUI does not render properly in Internet Explorer Version 10

The table of contents, search, and other web-based GUI help features do not render properly in Internet Explorer Version 10. These help features work properly and display properly in other web browsers.

This issue will be fixed in a future release of Tivoli Storage Productivity Center.

Information about removing an expired certificate is missing from the Enabling secure communication between Tivoli Storage Productivity Center and the LDAP repository information center topic

In the Enabling secure communication between Tivoli Storage Productivity Center and the LDAP repository information center topic, the following steps are missing after step 8:
  1. If the existing certificate has expired, click Security > SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates.
  2. Select the expired certificated and click Delete.

Update to process for changing the authentication method from local OS to LDAP

In the information center topic Changing the authentication method from local operating system to LDAP federated repositories, step 15 requires an additional verification when you restart the Tivoli Storage Productivity Center-related servers after changing the authentication method. This update applies to Tivoli Storage Productivity Center Version 4.2 (or later) and Version 5.1 (or later).

For more information about this documentation update, see https://www.ibm.com/support/docview.wss?uid=swg21661438.

An error message might appear when you try to download the launch.jnlp file in the Tivoli Integrated Portal console

The first time you log into Tivoli Integrated Portal by using HTTPS in Internet Explorer 9 and click the Start the stand-alone GUI for Tivoli Storage Productivity Center link, an error message might appear when you try to download the launch.jnlp file. This is caused by a security issue in Internet Explorer that requires you to confirm that the secure connection can be trusted.

For information about resolving this security issue and download files by using HTTPS, see the Microsoft Support web site. Search for Error message when you download files by using Internet Explorer 9 from secure websites: "<filename> couldn’t be downloaded".

Cannot launch Replication Manager GUI from the launch point buttons on the Replication Manager page of the Configuration Utility

If you are using LDAP authentication, the launch point buttons on the Replication Manager page of the Configuration Utility in the stand-alone GUI might not work. This can happen if the LDAP user is assigned to a user group that does not have the correct role assigned in Tivoli Integrated Portal.

To assign a Tivoli Integrated Portal role to the LDAP user, complete the following steps:
  1. Log on to Tivoli Integrated Portal. For example, you can enter http://<machine where Tivoli Integrated Portal is installed>:9568/ibm/console in a web browser.
  2. Click Users and Groups > User Roles.
  3. Search for a user by using an ID or a first and last name.
  4. Select the LDAP user.
  5. Under Available Roles, select a role and click Save. The LDAP user must have at least Monitor authority to use the Replication Manager launch points.
  6. Log on to the Tivoli Storage Productivity Center stand-alone GUI by using the LDAP user and password.
  7. Navigate to Replication Manager > Replication Manager. You should now be able to use the launch point buttons to open the Replication Manager GUI.

Starting the stand-alone GUI from the Tivoli Integrated Portal console results in an ATKLIC019E error or the console hangs with "Starting" status

If you used the javaws tool from the TPC_installation_directory/jre/bin directory or if you used another javaws tool, you might see the ATKLIC019E error or the Java Web Launcher might hang. To resolve this issue, you might have to configure your web browser to use another version of IBM Java Web Start when you open JNLP files. For example, you can click Browse and select javaws from the TPC_installation_directory/ewas/java/jre/bin directory. If you use JRE Version 1.6 or later, you can also reference the javaws tool from any version of IBM JRE that is installed on your computer.

For information about setting up Java Web Start in Mozilla Firefox, see the InfoSphere Identity Insights Knowledge Center. Search for Setting Mozilla Firefox to use the required Java Web Start.

Note: Ensure that there are no security or firewall restrictions when you execute the javaws tool. For example, on Linux operating systems, you might need to modify the settings for the SELinux module to allow the execution of javaws.

Data Path Explorer displays CRG connections that do not have volumes assigned from the subsystem

In some cases, the Data Path Explorer incorrectly displays connections to cluster resource groups (CRGs) even though the subsystem does not have any volumes assigned to those entities. You cannot drill down to these entities and display additional details.

Information center topic incorrectly lists embedded TPC as a valid license type

In the IBM Tivoli Storage Productivity Center Installation and Configuration Guide, the Adding an installation license topic states that an embedded version of Tivoli Storage Productivity Center is available as part of IBM® Systems Director. This is not correct for Tivoli Storage Productivity Center Versions 5.1 and later.

Unable to log on to the stand-alone GUI by using a Windows domain user name

If a Windows domain user name belongs to a local group that is mapped to a Tivoli Storage Productivity Center role, you cannot use this user name to log in to Tivoli Storage Productivity Center. To log in to Tivoli Storage Productivity Center, the domain user name must belong to a domain group that is mapped to a Tivoli Storage Productivity Center role.

Update to the "Cleaning up a failed installation or uninstallation on Windows" information center topic

Step 2 in the information center topic incorrectly specifies how to remove the Common Agent.

The correct text for step 2 is:

2. Remove the Storage Resource agent entries from the Windows registry by using the instructions in the following information center topic:
Deleting Storage Resource agent registry entries after a failed installation or uninstallation.

Unable to add a NAS filer if the Storage Resource Agent service that runs under the Administrator user ID is not used to add a NAS filer

When you add a NAS filer, you must enter the Administrator user ID for the Storage Resource agent service on which it runs.

To manually add a NAS filer, complete the following steps in the Tivoli Storage Productivity Center stand-alone GUI:
  1. Expand Administrative Services > Configuration > Manual NAS Server Entry.
  2. Click Add NAS Server.
  3. On the Add NAS Server window, enter the Administrator user ID in the Login ID field.

The back up and restore procedures fail to recover from an authentication change

You cannot log in to Tivoli Integrated Portal and Tivoli Storage Productivity Center after you modify the authentication and try to restore Tivoli Storage Productivity Center.

To resolve this situation, complete the following tasks:
  • Before you change the user authentication configuration by adding or removing an LDAP repository in the federated repositories framework, back up the existing WebSphere Application Server configuration files.
  • After you add an LDAP repository to the user authentication configuration and want to later change the LDAP authentication settings, back up the WebSphere configuration files.
  • In the TIP_installation_directory, back up, and if necessary, restore the isc.ear file.

On Windows operating systems:

TIP_installation_directory\profiles\TIPProfile\installedApps\TIPCell\isc.ear

If you completed a default installation on the Windows operating system, the isc.ear directory is located here:

C:\ProgramFiles\IBM\tipv2\profiles\TIPProfile\installedApps\TIPCell\isc.ear\

On AIX or Linux operating systems:

TIP_installation_directory/profiles/TIPProfile/installedApps/TIPCell/isc.ear

If you completed a default installation on the AIX or Linux operating systems, the isc.ear directory is located here:

C:/ProgramFiles/IBM/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear\

Update to process for changing the authentication method from local OS to LDAP

In the information center topic Changing the authentication method from local operating system to LDAP federated repositories, step 15 requires an additional verification when you restart the Tivoli Storage Productivity Center servers and related servers after you change the authentication method. This update applies to Tivoli Storage Productivity Center Version 4.2.x and Version 5.1.x.

This additional verification involves logging in to the Tivoli Integration Portal server to verify that it is fully functional before you start the other Tivoli Storage Productivity Center services.

For more information about this documentation update, see technote IC96172: Update to process for changing authentication method from local OS to LDAP.

For more information about this APAR, see APAR IC96172.

Stop all jobs and reboot servers before upgrading Tivoli Storage Productivity Center
(APAR IC99222)

Follow these steps before upgrading Tivoli Storage Productivity Center:

1. Stop all jobs including performance monitor jobs, system and fabric probe jobs, scan jobs, and other probe jobs.

2. If possible, reboot the Tivoli Storage Productivity Center servers. This action will stop any remaining Tivoli Storage Productivity Center Java processes that might not stop in a timely manner. If a reboot is not possible, stop and restart the Tivoli Storage Productivity Center server service. It is important for the Tivoli Storage Productivity Center Device server to stop and restart cleanly. If this does not occur, a server reboot might be indicated.

To track the status and resolution of this APAR, see APAR IC99222.

References to PowerHA® should be PowerHA® System Mirror for AIX

References to PowerHA in the Tivoli Storage Productivity Center documentation should specify PowerHA System Mirror for AIX. Other PowerHA versions are not supported by Tivoli Storage Productivity Center.

Error SRV0853E is displayed when you try to log in to the stand-alone GUI

In some cases, when you try to log in to the stand-alone GUI, you get a SRV0853E error message. You see an error similar to the following error in the Data Server log file (<TPC_installation_directory>\data\log\ServerTrace.log):

2016-10-18 13:14:23.931+0200 EXCEPTION
  java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy5.authenticate(Unknown Source)
at com.tivoli.itsrm.server.SingleSignonHndlr.authenticateUserOrToken(SingleSignonHndlr.java:409)
at com.tivoli.itsrm.server.SingleSignonHndlr.handle(SingleSignonHndlr.java:141)
at com.tivoli.itsrm.server.RequestManager$RmThread.run(RequestManager.java:501)
Caused by: [SOAPException: faultCode=SOAP-ENV:Server; msg=java.lang.IllegalArgumentException: Illegal daylight saving value: 0]
at org.apache.soap.providers.RPCJavaProvider.invoke(Unknown Source)
at com.tivoli.sanmgmt.middleware.data.RPCSecureJavaProvider.invoke(RPCSecureJavaProvider.java:172)
at org.apache.soap.server.http.RPCRouterServlet.doPost(Unknown Source)
at com.tivoli.sanmgmt.middleware.TSNMServiceManager.doPost(TSNMServiceManager.java:469)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1275)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:766)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:472)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1101)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:81)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:912)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:262)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:938)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:798)  com.tivoli.itsrm.server.RequestManager$RmThread run RequestHandler0

This error occurs because the Java Runtime Environment (JRE) does not comply with Daylight Saving Time (DST). To fix this problem, do one of the following actions:

Known issues for Tivoli Storage Productivity Center for Replication



HyperSwap session shows Prepared status when source is offline

In some cases , a Tivoli Storage Productivity Center for Replication for System z HyperSwap session will display Prepared status even though the HyperSwap source is offline to the z/OS system. This can cause issues with the HyperSwap session. The log file will show
device status = 0x40000


To resolve this, make sure that the HyperSwap source volumes are online to the z/OS system, and the target volumes are offline to the z/OS system when you start a HyperSwap session.. For more information about HyperSwap sessions, see http://www.ibm.com/support/knowledgecenter/SSU9FR_5.1.1.1/com.ibm.tpcrz.doc_5.1.1.1/frg_c_ct_hyperswap.html.

HyperSwap address space must be running before issuing HyperSwap starth1h2 command in z/OS sysplex environment [<!-- 107748 -->]

When the HyperSwap address space is not running, starting a Basic HyperSwap session by using the starth1h2 command in a z/OS sysplex environment can result in a Warning/Prepared status. Issuing the starth1h2 command a second time returns Prepared/Normal status. However, the HyperSwap session is not actually capable at this point. This occurs when the Basic HyperSwap address space is not started and running on all members of the sysplex.

To resolve this issue, make sure that the HyperSwap address space is running on all z/OS sysplex members. For instructions for starting HyperSwap address spaces, see http://www.ibm.com/support/knowledgecenter/SSU9FR_5.1.1.1/com.ibm.tpcrz.doc_5.1.1.1/frc_c_basichsconfig.html.



Return code is not displayed in message IWNR5441E

Message IWNR5441E displays with an incorrect or missing return code. This is a known problem and will be fixed in a later release.

An IWNR2072E error is displayed incorrectly for System Storage DS8000 sessions

If Tivoli Storage Productivity Center for Replication is connected to a System Storage DS8000 storage system by using an HMC connection and a quiesce and resume occurred for the cluster, one or more copy sets might report an IWNR2072E error.

This error is displayed when a role pair was deleted from the System Storage DS8000 storage system, but not from the Tivoli Storage Productivity Center session. However, in the situation of a quiesce and resume, the role pair was not deleted and this error is displayed incorrectly.

To resolve this issue, run the Start command for the session.

To prevent the issue from occurring, you can disable ESSNI queries in the Tivoli Storage Productivity Center for Replication rmserver.properties file by adding the following property to the file:

EnableESSNIQuery=false

This rmserver.properties file is in the following directory:

Tivoli Storage Productivity Center for Replication: WAS_HOME/profiles/ReplicationServerProfile/properties
Tivoli Storage Productivity Center for Replication for System z: WAS_HOME/profiles/ReplicationServerProfile/properties

When you disable ESSNI queries in the rmserver.properties file, an older and slower version of the Tivoli Storage Productivity Center for Replication API is used, which might have a significant impact on performance. However, if you have a planned quiesce and resume for a cluster, you might want to disable the ESSNI queries, complete the quiesce and resume actions, and then remove the EnableESSNIQuery=false property.

In zOS connected storage, the initially discovered device displays as disconnected

After you install Tivoli Storage Productivity Center for Replication Version 5.1.1.2 for zOS, if the connection has multiple storage systems, the first storage system that is found by Tivoli Storage Productivity Center for Replication remains disconnected. This device is displayed as disconnected when viewed from the active and the standby server.

When a session tries to use this device, Tivoli Storage Productivity Center for Replication displays the Could not be determined status message. Once you try to connect the storage by using an HMC connection, the zOS connection of the primary storage system remains disconnected, and the overall connection status is Degraded. If one of the connections can communicate with the storage, all functionality will be available, despite the degraded state.

To resolve this issue, complete the following steps each time you start the server:

Important: If you do not have two connection types to the server, when you remove the device, the session copysets are also removed. For example, HMC, direct, and zOS connections can exist for one device. If an HMC or direct connection is available over TCP/IP, you can add the connection before you complete this procedure.

  1. Ensure that multiple connections are defined for the device that shows as disconnected. For more information about ensuring that these connections are defined, see Storage connections.
  2. Remove the disconnected storage system from the zOS connection view in the GUI or use the rmstorsys command. For more information about the rmstorsys command, see rmstorsys.
  3. Add the storage system again by using the zOS connection view via the GUI or use the addstorsys command. For more information about the addstorsys command, see addstorsys.
Starting and stopping Tivoli Storage Productivity Center for
Replication from a command line (APAR IC98593)

When you start or stop Tivoli Storage Productivity Center for Replication from a command line, use the following parameter. This parameter is case sensitive:

replicationServer

This replaces the previous parameter, which is no longer valid:
ReplicationServer

On Windows, the command to start the Replication server is now:
WAS_HOME/profiles/ReplicationServerProfile/bin/startServer.bat
replicationServer

On AIX and Linux, the command to start the Replication server is now:
WAS_HOME/profiles/ReplicationServerProfile/bin/ startServer.sh –
username user_name –password password replicationServer

For more information about this APAR, see APAR IC98593.

[{"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.1.1","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
22 February 2022

UID

swg21695327