Justin,

What external manager are you using?  Typically, if you've got
libtype=acsls, you're not using an external manager because TSM is managing
the library via it's ssi processes.  If it's Gresham EDT, we're using
libtype=external, rather than libtype=acsls.  In the library definition, we
then have externalm=/usr/lpp/dtelm/bin/elm so TSM uses the EDT software to
communicate with ACSLS.

Alex Paschal
Freightliner, LLC
(503) 745-6850 phone/vmail


-----Original Message-----
From: Justin Derrick [mailto:jderrick AT CANADA DOT COM]
Sent: Friday, April 18, 2003 7:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Docs Wrong?? 5.1.6.0 ACSLS library path definition problem


Then you say 'For the TCP/IP attach, use the library name.'  Do you
mean the TCP/IP hostname for the ACSLS server?

-JD.

>You use the externalmanager parameter for a
>TCP/IP, the device parameter for a serial
>attached LMU - the options are mutually exclusive.
>For the TCP/IP attach, use the library name.
>
>I think someone else posted the parameter in
>the case of the serial attachment.
>----- Original Message -----
>From: Justin Derrick <jderrick AT CANADA DOT COM>
>Date: Friday, April 18, 2003 9:28 am
>Subject: Re: Docs Wrong?? 5.1.6.0 ACSLS library path definition problem
>
>>  I suppose the next question is, how do I define the 'external
>>  manager'?    Is that a library definition that the TSM Device Driver
>>  handles?  Can you show me the configuration file (lb.conf?) that
>>  defines this for Solaris?
>>