Description of problem:
Any -ve error code number reported as Illegal error by ldclt.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.1.6-25.el7.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Perform any OpenLDAP operation with ldclt which should give negative error for example 
/usr/bin/ldclt-bin -h dhcp201-149.englab.pnq.redhat.com -p 34004 -e
esearch -e bindeach -e randomauthid -e randomauthidlow=1 -e
randomauthidhigh=9999 -o mech=DIGEST-MD5 -o authid=loginXXXX -w redhat
-s base -b o=saslstress.com -f uid=modify* -V -q -E 10004 -n 10 -N
20000 -T 1000 -W 2

2. It will give ldclt[12170]: Illegal error number -6 in SASL

Actual results:
ldclt[12170]: Illegal error number -6 in SASL

Expected results:
It should report better error message.

More Info::(By Nathan)
Negative LDAP errors are local (client-side) errors in OpenLDAP.  Here
is how -6 is defined:

--------------------------------------------------------------
#define LDAP_AUTH_UNKNOWN                               (-6)
--------------------------------------------------------------

In mozldap, there were no negative error codes at all.  It might be that
ldclt doesn't expect a negative code, and reports a poor error message
when it encounters it.  This error code could be returned if an unknown
SASL mechanism was attempted (though I haven't confirmed this).

There is a minor ldclt bug in that it should expect that negative error
codes could be encountered.  This code is the culprit:

----------------------------------------------------------------
  /*
   * Update the counters
   */
  if ((err <= 0) || (err >= MAX_ERROR_NB))
  {
    fprintf (stderr, "ldclt[%d]: Illegal error number %d\n", mctx.pid, err);
    fflush (stderr);
    mctx.errorsBad++;
  }
----------------------------------------------------------------