commands against a set of objects that you cannot identify through commands such as ExecuteQuery, you can manually create an input file.
Use the following rules and guidelines when you create a persistent input file:
Enter “none” for the encoded ID. The
commands get the object information from the other arguments in the records.
For source objects, enter the object name as <DBD_name>.<source_name>.
For objects, such as mappings, that do not have a sub_type, enter “none” as object_subtype, or leave it blank. For more information about valid transformations and task types, see
Listing Object Types.
For versioned repositories, enter the version number of the object you want, or enter “LATEST” to use the latest version of the object.
For non-versioned repositories, leave the version_number argument blank.
For object types, such as targets, that are not reusable or non-reusable, drop the argument.
You cannot include non-reusable objects. You can specify the reusable parent of the non-reusable object.
For example, you want to list the object dependencies for a non-reusable Filter transformation. You can specify the mapping that is the parent object of the transformation:
The mapping m_seqgen_map is the reusable parent of the Filter transformation. The command runs successfully when you specify the reusable parent.
When you use a manually created persistent input file, the Repository Service returns a message indicating that the ID is not valid. This is an informational message. The Repository Service recognizes that this is a manually created input file and can process the command with “none” as the ID.