Troubleshooting Articles › Debug Security Discipline Datacom Connection Problems

Debug Security Discipline Datacom Connection Problems

Symptom:

I have the security discipline installed and configured to use the Datacom databases, and I encounter connection problems.

Or

When I try to open the security section tree in the Investigator, I receive the following error:

ETJDS091E An error occurred in a database: Group does not exist: SECURITY_DM_DB2_D91APTIB_CMGRD1.VIEWADMPOLICY.

Solution:

The cause can be identified by analyzing the server log for the following error messages:

Invalid DBSRV_HOME

Follow these steps:

1. Verify setting in CETOPTN(ENVE1M).
2. Verify DBSRV_HOME directory is mounted and contains a lib folder of files.
3. Check that all files are present in the lib folder with r-x permissions and aps/s extended attributes.

Missing CCI Library

Follow these steps:

1. Verify that the CCI modules are not in a Linklist library. If not, add CAI CCS library (CAW0PLD) containing LIBCCI and LIBCCI6E modules to the CA Chorus Application Server STEPLIB.
2. Verify the CCI External Links in Chorus/bin/lib.

Invalid SYSTEMID or CCI down

Follow these steps:

1. Verify that SYSTEMID is correct for remote Datacom server system.
2. Verify that the CCITCP job is running on the remote system.

Unauthorized Chorus Admin Userid

Verify the CHORADM authorization for the Datacom APPLID.

Missing View Definition

Verify appropriate view job for database type (E1MI0011,12,16 or 17) was successful.

Datacom Server is down

Start the Datacom Server: Ex. /S CMADSVR from SYSVIEW or SDSF command line.

Datacom Server hung

Follow these steps:

1. Check Datacom Server status report: Ex. /F CMADAVR,STATUS from SYSVIEW or SDSF command line.
2. Find the status report in the Datacom Server job listing. If the status "WAITING FREE DB THREAD" is found, recycle the Datacom Server. Ex. /P CMADSVR, then /S CMADSVR.

Database Configuration

Follow these steps:

1. Browse the following files in chorus/config:
   • security-database.cfg – user-defined csv defining database config. One record per database.
   • security- database-model.xml  - teiid model definition for each database.
   • security-database-jdbc-ds.xml – teiid datasource definition for each model including jdbc connection string.
2. Verify that the column values and database records that are defined in security-database.cfg correspond with models and datasource definitions.
3. If there are discrepancies or the configuration appears to be invalid, run the E1MI0010 security discipline database configuration job to regenerate the three configuration files. The input file is defined in the SYSUT1 DD in the COPY step. Verify that this dataset describes the desired database configuration before running.