Rocket Mainframe DevOps

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------------------------------

A user abend 310 (U0310) can occur when a ZMF Server task is started for a variety of reasons. Knowledgebase article S131584 documents a number of the potential causes/resolution steps and provides a starting point to commence investigation. If this fails to help you resolve the issue, please open a case with the Support team who will be happy to assist.#SupportTip#ChangeManZMF#SupportTips/KnowledgeDocs

Early versions of the ZMF REST API documentation, and a number of the videos generated at the same time, refer to two separate applications, zmfrest and zmfevent, distributed in war files of the same names. In ZMF 8.2 Patch 4 and later, however, only the zmfrest application is provided. Why is this? The very simple answer is that, as mentioned in the ZMF 8.2 Patch 4 Readme file, the zmfevent application was merged into the zmfrest application in that release. However, a more comprehensive explanation can also be found here.#ChangeManZMF#SupportTips/KnowledgeDocs#SupportTip

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

Need compatibility information for ChangeMan ZMF (or ChangeMan SSM, Comparex, StarTool FDM, and StarTool IOO) running on z/OS 2.5? This can be found in S143476.  If an upgrade is required to reach the minimum supported level, we recommend that the very latest patch version of the appropriate product is selected. At time of writing (December 2022) for ZMF that is 8.2 Patch 6. ZMF 8.2 Patch 7 is expected to GA in January 2023 (monitor updates here).#SupportTip#ChangeManZMF#SupportTips/KnowledgeDocs

When installing or upgrading to a new version of ChangeMan ZMF, customers will be presented with three options: Process FULL Product Installation (formerly referred to as ‘FULL’), Install All Available PATCHES (formerly ‘FIX’), and Install Only This Current PATCH (formerly ‘DELTA’). This sometimes confuses the person running the installation. So, what are the differences? - Process FULL Product Installation: This contains all of the software required to install a completely new ZMF environment at the specified software level or to upgrade from a prior version of ZMF. - Install All Available PATCHES: This contains all software changed since the initial version of this release of ZMF was shipped. - Install Only This Current PATCH: This contains all software changed in this patch level only. So, let’s take three examples of customers installing or upgrading to the 8.2 Patch 6 release: - Customer A is currently running ZMF 8.1.4.01 in their environment. This customer should select the firs

2022: Highlighting Customer Success It’s been a busy year for the Micro Focus Application Modernization and Connectivity (AMC) business.   There are far too many highlights to share in this short blog, but I did want to draw special attention to one new and exciting set of resources for modernization enthusiasts—resources which may also help influence future planning as we now look to 2023.  And to help accomplish that, I honestly can’t think of a better set of materials than these new customer success stories highlighting application, process, and infrastructure modernization.  A New Approach to Modernization For those that aren’t familiar with the Micro Focus modernization story, I’d encourage you to take a closer look.  It's a unique approach to IT transformation enabling developers and IT leaders to both run and transform while setting priorities to what, how and where modernization matters for their business and customers. Where agility and speed to market

I'm cloning from a repository based  on a Windows server with files in UTF-8.The repository contains files named XXXXXX.pli I'd like to clone to z/OS with the target codepage IBM-1047, but I cant get it to workI have placed .gitattributes file in the repository and also in the target work dataset,but I get no codepage conversion.Where should .gitattributes be located and are the any other setting there must be switched on/off or set ? Current .gitattributes looks like this: # line endings * text eol=lf # file encodings .cpy zos-working-tree-encoding=ibm-1047 .cbl zos-working-tree-encoding=ibm-1047 .bms zos-working-tree-encoding=ibm-1047 .pli zos-working-tree-encoding=ibm-1047 .mfs zos-working-tree-encoding=ibm-1047 .bnd zos-working-tree-encoding=ibm-1047 .lnk zos-working-tree-encoding=ibm-1047 .txt zos-working-tree-encoding=ibm-1047 .groovy zos-working-tree-encoding=ibm-1047 .sh zos-working-tree-encoding=ibm-1047 .properties zos-working-tree-encoding=ibm-1047 .asm zos-working-tree-enco

Customers sometimes ask how they can diagnose ISPF file tailoring problems that occur in external tasks, such as compile jobs built in a CMNADSP started procedure. This is documented in the section named ‘Debugging Skeletons in Started Task Procedures’ within the ZMF Customization Guide. The 8.2 Patch 6 version of this manual can currently be found here. #SupportTips/KnowledgeDocs#SupportTip#ChangeManZMF

