Rocket Mainframe DevOps

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

Customers sometimes report occurrences of the following type of message being issued to users who are running audit: CMN2622I - I/A table out of date. Cannot find BUN for library type {libtype} in application {appl}. This may result in invalid synchs. The cause of and resolution to this message is documented in the ZMF Messages Guide, the 8.2 Patch 7 version of which can be found here.  A general rule-of-thumb is that the ZMF Impact Analysis (I/A) table needs to be synchronized whenever changes are made to baseline library definitions in ZMF ISPF Option A.A.B. To synchronize the I/A table, the distributed IMPACT and LDSLOAD jobs must be executed. If unsure whether or not synchronization is required after making a change to baseline library definitions it is best to err on the side of caution and run these jobs. Although not strictly necessary if IMPACT and LDSLOAD are always run after every change to baseline library definitions, it may be beneficial for customers to also consider

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                                                      

Article opened to explain potential causes of the ZMF Tomcat started task issuing messages like 'Subscriber File //DD:ZEVENT must be type HFS', 'Subscriber File set to !Not Found' and 'Subscriber File null not available'. Read full knowledge article for resolution#ChangeManZMF#SupportTips/KnowledgeDocs

A customer encountered the following abend when running a package audit job: IEA995I SYMPTOM DUMP OUTPUT 892 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000010 TIME=07.26.03 SEQ=05610 CPU=0000 ASID=0091 PSW AT TIME OF ERROR 078D1000 97855B20 ILC 2 INTC 10 ACTIVE MODULE ADDRESS=00000000_17854658 OFFSET=000014C8 NAME=CMNBINDN DATA AT PSW 17855B1A - 18F54140 40020E4E B24900F1 GR 0: 8300C2E4 1: 179603B8 2: FFFFC2E4 3: 00000001 4: 17819BFC 5: FFFFC2E4 6: 1A4C2BE0 7: 1A4C2C74 8: 17955BE0 9: 179603B8 A: 17E06082 B: 17855658 C: 9785

The production ChangeMan Rest Services were enabled and working. The production TOMCAT server was then recycled for the first time about four weeks later.  Since then, the Rest Service events are not being received at the endpoint. The compile JCL Event step returns the response status code ‘200’ (success).  When testing the webhook it is returning a ‘501’ exception 'Header name may not be null’ error.  The following error message was found in the Tomcat log: 2023.02.11 22:51:34 ZMFRESTP java.lang.IllegalArgumentException: Header name may not be null at org.apache.http.util.Args.notNull(Args.java:54) Note:  ZMF task is recycled every day. Full article: https://portal.microfocus.com/s/article/KM000014863#SupportTips/KnowledgeDocs#ChangeManZMF

This is a knowledgebase copy of the information originally published in the New Features section of the ChangeMan ZDD 8.2 Patch 7 Readme file. Full article: https://portal.microfocus.com/s/article/KM000014672#SupportTips/KnowledgeDocs#ChangeManZMF

A frequent subject of cases opened with the Support team relate to batch jobs, TSO users, external routines, etc., failing with SER8203E impersonation failure problems. For example, the following message or variations of it: SER8203E User xxxxxxx is not authorized to impersonate user yyyyyyy KB article S133110 explains this processing and documents several options to resolve such problems.#ChangeManZMF#SupportTip#SupportTips/KnowledgeDocs

How are other shops implementing the vendor supplied newcopy or phasein process? Specifically how are you handling multiple CICS regions in a plexed environment? Do I have to maintain a table in an ISPF skeleton to build multiple jobsteps...one for each cics region?#ChangeManZMF

Customers sometime question why a request to scratch a like-SRC component fails to also remove the ‘associated’ or ‘ILOD’ components, e.g. LOD, DBR, etc., from the relevant baseline library. Generally this can occur for one of two reasons: 1. Global Admin option ‘Auto scratch load member with source’ is disabled. This option was introduced in the ZMF 8.1 release. When enabled, it will automatically delete all components associated with the SRC component whenever that is possible (see point 2 below). This option is documented in the ZMF Administrator’s Guide, the 8.2 Patch 7 version of which can be found here.  2. The SRC component was last built on a release prior to ZMF 8.1 and the last package to baseline the SRC component has been removed from the package master file, e.g. via ZMF housekeeping/ package aging. Prior to ZMF 8.1, associated component information was held in package records rather than component records. If the package records disappeared for any reason, such as re

Hello,  How do I know which version of Apache Tomcat for zOS is included with the ChangeMan ZMF Rest Services v8.r2 patch 07 installation? I know the vanilla Tomcat 8.5.6 distribution is included in ChangeMan ZMF Rest Services v8 r2 patch 04 and patch 05 and I would like to confirm if is the same version for v8 r2 patch 07 or it’s a version a newer version. Thanks Regards#ChangeManZMF

Running ZMF 8.2 Patch 5, which uses ChangeMan SSM v8.5.2, and turning on SSV function (staging Versions) for the first time.   Only one application testing SSV at this time.  Tested with several library type components and all 'hang' after entering the SSV description and trying to do a save.  'Hang' condition also occur trying to do the ‘VC’ command to display versions for a component. Full article: https://portal.microfocus.com/s/article/KM000014070#ChangeManZMF#SupportTips/KnowledgeDocs

