Re: [IBMiOSS] Python, ACS, Open Source and MKDocs

If you are going to go in through the green screen, it's always going to be
problematic.
Once you start going in through ssh (PuTTY is an SSH client) your IBM i
becomes a lovable if slightly clunky *nix box.
Once you have committed to that path, you change your shell using IBM Db2
for i services (SQL), e.g., via "Run SQL Scripts" in iACS:

*call qsys2.set_pase_shell_info('JWOEHR', '/QOpenSys/pkgs/bin/bash');*

and thereafter your login shell, whether from ssh or greenscreen, is bash.
This will suck badly in greenscreen, so you cross the Rublcon here, but you
will not regret it if your plan is to progress with PASE.

You'll want to set up a

- .bash_profile
- .bashrc #optional
- .bash_aliases #optional

Here are some examples from one of my machines. YMMV

$ cat .bash_profile
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

$ cat .bashrc
JAVA_HOME=/QOpenSys/pkgs/lib/jvm/openjdk-11
PKGS=/QOpenSys/pkgs
PATH=$HOME/bin:$JAVA_HOME/bin:$PKGS/bin:/QOpenSys/usr/bin:/
usr/local/bin:$PKGS/lib/nodejs12/bin
export JAVA_HOME PATH

TERM=xterm
export TERM # these two lines set your terminal nicely for most ssh clients
export LC_ALL=EN_US.UTF-8 # locale char set ... PASE is not EBCDIC
export PS1='\u@\h:\w\$ ' # sets your prompt nicely

# ~/.bash_aliases, instead of adding them here directly.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

export OBJECT_MODE=64 # This is for compiling C/C++ code under PASE