[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020318: McIDAS XCD uwgrid.sh script (cont.)

>From: Eirh-Yu Hsie <address@hidden>
>Organization: Aeronomy Laboratory/NOAA/DOC
>Keywords: 200203151916.g2FJGga03699 McIDAS gtokserv INITBLOK g77



>>>Could you tell me what the error message means?
>>>Starting uwgrid.sh NF at 2002074/191421
>>>PRODUCT CODE=NF          2002074     191421
>>>300 250 200 150 100 2 TRO DAY=2002074 GPRO=MERC TIME=12 FHOUR=0 NUM=ALL
>>>GRDCOPY: Grid token server unable to initialize McIDAS environment
>>>GRDCOPY - done
>>>uwgrid.k: Done....
>>>Ending uwgrid.sh NF at 2002074/191425

I originally offered the thought:

>It sounds like the McIDAS environment variables in uwgrid.sh are not
>set properly, but I would have anticipated a different error message
>than the one you show above.

After logging onto your Linux box rainbow, I discovered the cause of
the problem.  Several Fortran routines were declaring an argument to
the subroutine INITBLOK as INTEGER (which is INTEGER*4).  INITBLOK is
expecting an INTEGER*2, so the value being read by the calling routine
is accessing 2 bytes that are not set by INITBLOK.  For "standard"
Fortrans (i.e., the Fortran compilers from vendors), this does not
cause any problems.  g77, on the other hand, does not handle this

The solution for the problem was to go into all of the Fortran routines
that are calling INITBLOK with an INTEGER argument, and change the
argument to an INTEGER*2.  I made these changes on rainbow, and will
fold them into my next McIDAS addendum.

I would have thought that this should have been caught before now, but
several of the routines that had the mistake have been working with
no errors!

The upshot of all of this is 7 more routines that needed modification
to work correctly when built with g77...


>From address@hidden Mon Mar 18 11:24:55 2002
>Subject: Re: 20020318: McIDAS XCD uwgrid.sh script (cont.)


Thanks, Tom.

Eirh-Yu Hsie
Aeronomy Laboratory/NOAA
325 Broadway, R/AL4
Boulder, CO  80305-3328
voice:  303-497-3275
fax:    303-497-5373

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.