Whenever the ChangeMan ZMF installer is executed, it will build a set of batch commands that will execute the FTP transmission of the files to the mainframe environment. For a variety of reasons some customers are unable to run either the installer or the generated batch script FTP commands. This can raise questions related to the dataset attributes that are required when uploading the new files to the mainframe. The vast majority of uploaded datasets will be in TSO XMIT-format, hence require transmission to DSORG=PS, RECFM=FB, LRECL=80, BLKSIZE=3200 (or any appropriate multiple of 80) datasets. However, some, such as the *.WAR files, need to be uploaded to DSORG=PS, RECFM=U, LRECL=0, BLKSIZE=3060 datasets. Reviewing the FTP commands generated in the FTP.input file can help here. Each set of transmitted files are preceded by the relevant commands and literals that define the transmission type (i.e. binary or ascii) and the target dataset attributes.#ChangeManZMF#SupportTips/KnowledgeDo

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

Program CMNVSRVC executes exactly the same underlying ChangeMan ZMF Services as its public-facing equivalent, the XML Services (i.e. programs SERXMLxC). Several of the ISPF skeletons (skels) shipped with the product execute required services using CMNVSRVC rather than SERXMLBC or any of its SERXMLxC counterparts.The XML Services and their associated tags are fully documented in various product manuals and KB articles. However, the CMNVSRVC keywords used in the distributed skels are not documented. For various reasons, customers may need to verify or customize the shipped skels to investigate issues and/or include additional parameters/keywords that are required in their environment.  Full article: https://portal.microfocus.com/s/article/KM000013873#SupportTips/KnowledgeDocs#ChangeManZMF

Article to explain potential causes of a ‘Logon Error or Invalid CMN port specified...’ error message being issued when connecting to a ZMF Server started task. Possibly accompanied by LIC0033E & LIC0063E messages in the ZMF Server started task. Full article: https://portal.microfocus.com/s/article/KM000013900#ChangeManZMF#SupportTips/KnowledgeDocs

An environment is configured with the RACF option PASSWORD(NOMIXEDCASE) – “MIXED CASE PASSWORD SUPPORT IS NOT IN EFFECT” specified. If a user attempts to login from any off-mainframe interface (e.g. the REST Services API web app, the Client Pack UIs (ZDD or ZMF4ECL), etc.) with a lower or mixed-case RACF password phrase, which is always case sensitive despite the above option, rather than a password they fail with the following type of error message: ICH408I USER(USER001 ) GROUP(SUPPORT ) NAME(SUPPORT USER ) LOGON/JOB INITIATION - PASS PHRASE IS NOT VALID Problem originally reported for the REST Services API web app running against an 8.2 Patch 5 ZMF Server environment. Full article: https://portal.microfocus.com/s/article/KM000014053#ChangeManZMF#SupportTips/KnowledgeDocs

A new Readme file will be produced for each release of ChangeMan ZMF and the ChangeMan ZMF Client Pack (i.e. ZDD and ZMF4ECL) user interfaces. The Readme file contains New Feature and Fix information related to that specific release of the software. It will also contain links to KB articles containing similar information for prior patch releases. If your upgrade is skipping any interim patch levels, please take the time to review changes in the interim releases as well as the version to which you are upgrading. For example, if you are moving from ZMF 8.2 Patch 5 to 8.2 Patch 7, please click on the links contained in the ‘New Features and Fixes in ChangeMan ZMF 8.2 Patch 6’ section. This will hopefully prevent any surprises that may be encountered during testing or after upgrade to the new product release.#SupportTips/KnowledgeDocs#SupportTip#ChangeManZMF

Hi, I have some packages staying in APR status after approval (no error in distribution).I read It maybe caused by the influence of asid parameters in the file tailoring service. Did I well understand ?If Yes :1/ please, could you tell where I can verify my current ASID ?because when i do /f jobname,ASIDSthe response is SER0851W Unrecognized operator command ignored: ASIDS2/ please, where can I find the sernet keyword option ASID at startup?3/ Please, Can you tell me about this command : /F jobname,ASID=(64,30) ? Best regards.#ChangeManZMF

Our changeman Admin (and only Admin) left abruptly and it looks like i'm it now. There is a parm SITEADMINS That is followed by his RACF Id.    I can't find anything in the manuals about this.  Can I put additional ones there like XX03,XX15,XX36? Or do I need a new line for every SITEADMINS statement#ChangeManZMF

Prior to the 8.2 Patch 3 release, the ChangeMan ZMF for Eclipse (ZMF4ECL) Client pack user interface required installation of the ZMF Web Services (zmfws.war) in a web application server environment of choice. Changes in 8.2 Patch 3, however, removed this requirement and the following is documented in all ZMF4ECL Readme files since that release: “IMPORTANT! ZMF for Eclipse 8.2 Patch 3 and later releases have removed the dependency on ZMF Web Services. This simplifies the installation and configuration process as well the set-up process for Secure Sockets Layer (SSL) connections.” Some of the remaining ZMF4ECL documentation still currently refers to the need for the separate installation of zmfws.war. This will be updated in due course and any references to zmfws.war for use by ZMF4ECL can be ignored in the interim.#ChangeManZMF#SupportTips/KnowledgeDocs#SupportTip

Hello,  Please, could you tell me how are these files different and what is their meaning? CMNCMPNL (Long-Name Component Master) and CMNCMPNT (Short-Name Component Master) Many thaks  Regards Manuel#ChangeManZMF

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

The list of defects that have been addressed in the ChangeMan ZMF 8.2 Patch 7 Client Pack user interfaces. Full article: https://portal.microfocus.com/s/article/KM000013396#ChangeManZMF#SupportTips/KnowledgeDocs

The list of defects that have been addressed in the ChangeMan ZMF 8.2 Patch 7 release. Full article: https://portal.microfocus.com/s/article/KM000013397#SupportTips/KnowledgeDocs#ChangeManZMF