Re: I4GL licenses
Posted in 2006
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Licensing & Editions
Hi Obnoxio (and anybody who can help), thanks for the input. But my confusion prevails owing to the following reasoning: Once a developer has written a 4GL program and compiled and linked it into an executable, the executable is like any other executable that could have been written using C etc. and without using 4GL. I mean there is no distinction between executable coming from 4GL compile and link or otherwise. If the above is true, all I do while running the executable is access the library functions and set up a session with the Informix dynamic server. Consequently, running the executable should have nothing to do with I4GL licenses (development or runtime). Had it been RDS, runtime licenses were understandable because the execution would require the use of p-code runner which is a part of the RDS. But in the case of 4GL compiler, runtime licenses should have nothing to do with the running of the programs which the developers have written. Why, then as you say, should I need 20 runtime licenses for 20 users to run what the developers have written, compiled, linked and given to the users to run? As an analogy, if I developed an application with some other development environment (Microsoft Visual C++, say) using statically linked libraries and then deployed the executable to other machines for the users of the application to run, would I need to have some kind of runtime licenses for legally running the developed applications? Please clarify. thanks, Mrinal. On 12/30/05, Obnoxio The Clown <obnoxio@serendipita.com> wrote: > > Mrinal Kant said: > > I have a query regarding I4GL Compiler licenses. > > > > What is the difference between development and runtime (concurrent > users) > > licenses? That is, when are they required? > > > > As far as I understand, if I have 3 developers, each using 5 > simultaneous > > i4gl sessions, then I need 3 developer licenses and 3 X 5 = 15 runtime > > licenses. These figures should be independent of the number of users > that > > finally run the compiled executables. Am I right? Please help. > > If you have 3 developers, you need a 3-user developer license. If you also > have 20 users using what the developers write, then you also need a > 20-user runtime license. > > -- > Bye now, > Obnoxio > > "C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule" > - Coluche > > did i mention i like nulls? heck, i even go so far as to say that all > columns in a table except the primary key could/should be nullable. this > has certain advantages, for example, if you need to insert a child record > and you don't have a parent row for it, just do an insert into the parent > table with the primary key value (everything else null), and voila, > relational integrity is preserved. but this is, admittedly, a bit > controversial among modellers. > > --r937, dbforums.com >
Mrinal Kant <mrinal.kant@gmail.com> schrieb: >If the above is true, all I do while running the executable is access the >library functions and set up a session with the Informix dynamic server. >Consequently, running the executable should have nothing to do with I4GL >licenses (development or runtime). This is more a legal than a technical issue. I don't know whether there are any built-in checks that would keep you from exceeding your runtime licenses. However, the if you exceed the number of users defined in your license agreement, you are violating this agreement. Keep in mind that you also need sufficient licensing for the number of users accessing your database engine. Ask your sales representative about this. I have long stopped trying to understand the definition of "concurrent user". Regards, Richard