Print a help message and exit.
Do not use the Cascade DataHub, even if nserve is running. Normally cserve will assume that it should talk to a Cascade DataHub if nserve is available, even if no datahub is running, on the assumption that the datahub may be started later.
Log read and write information to the specified log file.
Timestamp the data coming from the TCP connection.
Produce debugging information on the data server. Using this option will create and append two potentially large files called /tmp/rlog and /tmp/wlog. These log files contain a complete log of all messages sent to the data server (rlog) and all messages sent to Windows (wlog).
Print the version number.
Exit immediately (usually used with -V).
The cserve program is an SRR/IPC to TCP/IP bidirectional conversion program. When messages are sent to it using SRR/IPC, it converts the data to TCP/IP and sends the information to the Cascade Connect executable (cascade.exe) under Windows.
When cserve receives information from a TCP/IP socket, it converts the message into data server IPC format and passes the information back to a recipient. If you are not using the Cascade DataHub, the recipient of the message is a program which has registered the name given in the Client Name field in DDE and Name Settings of the Setup window. If you are using the Cascade DataHub, typically it receives the message itself.
cserve is started from the script file /usr/local/bin/cascade which is called as required by inetd to start Cascade Connect. Program arguments to cserve should be added to the cascade script.
![]() | The user does not start this program. The inetd task spawns this task when it receives a message from the Cascade Connect. |