Rocket Mainframe DevOps

Hi, Is it documented anywhere what addresses and ports we need open on our firewall to reach the conda servers (both free and paid for) at Rocket? I'll have to make a request and have it approved, and I really don't want to have to go through that pain more than once.. :-)Thanks------------------------------Andy Stylesz/Series System ProgrammerLloyds Banking Group------------------------------

The downloads for cURL include:appdev_manifest_1.3.txtappdev_manifest_1.2..1txtbut onlyminiconda-zos-1.2.1-2020-12-23.runShouldn't there be a miniconda-zos-1.3-yyyy-mm-dd.run ?There also seem to be a bunch of older manifests--why?And what isminiconda-py39-zos-2022-01-17.run ?signed,Confused------------------------------Phil Smith IiiDistinguished TechnologistMicro FocusHerndon VA US------------------------------

I am at the end of a long day and a bit frustrated  (and with no budget for the professional support).  This post may expose some of my current irritations.After literally days of fighting with custom configured environment variables and destination file systems and the public rocket server I was finally able to create an environment with miniconda and attempt an install using the command.(/usr/local/Rocket) TECH905@jismvs_test-> export CONDA_PREFIX=/usr/local/Rocket/miniconda(/usr/local/Rocket) TECH905@jismvs_test-> conda install -c https://conda.anaconda.org/zoss-appdev --file /u/tech905/tmp/appdev_bundle_1.0.txtI have attached the output file as conda install 1.txtI do not see any new install results in my file system:   The error messages included arePreparing transaction: doneVerifying transaction: doneExecuting transaction: donesed: FSUM7310 no remembered regular expressionsed: FSUM7296 newline or end of file found in patternsed: FSUM7296 newline or end of file found in pat

As part of a code-signing initiative, I am working with SHA256 digests on z/OS.  In the past, I would download files to a Linux or Windows machine and verify that the hashes matched expected values. But for some reason, Rocket openssl (OpenSSL 1.1.1h 22 Sep 2020) yields different digest values (openssl dgst -sha256) than Linux or WIndows. The only way to get the same hash is to tag the file  on z/OS before creating the hash: chtag -tc ISO8859-1 <filename> This feels really odd, since the original file is binary.  Is this working as designed? ------------------------------Jeff MierzejewskiAdvisory Software EngineerIBM Global ServicesAustin TX US------------------------------

Status: DeliveredBy default, we will take the previous version after another checkout of a component. It would be helpful if this frequent process could be done in one workstep.If a component during its modification was changed at the baseline, the new baseline version of the component must be taken over again in the package via checkout. Afterwards the developer will check the last modification version against the new baseline version.   Our standard process is, the previous version is reactivated in the package after the checkout.   Because we process a large amount of components in this way, it would be helpful for us to be able to do this in one work step (checkout and reaktivating the last modification version).

I try to read a sequential dataset (FB LRECL(1000)) by using this simple code:# ================================================== count = 0 thefilepath = "//'sa8sb22.resultfb'" count = len(open(thefilepath, 'r', encoding="cp500").readlines( )) print("There are ", count , " lines in the file") # ================================================== I have 133 records in the file, but the above code delivers 1 (one). I suppose, no read is executed.I suppose it is realted to the encoding, but I don't find any better as the cp500.The file is definitive EBCDIC (x'81' for 'a').Any hints pls.?------------------------------Gabor MarkonMainframe ArchitectSelf RegisteredBudapest HU------------------------------

We are currently using a git protocol helper to allow us (in ZMF R&D) to synchronize off platform development, managed by git in a local repo, with the overarching control provided by ChangeMan ZMF. The target ZMF package is presented as remote repo to local git by using a ‘url’ of  ZMF://<target ZMF profile>/<target ZMF package>   For example, we use:   ZMF://PRODZMF/CZMF125     to address package CZMF000125 in our production ZMF subsystem.   We can then use clone, pull/fetch and push  to synchronize change between the local repo and the ZMF package.  The ZMF package is the ‘gold code’. We have put in place local regression checking as part of this support and the git merge process can be used when refreshing the latest code from the ZMF package into the local repo. The protocol helper relies on the use of our zowe zmf cli plugin to communicate with the target ZMF. The zowe zmf cli takes care of managing the ip add

We keep seeing emails that there is a HOTFIX for Log4j Security Issue.  If so, do we have to request the hotfix?#ChangeManZMF

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.

As the Apache Log4j vulnerability (CVE-2021-44228) was disclosed on Dec 09, 2021, your Rocket Open Systems Software for Z (ZOSS) teams have been actively monitoring the issue and assessing its impact on these products.  It has been determined that our ported tools do not contain a version of Log4j that is impacted by the vulnerability. Please feel free to reach out to support or product management should you have any questions or concerns regarding any of the open systems ports for z/OS and the Apache Log4j security vulnerability. ------------------------------Jeff CherringtonVice President, Product Management, Z SystemsRocket Software------------------------------

