DDM Files or same file in different libraries

[Guest.Visitor]

What I am trying to do is have a library that only has files which people can pull in through ODBC excel. I want them only to be able to get to a certain number of files (these files already exist on the 400 in different libraries). Is it possible to have ddm file if you only have one 400? If it is how do I set it up. I can create a DDM File but when I try to display the data I get an error. Is there any other suggestions?

[Guest.Visitor]

Hazen, here is the information you are looking for, as published by MC TeachTalk of January 1999. Courtesy of David Rowswell. Pass-through and DDM Files on a Standalone AS/400 A recent project I worked on was to move all users, programs, and data from one AS/400 to another. The client had recently installed a new model RISC 640. She now wanted to migrate users from an old F20 that was badly overextended. Users on the two machines had communicated with passthrough and Distributed Data Management (DDM)files, and now they were to share the same machine. It was, on the surface, a simple matter of changing programs and recompiling to remove the Start Pass Through (STRPASTHR) commands and the references to DDM files. However, the deadline was very tight, and I had no time to make all the necessary changes. The solution I found may be useful to other people in the same situation. I used a loop-back controller so that a single AS/400 communicates with itself as if it were two separate machines! Start with two AS/400s. The first AS/400 has a local location name AS400A. The second AS/400 has a local location name AS400B. After you have moved everything from AS400B to AS400A, take the following steps to create a loop-back controller: 1. Use the Create APPC Controller (CRT-CTLAPPC) command to create a controller of type *LOCAL. Note that no line description is needed for this type of controller: CRTCTLAPPC CTLD(LOOPBACK) + LINKTYPE(*LOCAL) 2. Create a pair of APPC devices that mirror each other?s local and remote location names: CRTDEVAPPC DEVD(AS400A) + RMTLOCNAME(AS400B) + LCLLOCNAME(AS400A) APPN(*NO) CRTDEVAPPC DEVD(AS400B) + RMTLOCNAME(AS400A) + LCLLOCNAME(AS400B) APPN(*NO) 3. Vary on the devices and the controller and execute the following command to pass through to the same AS/400: STRPASTHR RMTLOCNAME(AS400B) + LCLLOCNAME(AS400A) or (going in the other direction) execute this command: STRPASTHR RMTLOCNAME(AS400A) + LCLLOCNAME(AS400B) DDM files will work in the same way, as long as the loop-back devices are created with the correct local and remote location names. Once the loop-back controller is up and running, the pass-through programs and DDM files can be removed at a more leisurely pace. HTH