Why is uname coming back blank from stored proc call?
Issue #20
resolved
Other commands (tested echo, ls) seem to work, but uname comes back empty. Fully-qualifying uname to /QOpenSys/usr/bin/uname or /usr/bin/uname do not seem to make a difference. "-a" also renders a blank result.
***********************************************
*****uname:
***********
in:
{"script":[{"cmd":{"qsh":"uname -s"}}]}
********************
output:
{"script":[{"cmd":["uname -s",{"records":[{"R1":""}]}]}]}
****************************************************
Comments (2)
-
Account Deleted -
reporter - changed status to resolved
Verified. Closing. Thank you!
- Log in to comment
Ok, fix for remote via db2procjr (laptop).
Generally, stored procedure db2procjr path was intended for remote development. Not an async interface. Many CCSID, other problems, slow, etc. Should work, but not tested much by me. Thanks for help.