This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: Eirh-Yu Hsie <address@hidden> >Organization: CU/CIRES >Keywords: 200101021555.f02Ftlo18427 McIDAS-X 7.7 MCCOMPRESS Hsie, >I have some configuration problem. The data is there, but I can not list it: > >cirrus:[44]% ls -l GRID55* GRID56* >-rw-rw-r-- 1 ldm unidata 170930524 Dec 31 20:15 GRID5501 >-rw-rw-r-- 1 ldm unidata 171026240 Jan 1 20:13 GRID5502 >-rw-rw-r-- 1 ldm unidata 149938500 Dec 31 20:18 GRID5511 >-rw-rw-r-- 1 ldm unidata 149938500 Jan 1 20:17 GRID5512 >-rw-rw-r-- 1 ldm unidata 70002044 Dec 31 20:05 GRID5521 >-rw-rw-r-- 1 ldm unidata 70002044 Jan 1 20:06 GRID5522 >-rw-rw-r-- 1 ldm unidata 141201152 Jan 1 01:00 GRID5531 >-rw-rw-r-- 1 ldm unidata 141201152 Jan 2 00:52 GRID5532 >-rw-rw-r-- 1 ldm unidata 124833716 Jan 1 01:21 GRID5541 >-rw-rw-r-- 1 ldm unidata 124642284 Jan 2 01:19 GRID5542 >-rw-rw-r-- 1 ldm unidata 170930524 Jan 1 08:19 GRID5561 >-rw-rw-r-- 1 ldm unidata 171026240 Jan 2 08:22 GRID5562 >-rw-rw-r-- 1 ldm unidata 150129932 Jan 1 08:20 GRID5571 >-rw-rw-r-- 1 ldm unidata 149722632 Jan 2 08:24 GRID5572 >-rw-rw-r-- 1 ldm unidata 70002044 Jan 1 08:10 GRID5581 >-rw-rw-r-- 1 ldm unidata 70002044 Jan 2 08:10 GRID5582 >-rw-rw-r-- 1 ldm unidata 141201152 Jan 1 12:47 GRID5591 >-rw-rw-r-- 1 ldm unidata 124833716 Jan 1 13:18 GRID5601 > >cumulus:[127]% grdlist.k RTGRIDS/ETA.ALL FORM=FILE >stdin: not in compressed format >GRDLIST - done What is going on here is that the client application grdlist.k is requesting the transaction be done in compressed mode and something on the server side is not locating the 'compress' application. This can be caused by two different things: o 'compress' cannot be found on your server (not there or not in a "standard" location) o there is some sort of a problem in the ~mcidas/.mcenv file that is used to define McIDAS environment variables on your server Tom