Initiate the Runtime Transfer Utility with the following command:
R $(<Runtime Usercode>) NGENnn/RTU ON <Runtime pack>
Transfer Startup Screen
The first Runtime Transfer screen is the Transfer Startup screen. This screen allows you to identify the segment involved in the transfer, the configurations that are used, and the name of the RTU file containing the configuration information.
Enter the following in the startup screen.
Field Name | Description |
|---|---|
| Business Segment | Enter the name of the <<segment>> involved in the transfer. It verifies that the correct RTU file is used. |
| Generate Set used for Generate | Enter the name of the configuration to build or configure the Source system. |
| Configure Generate Set | Enter the name of the configuration to configure the Target system. Leave this field blank, if you are configuring the Target system manually. |
| RDB Generate Set | Leave this field blank. |
| RTU file title | Enter the title of the file that was uploaded for this transfer. Include the usercode and family name, if required. |
Transfer Selection Screen
The Transfer Selection screen allows you to enter the details of the transfer and to specify whether all or part of the system is transferred.
Enter the following in the Transfer Selection screen.
Field Name | Description |
|---|---|
| Transfer Medium | Transfer Medium is the medium to transfer the files to the Target host. Enter BNA. The transfer files are copied using BNA to the Target host name specified on the Transfer Creation screen. |
| Tape Tfr Interim Medium | Since BNA is the Transfer Medium, enter Blank. |
| Tfr/Configure All Ispec Code | Enter Y to transfer the full application. |
| System and all tfr reports | Enter Y in this property to transfer the application including all Reports that have Y in the transferable property on the Report Options screen. Enter N to obtain a set of screens for selecting individual Reports to be transferred. By default, the value is Y. Prior to the transfer, you must build the application and all Reports to be transferred using an MCP-based configuration. |
| Compile Free Configure | Leave the default value as N. |
| Transfer Static Listbox File | Enter Y in this property if you transfer a Static Listbox data file. |
| Auto Initiate Configure Program | Enter Y to initiate the Configure Utility on the target host automatically. The configure phase of the transfer starts automatically and does not require any intervention unless a problem occurs. |
| RDB Generate Set | This property displays the name of the RDB Configuration associated with the configuration. You cannot alter this value. |
| Clone DB | DB Centre establishes the secondary database. Set this field to N. |
Transfer Creation Screen
The Transfer Creation screen allows you to define other options associated with the initiation of a WFL job for your application transfer. You can specify a parameter file with WFL code to initiate user-defined tasks throughout the transfer process.
Field Name | Description |
|---|---|
| Transfer Parameter Name | Enter the name of the WFL Include file containing the transfer parameters that you want to use for this transfer run. Any transfer parameters that you enter manually overrides the settings in the WFL INCLUDE file. If the INCLUDE file does not exist, the following error message is displayed: “Saved transfer parameter not resident” The name of the parameter file is: (<Usercode>)<Segment>/INCLUDE/<saved transfer parameter> on <runtimepack> Where:
Enter only the last node, <saved transfer parameter>, in the Transfer Parameter Name property. |
| Tfr Source Files and Compile | Enter N to transfer Object files. |
| Copy Database Data | Leave the default value as N. |
| Auto Initiate of Transfer Job | Enter Y if the transfer job should be started automatically after the Runtime Transfer Utility is complete. |
| Transfer Job Usercode/ Password | Enter the usercode and password under which your transfer job runs on the source host. These properties do not govern the usercode of your application on the target host. |
Transmitting the Transfer Creation Screen
After you transmit the Transfer Creation screen, RTU proceeds to the next stage depending on the settings of some of the options.
If System and all tfr reports of the Transfer Selection screen is set to N, RTU proceeds to the Selected Transfer screen.
If System and all tfr reports of the Transfer Selection screen is set to Y and Auto Initiate of Transfer Job is set to Y, RTU initiates the TRANSFER/SETUP job and terminates.
If System and all tfr reports of the Transfer Selection screen is set to Y and Auto Initiate of Transfer Job is set to N, RTU terminates without initiating the TRANSFER/SETUP job. Then, you must manually start the TRANSFER/SETUP job.
From this point, the transfer process proceeds through the transfer phase and the configure phase. At the end of the configure phase, the Primary system is migrated to the AB Suite product.