extract

You can use the command option to create a text file by copying the item definitions from the database.

Overview

You can configure the command line syntax with different parameters to create specific item definitions. You can either use create or extract to copy the item definitions. You must have display access to the items being copied and modify access, if you want to use the ;lock keyword.

Syntax and command line options

You must provide at least one scheduling item and the filename with the command to perform the action. The ;lock parameter is optional.

ocli model create | cr | extract | ext filename from Scheduling item [;lock]

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

Scheduling items

Table 1. Scheduling items
Scheduling items	Description
`folder \| fol foldername`	You can specify the name of the folder. If you do not provide the `foldername`, all the folder definitions are copied into the file. Wildcard characters are permitted.
`jobs \| jobdefinition \| jd [[folder/]workstationame#][folder/]jobname`	If you provide a specific `jobname` only that particular job definition is copied and if not, all the job definitions are copied into the file. 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 copied and if not, all the job stream definitions are copied into the file. 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.
`workstation \| ws \| cpu [folder/]workstationame]`	You can specify the name of the workstation or workstation class or domain and optionally, you can provide the folder in which these items are located. Wildcard characters are permitted.

;lock

You can use the option to lock the selected items. If the selected items are locked by any other user, you cannot copy the definitions into the file.

Examples

Run the following command to create the file store with all job streams defined in the database:
```
ocli model cr store from jobstream=@
```
Run the following command to create the file mainvid.txt with the definition of user rorshar of workstation serv2356, including the encrypted password:
```
ocli model extract c:\mainvid.txt from user=serv2356#rorshar;password
```
The contents of file mainvid.txt will be:
```
USERNAME rorshar
  PASSWORD "ENCRYPT:EIu7PP+gvS8="
END
```