Errors after Netware client upgrade

2003-04-02 Thread Shannon Bach
OS 390 MVS 2.10 TSM Server V4.2.0
Server NW6 (5.60) TSM Client V5.1.0.0

Just upgraded the Novell Server on 03/29/03 and have been getting the
following messages ever since;

03/30/2003 19:40:43 (TSA600.NLM 6.0 291) An invalid path was used.
03/30/2003 19:40:43 PrivIncrFileSpace: Received rc=104 from
fioGetDirEntries:  Server Specific Info
03/31/2003 19:40:58 (TSA600.NLM 6.0 291) An invalid path was used.
03/31/2003 19:40:58 PrivIncrFileSpace: Received rc=104 from
fioGetDirEntries:  Server Specific Info
04/01/2003 19:40:48 (TSA600.NLM 6.0 291) An invalid path was used.
04/01/2003 19:40:48 PrivIncrFileSpace: Received rc=104 from
fioGetDirEntries:  Server Specific Info

I have searched the list, IBM, etc., with no results.  Has anyone seen this
particular error before?  I did get a hit on the 'invalid path' but that
was for a WIN client, not NetWare.

Shannon


Re: Errors after Netware client upgrade

2003-04-02 Thread Jim Kirkman
Shannon,

You don't say just when you get these errors, should we assume the are when you
are running a backup?

What level of the tsa's are you running, that is often an issue. Also, is this
only with the Server Specific Info or for any data?

Sorry to pepper you with questions, not answers!

Shannon Bach wrote:

 OS 390 MVS 2.10 TSM Server V4.2.0
 Server NW6 (5.60) TSM Client V5.1.0.0

 Just upgraded the Novell Server on 03/29/03 and have been getting the
 following messages ever since;

 03/30/2003 19:40:43 (TSA600.NLM 6.0 291) An invalid path was used.
 03/30/2003 19:40:43 PrivIncrFileSpace: Received rc=104 from
 fioGetDirEntries:  Server Specific Info
 03/31/2003 19:40:58 (TSA600.NLM 6.0 291) An invalid path was used.
 03/31/2003 19:40:58 PrivIncrFileSpace: Received rc=104 from
 fioGetDirEntries:  Server Specific Info
 04/01/2003 19:40:48 (TSA600.NLM 6.0 291) An invalid path was used.
 04/01/2003 19:40:48 PrivIncrFileSpace: Received rc=104 from
 fioGetDirEntries:  Server Specific Info

 I have searched the list, IBM, etc., with no results.  Has anyone seen this
 particular error before?  I did get a hit on the 'invalid path' but that
 was for a WIN client, not NetWare.

 Shannon

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