Windows Serial Service (jseriald)


jBASE windows includes a serial communications service that allows connection of serial terminal devices such as modems and dumb terminals to be connected to the jBASE database.

Copy files to %JBCRELEASEDIR\bin   (jBASE 3 only)

·         For jBASE3 you need to copy these items to %JBCRELEASEDIR\bin
%JBCRELEASEDIR%\telnet\jSeriald.exe
%JBCRELEASEDIR%\telnet\TranscmdSerial.exe

Modify or Create the jSeriald_config file

%JBCRELEASEDIR%\config\jSeriald_config should contain the following lines per COM port

typically - COM1:vt100,9600,8,FALSE,FALSE,FALSE

PORT#: Term type, Baud rate, Byte size, Parity, CTS, DRS

PORT # - COM1 through COMn where n is the maximum number of configured serial ports on the server.

Colon separator and then the following parameters delimited with a comma.

Term type - such as vt100, wy50 etc. (must be contained in %JBCRELEASEDIR%/misc/[a-z] folders)

Baud Rate - The value required.

Byte Size - Usually 7 or 8.

Parity - Either TRUE or FALSE - defaults to false (no parity).

CTS - Either TRUE or FALSE which indicates whether CTS (clear-to-send) signal is monitored for output flow control. If TRUE then CTS is turned off, output is suspended until CTS is sent again

DRS - Either TRUE or FALSE which indicates whether DSR( data-set-ready) signal is monitored for output flow control. If TRUE then DSR is turned off, output is suspended until DRS is sent again.

Install the service

Note: The jSeriald install must be done from the %JBCRELEASEDIR%\bin directory

jsh-> cd %JBCRELEASEDIR%\bin
jsh-> jSeriald install

jBASE Serial Port Service can now be started / stopped from within the Services Control Panel. It is initially installed as a manual service and can be set to Automatic if you want it started when Windows is rebooted.

When users logon, their environment will contain all system-wide environment variables that are set on the local system.  In order to run jBASE after logging on, the logon process must execute the file “remote.cmd” . This file is setup in the following manner: The logon procedure will first look for a local path within the user specification, containing the location of the “remote.cmd” file (See profile tab of user properties specification). If, present, then this file is executed, setting up the local jBASE environment for the user. If this entry is not present, then a search will be made in “C:\users\(username folder)\remote.cmd”, failing that within “C:\users\default\remote.cmd”. If the “remote.cmd” does not exist in any of these locations, then the user will still be allowed to logon, but the jBASE user environment will be set up per system-wide environment variables and unpredictable results may occur.