On Fri, 9 Feb 2001, Dilip Chhetri wrote:
> hello all,
> I am wondering if the sql$mod61.exe is a standard executable that comes
> with the os? I seem to have the other components (? right terminology)
> but my 'make' bombs because there is not sql$mod61 where it is looking
> (or anywhere in the machine) - if it comes with the os, is it in a some
> layer product cd?? Any insight would be much appreciated by this newbie.
> * perl 5.6 running (very nicely!!) on vms(axp) 7-2.1 ..
> thanks
> ---
Rdb is a layered product that installs on top of the OS. Histroically I
think was the case that DEC came under criticism from other
server/database vendors for "bundling" the Rdb product with the OS.
Although I have little experience with older Rdb installations from long
ago (say before version 5) I still think it was the case that Rdb would
install separately from the OS even in those old days.
For reasons unkown to me DEC sold the Rdb product to Oracle corporation
but I think it is still the case that any work that gets done on Rdb is
done by developers in Nashua New Hampshire.
Do you have a file named SYS$SYSTEM:SQL$MOD61.EXE ? If so I think that
the presence of the "61" version number in the file name would indicate a
so called "Multi-version" install. Widely different versions of Rdb can
be installed onto VMS in a way that allows the preservation and use of
older versions. Such installations are called Multi-versioned in the Rdb
world (and are unrelated to file versioning such as ";1" or ";2" etc.).
As an example, on a machine with a single version installation of Rdb
You might have files with names like:
SYS$SYSTEM:RMU.EXE;
SYS$SYSTEM:SQL$MOD.EXE;
SYS$SYSTEM:SQL$PRE.EXE;
whereas on a machine with a Multi version installation of Rdb there will
be two clues: one is that the RDB product that was installed and
registered in the SYS$UPDATE:VMSINSTAL.HISTORY file will have "MV" as part
of the name. For example:
SEARCH SYS$UPDATE:VMSINSTAL.HISTORY RDB
| RDBA | 7.0 | 26-JAN-2000 | S
^^^^ single version for Alpha
| RDBAMV | 7.0 | 17-FEB-2000 | S
| RDBAMVC | 7.0 | 29-FEB-2000 | S
^^ multi version for Alpha.
The other clue about a multi-version installation will be the presence of
versioned server image names. E.g. on a machine that had a single
version installation of Rdb, as well as both Rdb 6.1 and MV Rdb 7.1 I can
see:
dir sys$system:sql*.exe,rmu*.exe
Directory SYS$COMMON:[SYSEXE]
SQL$.EXE;4 SQL$61.EXE;5 SQL$70.EXE;3 SQL$MOD.EXE;4
SQL$MOD61.EXE;5 SQL$MOD70.EXE;1 SQL$PRE.EXE;4 SQL$PRE61.EXE;5
SQL$PRE70.EXE;1 RMU.EXE;3 RMU61.EXE;1 RMU70.EXE;3
RMUEXTRACT.EXE;3 RMUEXTRACT61.EXE;1 RMUEXTRACT70.EXE;3 RMUSTAT61.EXE;1
RMUWIN61.EXE;1
Total of 17 files.
Which Rdb installation you have as the default on your system can be
rather easily determined with, e.g.:
$ rmu /show version
Executing RMU for Oracle Rdb V7.0-3
>
> $ mmk
> perl "-Iperl_root:[lib]" "-MExtUtils::Install" -e "pm_to_blib({split('
> ',<STDIN>
> )},'[.blib.lib.auto]')" <.MM_tmp
> perl "-Iperl_root:[lib.VMS_AXP.5_6_0]" "-Iperl_root:[lib]" -e "use
> ExtUtils::Mks
> ymlists;" -e "Mksymlists('NAME' => 'DBD::RDB', 'DL_FUNCS' => { },
> 'DL_VAR
> S' => [], 'FUNCLIST' => [])"
> perl -e "print
> ""[.blib.arch.auto.DBD.RDB]RDB.olb/Include=RDB\n[.blib.arch.auto.
> DBD.RDB]RDB.olb/Library\n"";" >>RDB.OPT
> perl -e "print qq{PerlShr/Share\n}" >>RDB.OPT
> Copy/NoConfirm RDB.OPT [.BLIB.ARCH.AUTO.DBD.RDB]RDB.OPT
> CC/DECC
> /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList/NOANSI_ALIA
> S/Define=("VERSION=""1.1""","XS_VERSION=""1.1""")/Include=(perl_root:[lib.VMS_AX
> P.5_6_0.CORE],perl_root:[lib.site_perl.VMS_AXP.auto.dbi])/Optimize
> RDB.c
> mc sql$mod DBDSQL.SQLMOD /c_proto/connect/warn=nodeprecate
> %DCL-W-ACTIMAGE, error activating image SQL$MOD
> -CLI-E-IMAGEFNF, image file not found
> ENC$DRA0:[SYS0.SYSCOMMON.][SYSEXE]SQL$MOD6
> 1.EXE;
> %MMK-F-ERRUPD, error status %X100388B2 occurred when updating target
> DBDSQL.OBJ
> $
This might indicate that the logical name sql$mod points to the SQL$MOD61
disk image. On my multi version 7.0 installation I have such a logical
name that appears like so:
sho log sql$mod
"SQL$MOD" = "SYS$COMMON:[SYSEXE]SQL$MOD70.EXE" (LNM$SYSTEM_TABLE)
So it would appear that there is something fouled up in your Rdb
installation. One thing that might correct the matter would be to try
running the command:
@SYS$SHARE:DECRDB$SETVER RESET
And see if that helps (if so consider adding it to SYLOGIN.COM). Another
thing to check is that the system startup is installing the correct
versions of KNOWN IMAGES. As an example, on the Multi version 7.0 machine
we do:
$ @sys$library:rdbvms_setver 7.0 /system
within SYS$STARTUP:SYSTARTUP_VMS.COM.
HTH.
Peter Prymmer
