[
https://issues.apache.org/jira/browse/DERBY-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4004:
----------------------------------
Attachment: derby-4004_diff.txt
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.
> Remove required RDBNAM from ACCSEC. Use SECCHK RDBNAM if none is provided on
> ACCSEC
> ------------------------------------------------------------------------------------
>
> Key: DERBY-4004
> URL: https://issues.apache.org/jira/browse/DERBY-4004
> Project: Derby
> Issue Type: Sub-task
> Components: Network Client, Network Server
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-4004_diff.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
