Rocket has moved to a new system – conda – for downloading, installing, and upgrading all z/OS open source ports developed by Rocket.  With conda, a single command can replace dozens of steps and commands previously required to install some open source products.  For example, installing z/OS Git with its dependencies formerly required over thirty steps but now can be accomplished with a single conda command.

Conda is an open source tool ideally suited for delivery and deployment of software on the mainframe due to its channel concept and multiple types of channels supporting varying degrees of security including file channels for air-gapped systems. Rocket has set up two internet channels from which you can download z/OS open source ports using conda – one public and open to all, the other a secure channel server on premise at Rocket available only to Rocket customers on a support plan.

z/OS Miniconda is a free bundle of open source containing everything you need to run conda on z/OS. To get started using conda you need to install z/OS Miniconda on your z/OS system.

To download z/OS Miniconda, complete the following steps:

1. Sign in to the Rocket Community Portal.
   https://my.rocketsoftware.com/RocketCommunity
2. Click Downloads from the navigation menu. A list of available Rocket products for your account appears.
3. Select z/OpenSource.
4. Type 'Miniconda' in the search box to filter the list of available downloads.
5. Click the filtered ID A dialog window appears with the files that are required for setup.
6. Click each file to download them to your system.
7. Using a FTP or SFTP client transfer the setup files to z/OS:
   1. miniconda-py37-zos-<yyyy-mm-dd>.run
   2. app_dev_X.Y.txt

Full documentation on z/OS Miniconda is contained within zOS_Miniconda_Documentation_<date>.pdf.

Learn more about conda here.

Note, Rocket is decommissioning the old download and install system for all open source products except for z/OS Miniconda itself.

Rocket has moved to a new system – conda – for downloading, installing, and upgrading all z/OS open source ports developed by Rocket.  With conda, a single command can replace dozens of steps and commands previously required to install some open source products.  For example, installing z/OS Git with its dependencies formerly required over thirty steps but now can be accomplished with a single conda command.

Conda is an open source tool ideally suited for delivery and deployment of software on the mainframe due to its channel concept and multiple types of channels supporting varying degrees of security including file channels for air-gapped systems. Rocket has set up two internet channels from which you can download z/OS open source ports using conda – one public and open to all, the other a secure channel server on premise at Rocket available only to Rocket customers on a support plan.

z/OS Miniconda is a free bundle of open source containing everything you need to run conda on z/OS. To get started using conda you need to install z/OS Miniconda on your z/OS system.

To download z/OS Miniconda, complete the following steps:

1. Sign in to the Rocket Community Portal.
   https://my.rocketsoftware.com/RocketCommunity
2. Click Downloads from the navigation menu. A list of available Rocket products for your account appears.
3. Select z/OpenSource.
4. Type 'Miniconda' in the search box to filter the list of available downloads.
5. Click the filtered ID A dialog window appears with the files that are required for setup.
6. Click each file to download them to your system.
7. Using a FTP or SFTP client transfer the setup files to z/OS:
   1. miniconda-py37-zos-<yyyy-mm-dd>.run
   2. app_dev_X.Y.txt

Full documentation on z/OS Miniconda is contained within zOS_Miniconda_Documentation_<date>.pdf.

Learn more about conda here.

Note, Rocket is decommissioning the old download and install system for all open source products except for z/OS Miniconda itself.

Rocket has moved to a new system – conda – for downloading, installing, and upgrading all z/OS open source ports developed by Rocket.  With conda, a single command can replace dozens of steps and commands previously required to install some open source products.  For example, installing z/OS Git with its dependencies formerly required over thirty steps but now can be accomplished with a single conda command.

Conda is an open source tool ideally suited for delivery and deployment of software on the mainframe due to its channel concept and multiple types of channels supporting varying degrees of security including file channels for air-gapped systems. Rocket has set up two internet channels from which you can download z/OS open source ports using conda – one public and open to all, the other a secure channel server on premise at Rocket available only to Rocket customers on a support plan.

z/OS Miniconda is a free bundle of open source containing everything you need to run conda on z/OS. To get started using conda you need to install z/OS Miniconda on your z/OS system.

To download z/OS Miniconda, complete the following steps:

1. Sign in to the Rocket Community Portal.
   https://my.rocketsoftware.com/RocketCommunity
