CMS logs

Last Updated : May 21, 2024 |

The following is a list of CMS logs and the information they capture:

Location

Function

/cms/ahl/log

History of network configuration changes.

/cms/dc/archive/arch.log

Archive history.

/cms/maint/backup/back.log

Backup log.

/cms/env/cman/cman.log

Data cache update from CMS Web supervisor to CMS PC supervisor.

/usr/elog/elog

Error log - elog primary log used for troubleshooting.

/cms/env/gem/gem_log

User accesses to gem screens.

/cms/dc/harchive/harch.log

Interval archive log.

/cms/env/lm/license.log

License usage history log.

/cms/env/phl/phl.log

Performance history log.

/cms/env/cms_mon/proc_log

CMS processes start and end history.

/cms/db/qlog

Informix query log.

/cms/migrate/r3mig.log

Customer data migration log.

/cms/maint/r3mig/mig.log

Data migration log for services.

/cms/maint/restore/rest.log

Restore log.

/cms/env/gem/rt_gem

Real-time gem screen access.

/cms/acd[1-8]/spi.err

SPI error log.

/cms/acd[1-8]/spi.log

Messages between CM and CMS.

/cms/db/journal/timetable/ttlog

Time table (scheduler) log.

/cms/install/logdir/admin.log

CMS configuration administration log.

/cms/install/logdir/install.log

Install log.

/cms/env/lm/odbc_sess.log

Detailed ODBC and JDBC connection information for each audit cycle.

/cms/db/log/admin_chg.log

Logging of all CMS administration changes from the client. Actions logged include add, modify, delete, copy, and run.

/cms/acd1/spi.log

Spigate logging between AADA and CMS.

/cms/acd1/spigate.error

Spigate logging between AADA and CMS.