The "DeviceIoControl()" messages: these are merely annoying, and can be
safely ignored. APAR IC34308 has been opened to suppress these messages,
and will be fixed in a future 5.1 PTF (there are no plans at this time to
fix it in 4.2).

The "GetDfsInfo()" messages regarding RC 1722: this is unrelated to the
"DeviceIoControl()" messages. The 1722 is a Windows return code meaning
RPC_S_SERVER_UNAVAILABLE (The RPC server is unavailable). Try backing up
the system state with ntbackup and see if you get a similar error. If so,
then this is an MS problem and needs to be pursued with them. If ntbackup
does not get the error, then you should contact IBM support for further
assistance.

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.eyebm DOT com (change eye to i to reply)

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




Michel Engels <Michel.Engels AT DEVOTEAM DOT BE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/17/2002 07:01
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        DeviceIoControl: Win32 RC1 from FileOpen



Environment:

TSM Server: AIX with TSM V5.1.1.4
Client : W2K with TSM 5.1.1

Client is connected to an EMC NAS and used to backup the NAS

We obtain the message "FileOpen(): Unable to determine current compression
state
of 'unc-name of file'. DeviceIoControl: Win32 RC=1" for every file that we
want
to backup. Sometimes we see the message "GetDfsInfo(): EntryPath=unc-name
of
file, Server(null), Share(null) NetDfsGetInfo() returns RC=1722

We use this client to be able to backup the datamover because the TDP
apparently
does not yet support an EMC environment.

Did anyone experience the same problem?

Michel Engels
TSM Consultant
Devoteam Belgium