Messages, Errors and Warnings

Connexis prints various messages, errors and warnings at run-time to help debugging and troubleshooting problems. There are three categories of such output:

Informational initialization messages (printed by Connexis when an application starts up)
Initialization errors (printed by Connexis when some error occurs while an application starts up)
Parameter errors (printed by Connexis if command-line options are incorrectly used)

Initialization Messages

The table below lists several common initialization messages:

Output	Description
`dcs: transport listening at [endpoint]` The transport could be cdm, crm or your own customized transport	This is output once the transport starts up and begins listening at the endpoint. If it does not appear, your transport was probably not included.
`dcs:CNXcrms set to [size]`	The CDM maximum receive size specified was larger than the largest buffer available. Check your use of the command-line options `CNXtran_buffer_pool` and `CNXcdm_max_rx_size`.
`dcs:CNXtfms set to [size]`	The first message size specified was larger than the largest buffer available. Check your use of the command-line options `CNXtran_max_tx_size`, `CNXtran_first_msg_size` and `CNXtran_buffer_pool`.
`dcs:**** CNXendpoint port not specified - free port will be selected ****`	A port was not specified for the endpoint and Connexis will therefore choose a random free port on which the CDM transport will listen. If you want the transport to use a specific port, use the command-line option `CNXendpoint`.
`dcs: target agent enabled`	Indicates that the target agent is running. The target agent must be running if you want to use the Connexis Viewer.
`dcs: locator running as primary`	Indicates that the locator was linked into the executable and is configured as the primary locator.
`dcs: locator running as backup`	Indicates that the locator was linked into the executable and configured as the backup locator.
`dcs: local locator not running (CNXlp or CNXlb required)`	You are using the RTDBaseLocator or the RTDBaseLocator_Agent capsule in your model. The locator was linked into the executable but has not been configured. Use the command-line option `CNXlocator_primary` or `CNXlocator_backup` to configure the locator.
`dcs: locator service not available`	The locator is not available based on configuration parameters.
`dcs: metric service enabled`	Indicates that the metrics service is enabled.
`dcs: connecting to primary locator at [endpoint]` `dcs: connecting to backup locator at [endpoint]`	These two lines are output as a pair and indicate that the primary locator is remote (see command-line option `CNXlocator_primary_endpoint`) and the backup locator is remote as well (see command-line option `CNXlocator_backup_endpoint`.
`dcs: *** Parameter [<old parameter name>] not supported. Please use [<parameter name>=<value>] ***`	Indicates that an obsolete option is used. This output means the current release has been used. When Connexis encounters obsolete command-line options, it ignores the obsolete parameters and outputs this information message. You should switch to using the recommended command-line option instead.

Initialization Errors

In case of an initialization error, Connexis prints a general error message that looks like this (this banner will not be printed if the command-line option CNXnobanner has been set):

    dcs: *********************************************************
    dcs: ***** initialization failure - dcs not available *****
    dcs: *********************************************************
    dcs: ***** banner provided for diagnosis purposes ****
    dcs: ***** use CNXd to display configuration *****
    dcs: *********************************************************
    dcs: !!!!! system failure when initializing the : <step> (<error>) !!!!!

<step> is one of the following:

configuration: problem in parsing parameters
target agent: refers to target agent for Viewer
transport-capsule: refers to transport router
transport-callback: refers to the transport callback thread (input)
transport-helpers: refers to the transport helper thread (output)
controller: refers to registration control
locator: refers to the Connexis locator service
system: any other general error

Most of these errors are internal errors that should never happen. If they still happen it could sometimes be because not enough system resources were available which caused Connexis to fail. For some messages there will be additional information printed, and in all cases there is an error code printed..

Parameter Errors

The table below lists error messages that are related to incorrect or inconsistent use of command-line options:

Output	Description
`dcs: *** multiply defined parameter [<name>=<value>] ignored ***`	Reported if you try to use a command-line option multiple times.
`dcs: *** unknown parameter [<name>=<value>] ignored ***`	A command-line option you have specified is not valid. This check is performed for all command-line options starting with CNX. See Connexis Command-Line Options for the list of valid command-line options, or use the `CNXhelp` command-line option.
`dcs: *** CNXendpoint invalid port [<value>] ***`	The port number specified for the command-line option `CNXendpoint` is invalid (non-numeric or out of range).
`*** CNXendpoint (CNXep) invalid port [port #] - freeport will be selected **`	The endpoint specification contains a syntax error. Connexis will choose a free port on which to listen.
`dcs: *** # of mblks less than # of buffers in buffer pool ***`	The Connexis Transport buffer pool is not setup properly. Check your use of the command-line option `CNXtran_buffer_pool`.
`dcs: *** Not enough buffers in buffer pool specified ***`	The Connexis Transport buffer pool is not setup properly. Check your use of the command-line option `CNXtran_buffer_pool`.
`dcs: *** invalid buffer pool specified ***`	The Connexis Transport buffer pool is not setup properly. Check your use of the command-line option `CNXtran_buffer_pool`.
`dcs: *** CNXcurs = UDP system receive buffer size must be > max receive msg size - using target default ***`	UDP buffers are not properly configured. Check your use of the command-line option `CNXcdm_udp_rx_size`. Connexis will use the default UDP receive buffer size which depends on the operating system that is used.
`dcs: *** CNXcuts - UDP system Tx buffer size smaller than max buffer size defined in buffer pool - using system default ***`	UDP buffers are not properly configured. Check your use of the command-line option `CNXcdm_udp_tx_size`. Connexis will use the default UDP send buffer size which depends on the operating system that is used.
`dcs: *** CNXlpep ignored (CNXlp takes precedence over CNXlpep) ***`	This error occurs if you specify that the executable should host the primary locator, and at the same time specify that the primary locator is in another executable. This is inconsistent, and the command-line option `CNXlocator_primary_endpoint` will be ignored.
`dcs: *** CNXlb ignored (CNXlp takes precedence over CNXlb) ***`	An executable can either host a primary locator or a backup locator but not both at the same time.
`dcs: *** CNXlbep ignored (CNXlb takes precedence over CNXlbep) ***`	This error occurs if you specify that the executable should host the backup locator, and at the same time specify that the backup locator is in another executable. This is inconsistent, and the command-line option `CNXlocator_backup_endpoint` will be ignored.
`dcs: *** CNXlp ignored (locator not present) ***`	You are not using the `RTDBase_Locator` nor the `RTDBase_Locator_Agent` capsule in your model which means the locator is not linked into the executable. Still, the command-line option `CNXlocator_primary` was used to configure the primary locator (which does not exist).
`dcs: *** CNXlb ignored (locator not present) ***`	You are not using the `RTDBase_Locator` nor the `RTDBase_Locator_Agent` capsule in your model which means the locator is not linked into the executable. Still, the command-line option `CNXlocator_backup` was used to configure the backup locator (which does not exist).
`dcs: *** CNXlpep missing (CNXlpep mandatory at backup locator) ***`	When launching the executable that hosts the backup locator you must specify the location of the primary locator. Use the command-line option `CNXlocator_primary_endpoint`.
`dcs: *** CNXlpep missing (CNXlpep mandatory when using backup locator) ***`	When launching an executable that uses a backup locator, you must specify the location of the primary locator. Use the command-line option `CNXlocator_primary_endpoint`.