Re: DDM file between v7r3 and v5r4

Some further testing found that if I create an alias on v7r3 pointing to the physical file on v5r4, e.g.

CREATE ALIAS mylib/myFile FOR rmtv5r4/mylib/myFile

then on v7r3, both

SELECT * FROM myLib/myFile

and

DSPPFM myLib/myFile

retrieve the data with no problem.


But if I use

CREATE ALIAS mylib/myFile FOR rmtv5r4/mylib/myAlias

then on v7r3, only

SELECT * FROM myLib/myFile

works, and

DSPPFM myLib/myFile

fails with the same errors as RPG:

[CPI9200] DDM object myFile in myLib uses remote object myLib/myAlias.
[CPF9162] Cannot establish DDM connection with remote system.
[CPF4207] Cannot open DDM file SYSCDEP1 in UTLIB.
[CPF9845] Error occurred while opening file SYSCDEP1.

On the v5r4 system, the job pointed to by the CPI9200 error shows

[CPF4364] Remote location *LOCAL for program device DDMDEVICE was not found
[CPF9162] Cannot establish DDM connection with remote system.
[CPF4207] Cannot open DDM file myAlias in myLib.

And actually, on the v5r4 machine, using SELECT * FROM myLib/myAlias works fine, but DSPPFM myLib/myAlias gets the same error as when running it from the v7r3 machine. And it doesn't matter whether the CREATE ALIAS on v5r4 specifies a particular member or not, e.g. CREATE ALIAS myLib/myAlias FOR myLib/myFile (myMbr) or CREATE ALIAS myLib/myAlias FOR myLib/myFile  -- *Peter Dow*

/Dow Software Services, Inc. 909 793-9050 petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx> pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /