Toggle Sidebar
  • Recent updates
    • Post is under moderation
      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 gi...ve 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 subroutine, so you also check ‘B’ BofM. Again you enter the components name… There is a lot of unnecessary typing with the chance of typing errors. You understand the problem. It would be much easier, if you could get your information in the package, using a line command before the component! No repeated typing of component’s name and libtype again and again, as these items are known by ChangeMan, no typing error. And it would be even better, if you could use the same (!) line commands while browsing the baseline. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Paul  Caruana
      Paul Caruana is now friends with Matthias Lahme
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Matthias Lahme
      Matthias Lahme added new listing Store Audit Report content within ChangeMan in ChangeMan ZMF/Mainframe
      Storing content of an audit report within ChangeMan accelerates development because no tool-change (e.g. to SDSF) and additional time for searching has to be performed.  During our last internal Chang...eMan -training some developers asked, if it wouldn't be a good idea to store content of an Audit Report (Package and Release) within ChangeMan.The advantage would be that in doing that, audit-information is directly accessible within ChangeMan (without changing to SDSF or what ever) and that the last audit-report for a package or a release could also be baselined (like program-listings). This also may be obtained as a unchangeable proof with which audit-result the package (or release) went to production.We think there are much more arguments to find when dealing with this idea in deepth. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Matthias Lahme
      Matthias Lahme unlocked the badge Newbie
      Newbie
      Congrats on registering on the site!
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Matthias Lahme
      Matthias Lahme just registered on the site
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    20/10/2016 Store Audit Report content within ChangeMan

Recent Tweets