This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: "C. Vandersip" <address@hidden> >Organization: . >Keywords: 199912221723.KAA23061 LDM IDD NLDN Chris, >I'm not sure this has anything to do with your advisory, but I've noticed >alot of the following messages in the dcnldn logs today. Many more than >usual. Can you explain? This should have nothing to do with the advisory sent out re: pqact.conf NLDN action, since nothing has changed in the broadcast (the change will occur on/about January 1). Did you make the change as advised? If so, did you verify that there was no problem in the pqact.conf syntax? What happens if you delete the output NLDN file and let it get recreated? >Thanks, >Chris > >From dcnldn.log: > >DCNLDN[12053]: 991222/0813: Starting up >DCNLDN[12053]: 991222/0817: [DCNLDN -2] GEM DECODE_NLDN: Tried writing >data to file--unsuccesful. Data file could be corrupt >DCNLDN[12053]: 991222/0817: Normal Termination. >DCNLDN[12053]: 991222/0817: Number of bulletins read and processed: 0 >DCNLDN[12053]: 991222/0817: Shutting Down. Tom Yoksas