Rocket Mainframe DevOps

The ChangeMan ZMF 8.3 release introduced the concept of Db2 ‘core’ functionality. This can significantly simplify installation and maintenance of the ZMF Db2 Option for customers who use this functionality to manage package and plan binds only. Customers should review their current usage of the Db2 Option, and their expected future usage of this option, when upgrading to ZMF 8.3 and later releases. Additional information on this functionality can be found in the ZMF 8.3 Readme, Migration and Db2 Option Getting Started Guides. All ZMF 8.3 documentation can be accessed here.#SupportTips/KnowledgeDocs#s/KnowledgeDocs#s/KnowledgeDocss/KnowledgeDocs#s/KnowledgeDocss/KnowledgeDocss/KnowledgeDocs#ChangeManZMF

When doing a promotion with the 'Display Overlay Page' option selected, the ‘Promotion Overlays’ panel is not being displayed. If you do the promote again and DO NOT select ‘Display Overlay Page’ the ‘Promotion Overlays’ panel is now displayed. The selection of the ‘Display Overlay Page’ option is functioning backwards/reverse of how it should work.    Full article: https://portal.microfocus.com/s/article/KM000017289#SupportTips/KnowledgeDocs#ChangeManZMF

In the CMNENTFY ALFFLTR member you have the option to include (‘INCL’) and exclude (‘EXCL’) ZMF LOG events by application and/or application masking. These filters are not working as expected and all ZMF log events for all applications are being processed. Full article: https://portal.microfocus.com/s/article/KM000017447#ChangeManZMF#SupportTips/KnowledgeDocs

Hi  When I edit a source (copybooks have been downloaded) , I'm getting the following messages : So I have to set a propertygroup for the zopendeditor, but with V3 of the Z Open Editor, the json zopeneditor.propertygroups is not allowed anymore It seems they use zapp yaml files now to describe the syslib My questions are : - When working with the ZMF Explorer, what is the root of the Workspace - Does anyone has an example of such a yaml file - Where should the yaml file placed - If the workspace is the location of the folder C:\\Users\\<userid>\\.zmf\\<zmf instance>\\packages\\<packageID>\\<program>  can't the yaml file be created by the ZMF Explorer? Thank you#ChangeManZMF

Status: Under ConsiderationTo enhance the source-to-load tracking mechanism to take into account SSV versions (and anything else we might consider useful) as an option (i.e. allowing the existing mechanisms to co-exist) is likely to be a sizeable undertaking. We will need to make sure the solution is generic. The current development release is full so we will have to consider this further at a later date (i.e. for inclusion in a ZMF 8.3 patch release after patch 1). CR 307002 has been opened to track this request and we will be in contact with Johan (the requester) to discuss the design as soon as time becomes available. When enabling staging versions one can give a freeform text after each change of a component. We have customised Changeman in such a way that this freeform text has a standard naming convention, using HLLX exits BULD00XC, BULD01XC, CKOT00XM and CKOT01XM.  The label will look like  nnn-FNC(APPLnnnnnn-vvv) opt. text Where nnn is a sequence number increment

Hi, I would like to know how is the extension of file determined. When I download a PL1 program (SRC type in ZMF with language PL1) it nicely ends up with the extension PLI the included copybooks receive the extension INC When I download a component of lib type ERX (which are REXX components) it receives the extension TXT Where can I direct a lib type to a specific file extension when needed Thank you Johan#Fileextension#VSCode#ChangeManZMF#ZMFExplorer

We are testing upgrade in our Jenkins development environment with following version changes   Jenkins Master version from v2.346.2 to 2.387.1 Git client plugin from v3.11.2 to v4.2.0    Git Version z/OS not changed 2.14.4_zos_b09   We have setup up Jenkins Agent as a started task Setting up the CI Pipeline Agent on IBM Z as a Started Task   We see following errors   Jenkins Console:   org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id: fatal: bad config line 1 in file .git/config     STDERR info Jenkins Slave Started Task z/OS:   Exception caught during execution of command '<gitInstallFolder>/git/bin/git, config, --system, --edit¨' in '<gitInstallFolder>/git/bin', return code '128', error message 'fatal: Invalid path '/rsusr': EDC5129I No such file or directory.     Check System config location When we check system config information we receive following error git config --list --sys

