Rocket® Open-Source Languages and Tools for z/OS®

Ive looked at many installing curl threads, but nothing seems to work for me?  I get: <C1:$ conda install -c https://conda.anaconda.org/zoss-appdev curl --override-channels                    Collecting package metadata (repodata.json):   done                                                       Solving environment:   failed with initial frozen solve. Retrying with flexible solve.                                                                                                                              PackagesNotFoundError: The following packages are not available from current channels:                                                                                                                                - curl                                                                                                                                                                                                            Current channels:                                            

I'm sure I am not the first to ask this, but I had no good luck searching the forum for an answer.   New to miniconda, I have it installed, we are behind a proxy http/https proxy server.  I have that configured in .condarc.   When running a conda create, I get SSL error.   Ive set ssl_verify: False        and made no apparent difference. Any answers from the experts? (base) TEC1:$ conda create -p execution                                                                                             WARNING: A directory already exists at the target location '/TEC1/u/MaintMiniconda/execution'                                       but it is not a conda environment.                                                                                                  Continue creating environment (y/[n])? y                                                                                                                                                                                                 

Using Putty to access 2 different z/OS 2.4 images; Putty settings are same for each session save for the target IP address. On system with bash 4.2.53(2) backspace behavior works normally - content is deleted and cursor key backs up on screen to reflect that.  On system with bash 5.1.0(1) backspace deletes content from the buffer (but not the screen) and the cursor moves forward (sometimes more than a single character's worth).  On both systems using the native IBM supplied shell backspace works fine both before entering  bash and after exiting so the unexpected behavior seems to be pointing to bash 5.1.0(1).  Any pointers on where to look or what to change appreciated.  ------------------------------Karl HufSenior Vice President, Mainframe SupportNorthern Trust CompanyChicago IL US------------------------------

Hello, we're looking for a version of GnuPG running on z/OS. Is there a version available from Rocket or does anyone know a version somewhere available?  Furthermore can I find a list of all available ported tools from Rocket? Thanks for any help. Kind regards Juergen

Hi Everyone, We are planning to install curl on z/OS 2.2 I have a question related to curl for z/OS Is curl compatible for z/OS 2.2 , if yes, can you please let me know which version of curl is compatible to install on z/OS 2.2 ThanksSrinivas

I've installed Rocket Open AppDev for Z (free solution), but Python doesn't seem to be working quite right. In particular, I'm getting different behavior based on whether I invoke Python via executing the script vs. invoking Python manually and passing it the script.  For example, with the following sample test.py: #!/z/rocket/tools/bin/python print("Hello world!") If I invoke Python explicitly and pass it the script, it works just fine: $ /z/rocket/tools/bin/python test.py Hello world! If I instead invoke the script directly, I get the following. $ ./test.py ./test.py: can't open file '/u/z123/SHELL=/z/rocket/tools/bin/bash': [Errno 129] EDC5129I No such file or directory. That looks like it's somehow interpreting the environment being passed to python ("SHELL=...") as the script name it's supposed to execute.  Indeed, if I then pass the script name as the first argument, it works: $ ./test.py test.py Hello world! Stranger still, I don't see this behavior with scripts that i

Getting next error when using GIT 2.41.0-4 java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: a���a���������a���a���aٖ����a�����a������a���a���������

We are testing upgrade in our Jenkins development environment with following version changes   Jenkins Master version from v2.346.2 to 2.387.1 Git client plugin from v3.11.2 to v4.2.0    Git Version z/OS not changed 2.14.4_zos_b09   We have setup up Jenkins Agent as a started task Setting up the CI Pipeline Agent on IBM Z as a Started Task   We see following errors   Jenkins Console:   org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id: fatal: bad config line 1 in file .git/config     STDERR info Jenkins Slave Started Task z/OS:   Exception caught during execution of command '<gitInstallFolder>/git/bin/git, config, --system, --edit¨' in '<gitInstallFolder>/git/bin', return code '128', error message 'fatal: Invalid path '/rsusr': EDC5129I No such file or directory.     Check System config location When we check system config information we receive following error git config --list --sys

Something changed in git in terms of file encoding.These files were created using this code:cmd = 'cd' localrep'/'zigirep ,    '&& git show' hcommit':'element ,    '>' filewhere localrep/zigirep, hcommit, element and file are all variables. This is what I have on my work system for this use case using git version 2.26.2-78 t IBM-1047 T=on -rw-rw-rw- 1 SPLBD SYS1 1875 Feb 1 05:03 CHGSTR But with git version 2.26.2-84 I get this: t ISO8859-1 T=on -rw-rw-rw- 1 LBDYCK ZOWEDEV 1875 Feb 1 08:06 CHGSTRTo summarize this - with git 2.26.2-27 the git show generated file is tagged as IBM-1047 and then with git 2.26.2-84 it is now tagged as ISO8859-1.Why the change and how can I control it?

From my WorkStation (Mac in this case) I execute by curl an api authenticating me through a personal certificate: jmfernandezp@Josemas-MacBook-Pro ~ % curl -X GET -k -H 'CICS-Environment: A6' -i 'https://zosa.tor.es.ibm.com:7050/issdbdc/progprba/Hola' --cert ~/Customizacion\\ Productos/Certificados/personal_p083598.pem:JosemaHTTP/1.1 200 OKX-Powered-By: Servlet/3.1Content-Type: application/json; charset=UTF-8Content-Language: en-USContent-Length: 146Set-Cookie: LtpaToken2=orhzg9vapG1Pc+FCqUDptJERA9U2SNWGPUvdAVrShFHFiKZP6sE8DBi9jFh88MV4VcbyNUGr6o8nxNScDZFZX9RQfOuARKMyCmaGrHFSkScTWkkCxyV3WRngiKPA/4OYRRTt+eArYFyouzMsmOetUdt/QuXbh7moFJol1OcrNFJtu9cbQqKg0uL/fjM2kJ8CgaoBZUL/WJw9b804oZfe//Nvon0bhI4C8lYt77F9F8m7ZEOHbtgYQ9SsnZ6AdprMxv78OrwjaJntZedkAWEotEk0kNjzvLLDzMrdgOHnmVtAEN4yfZHxe+hwIq6MjJDH; Path=/; HttpOnlySet-Cookie: JSESSIONID=0000WLMVWLLT710Qmo9JJwgmF67:dd4c67f3-f2dd-48b7-b879-31de8f82960a; Path=/; Secure; HttpOnlyDate: Thu, 30 Mar 2023 11:35:24 GMTExpires: Thu, 01 Dec 1994 16:00:00 GM

Hi,I've been working to call an API via JCL using CURL by passing public & private keys of the certificate. I was able to successfully make a call to the PCF endpoint URL using below JCL where I got the request as expected by the API developer, however, due to security reasons now I need to make a call to an Apigee endpoint instead of PCF cloud directly. But for that I've been asked by our API team to pass below 3 parameters while making a CURL call. 1.) Client-meta data2.) API-key3.) requestUniqueIDBelow is the JCL.//ABCJ4API JOB (XXXX,P),'CURL',MSGCLASS=T,SCHENV=SYSPLEX,USER=XXX //* //S5QCUR1 EXEC PGM=BPXBATCH, // REGION=0M //STDPARM DD * SH cd /appshare/XXXX/road4z/bin; curl --get -v URL https://apigw-int.devxx.xxx.com/xxxx/pdg/v1 --key '/appshare/API/key.pem' --cacert '/appshare/API/ca.pem' /* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=*Please let me know how to pass the above 3 parameters using CURL and if this is not the correct forum, please let me know where I can post and get

