Re: Stored Procedure/Powerbuilder - Permission Questions
1) If you use finderr -668, informix says :
-668 System command cannot be executed.
A system call failed in the operating system. The following
example shows a statement that might cause an error.
SYSTEM `hello';
To me this implies you do not have the correct UNIX permissions to run a
command, possibly the C routine, from a remote machice. See hosts.equiv etc.
2) again using finderr -648 yields :
-648 Cannot open DEBUG file for stored procedure trace.
An error occurred trying to open DEBUG trace file. This can
happen when one of the directories in the specified debug
file name does not exist, or the directory is write-protected.
Make sure that the directory path is valid and that group
informix is able to write to the directory.
This also points to a permissions problem, or possibly a path that is not
fully qualified.
Nick Nobbe wrote in article <5vl5mk$ft5@cssun.mathcs.emory.edu>...
>
>Alicia,
> I think you might want to try creating the SP on the server using
dbaccess.
>Yours,
> Nick
>
>On Mon, 15 Sep 1997, Alicia Slaughter wrote:
>
>}
>} Environment:
>} Powerbuilder v5.0 running on Windows NT v4.0
>} Informix - Online v7.21 running on a DG/UX vC2
>}
>} Question(s):
>} 1. I have some folks here trying to execute a system call that runs a C
routine within a stored procedure. they are
>} successful at running the stored proc from dbaccess but get a permissions
error when they execute from their Powerbuilder app. the SQL code -668 with
ISAM code -172. does anybody have any ideas what the cause might be?
>}
>} 2. this is sort of related to the first question, at least I think it is.
we have a standard set of debug code in all our stored procs that basicallly
allows you to generate a trace file (SET DEBUG FILE TO ...) by passing a
parameter to the stored proc.
> we have designated /tmp on our UNIX server as the directory where we would
like all these trace files to be written. however, we get SQL code -648 with
ISAM -13. this setup works fine if we execute the stored proc from dbaccess
but not from Powerbuilder