This sample Python script demonstrates how to call  the ChangeMan ZMF  plugin-in  for Zowe CLI. import osimport sysimport json def print_to_stdout(*a):      print(*a, file = sys.stdout) # get run time parmsfolder = sys.argv[1]comp = sys.argv[2]type = sys.argv[3]package = sys.argv[4] zmf = sys.argv[5] # Print Parametersprint('Running Python Script: ', __file__)print_to_stdout(f"Parameters: Package({package}) Component({comp}) Library Type({type}) Output Folder({folder})") # retrieve component using component-browse-packageprint_to_stdout(f"Retrieving Component: Package({package}) Component({comp}) Library Type({type})")command = f"zowe zmf browse pcomp -c {comp} -t {type} -p {package} --zmf-p {zmf} > {folder}/{comp}.{type}"os.system(command) # retrieve the list of copybooks using component-source-include-locatecommand = f"zowe zmf get csil -p {package} -c {comp} -t {type} --zmf-p {zmf} > {folder}/list.json"os.system(command) with open(f"{folder}/

Got a curl c api based on a previous curl distro.Now I'm trying to rebuild using the current miniconda distro but......IEW2456E 9207 SYMBOL zos_compat_malloc_wrapper UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY. andIEW2456E 9207 SYMBOL gss_release_name UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.amongst a number of other similar missing symbols.Are these objects in Rocket code ? If not has anyone got a suggestion ?------------------------------hank oerlemansSenior Software EngineerHCL America Inc.North Sydney NSW AU------------------------------

Hello,I tried to create  a new conda environment separate from the base. It failed as we don't have a support contract (and don't have access to the secure channel).I activated the base environment to see if I could get a bit further.bash-4.3$ conda activate base(base) bash-4.3$ (base) bash-4.3$ conda info --envs # conda environments:#base * /global/rocket/miniconda(base) bash-4.3$ conda install -c https://conda.anaconda.org/zoss-appdev gitSolving environment: failedCondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://conda.anaconda.org/zoss-appdev/noarch/repodata.json>Our z/OS LPAR doesn't have access to the internet.How can I install the the package via conda without internet connectivity from z/OS?Can I download the package to z/OS (internet to workstation to z/OS) and run conda install?thanks------------------------------Gary GrossiIT Director, Z SystemsAlight Solutions LLCLincolnshire IL United States------------------------------

I have Conda installed and am using /etc/profile for the environment variables for Conda.  I'm trying to execute curl in batch but not having much luck.  I'm using the following JCL.//CURL EXEC PGM=BPXBATCH //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //STDENV DD PATH='/etc/profile',PATHOPTS=ORDONLY //STDIN DD DUMMY //STDPARM DD * sh 'curl --version' /* I keep getting "-bash: curl --version: command not found"  It's not finding the environment variables (PATH, MANPATH, etc). This works: //CURL EXEC PGM=BPXBATCH //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //STDENV DD PATH='/etc/profile',PATHOPTS=ORDONLY //STDIN DD DUMMY //STDPARM DD * sh '/rsusr/conda/envs/default/bin/curl' --version /*What's the magic secret handshake/decoder ring to get curl to execute in batch?  No, I don't want to issue the "conda activate default" command, I want it to use the /etc/profile environment variables I already have set up.------------------------------Michael Babcockz/OS Systems Programmer, SrOneMain Financia

We do not want any post approvers to be added to an emergency change package after it is installed.  The only approval we want is the one defined in the options for unplanned approval list.  Is it possible to prevent exit 9 from adding them?  If so how?#POSTAPPROVER#ChangeManZMF#CMNEX009

We would like JCL Plus to be invoked through the AUDIT process of Changeman.   #ChangeManZMF

Most organizations understand the value of modernizing mainframe application build and test processes, but bridging the open-source vs. traditional mainframe knowledge gap is often a barrier. This example entirely made up of open-source software may help get you started. @Tatiana Balaburkina and @Vladimir Kudriakov recently shared this demo at the Linux Foundation's Open Mainframe Summit, showing an open-source DevOps toolchain driven by Jenkins. The source code, scripts and metadata files used to build this sample application are included.  The 12 minute video demonstrates the toolchain in operation.Let us know what you think and what questions you have below, and do share your approach with the community if you have an existing solution that works for you. Download the example code attached to this post. Watch the embedded video to see the example in action. ------------------------------Peter FandelSr. Director, Product ManagementRocket Software------------------------------

UnicodeDecodeError: 'utf-8' codec can't decode byte 0x94 in position 0: invalid start byte solved by deleting my .netrc file.......would be nice if "something" looked at the tag info and catered for the problem------------------------------hank oerlemansSenior Technical SpecialistSelf RegisteredNorth Sydney NSW Australia------------------------------

