Re: 4GL Debugger ver. 4.14 bug

> I called up Informix with a problem. When I use the RUN RETURNING > statement in my 4GL code to run a unix script, it returns nulls for my > returning values. This is a known bug to Informix ( they actually said it > would core dump), their suggestion was--do not use the RETURNING on the > RUN statement. I need to return values. Does anyone have a work around > to this bug? Ideas that I thought of, but was not sure how to implement, > were: > > 1) Write a C program that runs str where str would be any unix script > command that I may need and return the value of that the unix script > returns, and then use the CALL RETURNING (because call returning does > return values) in 4GL. Example: > > str = move_file /usr2/test.txt -- unix script > call_scripts(str) -- C program > and then in my 4GL code have CALL call_scripts(str) RETURNING > unix_stat This is the approach that I take. In the C function, I use the "popen" call to catch the return status of a command that I want to execute and then pass it back to 4GL. > 2) Use the RUN with no RETURNING and have all my unix scripts write to > a unix_stat file. Then read the unix_stat file and erase it using 4GL.-- > No idea how to implement. This will, probably, also involve some C or UNIX shell interface. > 3) Downgrade to an older version....not sure if the bug exist in any > older versions between 4.10 - 4.14. There is not upgrade for an HP 9000 > K200 with HP/UX 10.0. Hope this helps. Cheers, -Atul.