After starting a new LPAR that shares the CA ACF2 databases, we see CA Chorus error messages even though CA Chorus is not running.

Products

• Mainframe Chorus DBA Discipline

Issue/Introduction

Problem:

After starting a new LPAR that shares the CA ACF2 databases, we see the following CA Chorus error messages even though CA Chorus is not running on this LPAR:

*CIA0310I CIA Real Time Sys Logger Connect LogStream=CHORUS.CIA. 

ST.LGSTRM RC=00000008 RSN=000008E2 

CIA0359I CIA Real Time Logstream - Writes pending 

 

We also continually receive the following message in our log: 

ACF79757 UNABLE TO SEND DATA, ERROR DIALOG TSF SUFFIX P RC 00000008

 

Cause:

Because the LPARs share the CA ACF2 databases, they also share the same GSO records. These GSO records are trying to start CA Chorus.

 

Resolution:

Assign a different GSO record that does not include any CA Chorus-related information to the new LPAR. Doing so lets the system with CA Chorus continue to use the existing GSO record, while the system without CA Chorus uses a GSO record that does not try to start anything related to CA Chorus.

Environment

Release:
Component: CHRSEC