The least I could do was post the solution here. Regards. On Thu, Oct 11, 2012 at 12:10 PM, IT Pro <[email protected]> wrote: > I completely agree, Peter. > Thanks for your understanding. > Aitor. > > On Wed, Oct 10, 2012 at 10:36 AM, Hunkeler Peter (KIUP 4) > <[email protected]> wrote: >>>Seeing that the message is quite misleading, yes it may deserve >>>opening an APAR. I didn't think about it really. I have never opened >>>an APAR before, but my boss won't be in the mood of my getting into >>>the process of creating one. There's always work to be done, and I >>>must not "waste time". I just obey (this doesn't mean IBM does not >>>deserve getting warned about this to correct the manual). >> >> I perfectly understand your situation, however, you did waste a lot of >> time just because the message was so misleading... >> >> It would be an APAR against the code not the manual. syslogd should >> differentiate between the different reasons why it cannot proceed. At >> least one additional (different) message would be appropriate. >> >> -- >> Peter Hunkeler >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
