Reported by @AnsleyManke on 2 May 2016 16:30 UTC
For the /REMOTE capabilities to be fully useful there needs to be a /REMOTE option for DEFINE DATA/AGG (TSERIES, ENSEMBLES, and FMRCs). Obviously, the /REMOTE is valid only if all members of the aggregation are on the same remote server. When they indeed are, then DEFIN DATA/REMOTE will execute the DEFINE DATA on the remote server.
The DEFINE DATA command could check the location of datasets and set a flag marking the data as remote-able. Then LET commands for data in the aggregated dataset would be set up as a LET/REMOTE.
Alternatively if a LET/REMOTE command is issued, even if the DEFINE DATA didn't have a /REMOTE on it, the check for members on the same remote server could be made at that time.
Reported by @AnsleyManke on 2 May 2016 16:30 UTC For the /REMOTE capabilities to be fully useful there needs to be a /REMOTE option for DEFINE DATA/AGG (TSERIES, ENSEMBLES, and FMRCs). Obviously, the /REMOTE is valid only if all members of the aggregation are on the same remote server. When they indeed are, then DEFIN DATA/REMOTE will execute the DEFINE DATA on the remote server.
The DEFINE DATA command could check the location of datasets and set a flag marking the data as remote-able. Then LET commands for data in the aggregated dataset would be set up as a LET/REMOTE.
Alternatively if a LET/REMOTE command is issued, even if the DEFINE DATA didn't have a /REMOTE on it, the check for members on the same remote server could be made at that time.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2406