Rocket Mainframe DevOps

The ChangeMan ZMF 8.3 Migration Guide mandates rebuild (i.e. re-assembly and re-link/re-bind) of all assembler exits (i.e. CMNEXnnn modules) in the section named 'Customize Other Version 8.3 Components'. Changes in ZMF 8.3 make this especially important when upgrading to this specific release. Full article: https://portal.microfocus.com/s/article/KM000015628#SupportTips/KnowledgeDocs#ChangeManZMF

Problems exist attempting to use the zMobile web application when the Tomcat task is running in a 'Virtual IP Address' (VIPA) environment. Full article: https://portal.microfocus.com/s/article/KM000015740#SupportTips/KnowledgeDocs#ChangeManZMF

ChangeMan ZMF 8.3 was released to customers on 15th March 2023. The software can be downloaded here. The documentation for the base product can be accessed here and the Client Pack documentation here.#ChangeManZMF#SupportTip#SupportTips/KnowledgeDocs

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

The list of defects that have been addressed in the ChangeMan ZMF 8.3 Client Pack (i.e. ChangeMan ZDD and ChangeMan ZMF for Eclipse) user interfaces. Full article: https://portal.microfocus.com/s/article/KM000014846#ChangeManZMF#SupportTips/KnowledgeDocs

Two problems have been identified in CMNEX009 processing running under the ZMF 8.3 release:1. The site table is blank when CMNEX009 is executed by the freeze function.2. Incorrect notification vehicles are being assigned to CMNEX009-added approval entities  Full article: https://portal.microfocus.com/s/article/KM000015311#SupportTips/KnowledgeDocs#ChangeManZMF

Customers who use the XML Services interface to customize ChangeMan ZMF product behavior or to integrate other applications with ChangeMan ZMF need to know about changes, additions, or deletions to the XML Services or their subordinate request and result tags from release to release. Full article: https://portal.microfocus.com/s/article/KM000015286#ChangeManZMF#SupportTips/KnowledgeDocs

Customers who use, or wish to use, the XML Services interface to customize ChangeMan ZMF processing require access to detailed, release-specific documentation covering the services and tags that are available to them. Full article: https://portal.microfocus.com/s/article/KM000015285#ChangeManZMF#SupportTips/KnowledgeDocs

The COBOL copybooks associated with 'yellow' XML Services (see Additional Information for details) are not distributed with the shipped ChangeMan ZMF installer. Full article: https://portal.microfocus.com/s/article/KM000015287#ChangeManZMF#SupportTips/KnowledgeDocs

Delete the components for a library type found in an existing package (ex: JCL).  Delete the library type baseline and library type definition from the application (Note: the deleted library type shared the same baseline with another library type).  Run the IA Extract followed by LDSLOAD.  Baseline the package where the component was deleted and you get the following error for the application and library type you deleted: ChangeMan(R) ZMF CMNDSPTM - 8.2 Patch 6 2023/03/15 16:28:36 Baseline ripple I/A dataspace maintenance for package TEST000004 Baseline information in I/A dataspace not current, unable to find BUN for appl/libtype: TEST/JCL You now need to run CMNIA000 to synchronize your I/A database with your baseline. Full article: https://portal.microfocus.com/s/article/KM000015431#ChangeManZMF#SupportTips/KnowledgeDocs

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

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

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