Bart,
I am running Analog 3.11 on an AXP 150 with OpenVMS 7.1 and the OSU Web
server. It sounds like you have built the executable correctly although
I don't remember getting those errors during linking. You did specify
the option file as in:
$ link analog/option
You need to add the LOGFILE command to your analog.cfg file or the proper
parameter to your command line to get analog to use your specific
logfile. You also need to specify an OUTFILE if you want the output
written to a file rather than stdout.
If you have any general analog questions this list is a great resource.
If your questions are more specific to the VMS/OSU/Analog configuration I
would be happy to pass on the small amount of experience I have
accumulated in the nearly 2 years I have been running this mix.
I don't have any experience using the CGI script side of it. I just have
set up a DCL batch file to produce the reports at my desired interval.
+--------------------------------------------------------------------+
| Joshua Cooley ([EMAIL PROTECTED]) http://www.kaycee.net/josh |
| Programmer/Network Administrator |
| KayCee Software, Inc. http://www.kaycee.net/kcsi |
+--------------------------------------------------------------------+
On Fri, 28 May 1999 [EMAIL PROTECTED] wrote:
> Hello,
>
> I'm a totally new user for analog. I downloaded it this
> morning and am trying to get it installed, but I got a
> bit confused.
>
> First the facts:
> I downloaded analog 3.3 source code, working on an
> Digital Alphastation (OpenVMS 7.1)
> The server software for our site is OSU.
>
> The installation procedure says for VMS:
>
> >Compiling under VMS. Type
> >
> >MMS
> >
> >to compile analog.
>
> Never heard about MMS and it seems not to be included.
>
> DCL of course answers:
> >%DCL-W-IVVERB, unrecognized command verb - check
> >validity and spelling
> > \MMS\
>
> Then I found the file BUILD_ANALOG.COM
>
> Executing it seems to compile the program, but linking
> gives two undefined symbols:
>
> >LINK-W-NUDFSYMS, 2 undefined symbols:
> >%LINK-I-UDFSYM, fdopen
> >%LINK-I-UDFSYM, open
> >%LINK-W-USEUNDEF, undefined symbol fdopen referenced
> > in psect $LINK$ offset %X00000000
> > in module CACHE file
> >SPENVIS:[BARTQ.ANALOG.ANALOG3_3]CACHE.OBJ;5
> >%LINK-W-USEUNDEF, undefined symbol open referenced
> > in psect $LINK$ offset %X00000110
> > in module CACHE file
> >SPENVIS:[BARTQ.ANALOG.ANALOG3_3]CACHE.OBJ;5
>
> However, an executable is created.
>
> Running this executable,
> [
> >After you've made the program, just type
> >
> >analog
> >
> >to run the program.
>
> I guess this should read
> $ run analog
> under VMS.
> ]
> gives me a print on my screen of the HTML-report for the
> logfile.log from the distribution (although I changed
> this to use our log file), but it doesn't write a file.
>
> I would like to install analog as script, but what do I
> have to do for that? Is it just installing the
> analog.exe in our script directory ? The section on Form
> interface and CGI program doesn't say anything on VMS.
>
> Thanks for helping me to find my way through this,
> Bart Quaghebeur.
>
> -------------------------------------------------------------------------------
> Belgisch Instituut voor Ruimte-Aeronomie
> ir. Bart Quaghebeur
> Tel: (32)-2-373.04.21 Wiskundige Aeronomie
> Fax: (32)-2-374.84.23 Fundamentele Dynamica
> E-mail: [EMAIL PROTECTED]
> BIRA-IASB, Ringlaan 3, B-1180 Ukkel (Belgium)
> -------------------------------------------------------------------------------
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
