Copying Parts of Databases

The RCFCOPY ALL command copies all the elements in the source Database (DB) World into the destination DB World. If the World of the destination DB already contains members, then the elements from the source DB are added to these.

The RCFCOPY command can be used to define the root elements to be copied. A root element is any element owned by the World, that is:

When a root element is copied, all elements owned by it are also copied. A maximum of 300 root elements may be specified in a single copy list.

The selective command RCFCOPY SPECIFICATIONS cause the first root elements of type SPWL, to be copied from the list part of the World in the source DB.

To copy only part of a DB, one or more root elements must be specified (by name or reference number) in a RCFCOPY command. For example:

Elements of any other types will be copied into the destination DB as null elements, that is they will be created as floating elements, not owned by any higher-level element. This does not mean that they are inaccessible. As long as such an element is named (or the administrator knows its new reference number) it can be incorporated as a member of any suitable parent element by using the INCLUDE command.

If the administrator is not at a top level element, there must be an existing element in the destination DB into whose list part they want to incorporate the element being copied. This is done using the INTO option of the RCFCOPY command. For example:

This would copy the Zone /ZONE5A and make it the last member of the Site /SITE-3.

If the intended owning element does not already exist in the destination DB at the beginning of PASS 2, the listed root element will not be copied. For example:

This is not allowed.

The INTO command cannot be used when the destination is FILES rather then a DB. The word AND and the comma (,) may be used as separators to improve readability:

Several RCFCOPY commands can be given in sequence to add elements to the copy list. For example:

This is exactly equivalent to the RCFCOPY command in the previous example.

If an element is quoted in the copy list but does not exist in the source DB, an error message is output and the element is not copied. Since RCFCOPY commands are additive, a correcting command may be given on the next line. For example:

Since SITE1, SITE2 and SITE4 are already in the copy list, all that is needed to add SITE3 is:

Note:
Partial reconfiguration of PADD DBs is only allowed for picture elements (i.e. SHEE, BACK, OVER, SYLB, LALB) and above.

Setting External References

In cases where the administrator has made a partial copy of a DB, sometimes it is necessary for the administrator to make sure the external references are correct in the copied elements.

For example, if the administrator moved a piping zone to a different DB while maintaining the references to an equipment zone which was to remain it the original DB, the copied piping zone could have unset external references and the equipment zone would remain connected to the original piping zone.

In these cases the administrator can use the ALLCONnections option to set the external references for the reconfigured elements:

This will set all references including those within the original DB not in the list of copied elements.

To update the references of the original DB to point to the new copied elements, use the RCFUPDATE INTERNAL command described in Section Updating References into a Reconfigured Database.