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

Products

• Chorus Platform
• Mainframe Chorus DBA Discipline
• Mainframe Chorus Security Discipline
• Mainframe Chorus Storage Discipline

Issue/Introduction

After starting a new LPAR that shares the CF2 databases, we see the following Chorus error messages even though 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 ACF2 databases, they also share the same GSO records. These GSO records are trying to start Chorus.

Resolution

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