rename

You can use the rename command to rename a scheduling or security item in the database.

Overview

Before you rename an item, make sure no other item with the same name exists in the database. You can use the rename command to move the item to a specified folder at the same time. Specify the folder path before the new_item_identifier (example: /folder path/new_item_identifier). You must have delete and add access to the item to perform the action. When you rename a variable, the variable table that contains the variable is locked and no other user can run commands to lock the variable or the table.

Syntax and command line options

Before you run the command, you must give the name of the item that you want to modify and a new name. The ;preview parameter is optional.
ocli model rename | rn Scheduling or security item =/old_item_identifier//new_item_identifier/ [;preview]
where,
  • old_item_identifier is the name of the scheduling or security item.
  • new_item_identifier is the name for the selected item to be updated.
For the list of scheduling or security items that you can use and the required format, see the following table.
Table 1. Scheduling items
Scheduling items Description
calendars | calendar | cal [folder/]calname You can specify the name of the calendar to update. Optionally, you can specify the folder that contains the calendar definition.
folder | fol foldername You can specify the name of the folder to update.
jobs | jobdefinition | jd [[folder/]workstationame#][folder/]jobname You can specify the jobname to update. You can provide the [folder/]workstationame#] path and the folder that contains the job definition to make the selection more specific.
sched | jobstream | js [[folder/]workstationame#][folder/]jstreamname You can specify the jstreamname job stream to update. You can provide the [folder/]workstationame#] path and the folder that contains job stream definition to make the selection more specific.
eso | eventsource | so [folder/]eventsourcename You can specify the name of the event source to update. Optionally, the folder in which the event source is defined. Wildcard characters are permitted.
parms | parm | variable | vb [folder/]tablename.variablename You can specify the variablename value and the table that contains the definition. You can also provide the path to the folder in that contains the variable definition, to make the selection more specific.
users | user [[folder/]workstationame#]username You can specify the username to update.
vartable | vt [folder/]tablename You can specify the variablename variable and the table that contains the definition.
workstation | ws | cpu [folder/]workstationame You can specify the name of the workstation to unlock. Optionally, you can specify the path of the folder that contains the required items. Wildcard characters are permitted.
Table 2. Security items
Security items Description
accesscontrollist | acl foldername|F+foldername|A+ADMIN You can specify the name of the security folder to update.

foldername|F+foldername: You can specify the option if you want to filter out the lists that are associated with a folder. The security roles are valid, only for the items available in the folder.

A+ADMIN: You can specify this option, if you want to filter out the lists that allows specific permissions on API keys (that are not defined in folders) and on agent registration action.
securityrole | srol securityrolename You can specify the name of the security role to update.
;preview
If you specify this optional parameter, the results are displayed without the name changes. You can use this option to check on the impact of commands on items when you plan to rename multiple items.

Example

  1. Run the following command to rename the WRNACC variable which is defined in the TEST1 table to RGTACC.
    ocli model rename parm=/WRNACC.TEST1/ /RGTACC/