Naaaaah..... :-)          It's a bug. The client shouldn't even start. I
haven't checked myself, but I'm sure that the command line interface
wouldn't start with this error. The GUI should behave similarly (i.e. not
start) when this error condition occurs.

Eric's PMR was reopened shortly after he posted this morning, and an APAR
will be opened for this.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Don France (P.A.C.E.)" <DFrance-TSM AT ATT DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/18/2002 13:36
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Bug or request for design?



Since the problem you indicate is beyond the first-failure (ever heard of
FFDC -- first-failure data capture), you really cannot expect the
subsequent
results to be predictable.  The current behavior seems reasonable, to me;
you cannot do a restore -- (and) hopefully, you also cannot do any other
functions, either.

You could request the design change (to prevent further client operations
--
yet still keep the window open so you can see - and respond to - the error
yet still keep the window open so you can see - and respond to - the error
message).  I would consider it a bug if any functions affected by INCLEXCL
were allowed to proceed;  the fact that restore "shows no files" is one
way
of doing that for the restore function -- what about
backup/archive/retrieve?!?