HCL Workload Automation, Version 9.4

update

Modifies the attribute settings of some specific scheduling object type that is defined in the database without using the modify or replace commands. You might update some attribute settings for the specific object type in the database without opening and modifying the object definition in a text editor or replace the object definition by using the new content that is saved in a text file.

Authorization

You must have the modify and display access to update object properties, otherwise composer is unable to update the object attributes.

Syntax

{update | up}
{[cpu={workstationame | workstationclassname}] |
[workstation | ws=workstationame] |
[workstationclass | wscl=workstationclassname];
[filter workstation_filter_criteria= selection [...]];
set [ignore= on | off]]}
[;noask]

Arguments

cpu

Updates workstations or workstation classes.

workstationame: The name of the workstation. Wildcard characters are permitted.
workstationclassname: The name of the workstation class. Wildcard characters are permitted.

Note: The command does not update domains.

workstation | ws

If no argument follows, update all workstation definitions.

If argument workstationname follows, update the workstationname workstation. Wildcard characters are permitted.

workstationclass | wscl

If no argument follows, modify all workstation class definitions.

If argument workstationclassname follows, update the workstationclassname workstation class. Wildcard characters are permitted.

filter

The workstation scheduling object filter criteria to use.

For more information about workstation scheduling object filtering criteria, see Table 1.

set

The set criteria is mandatory and introduces the list of the object attribute settings to modify.

ignore=on | off

The ignore workstation, cpu, and workstation class attribute. If you specify on, the workstation or workstation class is set to ignore in the database and the workstation or all workstations which belong to a workstation class are not included in the next production plan. If you specify off, the workstation or all workstations belong to a workstation class are included in the next production plan.

Comments

Note: The scheduling object definition changes are applied only in the database. To have the changes in the plan, you must wait for next production plan (Final job stream running) or you might run JnextPlan command.

Examples

If you want that all workstations with names starting with AB are not included in the next production plan and you need to update the ignore attribute to ON on their definitions, run the following command:

update ws=AB@;set ignore=on

If you want that all your workstations in the network are included in the next production plan and you need to update the ignore attribute to OFF on all workstations definition in your database, without replying to the composer prompting confirmation, run the following command:

update ws;set ignore=off; noask

If you want that all workstations which belong to New York workstation class are not included in the next production plan and you need to update the ignore attribute to ON on their definitions, run the following command:

update wscl=NewYork;set ignore=on

If you want that all your workstations in the domain DOMWIN1 are included in the next production plan and you need to update the ignore attribute to OFF on all workstations definition in your database, without replying to the composer prompting confirmation, run the following command:

update ws;filter domain=DOMWIN1; set ignore=off; noask

If you want that all your workstations in the MAIN_TABLE vartable are included in the next production plan, and you need to update the ignore attribute to ON on all workstations definition in your database, run the following command:

update ws=@; filter vartable=MAIN_TABLE domain=MASTER@; set ignore=on