Re: QSHELL SED insert

Hmmm. We really want the standard i/o stuff and to use our ide (anaconda3) where we can walk thru the code.

doable?

No problem mapping a drive to a folder on the IFS and loading a .py pgm.

We can't "run" it on the windows pc because we aren't in the Qshell on the I.

Pray tell how.

Thx,

Jerry

On 10/19/2020 4:48 PM, Jack Woehr wrote:

On Mon, Oct 19, 2020 at 4:20 PM Jerry Draper <midrangel@xxxxxxxxxxxxx>
wrote:

We have lots of CL pgms calling QP2BATCH to shell out and run sFTP and
other BASH scripts.

That sort of thing is the proper use of the Q stuff w/r/t PASE.

To test these scripts we get into *IX using QP2TERM. It's convenient.

It also makes it hard to develop and debug.


- Your scripts can't do normal standard i/o stuff because the Q stuff
lacks tty control
- Tools such as editors which are integral to the development
methodology of these new languages you are exploring will run in PASE but
not in a Q term.
- It's easy to get confused which version of what program you are
calling if you aren't in an easy-to-use shell environment.

To move forward in the open source world you want to:

- Learn ssh thoroughly
- Learn to use the shell including editing the configuration files
- Learn to mount your IBM i IFS onto your development workstation via
sshfs
- Learn to use tools we all use like
- mc
- modern editors/IDEs either
- running on IBM i and outputting via X windows, or
- running on local workstation and accessing your disks that you
mounted via sshfs
- git for versioning
- vim for quick edits

.. and a host of other tools and techniques. Onwards!!

Of course, if you're *happy right where you are now*, ignore all this ....
But if you find yourself saying, "If I could just do *one more thing*,"
then you are hooked and it's time to learn this stuff.