Jim,

Thanks. It looks like it's the all-local parm that is the problem. It
seems that as long as nds is first in the domain statement things work
OK. I have the following in an opt file and both nds and sys backed
up....domain nds: sys:
no quotes.

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


Jim Smith wrote:

>
> Jim,
>
> This looks like a bug that was introduced in TSM 5.1.5 b/a client.
> For now, it looks like you should be able to code "DOMAIN NDS:" with
> the ":" and it will work.  Pls. instruct level-2 to take an APAR on
> this to get this fixed.
>
> Thanks,
> Jim Smith
> TSM Client Development
>
> I have an ETR open with IBM on this, but just had to bump it from sev
> 3 to
> sev 2 because no one has responded since I opened it on Thurs. a.m.
>
> You can run a manual and it works, tsm> i nds
>
> Tim Brown wrote:
>
> > have seen this problem reported recently, just throwing in my
> complaint
> > netware 5.1 server, service pack4 with tsm client 5.1.5
> >
> > unable to specify nds in domain statement
> >
> > DOMAIN ALL-LOCAL NDS
> > also tried
> > DOMAIN ALL-LOCAL DIR
> >
> > ANS1036S Invalid option 'DOMAIN' found in options file
> >
> > Tim Brown
> > Systems Specialist
> > Central Hudson Gas & Electric
> > 284 South Avenue
> > Poughkeepsie, NY 12601
> >
> > Phone: 845-486-5643
> > Fax: 845-486-5921
> > Pager: 845-455-6985
> >
> > tbrown AT cenhud DOT com
>
> --
> Jim Kirkman
> AIS - Systems
> UNC-Chapel Hill
> 966-5884
>