>From: Unidata User Support <address@hidden> >Organization: Unidata Program Center/UCAR >Keywords: 200212271537.gBRFbgt17131 McIDAS-XCD Hsie, I sent a reply to your email of December 27 as soon as I saw it. I just got back notification that my reply bounced: ----- The following addresses had permanent fatal errors ----- <address@hidden> (reason: 550 5.0.0 Access denied) ----- Transcript of session follows ----- ... while talking to cirrus.al.noaa.gov.: >>> MAIL From:<address@hidden> <<< 550 5.0.0 Access denied 554 5.0.0 <address@hidden>... Service unavailable I am resending the message to your global al.noaa.gov address. But first, I have a comment. I logged onto cumulus.al.noaa.gov as 'mcidas' and made the changes that I suggest below. I noticed, however, the majority of GRID files are not stored in the /wrk/data/mcidas directory, but, rather, in the /home/mcidas/solaris/savedata directory. Is this what you want? Was I making the change on the correct system? I thought I was since cumulus is running an LDM. The other possibilitiy, of course, is that the machine you were interested in was rainbow.al.noaa.gov. I did not make any changes on it, since I wanted to see where the changes should be made. Tom -------------------- original message sent on December 27 - begin ----------- Hsie, >Somehow my McIDAS GRID and Point Source files are filed into the wrong >directory (/home/mcidas/solaies/workdata). I want them to be in >/wrk/data/mcidas. How can I change it. The GRID files in question are most likely ones that follow the naming pattern GRID6*. Here is what to do: <as 'mcidas'> cd /home/mcidas/solaris/workdata redirect.k ADD GRID6\* \"/wrk/data/mcidas mv GRID6* /wrk/data/mcidas Just to make sure that the XCD process being run by your LDM use the new file REDIRECTion, I recommend: <as 'ldm'> ldmadmin stop <wait for all LDM processes to exit> ldmadmin start The final thing you need to make sure of is that your scouring of XCD produced GRID files will take care of these extra GRID files. To do this, you must determine which user is running the McIDAS scouring routine, mcscour.sh, from cron. This is probably 'ldm'. Next, find the copy of mcscour.sh that is being run and edit it. Make sure that the GRID scouring line: qrtmdg.k GRID 5001 6400 1 will scour the full range of GRID files that are being created. In the example I show, GRID files from 5001 through 6400 will be scoured. Your mcscour.sh may not specify the second value as a high enough number. Adjust it from whatever it is to 6400. The final number on the scouring line is the number of days of GRID data you want to keep online. Leave this with the value you set previously. -------------------- original message sent on December 27 - end ------------- 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.