Skip to main content

I am trying to download the latest Rocket open source files from folder : 

USSP-2043 Rocket Open AppDev for Z (free solution)

I notice the following, which I assume I should use: 

I don't see a manifest file that corresponds to 2.0 .  should I use either of these manifest files  :

I recall a few months back there was a 2.0 Manifest file. 

appdev_manifest_2.0.1.txt

Please advise

Thanks,

Marco Passaretti

------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------

I am trying to download the latest Rocket open source files from folder : 

USSP-2043 Rocket Open AppDev for Z (free solution)

I notice the following, which I assume I should use: 

I don't see a manifest file that corresponds to 2.0 .  should I use either of these manifest files  :

I recall a few months back there was a 2.0 Manifest file. 

appdev_manifest_2.0.1.txt

Please advise

Thanks,

Marco Passaretti

------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------
Hi Marco,

1) The versions of Miniconda and AppDev bundle are not directly related with each other. Any list can be used for installing packages in a particular environment.
2) Since AppDev bundle packages are publishing with 6 months delay to public channel, we removed the appdev_manifest files that can be used for installation from Rocket secure channel. It was made to avoid some confuses until the packages are not available in the public channel.

Thanks,
Sergei

------------------------------
Sergei Rezepin
Rocket Software
------------------------------
Hi Marco,

1) The versions of Miniconda and AppDev bundle are not directly related with each other. Any list can be used for installing packages in a particular environment.
2) Since AppDev bundle packages are publishing with 6 months delay to public channel, we removed the appdev_manifest files that can be used for installation from Rocket secure channel. It was made to avoid some confuses until the packages are not available in the public channel.

Thanks,
Sergei

------------------------------
Sergei Rezepin
Rocket Software
------------------------------

Hi Sergei,

Thanks for the response!
I will use appdev_manifest_1.2.1.txt with miniconda-zos-2.0-2022-01-17.run

I assume this will also get me the latest version of Python?

Please advise if my assumption is correct.

Thanks,

Marco Passaretti 



------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------

Hi Sergei,

Thanks for the response!
I will use appdev_manifest_1.2.1.txt with miniconda-zos-2.0-2022-01-17.run

I assume this will also get me the latest version of Python?

Please advise if my assumption is correct.

Thanks,

Marco Passaretti 



------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------

Hi Sergei, 

I received a stange error when extracting the files : 


my zfs shows approx 9.8 GB free :
# df -Pm .
Filesystem 1M-blocks Used Available Capacity Mounted on
OD4J.OMVS.USER.Q3BBGX8 21992 12147 9845 56% /u/q3bbgx8

When I run the extract it complains about zfs out of space.  I think this is a bug : 

./miniconda-zos-2.0-2022-01-17.run --path /u/q3bbgx8/miniconda


Checking available space in /u/q3bbgx8/miniconda ... 9845 MB ... OK
Moving out sensitive files and directories...
Extracting packages from distribution...
3097 blocks
FSUM7131 Out of space or reached the end of the archive file.
If you want to go on, type device or file name when ready

Please advise if there is a workaround for this error .

Thanks,

Marco Passaretti 



------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------


Hi Sergei, 

I received a stange error when extracting the files : 


my zfs shows approx 9.8 GB free :
# df -Pm .
Filesystem 1M-blocks Used Available Capacity Mounted on
OD4J.OMVS.USER.Q3BBGX8 21992 12147 9845 56% /u/q3bbgx8

When I run the extract it complains about zfs out of space.  I think this is a bug : 

./miniconda-zos-2.0-2022-01-17.run --path /u/q3bbgx8/miniconda


Checking available space in /u/q3bbgx8/miniconda ... 9845 MB ... OK
Moving out sensitive files and directories...
Extracting packages from distribution...
3097 blocks
FSUM7131 Out of space or reached the end of the archive file.
If you want to go on, type device or file name when ready

Please advise if there is a workaround for this error .

Thanks,

Marco Passaretti 



------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------

Hi Marco,

Could you check that the file downloaded completely?

ls -laT miniconda-zos-2.0-2022-01-17.run

The size should be 100620275.

The other possible reason - the filesystem is compressed. You can check it by the following command on USS:

zfsadm fsinfo YOUR.FILE.SYSTEM.DATA.SET.HERE

if it's CO=Compressed try to install miniconda to another ZFS which is NC=Not compressed, or start decompression against compressed one and try again after it is decompressed.

You can also read this thread about the similar issue:

https://community.rocketsoftware.com/forums/forum-home/digestviewer/viewthread?MessageKey=80980cf0-c09b-4a63-8921-49ab6177ce2d

Miniconda 1.x contains python 3.7.0  (ported by Rocket).

Miniconda 2.0 contains IBM python 3.9.5.

Thanks,

Sergei



------------------------------
Sergei Rezepin
Rocket Software
------------------------------

Hi Marco,

Could you check that the file downloaded completely?

ls -laT miniconda-zos-2.0-2022-01-17.run

The size should be 100620275.

The other possible reason - the filesystem is compressed. You can check it by the following command on USS:

zfsadm fsinfo YOUR.FILE.SYSTEM.DATA.SET.HERE

if it's CO=Compressed try to install miniconda to another ZFS which is NC=Not compressed, or start decompression against compressed one and try again after it is decompressed.

You can also read this thread about the similar issue:

https://community.rocketsoftware.com/forums/forum-home/digestviewer/viewthread?MessageKey=80980cf0-c09b-4a63-8921-49ab6177ce2d

Miniconda 1.x contains python 3.7.0  (ported by Rocket).

Miniconda 2.0 contains IBM python 3.9.5.

Thanks,

Sergei



------------------------------
Sergei Rezepin
Rocket Software
------------------------------

Hi Sergei,

Thnaks for the information.

You were correct .  the download of miniconda-zos-2.0-2022-01-17.run was not complete.   Issue is now resolved .

I do notice some changes in the location to where my Conda enviroment is being deployed:

1) when I issue :

bash-4.3$ conda create -n sysprog  (from /u/q3bbgx8/miniconda/bin) 

I get the following :

Solving environment: done

## Package Plan ##

environment location: /u/q3bbgx8/.conda/envs/sysprog  <== I believe I used to get thsi resolved to /u/q3bbgx8/miniconda/envs/sysprog 


Proceed (Ýy¨/n)? y

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
# $ conda activate sysprog
#
# To deactivate an active environment, use
#
# $ conda deactivate

Has something changed and now my envs is now located at :
/u/q3bbgx8/.conda/envs/sysprog

or am I not entering something  incorrectly ? 

Please advise.

Thanks,

Marco 
  



------------------------------
Marco Passaretti
System Programmer
Royal Bank of Canada
Toronto ON CA
------------------------------