jRFS Quick Start Guide

These guide covers a basic configuration of jRFS. It describes a configuration up between a client machine (omega) and a server (demo), both running Windows.


The jRFS Service

Make sure you have an entry on both client and server machines in %SYSTEMROOT%\system32\drivers\etc\services that follows the schema:

<service name> <port number>/<protocol>[aliases...] [#<comment>]

For jRFS the entry required is:

jRFS    5001/tcp    jRFS      #jBASE Remote file service


Client Setup

On the client machine, omega, we create a Q pointer called RFSDEMO. This necessitates an MD/VOC file being set up on the client. The Q-pointer item is:

001 Q
(local SYSTEM account name entry)
(Actual remote filename to be accessed)

In the SYSTEM file on the client machine we must define the "account" ACCDEMO. The ‘R’ pointer identifies it as a remote reference.

001 R
004 DEMO
(hostname of remote machine)

There are 4 files concerned with configuration of jRFS:


jConnect client and server configuration file.


jConnect client mapping file.


jConnect server environment map file.


jRFS client and server configuration file.

jRFS provides some very useful logging capabilities that are the quickest way to debug your setup. The log entries will tell you what the jConnect software is looking for at the point of failure so that you can rectify the specific problem. jnet_config is where these logs are turned on as follows:


This will have the effect of writing detailed log information to the logfile specified above. Each access attempt will append multiple lines of text to the log.

The jnet_map file allows you to map your local username to a different username on the remote host. Any access to the remote files will then be carried out using the permissions of that user.

LOCAL:omega jRFS steve steve
REMOTE:demo jRFS jrfsuser

According to the logs, jRFS expects an entry to contain your username as both the local and remote username i.e. ‘steve steve’ in this case. This is mapped by the REMOTE entry to the user ‘jrfsuser’ on the host ‘demo’.

The jrfs_config file allows you to turn on a screen trace which outputs messages to stdout which can be useful in noting progress. This is done by putting in settings as follows:


jnet_env and jnet_access require no changes on the client machine.


Server setup

Create an account entry in the SYSTEM file on the server as follows:

001 D
002 C:\JBASE30\JDP\DEMO (path to account directory)

This will be the directory where the file to be accessed exists i.e. JCUSTOMERS in this example.

These settings will write corresponding logfile on server machine. Compare with client log when debugging.


This last setting causes a security check to be performed to see if the connecting machine/user id is allowed access.

On Unix:
There are two methods available, ruserok provided by the OS, and jnetok method provided by jRFS. The first method is normally sufficient for user’s needs. This involves adding the client hostname to the /etc/hosts.equiv file on the server, along with a reference to which users are allowed access, as follows:

jbase2 jbaseadmmike only this user will be allowed in from jbase2
jbase1 + all users allowed from jbase1

On Windows:
Only the jnetok method is supported on Windows, which will require the jnet_access file to be configured. This file contains account and password to map to, note that account must have profile set up with home directory. In this case account=jrfsuser and password=jbase

omega Steve jrfsuser jRFS jbase

No changes are required to jrfs_config, jnet_env or jnet_map.

This should be enough to get a simple demo working between two machines. The only potential problems are regarding user names on the Server, but if you follow what the logs are telling you the issues to be resolved will be obvious.

Below are a set of log file entries for the above configuration. What I did was to JED RFSDEMO on the client, which opened the remote file JCUSTOMERS on the server using the username ‘jrfsuser’. You can clearly see the checks it goes through and what jRFS is looking for. 

Unix config files examples
Username on jbase2 is jbaseadmmike
on sun is omega

CLIENT Machine – ‘jbase2’


LOCAL:sun jRFS jbaseadmmike jbaseadmmike
REMOTE:sun jRFS omega


SERVER Machine – ‘sun’


ENV:jRFS omega jbaseadmmike



Using jEDI stub files

If you’re trying to open remote files, which are actually stub files which interface into an external database, you may need to set up jnet_env on the server side in order to set up environment variables for jRFS.

For example using Oracle stub files on NT, I got a ‘cannot find orasql8.dll’ error with jRFS in the title bar, indicating that the file was not found in the PATH. This was fixed by the following in jnet_env:

ENV:jRFS jrfsuser Steve

This specifies to use these variables when a request comes in for the specified local and remote username. Setting this and stop/starting jRFS Service fixed this.

Accessing remote files via jDP

jDP advertises files from the MD configured for the user (via JEDIFILENAME_MD), as well as via HOME and JEDIFILEPATH. Hence you should be able to see the Q pointers which reference the remote files shown earlier. So far I haven’t been able to do this. In jDP I can ‘see’ local ‘F’ pointered files so the resolution via the MD is working OK. However I can’t ‘see’ even local or remotely defined Q ptr files from jDP, even though they both work OK from jsh.

An alternative method is to create jRFS stub files on the client machine. These will direct the request across to the remote machine specified. One stub file is created for each corresponding remote file. In the case of jDP, it only advertises dictionary files hence we need a dictionary stub to refer to the remote dict.

Using JED . RFSREM (and RFSREM]D) to create stubs:

File RFSREM contains

and file RFSREM]D contains

STEVE is actually an Oracle stub file created on the server using:


This will create a data and dict stub file and create the corresponding table called STEVE within Oracle itself.

At this point RFSREM will appear in the list of advertised ‘tables’ in jDP (as long as RFSREM]D is in the JEDIFILEPATH or HOME). This means that an ODBC connection can be made via jDP, jRFS and the jEDI interface into Oracle!

