Define/Redefine and Generate Scripts Commands
You may need to select the Define/Redefine and Generate Scripts commands if you create a new data source without customizing it (that is, you selected no post-add action in the Add Data Source dialog box).
The Define/Redefine command reads the DMSII information from the data source and starts building the relational database tables, layouts, and control information for the data source. If you run the Define/Redefine command after the relational database is created, it determines what has changed on the DMSII side and attempts to match it in the relational database while preserving the existing information.
Note: If your DMSII data includes links, running the Define/Redefine command may fail. To prevent this problem, set the Mode of any data sets with links to 0:Clone in the Properties view. Alternatively, you can force the recloning of data sets from a command line. Run the dbutility redefine command with the -y option or the dbutility redefine all command. (The dbutility -y option has no equivalent in the Client Console.)
To define a data source
The Generate Scripts command creates a set of script files and puts them in the dbscripts subdirectory of the data source's working directory. These script files include SQL scripts the Client uses to create tables and indexes, drop tables, and remove false duplicate records from tables. Also included are command files (shell scripts for UNIX clients) that run bulk loader tasks. These scripts are saved to the working directory of the data source. (Approximately six script files are created for each DMSII data table.)
To generate scripts for a data source