[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECnet/OSI for OpenVMS |
|
Moderator: | TUXEDO::FONSECA |
|
Created: | Thu Feb 21 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3990 |
Total number of notes: | 19027 |
3981.0. "NCL command consumes non-paged pool" by DECPRG::ZVONAR () Fri May 30 1997 10:27
Hello,
our customer (VAX OpenVMS 6.2, DECnet/OSI 6.3 ECO5) reported non-paged pool
expansions during repeated execution of NCL command:
$ mc ncl sho node prcn03 lapb link * CRC Errors Received,-
Data Octets Received,-
Data Octets Sent,-
Data PDUs Received,-
Data PDUs Sent,-
Times Link Inoperative
This command is used as a part of DCL batch procedure which is re-submitted
every 5 minutes. During execution of this procedure non-paged pool expands
UNKNOWN memory blocks - approx. 100K during every hour.
Customer uses the same procedure on OpenVMS 5.5-2 and DECnet IV & extensions
without problems.
I tested this command on our inhouse system (VAX 6.2, DECnet/OSI 6.3 ECO3) with
the same result - non-paged pool UNKNOWN blocks grow.
Does anyone heard about this problem?
Thanks in advance for your answer.
Karel
----------------------------------------------------------------------------
$!TEST.COM Test of NCL show command, resubmit interval 1 minute
$ set noon
$ pur test.log/keep:3
$ node = "chkrt2"
$! Part of customer's procedure - beginning
$ if f$search("temp.txt") .nes. "" then delete temp.txt;*
$ define sys$output temp.txt
$ mc ncl sho node 'node' lapb link * CRC Errors Received,-
Data Octets Received,-
Data Octets Sent,-
Data PDUs Received,-
Data PDUs Sent,-
Times Link Inoperative
$ deassign sys$output
$! Part of customer's precedure - end
$ submit/log/noprint/after="+00:01:00" test.com
$ exit
T.R | Title | User | Personal Name | Date | Lines |
---|
3981.1 | Fixed in DECdns ECO-70 | COMICS::WEIR | John Weir, UK Country Support | Mon Jun 02 1997 09:23 | 10 |
|
Karel,
Known problem -- install DECdns ECO-70 (actually, it was fixed in ECO-65, but
why not install the latest and greatest).
Regards,
John
|