A new hotfix build of ChangeMan ZMF for Eclipse (ZMF4ECL) 8.3 is now available for customer use. ZMF4ECL 8.3.0 Hotfix 002 (build 681) resolves the following issues: OCTCR46A298001 - Package creation uses incorrect default scheduler OCTCR46A285001 - Promotion overlay message ‘CMN3252A’ prevents promotion from completing OCTCR46A287001 - Previously promoted components not displayed on ‘Demotion Options’ screen OCTCR46A297001 - Export of CMN990 report failing to save file OCTCR46A267003 - Revert of a DIS package not possible with ZMF4ECL on ZMF Development Site  We recommend customers either running or upgrading to ZMF4ECL 8.3 open a case with the Support team requesting a copy of this hotfix.#SupportTip#SupportTips/KnowledgeDocs#ChangeManZMF

During startup of a ZMF 8.2 Patch 4 task a S0C4-10 abend was encountered in module SERXMSIP at offset 76C. The abend is accompanied by a SER0953E message indicating that processing failed in the PARM#UPD function. Full article:https://portal.microfocus.com/s/article/KM000017145#SupportTips/KnowledgeDocs#ChangeManZMF

A new ZMF4ECL user receives the following message when attempting to logon to a ZMF Server: NumberFormatException - For input string: "ú³…". The problem is caused by specifying the wrong port numbers in the ZMF4ECL Server folder properties. Full article: https://portal.microfocus.com/s/article/KM000017231#ChangeManZMF#SupportTips/KnowledgeDocs

When executed against an existing package component, the Component History function behaves differently in the ZMF4ECL and ZMF ISPF user interfaces:   In ZMF4ECL. right-clicking on a component and selecting View – Component History displays history for the current package only.  In ISPF, navigating to option 1.6.2 or 5.S2, listing the same package and typing ‘H’ next to the same component results in all cross-application component history being displayed. ISPF is the more user-friendly behaviour. Full article: https://portal.microfocus.com/s/article/KM000017227#ChangeManZMF#SupportTips/KnowledgeDocs

zowe 2 introduces a major change to the way profiles are now created. Gone are the individual profiles for each subsystem. Also gone now is the need to saved userids and password in clear text in those profiles which was clearly a security issue. Now, credentials are saved in the operating systems secure credential storage. As a result, the old zowe supplied secure credentials storage' plugin is no longer required. To get a better understanding of zowe 2 profiles, please refer to this Medium blog post -  Zowe CLI — Getting Started, Made Easy! zowe 2 profiles are stored in a zowe.config.json file that resides in the <homedir>/.zowe/ folder..Also stored along with the profile is a zowe.schema.json file. (This file should never be changed). zowe 2 profiles no longer contain any user identifiable information. This allows an admin to create a zowe.config.json profile file and distribute that file to users who then do not need to know any particular settings. Instead, the use

Online ChangeMan ZMF documentation can be found by following various different links on the Micro Focus Support site or by clicking here.  By default, only the documentation for the latest release of ZMF is displayed on this screen. However, clicking on the ‘More’ dropdown button allows customers to view the documentation associated with earlier releases of ZMF, too.#SupportTips/KnowledgeDocs#ChangeManZMF#SupportTip

When ending a ZMF ISPF edit session, a user sees the following type of screen: CMNSTDWN Serena(R) ChangeMan(R) ZMF Down Command ===> Unable to establish session with ChangeMan ZMF Started Task for Subsystem ID "T" . User disconnected from SerNet If you have Load Balancing enabled, contact your ChangeMan ZMF Administrator to have ChangeMan ZMF for Subsystem ID "T" started on one Logical Partition at your installation. If yo

When creating a package in ZMF4ECL, if the ‘No implementation instructions’ option is selected the package is always generated with the Manual scheduler option. This is regardless of the ‘Default job scheduler’ specified in application admin options (A.A.1 Part 2 of 4).Issue recreated running against both 8.2 Patch 7 and 8.3 Server environments. Full article: https://portal.microfocus.com/s/article/KM000016884#ChangeManZMF#SupportTips/KnowledgeDocs

Attempts to export a ZMF CMN990 report fail with no visible error messages being issued to the user. An 'Unhandled event loop exception/java.lang.NullPointerException' error message can be seen in the workspace .log file. At least some other reports, e.g. a CMN110 report, can be saved without any problems. Full article: https://portal.microfocus.com/s/article/KM000016877#SupportTips/KnowledgeDocs#ChangeManZMF

In the following, when the HLLX DETACH is issued there is the CMNx482I message, but it is not followed by ‘CMNx483I CMNSTART Termination of HLL exit address space complete’.  Instead, it has the message ‘CMNx499E HLLX address space is no longer active.’:                   MODIFY CHGMAN.CHGMAN,CMN,DETACH,HLLX SER0850I Operator command: CMN,DETACH,HLLX CMN1482I CMNSTART Termination of HLL exit address space requested. CMN1499E HLLX address space is no longer active. IEA995I SYMPTOM DUMP OUTPUT 738 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011 TIME=08.22.24 SEQ=37663 CPU=0000 ASID=0458 PSW AT TIME OF ERROR 078D0000 B537E8A0 ILC 4 INTC 11 ACTIVE MODULE ADDRESS=00000000_35379000 OFFSET=000058A0 NAME=CMNSTART

