Action Option -CU (-CheckUpdate) :

checks update status via looking at if remote files are available for retrieving. This action is useful to check if remote files are ready to be retrieved for updates for remote data files are ready irregularly while the data themselves are organized into files with regular temporal periods.

dsupdt	[[-(DS|dataset)] dsnnn.n] -(UF|UpdateFile) [Mode Options]
	[-(LI|LocalIndex) LocalFileIndices]
	[-(LF|LocalFile) LocalFileNames]
	[-(CI|ControlIndex) UpdateControlIndices]
	[-(XO|ExecOrder) ExecOrderIndex]
	[-(RF|RemoteFile) RemoteFileNames]
	[-(SF|ServerFile) ServerFileNames]
	[-(DO|DownloadOrder) DownloadOrderIndices]
	[-(DC|DownloadCommand) DownloadCommand]
	[-(ED|EndDate) NextDataEndDate]
	[-(EH|EndHour) NextDataEndHour]
	[-(GP|GenericPattern) GenericPatterns]
	[-(WD|WorkDir) WorkingDirectory]
	[-(MR|MissRemote) AllowMissRemoteFile]
	[-(FQ|Frequency) UpdateFrequencies]
	[-(CD|CurrentDate) CurrentDate]
	[-(CH|CurrentHour) CurrentHour]
	[-(HO|HourOffset) TimeZoneHourOffset]
	[-(CC|CarbonCopy) Cc'dEmailAddresses]
	[-(DB|Debug) DebugModeInfo]

Mode options that can be specified for checking update Action:

Execute this action without other conditions, all datasets that are due for updates are checked for update status.

Back to Top

-(EE|-ErrorEmail)	sends email only when error happens during checking
-(MU|MultipleUpdate)	checks remote files for multiple update periods
-(NE|NoEmail)	does not send email to the specialist after update checking
-(NY|NoLeapYear)	skips February 29 for leap years
-(SE|SummaryEmail)	send a summary email for update status to the specialist
-(UB|UseBeginTime)	when present, use the beginning time of update period
-(UB|UseBeginTime)	when present, use the beginning time of update period for replace temporal pattern of end time in file names and download commands