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.
Scott, >Date: Wed, 04 May 2005 08:57:32 -0800 >From: "Scott Swank" <address@hidden> >Organization: NOAA/NWS >To: Steve Emmerson <address@hidden> >Subject: Re: 20050504: LDM: PIPE-ing to scripts >Keywords: 200504291922.j3TJMbKx001883 The above message contained the following: > I setup the pqact.conf with the following: > EXP ^(METAR.*) > PIPE -close /apps/datatools/runDecoder.ksh /data/raw/\1 The separators in the above are not tabs. I hope they are in the configuration-file. > According to example, it should have written the products, but the files > are not there. $1 contains the filename, but where did the data end up? The above will try to execute the "runDecoder.ksh" script and pipe the data-product to it, but whether or not an output file is created depends on the actions of "runDecoder.ksh". Can you send it to me? Also, check the log messages from pqact(1) to see if anything untoward happened. You might try temporarily replacing the "runDecoder.ksh" script with the simple cat(1)-based script in my previous email -- just to verify that LDM system does, indeed, work as stated. > If FILE would be a better option, how does the filename then end up > getting passed to the decoding script so I can process the data? The FILE action is only for filing the data-product: no "decoding" is done. One could follow a "FILE -overwrite -close" action with an EXEC action that would decode the just-filed data-product, but that would merely be a convoluted way of simulating the PIPE action, which is more efficient. > Thanks, > Scott Regards, Steve Emmerson