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.
Hi Heath,
The problem appears to be in your pqact.conf action. Here is what
you have currently:
NEXRAD2 /KLIX/ FILE -overwrite data/NEXRAD2/\1.ldm
The \1 reference refers to a subset of the product ID pattern that
is matched, and that subset is delimited by parentheses.
Here is what we think you want:
NEXRAD2 (KLIX)
FILE -overwrite data/NEXRAD2/\1.ldm
NB: use tabs, not spaces, where needed:
- between NEXRAD2 and (KLIX)
- before and after FILE
Since you didn't have a subset delimited in your action, it
is very possible that the LDM has been creating the file '.ldm'
in the ~ldm/data/NEXRAD2 directory. Check to see if this is
true using:
<as 'ldm'>
ls -alt ~ldm/data/NEXRAD/*
After you make the change to your action in ~ldm/etc/pqact.conf, you
should check your typing using:
ldmadmin pqactcheck
If you have no gross errors (those reported by this check), then you
can make the change(s) active without stopping and restarting your
LDM:
<as 'ldm'>
ldmadmin pqactHUP
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: NAN-265528
Department: Support IDD
Priority: Normal
Status: Closed