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 Patrick, re: > After looking at things for a while today, I'd guess your suspicions are > correct. I too would lean toward timeouts, as if there were this many network > outages (several per day) we'd be seeing it in other places as well. You > asked > about the failure rate, it's very small, I saw 5 of these errors over the last > 36 hours and there are probably about 10,000 transfers in that time period. OK. With this sort of duty rate, it would be less likely that there is a server problem that needs addressing. re: > I see IMGCOPY commands in our log that all follow this format: > > IMGCOPY GWR/POS.944 LOC/GWFDSK04I4.1 BAND=4 SIZE=SAME STY=VISR TWIN=0 MAG=-1 > -1 > > with different values, so a generic entry would be: > > IMGCOPY XXX/POS.XXX LOC/XXXXXXXXX BAND=X SIZE=SAME STY=VISR TWIN=0 MAG=X X > > Is there a default timeout for IMGCOPY or ADDE for these transfers? Yes, the default timeout for ADDE is 120 seconds. Setting the ADDE timeout is described in the McIDAS Users Guide: Unidata HomePage http://www.unidata.ucar.edu Unidata McIDAS http://www.unidata.ucar.edu/software/mcidas McIDAS Users Guide http://www.unidata.ucar.edu/software/mcidas/current/users_guide/toc.html Appendicies I - McIDAS-X Site Administration and Management http://www.unidata.ucar.edu/software/mcidas/current/users_guide/McIDAS-XSiteAdministrationandManagement.html#25223 Setting the ADDE Server Timeout http://www.unidata.ucar.edu/software/mcidas/current/users_guide/SettingtheADDEServerTimeout.html#16639 re: > I see the > TIMEOUT command being used for READs, but not the IMGCOPYs. The timeout value is an ADDE setting. It is the amount of time that an ADDE transfer would have to be idle before a transfer is terminated. re: > Maybe we can look into using TIMEOUT to decrease the timeout to something > fairly small so any slow transfers won't stop up the processing. When a process is waiting for data from a server, very little CPU should be used. Decreasing the timeout value for ADDE would not be something that I would try. Increasing the timeout, however, is something I would do if there is a worry about transferring data over a slow link. 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: QLW-227820 Department: Support McIDAS Priority: Normal Status: Closed