Re: Access remote system file as if local

CHGDDMTCPA AUTOSTART(*YES) PWDRQD(*USRIDPWD) ENCALG(*DES)

Might help to see that message id also.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/23/2014 02:59 PM
Subject: Re: Access remote system file as if local
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I added relational database entry for remote system. That allows SQL to
function.

My most recent command:

CRTDDMF FILE(SVBBADPLPP) RMTFILE(BSYDTAA/BaDPLPP) RMTLOCNAME(xxxhis *IP)

No errors

dsppfm svbbadplpp

Authorization failure on DDM TCP/IP connection attempt. Reason code 17 -
The security mechanism requested by the client is not supported or allowed
at the server.

I do not see parms for user and password, Why did yours work? Same user
id/password on both systems?

John McKee

On Tue, Dec 23, 2014 at 12:55 PM, <rob@xxxxxxxxx> wrote:

And *NONSTD is probably for unlike systems, NOT IBM i to IBM i.

From my source IBM i (GDISYS) to a different lpar of IBM i (GDIHQ)

CRTDDMF FILE(QTEMP/LOOKIE) RMTFILE(ERPLXF/RCO) RMTLOCNAME(GDIHQ *IP)
DSPPFM QTEMP/LOOKIE
*...+....1....+....2....+....3....+....4....+....5.
A ??GROUP DEKKO 6928 N 400 E
A ??GRUPO DEKKO MEXICO S.A. DE C.VHENEQUEN NO. 1107
A ??Dekko Global Enterprise 6928 N 400 E
A ?|Group Dekko Holding
A ??Dekko Acquisition Parent 6928 N 400 E
****** END OF DATA ******

Operations ARE limited.
DSPPFM works.
RUNQRY QRYFILE(QTEMP/LOOKIE) does not.
RPG with RLA works fine
RPG with imbedded SQL is probably better served by the CONNECT TO
statement of SQL
STRSQL then SELECT * FROM QTEMP/LOOKIE does not work.
CPYTOIMPF fails asking you to fill in some non supplied SYSTEM

parameter.

Once again, my 'favorite' command falls flat on it's face.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/23/2014 12:36 PM
Subject: Re: Access remote system file as if local
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Yes, DDM is probably what you want..

But the systems ahve to be configured to talk to each other

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/ddp/rbae5prepddm.htm

From a security standpoint look here

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/ddp/rbal1secdb.htm

HTH,
Charles

On Tue, Dec 23, 2014 at 12:19 PM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:

Several files on the remote 520 (v5r3) ned to be accessed. I had the

wild,

and possibly incorrect, notion that a file could be created on the

local

system that pointed to the remote system file. I >thought< this was a

DDM

file. But, my efforts are't working. My first question is how would
authentication for user be accomplished, as neither the CRTDDMF or

CHGDDMF

on the local (v5r4) system have user name and password parameters.

This the command I started with:

CRTDDMF FILE(SOURCE/SALES) RMTFILE(*NONSTD 'SALES.REMOTE')
RMTLOCNAME(NEWYORK)

Does what I want to do not work tis way?
Is this an issue where user and password

must be same on both systems? PLPP) RMTFILE(libray / file)
RMTLOCNAME(xxxx *IP)

Actual library and file names used in command. The xxxx was the
remote system name defined in the host table.

Is it possible? Am I using the right command?

John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.