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.
Jingtao, There are two ways to do what you want. The firstway is to use the PIPE action in a pqact(1) configuration-file: <feed><tab><pattern><tab>PIPE<tab>-close shefparse This assumes that "shefparse" reads from its standard input stream. The second way is to use the FILE and EXEC actions in a pqact(1) configuration-file: <feed><tab><pattern><tab>FILE<tab>-close <pathname> <feed><tab><pattern><tab>EXEC<tab>shefparse <pathname> More information on these actions can be found at <https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/pqact.conf.html>. > If I install LDM and configure to receive SHEF data, and store the data > under /tmp/shef directory. I also have a decoder program "shefparse" which > reads shef data from /tmp/shef dir and outputs a standard format file. But > I would like the "shefparse" program is triggered once the shef data comes > in the /tmp/shef. Another word, when detecting a shef data comes, the > shefparser runs. Can I do this via LDM? how to setup the link between the > data and the "parser"? Regards, Steve Emmerson Ticket Details =================== Ticket ID: XYN-356034 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.