Hi all,I am a bit confused what to download for the free variant.First I seeminiconda-zos-1.2.1-2020-12-23.run which has a corresponding appdev_manifest_1.2.1.txt. In the appdev file mentions python=3.7.0=36Then I seeminiconda-zos-2.0-2022-01-17.run with no corresponding appdev_manifest_2.0.txtQuestions: Is the 2.0 file the one which is based on IBM Python? Shouldn't the 2.0 have a corresponding appdev manifest file? Thanks.-- Manfred------------------------------Manfred LotzKyndryl Deutschland GmbHKelsterbach DE------------------------------

Hello, Installed gzip, curl under zoss-app environment. I am not able to get any information while I search for command man gzip or man curl.  MANPATH=$MANPATH:/minicond/envs/zoss-app/share/man/cat1:/minicond/share/man/cat1 ------------------------------Raju ------------------------------

With ZMF 8.3 currently expected to GA in Spring 2023, what's next for ZMF 8.2? You can find Product Manager Jimmy O'Rourke's latest update here.#SupportTips/KnowledgeDocs#SupportTip#ChangeManZMF

As we continue to support ChangeMan ZMF 8.2 Release, we felt it was important to create a page about the patch update (PU) releases and announcements for new patches as they relate to ChangeMan ZMF 8.2. As a refresher, since the release of Patch Update 5 (PU5) we have removed customizable components from PUs. Only executable components have been part of any PU for the 8.2 release (starting with PU5). This has greatly improved adoptability and provides an easier upgrade path for our customers. We also changed the PU release cadence and moved from a 6 month PU cadence to a more flexible 9-12 month timeframe. This has given customers more time to test as well as stay on a PU longer than before, without having to plan for an upgrade every 6 months. With the new PU cadence, customers have 9-12 months between patch updates to plan for upgrades. Also, as a reminder, we will only issue Hot Fixes and execute OEM compatibility testing against the current / latest PU.  For reference: PU5 (8

As documented in the Known Issue sections of our ZMF Readme files (the 8.2 Patch 6 version can currently be found here), there are two potential causes of user 44 (U0044) abends in ChangeMan ZMF. 1) The most common situation is when users attempt to connect to the ZMF ISPF User Interface (UI) and receive the following response: User abend 44 dec occurred processing command 'CMNINIT '. ***                                                       This occurs when a user is already logged onto another ZMF instance via the ISPF UI and that other instance is running a different version of the product. Disconnecting from one of the ZMF instances should clear the problem and allow the other ZMF instance to be accessed. 2) Alternat

Status: Waiting for VotesWaiting for VotesThe prompt of many TSO messages hinders at work. A reduction would be useful.When triggering operations in ChgMan (eg Promote Jobs, Stagejobs), a relatively large number of TSO messages (depending on the individual Todo steps of the process) are generated as confirmation / notification about the individual steps.   In our opinion, a message for the submit and a final message per triggered process would be more useful here.   If many of these processes are triggered and you want to continue working, then these numerous messages that you have to constantly click away, can be very disturbing.   You can completely suppress these messages for your own user, but this is not ideal, because then you would be 'blind'.   A 'healthy mix' with fewer messages would be good.

