Subject:
Re: new releases of MySQL and Python
From:
p_sture@elias.decus.ch (Paul Sture)
Date:
23 Mar 03 10:24:20 +0100
Newsgroups:
comp.os.vms

In article <3E7C9672.ED85BC9B@laposte.net>, =?iso-8859-1?Q?Jean=2DFran=E7ois=20PI=C9RONNE?=  writes:

>> 

<snip>

>> 
>> Currently, documentation is missing but I have planned to put it on a new site
>> named
>> http://vmsmysql.dyndns.org. I will start this work probably next week.
>> 
>> Basic installation guide:
>> 
>> 1) unzip the file
>> 2) restore the saveset, you probably need a ODS-5 disk not sure.


Works fine on an ODS-2 disk (so far).


>> 3) goto the sub directory named vms
>> 4) @logicals "/system"
>> 5) building procedure
>> @build_all [vms_ssl/openssl] [zlib]
>> vms_ssl if you have installed HP OpenSSL distribuion
>> openssl if you have installed standard OpenSSL distribution
>> zlib if you have zlib installed (need libz:libz.olb and libz:*.h files)
>> 6) goto the sub directory vms.mysql
>>       $ spawn/nowait/input=nl:/notif @mysql_root:[vms.mysql]first_run_mysqld
>>       $ @mysql_root:[vms]symbols
>>       $ @mysql_root:[vms.mysql]mysql_privileges
>>       finally (you really have to do the command twice):
>>       $ mysqladmin -u root shutdown
>>       $ mysqladmin -u root shutdown
>>       optionally build a few demonstration databases:
>>       $ spawn/nowait/input=nl:/notif run_mysqld.com


should read:
        $ spawn/nowait/input=nl:/notif @run_mysqld.com


>>       $ @mysql_root:[vms.mysql]samp_db
>>       $ @mysql_root:[vms.mysql]vmsmod


should read:
        $ @mysql_root:[vms.mysql]vmsmod_db


>>       $ @mysql_root:[vms.mysql]load_repository
>>       $ @mysql_root:[vms.mysql]load_objects
>>       $ mysqladmin -u root shutdown
>>       $ mysqladmin -u root shutdown
>> 
>> 7) now use the run_mysqld.com to run MySQL server
>> 
>> 


That worked fine thanks. I believe my initial attempt failed because
I got a %LIB-F-INSVIRMEM at some point during the build. Increasing
my Pgflquo from 250,000 to 500,000 solved that, but rerunning the
build completed so quickly that it must have skipped the step which
went wrong.

I deleted the directory tree and started again from scratch. This time
all went well.

Many thanks for your efforts.


-- Paul Sture