19991118: Client Routing Table

>From: "Jennie L. Moody" <address@hidden>
>Organization: University of Virginia
>Keywords: 199911182049.NAA16853

Jennie-

re: listing of environment variables
>No, it was the listing of user mcidas's environment variables.
>
>> 
>> MCTABLE_WRITE=/home/mcidas/data/ADDESITE.TXT
>
>Okay.  I made this change.

good.

re: difference between user and mcidas
>> This means that the RTGRIDS datasets pointed to by LOCAL-DATA
>> are different than those pointed to by the remote server at
>> windfall.  What you should do is run:
>> 
>> DSSERVE LIST RTGRIDS
>> from your account and see what is listed.  Then run this from
>> the mcidas account on windfall and see where it points to.
>
>My ACCOUNT:
>
>TFILE did OPEN on window 0
>DSSERVE LIST RTGRIDS
>
>Group/Descriptor         Type  Format & Range     RT Comment
>------------------------ ----- ------------------ -- --------------------
>RTGRIDS/ALL              GRID  GRID 5001-5400     Y  Real-Time Grids
>RTGRIDS/ECMWF            GRID  GRID 5251-5260     Y  ECMWF Grids
>RTGRIDS/ETA              GRID  GRID 5011-5050     Y  ETA Grids
>RTGRIDS/MISC             GRID  GRID 5001-5010     Y  Miscellaneous Grids
>RTGRIDS/MRF              GRID  GRID 5101-5200     Y  MRF Grids
>RTGRIDS/MRF-UW           GRID  GRID 101-102          MRF Grids in UW stream
>RTGRIDS/NGM              GRID  GRID 5051-5090     Y  NGM Grids
>RTGRIDS/NGM-UW           GRID  GRID 1-2              NGM Grids in UW stream
>RTGRIDS/RUC              GRID  GRID 5201-5280     Y  RUC Grids
>DSSERVE: done
>TFILE CLOSE
>
>McIDAS ACCOUNT:
>
>Group/Descriptor         Type  Format & Range     RT Comment
>------------------------ ----- ------------------ -- --------------------
>RTGRIDS/ALL              GRID  GRID 5001-5400     Y  Real-Time Grids
>RTGRIDS/ECMWF            GRID  GRID 5251-5260     Y  ECMWF Grids
>RTGRIDS/ETA              GRID  GRID 5011-5050     Y  ETA Grids
>RTGRIDS/MISC             GRID  GRID 5001-5010     Y  Miscellaneous Grids
>RTGRIDS/MRF              GRID  GRID 5101-5200     Y  MRF Grids
>RTGRIDS/MRF-UW           GRID  GRID 101-106          MRF Grids in the UW strea
> m
>RTGRIDS/NGM              GRID  GRID 5051-5090     Y  NGM Grids
>RTGRIDS/NGM-UW           GRID  GRID 1-6              NGM Grids in the UW strea
> m
>RTGRIDS/RUC              GRID  GRID 5201-5280     Y  RUC Grids
>dsserve.k: done
>
>
>They are identical.

Okay.  What this means is that mcidas is finding a copy of RESOLV.SRV
but that the ADDE server (mcadde) isn't.  From the mcidas account,
run DMAP RESOLV.SRV and see where it is located.  For the ADDE server,
it should be located in the directory pointed to by the MCDATA environment
variable in .mcenv.  Check to make sure .mcenv is correct.

>> 
>> I just pointed my RTGRIDS at windfall and there are not datasets
>> listed for that group.  I also just pointed RTIMAGES to windfall,
>> and there are no images available from the remote server on 
>> windfall.  This indicates to me that the remote server was not set
>> up correctly on the mcidas account on windfall.  Given that you
>> had to copy over ADDESITE.TXT from 7.4, I would guess that the
>> server table (RESOLV.SRV) was never set up by running LSSERVE.BAT.
>
>Well, it was never run for McIDAS7.6.  So is the idea that each time you
>upgrade you should re-setup the ADDE server?

Well, since you are using a "non-standard" McIDAS setup (using the
runtime cutover idea) then the answer is yes.  In general, these files
will not get overwritten by an installation.  It doesn't hurt to do
this every time you install though.

>> (See http://www.unidata.ucar.edu/packages/mcidas/mcx/config_mcidas.html
>> for instructions).  This file will be located in /home/mcidas/uvaworkdata.
>> I suggest you:
>> 
>> 1) edit the .cshrc file to put the correct location of MCTABLE_WRITE.
>> 2) source this file.
>> 3) Start a McIDAS session as the user mcidas
>> 4) follow the steps in the URL above to configure the ADDE access.
>
>I did 1, but need to go read the info on setting up and configuring
>the ADDE access...but its time for the seminar, so.....

See where RESOLV.SRV is located.  Since you copied over ADDESITE.TXT,
you could probably just copy RESOLV.SRV over to /home/mcidas/uvaworkdata
instead of running through steps 2-4.

>> The problem is that the ADDE data sets were not set up correctly
>> (by running LSSERVE.BAT and LOCDATA.BAT), so when you made the
>
>  Scary.

You should figure out how these steps got skipped during the installation.

>> switchover, the remote server couldn't find any data.  So once
>> you get it set up correctly, you should run:
>
>> 
>> DATALOC ADD RTGRIDS WINDFALL.EVSC.VIRGINIA.EDU
>> 
>> from your account (to put it back the way it was before) and things 
>> should work correctly.
>> 
>> 
>> Yes, then follow the other instructions above.
>> 
>
>righto.

So, the bottom line is to find out were RESOLV.SRV is located.  It could
be that it is being found in /home/mcidas/data and that both mcidas and
your account are finding it there.  Move it to the directory pointed to
by the MCDATA environment variable in .mcenv.

Don