Re: ITM 6.2.3 FP 03 expected release date
Jay Slay <[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general,gmane.comp.sysutils.tivoli.tme10 |
|---|---|
| Message-ID | <[email protected]> |
Ah. Provisional. Not interim. I suppose I'm out of practice. If one isn't yet available (depending on the underlying problem) you can also request a test fix, but realize its a test fix and could break stuff. In my experience most of these things are simple underlying file changes and can be easily reversed. So I am not too scared to get them when I need them. Plus, this is what no prod environments are for. -jks On Dec 18, 2012, at 12:22, John Alvord <jalvord-r/[email protected]> wrote: > For clarity - in my "central framework area" of TEMS/TEPS/TEMA/communications - a customer can request a provisional fix for earlier relief, > > A provisional fix is an early delivery of an existing fix when the customer needs it. It has been through L3 QA testing and is supported for production use. > > It is not always possible to create a provisional... for example > > 1) Fix not complete and tested for target maintenance > 2) Fix is dependent on other uplevel maintenance changes > 3) Fix is complex to test - so L3 could not deliver for production use with enough confidence. > 4) Multiple components are involved. > 5) Customer does not commit to testing and using the provisional fix. > > So - a request might be denied. > > There is basic information required... like APAR number etc but also > > A) platforms where required > B) maintenance levels required > C) a cinfo -i or kincinfo -i capture on example platforms > D) What other APAR provisional fixes are currently installed > E) A statement on why this is needed earlier then the normal maintenance cycle. > > It can take 5-6 weeks or more to create and deliver a provisional fix. If one has already been created for the target platform and maintenance level, it can take less time. If there is a pile-up of many customers requesting provisionals, that can also increase delivery times. > > Regards, > > > > John Alvord - Ph: 1-720-396-2788 Cell: none > Customer Support - Tivoli Software - jalvord-r/[email protected] > Advisory Engineer - Tivoli Monitoring - ITM infrastructure > Follow us on Twitter! @Tivolisupport and Facebook > Personalize your support needs with the IBM Support Portal > Use Service Request to get assistance! > For emails regarding a PMR, copy [email protected] > For secure browser uploads: https://www.ecurep.ibm.com/app/upload > For Customer Support guidance: IBM Software Support Handbook > > > > > > > From: Jay Slay <[email protected]> > To: "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]>, > Cc: "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]> > Date: 12/18/2012 08:29 AM > Subject: Re: [TME10] ITM 6.2.3 FP 03 expected release date > Sent by: [email protected] > > > > No you don't. Make support give you an interim fix for your apar. It will not have a fancy installer and you might have to back it out before applying the next fp, but if the problem is bad enough it's sometimes worth it. > > -jks > > On Dec 18, 2012, at 4:17, kalpesh parmar <[email protected]> wrote: > > Thanks for the reply. Will have to wait approximately 3 Month :( > > Thanks and regards > Kalpesh Parmar > > On Tue, Dec 18, 2012 at 12:35 PM, Robert Barron <[email protected]> wrote: > http://www-01.ibm.com/support/docview.wss?uid=swg24033803 > This fix is scheduled to be released on March 31, 2013. This is a target date and does not represent a formal commitment by IBM. This date is subject to change without notice. > > Robert Barron > Enterprise Management Specialist - IBM Israel > > > > > On Tue, Dec 18, 2012 at 8:38 AM, kalpesh parmar <[email protected]> wrote: > 6.2.3-TIV-ITM-FP0003 > > > _______________________________________________ > TME10 mailing list > [email protected] > Unsubscribe:[email protected] > > > _______________________________________________ > TME10 mailing list > [email protected] > Unsubscribe:[email protected]_______________________________________________ > TME10 mailing list > [email protected] > Unsubscribe:[email protected] > > _______________________________________________ > TME10 mailing list > [email protected] > Unsubscribe:[email protected] _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]