2. Click Downloads from the navigation menu. A list of available Rocket products for your account appears.
3. Select z/OpenSource.
4. Type 'Miniconda' in the search box to filter the list of available downloads.
5. Click the filtered ID A dialog window appears with the files that are required for setup.
6. Click each file to download them to your system.
7. Using a FTP or SFTP client transfer the setup files to z/OS:
   1. miniconda-py37-zos-<yyyy-mm-dd>.run
   2. app_dev_X.Y.txt

Full documentation on z/OS Miniconda is contained within zOS_Miniconda_Documentation_<date>.pdf.

Learn more about conda here.

Note, Rocket is decommissioning the old download and install system for all open source products except for z/OS Miniconda itself.

Hi Marc,
Take a look at this thread:

https://community.rocketsoftware.com/forums/forum-home/digestviewer/viewthread?MessageKey=a19796f8-b451-427c-bb5e-6d3c9f27b8ac&CommunityKey=1e694975-142d-4f2d-9b52-0e37e225db41&tab=digestviewer#bma19796f8-b451-427c-bb5e-6d3c9f27b8ac

Thanks

Rocket has moved to a new system – conda – for downloading, installing, and upgrading all z/OS open source ports developed by Rocket.  With conda, a single command can replace dozens of steps and commands previously required to install some open source products.  For example, installing z/OS Git with its dependencies formerly required over thirty steps but now can be accomplished with a single conda command.

Conda is an open source tool ideally suited for delivery and deployment of software on the mainframe due to its channel concept and multiple types of channels supporting varying degrees of security including file channels for air-gapped systems. Rocket has set up two internet channels from which you can download z/OS open source ports using conda – one public and open to all, the other a secure channel server on premise at Rocket available only to Rocket customers on a support plan.

z/OS Miniconda is a free bundle of open source containing everything you need to run conda on z/OS. To get started using conda you need to install z/OS Miniconda on your z/OS system.

To download z/OS Miniconda, complete the following steps:

1. Sign in to the Rocket Community Portal.
   https://my.rocketsoftware.com/RocketCommunity
2. Click Downloads from the navigation menu. A list of available Rocket products for your account appears.
3. Select z/OpenSource.
4. Type 'Miniconda' in the search box to filter the list of available downloads.
5. Click the filtered ID A dialog window appears with the files that are required for setup.
6. Click each file to download them to your system.
7. Using a FTP or SFTP client transfer the setup files to z/OS:
   1. miniconda-py37-zos-<yyyy-mm-dd>.run
   2. app_dev_X.Y.txt

Full documentation on z/OS Miniconda is contained within zOS_Miniconda_Documentation_<date>.pdf.

Learn more about conda here.

Note, Rocket is decommissioning the old download and install system for all open source products except for z/OS Miniconda itself.

Hello András,

I recommend two videos.  The video instructing how to download and install z/OS Miniconda, and another video instructing how to use conda to download and install open-source ports for z/OS.

As for firewall/proxy settings this posting explains (it is exactly the same for z/OS as it is for Linux).  However with a support contract you will also have access to install options that do not require internet access for you z/OS systems.

As Volkswagen is not on a support contract for any of our Rocket z/OS open-source ports, you will need to ask additional questions here on this forum.  Rocket's support portal is restricted to customers that are paying support.

Please note also that without a support contract Volkswagen will not have access to new versions of ports, nor to CVE (security vulnerability) fixes until after a six month delay.  If you need fast access to vulnerability fixes I recommend getting on support.

Best regards,

-Peter

Hello,

Thank you for the videos, I've managed to get to the following point:
After I issue 'conda create -n test1203' I face the following error:

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

Traceback (most recent call last):
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/exc
eptions.py", line 819, in __call__
return func(*args, **kwargs)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/cli
/main.py", line 74, in _main
context.__init__(argparse_args=args)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/bas
e/context.py", line 238, in __init__
argparse_args=argparse_args)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/configuration.py", line 722, in __init__
self._set_search_path(search_path)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/configuration.py", line 728, in _set_search_path
self._set_raw_data(load_file_configs(search_path))
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/configuration.py", line 369, in load_file_configs
raw_data = odict(kv for kv in chain.from_iterable(load_paths))
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/configuration.py", line 369, in <genexpr>
raw_data = odict(kv for kv in chain.from_iterable(load_paths))
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/configuration.py", line 344, in _file_yaml_loader
yield fullpath, YamlRawParameter.make_raw_parameters_from_file(fullpath)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/configuration.py", line 332, in make_raw_parameters_from_file
ruamel_yaml = yaml_load(fh)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/conda/com
mon/serialize.py", line 54, in yaml_load
return yaml.load(string, Loader=yaml.RoundTripLoader, version="1.2")
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/ruamel/ya
ml/main.py", line 638, in load
loader = Loader(stream, version, preserve_quotes=preserve_quotes)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/ruamel/ya
ml/loader.py", line 59, in __init__
Reader.__init__(self, stream, loader=self)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/ruamel/ya
ml/reader.py", line 80, in __init__
self.stream = stream # type: Any # as .read is called
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/ruamel/ya
ml/reader.py", line 125, in stream
self.determine_encoding()
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/ruamel/ya
ml/reader.py", line 169, in determine_encoding
self.update_raw()
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/site-packages/ruamel/ya
ml/reader.py", line 278, in update_raw
data = self.stream.read(size)
File "/VERSION/usr/lpp/ROK/Miniconda/lib/python3.7/codecs.py", line 323, i
n decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa7 in position 235: in
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa7 in position 235: in
valid start byte 

