Re: 4GL Debugger ver. 4.14 bug

We had the problem with 4.14UC1 on a RUN with RETURNING statement coring. Informix has since sent us a patch for this problem (verson 4.14UC1X1 for SUN Solaris 2.4). But when we installed the patch, the get_fldbuf() function within a CONSTRUCT statement quit working (I think it gave us a runtime error). I think they are still working on that one. ------------------------------------------------------------------------------- Shelly Whittington | ######## ####### ConferTech shelly@cfer.com | ### ### International |##### ### Inc. Standard disclaimers apply... |############ ## Westminster, CO ------------------------------------------------------------------------------- } } > Data Missing } > } > This document resulted from a POST operation and has expired from } > the cache. If you wish you can repost the form data to recreate the } > document by pressing the reload button. } 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 } } } 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. } } } 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. } } }