Rocket Mainframe DevOps

I'm a bit confused about the instructions for upgrading Git from 2.14 to 2.26.There are some notes:Once you change a repository with Git for z/OS 2.26.2, this repository won't be compatible with previous versions of Git for z/OS. It is vital that entire team will move to the new version of GitandWhen you clone the repository with Git for z/OS 2.26.2, you need to run git status command. You might see that Git marks some files with the attribute as modified, even if you didn't modify them. ...We recommend to update the files in the index (commands: git add ; git commit).Typically different people will be working with separate clones of the repository and different branches, so at what point does the incompatibility occur?Presumably you can still clone a repository and check out old commits with the old version?Does the commit for files that 2.26 marked as modified interfere with merging branches, either on z/OS or via pull request?What happens with e.g. git bisect?I'm not sure what "It i

There seems to be a problem with git blame on z/OS. For example if I run git blame -L 14,+1 PARMLIB/IEASYS00 on a copy of a repository on my laptop I get this: 41657ed0 (Gary Freestone (U70021A) 2020-06-10 11:30:25 +0000 14) GRS=STAR, MASTER OF GRS COMPLEX 00013100 If I run the same command of z/OS I get the following: fatal: file PARMLIB/IEASYS00 has only 1 line Running git blame PARMLIB/IEASYS00 on z/OS I get this: 00000000 (Not Committed Yet 2020-07-01 00:38:39 +0000 1) <<|ä........................ íèç|²ñ! èñ|+.<ñ³è... FFFFFFFF44D9A4C9998AA884E8A4FFFF6FF6FF4FF7FF7FF44FFFF4F5444444333222222222222222222222455445454544424455222 000000000D5630364493354085302020007001000A38A390E000001D01CCF3D00C000000000000000000001548F29A149FE0C934000 Note:I only receive a single line of output. The second and third lines are hexadecimal display of the line I’m receiving. The first few characters after the date and time are X’414C4C4F433D30302C’ which i

Hi Team,Is there any documentation explaining the usage of "Diffutils". I see the installation bin folder is having 'cmp', 'diff', 'diff3' and 'sdiff' binaries.Can we compare Z/OS files directly using Diffutils? Please help us to understand.------------------------------Sai PraneethLead ConsultantWipro TechnologiesChennai India------------------------------

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

Status: DeliveredI'm suggesting for pre-existing components (in baseline) that in addition to changmen zmf requiring checkout, that changeman should also require and edit (NOT a S1 / Stage from external source). This way an audit trail in user worklist (UL) is always in place as an edit-stage. thoughts??

Status: DeliveredIncluded in ZMF 8.3We have two separate Sysplexes, one for production (PLEX1) and one for development/testing (PLEX2).  There is another Sysplex for systems testing (PLEX3).  None of the Sysplexes have shared DASD between them. We use FTP for package distribution and remote promotion, though NDM has been used before for remote promotion with some of the similar concerns.  I have configured the FTP-related skeletons for package distribution and remote promotion to use an IP address by hardcoding the IP address within the ISPF skeletons.  This seems silly, being that the IP address is already specified within Global Site Information.  Knowing that the SER#PARM information is generated on-the-fly for the job that initiates a backout or revert from a DP-site that is done against a P-site, I had looked at the CMN$$BRQ skeleton.  Within this skeleton, there is reference to the IP address (&STEIPAD) and port number (&STEPORT).&n

Status: DeclinedWe had considered adding this enhancement to the next major release. However, after looking at this in greater detail it would require too much code rewrite to do this correctly. Its just not something we can consider at this time. Query component information from component list in package and from browse baseline via linecommand saves time and effort.Getting information about a component in ChangeMan is inconvenient. Let me give an example: You are in a package working with component ABC. Now you want to know about the dependencies of ABC to other components. You may open ChangeMan ZMF on a second screen, so you can stay in the package on the first screen. On the second screen you choose ‘QC’, ‘I’. Then you need to enter the components name, libtype, type of relationship. Now you want to check the history of the component. You leave item ‘I’ and enter ‘C’. You have to enter the components name and libtype again. You get the information. Your component is a

Status: DeclinedChangeMan ZMF version 8+ does not log a message to the system log when the started task cannot create the complete TCPIP member (#SERx).  This failure prevents the Users from logging on.  The message in the SERPRINT: SER8615I CMN TCPIP information not detected - cannot be saved This error message needs to put into the system log, so automation can capture the error and restart the started task to correct the problem.   Serena does not feel that Users being unable to access ChangeMan is a problem, but we at AT&T do. 

Status: DeliveredIncluded in ZMF 8.3I had a user call and asked if there is a SCAN function at a package level so that STAGING datasets can be scanned the same way as the baseline Scan functions Please add new function so that we can invoke a SCAN function on staging datasets same as we can run on Baseline. I think we need new  command from LIST and/or from in STAGE panel to be able to scan a stage library type for stings same as we can for Baseline.  Example we sometimes want scan Source for code, or scan LISTINGS for errors or strings and this would enable it to be done quickly on inflaight components.  Allow Online, batch, Alternate bach mode at library TYPE level.      

Status: DeclinedThis feature is implemented using EROI would like to propose in Application Administration an option where to specify, for a given application, the links with other applications.ChangeMan should use these links:1) in compile jobs (the copy and load baselines of all linked applications should be included)2) in audit jobs (the baselines of all linked applications should be analyzed by the Audit process)#applicationrelationships

Status: DeliveredThis facility will be delivered in ZMF 8.3In ERO area audit with ARS, we would like an enhancement, much like complex/participating schemes, were you can point all your recompile/relinks from auto-resolve to a specific package within the release. This makes the management and deployment of those components easier to implement.  Many of our apps that use ERO converted from the complex/part. scheme and liked they idea they could do that in that setup but not in ERO.

