ADSM-L

Re: DOMDSMC TDP for Domino on Solaris error

2005-07-09 08:03:06
Subject: Re: DOMDSMC TDP for Domino on Solaris error
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 9 Jul 2005 08:02:50 -0400
On Jul 8, 2005, at 4:10 PM, Zoltan Forray/AC/VCU wrote:

How do you get to that Technote ?   I tried to search IBM for it
and got no hits.


I was wondering if someone would ask.  Instincts honed by years of
online research experience...
I'll surrender this one secret...  :-)
I knew from experience that the sought info may not be identified by
the evidenced error ANS message ID; and searching on the short error
number (959) would be too vague. And knowing that the TDPs are based
upon the TSM API, and that API error numbers have C #define names, I
looked up the 959 in the API manual, found its DSM_RC_FILE_IS_SYMLINK
name, and then searched the IBM database for that. Bingo.
Simple.  :-)

It's still bugging me where that "pesky asterisk" (as Consumer
Reports likes to say) is coming from in message "ANS1192E (RC959)
Specifying the error log '*' as a symbolic link is not allowed.".  If
you haven't already, do 'dsmc q opt' and see something odd shows up -
though I would expect that to more likely show up issues with
standard B/A client options.  Another stretch of the imagination: An
asterisk is the character which starts a comment on an option file
line. Perhaps the asterisk is sneaking in from a comment somehow,
perhaps through a tortured line, which may inadvertently contain
binary. Where I'm suspicious of something like that, I use the emacs
editor to expose binary in files; or in Unix you can do 'od -cx
<Filename> | less' and look for binary other than Carriage Return and
Line Feed.

    Richard Sims