ReviewerConsole actions

The actions allow you to analyze and run Reviewer batch jobs on a dataset. You can also create or erase Reviewer sessions in a workspace, as needed, or list the checks that are included in a batch job.

Parameter	Description	Configuration notes
/create	Creates or converts the specified workspace and/or session.	You can specify /erase in conjunction with /create to erase all existing session information before creating the new session. If the workspace already contains the Reviewer administration tables, /create is ignored and the session is created. To overwrite existing tables, include the /erase option in conjunction with /create, for instance, ReviewerConsole.exe /wks:MyWks.mdb /create /erase. If a session is specified with the /session: parameter, it will be created in addition to the Reviewer workspace tables.
/delete	Deletes a specific session or group of sessions.	The /sessionid parameter can take one of three formats: A single session ID (for example, /sessionid:6 ) A comma-delimited list (for example, /sessionid:1,2,3,10 ) A range of sessions (for example, /sessionid:1-30 ) To delete a session by name, include the name of the session; for example, ReviewerConsole.exe /delete /wks:MyWorkspace.mdb /session:Session 1. To delete session(s) with a specific session ID, specify the session ID; for example, ReviewerConsole.exe /delete /wks:MyWorkspace.mdb /sessionid:10.
/erase	Erases all Reviewer session information from the specified workspace.	It is used in conjunction with the /wks: parameter. You cannot erase an individual session. If a /session: parameter is specified, it is ignored. The /session: parameter only applies if the /create option is also specified.
/exec	Executes the specified batch job or batch jobs. The following options can also be used with /exec: /changedonly—Runs the batch job checks on changed features only. This option affects checks that use a versioned geodatabase and are run on a version other than default. /nodefault—Skips execution of session default checks when the batch jobs are run.	If multiple batch jobs are specified, the checks from each are merged internally into a single job that is executed. Multiple batch jobs are not executed individually. To specify multiple batch jobs, provide a comma-separated list after the /rbj: option; for instance, /rbj:job1.rbj,job2.rbj,job3.rbj. A workspace and session must be specified. /exec cannot be specified in conjunction with any other action, such as /list, /validate, or /merge.
/list	Lists the Reviewer batch job checks or Reviewer session information from a workspace. When listing Reviewer workspace information, a list of the sessions and their names is provided. When listing batch jobs, the listing includes information on the batch job (who created it, number of checks, and so forth) and information on each individual check. Checks are listed group by group. If multiple batch jobs are specified to list, the listing is grouped by batch job.	To specify multiple batch jobs, provide a comma-separated list after the /rbj: option, for instance, /rbj:job1.rbj,job2.rbj,job3.rbj. If a workspace and session are provided, as well as batch jobs, the workspace and session are ignored. To list workspace session information, do not specify an /rbj: parameter, for instance, ReviewerConsole.exe /wks:MyWorkspace.sde /list. Multiple workspaces cannot be specified. /list cannot be specified in conjunction with any other action (for instance, /exec, /validate, /merge).
/merge	Merges the batch job content into a single batch job specified as output_batch_job_file_name.	A minimum of two batch jobs must be provided. If the output file specified with /merge exists, it will be overwritten. To specify multiple batch jobs, provide a comma-separated list after the /rbj: option; for instance, /rbj:job1.rbj,job2.rbj,job3.rbj. If a workspace and session are provided, they are ignored. /merge cannot be specified in conjunction with any other action, such as /exec, /validate, or /list.
/validate	Validates the Reviewer batch job checks in the list of batch jobs or the service job. The output provides a summary validation report that applies to all jobs specified on the command line along with individual stats for each job.	To specify multiple batch jobs, provide a comma-separated list after the /rbj: option; for instance, /rbj:job1.rbj,job2.rbj,job3.rbj. A workspace and session must be provided. /validate cannot be specified in conjunction with any other action, such as /exec, /list, or /merge.

Reviewer service console actions

The /changedonly and /nodefault flags

The following flags can be used in conjunction with /exec to further control the way batch jobs are run on a workspace.

• /changedonly—Can be used when running batch jobs against versioned geodatabases and when running the checks against a version other than default.

  The /changedonly flag instructs the underlying Reviewer Engine to execute the batch job checks on changed (edited) features only. It corresponds to the Changed Features Only check box on the Reviewer Batch Validate dialog box. Internally, the Reviewer Engine constructs a difference cursor to identify the changed features and executes the checks against the features returned by the difference cursor. If the /changedonly option is specified for checks that use a workspace that is not versioned or is not a version other than default, it is ignored. The workspaces being referred to, with regard to the /changedonly option, are the workspaces that are specified in the batch job check data source parameters, not the Reviewer workspace specified via the /wks: option. The use of a versioned workspace for the /wks: parameter has no bearing on the behavior of the /changedonly flag.

• /nodefault

  When the checks for one or more batch jobs are prepared for execution against the Reviewer Engine, any default checks specified for the active session are also constructed. A default check is constructed for each feature dataset referenced in any check of the batch jobs. This behavior is identical to the construction of the Default node in the Reviewer Batch Validate dialog box after clicking Validate All. Specifying the /nodefault option skips creation of any default checks specified in the active session. To change which default checks, if any, are executed in conjunction with batch jobs, open the Reviewer Session Manager dialog box in ArcMap and click the Default Checks tab. Check the default checks to be executed for that particular session.