> -----Original Message-----
> From: Geoff Worboys [mailto:geoff@...]
> Sent: Jueves 18 de Enero de 2001 3:33
>
> I have not looked at ibase.h from the Firebird source. IBOs
> IB_Header.pas file was taken from the old IB5.x header and the service
> enumerations...
>
> isc_info_svc_version = 4;
> ...
> isc_info_svc_get_env_msg = 24;
>
> are not valid for IB6.
>
> The version of ibase.h that was released with IB6 (from borland) has a
> rather different set of values...
>
> isc_info_svc_svr_db_info = 50;

[snip]
Please add the vales you listed. We need them if something has to be done
and even if it's not done, they can help for people that wants to write to
the API.

> Needless to say, I discovered this the hard way! These are a
> different set of enumerations to the isc_action_svc_* series, which
> are not currently in the IB_Header unit at all (but they can soon be
> added).

Consider adding them ASAP, they can't hurt, Geoff, please.

> I dont know if the old isc_info_svc_* series had any use with pre-IB6
> releases. If anyone is using these values let me know, because I have
> simply removed the old definitions (not used in IBO) and put in the
> new IB6 series.

They has use. Some day I will post at my site the history of the Services
API. Certainly it was present on IB4, but undocumented... how do you think
Server Manager did its tricks? When I asked Borland for more info at that
time, I received complete silence. I knew that isc_service_attach was
present (see the remote.dll in IB4.0C for Win311) but I didn't have any clue
on how to use it. Some Russian person wrote that the way was to call one
action by writing a value to a DPB (that corresponds to one command like
gbak) and append a string with the parameters to the API; the same
parameters that you would pass to gbak from the command line, for example
"-b -v". There was not specialized DPB for those actions, etc. The thing
remained unchanged for IB5 and Borland only added the three functions to
deal with user management.

I'm in favor of implemented different components for the specialized
services. Having a fat interface with 40 unrelated calls makes me look at
the bed immediately.

I also can add a service component named IBO_crush (to kill the server) and
IBO_backdoor (to test for unsecure installations)... just kidding. :-) And
you think that the closed backdoor is all the story? Just wait some weeks...
oh, I'm outspoken this evening!

C.