Some of you reported problems with UPDNODES when trying to run it against the VERS8612 NODUPD file. It took us a long while to realize that the problem did not come from UPDNODES itself, nor from the VERS8612 file, from storage/disk space requirements, but from the fact that some people had changed the entry of node WLUCP6 in last month's BITEARN NODES. This entry contained a node number of 0000 which ought to have been PEND (0000 is an invalid node number). It seems that someone sent mail to several NADs telling them to change this node number to PEND using XEDIT lest some other BITEARN NODES based program might choke on the thing, and that they did it. Or maybe they misunderstood something, but anyway some NADs XEDITed their BITEARN NODES file to change the 0000 to PEND and forgot about it, possibly thinking that this was an "official" change which had been done "at the other end". This caused UPDNODES not to function properly on the VERS8612 file. If you have made this change to your BITEARN NODES file, you must make the change back before you can successfully run UPDNODES against VERS8612. Eric PS: Sorry for possible duplicates. I sent this note to several lists.