RECONFIGURE (Reconfiguration)
- Last UpdatedFeb 22, 2022
- 2 minute read
Function:
Starts a reconfiguration operation. The administrator can specify that the reference numbers stay the same in the reconfigured Database (DB). The administrator can specify that session information such as the original session comment, session number, username and original date stays the same in the reconfigured DB.
Description:
The administrator can specify that the reference numbers stay the same in the reconfigured DB. The SAMEREF option will fail if:
-
The DB specified in the TO DB command has a different DB Number from the DB given in the FROM DB command.
-
An element already exists with the same reference number.
-
The administrator can specify that session information stays the same in the reconfigured DB by using the SESSIONS option:
-
The option is not valid for System, or Global DBs.
-
The option is not available if the administrator is doing a partial reconfiguration. The administrator must use the RCFCOPY ALL command with RECONFIG SESSIONS.
-
For extracts, RECONFIG SESSIONS will be assumed, even if the option is not given.
-
For Draft DBs, the picture files will be ignored.
-
The reconfigured data must go TO a file.
-
After reconfiguration, data can be read back in from the file, replacing the original DB data. The SAMEREF option is assumed when reading the data.
-
When reading in data created by RECONFIG SESSIONS, the DB Number and extract number must be the same as the originating DB Number and extract number.
-
If errors occur when reading in data created by RECONFIG SESSIONS, the data is not saved unless the administrator uses the RECONFIG FORCE option.
The normal procedure for reconfiguring a DB and maintaining the reference numbers is as follows:
-
Reconfigure from the target DB to a file.
-
Delete the target DB, and create a new one with the same DB Number.
-
Reconfigure from the file to the new DB.
For Global Projects, note the following:
-
To reconfigure the Global DB in a Global Project, give the command FROM GLOBAL, followed by RECONFIGURE. Refer to Reconfiguration for further information.
-
In a Global Project, the TO NEW option is only valid at the Hub (Refer to the TO command).
-
To reconfigure a Satellite transaction DB, reconfigure the DB to file, renew the file to empty it (Refer to the RENEW command), stop the daemon at the Satellite, and then reconfigure the transaction DB from file.
-
If the TO DB is allocated to other Locations, the RECOVER command should be used to copy the DB to all Secondary Locations.
Examples:
|
RECONFIGURE |
Command Syntax:
|
>--- RECONfigure ---+---- FORCE ----. |
Related Commands:
CREATEDBFILE (Project Definition)