Re: Broken date support on old releases? -- MIDRANGE-L

Subject: Re: Broken date support on old releases?
From: Holger Scherer <hs@xxxxxxx>
Date: Wed, 2 Jan 2019 21:51:09 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

know this issue - we have even a customer still running V3R2 in production as their software is totally modified, no source available, no programmer alive.
Next week schedules at two customers running V5R1 asking for what to do…

-h

Am 02.01.2019 um 21:43 schrieb Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>:

BTW, I've been trying to migrate these customers to current machines, even
hosting them on current hardware, but the longevity and self-management
features of the system lead to some customers not even thinking of
upgrading...

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Broken date support on old releases? , Rich Loeber

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.