I didn't set up the backupsets so thanks for the idea of checking the
unicode settings/using FSID, that might just do it.

Now you know why no one reads the FAQ, we just ask, and you answer....

Hoisted on your own petard, eh? :)



Dale Jolliff
Sungard Midrange Storage Administration
Office Telephone: (856) 566-5022





Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/25/2004 09:18 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: error during generate backupsets


>This error message appears to be associated with a particular node each
>time a generate backupset is done;
>Would running an archive conversion on the node help alleviate this, or
is
>this something more serious?
>
>ANR9999D smexec.c(7690): ThreadId<79> Internal error in obtaining the
node
>conversion state for Session 22036.

Dale - More details may help in the pursuit of this problem, such as the
TSM
       software levels of the server and the client whose filespace is
involved, plus the command syntax used.  The history of this filespace may
shed light on issues.

>From my understanding, this kind of error occurs when the server does not
understand the full nature of the client, and may occur where there is an
inconsistency across TSM server software modules.
If this was a Unicode-enabled client and the filespace involved is
Unicode,
be sure to either specify UNIcode when providing the filespace name, or
use
an FSID, as wacky results may ensue if the server misinterprets text.

  Richard Sims