I finally heard back from TSM support.
1) You are unable to use a station restricted account. Which means that
according to our security guidelines, I need to change the tsm account
password (for 150 servers)every 45 days :(

2) The only syntax that will work is .cn=user.ou=container.o=org,
.user.container.org won't work.

3) As Jim points out, both are required.

-----Original Message-----
From: Jim Kirkman [mailto:jmk AT EMAIL.UNC DOT EDU]
Sent: Thursday, October 03, 2002 4:54 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Station restrict Netware client


Doug,

In order to back up you need both tsa410 and tsands, usually loaded in the
autoexec.ncf. If an unrestricted user works then you should be able to use
that ID to authenticate and run
your incr (as long as it has admin rights). Or am I missing something?
Normally the syntax is .ID.context.container

Jim

"Nelson, Doug" wrote:

> Server win 2k 5.1.1 client Netware 4.2 4.2.2 tsm client
>
>    Problems:
> 1) I'm unable to use a station restricted netware user (restricted to the
server node where the client is installed). An unrestricted user in the
servers' nds context works fine.
>
> 2) I'm unable to use a fully qualified NDS account name to login after
issuing the
> load dsmc query tsa nds
> command. I've tried x.x.x  .x.x.x  and u=x.ou=x.o=x  format. The client is
(for example) server.test.testcorp
> and I want to use client.testcorp as the nds login. What is the correct
format for the id?
>
> 3) Can I just use nds to backup the server (data, system specific info,
and nds info for the container) or do I need to use a combination of tsa and
tsa nds?
> (load tsa410
>  load dsmc query tsa
>
>  load tsands
>  load dsmc query tsa nds)
>
>                                                 Thanks.
>
> Douglas C. Nelson
> Distributed Computing Consultant
> Alltel Information Services
> Chittenden Data Center
> 2 Burlington Square
> Burlington, Vt. 05401
> 802-660-2336

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884