[LDM #MDC-227212]: LDM Compile Error

Hi,

re:
> I think we could probably cut our request statements by roughly 30% (maybe 
> more) with
> some creative expressions.  

That would be a good thing to do!

re:
> Some products we request specifically by name (e.g. .gz
> files).  Those that come from the same server but are of different product 
> types, we
> could conceivably "request any" and combine the product names into a single 
> statement,
> correct?

Yes, but you can also specify a "list" of files to REQUEST from a single
upstream.  Here is a hypothetical example (hypothetical since I do not
know if the REQUESTs I am using are to the same upstream host given the
redaction in the LDM configuration file you sent):

REQUEST EXP 
"(LRE_edit-db.tar.gz|MVP_edit-db.tar.gz|LRN_edit-db.tar.gz|LRH_SHEF)" x.x.x.x

It is possible that all REQUESTs to an upstream for a particular LDM/IDD 
feedtype
could be combined into a single REQUEST line.

re:
> For instance, requesting EXP "LRN_SHEF" and "LRN_edit-db.tar.gz" from the
> same server using a single statement ("or" regex operator).

Yes, exactly:

REQUEST EXP "(LRN_SHEF|LRN_edit-db.tar.gz" x.x.x.x

would reduce the number of REQUESTs by 1.

If you run into any hiccups, we can do a WebEx...

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: MDC-227212
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.