Toggle Sidebar
  • Recent updates
    • Post is under moderation
      Clark Rogers
      Clark Rogers unlocked the badge Points Achiever
      Points Achiever
      Earn points on the site.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Current ChangeMan functionality requires read, update access to the applciaiton while peforming admin functions.  We would like the ability to perfrom global and local admin functions while having jus...t 'read' access to the application. We are facing a requirement where the ChangeMan admins should not have read,update access to the applications.  With this level of access the admin can create ChangeMan packages, checkout/change code, etc.  It would with separation of duties to have 'read' access to the application and 'read,update' to the various admin resource rules.  This would allow admin functions using non-privilege accounts and orevent udpate access to components within the applicaiotn. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      PLEASE ADD A FIELD TO THE HLLX CHECKOUT FUNCTION (PANEL CMNCKOTS) SO THAT WE CAN REVIEW THE LINE COMMAND ISSUED IN THE MEMBER LIST FOR CHECKOUT FROM PACKAGE COMPONENTS IN HLLX PROCESSING AND PREVENT C...OMMAND WE DO NOT WANT USER TO BE ABLE TO INVOKE   EX:  "D"ELETE FUNCTION            UPDATE HLLX CHECKOUT FUNCTION SO WE CAN PROCESS THE COMMANDS ISSUED NEXT TO COMPONENTS AND PREVENT USAGE IF NEEDED   EX:  STOP DELETE FUNCTION CMNCKOTS                  CHECKOUT: CCHM000365 Components      COMMAND INVALID                                                                                   Name   + Type Status   Changed         Language Procname User    Request       ADPAUD01 SRC  ACTIVE   20170823 022840 COBOL2   CMNCOB2  HVIJAYA *ERROR        STATICPH SRC  CHECKOUT 20170823 023121 COBOL2   CMNCOB2  JBREX00            ******************************* Bottom of data ******************************** CMN000 CMN2494I - Valid codes are: B, D, H, S, SL, UC, UL, V   More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Resolve issues with installing ChangeMan ZMF packages that end-up having Audit out-of-synch situations because time has passed. This particular issue has been around for a couple of decades, and we sh...ould look at resolving the issue to get around this particular “hole” in the ChangeMan ZMF software lifecycle. Here is the scenario: You have a ChangeMan ZMF Package 1 that has Component A that was changed as part of a long-running project.  Package 1 was Audited successfully and Frozen, and then goes to, say, INTG testing for several weeks.  No additional changes end-up getting done to anything within Package 1, hence no reason for any additional Audits of Package 1. While INTG testing is being done of Component A, a production maintenance change needs to be done to Component A.  So Package 2 is created.  Component A has the minor change done, and for whatever reason the developer does not notify the owner of Package 1 of this maintenance change. Then Package 2 is Audited successfully, Frozen, and Installed into production within a day or two. The owner of Package 1 would have had a “checkout conflict” TSO message flash by on his/her screen, but (s)he would have likely missed it when you end-up pressing function and/or the Enter keys in quick succession. When the owner of Package 1 installs the project’s change into production, then the change from Package 2 gets accidentally regressed in production. Granted, we can implement (and have suggested implementing) a manual processes so that the final approver (or close to the final approver) has to submit a package Audit to ensure that there are no last-minute Audit errors.  However, anything that is manually done can be forgotten and missed. With regard to a design to get around this issue in ChangeMan ZMF, we are flexible.  But here is an idea: Maybe R&D can implement a Last Package Audit Date/Timestamp field that is stored as part of the ChangeMan ZMF package metadata.  Within Global Admin (which can be overridden in Application Admin), one can specify (1) which approval level number(s) must have a Package Audit be run before an approval can be done, and (2) how old the Last Package Audit Date/Timestamp can be until another Package Audit has to be run before the next approval level associated with a Package Audit requirement can be done.  If nothing is specified in one or both of these new configuration items in admin, then ChangeMan ZMF would act just like it has been with the scenario described above.  (As an aside, I suppose that this age-based requirement for Package Audit can also be applied to packages that are in DEV status that were Audited, say, 2 months ago.  In this situation, it is possible to freeze a package in DEV status with an Audit RC=00 from 2 months ago that now has a version regression situation that could go undetected.) The reason to have the ability to specify one or more approval levels that are associated with a Package Audit requirement is to take into consideration situations when a package may be in FRZ status while in QUAL and then INTG testing.  Testing could go on for months, and things can change in just a few days (if not hours).  If, for example, there was a Package Audit requirement prior to giving approval to promote to QUAL, and also an Package Audit requirement prior to giving approval to promote to INTG, and then finally a Package Audit requirement prior to giving approval to install into PROD, then one could avoid out-of-sync conditions earlier in the testing part of software lifecycle, and even eliminate them before going to PROD---even if the package stays in FRZ status (without any changes via selective unfreeze) for several months. As far as being able to quickly “eyeball” which ChangeMan ZMF packages’ Audit RCs are too old (or “expired”), maybe within the CMNLIST3 panel the “Aud” field could have a different color (e.g. red) indicating that the Audit RC has expired and a Package Audit needs to be re-run.  Of course, any package in BAS status would not have a different color, even after the age-based Package Audit criteria has expired. It was mentioned to associate an approval level number with a Package Audit requirement.  Thinking about it more, it may make more sense to associate the Package Audit requirement with an approval security entity. I do realize that the above idea still does not resolve the situation in which a package has had all its approvals done, and the package sits in APR or DIS status for days, weeks, or even months before production installation.  By then, something could have changed that would result in a package out-of-synch situation as far as Audit would be concerned.  I’m not sure what we could do to get around this, but at least being able to “eyeball” which ChangeMan ZMF packages’ Audit RCs have expired that are in a different color (such as red) within the CMNLIST3 panel would be helpful.  I suppose that something can be implemented where if anyone tries to reference the package through option U1, S2, BB, QP, etc., then a “PACKAGE AUDIT EXPIRED” ISPF message could be displayed as a warning.  This particular message would definitely show-up for packages in APR or DIS status, and maybe a Global and Application Admin setting can be created that would also show this message for packages in other non-BAS statuses (which I can see some users complaining about getting that message quite often...but for a critical application, this might be acceptable). More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Clark Rogers
      Clark Rogers is now following Benny Westaedt
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Clark Rogers
      In 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 rele...ase.  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. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Clark Rogers
      Clark Rogers added new listing Additional selective promotion status in ChangeMan ZMF/Mainframe
      Additional status on selective promotion panel. We see an situation with Changeman's 'Selective Promotion Screen Status Column'. When a program has been staged or recompiled (restaged) since last prom...otion but it was overlaid prior to the last stage, the status of overlaid is not changed to restaged. We would like to see a status added that represents both restaged and overlaid. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Several groups within our company are tracking developer productivity to determine who are active developers and how often changes are committed.     We would like data extracts to allow generation ...of data to be sent to our Application Development teams so the groups can track developer productivity.  The intent is to track each time a developer changes a piece of code or migrates the code to production. The ideal data format would be XML with data similar to the ChangeMan activity logs that are part of the ChangeMan log/recovery processes. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Clark Rogers
      Would like to see an automated process where packages that are x # of days past due can be automatically cleaned up and deleted for the system Applicaiotn development teams have a habit of creating te...st packages ad-hoc tests, etc and do not cleanup the packages when the go intto 'past due' status.   We would like to have functionality where we could pass a date parameter to an XML service and that would delete the components from the package and memo dlete the package. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Clark Rogers
      auditReturnCode tag needs to be available in all audit HLLX processing. In ZMF 8.1.2, the audit HLLX for AUD0001 and AUD00101 does not allow for auditReturnCode to be processed except for if the audit... is with auto-resolve.  We would like to see this tag be available for all audit processes since it is vital to many customizations. More
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    23/10/2017 ERO area audit-resolve - assign release package to house recompiles.
    05/06/2017 Additional selective promotion status
    18/05/2017 HXRAUDIT HLLX needs to make auditReturnCode available for pre/post porcessing
    15/02/2017 Add MODCNT variable to table LTYPETBL during staging.
    09/05/2016 ISPF Variables from backout using ZMF list option and 'B' option on Primary menu don't match

Recent Tweets