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

[LDM #OXP-765029]: Using pqinsert with -p option

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: [LDM #OXP-765029]: Using pqinsert with -p option
  • Date: Wed, 19 Sep 2018 15:33:51 -0600
Carol,

> I'm pretty sure we usually only do a single file for each pqinsert.

In that case, the sequence number will *not* be appended and the product 
identifier will be the option-argument of the "-p" option. So, for example, 
pqinsert(1) could be invoked this way:

    pqinsert -v -p "Upper.Sounding.GTS.<whatever>" <file>

where:
    <whatever> is your choice for the product-identifier after the "GTS."
    <file>     is the pathname of the file to be inserted

The script that invokes pqinsert(1) should either be executed via an EXEC entry 
in the LDM configuration-file, or it should send a SIGCONT to the LDM 
process-group (e.g., "kill -s CONT -`cat ~/ldmd.pid`") so that the upstream LDM 
processes in the LDM process group immediately learn about a new addition to 
the product-queue.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: OXP-765029
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.