The use of the StarTool FDM STARBAT COPYMBR/NEWMBRS parameters generates invalid PDS member names when and asterisk (*) is used for masking. For example, the intention of the following is to replace the last two characters of the member name, currently ’57’, with ‘60’:   DD01 COPYMBR MEMBERS=*57,NEWMBRS=*60, Here are the input member names:   MEMBER57 MEMBE57 MEMB57 MEM57 ME57 Here are the expected member names to be generated: MEMBER60 MEMBE60 MEMB60 MEM60 ME60 When using the asterisk (*) for masking, the member names generated are invalid: *60BER57 *60BE57 *60B57 *6057 *607 Full article: https://portal.microfocus.com/s/article/KM000015706#Comparex#StarTool#SupportTips/KnowledgeDocs

Is anyone running Changeman ZMF V8.1.4 and z/OS 2.5?     We plan to upgrade changeman,  but not before the mainframe systems team upgrades to z/OS 2.5. We will standup a test changeman environment on the test box when they upgrade to z/OS 2.5 to see if we have any issues#ChangeManZMF

The very simple answer is that they do not differ, and have not differed for a very long time (i.e. 20+ years). As documented in the “Creating a Change Package” section of the User’s Guide (the 8.3 version of which can currently be found here): “...There are no processing difference [sic] between super and complex change packages...” Both terms have been retained simply to ensure that customers can stick to the name with which they are comfortable. Technically they are identical.#ChangeManZMF#SupportTips/KnowledgeDocs#SupportTip

Something changed in git in terms of file encoding.These files were created using this code:cmd = 'cd' localrep'/'zigirep ,    '&& git show' hcommit':'element ,    '>' filewhere localrep/zigirep, hcommit, element and file are all variables. This is what I have on my work system for this use case using git version 2.26.2-78 t IBM-1047 T=on -rw-rw-rw- 1 SPLBD SYS1 1875 Feb 1 05:03 CHGSTR But with git version 2.26.2-84 I get this: t ISO8859-1 T=on -rw-rw-rw- 1 LBDYCK ZOWEDEV 1875 Feb 1 08:06 CHGSTRTo summarize this - with git 2.26.2-27 the git show generated file is tagged as IBM-1047 and then with git 2.26.2-84 it is now tagged as ISO8859-1.Why the change and how can I control it?

Request to help with cics TS 5.6 compatibility for the below micro focus products.   ChangeMan SSM       8.3.2 ChangeMan ZMF       7.1.2 Mainframe Access      3.1.0 Sernet  8.4.0#ChangeManSSM

It is worth stressing that use of IBM’s Application Transparent Transport Layer Security (AT-TLS) product is the only supported method of securing connections to ZMF-related applications that run in the supplied Apache Tomcat address space. This includes the REST services (zmfrest.war), zMobile (zmobile.war), and the base ZMF web services (zmfws.war). Whilst it may technically be possible to run secure versions of some of these applications in other ways, e.g. by implementing native Tomcat SSL functionality, this is not a supported configuration. If problems are experienced running in such a manner it may be necessary to switch to AT-TLS before assistance can be provided. This AT-TLS requirement is documented in the ChangeMan ZMF REST Services Getting Started Guide, the 8.3 version of which can be found here, but also applies to the other applications listed above.#SupportTip#ChangeManZMF#SupportTips/KnowledgeDocs

A REST API webhook is configured for package audit in a German-speaking environment, e.g. one using codepage 1141 in TSO emulator sessions. The expected EVENT50 step is included in the audit job and appears to complete successfully. I.e. it ends with a step RC=0 and all of the usual SYSPRINT messages ending with: … Results follow: --------------- HTTP/1.1 200 Processing complete with return code: 00 However, the Tomcat task shows no sign of the transaction being processed and the procedure specified by the target URL is not executed. Full article: https://portal.microfocus.com/s/article/KM000016535#ChangeManZMF#SupportTips/KnowledgeDocs

Although referenced in the ChangeMan ZMF 8.3 Readme, it is worth stressing that 5 new package status values were introduced in this release of the product. They are as follows: AIP - Approval in progress XDS - Distribute failedXIN - Install failed XBK - Backout failedXRV - Revert failed Customers should consider these new values when upgrading any custom processing or routines that look at the ZMF package status field.#ChangeManZMF#SupportTip#SupportTips/KnowledgeDocs