Hi,I installed Bash over the free conda channel (version Bash 4.3.48). This version seems to have a problem with its terminal config.The bash version don't read the TERM env correctly.For example:$> export TERM=xterm$> export TERMINFO=/usr/share/lib/terminfo$> echo $TERMxterm$> clear'/u/userid': unknown terminal type.echo $TERMxtermI would guess this bash version reads the homedir env instead of term.Rolling back to the previous Version  fixes the problem.Kind regards,Björn------------------------------Björn SchanzSysprogR + V Allgemeine Versicherung AGWiesbaden Germany------------------------------

Having problem with the following issue: I don't know if I missed something, login as root and I should have all the write permissions.---- installing extra_pkgs to the base env ----conda-repo-cli-1.0.1+2.g39f4600-py_0.tar.bz2:NotWritableError: The current user does not have write permissions to a required path.path: /.conda/pkgs/urls.txtuid: 0gid: 100If you feel that permissions on this path are set incorrectly, you can manuallychange them by executing$ sudo chown 0:100 /.conda/pkgs/urls.txt Here is the log:ROOT:/SYSTEM/var/minirun #>ls -latotal 158496drwxrwxrwx 2 ROOT OMVS 8192 Oct 25 15:20 .drwxrwxrwx 22 ROOT OMVS 8192 Oct 25 15:20 ..-rw-r----- 1 ROOT OMVS 624 Oct 25 14:18 appdev_manifest_1.2.txt-rwxr-x--x 1 ROOT OMVS 81071562 Oct 25 14:06 miniconda-zos-1.2.1-2020-12-23.runROOT:/SYSTEM/var/minirun #>./miniconda-zos-1.2.1-2020-12-23.run -p /var/miniconda********************************************************************************* Miniconda installation script is starting a

I am trashing all of my current miniconda efforts and hoping the old ways still work.Too much 'assumed' lnowledge from the Linux world (bash shell for example) is not in my 30 year z/OS history.  I can stumble around basic commands and super simple scripts, but this miniconda thing is a monster.   I did manage to get miniconda under my $HOME directory and it can query the public channel web site.Creating local environments and attempting to install actual open source (like Perl) failes spectacularly.what the heck is a .so file and why didn't it create them when I defined a new environment?  ../.ffi/*.so files not available or found.How do you select where to install the open source.  At the end of the day what would end up in my General User $PATH variable.I was trying to update my Open software (last done in 2015).   But this way is just not going to cut it.    It all looks simple in the pdf downloaded instructions until it cheaps out with a web link to a conda website for how to lear

Status: DeliveredIncluded in ZMF 8.3Hej ! In our site, we use CMNVPOOL variables at various stages of a package, created  auto-mechanisms that are triggered by the variables, Etc..  At the moment, to maintain the variables it has to be done only within the HLLX environment. I am wondering if we can have a PGM utility, which we can execute via BATCH to Delete, Put, or even Define variables directly into the CMNVPOOL. What do you reckon ? /Flint#CMNVPOOL#HLLX#ZMF

Each z/OS Open Source Language and Tool comes with some manner of open source license. Most, but not all, are licensed under GPL, the GNU General Public License. The license document for each distribution can be found in this location: share/doc/<toolName>/ If you need to read the license for a particular language or tool without downloading and unpacking it, then you must go to the public community pages for that language or tool. The license document included with our distributions is (by law) identical to the license you will find in the public pages. Rocket adds the following additional terms and conditions in the following README file which can be found at the root level of the distribution. Rocket Ported Tools for z/OS ("Program") ============================================================================== See more detailed information in directory share/doc/<toolName>/ ============================================================================== NOTICES

Gidday all, If the first and only release of Git for z/OS you installed on your system is 2.26 or higher you can ignore this post and exit now.  But if you installed releases prior to this, you COULD have problems when moving to 2.26. Prior to 2.26 the z/OS version of Git encoded its database in ISO8859-1 (aka ASCII) but from 2.26 and above the database is now encoded in UTF-8.   This means repos created with the older releases have to be re-encoded.  Rocket has updated Git to do the re-encoding automatically but depending on what characters are used in your repo, the their automatic re-encoding can create false results as seen here. Below is the output of a "git diff" between the master branch with a selected commit e45b11. This was using Git for z/OS release 2.14.Below is the output of the same command run after the master branch has been re-encoded as recommended by Rocket's Git for z/OS 2.26 migration guide. (Note that the output has been truncated, it's actually 805 lines)The outp

Hi, Earlier on this year there were discussions about converting from z/OS Git 2.14 to z/OS Git 2.26 and the change of encoding from ISO-8859-1 toUTF-8.     I'm finally getting around to upgrading to the latest level and was wondering what problems I may expect to find and how easy they are to fix. I've just done my first clone from github that was originally created with git 2.14. The clone completed successfully but when I did a "git status" I find I have 60+ files that git thinks are modified but I have done nothing to them. Is this that I should be expecting ?  If yes,  how much trouble has this caused ?Gary Freestone------------------------------Gary FreestoneSystems ProgrammerKyndryl IncMt Helen Australia------------------------------