RE: Access remote system file as if local

John,

Firstly the DDM server has to be running on both systems and host entries for each remote system need to be in the corresponding system's host table. If a password is needed by DDM you need to add an authentication list entry (ADDSVRAUTE). This entry provides the password sent to the remote system. For DDM you use QDDMSERVER as the server name.

An alternative to DDM is SQL. Interactively, run STRSQL and connect to the remote system using CONNECT. You will be requested to supply a user id and password. When you are done use DISCONNECT to disconnect from the remote system. Same holds true for embedded SQL.

HTH

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, December 23, 2014 9:19 AM
To: Midrange Systems Technical Discussion
Subject: Access remote system file as if local

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.