Why is uname coming back blank from stored proc call?

[kadler]

Original report by Jesse G (Bitbucket: ThePrez, GitHub: ThePrez).

---

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":""}]}]}]}

****************************************************

[kadler]

Original comment by Jesse G (Bitbucket: ThePrez, GitHub: ThePrez).

---

Verified. Closing. Thank you!

[kadler]

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

---

remote ... uname -s (laptop db2procjr)

Ok, fix for remote via db2procjr (laptop).

• Yips Super Driver - test driver - 1.1.2-sg9 - remote db2procjr various differences (Jesse G.)

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.

#!bash

=============================
test5000_sql400json_procjr64 ../json/j0362_cmd_qsh_uname
=============================
input(5000000):
{"cmd":{"qsh":"uname -s"}}

output(62):
{"script":[{"cmd":["uname -s",{"records":[{"R1":"OS400"}]}]}]}

result:
success (0)