System Builder to OSMOSiS Conversion

How Does it Work?

The system converts the Dictionary and/or Data of every file in the SB source account and creates the equivalent files in the ‘new’ OSMOSiS account. The SB Dictionary holds all SB field definitions, OE fields, screens and prints, which are copied to OSMOSiS files.

The resulting converted files are split so that the file’s dictionary contains the OE definitions, the _DICTS,filename contains the OSMOSiS definitions (converted from SB), the _DISPLAYS,filename contains the screen definitions and the _PRINTS,filename contains the print forms and/or reports.

The System Builder Conversion Process

System Builder Files











xxCONTROL records are converted to various files:

Menus are converted to _MENUS.
Generated numbers are converted to _GENNO.
xPASSWORD is converted to _PASSWORD.

During the conversion process, any SB defaults, validations, correlatives and conversions are recorded in BOTH SB and OSMOSiS formats.

This enables developers to continue with their familiar formats and the items are converted at the time of entry into OSMOSiS formats for run-time execution.

Finally, any file named xxUFO or xxPROGS, where xx is the SB system id., will be treated as a program file together with any that the operator specifies separately.

Each program’s code convert to use the OSMOSiS COMMON area and the OSMOSiS subroutines that correspond to COMMON variables and routines in SB. These files will be compiled and catalogued ready for use in running the application.

After the System Builder conversion

Once the conversion process is complete, the OSMOSiS account’s logon is attempted and the Password and User Id are requested. Upon a successful logon, the “MAINMENU” is displayed, which is the list of original SB ‘systems’.

OSMOSiS does NOT work with ‘systems’ and therefore during the conversion menu names are created which are prefixed with the SB system parameter, e.g. SALESMENU in a SB system id of AC will become ACSALESMENU. Similarly, transactions will be prefixed with the SB system id for the file that the transaction was converted from.

OSMOSiS does NOT allow field names that contain full stop, comma, plus, star, slash, minus or equals. Underscore is the most commonly used delimiter that is permitted in OSMOSiS. During the conversion process it was recognised that many SB applications use any (and most) delimiters in field names. OSMOSiS allows the continued use of these fields, as is, BUT new fields cannot be defined with the restricted delimiters within their id.

The resulting application will have the same files, fields, screens, prints, reports, menus, updates, passwords and generated numbers as the original. The contents of each database element will be the same but will be formatted differently and will reside in OSMOSiS 4GL files. Some names will have changed.

The data file’s dictionary will only contain the OE definitions for the file. Defaults, Validations, Correlatives and Conversions will be visually identical to those in the original SB application. Developers can continue to use these same formats that are so familiar to them and OSMOSiS will take care of making it a OSMOSiS formatted statement, invisible to the developer.

Now the application can move forward into the Client/Server Windows environment by running the same character screens in the OSMOSiS Windows system.

The final application can be operated in Character and Windows GUI modes and if required in a combination of both, even on the same screen. 

<< Back


Copyright 2015 SC Systems Ltd.  SC Systems is a member of the Mpower1 Group of Companies.
Privacy and Cookie Policy