RE: Aldon vs V5R3 was SAVLIB vs SAVOBJ

It's on our i5 - shows temporarily applied as of 1/5/2005 - also shows on 
order.  ;')

Vern

-------------- Original message -------------- 

> The cover letter says it's not on a cume. Got that from the url you 
> posted. 
> 
> It's not in the DB2 group ptf yet: 
> http://www-912.ibm.com/s_dir/sline003.NSF/554c38c4848b77f2862567bd0046e003/39891
>  
> 99192d41e0786256ea0005da927?OpenDocument 
> 
> Nor the hiper: 
> http://www-912.ibm.com/s_dir/sline003.NSF/554c38c4848b77f2862567bd0046e003/ffdeb
>  
> c8d8fee5adc86256ea000633eb4?OpenDocument 
> 
> However, there's nothing stopping you from ordering that one individually. 
> 
> Hope Aldon's Linux move isn't cutting off their nose to spite their face. 
> 
> Rob Berendt 
> -- 
> Group Dekko Services, LLC 
> Dept 01.073 
> PO Box 2000 
> Dock 108 
> 6928N 400E 
> Kendallville, IN 46755 
> http://www.dekko.com 
> 
> 
> 
> 
> 
> "Wilt, Charles" 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
> 02/23/2005 10:43 AM 
> Please respond to 
> Midrange Systems Technical Discussion 
> 
> 
> To 
> "Midrange Systems Technical Discussion" 
> cc 
> 
> Subject 
> RE: Aldon vs V5R3 was SAVLIB vs SAVOBJ 
> 
> 
> 
> 
> 
> 
> Rob, 
> 
> PTF was SI16108 for 5722ss1. 
> 
> http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/6d690d3
>  
> f3384c0f986256f4d0052a561?OpenDocument 
> 
> 
> or 
> 
> http://tinyurl.com/6drto 
> 
> Doesn't say much, just "OSP Internal maintenance for SQL" 
> 
> The way I read Aldon's notice, they were working/did have an alternative. 
> But when they were validating the solution on v5r3, they ran into 
> problems. Now the earliest memo I've saved is dated 10-2004, but it 
> mentions that there was a prior memo that first discussed the problem. 
> 
> Don't know when the actually found the problem, I assume it was pre-GA. 
> 
> Of course, Aldon will soon be releasing LM support on AIX and Linux. So I 
> guess that's one way of working around IBM removing support from beneath 
> you. 
> 
> Charles Wilt 
> iSeries Systems Administrator / Developer 
> Mitsubishi Electric Automotive America 
> ph: 513-573-4343 
> fax: 513-398-1121 
> 
> 
> > -----Original Message----- 
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx 
> > Sent: Wednesday, February 23, 2005 10:20 AM 
> > To: Midrange Systems Technical Discussion 
> > Subject: RE: Aldon vs V5R3 was SAVLIB vs SAVOBJ 
> > 
> > 
> > Do you know the ptf number, or APAR number? It's easy to 
> > check. I'll do 
> > it for you and post the site. 
> > 
> > Don't know if the open class stuff announcement was in the 
> > V5R2 version of 
> > 
> > http://www-1.ibm.com/servers/eserver/iseries/support/planning/ 
> > futuresftwr.html 
> > 
> > But it's sure here: 
> > http://www-1.ibm.com/servers/eserver/iseries/support/planning/ 
> > v5r3software.html 
> > 
> > In theory, they could have been working on an alternative 
> > that would work 
> > on V5R2. 
> > 
> > Still, since the GA date for V5R3 was June 11, 2004 let's 
> > hope that Aldon 
> > and IBM get their ducks in a row. 
> > http://www-1.ibm.com/servers/eserver/iseries/support/planning/ 
> > suptschedule.html 
> > 
> > Rob Berendt 
> > -- 
> > Group Dekko Services, LLC 
> > Dept 01.073 
> > PO Box 2000 
> > Dock 108 
> > 6928N 400E 
> > Kendallville, IN 46755 
> > http://www.dekko.com 
> > 
> > 
> > 
> > 
> > 
> > "Wilt, Charles" 
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx 
> > 02/23/2005 09:41 AM 
> > Please respond to 
> > Midrange Systems Technical Discussion 
> > 
> > 
> > To 
> > "Midrange Systems Technical Discussion" 
> > cc 
> > 
> > Subject 
> > RE: Aldon vs V5R3 was SAVLIB vs SAVOBJ 
> > 
> > 
> > 
> > 
> > 
> > 
> > Rob, 
> > 
> > Actually, the problem appears to be with the LM product (aka 
> > Affiniti) not 
> > the LM(i) product (aka green screen ACMS). 
> > 
> > I don't think I can hold it against Aldon, given the 
> > information I have. 
> > "IBM removed support for the Open Class Library, a library on 
> > which the 
> > Aldon LM server depends. Aldon has made the necessary changes 
> > to the Aldon 
> > LM product to support OS/400 V5R3. Testing these changes 
> > uncovered OS/400 
> > SQL defects which were forwarded to IBM for repair. We 
> > recently received 
> > a test PTF from IBM for the reported issues; the test fixes 
> > did resolve 
> > the issues found. 
> > We await the permanent fix from IBM before we are able to certify the 
> > product for OS/400 V5R3." 
> > 
> > Now as of, Dec-2004, the level 3 database group PTF did not 
> > include the 
> > PTF needed. It could at that time be ordered separately. 
> > 
> > I haven't heard if the PTF has made it into the latest group 
> > or cume yet. 
> > 
> > Charles Wilt 
> > iSeries Systems Administrator / Developer 
> > Mitsubishi Electric Automotive America 
> > ph: 513-573-4343 
> > fax: 513-398-1121 
> > 
> > 
> > > -----Original Message----- 
> > > From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx 
> > > [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On 
> > > Behalf Of 
> > > rob@xxxxxxxxx 
> > > Sent: Wednesday, February 23, 2005 8:18 AM 
> > > To: Midrange Systems Technical Discussion 
> > > Subject: Aldon vs V5R3 was SAVLIB vs SAVOBJ 
> > > 
> > > 
> > > I would be seriously surprised if Aldon didn't support V5R3 
> > > currently. And 
> > > if they didn't by now, I'd dump them because if they couldn't 
> > > come out 
> > > with a fix by now, their technical support must be down the loo. 
> > > http://www.aldon.com/news/pr_20040629.html 
> > > 
> > > Softlanding (the vendor we use) ran on our machines on V5R3 
> > > since at least 
> > > day 1 of V5R3 GA. 
> > > 
> > > Rob Berendt 
> > > -- 
> > > Group Dekko Services, LLC 
> > > Dept 01.073 
> > > PO Box 2000 
> > > Dock 108 
> > > 6928N 400E 
> > > Kendallville, IN 46755 
> > > http://www.dekko.com 
> > > 
> > > -- 
> > > This is the Midrange Systems Technical Discussion 
> > > (MIDRANGE-L) mailing list 
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> > > To subscribe, unsubscribe, or change list options, 
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> > > Before posting, please take a moment to review the archives 
> > > at http://archive.midrange.com/midrange-l. 
> > > 
> > > 
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion 
> > (MIDRANGE-L) mailing 
> > list 
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> > To subscribe, unsubscribe, or change list options, 
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> > Before posting, please take a moment to review the archives 
> > at http://archive.midrange.com/midrange-l. 
> > 
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion 
> > (MIDRANGE-L) mailing list 
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> > To subscribe, unsubscribe, or change list options, 
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> > Before posting, please take a moment to review the archives 
> > at http://archive.midrange.com/midrange-l. 
> > 
> > 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>