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 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?!? ----- Original Message ----- From: "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 18, 2002 1:18 AM Subject: Bug or request for design? > Hi *SM-ers! > I would like to know your opinion on something: > I opened a PNR for the following TSM client behavior: > The TSM client (AIX and NT tested) doesn't list any restorable objects when > the options file contains an error. > Try the following on AIX: rename your include/exclude file and start the TSM > client. It returns the error: ANS1036S Invalid option 'INCLEXCL' found in > options file. Click on OK and now click the restore button on the main GUI. > No files are listed! > This was quite disturbing for our UNIX people! When you correct the > include/exclude and you restart the GUI all files are listed again. > To my opinion, this is clearly a bug, but this was the response form the > Tivoli lab: > With both the command line and the GUI, the TSM client informed the user of > the option file problem and location. If the option file problem is > resolved, normal client behavior is returned. This appears to be a request > for a design change. > What do you think? Is it a bug or am I a nit-picker? > Kindest regards, > Eric van Loon
