CA Mainframe Software Manager

Expand all | Collapse all

EOS for CA Common Services for z/OS v14.0

  • 1.  EOS for CA Common Services for z/OS v14.0

    Broadcom Employee
    Posted 10-02-2014 10:21 AM

    On September 30, 2014 we announced the EOS (End of Service) for v14.0 of CA Common Services for z/OS

    End of Support is September 30, 2015.

    Please consider upgrading to r14.1, our current GA release as soon as possible.

     

    As a result of this announcement some are wondering how this impacts the LEGACY and MFNSM packages which as stated in the original CA Common Services for z/OS r14.1 announcement, "...remain at the CCS v14.0 level".

     

    I want to clarify that this announcement does not impact the components delivered with the LEGACY and MFNSM packages. They will still be supported and delivered until further notice. Furthermore, when we repackaged r14.1 as S1401 we did this for ALL four packages (BASE,OPTIONAL,LEGACY,MFNSM). So as it currently stands, all four packages are listed as r14.1 S1401. Details about S1401 can be found in RI67924 and RI69562.



  • 2.  Re: EOS for CA Common Services for z/OS v14.0

    Posted 10-31-2014 02:18 PM

    Frank -

     

         What exactly is S1401?  Is this a "sprint"?  In MSM (5.0) I see for 14.1 two sub entries:  0000 (which is populated) and S1401 (which is empty).  I was under the impression maintenance, including sprints, would come out as PTFs.

     

         Thanks,

     

    - Don



  • 3.  Re: EOS for CA Common Services for z/OS v14.0

    Broadcom Employee
    Posted 11-03-2014 11:36 AM

    Hi Don,

     

    S1401 is a service update package for CCS r14.1

     

    Have a looks at this previous posting - https://communities.ca.com/message/111788472#111788472

     

    Maintenance is delivered as PTFs as you correctly thought, but because the initial delivery of CCS r14.1 (ie. 0000) was back in June 2012 and no new release was forthcoming, we produced this service update package that was intended for our customers that have not yet upgraded to r14.1. Thus using the S1401 package would put them at the CA RS 1401 level.

     

    If the S1401 subentry is empty within your CA CSM environment, this simply means that you have not yet performed an "Update Product Release" for CA Common Services r14.1 since this subentry was added. The subentry was likely added during a previous update of your product list.

     

    Have a good day!

     

    Frank...

     



  • 4.  Re: EOS for CA Common Services for z/OS v14.0

    Posted 11-03-2014 05:41 PM

    Thanks, Frank.  The posting plus your reply answered my question completely.

     

    - Don