Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
10.5.1.1
-
None
-
Patch Available
Description
Currently Derby requires RDBNAM on ACCSEC. The DDM spec lists it as optional. For DERBY-728, in order to negotiate the encoding, EXCSAT and ACCSEC will need to remain EBCDIC, so we want the RDBNAM to be optional. We can use the RDBNAM sent in SECCHK instead.
Once this is done. Client can be changed to only send RDBNAM on ACCSEC if an EBCDIC conversion is possible.
Here is a preliminary patch for this issue. I am running tests now. The change makes RDBNAM optional on ACCSEC and initialize the datbase name on SECCHK instead. I added two protocol tests. One for successful connection if there is no RDBNAM on ACCSEC but we send it on SECCHK. Another to test that we throw a SYNTAXRM if there is no RDBNAM on either ACCSEC or SECCHK.