Hello, I have been able install the OpenSource products using the SMPE installer with FMID HROA110. Plus the 2 PTFs that were available. The 2 PTFS list the " Package name               version     build " information supplied in the PTF. I do not have a similar list for the base FMID. Is there a list of packages shipped in HORA110? Thanks Bruce ------------------------------Bruce HewsonInfra Tech Lead AnalystCitigroup Technology IncSingapore SG------------------------------

Hi, I was asked to install curl to help diagnose a problem with another product.  I installed miniconda, and that seems to be ok. When I try to use miniconda to install curl, I get: Collecting package metadata (repodata.json):   failed                                                                                                           CondaHTTPError: HTTP 401 UNAUTHORIZED for url <https://condaserver.rocketsoftware.com/api/repo/zoss-appdev/zos-z/repodata.json> I don't have a support contract with Rocket Software. What do I have to do? Thanks Gadi

Not wanting to perform an installation to active system, our process is installation and maintenance to a non-active environment which is later copied to a SYSRES based set of files, which are mounted at IPL. The SMPE installation process hardcodes the Installation path /mvsde2/ into the installed files.  e.g.   /mvsde2/usr/lpp1/roa/ro/export_vars.sh             **************************************************************** #common export of PATH, LIBPATH and MANPATH            export PATH=/mvsde2/usr/lpp1/roa/ro/bin:$PATH           export LIBPATH=/mvsde2/usr/lpp1/roa/ro/lib:$LIBPATH        export MANPATH=/mvsde2/usr/lpp1/roa/ro/share/man:$MANPATH                                      for file in /mvsde2/usr/lpp1/roa/ro/etc/conda/activate.d/*.sh   do                                   if [ -f "$file" ]; then                        . "$file"                           fi                               done                                **************************************************

