Closed kadler closed 6 years ago
Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).
remote ... qsh ls -l (laptop db2procjr)
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.
#!bash
=============================
test5000_sql400json_procjr64 ../json/j0361_cmd_qsh_ls
=============================
input(5000000):
{"cmd":{"qsh":"ls -1 /QOpenSys"}}
output(855):
{"script":[{"cmd":["ls -1 /QOpenSys",
{"records":[
{"R1":"QIBM"},
{"R2":"QOpenSys"},
{"R3":"QOpenSys.bak"},
{"R4":"QSR"},
{"R5":"austin"},
{"R6":"austin.20180129.105931.tmp"},
{"R7":"austin.20180129.105949.tmp"},
{"R8":"bin"},
{"R9":"builder"},
{"R10":"cert"},
{"R11":"cert.crt"},
{"R12":"cert.key"},
{"R13":"cert.p12"},
{"R14":"certificate.p12"},
{"R15":"certificate.pem"},
{"R16":"chroot1"},
{"R17":"db2sock"},
{"R18":"dev"},
{"R19":"etc"},
{"R20":"git"},
{"R21":"git.env"},
{"R22":"git.job"},
{"R23":"git.log"},
{"R24":"home"},
{"R25":"jenkins"},
{"R26":"lib"},
{"R27":"lib64"},
{"R28":"mydebug.txt"},
{"R29":"new_chroot"},
{"R30":"node4"},
{"R31":"node6"},
{"R32":"opt"},
{"R33":"pkgs"},
{"R34":"ranger"},
{"R35":"sbin"},
{"R36":"tmp"},
{"R37":"tools"},
{"R38":"tools-internal"},
{"R39":"usr"},
{"R40":"vac101"},
{"R41":"var"},
{"R42":"yum"},
{"R43":"yum2"},
{"R44":"zend5"},
{"R45":"zend7"}]}]}]}
result:
success (0)
Original report by Jesse G (Bitbucket: ThePrez, GitHub: ThePrez).
I encounter a JSON parsing error when trying to run QSH commands via "CALL DB2JSON.DB2PROCJR(?)"
Position 62 seems to be the first newline, but there seem to be issues beyond that, with "R2" (row 2) starting mid-row on later records
The following is the actual result of running this command in an SSH terminal: