|
Wasn't V3R2 the oldest Y2K compliant version ? One Y2K work around for non compliant systems would be to set the date back 28 years (calendars are indentical). But just keeping a S/38 running today would be dificult. DASD from that era was not that reliable. 9332s probably being the best bet and 3370s not. If there's one still running, I 'd like to hear about it. Keith ----- Original Message ----- From: "Al Barsa" <barsa@xxxxxxxxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, August 12, 2004 8:25 AM Subject: Re: IBM overhauls iSeries for the long haul > > > > > > As of 1999, the best info on the S/38 was that it was not Y2K compliant. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > "i" comes before "p", "x" and "z" > e gads > > Our system's had more names than Elizabeth Taylor! > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > http://www.as400connection.com > > > > > michaelr_41@myfas > tmail.com > Sent by: To > midrange-l-bounce "Midrange Systems Technical > s@xxxxxxxxxxxx Discussion" > <midrange-l@xxxxxxxxxxxx> > cc > 08/12/2004 11:05 > AM Subject > Re: IBM overhauls iSeries for the > long haul > Please respond to > Midrange Systems > Technical > Discussion > <midrange-l@midra > nge.com> > > > > > > > And I'll bet there are now 25-35 functioning S/38s left, and over > 100,000 S/36s left. > > On Thu, 12 Aug 2004 10:51:37 -0400, "Al Barsa" > <barsa@xxxxxxxxxxxxxxxxxxx> said: > > > > > > > > > > > > Depending on who you listen to (IBM doesn't talk) There were 25,000 to > > 35,000 S/38's, and 250,000 to 275,000 S/36s. > > > > Al > > > > Al Barsa, Jr. > > Barsa Consulting Group, LLC > > > > 400>390 > > > > "i" comes before "p", "x" and "z" > > e gads > > > > Our system's had more names than Elizabeth Taylor! > > > > 914-251-1234 > > 914-251-9406 fax > > > > http://www.barsaconsulting.com > > http://www.taatool.com > > http://www.as400connection.com > > > > > > > > > > > Pat Barber > > > <mboceanside@worl > > > dnet.att.net> > > To > > Sent by: Midrange Systems Technical > > > midrange-l-bounce Discussion > > > s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> > > > > cc > > > > > 08/12/2004 10:06 > > Subject > > AM Re: IBM overhauls iSeries for the > > > long haul > > > > > > Please respond to > > > Midrange Systems > > > Technical > > > Discussion > > > <midrange-l@midra > > > nge.com> > > > > > > > > > > > > > > > > > More than you can imagine. Since there was far more S/36 > > installed than S/38(50 to 1, maybe much higher), you gotta > > imagine many of those folks never bothered to convert to > > "native". > > > > I have several customers who never bothered and never asked > > to be converted once they saw that the 400 could handle > > their software "as is". > > > > Many have converted over the years, but some still run a few > > applications just as they were on the S/36. The S/36 customers > > are the reason the 400 exists today in my opinion. > > > > I don't believe "anybody" including IBM, has any idea how > > much S/36 code still runs. Remember the S/36 was wildly > > popular in other countries other than the USA. > > > > Of course IBM also didn't think many people were using > > OV/400. > > > > Shields, Ken wrote: > > > > > > That's another reason why IBM, rushed to put the Sys/36 out in the > > market. > > The S/36 was so popular, that even to-day, on the current release of > > OS400, > > the Sys 36 Environment is still supported. > > > > I'm very curious to know just how many companies are still using the > > S36 Environment. > > > > > > -- > > 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. > > > -- > > michaelr_41@xxxxxxxxxxxxxx > > -- > 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. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
