|
For Y2K we had a similar issue with CA and their Pansophic software; it had not been under maintenance for some time and they were asking some ungodly sum to get it up to date in order to get their Y2K version. When we replied "thanks, but we'll go elsewhere". When they realized some little money and future maint. revenues were better than none they suddenly became reasonable. It's all negotiable Dale -----Original Message----- From: Bill Erhardt [mailto:ERHARDT@xxxxxxxxxxxxx] Sent: Friday, May 30, 2003 9:16 AM To: 'Midrange Systems Technical Discussion' Subject: RE: Data 3 software CICS to RICS is not a problem. He will need the talk with SSA about a new key for his system though. It is kept in an RPG program (RTMENU02 I think) but they do not give you the source code. -----Original Message----- From: Paul Nelson [mailto:pnelson@xxxxxxxxxx] Sent: Friday, May 30, 2003 12:06 PM To: midrange-l@xxxxxxxxxxxx Subject: Data 3 software <Hold the laughter until I finish> We have just stumbled across a small company that is still running an F10 at V3R2. The IT manager needed some PTF's that we were able to find and loan him. He desperately needs to be on a new system, but his software is from the old Data 3 company, which was purchased by CA, and then by SSA. The system is heavily modified, and the company quit paying maintenance years ago. While investigating a new system during the time that the software was owned by CA, he was told that the charge for getting a new license key would be $200K. Do any of you old-timers out there have any experience with Data 3, specifically as to how they did their serial number checking? Is there a way around it, or is he hosed? Also, if there is a way around it, how well does the Data 3 system survive a CISC to RISC conversion? Before you ask about source code and observability etc., I only spent 20 minutes talking with this unfortunate fellow yesterday when I dropped off the PTF tapes. <Laughter may resume> Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell 708-923-7354 Home pnelson@xxxxxxxxxx _______________________________________________ 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.