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.
Neil, My bad. The action should be PIPE; not FILE. PIPE sends the data-product to the decoder via the decoder's standard input stream. EXEC does nothing with the data-product. So your entry should be NEXRAD<tab>^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(NET)(...) <tab>PIPE<tab>-close /unidata/ldm/bin/dump.n.link data/gempak/nexrad/NIDS/(\1:yyyy)(\1:mm)(\1:dd)/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3 data/gempak/nexrad/ALLNIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3 Note that 1) the <tab> after the PIPE is the last tab needed; and 2) the "-close" option is used to close the pipe to the decoder so that it knows where the end of the data-product is. > Steve, > I may have spoken too soon. > And I’m just getting back around to this … > > The script fails to write the normal output file vi the script’s ‘cat >$1’ > line — > - it will create the file at the designated path > (path had to be full path, script didn’t inherit the user ldm’s path) > - but the file is of zero length > - the link is created fine > > > Script: dump.n.link > mkdir -p `dirname $1` > cat >$1 > mkdir -p `dirname $2` > ln -sf $1 $2 > > pqact entry: > NEXRAD<tab>^SDUS[2357]. .... > ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(NET)(...) > <tab>EXEC<tab>/unidata/ldm/bin/dump.n.link<tab>data/gempak/nexrad/NIDS/(\1:yyyy)(\1:mm)(\1:dd)/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3 > data/gempak/nexrad/ALLNIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3 > > User ldm’s shell is csh. Regards, Steve Emmerson Ticket Details =================== Ticket ID: DIL-286118 Department: Support LDM Priority: Normal Status: Closed