Hi Jim, after thinking about this situation, I found that my first idea was wrong. If SDBINST.TGZ is missing, you would see something like:
cannot open SDBINST.TGZ No such file or directory The message cannot eval module from repository module SAPDB::Install missing means that all modules are read from SDBINST.TGZ and the main entry point is expected in SAPDB::Install but not found. In fact there is no module SAPDB::Install in SDBINST.TGZ. SDBRUN wants to start SAPDB::Install::main if no other main entry point is known. SDBINST starts SDBRUN, but is sets the entry point by putting the arguments '--main' 'SAPDB::Install::StartInstall::main' and '--programname' 'SDBINST' to the command line. The question is want happened to these arguments. Maybe you could call 'SDBRUN --main SAPDB::Install::StartInstall::main ...' to find out if this works. Regards, Christoph - SAP Labs Berlin -----Urspr�ngliche Nachricht----- Von: Jim Eatmon [mailto:[EMAIL PROTECTED]] Gesendet: Sonntag, 16. Februar 2003 14:33 An: Bautz, Christoph Cc: '[EMAIL PROTECTED]'; Jim Brown Betreff: Re: SDBINST fails Thanx for response Chrisoph... A little more background info from my previous post... I am using InstallAnywhere 5.x to create an installation. I run a script during this install by getting control in some Java custom code, and then doing the following: String instDir = ip.substitute("$USER_INSTALL_DIR$"); // the install directory String commandShell = "/bin/sh"; String commandOption = "-c"; String command = instDir + "/ISAPDB " + instDir; String[] commandArray = {commandShell, commandOption, command}; Runtime rt = Runtime.getRuntime(); Process proc = rt.exec(commandArray); . misc handling of STDOUT/ERROUT streams . . The ISAPDB script looks like this: #!/bin/sh echo "---------------------------------" echo "- ISAPDB started..." echo "---------------------------------" ls cd $1/sapdb-all-linux-32bit-i386-7_4_3_10 ls $1/sapdb-all-linux-32bit-i386-7_4_3_10/SDBINST -b -profile Server -indep_data $1/sapdb/indep_data -indep_prog $1/sapdb/indep_prog -depend $1/sapdb/depend -o sapdb -g sapdb SDBINST is failing with the following messages: cannot eval module from repository module SAPDB::Install missing The funny part is that I can run this script from the commandline and it completes successfully. Perhaps perl expects a specific permission on SDBINST.TGZ? Are there any perl specific env variables that must be set prior to the eval? Jim "Bautz, Christoph" wrote: > > Hi Jim, > > I do not know exactly wants wrong with your installation. > You would get such a message if the file SDBINST.TGZ is missing or demaged. > SDBINST.TGZ contains all perl modules needed for the installation. > It seems to me, that your installation kit is not complete. > Maybe the download was broken. > > Best regards > Christoph, SAP Labs Berlin > > -----Urspr�ngliche Nachricht----- > Von: Jim Eatmon [mailto:[EMAIL PROTECTED]] > Gesendet: Samstag, 15. Februar 2003 22:27 > An: [EMAIL PROTECTED] > Betreff: Re: SDBINST fails > > Can anyone help me with this. It seems that it might be issued by a > perl module, but which one? > I fail before I receive the typical "Installation of XXXXXXX" message. I > am not familiar with the debugging of perl modules. > > Any ideas? > > Any help is appreciated... > > Jim > > Jim Eatmon wrote: > > > > My environment is Redhat 7.1 SAPDB 7.4.3.10... > > > > SDBINST is failing with the following messages: > > > > cannot eval module from repository > > module SAPDB::Install missing> > > > What do these messages indicate? > > > > Jim > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
