| Title: | DEC X.25 for OpenVMS AXP |
| Moderator: | OZROCK::MUGGERIDGE |
| Created: | Mon Jan 18 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 524 |
| Total number of notes: | 2218 |
I am curious how related the X.25 for OVMS and X25 Client V1.1 products are. I have a customer (MEGASYS) who says he experiences memory leaks using the X25 Client V1.1 product, only if an outgoing call is attempted, and only if the call fails. The only documented memory leak that I could find documented on ozrock with X25 Client V1.1 was with CFS30844 and users that did not have BYPASS. But the X.25 for AVMS V1.0 product had a escalation CFS23252 that does acurately describe what the customer says: The readme says: ------------------------------------------------------- The image X25$ACCESS.EXE in this directory fixes two memory leaks when a connection attempt is made to a X.25 gateway for an outgoing call and the connection is rejected. The leaks are non-paged pool blocks of at least 64 bytes (depends on the length of the names of the gateways) and 322 bytes. ------------------------------------------------------- So is it possible for X25 Client V11 customer's to see the problem also ? Mike Sheldon CSC/CS Network Support
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 517.1 | OZROCK::HARTWIG | Arthur Hartwig, TaN Engineering-Australia | Sat May 17 1997 00:16 | 12 | |
> I am curious how related the X.25 for OVMS and X25 Client V1.1 products > are. There is a lot of common code (and consequently lots of common bugs). > So is it possible for X25 Client V11 customer's to see the > problem also ? Yes its possible. My (unofficial) advice to customers is to migrate to X.25; its a much more robust product. X.25 includes all the functionality of X25 CLIENT, performs better and has more configuration options. | |||||
| 517.2 | Thanks ! | HTKING::M_SHELDON | Mon May 19 1997 23:55 | 0 | |