sybperl-l Archive

From: abe dot crabtree at citicorp dot com
Subject: Re: ct_init error for Sybperl CTLib on ASE 12.5 OCS
Date: Apr 18 2002 8:43AM

Do you definitely have to have more than one version of Sybperl because of 
different applications using other versions of OC?

You could run perl as an alias or a script, and change SHLIB_PATH (if 
necessary) so that the libraries were always correctly located.  Perl would 
always run as:

SYBASE=/opt/sybase/oc12-xyz SYBASE_OCS=blablabla perl $*

If perl's version of OC were always installed at the same path, CTlib.sl could 
be chatr-configured not to search, but always go for that path (I think that 
might be the default.)

Meantime the other apps would have the standard system-wide $SYBASE settings.


I'm not sure if I've understood exactly how you're migrating.  Solutions like 
this may be possible, but I always think it's good to try and keep things 
simple - in our recent migration we moved everything except perl to 12.0, and I 
regret not winning the argument to move perl at the same time.


I hope this helps too,

Regards,

Abe



-----Original Message-----
From: Graham1.SIMPSON [mailto:Graham1.SIMPSON@hsbcib.com]
Sent: 18 April 2002 09:29
To: SYBPERL-L
Subject: Re: ct_init error for Sybperl CTLib on ASE 12.5 OCS





To:   SYBPERL-L@list.cren.net
cc:
Subject:  Re: ct_init error for Sybperl CTLib on ASE 12.5 OCS   (Document link:
Graham1 SIMPSON)


Hello again,

Okay dokay. I really don't want to have multiple versions of Sybperl compiled
against different OClients. To try to keep things simple, I have currently
compiled sybperl against 12.0 EBF 10109. It's packaged in an OS package and
dependencies set to also install the OC_1200-10109 package. i.e. every machine
will have OC1200-10109 installed when sybperl is installed.

The downside is that all applications will have to set their environment to be
OC12-10109 but the upside is one sybperl, one OC.

Last question, then I'll stop bugging you all. It seems a smart idea before
rollout to use OC12.5 instead of OC12. Can anyone recommend an EBF level for use
with sybperl or would I be more wise to stay with OC12-10109? Thoughts....

Thanks to everyone who supplied help with my problems.

Graham Simpson.




Michael Peppler  on 17 Apr 2002 19:40
                                                                                
                                                                                
                                                                                



To:   SybPerl Discussion List 
cc:     (bcc: Graham1 SIMPSON/IBEU/HSBC)
Subject:  Re: ct_init error for Sybperl CTLib on ASE 12.5 OCS





On Wed, 2002-04-17 at 11:26, Matthew.Persico@Lazard.com wrote:
>
> Hmm. Which means that if you really want multiple versions on a box (for
testing
> purposes, let's say) you better not take the defaults at installation and make
> sure you put different versions in different directories. This way, you can
> create the same-named non-numbered softlinks to the numbered libs in each
> directory, build sybperl (and DBD or that matter) using the links against the
> earliest version and swap versions with a $SYBASE redefinition.
>
> Of course, if the libraries are turn out to be incompatable from release to
> release, you will be forced to rebuild one instanance of Sybperl/DBD for each
> incompatable release. Each instance will have reside in its own directory tree
> (/opt/sybase/12.0/lib/perl5/, /opt/sybase/12.5/lib/perl5/...) and you will
have
> to muck with PERl5LIB before you call your code OR @INC inside your program.
>
> Here's hoping that the libraries are compatable...

That will mostly work.

However, you *must* *build* against a 12.5 OC to get the latest
functionality (wide varchars, etc), and a binary built that way will
*not* work with the 12.0 or 11.x libraries.

Michael
--
Michael Peppler                              Data Migrations, Inc.
mpeppler@peppler.org           *or*          mpeppler@mbay.net
http://www.mbay.net/~mpeppler
International Sybase User Group: http://www.isug.com



***************************************************************************
This message originated from the Internet. It's originator
may, or may not be who they claim to be, and the information
contained herein may, or may not be accurate.
***************************************************************************









_____________________________________________________

This transmission has been issued by a member of the HSBC Group 
"HSBC" for the information of the addressee only and should not be 
reproduced and / or distributed to any other person. Each page attached 
hereto must be read in conjunction with any disclaimer which forms part 
of it. Unless otherwise stated, this transmission is neither an offer nor the 
solicitation of an offer to sell or purchase any investment. Its contents are 
based on information obtained from sources believed to be reliable but
HSBC makes no representation and accepts no responsibility or liability as 
to its completeness or accuracy.