[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051017: sending data products

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.

  • Subject: 20051017: sending data products
  • Date: Mon, 17 Oct 2005 16:20:00 -0600
Brian,

The static file name is not important to the LDM, and you can insert multiple 
products
with the same file name.

However, the LDM does reject duplicate data, so the MD5 checksum being computed
on your file is the same as already in the queue. A static file name is OK.
A static data product is not OK.

If you need to send the same product again, you could append the current system 
time
to the contents of the file when you insert the product, so that the MD5 
checksum will
be unique.

Steve Chiswell
Unidata User Support



>From: "Brian V. Olsen" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200510172159.j9HLxO7s028299

>I want to send a file with a static name several times an hour.
>I try to do this using 'pqinsert'.  (Should I use 'ldmsend'
>instead?)
>
>I cannot insert the product more than once.  After the first
>time, I get:
>
>pqinsert: Product already in queue:  ...
>
>followed by a bunch of alpha-numerics, the size of the product,
>the timestamp, the feedtype, and other things.
>
>I tried using sequence numbers and product IDs with 'pqinsert',
>but I still cannot insert the product more than once.
>
>I use the command:
>pqinsert -v -q /product-queue-path/ldm.pq -s 1 -p <random-number> -f EXP 
>file
>
>Can you suggest how I can repeatedly send a static-named file?
>
>--Brian
>
--
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.