Status: DeclinedRequested behaviour change is not possible.Panelid: CMNRCMPR / CMNRCMP2Since Version 8.2.01 it is possible to get dependent sources, when you filter after Copies (CPY).The problem is, that you get only the sources from the defined application (packagename), and you do not get all source like in audit "Auto resolve".What I want is, that I get an additional option, that I get all sources in "Recompile Member List " (Panel:CMNRCMP2) , that uses the copy.That is, what Micro Focus described in there own manual:<<<.. You Can Now Display a List of Like- Source Components Affected by a Like- Copy Component and Recompile ThemYou access this function by selecting a like- copy library type from the main Recompile Source (CMNRCMPR) panel. Recompile will display a list of copylib members. You can then select a copylib member. Recompile will do a query impact for the selected copylib member and display a list of source members that reference it. You can t

Status: DuplicateZMF4ECL - Auto refresh packages and components after a developer actionIf the developer does a check out of a component to a package or does a build of a component in the package, the action is not reflected immediately and requires developer to manually refresh the package or the component to see the change in state. Automating this refresh option could be of an aid for Developers to see the changes immediately.

Status: DeliveredIncluded in ZMF 8.3In many cases there are no "refresh" called for a package leaving the user a confused because you can't see what is in a package unless you refresh it yourself.

Status: DeclinedAt this time, this isn't an enhancement we're in position to pursue as it would require a near rewrite of the Client Pack code base. Work with plugin changeman with RDzI would like to see if Serena can to add option MERGE AND RECOCILE in plugin changeman

Status: DeliveredCommand CICS for WebServiceGood Morning, Good morningI wanted to note that in the version ZMF/Changeman 8.2 There are some CICS commands to be able to manage the WSebService, in particular have been entered the commands for BUNDLER and for PIPELINES, but have not been considered the commands for the DISCARD of the WebService, command Very important to be able to manage the versioning of the webservice, because without the need to close and reopen the CICS.You can evaluate the management of this command: CEMT DISCARD WEBSERVICE (namewebservice).Sorry for my EnglishThank you Matteo Gervasi

Status: DeclinedThanks for submitting the IDEA Johan. At this time however, this isn't an enhancement we're in position to pursue as it would require a near rewrite of the Client Pack code base. Customers would like to have the ability to merge multiple version into 1 in the IDz enviroment when using the client pack    Customers doing the transition towards IDz would like to see Merge and Reconcile integrated in the Client Pack (at least into the IDz interface), giving the possibility to merge different package versions into 1

Status: DeliveredIncluded in ZMF 8.3I had read the following information about the CLR= parameter that is passed to the CMNSRCPP program via SYSIN DD:CLR=YES is the default. This parameter tells CMNSRCPP whether (YES) to delete allpre-existing source-to-copy records for the component in the current package beforeproceeding. That is, we are using CMNSCRPP to record both macros and copybooks.CLR=NO means that pre-existing source-to-copy records will not be deleted. CLR=NOshould only be specified where CMNWRITE will have cleared the source-to-copyrecords before adding entries for copybooks. CMNSRCPP then adds entries for macrosonly.This makes sense for the a regular single assembly build procedure, such as done via the delivered CMNASM ISPF skeleton.  The way CMN$$WPP is currently coded:)SEL &ADATA NE Y CLR=NO )ENDSEL &ADATA NE Y it takes into account, when &ADATA is not "Y", to not clear the source-to-copybook information created by CMNWRITE when copybooks are proce

Status: DeliveredIncluded in ZMF 8.3Please enhance panel CMNUTL02 and its underlying program code to support scrolling (left/right) the ISPF Stats columns to display standard ISPF stats columns such as ‘user ID’ that aren’t currently displayed on the CMNUTL02 panel. Business case: need to scratch all members in a library that were modified by my user ID, so I need to display and sort the member list based on that column of information but can’t do that presently since that column is no longer displayed on the screen and standard ISPF left/right scrolling is also not currently supported on the screen to display that information. The underlying code does actually support use of the primary command SORT ID already, but you just can't see the data that was sorted on since the ID column is not displayed and can't be scrolled to display.

Status: DeliveredIncluded in ZMF 8.3i would like to see if in zmf that the sort command be changed to allow sort cha command instead of full sort changed command that is currently needed since 'sort cha' works on other ispf screens ie: member list of a pds modify changeman panels that allow sort to accept 'sort cha' as well as 'sort changed' for command for sort/display. All IBM panels allow abbrev of CHA instead of typing CHANGED example of ISPF/TSO sort changed DSLIST JBREX00.TEMP.JCL Row 0000001 of 0000129 Command ===> sort cha Scroll ===> CSR Name Prompt Size Created Changed ID _________ ALTGDG 31 2004/06/09 2006/03/28 08:40:04 JBREX00 _________ ALTGDG2 4 2015/02/11 2015/02/11 22:56:00 JBREX00 _________ ALTKEY 34 2014/06/06 2014/06/09 15:12:49 JBREX00 DSLIST

Status: DeliveredCMNLIST3/4/5 - Unable to block Fx/RV commandFREZ0101 provides the ability to validate the package being 'manipulated'. When going via CMNLIST3/4/5 you are unable to pre-validate the options Fx. This is an inconsistent design. Exit FREZ0101 should be called when Fx is choosen on panels CMNLIST3/4/5 This way the same validation will be executed independent from where the freeze/unfreeze options selected The same applies to the RVRT0101 exit point.