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

20050429: LDM - Binaries available?

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: 20050429: LDM - Binaries available?
  • Date: Tue, 03 May 2005 17:33:28 -0600
Scott,

>Date: Tue, 03 May 2005 15:09:41 -0800
>From: "Scott Swank" <address@hidden>
>Organization: NOAA/NWS
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050429: LDM - Binaries available?
>Keywords: 200504291922.j3TJMbKx001883

The above message contained the following:

> I have solved this problem, and have run across a new one.
> 
> Example: ldmadmin watch shows me that 5 products came in, but my script 
> is only executed on say (in this case) 2 of them.  I have added that 
> -wait to the pqact.conf file, but I'm still seeing this problem. 
> Suggestions on where to look?
> 
> ie:
> (ldmadmin watch snippet)
> May 03 23:02:06 pqutil:  118  EXP 000  METAR_vrh_.88569.123230028
> May 03 23:02:36 pqutil: 1780  EXP 000  METAR_vrh_.88594.123230108
> May 03 23:02:36 pqutil:  123  EXP 000  METAR_vrh_.88595.123230108
> May 03 23:02:36 pqutil: 1850  EXP 000  METAR_vrh_.88598.123230108
> May 03 23:02:36 pqutil:  125  EXP 000  METAR_vrh_.88599.123230108
> 
> (logfile generated when the EXEC portion of my pqact.conf is called)
> Arguments: /apps/decoders/ldm_metar.ksh METAR_vrh_.88569.123230028
> Arguments: /apps/decoders/ldm_metar.ksh METAR_vrh_.88599.123230108

I don't think the above two entries were generated by the LDM system.
Do you know what utility created them?

> You can see that the files with 88594, 88955, and 88598 didn't get 
> processed even though they have the same naming convention and are 
> inserted by the same process on the 6.3 machine.

Does this happen if you replace

    EXP ^(METAR)
        EXEC    -wait   /apps/datatools/runDecoder.ksh

with, for example,

    EXP ^(METAR.*)
        PIPE    -close  /apps/datatools/metarDecoder.ksh        \1

The above is more efficient than using an EXEC entry in the pqact(1)
configuration-file coupled with a script that uses pqcat(1) to obtain
the desired data-product.  It would require, however, that the script be
rewritten to read the data-product from standard input rather than use
pqact(1).

> Thanks,
> Scott

Regards,
Steve Emmerson