Hi Terri, re: > Hey Tom, I came up with what I think is a pretty efficient way to do this: > > EXP XXX_OBS.CSV.(..........) FILE -overwrite -close > /home/ldm/data/raw_data/obs/customer/tmp/xxx_obs.\1.csv > EXP XXX_OBS.CSV.(..........) EXEC csh -c "cp > /home/ldm/data/raw_data/obs/customer/tmp/xxx_obs.\1.csv > /home/ldm/data/raw_data/obs/customer/raw/xxx_obs.`date -d @\1 > +%Y%m%d.%H%M`.csv” OK. My approach would have been to write a single script to which you PIPE the product, and then have the script write the product in the intended output directory using the naming formalism that you desire. I would also have the script write a log message indicating that the product has been received and filed. In case you are interested, I have attached a Bourne shell script that I wrote to file GOES-16 imagery into daily directories that have names using the century, year, month and day in the form: CCYYMMDD. The images have names that include date/time information that are in the CCYYJJJHHMMSS format, so I have to convert from day of the year to month and day using 'date'. As you will see, the script (grbfile.sh) logs to the ~ldm/logs directory in a log file whose name is passed in on the command line specified in an LDM pattern-action file action. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: UFM-160152 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.
Attachment:
grbfile.sh
Description: application/shellscript