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.
Hi Steve, re: >> So, what Kevin did works, but the question is why his specifying >> the fully qualified pathname for the same FILE action did not. > > I agree. That's why I indicated there might be some other problem. I understand, but how do you explain his "solution" of specifying <datadir-path> for 'pqact' in the LDM registry to be '/', and then setting his FILE action to write to 'data/gempak'? To me this almost says that the CWD is being added onto the beginning of the already fully-qualified pathname in FILE actions. If this is the case, it is a problem that needs addressing. If it is not a problem, I have a problem explaining why one of Kevin's settings did not work while another does. re: > Is Shemp still active? It does a lot of filing and could be used for testing > if > it's still available. I don't know as I have never been a big user of shemp. gale, on the other hand, is running. I will poke around on gale to see if anything jumps out at me (this will be more tricky as I think that Ryan is still using gale to do something specific). re: > I believe the "-log" option will log the pathname of the output file. I'll give this a try on gale. Cheers, Tom -- +----------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/ * +----------------------------------------------------------------------+ Ticket Details =================== Ticket ID: WLE-664327 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.