Toggle Sidebar
  • Recent updates
    • Post is under moderation
      Foresee the ability to add system copybooks and loadmodules to the SYSLIB of the compile and binder step via an additional skeleton Today we have CMN$$SYC and CMN$$SYL adapted to imbed a skeleton ...at the end of CMN$SYxThese imbedded skeleton have systems copybooks and loadmodules defined to be used during compile or linkeg.: at the end of CMN$$SYC we have)CM                                 )CM ADD SYSTEM LIBRARIES WHEN NEEDED)SEL &ECADDSYC EQ Y                 )IM EC$SYSLC                        )ENDSEL &ECADDSYC EQ Y        and at the end of CMN$$SYL we have)CM                                 )CM ADD SYSTEM LIBRARIES WHEN NEEDED)SEL &ECADDSYL EQ Y                 )IM EC$SYSLC                        )ENDSEL &ECADDSYL EQ Y        The switch is set in the buildproc skeleton)SET ECADDSYC = Y )IM CMN$$COE (or CMN$$PLE ...))SET ECADDSYL = Y )IM CMN$$LNK      Would it be possible to foresee this mechanism in the base product, where the skeleton name is a variable in CMN$$VAReg.:)CM CMNSYCSK : name of the skeleton where system copybook libraries are imbedded)CM CMNSYLSK : name of the skeleton where system copybook libraries are imbedded)CM CMNSYCAD : Indicates if teh skelton will be added at the end of CMN$$SYC)CM CMNSYLAD : Indicates if teh skelton will be added at the end of CMN$$SYC)SET CMNSYCSK = EC$SYSCL)SET CMNSYLSK = EC$SYSLL)SET CMNSYCAD = &Z)SET CMNSYLAD = &Zat the end of CMN$$SYC we have)CM                                 )CM ADD SYSTEM LIBRARIES WHEN NEEDED)IF &CMNSYCAD EQ Y AND &CMNSYCSK NE &Z THEN )IM &CMNSYCSKand at the end of CMN$$SYL we have)CM                                 )CM ADD SYSTEM LIBRARIES WHEN NEEDED)CM                                 )CM ADD SYSTEM LIBRARIES WHEN NEEDED)IF &CMNSYCAD EQ Y AND &CMNSYLSK NE &Z THEN )IM &CMNSYLSK More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      CMNEX019 gives will be called before/after checkout and before/after checkout. But when performin a "stage" of a non-SRC component the exit CMNEX019 is also called.   When a component is modified an...d saved, the exit is called and the checkin indicators are enabled. This is indepedent for a like-SRC component or a non like-SRC component. When a like-SRC component is "staged" (so no change took place) the exit is not called (obvious as no checkin took place) However when a non like-SRC is "staged" (so no change took place) the exit is called and the checkin indicators are enabled. To better differentiate CHECKOUT/CHECKIN/BUILD it would be nice to see an additional indicator in the exit eg. x19$sbld and x19$ebld (before and after build - aka stage) For a like-SRC this would be just before the kickoff of the file tailoring For a non like-SRC as it is performing today.  More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Johan Jacob
      Johan Jacob is now friends with Steve Nevin
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Hi Jeff, Thanks, that one slipped my attention, activated it, deleted the custom panel and works like a charm Cheers Johan
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Johan Jacob
      Johan Jacob is now friends with Jeff Jones
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Hi Guys, Sorry for this late response. So if in the meantime you all have a proper solution working, disregard the comment :-) 1. We have created a prototype for an automated code review process usin...g the Component Activity File (CAF) 2. In the CAFwe keep the status and comments of the code reviewer 3. In addition to it, we have an ISPF applications managing the CAFs a) When a CAF is "rejected" the related object is set to INCOMP (and it's related ILODs are deleted) b) When the related object is edited the CAF is set to INCOMP c) When the CAF is approved the CAF is set to ACTIVE d) The release manager has a reporting job giving an overview of all components in the release and their code review status 4. Audit validates it all Cheers Johan More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Johan Jacob
      Show component description in component lists We use the "Component Description" field to give a short specification of the component. Unfortunately CHangeMan does not show this description in any com...ponent list, e.g. if you browse the baseline or enter your package with "S2". It can be very circumstantial to find the component someone is searching for if they don’t know the exact name. So we suggest that the "Component Description" field is shown every time components are listed. For example if you check out a component from baseline, browse the baseline or list your package. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      This is now fully available in 814 and can be set to delivered (No?)
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Johan Jacob
      Hi Joseph, I created such a function. It has a number of parameters to tweak the process The package creator is notified 4 weeks in advance that the package will be cleaned (also a parameter) (If the... creator is no longer present in the company, we base ourself on a RACF extract, we change the creator to the last actionee in the package) Once a package has passed the criteria the process will a) recall all staging datasets b) back all staging datasets of the package c) delete the package - depending on your admin settings you'll need additional actions - we have decided to use XML services to remove all promotion data and then delete the components from the package If you need more info, just let me know (you have my email address) best regards Johan More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      It would be nice if there where better integration within view'a in RDz/IDz. A coulple of examples: Remote systemsSometimes I use MVS-files with a filter on our Serena baseline libs. This is becaus...e there are great support for search and I can brose code with a real editor and the many possibilities provided.But when a memer is found I would like to be able to just rightclick and do a Serena Checkout. No need to find the member again using Serena Explorer baseline lists. Same as above for search results. Maybe even from within the editor. Some uses other products like ADI (kind of the new ezSource) and in there integration would be great too. Is it possible to do somethink like this myself?Maybe a simple solution using Menu Manager first?A more advenced solution using Jave PDE? It would be really nice if Serena could provide some code for this - then we could integrate what we want. Regards Peter More
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    17/01/2019 Foresee the ability to add system copybooks and loadmodules to the SYSLIB of the compile and binder step
    23/04/2018 CMNEX019 - Better differentiate between checkin and "stage" of non-SRC components
    27/12/2016 ZDD doesn't support 'component change description' when staging versions are enabled
    27/12/2016 Foresee an HLLX pre and post exit on panel CMNCMP02
    23/12/2016 Add filter capabilities in ZDD tree view

Recent Tweets