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
08.11.2005 13:07:45 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:09:42 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:10:51 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:13:57 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:17:04 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:20:10 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:23:17 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:26:23 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:29:29 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:32:38 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:35:47 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:38:56 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:42:02 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:45:09 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?

Thanks for any help
Regards
Werner Nussbaumer

Reply via email to