[LDM #RWF-208175]: How do I verify pqinsert inserted something into the product queue?

Mike - there are several ways to check.  For the purposes of this explanation, 
I will establish the test case that you have a file called, 
"co2_data_archive.txt", and it is of file size 987453 bytes.

As an example, if you used pqinsert in the following way:

pqinsert -s 998 -f EXP -p "Todays CO2 Data" co2_data_archive.txt

You could create a pqact.conf entry to capture it on the other side of the 
queue as a validation:

#--- edit into the ~ldm/etc/pqact.conf
EXP <tab> ^Todays
<tab> FILE <tab> /data/ldm/validation/%Y%m%d_%H%M_co2data_validation.txt
#--- end of edit

You would replace the <tab> with literal tabs on your keyboard.  After you make 
this edit, you will need to HUP the pqact so it rereads the configuration file:

ldmadmin pqactHUP

That is a straight forward way, and it does test "end-to-end" that you have 
inserted the file onto an active LDM session.

Another way to exact some validation - along with any errors - is to change the 
logging file to be specific to your pqinsert instance, and set verbose and 
debugging:

pqinsert -v -x -l /home/ldm/logs/insertion.log -s 998 -f EXP -p "Todays CO2 
Data" co2_data_archive.txt

And after you do the pqinsert, open the file /home/ldm/logs/insertion.log and 
see what it says.

One last note . . . in the above examples, the ldm user will need to have 
read/write permission to the /data/ldm/validation and /home/ldm/logs paths.

Please let us know that one of these successfully gets you where you want to 
go, or if you need other methods articulated.

Stonie
-
Stonie Cooper, PhD
Software Engineer III
NSF Unidata Program Center
University Corporation for Atmospheric Research
I acknowledge that the land I live and work on is the traditional territory of 
The Pawnee, The Omaha, and The Otoe.

Ticket Details
===================
Ticket ID: RWF-208175
Department: Support LDM
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with NSF 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.