Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

945 Update trusted-context testscripts for current cldriver messages and also allow running from remote #951

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

imavo
Copy link
Contributor

@imavo imavo commented Jun 20, 2024

Testcases changed files (3).

Allow trusted-context testcases to run on a hostname that is different from that of the Db2-server (i.e allow to run from remote). Allow the default hostname allowed in the trusted context to be local hostname, but additionally allow the config.py to specify the IP-address of the trusted-context IP-address to support the scenario of the Db2-server being unable to resolve the remote hostname (so can instead use the remote IP-address).

Updated the EXPECTED RESPONSE for one specific SQLCODE to reflect the current (11.5.9) english-language revised-message-text issued by clidriver, this allows the trusted-context testcases to pass , at least when tested on Db2-LUW. ( I lack any i-series or z/os environment access to test against those platforms).

Notice that no additional python modules are required other than those already used by the python-ibmdb-testcases

Signed-off-by: user1 <imavo@users.noreply.github.com>
@bimalkjha bimalkjha merged commit cf653e0 into ibmdb:master Jul 24, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants