3.3.8 - Check Update Status

Action Option -CU (-CheckUpdate) :

verifies whether remote files are available for retrieval. This is useful when remote data files become available irregularly but are organized into files covering regular temporal periods.

dsupdt [[-(DS|Dataset)] dNNNNNN] -(CU|CheckUpdate) [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]

Available Mode options:

-(CA|CheckAll)

checks all remote files rather than stopping at the first unavailable one

-(EE|ErrorEmail)

sends email only when an error occurs during checking

-(MU|MultipleUpdate)

checks files across multiple update periods

-(NE|NoEmail)

suppresses post-check email notification

-(NY|NoLeapYear)

skips February 29 in leap years

-(SE|SummaryEmail)

sends a summary-only email with update status, without detailed log information

-(UB|UseBeginTime)

uses the period’s beginning time instead of the end time when substituting temporal patterns

When executed without additional conditions, every dataset due for updates is checked for update status.