Adds or updates scheduling objects to the database.


You must have add access to add a new scheduling object. If the object already exists in the database you must have:
  • modify access to the object if the object is not locked.
  • modify and unlock access to the object if the object is locked by another user.

To add security objects, you must have permission for the modify action on the object type file with attribute name=security.


{add | a} filename [;unlock]


Specifies the name of the text file that contains the object definitions. For event rules, filename specifies the name of the XML file containing the definitions of the event rules that you want to add (see Event rule definition for XML reference and see The composer editor for details about setting up an XML editor).
Indicates that the object definitions must be unlocked if locked by the same user in the same session. If you did not lock the object and you use the ;unlock option, when you issue the command you receive an error message and the object is not replaced.


The text file is validated at the client and, if correct, objects are inserted into the database on the master domain manager. Composer transforms object definitions into an XML definition used at the server; otherwise the command is interrupted and an error message is displayed. This does not apply to event rule definitions because they are provided directly in XML format.

With the add command, if an object already exists, you are asked whether or not to replace it. This behavior does not affect existing job definitions inside job streams, and the job definitions are automatically updated without prompting any message. You can use the option unlock to update existing objects you previously locked by using only one command. For all new objects inserted, the option is ignored. If you change the name of an object, it is interpreted by composer as a new object and will be inserted. A rename command is recommended in this case.

The add 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 add 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.


To add the jobs from the file myjobs, run the following command:
add myjobs
To add the job streams from the file mysked, run the following command:
a mysked
To add the workstations, workstation classes, and domains from the file cpus.src, run the following command:
a cpus.src
To add the user definitions from the file users_nt, run the following command:
lata users_nt
To add the event rule definitions you edited in a file named newrules.xml, run:
a newrules.xml

See also

From the Dynamic Workload Console you can perform the same tasks as described in:

the Dynamic Workload Console User's Guide.