The product size limit for which COMINGSOON is invoked is 16K. Yes, it's hardwired into the code. You could try changing it, but it looks like that value is also used to determine packet sizes. Thus, if you made it smaller you'd also be incurring the overhead of sending lots more smaller packets. Or, you could simply take out the test, but I'm not sure where that should happen, offhand.
You can take a look at this if you have the source code. The constant is called DBUFMAX. The files where this is important would be ldm_xdr.c, ldmclnt.c, and forn_svc.c. Note: there are some files in the distribution that are for LDM V4 and thus are pretty much obsolete. Also, there are a few other utilities that reference DBUFMAX.
One utility that uses DBUFMAX is pqsend. It's a utility that sends data from a local LDM queue to a remote LDM. There is a test in there for when to use COMINGSOON. You could take out the test there, then run that on your upstream sites.
Or, you could just go with it the way it is. 16K isn't that big - for smaller products it could be that the overhead associated with performing the COMINGSOON SEND/DONT_SEND exchange would be close to the performance hit due to rejecting small duplicates.
FYI. Happy Computing!
Anne
-- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************