******
At the moment we are unable to open cases for open software can you support me with this case, in this format? 

env|sort
ls -T ~/.condarc
cat ~/.condarc
conda config --show-source

ls -T ~/.condarc
cat ~/.condarc

Hi,

I guess Andreas is dying at the same point I do.
The path "/versions/usr/lpp" tells me, that Andreas wants to put the opentools  on sysres/ipl volume and/or in an shared sysplex environment. Unfortunaly the conda selfextracting .run-script dosn't fit traditional installation procedures.
When you execute the script even with the parameter -p /usr/lpp/rocket the script is restting the by the line
prefix=$(to_absolute_path "$1")
In my case after the installation of packages via conda install in hundreds or thousands of files the path was modified to /SYSRES1/usr/lpp and hardcoded inserted. This means after an IPL and flipping the ipl volume this installation seems to be broken.

I think it would be very useful if Rocket would publish a best practice step-by-step guide how I use conda to install tools and deliver it centralized to my users. I mean in particular installing package once anywhere in the filesystem and copy it across the sysplex to other systems.

Or means conda that I have to do conda install packagename on every system in the sysplex?

I've just watched your youtube introduction (https://www.youtube.com/watch?v=wRWDJPSDwIc), but felt a little bit confused because everytime when I saw or read about rocket install over conda procedures they use /u/username directories

as target places. Sorry, don't get me wrong but if I would tell my user "use conda to install the tools by yourself", they would laught at me. Thats my job as an sysadmin.

So i tried to install miniconda and the whole appdev manifest at /u/myhome and copied all stuff from /u/myhome/envs/appdev to /usr/lpp/rocket/appdev but now when users try to use git for example they got ICH408 messages by reading /u/myhome.

Conda seems to be linking packages against the original used environment path.

To have DevOps capabilities on the mainframe is nice, but the majority of z/OS installations were managed very centralized. How I deal with conda in that case?

I would be very thankfull if you should show us a way to go. Thank you.

Kind regards,

Björn Schanz

Hi,

I guess Andreas is dying at the same point I do.
The path "/versions/usr/lpp" tells me, that Andreas wants to put the opentools  on sysres/ipl volume and/or in an shared sysplex environment. Unfortunaly the conda selfextracting .run-script dosn't fit traditional installation procedures.
When you execute the script even with the parameter -p /usr/lpp/rocket the script is restting the by the line
prefix=$(to_absolute_path "$1")
In my case after the installation of packages via conda install in hundreds or thousands of files the path was modified to /SYSRES1/usr/lpp and hardcoded inserted. This means after an IPL and flipping the ipl volume this installation seems to be broken.

I think it would be very useful if Rocket would publish a best practice step-by-step guide how I use conda to install tools and deliver it centralized to my users. I mean in particular installing package once anywhere in the filesystem and copy it across the sysplex to other systems.

Or means conda that I have to do conda install packagename on every system in the sysplex?

I've just watched your youtube introduction (https://www.youtube.com/watch?v=wRWDJPSDwIc), but felt a little bit confused because everytime when I saw or read about rocket install over conda procedures they use /u/username directories

as target places. Sorry, don't get me wrong but if I would tell my user "use conda to install the tools by yourself", they would laught at me. Thats my job as an sysadmin.

So i tried to install miniconda and the whole appdev manifest at /u/myhome and copied all stuff from /u/myhome/envs/appdev to /usr/lpp/rocket/appdev but now when users try to use git for example they got ICH408 messages by reading /u/myhome.

Conda seems to be linking packages against the original used environment path.

To have DevOps capabilities on the mainframe is nice, but the majority of z/OS installations were managed very centralized. How I deal with conda in that case?

