As a transitional step to BBj, PRO/5 and Visual PRO/5 interpreters can continue to be deployed while gaining access to the advanced features of the BASIS DBMS.
This is achieved without any application code changes by:
- For PRO/5 via the memory-mapped file protocol which, without any code changes or data conversion, can leverage all of the features and benefits of the BASIS DBMS.
- For Visual PRO/5 it’s as simple as changing from the PRO/5 Data Server to the BBj P5 DS Server.
- During this transition, all three components can co-reside. PRO/5, Visual PRO/5, and BBj interpreter sessions can simultaneously interact with the BASIS DBMS.
PRO/5 and Visual PRO/5 applications can reach out and consume BBj code via the XCALL verb for specific functionality that doesn’t exist in the PRO/5 family.
It is noteworthy that during testing, the BASIS DBMS can be easily switched on and off thereby allowing developers to easily step forward and back again.
A single BASIS license supports any and all of the three language interpreters and supports the ability to mix and match them.
New PRO/5 and Visual PRO/5 development is generally limited to three areas; providing security patches to the product, supporting newer operating system platforms, and ensuring seamless interoperability with BBj.