RE: Adopted Authority to get DDM Access.

Thanks Gary. That did it.

Mark D. Walter
Business to Business Data Integration Specialist
Certified IBM System I Specialist
Paragon Consulting Services, Inc.
mwalter@xxxxxxxxxxxxxxx
717-764-7909 Ext. (1)26

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Monday, April 25, 2011 2:41 PM
To: Midrange Systems Technical Discussion
Subject: RE: Adopted Authority to get DDM Access.

Mark,



Adopted authority does not cross systems. The error may be on the
target system. Try adding a server authentication list entry for the
DDM server.



ADDSVRAUTE USRPRF(userprf) SERVER(QDDMSERVER) USRID(tgtusrprf)
PASSWORD('tgtuserpassword ')



userprf = The local system's user profile

tgttusrprf = The user profile to sign onto the target system with

tgtuserpassword = The password to use with the target system user
profile



tgtusrprf needs enough authority on/to the target file to allow your
program/process to run.





Gary



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Walter
Sent: Monday, April 25, 2011 11:14 AM
To: Midrange Systems Technical Discussion
Subject: Adopted Authority to get DDM Access.



I have 3 *IP DDM files over a files on another iSeries. The issue is
that the user profiles are not the same between boxes. I created a CL
program to call the RPG. I changed the CL's ownership to a common
profile and changed the program's user profile argument to *OWNER and to
use adopted authority. But, when I call from a non-like user profile, it
still fails with CPF4207.



Are there any options to get this to work with non-like user profiles.



Thanks in advance,



Mark.



Mark D. Walter

Business to Business Data Integration Specialist

Certified IBM System I Specialist

Paragon Consulting Services, Inc.

mwalter@xxxxxxxxxxxxxxx

717-764-7909 Ext. (1)26