I would be very thankfull if you should show us a way to go. Thank you.

Kind regards,

Björn Schanz

iconv -f ISO8859-1 -t UTF-8 .condarc > .condarc.utf8

mv .condarc .condarc.off

Hello,

I've converted the .condarc file to UTF-8 and the conda info, and conda config --show-source commands started to work, but when I issued conda create -n test1213 I've got the same issue as before.

Regards, András Szabó

Hello,

I was able to solve the issue with the .condarc (I missed a §) and now I was able to create the new environment without any issue and I was able to activate it. However when I tried to search for "git" I got te following error:

compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_.so: CEE3501S The module /u/axn0292/.ffi/i_.so
was not found.                                                                 
No ffi call function could be found or created                                 
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_iiPi.so: CEE3501S The module /u/axn0292/.ffi/v_
iiPi.so was not found.                                                         
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/P_PXPP.so: CEE3501S The module /u/axn0292/.ffi/P_
PXPP.so was not found.                                                         
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_.so: CEE3501S The module /u/axn0292/.ffi/v_.so
was not found.                                                                 
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_P.so: CEE3501S The module /u/axn0292/.ffi/i_P.s
o was not found.                                                               
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_PP.so: CEE3501S The module /u/axn0292/.ffi/v_PP
.so was not found.                                                             
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PiiP.so: CEE3501S The module /u/axn0292/.ffi/i_
PiiP.so was not found.                                                         
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PIPPPP.so: CEE3501S The module /u/axn0292/.ffi/
i_PIPPPP.so was not found.                                                     
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_PIPP.so: CEE3501S The module /u/axn0292/.ffi/v_
PIPP.so was not found.  
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PIPXPP.so: CEE3501S The module /u/axn0292/.ffi/
i_PIPXPP.so was not found.                                                     
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_Pii.so: CEE3501S The module /u/axn0292/.ffi/v_P
ii.so was not found.                                                           
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_iP.so: CEE3501S The module /u/axn0292/.ffi/i_iP
.so was not found.                                                             
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PPPPIP.so: CEE3501S The module /u/axn0292/.ffi/
i_PPPPIP.so was not found.                                                     
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PP.so: CEE3501S The module /u/axn0292/.ffi/i_PP
.so was not found.                                                             
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PP.so: CEE3501S The module /u/axn0292/.ffi/i_PP
.so was not found.                                                             
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PPP.so: CEE3501S The module /u/axn0292/.ffi/i_P
PP.so was not found.                                                           
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PPI.so: CEE3501S The module /u/axn0292/.ffi/i_P
PI.so was not found.                                                           
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PPPPIP.so: CEE3501S The module /u/axn0292/.ffi/
i_PPPPIP.so was not found.                                                     
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PPPP.so: CEE3501S The module /u/axn0292/.ffi/i_
PPPP.so was not found.                                                         
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/I_PPPIPI.so: CEE3501S The module /u/axn0292/.ffi/
I_PPPIPI.so was not found.                                                     
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/I_PPPI.so: CEE3501S The module /u/axn0292/.ffi/I_
PPPI.so was not found.                                                         
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/i_PPP.so: CEE3501S The module /u/axn0292/.ffi/i_P
PP.so was not found.                                                           
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_P.so: CEE3501S The module /u/axn0292/.ffi/v_P.s
o was not found.                                                               
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_P.so: CEE3501S The module /u/axn0292/.ffi/v_P.s
o was not found.                                                               
compile command returned 65280                                                 
Failed to load /u/axn0292/.ffi/v_P.so: CEE3501S The module /u/axn0292/.ffi/v_P.s
o was not found.                                                               
Loading channels: Ö compile command returned 65280                             
Failed to load /u/axn0292/.ffi/i_iP.so: CEE3501S The module /u/axn0292/.ffi/i_iP
.so was not found.                                                             
No ffi call function could be found or created                                 
! No ffi call function could be found or created                               
CEE3201S The system detected an operation exception (System Completion Code=0C1)
.                                                                              
         From entry point internal_verify at compile unit offset +00000000000000
00 at entry offset -00000000170F7538 at address 0000000000000000.              
         Possible Bad Branch:  Statement: 1919  Offset: +00000230              
CEE5202S The signal SIGILL was received.                                                                                              

I've ​checked the directory and in i_.list I've found that it is looking for the following path /usr/lpp/cbclib/xlc/exe/ccndrvr
Could you please advise us how should we solve this error?

Regards, András Szabó