Welcome to jBASE's new documentation site! Many answers to your questions can be found by searching the Knowledgebase or viewing the jBASE Documentation. We also have a Google Group for peer discussion about jBASE. If you are unable to find the information you are looking for, jBASE Support will be glad to assist in resolving your technical problems. Enjoy and please provide comments and feedback .

How can we help you?

Migrating to jBASE: Overview


jBASE is a packaged set of tools, which provides support for MultiValue applications.

These tools enable legacy applications to move from being applications executing within rigid proprietary environments or operating systems to become native applications executing on one or more open platforms.

Once an application has been moved to jBASE, it then executes directly upon the base operating system, UNIX or Windows. All application main programs become either UNIX or Windows native executables, (Windows .exes) and all application subroutines become either UNIX .so files, shared libraries or Windows DLLs, dynamic linked libraries.

In addition jBASE provides full legacy application support for Visual Basic .NET, C#, Visual C++ and Java, via jRCS or jAgent. This enables legacy applications to be redesigned at the front end for presentation via a desktop or laptop in parallel with the original character based application, so that applicable legacy subroutines can continue to be utilized from both arenas.

Another advantage of jBASE is the capability to provide Multivalue applications with access to other databases, e.g. Oracle and DB2. This is possible because of the unique jBASE design which separates the application from the database, thus allowing an application to attain read/write access to many different database systems.

An interface is also provided to enable external applications to access any database, which is available to any jBASE application.


Migrating to jBASE
Installation (Windows) (Linux)
Installing jBASE
Environment Variables
Setting environment variables
Migration
Migration steps (Includes Video Tutorial)
Restoring Data (D3) (Universe)
Restoring legacy data into a jBASE environment
Emulation
Emulation settings
Data Conversion Converting legacy directories, files, programs, procs and MD items
PORTBAS
Migrating BASIC source code
Keywords
Compiler reserved words
Compilation
Compiling BASIC programs and subroutines
SYSTEM Functions
The jBASE SYSTEM function
Performance
Monitoring the performance of jBASE applications


OPEN SYSTEMS

  • Inter-operate in a non-proprietary way with other systems
  • Enable use of 3rd party hardware or software
  • Use industry standards where ever possible

 

PLATFORM INDEPENDENT

  • Most portable language is C, library code written in ANSI C.
  • Utilities have been coded in BASIC for ease and speed of maintenance.

 

ENVIRONMENT INDEPENDENT

  • jBASE does NOT sit between the application and UNIX or Windows.
  • The application executes directly upon the base operating system.
  • jBASE produces native machine executables and shared libraries UNIX.so, Windows .dll.
  • jBASE does NOT produce intermediate object code to be interpreted.
  • The application becomes a machine code executable. An application is just another executable or shared library that can then inter-operate.
  • No interim manipulation required to obtain access to the native environment.
  • jBASE applications can exploit the wide variation of tools provided on platforms, e.g. Source Code control, editors, windows applications.

 

DATABASE INDEPENDENT

  • Enable applications users to read and write from any database or device. For example, DB2 or ORACLE.
  • Release interface specifications and examples for coding drivers or application.
  • Provide tools to access SQL databases via embedded SQL.

Was this article helpful?