I heard that making program calls between Native MPE/iX "CI" and MPE/iX
"POSIX" was not supported by HP.

At another company we did this successfully, no problem. Then one minor
change the (POSIX compiled) "C" routine and nothing worked anymore. The
program was aborting because it was trying to access data outside it's
data stack.

A support call was placed after extensive debugging to find the cause
failed. HP said that POSIX routines and the regular MPE/iX routines
share the same data stack yet are not aware of each other, and will
randomly walk on each other's data in the data stack.  I don't have
access to the exact wording of the support call, any POSIX experts care
to comment?

If what I'm saying is true, then accessing "DB" Image calls may not be
very reliable, I dunno.

Does HP Support the calling of Image routines from POSIX?



>-----Original Message-----
>From:  Bob Walker [SMTP:[log in to unmask]]
>Sent:  Friday, October 10, 1997 5:03 AM
>To:    [log in to unmask]
>Subject:       Re: CGI to TurboImage
>
>[Anderson, Michael ]  SNIPPED to save resources--------
>
>With the old NCSA server we used a CI compiled program that was run
>with 'callci' and information passed back and forth through temp
>files.
>
>Now with Apache we have a more conventional cgi setup. C program is
>posix compiled, getting info from env variable QUERY_STRING
>and writing to stdout.
>
>And yes you can open an Image database from a posix compiled C
>program.  If you are a VESOFT shop, *DO NOT* use veopen
>in a program called directly from the posix shell. Your system will
>crash.
>
>Bob.
>
>--=--=--
>Bob Walker, Computer Centre  --  [log in to unmask]
>Capilano College, North Vancouver, BC, CANADA.
>------