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.
I'll rerun and get the info you need...In the meantime you can access the machine (tornado.usask.ca) eripley/dachshund but not at the moment apparently because of running SFCCON until I reboot... ----- Original Message ----- From: "Unidata Support" <address@hidden> To: "Earle" <address@hidden> Cc: <address@hidden> Sent: Friday, December 27, 2002 12:40 PM Subject: 20021227: Access to Mcidas files from OS/2 (cont.) > >From: Earle <address@hidden> > >Organization: University of Saskatchewan > >Keywords: 200212152209.gBFM9w412746 McIDAS-OS2 > > Earle, > > >The results were 26 lines in yellow, some of which I reproduce below:--- > > > > > >SFCCON GetConfigDefaultHandle () starting > > " opening SFCCUNUSER > > " opening SFCCONSITE > > " opening SFCCONCORE > > " return code is - > >100002 > >[the above lines were repeated 3 times} > >Number of Dataset Names = 1 > >RTPTSRC SFCHOURLY BPOS=0 EPOS=0 VERSION=1 > >ipad = 1997370752 > >reading nbytes = 256 > >echo_type status = > >Source type = ISFC > >PTCON RTPTSRC/SFCHOURLY GRA=5 etc........ > > > >Is this enough to give you a clue to what's happening??? > > Unfortunately, the important part of the output is after what you > sent. I should have remembered that it would be difficult for you to > capture the output from the SFCCON invocation and mail it to me, > sorry. > > The following should make it easier for you to give me the complete > output from SFCCON: > > SFCCON T USA DEV=TTT SFCCON.OUT > > This will send all textual output to the file 'SFCCON.OUT', and that > file will be in the McIDAS working directory on your OS/2 machine. > Now, which directory that really is I can't remember, but I think it is > the mcidas/data directory (it has been a long time since I worked on an > OS/2 system, and I have forgotten a lot about how things were setup). > You should be able to find out what directory is the McIDAS working > directory by typing > > !pwd > > from the Text and Command window. > > After you are able to locate the output file, you will need to email > its contents back to me. > > It strikes me that there might be a way for me to get on your machine > so I can look around. You would have had to setup a telnet daemon > to allow this, however. Can your machine be accessed by telnet? > If so, what is the machine name and user/password? If telnet was > not setup, what about FTP? > > Tom > **************************************************************************** < > Unidata User Support UCAR Unidata Program < > (303)497-8643 P.O. Box 3000 < > address@hidden Boulder, CO 80307 < > -------------------------------------------------------------------------- -- < > Unidata WWW Service http://www.unidata.ucar.edu/ < > **************************************************************************** <