Endevor

Expand all | Collapse all

ENDEVOR Release ID in source members

  • 1.  ENDEVOR Release ID in source members

    Posted May 23, 2017 08:47 PM

    Hi all

     

    Just wondering whether CA could/should put in the Release Id in delivered source. (Maybe at Top & Bottom just to be sure). Might help to eliminate any doubt about what is in what library once installed.

     

    Asking this because we are outsourced, and

    ( see https://docops.ca.com/ca-endevor-SCM/18/en/ca-endevor-scm-release-notes/increment-18-0-09 )

     

    indicates

     

    PRESERVE_GEN_TIME_IN_SOL_MEMBER_FP  should be in the ENCOPTBL source, but it's not

     

    Don't know yet what the issue is, but it made me think if source was labelled with an internal Release id comment. that would help. 

    Or maybe use a CCID to indicate the release & deliver an Endevor current source element (which has been Transferred to a dataset) and therefore has the Source Level Information with CCID at the top, so we can Transfer that in to our own Endevor repo ?

     

    Thx

     

    MJ



  • 2.  Re: ENDEVOR Release ID in source members

    Posted May 24, 2017 04:47 AM

    Yes.

     

    By keeping the Release ID and we can match back the changes Vs Release ID.

    Even in DOCOPS.ca.com , if CA teams can mention what all PTF's are being pushed for each summary changes and with each release.



  • 3.  Re: ENDEVOR Release ID in source members

    Broadcom Employee
    Posted Jun 22, 2017 09:52 AM

    Hi Melvyn,

     

    The ENCOPTBL is update with Fix #RO93928, did you install it when upgrading to INC09.

    If you wish to have the Release Id in delivered source, you should raise an ideation to request that.

     

    Let me know if this help?

     

    Regards,

    Ollivier



  • 4.  Re: ENDEVOR Release ID in source members

    Posted Jun 22, 2017 07:11 PM

    So, was 

    PRESERVE_GEN_TIME_IN_SOL_MEMBER_FP 

    in the "base" 09 source ? Did we need to update with the fix ?  

    If so, I don't think it  was clear we had to do that, unless I missed something somewhere

    I asked for & received a copy of the 09 source in a related case, and no mention was made of changes being only visible if we installed this fix to update it from 07 (our prev version)

     

    Gets messy too because we are reliant on IBM to deliver it, so we have no direct control or visibility

     

    That's why it is almost essential to document in the source which version, whether it's a "base" or "base + PTF number".  Let's remove the confusion . . .  

     

     

     



  • 5.  Re: ENDEVOR Release ID in source members

    Broadcom Employee
    Posted Jun 26, 2017 04:58 AM

    Hi Melvyn,

     

    When installing an INCremental, you have to know that it is a build of several PTF, for new feature and fixes.
    I think it is well explained(better than I could) in document; https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec1620556.html

     

    Let me know if this answer your question?

     

    Best Regards,

    Ollivier



  • 6.  Re: ENDEVOR Release ID in source members

    Posted Jun 26, 2017 06:35 PM

    Hi Ollivier

     

    Sorry, no . . .  I understand the principles involved in doing an Incremental release

     

    What I an asking for is

     

    1 -  to have the Release identifier IN the customisable source (C!DEFLTS / ENDICNFG / ENCOPTBL / etc.) as a comment

     

    2 - Identify which PTF's - and the feature/fix they perform - are included in each Incremental Release, so we can verify what we actually have against what we should have

     

    3 - If there are any PTF's created AFTER an initial Incremental release, available to include additionally, identify those in the release documentation.

     

    All I get is a PDS from IBM (our outsourcer), and I am totally reliant on how they construct their delivery.

    I have nothing to indicate what release anything belongs to, apart from what I am told. Thus if something seems or is amiss, I don't whether it's an issue with the CA delivery or the IBM delivery. I would like to know, and having the Release ID IN the customisable source will tell me this.  It will also help with the source management, as I use Endevor for these, so it will help to show what changes belong to what release

     

    Thanks

     

    Melvyn



  • 7.  Re: ENDEVOR Release ID in source members

    Broadcom Employee
    Posted Jun 27, 2017 11:29 AM

    Hi Melvyn,

     

    I well understand your concern and your ideation is the best way to address it.

    In the mean time, you can use the display footprint option to check the version of the Endevor's object, can you check that and send me your feedback.

     

    Regards,

    Ollivier  



  • 8.  Re: ENDEVOR Release ID in source members

    Posted Jun 27, 2017 07:09 PM

    Interesting . . . both R18 deliveries we have had so far for .CSIQSRC  have NO footprints for

    BC1TNEQU

    C1DEFLTS

    ENCOPTBL

    ENDICNFG

    which are the ones I am interested in

     

    ( Our R16 CSIQSRC DOES have them for ENDICNFG & C1DEFLTS. Don't have any earlier ones )

     

    Those members (in R18 CSIQSRC) which do have a footprint, just show , e.g.

     

    MEMBER     SYSTEM   SUBSYS
    C1LIBRSQ   ESCM180  GA

     

    so does not show the Incr. release id



  • 9.  Re: ENDEVOR Release ID in source members



  • 10.  Re: ENDEVOR Release ID in source members

    Broadcom Employee
    Posted Jul 19, 2017 03:05 PM

    Hi Melvyn,

    With the later Increments of V18, the version and Increment are displayed on the Endevor ISPF Main and QE panels -

    C1SM1000 --------------- CA Endevor SCM Version 18.0.10 ----------------------

     

    ENDIE110 --------- CA Endevor SCM Version 18.0.10 Quick Edit --------

     

    When the PTFs for an Increment are applied, any updates to the Endevor CSIQSRC tables will have been made. 

     

    You can determine what Increment the CSIQ* libraries are at by checking the Increment on either of these panels.

     

    June



  • 11.  Re: ENDEVOR Release ID in source members

    Posted Jul 19, 2017 06:37 PM

    Hi June

     

    Yes I know this - what I am after is to have the specific release identifier in the SOURCE MEMBERS in the Endevor CSIQSRC library, and/or having a footprint in them that tells me the same information.

     

    I know what version I have running, I want to know what version a source member belongs to

     

    cheers

     

    MJ



  • 12.  Re: ENDEVOR Release ID in source members

    Posted Jul 20, 2017 02:50 PM

    Hi Melvin,

     

    Are you versioning what your Outsourcer is giving you?

     

    Dana



  • 13.  Re: ENDEVOR Release ID in source members

    Posted Jul 20, 2017 08:29 PM

    Hi Dana

     

    In Endevor I am, but I'd like them to have a unique set of libraries for each release, so I can always go back to them for verification, and so THEY know too what they delivered to the Lpar.. (They are about to overwrite a prior delivery with R18 Incr.10). I''m trying to persuade them, but it's hard . . . I see it as basic version  control THEY should be practising.  . . .

     

    thx

     

    Melvyn



  • 14.  Re: ENDEVOR Release ID in source members

    Posted Jul 21, 2017 02:17 PM

    Hi,


    That could be the SMP/e datasets.

    In the past, I have used version at install time.


    Then there is a dataset to compare against.

    SMP/e also allows the backing out of a PTF


    Does that help at all?


    I also try to keep the run time datasets the same but use the PDSMan empty command to start with clean datasets before copying in the appropriate SMP/e datasets.



  • 15.  Re: ENDEVOR Release ID in source members

    Posted Jul 22, 2017 10:35 AM

    Hi Stuart - no not really.

     

    What happens is - IBM give me a set of files. I have to trust what they say is in them. So doing that, I add the customisable source to Endevor with a CCID that helps me identify the version.

    (I keep CA delivered & Customisable source separate)

    But if the CA delivered customisable files had footprints (some others do) indicating precisely what version + Incr. release  they belong to, life would be much simpler. And if they took just 5 minutes to put a comment up the top to indicate the release, I'd be happy. Because I can then verify a CA delivered PDS member against what I have customised, and any new CA delivery, with a lot more surety, at any time. Right now, there nothing in any delivered file I get to indicate what version anything belongs to. IBM won't even use a DSN qualifier to indicate the Version

    Just feels like I am working in the dark to some extent.

     

    cheers

     

    MJ