DDM example 2: Transfer a program to a target server

In this task, the central server in the DDM network, located in Philadelphia, sends a program named ORDERENT to a remote System/38™ in Chicago.

The program ORDERENT is transferred from the Philadelphia server to the user in Chicago whose user ID is ANDERSON CHICAGO, and then the program is set up so that ORDERENT in Chicago changes the CUSTMAST file in library PGMLIB on the central server in Philadelphia. The read-only function is performed against the local file (in Chicago) and the change is done in the remote file (in Philadelphia).

For this task, two methods are shown for transferring the ORDERENT program in Philadelphia to the remote server in Chicago. Basically, the same sets of commands are used in both methods, except that the second group of commands used in the pass-through method are embedded in Submit Remote Command (SBMRMTCMD) commands used in the SBMRMTCMD command method.

The first method uses pass-through and object distribution, allowing the operator on the source server to set up both servers without involving the target system operator or using the SBMRMTCMD command. This method can be used only for iSeries™ servers or System/38s.
The second method uses the SBMRMTCMD command because, in this task, the target server is a System/38. (The SBMRMTCMD command can be used when the target server is an iSeries server or a System/38.)

DDM example 2: Pass-through method
One set of commands is entered on the source server, a pass-through session is started with the target server, and a second set of commands is entered on the source server and run on the target server.
DDM example 2: SBMRMTCMD command method
Commands needed to accomplish the task are entered at the source server. The source server sends commands that are needed on the target iSeries server by using the Submit Remote Command (SBMRMTCMD) command between the servers.

Parent topic: DDM example 2: ORDERENT application