Rocket Mainframe DevOps

Discussion posted 3/28/08 by Serenity Thompson, last edited 7/27/09 by Dave SealeyDetails: steverkI had opened a case with Serena, wanting to be able to restrict the revert function to only QA , at the QA promotional environments. This would keep the application team from reverting a package when they have already turned it over to QA. Serena said they currently could not do this, but have an enhancement request in to create this functionality. Serena also said that certain companies already do this.Does anyone out there do this, that would like to help?Posted 11/29/2007 1:28 PM chgadmAccess to revert ChgMan pkgs in frozen status is controlled by a security entity. Take a look at your RACF or ACF2 etc. security setup for security entity "CMNREVRT", are there too many users defined to this rule? The security section of the ChgMan install guide can provide further details. CMNREVRT or CMNxREVR Reve

Question posted 4/18/09 by SATYASAI GDetails:Hi All,We are user of Changeman ZMF 5.6.X ERO,We have DEVL,TEST and PROD.When we try to check in components into DEVL changeman session getting termainted.This release has 5 packages , each package has 1000 more components.is this due to space issue of changeman package PDS/AREA PDS libraries?is there any one who can help us ? Thank yousatyasaigvvss@rediffmail.com #oldforumpost

Question posted 12/9/08 by Anthony Dahlgren#oldforumpost#ChangeManZMF#post92a530f0a0

Question posted 9/24/09 by Lisa MastDetails:We are working on a project to support CICS applications which would be called as Web Services. The program CICS’s DFHLS2WS post processor is used to map the PLI program’s input and output structures into two XML members that would live in the HFS (or ZFS) file system. If Change Man would be supporting this, CM would need to create package-level HFS files just like it does for other entities. Then when a promote is done, the two XML files in the HFS package data sets would be copies to the staging level dataset in the HFS. CICS uses these two files (the WSBIND#oldforumpost

Question posted 10/6/08 by Tony PDetails:We've had component version control issues in ChangeMan where prior versions of components in change packages are corrupt. This issue only seems to be affecting change packages that have not installed. For example, a new version is created in a change package every time a component is changed (place "VC" next to the component in the change package). However, the PROGRAM-ID at the top of some of the prior versions is a completely different component name and sometimes the prior versions begin with code from different components. If you page down, you eventually get to the correct PROGRAM-ID and the program begins. I can't find a pattern to why/how this scenario happens. Sometimes the version control works fine while other times different programs are in prior versions and/or the prior versions begin with code instead of the PROGRAM-ID. Has anyone experienced this issue or any other issues with ChangeMan ver

Question posted 7/3/08 by Linda BrennanDetails:We are setting up a new system on an LPAR and changeman will not be on this.We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.These two systems will not be sharing DASD. I was wondering had anyone done anything like this before?Thanks,Linda #poste89de45bf5

Question posted 6/2/10 by Anthony DahlgrenDetails:We are planning to upgrade to z/OS 1.11 by September, is 5.6.1.02 compatible.Thanks,Anthony Dahlgren #oldforumpost#post1e14562b21#ChangeManZMF

Question posted 9/14/10 by Esteban SanchezDetails:Until recently we were running ZMF 5.5.2 under z/OS 1.9 without any problems. But the team suport are planning to upgrade to z/OS 1.11, Is 5.5.2 compatible to z/OS 1.11? Thanks #oldforumpost#ChangeManZMF

Question posted 6/2/10 by M KreutzianDetails:We are using the flat file for impact analysis and run a weekly job to rebuild it, the problem is that no Assembler Macros are being pulled out of the source. Copybooks in Assembler programs are working fine, but it will not even see the macros in the program. Anybody have any insight into this. It has been causing some problems for us when some recompiles are missed because they are not showing up in the impact file. We are on Changeman zmf 5.6.1A #postf3d407ee0d