"robert" <gn*****@rcn.com> wrote in message
news:da**************************@posting.google.c om...
well, a COBOL stored procedure has stopped functioning. we pass
up data from UDB (v 8.1.4 in this case) to 390 (v 7.1.1). had
been working just fine. the application gets a SQL 100, no row.
when i look at the staging table where the stored procedure
writes, the rows are there. the destination table doesn't get the
row.
db2diag.log has this code and a text (from memory) "the credential
is not valid".
i can log on to the 390 database with the same userid/pwd that the
application is using, and see the staging table rows. i did a
search of the 390 books on-line, but got no hits on any of 3282,
3282N, or SQL3282N.
I just looked at my UDB for Windows V7.2 Message Reference and found this:
----------------------------------------------------------------------------
------------------------------------
SQL3282N The supplied credentials are not valid.
Explanation: Either or both the distinguished name (DN) of the user and the
password that were specified were not valid.
User Response: Resubmit the command using valid values for both the
distinguished name (DN) of the user and the password.
----------------------------------------------------------------------------
-------------------------------------
The message seems to be originating from your workstation, not your
mainframe. The mainframe appears to be passing the wrong userid or password
to the workstation.
Rhino
