modify

You can use the command option to modify existing scheduling items in the database.

Overview

The command option performs similar to the new command, when you want to modify an item that is not available in the database. When you run the command, the selected item definition is copied and opened in a temporary file. You can then edit the file and replace the existing item.

Syntax and command line options

You must provide at least one scheduling item with the command to perform the action.

ocli model modify|m Scheduling item

Important: If you modify an item by changing its key, a new item is created without modifying the existing one. You can use the rename command to modify the item.

For the list of scheduling parameters that you can use and the format that needs to be followed, see the tables below.

Table 1. Scheduling items
Scheduling items	Description
`calendars \| calendar \| cal [folder/]calname`	You can specify the `[folder/]calname` that you want to modify. If you do not specify a `[folder/]calname`, all the calendar definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`domain \| dom domainname`	You can specify the `domainname` that you want to modify. If you do not specify a `domainname`, all the domain definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`folder \| fol foldername`	You can specify the name of the folder. If you do not provide the `foldername`, all the folder definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`jobs \| jobdefinition \| jd [[folder/]workstationame#][folder/]jobname`	If you provide a specific `jobname` only that particular job definition is displayed for editing and if not, all the job definitions are displayed. You can provide `[folder/]workstationame#]` and the folder in which the job is defined to make the selection more specific. Wildcard characters are permitted.
`sched \| jobstream \| js [[folder/]workstationame#][folder/]jstreamname[valid from date\|valid to date \|valid in date date][;full]]`	If you provide a specific `jstreamname` only that particular job stream definition is displayed for editing and if not, all the job stream definitions are displayed. You can provide `[folder/]workstationame#]` and the folder in which the job stream is defined to make the selection more specific. Wildcard characters are permitted. You can also add the options below to provide more details of the job stream. `Valid from date`: You can specify a date which will restrict the selection of job streams, that have a `valid from` date equal to the value specified. The format is `mm/dd/yyyy`. `Valid to date`: You can specify a date which will restrict the selection of job streams, that have a `valid to` date equal to the value specified. The format is `mm/dd/yyyy`. `valid in date date`: Specify the time frame at which the job is run. You can specify one of the dates as `@`. The format is `mm/dd/yyyy-mm/dd/yyyy`. full: If you add the option, all the job definitions in the job stream are displayed for editing.
`prompt \| pr [folder/]promptname`	You can specify the `[folder/]promptname` that you want to modify. If you do not specify a `[folder/]promptname`, all the prompt definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`resource \| re \| reso [folder/]resourcename`	You can specify the `[folder/]resourcename` that you want to modify. You can provide the `[folder/]workstationame#]` and the folder in which the resource is defined to make the selection more specific. If you do not specify a `[folder/]resourcename`, all the resource definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`runcyclegroup \| rcg [folder/]rcgname]`	You can specify the `[folder/]rcgname]` that you want to modify. If you do not specify a `[folder/]rcgname]`, all the run cycle group definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`users \| user [[folder/]workstationame#]username [;password]`	You can specify the `[[folder/]workstationame#]username [;password]` that you want to modify. Wildcard characters are permitted.
`parms \| parm \| variable \| vb [[folder/]tablename.]variablename`	You can specify the `[[folder/]tablename.]variablename` that you want to modify. Wildcard characters are permitted.
`vartable \| vt [folder/]tablename`	You can specify the `[folder/]tablename` that you want to modify. Wildcard characters are permitted.
`workstation \| ws \| cpu [folder/]workstationame]`	You can specify the name of the workstation that you want to update. Optionally, you can provide the folder in which the items are located. If you do not specify the `workstationame`, all the workstation definitions in the database are displayed in a file for editing. Wildcard characters are permitted.
`workstationclass \| wsc [folder/]workstationclassname]`	You can specify the `[folder/]workstationclassname]` that you want to modify. If you do not specify a `[folder/]workstationclassname]`, all the workstation class definitions in the database are displayed in a file for editing. Wildcard characters are permitted.

Examples

Run the following command to edit all the job definitions:
```
ocli model modify job @
```
Run the following command to modify the job stream FINAL located at folder TEAMS that is launched on workstation WS1:
```
ocli model modify sched WS1#TEAMS/FINAL
```