Re: database engine

>From: uunet!sun419.nas.nasa.gov!jcarter (John R. Carter Sr.) >Message-Id: <1992May11.194247.10863@nas.nasa.gov> >Subject: Re: database engine >Date: 11 May 92 19:42:47 GMT >X-Informix-List-Id: <news.1233> >Article <8894@emory.mathcs.emory.edu>, ar@valstr.uucp (Andrew Roberts): >|>>Article <8881@emory.mathcs.emory.edu> Doimic01@saad-emh1.ARMY.MIL: >|>>>2) Is it possible to write a stand-alone Informix 4gl/esql-C application >|>>> that can be ported from one machine (same model, of course) to another, >|>>> without Informix on the second machine? I know the answer to this (NO!), >|>> >|>> Yes. The run-time module costs about half of the development version. >|>> And it doesn't have to be the same model as long as you recompile >|>> the application with the run-time module for the target system >|>> (same for dBase by the way). >|> >|> Do you know something about the run-time module that I don't? I use >|> ESQL-C on an HP 9000, and I know for a fact that you don't get the >|> preprocessor with the run-time module, so you can't recompile; and >|> you don't get the sql libraries either, so you can't even relink. >|> The machines have to be executable code compatible. > >I just had a look at the price sheet. We spent several minutes in a meeting >deciding whether to get a run-time module or stay with the development >module in its entirety. Since we never expect to port a standalone version >of our application the decision was easy. >Maybe we're interpreting the price sheet wrong? Maybe I can help muddy the waters -- sorry, I mean clarify the situation. There are three sets of development environment to consider, the C-based ones (ESQL/C and Informix-4GL), the P-code ones (Informix-4GL RDS & ID), and Informix-SQL. Additionally, you need to consider the database engines, since they are bought separately. Rule-of-thumb: if you are going to compile application code on a particular machine, you need development licences. If you are only going to run application code developed on a different machine, you only need run-time licences. Custom runners only require run-time licences. ENGINES: You need an engine licence for each machine which runs an engine. If the engine is ever used by a development system, you need a develpment engine; otherwise, you only need a run-time engine. End of story -- that was easy. INFORMIX-SQL: If you want to modify a form or report on the target machine, you need a development copy of ISQL (because you won't get the form/report compilers if you buy the run-time). What about customised runners for forms/reports? Assuming they are bundled with the ISQL product (correct for 4.10), then the tools needed to build the runners are available with the run-time, so you can port your forms and reports from Machine Type A to Machine Type B, and re-create the custom runners on Machine Type B. Machine Type B had better have a compiler on it. If not, you are stuck until you do get one! Prior to Version 4.10, you needed ESQL/C to get the customising facilites. If you only needed the custom runners, an ESQL/C run-time licence was sufficient. INFORMIX-4GL RDS & ID: There is no such thing as a run-time version of ID -- it is a development tool only. An application developed using I4GL-RDS is portable to a second machine which has an I4GL-RDS R/T licence. If the hardware is different and a custom runner is required, then you can create a custom runner on the target hardware with the contents of the run-time system -- again subject to having a C compiler on the target hardware. (Why this emphasis on having C compilers? Because some versions of Unix (Xenix, Solaris to name but 2) do not necessarily provide a C compiler as standard.) The target machine will not be able to modify forms or programs if it only has a run-time licence. INFORMIX ESQL/C and INFORMIX-4GL: If you want to port an application from Machine Type A to Machine Type B, someone, somewhere, is going to need a development licence for Machine Type B as well as the one for Machine Type A. On Machine Type B, providing there is no compilation to be done, you only need a run-time licence. I hope this helps, Jonathan Leffler (johnl@obelix.informix.com) #include <disclaimer.h>