Run The Copy Scripts DB Process

After you have a "copy scripts" DB process in the target database, you should add a table rule to its primary instruction to define which script(s) to copy from the demonstration database. For example, if you want to copy a single script called CI_WSS, you'd have a table rule that looks as follows

Table: CI_SCR
Override Condition: #CI_SCR.SCR_CD='CI_WSS'

If you do not introduce this table rule to the primary instruction of the DB process, ALL scripts in the demonstration database will be copied to the target database (and this may be exactly what you want to do).

Note: Tables rules are WHERE clauses. A table rule is simply the contents of a WHERE clause except the tables names are prefixed with #. This means that you can have table rules that contain LIKE conditions, subqueries, etc.

At this point, you're ready to submit the background process identified on your "copy scripts" DB process. This background process highlights the differences between the scripts in the demonstration database and the target database (the target database is the environment in which you submit the background process).

Note: The background process you submit is typically named the same as the DB process that contains the rules. If you used the CL-COPDB background process to transfer the "copy scripts" DB process from the demo database, it will have also configured a batch control and linked it to the "copy scripts" DB process. This batch control has the same name as its related DB process (this is just a naming convention, it's not a rule). This means that you'd submit a batch control called CI_COPSC in order to execute the CI_COPSC DB process.

When you submit the CI_COPSC background process, you must supply it with an environment reference that points to the source database (i.e., the demonstration database).

When the CI_COPSC process runs, it simply highlights differences between the scripts in your source database and the target database. It creates a root object in the target database for every script that is not the same in the two environments (actually, it only concerns itself with scripts that match the criteria on the table rule described above). You can use the Difference Query to review these root objects and approve or reject them.

Note: Auto approval. When you submit CI_COPSC, you can indicate that all root objects should be marked as approved (thus saving yourself the step of manually approving them).

After you've approved the root object(s) associated with the script(s) that you want copied, submit the CL-APPCH batch process to cause your target database to be changed. You must supply the CL-APPCH process with two parameters:

The DB process of the "copy scripts" DB process (i.e., CI_COPSC)
The environment reference that identifies the source database (i.e., the demonstration database)