Known Issues

CA Chorus Known Issues

Important! CA Chorus known issues apply to all disciplines.

Equal sign does not work for date filtering

When filtering based on data in the Investigator, the equals option does not work properly. To navigate around this issue, use search criteria Column>=Day X and Column <=Day X+1.

100 Percent File System and zFS Growth

When the CA Chorus file system reaches 100 percent, the CPU spikes. Using the AGGRGROW option for your zFS0 data set may mitigate this issue, as noted in our installation materials. If this option does not help, move the zFS to a larger volume that allows for greater growth of the zFS.

User-Added Content Not Retained in Knowledge Center

If you upload and index documentation to the Knowledge Center and then install a new release of CA Chorus or apply an APAR, you must reindex your content. Otherwise, the content does not appear in your search results. For example, if you upload a file about your site policies and then apply an APAR, reindex to ensure that this information appears in the Knowledge Center.

Browser Refresh Closes Child Windows

If you use the browser refresh button while in a CA Chorus main window, child windows close (for example, Investigator and Knowledge Center). This issue applies to Internet Explorer and Mozilla Firefox.

Selecting Large Number of Objects While Creating Policy Can Cause High CPU Usage

Selecting large number of objects while creating a policy using the Object Picker can cause high CPU usage.

Best practice on Select All Usage:

Use Select All when building a policy rather than selecting individual objects. That way, if similar, new objects are created, they will be covered by the policy without any additional configuration. Note the following points to avoid high CPU usage:

If there are groups of objects that you want to include or exclude, specify them through filters.
If the count of objects included is in the tens of thousands or more, it can cause high CPU usage. If you are building policy for an object type that has thousands of instances, use appropriate filters to include only the objects needed for your policy.

Discrepancies in the Policy Status Light Module

When the objects associated with a policy are no longer available, users may observe the following discrepancies in the Policy Status Light module:

The Show Overall or the Group By Object Type options show colored-lights for the object that is unavailable. But, the hover text indicates that the information about the object is unavailable. The Show Object Instances option does not show colored-lights for the objects that are unavailable.
The Show Object Instances option shows less number of objects than the number of objects in the policy or the hover text indicates that the information about the object is unavailable.

ClientAbortException in the Server Log

When a connection is closed from the client (browser) side before the server sends all data, you may see a ClientAbortException in the Server log. Ignore this exception because it does not have any impact on the application.

Error While Navigating from Actions and Enabling Auto-Refresh

In the Investigator, with the auto-refresh option enabled, in some instances, when the data refreshes, you get an error.

Back-end Documentation with CA Chorus Updates Not Indexed

For use with CA Chorus, we have updated the following documentation:

CA ACF2 Version 15
CA Compliance Manager Version 2
CA LDAP Server Version 15
CA DSI Server Version 15
CA NetMaster NM for TCP/IP Release 12.1
CA SYSVIEW Release 13.7
CA Top Secret Version 15
CA Vantage Release 12.6

The updates for CA Chorus-related content since Release 2.5 are not yet generally available (GA); therefore, they cannot be posted on CA Support Online. The Knowledge Center requires that the content be on CA Support Online to be indexed. This content is not included in the Knowledge Center. Instead, the latest available GA release of these documentation sets is indexed. The documentation sets that include the CA Chorus Version 3.0 updates are posted on the beta FTP site.

Additionally, these documentation sets temporarily refer to the product as CA Mainframe Chorus.

User encounters error ‘bash: line 61: syntax error near unexpected token’ while using CA CSM to configure CA Chorus.

If the user encounters the error ‘bash: line 61: syntax error near unexpected token’ and the user has ‘exec bash’ in their .profile, replace ‘exec bash’ with the following code: TTY=`/bin/tty` if [ "${TTY}" != "not a tty" ];then stty erase ^? exec bash fi

Contradicting filter gives a possible result

If you enter contradicting filters in the Investigator, you may see search results when you should not see any rows of data.

Select Button is Disabled While Creating the Policies

The selection of the following type of objects is disabled while creating policies:

Objects that have some mandatory and default filters, but do not have any columns available for filtering.

Limited Number of Records Appear While Expanding a Summarized Node in the Data Pane

You use the Group By option to group the data based on the selected columns when you customize your column settings. When you expand the grouped data, the Data pane displays a maximum of 100 records. Do a search to view the rest of the records.

Exported CSV Files Show Large Value for Time Interval

When you export time-based objects using the Export option in the Investigator, the CSV file may show a large value for the Time Interval column than it was displayed in the Data pane of the Investigator. This happens because the export functionality exports all the rows. If the rows to be exported exceed 1200, the Time Series Facility adjusts the interval value to display only 1200 rows.

Resource Adapter is Not Deployed and CHORJBOS Shuts Down During Data Source Deployment of JBoss Startup

When data sources are deployed during JBoss startup, the following error appears:

Failed to start service jboss.ra.deployment.vice thread 1-1
teiid-connector-file.rar_4
JBAS010446: Failed to start RA deployment [teiid-connector-file]
Caused by: javax.resource.spi.InvalidPropertyException:
ParentDirectory is not set.

The Resource Adapter (RA) file is not deployed or accessible and the JBoss server started task (CHORJBOS) shuts down. You must restart CHORJBOS.