Hello listmembers.

Here's my problem.

If I issue a LISTF [log in to unmask],2 I see this :

ACCOUNT=  SYS         GROUP=  PUB

FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
                  SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX

NMLG0424  NLOG   1024W  FB          21         21   1      176  1  *
NMLG0425  NLOG   1024W  FB           8          8   1       64  1  *
NMLG0426  NLOG   1024W  FB           1          1   1       16  1  *
NMLG0427  NLOG   1024W  FB           1          1   1       16  1  *
NMLG0428* NLOG   1024W  FB        2047       2048   1    16384  1  *

Which tells me that the current log file is NMLG0428.  And it
has a number of records in it that I want to view using NMDUMP.
So, since I can't view the file whilst it's being accessed exclusively,
I issue SWITCHNMLOG 428.  Which, as far as I understand things,
should create a NEW log file (429) leaving NMLG0428 with an
EOF of 2047. The records I wish to peruse.  Alas, this is what I
get when I issue a LISTF [log in to unmask],2 :

ACCOUNT=  SYS         GROUP=  PUB

FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
                  SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX

NMLG0424  NLOG   1024W  FB          21         21   1      176  1  *
NMLG0425  NLOG   1024W  FB           8          8   1       64  1  *
NMLG0426  NLOG   1024W  FB           1          1   1       16  1  *
NMLG0427  NLOG   1024W  FB           1          1   1       16  1  *
NMLG0428  NLOG   1024W  FB           1          1   1       16  1  *
NMLG0429* NLOG   1024W  FB        2047       2048   1    16384  1  *

Now the NEW file has the EOF of 2047 and the old file an EOF of 1.

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.


----------------------------------------------------------------------------
-------
David Burney                               [log in to unmask]
Summit Racing Equipment                     http://www.summitracing.com
                                       -----------
      All opinions expressed herein are my own and reflect,
                  in no way, those of my employer.