Status: DeliveredCMN$$JBL.SKL.txtCurrently, the CMN$$JBL (generate JOBLIB DD skeleton) and CMN$$SEX (generate SYSEXEC DD skeleton) along with CMN$$DSN require modifications to ensure that the correct ChangeMan ZMF load library and REXX exec library concatenations are built, depending on the ChangeMan ZMF subsystem ID. This proposal sets forth to reduce---and likely even eliminate---the need to customize CMN$$JBL and CMN$$SEX, and just have the customizations be done in CMN$$DSN.  My understanding is that CMN$$DSN was created to move all data set specifications---and various scenarios for data set specifications---out of other skeletons to keep the other skeletons simpler.  If there is the need for more complicated logic, then this complicated logic would be in a skeleton such as CMN$$DSN that is meant to be customized anyway.  This way, other skeletons such as CMN$$JBL, CMN$$SEX, CMN$$COE (which uses &SIGYCMP), CMN$$SYL (which uses &SCEESPC, &SCEELK

Prior to ChangeMan ZMF 8.2 Patch 4, components that were locked within a package could only be unlocked by the user who possessed the lock or by administrators. In ZMF 8.2 Patch 4 we added the option to add a new security entity to the application admin parms that allows additional users the ability to unlock components. Further information on this option can be found in the 8.2 Patch 4 Readme file and the ZMF Administrator's Guide, the 8.2 Patch 6 version of which can currently be found here.#SupportTip#SupportTips/KnowledgeDocs#ChangeManZMF

Hello,There is a new vulnerabilty CVE-2022-37454 for "Extended Keccak Code Package Project Extended Keccak Code Package vulnerabilities"Does this affect any Rocket z/OS Tools?Many Thanks!

Questions still occasionally arise regarding the need to run the SERSET job and the purpose of the SERXPTIK module. To summarise: - SERXPTIK is a small, executable module that is loaded into CSA on every LPAR hosting ZMF users or batch jobs. - This module is executed each time a user connects to a ZMF Server started task using the TCP/IP connection method – either explicitly or when technically required (e.g. when connecting across LPARs using Load Balancing Option (LBO) functionality). - It is used in the generation of a Security Server PassTicket for the connecting user or batch job. - This PassTicket is validated by the ZMF Server started task at connection time. - SERXPTIK is automatically loaded into CSA whenever a ZMF Server task is started on an LPAR. - For LPARs not hosting a ZMF Server task, you must run the SERSET job to load SERXPTIK into CSA before any users or batch jobs attempt to connect to any ZMF Server started task from that LPAR. - IPLing the LPAR will result in SERX

Hello,We're having an issue trying to read a z/OS dataset. It works for a USS file. Running Python 3.95 in the base environment.What are we missing?thanks# FileNotFoundError: [Errno 129] EDC5129I No such file or directory.with open("//'xxxxxx.x.xxxxx'", 'r') as f:     print(f.read()) # this workswith open('/u/xxxxxx/python/aws.py', 'r') as f:    print(f.read())

Hi.OpenSSL recently reported critical/high vulnerability CVE-2022-3602 which is a buffer overrun in v3.x that is fixed in v3.0.7.Can you confirm that this vulnerability is not present in the OpenSSL supplied with Rocket z/OS Open-Source tools or any other z/OS tool supplied by Rocket?The "openssl version" command shows OpenSSL at v1.0.2 in Rocket Open-Source tools for z/OS so it would appear that this version is not affected.Thanks.

After updating Miniconda  with miniconda-zos-2.0-2022-01-17.run and appdev_manifest_1.2.1.txt,  Python 3.9.5 was installed in the base environment.A few questions:1)  All of the packages I installed in the "base" environment prior to the update had to be re-installed. Is this to be expected?2)  I created a new environment and installed several packages from my file channel. How do I install Python 3.9.5 into this environment?3)  Using Python 3.9.5, how do I install the boto3 python package? Can I run pip3 install boto3? I saw this message after cancelling the download.WARNING: You are using pip version 21.3.1; however, version 22.3 is available.You should consider upgrading via the '/hewitt/rocket/miniconda/bin/python3.9 -m pip install --upgrade pip' command.Thanks,Gary

A frequent cause of customer problems that we see in the Support team is related to batch JOBs executing on unexpected LPARs. Even when JOBs are actually submitted on the correct, expected LPAR, a variety of factors may dictate that the JOB is routed away to another LPAR for execution. If your problem could be related to a JOB running on an incorrect LPAR, it is always worth taking a moment to confirm that it did actually execute on the anticipated LPAR before progressing investigation. For example, in a JES2 environment, the following kind of message may provoke an assumption that the job actually executed on the LPAR named LPA1:                    J E S 2  J O B  L O G  --  S Y S T E M  L P A 1  --  N O D E  M A C H I N 1 However, the subsequent $HASP373 message shows that the job actually executed on LPA2: 05.29.19 J0703655  $HASP373 USER01J  ST

The scenario is this. Multiple users working on a repo user a has branch A and user b has branch B user a needs to merge branch B into branch A merge fails as branch B is only on the server (remote) rather than local Using Git version 2.26.2-82 The workaround is to : user a does a checkout branch B - this gets it local user a does a checkout branch A - return to the users branch user a can successfully do a git merge I've tried git fetch --all and it does not fetch branch B to the local repo.Thoughts?  Is this a bug in the git version I'm using? Known bug? Other thoughts/suggestions.------------------------------LionelDyck