Re: Perl/ClearQuest or CQPerl/DBI on XP 64-bit

Please note, I know nothing of ClearQuest!

You are using OLE, and OLE loads dlls and then calls functions within them. You cannot load a 32-bit DLL from a 64.bit process.

So, unless IBM/Rational supplied you with 64-bit version of their interface components; or the sources so that you can build your own 64-bit versions, you are probably out of luck trying to use it from a 64-bit Perl.

Stick with a 32-bit version of Perl, they run fine under win64.

You could either:

stick with their supplied version of perl, and add your own modules to it.
This appears to be what you tried to do when you got
```
Can't load 'c:/path/to/blib/arch/auto/DBI.dll' for module DBI: 
load_file:%1 is not a valid Win32 application at 
c:/path/to/CQPerl/lib/5.8.6/lib/DynaLoader.pm line XX
[download]
```
It looks like the problem is that you had VC set up to do 64-bit builds. You need to use SetEnv.cmd to configure for 32-bit builds.
Alternatively, you could try using AS PPDs of DBI etc. with it. You would have to installl them manually (unzip and move the files), but it isn't too hard to do. You could even automate it.
Ditch their Perl and use a home-built (32-bit) or pre-compiled (32-bit).
You would have to copy their bits into your libs tree which might be an awkward process.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP PCW

Comment on Re: Perl/ClearQuest or CQPerl/DBI on XP 64-bit Download Code

Replies are listed 'Best First'.
Re^2: Perl/ClearQuest or CQPerl/DBI on XP 64-bit by romm (Novice) on Aug 05, 2009 at 17:13 UTC
Regarding the copying of AS PPDs into CQ installation. Wouldn't there be some path problem, as well as version mismatch problem? Or I should pick AS perl 5.8.6, just like the CQ perl is?	[reply]
Re^3: Perl/ClearQuest or CQPerl/DBI on XP 64-bit by BrowserUk (Patriarch) on Aug 05, 2009 at 17:35 UTC
Regarding the copying of AS PPDs into CQ installation. Wouldn't there be some path problem I'm not sure what you mean by "path problem"? You would have to move/copy the files (manually) extracted from the AS .zips into the appropriate places with the CQPerl subtrees. This is generally not hard to do manually, though it begs to be automated. as well as version mismatch problem? So long as you fetch the AS .zip compatible with the build of CQPerl, it should be fine. Eg. If the CQPerl reports it's version as 5.8.x then get the zips from here. In general (though not guarenteed), dlls built with any compiler, for a given major release of Perl will interoperate correctly, Or I should pick AS perl 5.8.6, just like the CQ perl is? Are you saying that CQPerl is just a binary copy of AS Perl with some extra packages added? If so, does it come with `ppm`, or `ppm-shell`? If so, then just using that to install the extra packages you want would be by far the simplest option. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. RIP PCW	[reply] [d/l] [select]
Re^4: Perl/ClearQuest or CQPerl/DBI on XP 64-bit by romm (Novice) on Aug 05, 2009 at 18:20 UTC
Path problems, I mean, the dlls may have some hardcoded path values of expected perl? CQ Perl is a 5.8.6 build. I don't know if Rational took an AS release and glued some modules to it, or built it from source themselves. I'll try both advices, using 32-bit AS perl 5.8.9 and if it fails, copying the AS modules' binaries over into the CQ Perl tree. Solution with AS perl is always preferred because of easier maintenance. Thanks, Roman.	[reply]
Re^5: Perl/ClearQuest or CQPerl/DBI on XP 64-bit by BrowserUk (Patriarch) on Aug 05, 2009 at 18:36 UTC
Re^4: Perl/ClearQuest or CQPerl/DBI on XP 64-bit by Anonymous Monk on Aug 31, 2009 at 01:15 UTC
cqperl is an IBM Rational maintained and slimmed down distribution. The best method is to get the module source from CPAN, compile with cqperl, and install either via copy or MSI with dependency on clearquest. This is especially true if you need to centrally distribute. I don't suggest doing things like "use lib..." because the code's in the schema and this will cause problems with cross-platform interop.	[reply]