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

20021027: IMGOLAY/FRMOLAY on Solaris SPARC gcc/g77 does not work (cont.)



>From: Robert Mullenax <address@hidden>
>Organization: NSBF
>Keywords: 200210270159.g9R1x6q20772 McIDAS v2002 gcc/g77

Hi Robert,

re: the version of the OS, gcc, and g77 you are running?

>Reading specs from /opt/sfw/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/specs
>gcc version 2.95.2 19991024 (release)
>
>__G77_LIBF77_VERSION__: 0.5.25 19991024 (release)
>@(#)LIBF77 VERSION 19990503
>__G77_LIBI77_VERSION__: 0.5.25 19991024 (release)
>@(#) LIBI77 VERSION pjw,dmg-mods 19990503
>__G77_LIBU77_VERSION__: 0.5.25 19991024 (release)
>@(#) LIBU77 VERSION 19980709
>
>I am running Solaris 8, patches are about 5 months old.

OK.  I just now ran the following sequence which worked with no problems:

IMGDISP GINIWEST/GW1KVIS STATION=KDEN PLACE=C MAG=-2 -2 EU=IMAGE SU=X ALL=11 
SF=YES REFRESH='EG GRA=(GRA);MAP FILE=OUTLUSAM MCOL=1 WID=1 GRA=(GRA);BAR (GRA) 
SU=X X COL=7 ORIENT=VER'

FRMOLAY NEXRCOMP/1KN0R-NAT UNIT=BRIT 
RAN='3:85,86:96,97:107,108:119,120:130,131:141,142:153,154:164,165:175,176:187,188:198,199:209,210:221,222:232,233:243,244:255'
 INT=0 GU=RADAR16_32

GRAPHICS TABLE RADAR16_32.GRX HAS BEEN RESTORED
 LEVEL   COLOR         BLUE  GREEN  RED
 -----  ----------     ----  -----  ---
    0   BLACK             0      0    0   (Graphic background)
    1   MAGENTA         255      0  255
    2   CYAN            255    255    0
    3   YELLOW            0    255  255
    4   GREEN             0    255    0
    5   RED               0      0  255
    6   BLUE            255      0    0
    7   WHITE           255    255  255
    8   GRAY            127    127  127
    9   GOLD              0    187  255
   10   PINK            127    127  255
   11   AQUAMARINE      147    219  112
   12   ORCHID          219    112  219
   13   NAVY            115      0    0
   14   SKY             255    163    0
   15   BEIGE           127    171  255
   16                   224    128  255
   17   WHITE           255    255  255
   18                   160     64  202
   19                   128     32  176
   20                     0      0  144
   21                    32     16  240
   22                    32    128  240
   23                    16    192  240
   24                    16     64   16
   25                    32    104   44
   26                    48    144   72
   27                    64    184  100
   28                    80    224  128
   29                   144    144    0
   30                   240    240    0
   31                    65      0    0
   32   BEIGE           127    171  255
GU: Done
Beginning Image Data transfer, bytes= 14209024
Beginning Image Data transfer, bytes= 2233520
Getting overlay data: rows= 1286
Done getting overlay data
Plotting overlay
FRMOLAY: DONE

The display of GINIWEST/GW1KVIS data was done out of the MCGUI (centered on
KDEN and blown down by a factor of 2).

The FRMOLAY invocation was cut out of the online help for FRMOLAY and
pasted into the command entry.

The results of this two step process can be seen online at:

http://www.unidata.ucar.edu/staff/tom/gifs/frmolay.gif

re: what is output when using DEV=CCC keyword

>Here is the DEV=CCC output:
>FRMOLAY NEXRCOMP/1KN0R-NAT UNIT=BRIT 
>RAN='3:85,86:96,97:107,108:119,120:130,131:141,142:153,154:164,165:175>
>FRMOLAY* $Header: $                                                            
>                 
>FRMOLAY* mcadir:NEXRCOMP 1KN0R-NAT 0 0 AUX=NO
>FRMOLAY* 
>mcadir:
>FRMOLAY* 
>mcadir:                                                                       
>         
>FRMOLAY: Data service module problem, RC= - 1

This error message comes from m0addef.for.  It means that an attempt to
run 'mcserv -R' failed.  This is the middleman for transactions to
remote servers.

>FRMOLAY* Server returned error number  - 98
>FRMOLAY: Local interface module cannot be found
>FRMOLAY: error on call to mcadir for overlay -98 2
>FRMOLAY: DONE                                                                 

So, this is all saying that mcserv can't be run.

The first thing that I would check is the results of 'which mcserv'
from the login from which you were trying to run the McIDAS command
before you start a McIDAS session.

The next thing I would try -- after starting that McIDAS session -- is
a '! which mcserv' from the McIDAS Text and Command window.

It may be possible that your PATH is getting hosed up from within your
McIDAS session, so mcserv can't be found.  I find this hard to believe
given you said that you were able to access both image and NEXRCOMP
datasets from that session, but I am grasping at straws to understand
what may be happening.

Tom


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.