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.
Gerry, Glad setting PATH fixed it. It sounds like you could set LDMHOME in your shell's profile-file and then, later in the same file, add $LDMHOME/BIN to PATH. That should keep it simple. > There's plenty non-standard, but nothing I've not done before. I don't have > root access, and couldn't install in the ~ldm directory (no ~ldm user...). > Registry looks right, but I suspect it's not all set up properly in my path > dir. Let me get a snapshot of 'env' real fast, while I try adding ~/LDM/bin > to my path. > > Adding the path worked. That's not a good thing, though. I'd be MUCH > happier with using the $LDMHOME directory to reference things than to > depend on PATH. When you twiddle a lot of bits at the command line, having > something like that in your path is a bit of a problem... > > login01.ls5(15)$ env ... Regards, Steve Emmerson Ticket Details =================== Ticket ID: MXK-668269 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.