replace
Replaces scheduling object definitions in the database.
Authorization
- modify access to the object if the object is not locked.
- modify and unlock accesses to the object if you want to use the ;unlock option against objects locked by other users.
To replace security objects, you must have permission for the modify action on the object type file with attribute name=security.
Syntax
{replace | rep} filename [;unlock]
Arguments
- filename
- Specifies the name of a file containing the object definitions to replace. The file can contain all types of scheduling objects definition.
- unlock
- Updates existing objects previously locked and unlocks them. An error is displayed if the objects are not previously locked. For all new objects inserted, this option, if specified, is ignored.
Comments
The replace command is similar to the add command, except that there is no confirmation prompt to replace existing objects. For more information, refer to add.
The replace command checks for loop dependencies inside job streams. For example, if job1 follows job2, and job2 follows job1 there is a loop dependency. When a loop dependency inside a job stream is found, an error is displayed.
The replace command does not check for loop dependencies between job streams because, depending on the complexity of the scheduling activities, this check might take too long. If you need to check for loop dependencies between job streams, use the datamigrate utility.
- Extract the object definitions from the database on an HCL Workload Automation instance into a flat file using the composer extract command line.
- Import the file into the database on the master domain manager with the datamigrate utility.
For more information about the datamigrate utility, see datamigrate.
Examples
replace myjobs
rep myres
- You write the entire definitions in an XML file you name 2Q07rules.xml.
- You run:
rep 2Q07rules.xml