This document outlines the process used to configure the PRO/5 TCP/IP client to access files through the PRO/5 Data Server. It does not contain the specifics of installing the TCP/IP stack and relies on the TCP/IP layer working; see Troubleshooting PRO/5 Data Server TCP/IP Connections.

1. Install and license the products according to their instructions. Specific installation instructions for different PRO/5 Data Server OS platforms are documented in the PRO/5 Data Server Guide.

   Prior to Feature Release 2.10 of our product, the PRO/5 Data Server is installed on the server, and a single-user Visual PRO/5 TCP/IP client is installed on each Windows workstation. Due to the nature of BASIS' TCP/IP client/server connection to the Data Server, each PC must have its own TCP/IP address and unique Visual PRO/5 serial number.

   For Feature Release 2.10 and above, the PRO/5 Data Server is installed on the server. Starting with this release, the client can either be a single-user or multiuser Visual PRO/5. Visual PRO/5 can be installed either on the local workstation or on a common mapped drive. Due to the nature of BASIS' TCP/IP client/server connection to the Data Server, each PC must have its own TCP/IP address.

2. Modify the services file to include an entry for the Data Server. This entry is the PRO/5 service name, and the following defaults are recommended:

     pro5srv  1100/tcp  # PRO/5 Data Server
   

   The services file will need to be modified on the machine on which the Data Server is running as well as every workstation on which the client is running. The following shows typical locations for the services file.

   Operating System	Services File Location
   UNIX	/etc/services
   Windows 95	\windows\services
   Windows NT	%SystemRoot%\system32\drivers\etc\services

   Note: %SystemRoot% is the drive and root directory where NT was loaded.

3. Verify that all workstations and the server name and IP addresses are in the server's hosts file.

   Note: If problems occur resolving workstation and server names to IP addresses, it may also be necessary to create a hosts file with the same information on each workstation. Refer to Step 4 in Troubleshooting PRO/5 Data Server TCP/IP Connections.

   < li>Start the Data Server with logging enabled. This example will invoke the Data Server, force it to use port 1100, and log all activity to the file named ds.log in the Data Server's directory. Note that it is not necessary to specify the port, but it can be helpful for testing purposes to rule out problems with the services file mentioned in Step 2.

   UNIX Data Server:

     ./pro5.server -r -l./ds.log -p1100
   

   NT Data Server Revision 2.03 and lower:

     C:\BASIS\NTDS\pro5srv.exe -r -l./ds.log -p1100
   

   NT Data Server PRO/5 Revision 2.04 and higher:

   The PRO/5 Data Server for Windows NT Revision 2.04 and higher is designed as a Windows NT Service. To accommodate the differences, the required steps to set up and start the Data Server with logging enabled are:

   1. From the Windows Start menu, open the Control Panel.
   2. Execute the PRO/5 Data Server applet. (This applet sets the parameters contained on the command line in previous releases.)
   3. Select the checkbox next to Enable Event Logging.
   4. Click on the Apply button to accept changes.
   5. Close the window and return to the Control Panel.
   6. Open the Services window, highlight the PRO/5 Data Server in the list and click Start. Note that the Startup Parameters line in the Services window does not have any effect on the PRO/5 Data Server.

4. The

   setopts

   bit for Data Server access must be enabled to open files through the Data Server. To set byte 4 bit

   $20$

   for Data Server access in Visual PRO/5 at the console prompt, enter the following:

     >LET A$=OPTS
     >LET A$(4,1)=IOR(A$(4,1),$20$)
     >SETOPTS A$
   

5. Verify that you have enabled the Data Server access bit

     >LET A$=OPTS
     >IF AND(A$(4,1),$20$)=$20$ THEN PRINT "enabled" ELSE PRINT "disabled"
   

   If the bit does not stay set, you are not running the TCP/IP client version of BBx or PRO/5. We suggest permanently setting the

   setopts

   bit in the

   config.bbx

   file. The following example sets only the Data Server access bit:

     SETOPTS 00000020
   

6. Open a file via the Data Server by executing the following from a Visual PRO/5 client:

   UNIX Data Server:

     >OPEN(1) "/<server_name,port=1100>/etc/services"
   

   NT Data Server:

     >OPEN(1)"/<server_name,port=1100>
     %SystemRoot%\system32\drivers\etc\services"
   

   Note: For %SystemRoot%, substitute the drive and root directory where NT was loaded.

   This is a good example for two reasons:

   1. The services file should be there, and all users should have adequate permissions to read the file.
   2. The port=1100 forces the port selection, bypassing potential problems with the services file in specified in Step 2.

7. Try the following if the first file open was successful:

   UNIX Data Server:

     >OPEN(1) "/<server_name>/etc/services"
   

   NT Data Server:

     >OPEN(1)"/<server_name>%SystemRoot%\system32\drivers\etc\services"
   

   If this works, you're in business! Otherwise, a problem may exist with the services file in Step 2. Please refer to Troubleshooting PRO/5 Data Server TCP/IP Connections for additional information.

Your programs must use a special syntax for accessing files through the Data Server. The file name begins with a forward slash and the name of the server is in angle brackets:

  OPEN(1)"/<server_name>/u/path/filename"

The difficulty in converting your programs to access the Data Server depends largely on how they are currently structured. For example, if your programs rely on the PREFIX or a path variable to determine where the files are located, the conversion process can be simple. All that may be required in this case is a simple modification of your PREFIX or the line of code that defines your path variable.

Some examples are:

  0010 PREFIX "/<server>/u/path/data/"
  0020 OPEN(1)"myfile"

or

  0010 PATH$="/<server>/u/path/data/"
  0020 OPEN(1)PATH$+"myfile"

If your programs specify a full path, relative pathnames, drive parameters, or change the PREFIX dynamically, the conversion process will require more effort. The level of difficulty is directly related to the number of programs you must modify, how many OPEN statements they contain, methodologies used for file opens, degree of consistency between programs, and perhaps most important, your familiarity with the code.