When transferring systems using RTU, you have to consider the following three fundamental processes that are involved.
Creating the RTU file.
Running the RTU utility.
Starting the Configure process.
Creating the RTU File
An RTU file contains the data from the Configuration properties that is required by the RTU utility. This file is transferred to the MCP system where it is visible to the RTU utility when it is run.
To create an RTU file, perform the following:
Create a Configuration for RTU. The maximum length is limited to ten characters.
In the Folder properties, set the Generate Runtime Transfer Utility File to folder configuration property to True.
Under the Runtime Transfer Utility configuration category, enter the Filename and fill in the details of the Configuration set used for the Build of the Base system in the appropriate properties.
Build the folder to create the RTU file.
Copy the file to your ClearPath MCP host using FTP or MCP extensions to Windows explorer. The file should be copied as EBCDIC characters in a type DATA file.
Running the RTU Utility
The RTU utility is initiated using the following command:
(<Runtime usercode>)NGEN28/RTU ON <Runtime dictionary pack>This utility has three to four screens depending on the options chosen. To illustrate the screens and explain their use in an RDB-specific environment, a brief description of most common usage is given below. Refer to Running the Runtime Transfer Utility for more information.
The following are the most common RTU screens:
Transfer Startup Screen
This screen enables you to specify the System to be transferred and where it is to be transferred to. The usage of this screen varies with the context and this is described in full in Section 5.
Transfer Selection Screen
Use this screen to specify whether to transfer all or part of your System, and to define the transfer method and identifies the transfer media. The Transfer Medium field is most often modified and changed to DISK as most transfers either being within the same host or between networked hosts. The default for this field is TAPE.
The other fields of the Transfer Options section left at the default settings - which causes the system and all transferable reports to be transferred. If you set the System and all tfr reports field to N then the next screen presented allows selection of a system transfer (Yes or No) and each individual report. This selection screen is not shown in this Section as it has no bearing on the use of RDB.
The data in the fields in the he Configure Options section shows information about the target system.
Transfer Creation Screen
Use the Transfer Creation screen to define other options associated with the initiation of a WFL job for your System Transfer. You have to specify the values for only the following fields in the Transfer Job section: Usercode, Accesscode (if required) and associated passwords, chargecode, and Job Family. Note that the Target computer (host) name should be changed if required.
The RTU utility completes after starting a transfer WFL job. After completion, You will find a set of files called RUNTIMETRANSFER/= - on the <Target computer (host) name> host under the usercode you specified for transfer, both on the Transfer Creation Screen and on the pack specified as the Configure work pack as reported on the Transfer Selection screen. These files are ready for installation by running the configure process.
Starting the Configure Process
To start the configure process, log on to the host using the usercode where the RUNTIMETRANSFER/= files are located and use the RUN command (CANDE or MARC) as follows:
RUN $RUNTIMETRANSFER/<host name>/<Configuration set name>/<system name>/CONFIGURE ON <pack name>.
The applicable values used for the Configuration set and system names are specified each time this process is used.