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 displayed 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 Transfer Startup screen.
Field name | Description |
|---|---|
| Business Segment | Enter the name of the <<segment>> involved in the transfer. It verifies that you use the correct RTU file. |
| Generate Set used for Generate | Enter the name of the Configure configuration. |
| Configure Generate Set | Enter the name of the configuration that configures the Target system. Enter the name of the RDB configuration. |
| 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
Use the Transfer Selection screen to enter the details of the transfer and specify whether you can transfer all or part of the system.
Enter the following in the Transfer Selection screen.
Field Name | Description |
|---|---|
Transfer Medium | Enter BNA. |
| Tfr/Configure All Ispec Code | Enter Y to transfer the entire 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 in the Report Options screen. |
| 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 no intervention is required unless a problem occurs. This is valid only if the Transfer medium property is set to BNA and you are using a Configure Configuration. |
| RDB Generate Set | Enter blanks. |
| Clone DB | Enter N. |
Transfer Creation Screen
The Transfer Creation screen defines 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.
Enter the following in the Transfer Creation screen.
Field Name | Description |
|---|---|
| Transfer Parameter Name | Enter the name of the WFL INCLUDE file containing the transfer parameters 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 to initiate the transfer job automatically when the Runtime Transfer Utility is complete. The various files and programs are copied from the system, database, usercode, object, and dictionary packs and moved to the pack or tape specified on the Transfer Selection screen. |
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. |
Target Computer (Host) Name | Enter the target host name in this property. |
Transmitting the Transfer Creation Screen
After the transmission of Transfer Creation screen, RTU proceeds to the next stage depending on how certain options are set.
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. You must manually start the TRANSFER/SETUP job.
Recovering Missing Database Files during Runtime Configuration Phase
When an AB Suite system is set up as an RDB system using RDBUTILITY or DB Center, none of the AB Suite database libraries or control files are copied from the primary system to the Secondary database in preparation for a transfer of the Primary system to the Standby system. During the transfer of the Primary system to the Standby system, the Configure Utility detects when the LINCCNTL file is missing for the Standby system. In such cases, the Configure job copies the LINCCNTL file and the DBRECORD/ LAYOUT file into the Standby system before the Configure job starts. If the Configure Utility needs to copy the LINCCNTL for the Standby system, the Configure job prompts you to confirm that a you should create a clone and you should compile the appropriate libraries or copy the files; else, those files are not compiled or copied.
During the CONFIGURE phase, the waiting entry appears. Respond to the waiting entry by entering:
<MIX> AX YES
From this point onward, the CONFIGURE phase continues to completion and an RDB capable system is set up in AB Suite with DB Center.