Platforms

All platforms under which LISTSERV's DBMS features are supported.


Abstract

Tells LISTSERV to mirror a copy of all or selected changelogs to DBMS.

Examples

z/VM:

(not supported)

Unix:

CHANGELOG_DBMS="ALL"

CHANGELOG_DBMS="SYSTEM BIGLIST-L"

export CHANGELOG_DBMS

Windows:

CHANGELOG_DBMS=ALL

CHANGELOG_DBMS=SYSTEM BIGLIST-L

Details

LISTSERV allows a copy of change logs to be stored in a DBMS. This requires a pre-existing DBMS connection (see the Advanced Topics Manual for LISTSERV, chapter 1, if you need guidance), and is controlled by three site configuration parameters, and a table that must be created manually. The parameters, which are defined in LISTSERV's site configuration file, are CHANGELOG_DBMS, CHANGELOG_DBMS_TABLE, and CHANGELOG_DBMS_CONNECTION .  The first two are mandatory while the third is optional.

Note:  It is not possible for LISTSERV to write the changelog in multiple different tables based on various combinations of parameters. This can be accomplished on the DBMS side with a stored procedure if required.

Important: The DBMS copy is just that, a copy. The disk files are still generated. Naturally if they are not needed they may periodically be erased with a script.

CHANGELOG_DBMS controls which entries are to be copied to the DBMS. Note that only entries that are actually generated can be copied. If a given change-log is disabled, it will not go to the DBMS even if you request it in this variable.

The value can be ALL or a space-separated combination of SYSTEM, NOLIST (matches any NOLIST-xxx), LISTS (matches any list) or the names of individual lists.


Default Value

Not set (null string).


Wildcards

Not allowed.


See also

CHANGELOG_DBMS_TABLE, CHANGELOG_DBMS_CONNECTION