Issue with using the "cl:" SQL prefix in db2i

[sriedmue79]

I'm trying to execute the example given here: https://codefori.github.io/docs/extensions/db2i/
-- run CL commands. output is directed to IBM i output channel
cl: dspffd sample/employee

I replaced the library/file with a valid one in my library, and the command works from the 5250, but from VS Code I get this result:
Statement executed with no result set returned. Rows affected: undefined

What I tried (based on messages previously in the joblog):
Set a valid OUTQ in my user profile
Set a valid printer device in my user profile

I'm not seeing any errors in the joblog now, but I still get the "Statement executed with no result set returned. Rows affected: undefined" message.

It does work with the CRTPF command, but any DSPxxx commands do not seem to work.

[sebjulliand]

Hi @sriedmue79 ,
I'm afraid the documentation is a bit misleading about how cl: redirects the output. Maybe it used to run the CL commands through Code for IBM i SSH channel, but not anymore since a while now. The messages logged by the command will be listed in the result set view, but that's it.

In this case, DSPFFD acts as usual: it prints the file's fields details into a spooled file named QPDSPFFD. If you have Matt Tyler's Spooled File Browser extension, you'll be able to display it from VS Code.

Every DSPxxx will act the same way.

[sriedmue79]

Many thanks Sébastien Julliand. I am totally ok with this, as it's similar to the Run SQL Scripts behavior. When I saw the example "cl: dspffd" I was prepared to be very impressed! I would not expect DSPxxx command output to be returned in this UI, but the example seemed to suggest that it would be! Maybe a different example command should be used. Anyway, thanks again!