Thanks Chuck,
The three-part naming creates an implicit connection [to the
first-named entity], essentially performing the CONNECT TO implicitly.
This is how i was thinking/hoping it would work.
It 'seems' like now i have to get the authority setup.
Running this
insert into jrpers/log
select * from prod/jrpers/log
now gives me this
-- Authorization failure on distributed database connection attempt.
Based on additional message information...
It seems like ADDSVRAUTE will be the mechanism for doing this,
and/or the CHGDDMTCPA command -- will have to read/experiment.
John
Additional message info -
Message ID . . . . . . : SQ30082 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Message . . . . : Authorization failure on distributed database
connection
attempt.
Cause . . . . . : A connection attempt failed with reason code . The
reason
codes and their meanings are as follows:
0 -- Unknown cause.
1 -- Password expired.
2 -- Password not valid.
3 -- Password missing.
4 -- Protocol violation.
5 -- User ID not found.
6 -- User ID not valid. For a DB2 for IBM i server, this could mean a
damaged user profile or PASSWORD(*NONE).
7 -- User ID revoked or disabled.
15 -- Security processing at the server failed.
16 -- The new password is not valid.
17 -- The security mechanism requested by the client is not supported or
allowed at the server. See recovery information below.
22 -- Security processing at the client failed.
23 -- CCSID conversion of the password failed.
Recovery . . . : Correct the problem indicated by the reason code, if
possible, and attempt to connect again. A common cause for reason code
17
is that the server requires a password, but because the client does not
have
a password to send, sends only a user ID. Or, the server requires an
encrypted password and the client did not send an encrypted password. A
password can be supplied by the user in two ways:
1 -- By using the USER ... USING ... clause on the SQL CONNECT
statement, or
2 -- By using the ADDSVRAUTE CL command to add a server authorization
entry
for the remote server under the user's profile. The server name (DRDA
RDB
NAME) must be entered in upper case.
The DRDA server can be configured with the CHGDDMTCPA CL command to not
require a password, or to not require an encrypted password.
John Rusling
Senior Developer/Analyst
Quadion LLC
Minnesota Rubber & Plastics
952.927.1419
<br />
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.
midrange.com
