Subject | Re: [firebird-support] Re: End user repair utility - assuming the worst-case. |
---|---|
Author | Ann W. Harrison |
Post date | 2011-01-19T21:38:53Z |
On 1/19/2011 2:07 PM, homerjones1941 wrote:
interface. It probably gives status codes on the results of
runs. Perhaps someone has fixed all the utilities to return
the right status on the right operating system. In the ancient
days when InterBase ran on VAX/VMS, Ultrix, Apollo Aegis, whatever
DG Unix was called, AIX, HP-UX, and a few others, getting the
right error codes on the right operating system was an overwhelming
chore and never got done.
Ann
> There are a few places where you say: Do "A". If "A" fails do "B". If "B" works, do "C." Is it possible for a Delphi program to determine failure or success of the steps you've outlined, or does this actually require human intervention? For example, can my program parse some kind of log file and then act accordingly?Probably the sane way to handle that is through the services
interface. It probably gives status codes on the results of
runs. Perhaps someone has fixed all the utilities to return
the right status on the right operating system. In the ancient
days when InterBase ran on VAX/VMS, Ultrix, Apollo Aegis, whatever
DG Unix was called, AIX, HP-UX, and a few others, getting the
right error codes on the right operating system was an overwhelming
chore and never got done.
> Perhaps a parallel, more specific, question is: When I run gfix -v -n, is there a way to get the result such that I can parse it? I've tried a simple pipe into a .TXT file, but my syntax may not have been correct.Hunh. -z used to print out the version information...
> gfix -z -u<username> -p<password> <Database> |<destination file>
> BTW, I used -z because -i -v produced no result. I assume that was because my database was okay.Cheers,
Ann