Thank you for your answer. In errno.h there is:

                             /* Connection timed out.  The */
#define ETIMEDOUT      1127  /*  connection to a remote    */
                             /*  machine has timed out.    * 
                              *  If the connection timed   * 
                              *  out during execution of   * 
                              *  the function that reported* 
                              *  this error (as opposed to * 
                              *  timing out prior to the   * 
                              *  function being called),   * 
                              *  it is unspecified whether * 
                              *  the function has completed* 
                              *  some or all of the        * 
                              *  documented behavior       * 
                              *  associated with a         * 
                              *  successful completion of  * 
                              *  the function.             */

The only thing that would be nice is if dsmc would display to directory
which causes problems.

Regards
Werner Nussbaumer 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Dienstag, 8. November 2005 14:18
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TransErrno: Unexpected error from GetFSInfo

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