Object Specifications
Object Specification Syntax
<Object type>: ALL[(<Version number>)] | SKIP <Object name(s)> | <Object name>[(<Version number>)] {<Object name>[(<Version number>)]}
Existing Object Types
| Type | Description |
|---|---|
| CC: |
If Cobol Copies must be exported or imported. |
| CF: |
If Cobol Forms must be exported or imported. |
| CI: |
If Cobol Includable Forms must be exported or imported. |
| CP: |
If Cobol Programs must be exported or imported. |
| CS: |
If Cobol Subprograms must be exported or imported. |
| EI: |
If External Interfaces must be exported or imported. |
| IN: |
If AMT relational database Indexes must be exported or imported. |
| SC: |
If Scripts must be exported or imported. |
| SP: |
If AMT relational database Stored Procedures must be exported or imported. |
| SQ: |
If sequences must be exported or imported. |
| TA: |
If AMT relational database Tables must be exported or imported. |
| VI: |
If AMT relational database Views must be exported or imported. |
Object Specifications
| Specification | Description |
|---|---|
| ALL |
Indicates that all objects of the concerned object type must be exported or imported. |
| SKIP <Object name(s)> |
Excludes the specified object(s) from the import; all other objects of the concerned object type are imported. |
| <Object name> |
Name of the object to be exported or imported. |
| (<Version number>) |
Version number that must be assigned to the imported object included in parenthesis. E.g. (3.1.4). Info Note: This option does not apply if the parameter file is used for exports. |
| Multiple objects of the same type can be specified by delimiting the object specifications by single spaces. All specifications of the same object type must be specified on a single line. |
Version numbering on import
To import objects under a new version number, the new version number must be specified between parentheses directly after the concerned object specification. The new version number must be a higher version than the previous one if its a main revision (1.2, 1.5, etc.). Also importing under a branch is allowed but the following rules apply:
- The main revision (first two numbers) must exist.
- The branch nodes may or may not exist (1.2.1, 1.3.2, etc.). When not, the import creates the branch node.
- The revision must be the highest revision in an existing branch.
- The previous revision in the branch may NOT be locked.
- When specifying an invalid revision the object is NOT loaded.
Example:
| When having revisions | |
| 1.4 | |
| 1.3 | |
| 1.2 | |
| After importing revision 1.3.1.4 | |
| 1.4 | |
| 1.3.1.4 <- Loaded revision | |
| 1.3.1 <- Automatically created branch node | |
| 1.3 | |
| 1.2 | |