The following restrictions apply when configuring transferred applications:
Only applications transferred from MCP based hosts can be configured.
The release level of Runtime on your source host must be the same as the release level of Runtime on your target host.
If you configure with the Retain Existing Database property set to N, checks are performed to determine if the database is in use or requiring recovery. In either case, it is assumed that the database is still in use, and you will be prompted for confirmation that you want to continue.
If a Configure Configuration was specified for the transfer, no properties can be changed when running the SMU.
If the Reorgnisation Type segment configuration property for the target configuration is REORGDB, the usercode under which the configure job runs must be the same as the usercode of the target database. If you set a generate family for a configure or generate using REORGDB then either the primary or alternate pack should be the dictionary pack.
The following properties must have the same settings in configuration as in generation, even if a Configure Configuration was not specified for the transfer. In addition, OLTP settings cannot be changed.
System Uses ROC property
When configuring an optional standby System to support a Remote Database on a secondary host, the following restrictions apply:
Any changes to database packs, expected size of database files, and the Copy Audit to Tape property have no effect when running the SMU, as they are defined by the cloning process.
The usercode for the standby application must be the same as for the primary application.
If the old description files need to be saved to the same usercode as the usercode of the target system when DASDL is compiled for a reorganization, the configure program must be started with the usercode of the target system. Otherwise, the old description files are saved to the usercode under which the configure program is running.