Hello Tom,
First of all I would like to clarify a couple of things.
The manifest files are treated by conda as UTF-8 files. However, our manifests only contain single-byte UTF-8 characters - these characters form
a subset that is actually called ASCII, and this set of characters is identical in both UTF-8 and ISO8859-1 (and many other encodings). So, in a certain sense, our manifest files are
valid in
both UTF-8 and ISO8859-1. There's nothing in there that '
triggers UTF-8 character conversions', because UTF-8 conversion (or, rather, decoding) for manifest files happens
always.
That said, as long as conda reads manifest files as valid ASCII text, there will be no UTF-8 validation issues - valid ASCII text is always valid in UTF-8, too. For this to happen on USS:
(1) the file must be tagged according to the encoding of its contents, and
(2) the encoding itself must be eligible for auto-conversion - which limits us to ISO8859-1 and IBM-1047.
Looking at your output with the UTF-8 error, I can guess that (sorry, only a guess):
- The manifest file was copied to mainframe over FTP in text mode, which effectively converts the file from ISO8859-1 to IBM-1047. Binary mode is preferable since it retains the file's original encoding.
- You then changed the file tag to the code page 859, which is an alias for ISO8859-15, not ISO8859-1. Not sure where 859 came from; the Miniconda doc mentions 819, which is an alias for ISO8859-1. Now, ISO8859-15 is not eligible for automatic conversion, and so the manifest file was read 'as is', in its current IBM-1047 encoding. In this encoding, it's not a valid UTF-8, neither it is a valid ASCII, - hence the UnicodeDecodeError.
Now let's get back to your last message. I would like to reiterate what Tatiana
already said in the other thread: we do test our products on a live system ('QA' in her message stands for 'quality assurance'), and this includes the installation process. The manifest files published on the Rocket Community portal
can and
should be used 'as is'. Please verify your assumptions before giving other users bad advice like that.
Regards,
Vladimir
------------------------------
Vladimir Ein
Software Engineer
Rocket Software
------------------------------
Original Message:
Sent: 01-24-2022 16:52
From: Tom Longfellow
Subject: Still trying to get an install --- Weeks of frustration is building
Finally --- SUCCESS ---
The change to the BPXK AUTOCVT variable took me further. BUT a recommendation to others. Avoid installing the manifest files as downloaded. Something in there triggered Utf-8 character conversions when trying to install 'everything'
I pared back to the ones I needed and the install completed. Next will be some testing.
Thanks to everyone for their help.
------------------------------
Tom Longfellow
Senior Systems Programmer
Maryland Judicial Information Systems (JIS)
Annapolis MD US
Original Message:
Sent: 01-20-2022 15:39
From: Vladimir Ein
Subject: Still trying to get an install --- Weeks of frustration is building
Hello Tom,
Looking at your environment variables in one of the attached files, I can tell you're definitely missing some of the important ones.
First, there's no such thing as _BPX_AUTOCVT - the correct name is _BPXK_AUTOCVT (yes, both BPX and BPXK prefixes exist on z/OS, and are used for different parts of USS; they're not interchangeable of course).
Then, conda requires more than just _BPXK_AUTOCVT... The PDF doc provided with Miniconda (zOS Miniconda Documentation 1.2.1.pdf) explicitly states that:
Each end user who needs access to Miniconda should have following settings in a Bash startup file:
export _BPXK_AUTOCVT=ON
export _CEE_RUNOPTS="FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)"
. <miniconda_installation_path>/etc/profile.d/conda.sh
So you need the _CEE_RUNOPTS, too. Without these two variables, most of our Ported Tools aren't going to work properly.
--
Regards,
Vladimir
------------------------------
Vladimir Ein
Software Engineer
Rocket Software
Original Message:
Sent: 01-20-2022 14:37
From: Tom Longfellow
Subject: Still trying to get an install --- Weeks of frustration is building
Another day with no working results.
Ended up reinstalling from scratch. miniconda install worked (eventually --- but I am getting better at this)
Environment create says it works.
conda activate of the new environment worked.
conda install -c https://conda.anaconda.org/zoss-appdev zip unzip
Fails
with
bash: $'\025': command not found
Again - no clue as to what part of conda is producing the bash error or how I could find it or correct it.
Another damned brick wall
------------------------------
Tom Longfellow
Senior Systems Programmer
Maryland Judicial Information Systems (JIS)
Annapolis MD US
Original Message:
Sent: 01-20-2022 09:41
From: Tom Longfellow
Subject: Still trying to get an install --- Weeks of frustration is building
I am working with z/OS 2.4
I was using the manifest file in order to get all dependencies resolved in one pass.
You have given me some ideas
A) a newer manifest file. I think there is a newer one from Rocket
B) individual or small group installs of key products only.
Unfortunately, I have no clue which package is generating the bash character (unknown command) problem.
I have a vague recollection from earlier threads that if the 'wrong' level of python was in your PATH, bad things could happen. That is something else that will eat up my working days. What should be at most a two day project has been a burden to me since I started it over 3 months ago
------------------------------
Tom Longfellow
Senior Systems Programmer
Maryland Judicial Information Systems (JIS)
Annapolis MD US
------------------------------