RE: Callpath/400 5716CP3 under V4R4M0 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks for your input, Ross.  Other changes are that the QTY library is
no longer used.  Some third party applications that use CallPath make
use of this library.  Another change is that the commands STRTELCNNM and
ENDTELCNNM are no longer supported.  So it's not as simple as you
describe. Changes like this are very disruptive in a production
environment.  How are we supposed to test all these changes? We work 7
days a week here.

The fact that IBM doesn't 'support' 5716CP3 any more is just about a
non-issue considering the level of support that was offered when they
did support it (ie., practically none). 

Lorne Sturgeoff
Allied International Credit Corp.
11 Allstate Pkwy, Suite 500
Markham ON Canada L3R 9T8
Phone: 905 513 3517
Fax:     905 470 8155
Email: lgs@aiccorp.com

> -----Original Message-----
> From: Ross Hartford [SMTP:rossh@ccslink.com]
> Sent: Friday, June 30, 2000 3:52 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Callpath/400 5716CP3 under V4R4M0
> 
>  << File: ATT00007.txt; charset = Windows-1252 >>

application/ms-tnef

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.