At 4:30 PM -0500 12/20/00, David Burney wrote:
>I'm attempting to track down the source of a somewhat obscure
>NetIPC error (34) that states :
>
>CRITICAL ERROR PREVIOUSLY REPORTED; MUST SHUTDOWN SOCKET.  (SOCKERR 34)
>
>Which was returned after a call to the IPCSEND intrinsic.
>
>In the error manual under CAUSE I see :
>
>NetIPC previously detected and reported an irrecoverable error;
>most likely it was initiated by the protocol module.
>
>Previous to what ?  None of the previous intrinsic calls so much
>as hiccup'd.  So I'm assuming (read: praying) that there are
>errors in the log file related to the protocol module that will
>help me eliminate this problem. Also, the necessary flags are
>set in NMMGR to log any entries associated with NetIPC.
>
>Any help or enlightenment would be greatly appreciated.


Have you tried turning on NetIPC tracing? You can do this with the correct
call to the ipccontrol intrinsic:

   ipccontrol ( sock_descriptor, 259 );

This will result in a trace file called "SOCK####" to be created in your
logon group. You can then use NMDUMP to read that file. For more
information on this please see

  http://docs.hp.com/mpeix/onlinedocs/5958-8600/00/00/24-con.html

Good Luck!



Barry Lake                              [log in to unmask]
Allegro Consultants, Inc.               www.bogus.allegro.com
(408)252-2330
--------
Attempting to reduce spam influx.
Remove ".bogus" to create valid address.