Modifying Programs to Access the Data Server

The ease in modifying programs to access the Data Server is dependent on the current programming standards, as follows.

If the program's file search paths are set via PREFIX statements or path variable, all that may be required is a simple modification to the PREFIX statement or the line of code that defines the path variable, as illustrated in the following two examples:

PREFIX Modification Example	Path Variable Modification Example
prefix "/<server>u/path/data/" open(1)"myfile"	path$="/<server>u/path/data/" open(1)path$+"myfile"

Secure Sockets Layer (SSL) will need to be included in the server name field if the data server is configured to use SSL, as shown in these examples:

PREFIX Modification Example	Path Variable Modification Example
prefix "/<server,ssl>u/path/data/" open(1)"myfile"	path$="/<server,ssl>u/path/data/" open(1)path$+"myfile"

If the program's file search paths are set via hard-coded paths, relative path names, or drive parameter, or the program dynamically changes the PREFIX, the conversion can be considerably more difficult. The effort involved depends on the number of programs to be modified, the number of contained OPEN statements, the file open methodologies, the degree of consistency between programs, and perhaps most important, the modifier's familiarity with the code.

To use the Data Server with a BASIS data dictionary, add the following to the data dictionary config.tpm file:

USERID=user_login

where user_login is the remote server login.