Hmmm, upgrading isn't an option, and I just double checked with nettool, and
the resources that looks at (as you eluded to) does not show any
problems......

[3]RESOURCE>>>display
THU, JUN 23, 2005,  1:33:04 PM
 Item  Subsystem   Name   G/N  Description      Used   High    Max
____________________________________________________________________

  1    NS XPORT  CP_POOL_ (G)  Control Buf Pool    0      1    300 :)
  2    NS XPORT  1536____ (G)  Inbound Buf Pool   33     47    341 :)
  3    NS XPORT  LOOP____ (N)  Outbnd  Buf Pool    0      2    128 :)
  4    NS XPORT  LAN1____ (N)  Outbnd  Buf Pool    0     56    128 :)
  5    NS XPORT  LAN1____ (N)  StrFwd  Buf Pool    0      0     20 :)
  6    NS XPORT  UDP      (G)  GProt  Msg  Pool   50    N/A    512 :)
  7    NS XPORT  PXP      (G)  GProt  Msg  Pool    1    N/A    660 :)
  8    NS XPORT  PROBE    (G)  CM Prot Msg Pool    1    N/A    678 :)
  9    NS XPORT  IP_NI    (G)  IP-NI  Msg  Pool   50    N/A   2048 :)
 10    NS XPORT  IP_NI    (G)  IP-NI  Msg  Pool   50    N/A   2048 :)
 11    NS XPORT           (G)  Node  Name Cache    0    360    360 :)
 12    NS XPORT           (G)                      1      9   2048 :)

-----Original Message-----
From: Bartram, Chris (Contractor) [mailto:[log in to unmask]]
Sent: Thursday, June 23, 2005 1:29 PM
To: Dan Barnes
Subject: RE: [HP3000-L] FTP 'Unkonwn Socket Error'


6.0 has some serious network resource problems. It's likely that some of
the resources are maxed out.

Back when I had my last heavily-networked 6.0 system, I was having to
reboot it once every ~36 hours to reset the network resources (a simple
stop/start of the network didn't fix it). It got so bad before we
updated, that we had developed an automated job that ran every 30
minutes to check on network resources, and halted the system (with
auto-reboot) if we were out of resources.

Moving to 6.5 eliminated that problem.

FWIW, we obtained a DEBUG script from the HPRC that interogated the
relevant internal tables for resources that weren't being recycled -
that was the only way to view them (nettools didn't display the
appropriate tables either).

HTH,
  Chris Bartram

HP-3000 Systems Discussion wrote:
> Hi Gang,
>
> We are having a problem that impacts a single site.  We do
> daily gathering of disaster recovery information, then FTP it
> back to a central system just prior to its nightly backup.
> All other locations are working fine, and no changes have
> been made to this process for a very long time.
>
> The one caveat is that the location having the problem, which
> just began on June 1 after many, many moons of working just
> fine like everyone else, is that they are a 9x7 box on 6.0
> PP6.  All other systems are 7.0 PP2 systems.
>
> I have worked with the site and they state there have been no
> network changes, and there are no ther applications or users
> having network problems.
>
> The latest FTP patch that has been applied to the target
> system is FTPHD67A, and that was applied in October of 2004.
>
> The error and pertinent JCL are below.  Additionally, I can
> replicate this online, so it is not a batch issue.
>
> - - - - -
>
> 393   :CHGROUP disrecov
> 394   :CONTINUE
> 395   :PURGE ftpin,temp >  $null
> 396   :ECHO open hp1609 >  ftpin
> 397   :ECHO user mgr.rmidist,!hpnode >> ftpin
> 398   :ECHO mput @ >> ftpin
> 399   :ECHO put hosts.data.itxxrmi hosts >> ftpin
> 400   :ECHO quit        >> ftpin
> 401   :PRINT ftpin
> 402   open hp1609
> 403   user mgr.rmidist,HP0917
> 404   mput @
> 405   put hosts.data.itxxrmi hosts
> 406   quit
> 407   :
> 408   :FTP.arpa.sys < ftpin
> 410   File Transfer Protocol [A0009O11] (C) Hewlett-Packard Co. 2000
> [PASSIVE SUPPORT] 411   ftp> open hp1609
> 412   220 HP ARPA FTP Server [A0011L10] (C) Hewlett-Packard
> Co. 2000 [PASV
> SUPPORT]
> 413   Connected to hp1609 (xxx.xxx.xxx.xxx).  (FTPINFO 40)
> 414   ftp> user mgr.rmidist,HP0917
> 415   230 User logged on
> 416   Remote system type is MPE/iX.
> 417   200 Type set to I.
> 418   ftp> mput @
> 419   200 PORT command successful.
> 420   150 File: BLDSYJB1 opened; data connection will be opened 421
> UnKnown Socket Error. 422   200 PORT command successful.
> 423   150 File: BLDSYJB1;REC=-80,16,F,ASCII;DISC=26843545,8
> opened; data
> connection will be opened
> 424   200 PORT command successful.
> 425   150 File: BLDSYJB1;REC=-80,16,F,ASCII;DISC=26843545,8
> opened; data
> connection will be opened
>
> - - - - -
>
> the jcl hangs at this point, repeating the above line until
> the job is aborted......
>
> Any guidence would be greatly appreciated.
>
> Dan
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *