On Fri, Dec 13, 2019 at 9:10 AM Smith, Mike <Mike_Smith@xxxxxxxxxxxxxxxx>
wrote:
I do often use Putty, but don't do bash. I'm not sure what it really is
or what it does for me(topic for another day I suppose)
Putty is a Windows rubber-bumper version of SSH. That's perfectly adequate.
When you log into a Unix environment, there has to be some kind of command
interpreter loaded.
The default command interpreter is limited. You probably want
/QOpenSys/pkgs/bin/bash *if you knows what's good for you, pal!*:)
In the iAccess "Run SQL Scripts":
call qsys2.set_pase_shell_info('MSMITH', '/QOpenSys/pkgs/bin/bash');
with my user level profile I only see python 3.4.6
On my QSECOFR level I see python 3.6.9
Different paths.
$ ls -l `which python3`
lrwxrwxrwx 1 qsys 0 18 Nov 9 01:05 /QOpenSys/pkgs/bin/python3 -> python3.6
Once your shell is set to bash, you need a .bash_profile file in your root
directory and .bashrc file, e.g.
$ cat .bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
$ cat .bashrc
PKGS=/QOpenSys/pkgs
PATH=$HOME/bin:$PKGS/bin:/QOpenSys/usr/bin:/usr/local/bin:$PKGS/lib/nodejs12/bin:$PATH
export PATH
TERM=xterm
export TERM
export LC_ALL=EN_US.UTF-8
export PS1='\u@\h:\w\$ '
# ~/.bash_aliases, instead of adding them here directly.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
Your settings will vary, e.g., LC_ALL
The aliases file is of course optional .. I have several aliases defined in
min.
midrange.com
