PE>> Well one of the problems was bad dates coming in, and Tobruk changing
 PE>> them to worse dates!  Now it barfs instead.  I tried looking for the
 PE>> message you sent me about the origin of the messages with bad dates,
 PE>> but couldn't find it.  I have sent netmail to the board that generated
 PE>> the one that I was looking at. BFN.

 PM> Shouldn't Tobruk just pass the message through without trying to do
 PM> something with the dates?

Well Tobruk interprets the whole header, and then reconstructs it.  It
needs to use some of the control information (specifically the
"to" net and node). It then reconstructs the control block.  The
date was being checked and was being flagged as bad, but I wasn't checking
the return code.  You wouldn't believe how easy it is to stick in
error-handling with PDS0001.  I just whacked in an "errorSet"
into dtsplit, and didn't do any more work, and processing dutifully stopped
even though I wasn't checking the return code. Of course, because I wasn't
checking the return, processing continued a bit longer, but as soon as it
reached the next ALLOK, it gracefully terminated, displaying the proper
error message.  BFN.

Paul

--- GoldED/2 2.42.G1114