3.1.5 - Set Remote Files

Action Option -SR (-SetRemoteFile) (Alias: -SetRemote) :

(Alias: -SetRemote) creates or modifies remote file update records in GDEXDB for a given dataset and local file. One or more remote file records may be processed per execution.

dsupdt [-(DS|Dataset)] dNNNNNN -(SR|SetRemoteFile) [Mode Option]
-(LI|LocalIndex) LocalFileIndices
-(RF|RemoteFile) RemoteFileNames
[-(DO|DownloadOrder) DownloadOrderIndices]
[-(DC|DownloadCommand) DownloadCommand]
[-(SF|ServerFile) FileNamesOnRemoteServer]
[-(BT|BeginTime) BeginningDay/Hour]
[-(ET|EndTime) EndingDay/Hour]
[-(TI|TimeInterval) TimeInterval]
[-(DB|Debug) DebugModeInfo]

Available Mode option:

-(MD|MyDataset)

sets information into GDEXDB regardless of dataset ownership

Configure remote file update information only when needed. When the remote and local file names are identical, the local file record alone is enough to drive the update. A remote file record is required only when the remote file differs from the local file, when multiple remote files are downloaded and tarred into a single local file, or when a single remote file is available from multiple servers.

Local file indices and remote file names must be provided via -LI (-LocalIndex) and -RF (-RemoteFile), respectively, for this action to work.

When -DC (-DownloadCommand) is set in the remote file record, it takes precedence over the download command in the local file record.

Use -SF (-ServerFile) to specify the file’s name on the remote server when it differs from the remote file name. If not set, the server file name is assumed to match the remote file name.

Files downloaded from a server or generated locally are staged on disk as remote files until they are validated and converted into local files.

When a remote file is available from multiple servers, use -DO (-DownloadOrder) to set download order indices. The server with the lowest index is tried first; if it fails, the next is tried in ascending index order until one succeeds.