Rocket® ChangeMan® ZMF

Have you ever had the need to change a module in an active ZMF Server started task at a really inconvenient time? For example, to install a product hotfix or a new assembler exit whilst an important release or package is being installed? You do not want to restart the task to pick up the new module but you really need it implemented as soon as possible.If so, take a look at the REFRESH modify command that is documented in the ZMF Installation Guide. We should stress that the REFRESH command cannot be used for all modules that are active in the ZMF Server task, can fail (make sure you see a RC=0 in the task's SERPRINT response), and that we would always recommend restarting the Server task if that is possible. However, this command may just come in useful if you were to find yourself in such a position in the future.#ChangeManZMF#SupportTips/KnowledgeDocs

I want to use zowe to create a package and I need to know what options to use for the site/install date section.  There are no options that match those used by XML or REST services. I'm also curious about the spelling of --applmame.  I thought it was a typo but that is the spelling that works. #ChangeManZMF

Version 2 of the ZMF cli plugin for Zowe provides support for Zowe V2. To install an advance version of Zowe V2, please visit the Zowe website location Zowe VNext   Zowe V2 is scheduled to be generally available at the end of February 2022. A version of the ChangeMan ZMF cli plugin for Zowe Version 2 is available and if you are interested in receiving this version  - please let us know by responding to this thread.  Installing zowe V2 and then installing the ZMF cli plugin V2, will enable the features that are available within zowe V2. This includes: - Support for daemon mode   Daemon mode preloads node modules and improves performance when issuing mulitple zowe commands. Daemon mode is enabled by issuing the command:     zowe daemon enable Once enabled, daemon mode will remain in effect across system restarts until it is subsequently disabled. Should you at any future time wish to disable daemon mode, issue the command:   zowe d

Status: Already OfferedIf the existing exit points don't serve your purpose please let us know. Currently there are no exit points for the stage from Development function.#ZMF#Build#ZMF4ECL

Hello, we are planning to update our mainframe to z/os 2.5. Is it possible to run Changeman ZMF 8.2.3 with z/os 2.5? We use following products:     Changeman DB2 8.2.3     Changeman ERO 8.2.3     Changeman M+R 8.2.3     Changeman ZDD 8.2.3     Changeman ZMF 8.2.3 Kindly regards, Jens Poser#ChangeManZMF

When the CICS NEWCOPY function executes a batch job to communicate with CICS transaction SEML, if the NEWCOPY function fails the job ends with RC=0 and no error message is written to SYSPRINT. Full article: https://portal.microfocus.com/s/article/KM000004966#ChangeManZMF#SupportTips/KnowledgeDocs

CMN990 report is using the obsolete EVNTSRVR ADMIN LIST service when it should be using the RESTSRVR ADMIN LIST service. Full article: https://portal.microfocus.com/s/article/KM000004931#ChangeManZMF#SupportTips/KnowledgeDocs

ZMF4ECL 8.2 Patch 6 still has references to LOG4j libraries 2.11.1 when it should be using 2.17.1 Full article: https://portal.microfocus.com/s/article/KM000005115#ChangeManZMF#SupportTips/KnowledgeDocs

Using ZMF4ECL 8.2 Patch 6 to attach a package to an ERO Release is incorrectly attaching the package to the wrong release (not the one selected). Full article: https://portal.microfocus.com/s/article/KM000005096#SupportTips/KnowledgeDocs#ChangeManZMF

In ZMF 8.2 Patch 6 when attempting to checkout a component from a baseline 'minus' level and you leave the component name blank, you get a S0C4 abend in module CMNVNSRD @ OFFSET=000007E0. Full article: https://portal.microfocus.com/s/article/KM000004797#SupportTips/KnowledgeDocs#ChangeManZMF

Using the XML service PACKAGE SERVICE PRMLOCK to lock a package from being promoted to the ‘locked’ promotion site is not working. Full article: https://portal.microfocus.com/s/article/KM000004415#ChangeManZMF#SupportTips/KnowledgeDocs

Micro Focus Universe, our premier customer event of the year, taking place March 23-24. Virtual for 2022, the benefits for our Application Modernization and Connectivity (AMC) customers are real.  Hundreds have registered to see the latest market trends, innovations, and customer stories. We’ve rounded up the AMC sessions below—browse the keynote, breakout, and live studio sessions to find what you’re looking for to run and transform your organization. Take a look and be sure to book your spot at Universe here.  Day 1  Track Keynote—AMC: Provide Value at Each Step of the Journey In this AMC track keynote, Neil Fowler, Micro Focus Senior VP and General Manager will share the latest on mainframe modernization, COBOL development, mainframe access and security, as well as ecosystem investments enabling new opportunities for application modernization in the cloud.  Kill It with Fire: Manage Aging Computer Systems (and Future Proof Modern Ones) Join us for an exclusive

HLLX server started getting 'CEE0374C CONDITION=CEE3201S TOKEN=00030C81' and 'CEE0374C CONDITION=CEE3204S TOKEN=00030C84' messages. Full article: https://portal.microfocus.com/s/article/KM000003870#SupportTips/KnowledgeDocs#ChangeManZMF

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

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

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

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

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

Status: DeliveredThe 8.3 CR will not be used as this can already be accomplished as of 8.2 patch 5.C:D transfer can be speeden up, during remote promote by adding select cards into the instreamskeleton CMN$$NPM )SEL &LTYPHFS NE Y                                                    CPY&LIBTYPE COPY FROM(PNODE DSN=&STGLIB..&LIBTYPE -     )CM )CM  Only transfer the selected members in case of selective promote              )SEL &PROMACT EQ P  AND  &PROMFUN EQ SELPROM                                 SELECT ( -                 )DOT RPMTB&LIBTYPE                                                                    &CMPNAME. -       )ENDDOT RPMTB&LIBTYPE                                                               ) -                 )ENDSEL &PROMACT EQ P  AND  &PROMFUN EQ SELPROM     )CM                                                                  DISP=(SHR)) -                                                         TO (SNODE DSN=&RMTLIB..&am

Status: DeliveredCompleted in 8.3Within the ChangeMan ZMF Administrators Guide, there is an “Enabling the Network Data Mover” section that discusses taking a copy of the #NDM member from the CMNZMF CNTL file, and then following a few steps. In this enhancement request, I’m proposing that we streamline this process a bit. It appears that we have an opportunity to make a ChangeMan ZMF upgrade (or even an installation) a little more seamless when it comes to ChangeMan ZMF systems configured to use NDM (Connect:Direct). Instead of putting a copy of the #NDM member into the custom CMNZMF CNTL library, changing the “$/” to “./”, and specifying the correct “DSN=somnode.NDMPLIB” (i.e. &NDMPLIB) library before running the JCL that uses PGM=IEBUPDTE, why not have the NDM PROCESS members be built within the ChangeMan ZMF skeleton? The way I see it, the #NDM member needs to be run to add NDM PROCESS members against each node that NDM (Connect:Direct) will be running in. This means that mul

Status: DeliveredThis has been delivered in ZMF8.3 CR 131927 covers this idea.Duplicate Components in same CMN Release - but different packages - should be reported in TestArea - even if no Checkin is done yet.We had the case - where 2 programmes have create a new component with the same name - but in different application-packages (and different applications). The more often case is - that the same component is in different packages of the same application. The problem was - that ERO TestArea does only report this - after the first has finished the work - and went to Area Checkin. I would be much better, if ERO TestArea could already report duplicate components in different packages - as early detection. To solve this problem later - is always more effort.

Status: DeliveredThis is completed and will delivered in ZMF 8.2 patch 6.see belowFrom ChangeMan(R) ZMF Primary Option Menu please select "Release", afterwards search in "Release List Selection Parameters" an appropriate Release. Within "Release List" please chose via "AR" (AR Area Functions). Thereafter you should be in "Release Area List". Please type "PH" for "PH Promotion History" and you will get a long list with items of "Count Package Date Time User Status History". The only possible Command are: "Invalid Command - The only valid input commands are CANCEL and LOCATE.". It would be helpful to get a "sort" command as well as a "search" command" (e.g. for field Package / User / Status. It would be really helpful to get this because otherwise you have to press "down" plenty of "down"s to find what you search if the default-search isn't what you n

Status: Already OfferedCurrent REST-API  only provide read-only services.In order to manage full Package and Component lifecycle from a CI/CD perspective, we would welcome the introduction of  REST-API Services which allow us update of package and component properties in ChangeMan ZMF. Leone CalderoneUBS Solution AG Switzerland  #REST-APIservices