I'm attempting to run the miniconda self-extracting installer and am receiving the following error.  Thanks for any help you can provide. The license agreement can later be accessed for review at the following path:            /usr/local/miniconda/IBM_LICENSE.txt                                                                                                                                        Please, press ENTER to continue                                                      

Hello, I am writing to consult you on activating miniconda on z/OS. After I installed z/OS Miniconda and tried to activate the environment, I encountered the following error. Would you please help figure out what' wrong? Thanks. bash-5.1$ conda activate proenvCommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.To initialize your shell, run     $ conda init <SHELL_NAME> Currently supported shells are:  - bash  - fish  - tcsh  - xonsh  - zsh  - powershell See 'conda init --help' for more information and options. IMPORTANT: You may need to close and restart your shell after running 'conda init'. bash-5.1$ conda init bash # >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<     Traceback (most recent call last):      File "/u/mvsbuild/miniconda/lib/python3.10/site-packages/conda/exceptions.py", line 1118, in

This is an FYI post because it was an issue for us.In git 2.35, a new feature was added that checks if the user executing the git command is the owner of the git root directory and will fail if they don't match.This feature seems to have found it way into version 2.26.2-87 somewhere between 2.26.2-84 and 2.26.2-87.This feature can be disabled withgit config --global--add safe.directory '*'There is a bunch of customizations to this command that might be relevant for you - read the documentationYou can also read why the check was added - setup_git_directory(): add an owner check for the top-level directory · git/git@8959555------------------------------Adam Martin BrittIT-ArchitectBECRanders SV DK------------------------------

We have been using bash GNU bash, version 4.3.46(51)-release (i370-ibm-openedition) which is pretty old. Just updated to all the new Opensource Rocket tools and the new bash (5.1.0) does not call the .bashrc (or bashrc) anymore. Switch back to the old version (4.3.46) and it works fine with no other changes.Any ideas on why I am having this issue? Potential solutions?Thanks Mark Shackelford------------------------------Mark ShackelfordSystems ProgrammerDynatraceDetroit MS US------------------------------

Hi Team,I am trying to clone the repo from Bibucket to IBM IDz by Egit and Rocket git but some unstaged files are coming from the Bitbucket server everytime.Could you please suggest what should be the solution for this?------------------------------Ratnam GuptaRocket Forum Shared Account------------------------------

I am having trouble getting the Miniconda environment working without breaking BPXBATCH.I have a sample BPXBATCH job://BPXBATCH EXEC PGM=BPXBATCH,REGION=512M,PARM='sh java -version'//STDENV DD * //SYSOUT DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* If I follow the Miniconda instructions for login shell of /bin/sh, the program specified in the BPXBATCH parm is not executed.If I change the login shell to bash, and add conda.sh to .profile, the program is executed (i.e. attempted)  but the PATH etc. is not set. It appears that bash does not execute .profile when invoked from BPXBATCH.(This may be a bash problem rather than Miniconda.)Any suggestions about how to get this working without breaking BPXBATCH?ThanksAndrew Rowley------------------------------Andrew RowleySelf RegisteredBallarat AU------------------------------

Hello Is strace command available for USS?------------------------------John DavisDeveloperBroadcom Corporation------------------------------

Hi all,I am having a problem with sudo 1.8.6p3. I know, I know this is not the latest release, but we're still not ready to deploy miniconda, so please bear with me.The problem is that upon executing some commands I get a SIGPIPE.Example: yesterday I was experimenting with some sudoers rules and I launched this one (real user has been amended):sudo -H -n -u XXXXX -- git ls-remote --tags origin "refs/tags/PROD*"which ends immediately with this error: CEE5213S The signal SIGPIPE was received.The same command executed without sudo (from the correct user) works perfectly.I have tried googling around but I do not find anything. Is this a known behavior fixed in the latest release?Thank you in advanceCris

Dear community,I have installed vim via miniconda. When I call it, the Help information which is normally shown in the middle of the screen, is shown at the bottom.In the version installed directly in the past, it looks like this:I tried some hints which were given in the forum but nothing changed. unset TERMINFO export VIM=/usr/lpp/rocket/share/vim/vim80 add  set t_RV= to .vimrcHints are very welcome!RegardsJuergen------------------------------Jurgen HildebrandtSystemprogrammer Mainframe Plattform ManagementT-Systems International GmbHDüsseldorf DE------------------------------

With the switch from Rocket Ported Tools to z/OS Miniconda the findutils disappeared.  At least I could not find it in zoss-appdev.Is this correct or do I just miss anything?------------------------------Manfred LotzKyndryl Deutschland GmbHKelsterbach DE------------------------------

We have some interest in a zip/unzip that can handle very large files greater than 2GB or 4GB and beyond.'Dan