ADSM-L

Re: TransErrno: Unexpected error from GetFSInfo

2005-11-08 08:18:55
Subject: Re: TransErrno: Unexpected error from GetFSInfo
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 8 Nov 2005 08:17:53 -0500
On Nov 8, 2005, at 7:50 AM, Werner Nussbaumer wrote:

Hi, we use the TSM client version 5.3 on z/OS OMVS (UNIX). If we start
"dsmc incr" then we see the following error messages in dsmerror.log:

08.11.2005 13:06:36 TransErrno: Unexpected error from
GetFSInfo:statfs,
errno = 1127
...

There must be some problems for dsmc scanning the directory.
However is
there any way to see which directories are causing the problems, and
what does error 1127 mean?

See the errno.h header file in your OMVS arena, probably under /usr/
include/.
I don't have access to an OMVS system, but I believe the 1127 is
ETIMEDOUT.
That is most common in a statfs() operation where the file system is a
networked type (e.g., NFS), where the NFSD on the serving system is
having
response problems or there are protocol or network problems.  When it
happens on a local file system, it could mean disk problems, which
should
show up in your OS error log.

A recursive 'ls -lR /fsname' or 'find /fsname -ls' through the file
system may
reveal a problem area.

   Richard Sims

<Prev in Thread] Current Thread [Next in Thread>