jRFS Client Log File
May 05 18:06:31:320[Connect] connect request for host DEMO, server jRFS
May 05 18:06:31:320[Connect] HostId not null DEMO
May 05 18:06:31:320[GetUser] GetUserName succesful, username Steve, size 6
May 05 18:06:31:320[Connect] RemoteId null defaulted to User Steve
May 05 18:06:31:320[NameMap] mapping host demo, server jRFS, user Steve, client Steve
May 05 18:06:31:320[NameMap] searching C:\JBASE30\config\jnet_map for map string 'LOCAL:demo jRFS Steve Steve'
May 05 18:06:31:320[NameMap] map string found
May 05 18:06:31:320[NameMap] remote host demo, remote server jRFS, remote user jrfsuser
May 05 18:06:31:320[GetAddr] find addr for host demo, server jRFS
May 05 18:06:31:320[GetAddr] looking for server jRFS by name
May 05 18:06:31:320[GetAddr] server using port 5001
May 05 18:06:31:320[GetAddr] provider is \dev\tcp
May 05 18:06:31:320[GetAddr] transport address : 020013890a00021b
May 05 18:06:31:320[ChkConnect] creating connect request info
May 05 18:06:31:320[ChkConnect] connect info Host demo, User Steve, Remote jrfsuser, Server jRFS
May 05 18:06:31:320[ChkConnect] connect ok, handle 248
May 05 18:06:31:320[Send] send data, fd 248
May 05 18:06:31:320[Recwait] receive message, fd 248
May 05 18:06:31:320[Send] send data, fd 248
May 05 18:06:31:320[Recwait] receive message, fd 248
May 05 18:06:31:320[Send] send data, fd 248
May 05 18:06:31:320[Recwait] receive message, fd 248
May 05 18:06:31:320[Send] send data, fd 248
May 05 18:06:31:320[Recwait] receive message, fd 248
May 05 18:06:31:320[Recmore] request more data, buffer 123
May 05 18:06:33:320[Send] send data, fd 248
May 05 18:06:33:320[Recwait] receive message, fd 248
May 05 18:06:33:320[Send] send data, fd 248
May 05 18:06:33:320[Recwait] receive message, fd 248
May 05 18:06:33:320[Disconnect] disconnect request, fd 248

jRFS Database Server Log File
May 05 18:10:19:476[Accept] client address
May 05 18:10:19:476[Accept] client name OMEGA
May 05 18:10:19:476[Accept] accepted on handle 224
May 05 18:10:19:476[Accept] CreateNewProcess to handle request, jRFS -i
May 05 18:10:19:476[Accept] CreateNewProcess successful
May 05 18:10:19:412[Accept] accept request using host , server jRFS
May 05 18:10:19:412[Accept] client address
May 05 18:10:19:412[Accept] client name OMEGA
May 05 18:10:19:412[Accept] accepted on handle 224
May 05 18:10:19:412[ChkAccept] checking connect request, Fd 224, Server jRFS, ClientHost omega
May 05 18:10:19:412[AccessChk] using jnetok access check
May 05 18:10:19:412[AccessChk] using network detected hostname omega
May 05 18:10:19:412[AccessChk] searching c:\jbase30\config\jnet_access for access string 'omega Steve jrfsuser jRFS'
May 05 18:10:19:412[AccessChk] access string found
May 05 18:10:19:412[AccessChk] Logging on user using Username jrfsuser, No Domain, Passwd ***
May 05 18:10:19:412[AccessChk] Result of LogonUser 1, error 183
May 05 18:10:19:412[AccessChk] LogonUser successful
May 05 18:10:19:412[AccessChk] Result of Impersonate user 1, error 183
May 05 18:10:19:412[AccessChk] Impersonate user sucessful
May 05 18:10:19:412[AccessChk] Now executing as user JRFSUSER
May 05 18:10:19:412[ChkAccept] security check passed
May 05 18:10:19:412[ChkAccept] umask set to 0
May 05 18:10:19:412[Environ] creating environment for client Steve, server jRFS, user jrfsuser
May 05 18:10:19:412[GetUid] getuid for user jrfsuser 
May 05 18:10:19:412[AccessChk] Successfully got info into Buffer
May 05 18:10:19:412[AccessChk] Home directory for user jrfsuser is C:\jbase30\jdp\demo
May 05 18:10:19:412[GetUid] established user jrfsuser, user directory C:\jbase30\jdp\demo
May 05 18:10:19:412[Environ] changed directory dir C:\jbase30\jdp\demo
May 05 18:10:19:412[Environ] set variable PWD=C:\jbase30\jdp\demo
May 05 18:10:19:412[Environ] set variable HOME=C:\jbase30\jdp\demo
May 05 18:10:19:412[Environ] set variable PATH=C:\JBASE30\bin
May 05 18:10:19:412[Environ] set variable LIB=C:\JBASE30\lib
May 05 18:10:19:412[Environ] searching C:\JBASE30\config\jnet_env for environment string 'ENV:jRFS jrfsuser Steve'
May 05 18:10:19:412[Environ] no entry found for environment string
May 05 18:10:19:412[ChkAccept] accept check successful
May 05 18:10:19:412[Recwait] receive message, fd 224
May 05 18:10:19:412[Send] send data, fd 224
Etc etc
May 05 18:10:21:412[DisconSeen] confirming disconnect, fd 224