Next, I tried the install of MKDocs using pip3, and I got an error which
makes no sense to me:
-bash-4.4$ pip3 install mkdocs
Collecting mkdocs
Downloading
https://files.pythonhosted.org/packages/5d/89/ed04b217404bbba031c4e2e084f36ef840b8663fce0b80302b547e651e4d/mkdocs-1.1.2-py3-none-any.whl
(6.4MB)
100% |################################| 6.4MB 118kB/s
Collecting PyYAML>=3.10 (from mkdocs)
Downloading
https://files.pythonhosted.org/packages/64/c2/b80047c7ac2478f9501676c988a5411ed5572f35d1beff9cae07d321512c/PyYAML-5.3.1.tar.gz
(269kB)
100% |################################| 276kB 1.1MB/s
Collecting Jinja2>=2.10.1 (from mkdocs)
Downloading
https://files.pythonhosted.org/packages/30/9e/f663a2aa66a09d838042ae1a2c5659828bb9b41ea3a6efa20a20fd92b121/Jinja2-2.11.2-py2.py3-none-any.whl
(125kB)
100% |################################| 133kB 1.3MB/s
Collecting click>=3.3 (from mkdocs)
Downloading
https://files.pythonhosted.org/packages/d2/3d/fa76db83bf75c4f8d338c2fd15c8d33fdd7ad23a9b5e57eb6c5de26b430e/click-7.1.2-py2.py3-none-any.whl
(82kB)
100% |################################| 92kB 1.3MB/s
Collecting livereload>=2.5.1 (from mkdocs)
Downloading
https://files.pythonhosted.org/packages/bd/60/6640b819e858562ef6684abac60593b7369fe0a8a064df426d3ab0ab894d/livereload-2.6.3.tar.gz
Exception:
Traceback (most recent call last):
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/_vendor/pkg_resources/__init__.py",
line 2610, in _dep_map
return self.__dep_map
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/_vendor/pkg_resources/__init__.py",
line 2685, in __getattr__
raise AttributeError(attr)
AttributeError: _Distribution__dep_map
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/basecommand.py",
line 209, in main
status = self.run(options, args)
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/commands/install.py",
line 310, in run
wb.build(autobuilding=True)
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/wheel.py",
line 748, in build
self.requirement_set.prepare_files(self.finder)
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/req/req_set.py",
line 360, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/req/req_set.py",
line 647, in _prepare_file
set(req_to_install.extras) - set(dist.extras)
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/_vendor/pkg_resources/__init__.py",
line 2810, in extras
return [dep for dep in self._dep_map if dep]
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/_vendor/pkg_resources/__init__.py",
line 2624, in _dep_map
dm.setdefault(extra,[]).extend(parse_requirements(reqs))
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/_vendor/pkg_resources/__init__.py",
line 2980, in parse_requirements
"version spec")
File
"/QOpenSys/QIBM/ProdData/OPS/Python3.4/lib/python3.4/vendor-packages/pip/_vendor/pkg_resources/__init__.py",
line 2945, in scan_list
raise RequirementParseError(msg, line, "at", line[p:])
pip._vendor.pkg_resources.RequirementParseError: Expected version spec
in tornado;python_version>"2.7" at ;python_version>"2.7"
-bash-4.4$
On 12/18/2020 9:28 AM, Joe Pluta wrote:
Okay, I got rid of my .profile and did nothing other than call
set_pase_shell_info. Now, if I come in through SSH, echo $0 returns
-bash, while in QSH it still returns the original QSHELL/QZSHSH.
That's an interesting turn of events.
Then I checked your .bashrc and I see references to openjdk-11 and
modejs12, neither of which I find in my /QOpenSys folders. In ACS, I
see that I can install various flavors of nodeJS, but I don't see a
JVM. So while I'm getting closer, I still don't see a path to getting
to your configuration just yet.
On 12/18/2020 8:25 AM, Jack Woehr wrote:
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
midrange.com
