× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The DDMFile is merely an "implementation object" for the SQL ALIAS. Although the device file appears by DSPDDMF or DSPFD to implement a DDMF pointing to a remote file at the RMTLOCNAME(*LOCAL), note that there is support neither for a member name which the ALIAS accomplishes nor for a Remote Location Name of *LOCAL which appears. And although the DDM File implementing the ALIAS could be changed using CHGDDMF to make the device file generally functional to access a file by the name listed in the NonStandard file name [or even a completely different file], I would not recommend it even though that has no effect on the file.mbr accessed when referencing the ALIAS. I am unsure why CHGDDMF was not prevented from changing a DDMF which exists only to implement an SQL ALIAS.

Regards, Chuck

Jose Antonio Salazar Montenegro wrote:

The DDM Server is up and working fine except for local access,
be it by *SNA or *IP.

The SQL ALIAS worked nicely, it made the connection by SNA.
But I'd like to leave it all on a simple CL and plain CRTDDMF
commands, but it's fine to have the ALIAS option as a last
resort.

Mark S. Waterbury wrote:

Yes, it is possible. For example, I did this:

CRTDDMF FILE(QTEMP/MYDDMF) RMTFILE(MYLIB/MYFILE) RMTLOCNAME('127.0.0.1' *IP)

and this worked fine on my system.

Also, if you create an SQL ALIAS, it creates a DDMF "under the
covers".


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.