Richard,

Thanks for the help - I had eventually worked it out - I knew it would
be simple. I think I must have been suffering from a "Senior Moment". An
application has been installed on the machine that has its own (older
version) of the library - and has put its library directory at the
beginning of LD_LIBRARY_PATH.

Thanks Again,
   =Adrian=

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: 21 August 2008 12:43
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Problem with 5.4 Solaris Client

Adrian -

Okay, good to have that verified.
The only other thing I could think of is "misdirection", where the
environment under which the client execution is attempted has a
LD_LIBRARY_PATH environment variable or the like in effect which is
causing the loader to look in the wrong directories.  If nothing
apparent, you could try setting that var to "/usr/lib".  Beyond that,
you might try invoking the client under the 'truss' or similar trace
command for indications of where it is going astray.  If all else fails,
a TSM Support call may be needed, given that you had no such difficulty
running the 5.3 client.

    Richard

On Aug 21, 2008, at 3:46 AM, Davis, Adrian wrote:

>
> Richard,
>
> I get...
>
>        libCrun.so.1;
>        SUNW_1.1;
>        SUNW_1.2;
>        SUNW_1.3;
>        SUNW_1.4;
>        SUNW_1.5;
>
> ...from the "pvs".
>
> I just know the solution is going to be something very simple!!!
>
> Best Regards,
>   =Adrian=

DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. To see the full
version of this disclaimer please visit the following address:
http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the "Get Safe Online" website at
http://www.getsafeonline.org