lock

You can use the command option to lock access to a scheduling item definition.

Overview

Syntax and command line options

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

ocli model lock|lo Scheduling or Security item

For the list of scheduling or security 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 name of the calendar and optionally, the folder in which the calendar is defined. If you do not specify the `calname`, all the calendar definitions in the database are locked.
`folder \| fol foldername`	You must specify the name of the folder that you want to lock. Wildcard characters are permitted.
`jobs \| jobdefinition \| jd [[folder/]workstationame#][folder/]jobname`	If you provide a specific `jobname` only that particular job definition is locked and if not, all the job definitions are locked. 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 locked and if not, all the job stream definitions are locked. 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.
`eso \| eventsource \| so [folder/]eventsourcename`	You can specify the name of the event source and optionally, the folder in which the event source is defined. If you do not specify the `eventsourcename`, all the event source definitions are locked. Wildcard characters are permitted.
`parms \| parm \| variable \| vb [[folder/]tablename.]variablename`	If you specify the `variablename` only, all the variable definitions in that table are locked. If you do not provide the `[[folder/]tablename.]variablename`, all the global variable definitions in the default variable table are locked. Wildcard characters are permitted on both `[folder/]tablename` and `variablename`.
`users \| user [[folder/]workstationame#]username [;password]`	If you do not provide any specific `username`, all the usernames in the database are locked. You can provide `[folder/]workstationame#]` and the folder in which the user is defined, to make the selection more specific. Wildcard characters are permitted.
`vartable \| vt [folder/]tablename`	You can specify the name of the variable table and optionally, you can provide the folder in which the variable table is defined. If you do not specify the `tablename`, all the variable table definitions are locked. Wildcard characters are permitted.
`workstation \| ws \| cpu [folder/]workstationame]`	You can specify the name of the workstation that you want to lock. Optionally, you can provide the folder in which the items are located. Wildcard characters are permitted.

Table 2. Security items
Security items	Description
`accesscontrollist \| acl foldername\|F+foldername\|A+ADMIN`	If you specify the `foldername\|F+foldername\|A+ADMIN`, the access control list definition for that particular folder is locked and if not, the access control list definitions for all the folders are locked. Wildcard characters are permitted. `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`	If you specify the `securityrolename`, the security role definition for that particular security role is locked and if not, the security role definitions for all the security roles are locked. Wildcard characters are permitted.

Examples

Run the following command to lock the calendar weekdays:
```
ocli model lock calendar=weekdays
```
Run the following command to lock the folder delhi:
```
ocli model lock folder /delhi
```