Hi, Thomas - That's a good one...

You can verify whether the number/text inconsistency is a TSM
programming error, or an OS problem, via the following C fragment:

  #include <string.h>
  printf("Errno 13 text = '%s'\n", strerror(13));

(In AIX, at least, error strings are contained in libc.a module
errlst.o array sys_errlist.)

In any case, the scenario is made needlessly worse by one of my pet
peeves about the TSM product: lazy programming in the messages
emitted in error handling. In this case, the programmer shortchanged
the customer by not including the full path of *which* TSM error log
was at issue, so that the customer could unambiguously pursue the
issue. I can envision the case where dsmc was kicked off with specs
which told it to use an error log in a non-standard location and,
finding it could not write to it, reverted to the dsmerror.log in the
install directory to record the message. Depends upon how it's
programmed.

Note also that "permissions" is one cause of the errno 13 (EACCES):
another is locking, as via lockf().

Error log handling was thoroughly overhauled in TSM 5.3 (see the TSM
5.3 FAQ: IBM Technote 1193418). There may have been errors in the
programming of this 5.3 HP-UX client. I'd call it in to TSM Support.

   Richard Sims

On May 23, 2006, at 4:11 PM, Thomas Denier wrote:

We are seeing messages like the following in the error log on one
of our clients:

ANS1520E Failure writing to the Tivoli Storage Manager error log:
errno = 13, No child processes

This is strange in several respects:
1.An error message reporting failure to write to the error log
  appears in the error log.
2.The number indicates a permissions problem, while the text
  following the number indicates a different sort of error,
  which would be associated with error number 10.
3.The permissions on the error log allow reading and writing by
  owner, group, and world.

The client is an HP-UX system running 5.3.2.0 client code.