At 12:22 PM 29/01/2004 +1000, you wrote:

>I am doing up an installation script for linux and windows to be used in
>an InstallAnywhere installation. The problem I am facing is that I
>sometimes receive a error message after installing and starting the
>service, when attempting to create a database. The message is:
>
>Use CONNECT or CREATE DATABASE to specify a database
>Statement failed, SQLCODE = -904
>
>unavailable database
>
>I tried adding the -b option to the instsvc start command which worked
>if I had some file actions between starting the service and attempting
>the create database command (a big enough delay). I need a way to force
>instsvc start to not return until it has started the database service or
>a way of telling the create to wait until the service has started. I can
>not rely on the service taking x amount of time to start.
>
>Any help would be greatly appreciated,

You can't control Windows - it pleases itself about how long it takes to up
the service. As far as the client is concerned, no service means
unavailable database.

But your application's connection procedure can easily intercept the
"unavailable database" message in a while-not loop, with a timeout
loop-breaker in case connect errors come from network or other external faults.

/hb