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.
G, Ugh. Still not fixed. > > Doing the command you requested yields...a blank line. > > ldm@noaaport3:~/var/logs$ grep '^010 003 204' $HOME/etc/g2varsncep0.tbl > ldm@noaaport3:~/var/logs$ > > And this is the result of the "updateGempakTables" command: > > ldm@noaaport3:~/var/logs$ updateGempakTables > Cloning into '/tmp/gempak-tables9473'... > remote: Enumerating objects: 14, done. > remote: Counting objects: 100% (14/14), done. > remote: Compressing objects: 100% (10/10), done. > remote: Total 170 (delta 7), reused 11 (delta 4), pack-reused 156 > Receiving objects: 100% (170/170), 111.26 KiB | 1.99 MiB/s, done. > Resolving deltas: 100% (102/102), done. > The updateGempakTables(1) utility isn't working for you. Try this: edit the file "bin/updateGempakTables" and change the line make install >install.log 2>&1 && echo GEMPAK tables updated to mv *.tbl $ldmhome/etc Then, execute updateGempakTables(1) and re-execute the above grep(1) command. If it shows the new parameter, then restart your LDM; otherwise, let me know. --Steve Ticket Details =================== Ticket ID: RMM-695035 Department: Support LDM Priority: Normal Status: Open =================== 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.