Turn on debug, either for all facilities or for the specified facility.

Turn on process group timing debug.

Specify name of logical RDBMS.

Add SQL timing information to the log file. At level 1, all SQL commands (queries/updates) are printed. At higher levels, all SQL commands that take more than the specified number of milliseconds are printed. For example, -debugSqlTiming 500 prints all SQL commands that take more than 500 ms.

Sets the cursor_sharing option to FORCE for all RDBMS connection sessions managed by this instance of DBService.

Specifies the maximum number of concurrent RDBMS sessions (dbrdwr processes) to support.

Use process name other than DBService.

Writes queries to standard output. If no option is passed, DBService toggles the flag.

Specify name of database service. Default is ops.

Writes update statements to standard output. If no option is passed, DBService toggles the flag.

Activate the generation of alarms when DDService detects control zones without a controller or subscriber. This option takes an optional argument which is the rate (in seconds) at which to re-generate an alarm if the zone is still unsubscribed.

Create a new alarm for any of the following actions. Note that these options can be used in any combination and do not affect one another, although there is some occasional overlap. Also note that the alarmDigital SRS_RULES entry controls whether DDService creates alarms for changed non-status digitals. This is separate configuration and not included with the ALL option below.

Allow a full model reset to be performed, for testing and/or training. This should NEVER be specified on a production system.

This option specifies whether DDService should sort zones alphabetically by zone name before sending them to the authority tool for display.

Without this option, DDService sorts zones by the CONTROL_ZONES.sequence number. This column is populated implicitly by the nms‑parse‑zones script, and follows the ordering in the control_zones.dat file. Projects can choose to reset the sequence column to change the order of the zones if the so choose.

Activate automatic clearing of DDS alarms and purging of FLM and SCADA history. If this option is used with no other arguments then DDS alarms will be cleared hourly from the time DDService is initialized. If you supply an argument in the form "#:#:A" The first number is the amount in days. The second number is the time of day (0-23, 0 being 12:00a). The last item in the argument should either be an "A" or nothing. If you give it invalid arguments, then it reverts to clearing all DDS alarms daily (1:23:A).

example: 0:23

which will cause all DDSalarms to be cleared at 11:00p

example: 1:23

which will cause DDSalarms older than one (1) day to be cleared at 11:00p

example: 40:23

which will cause DDSalarms older than forty (40) days to be cleared at 11:00p

and so on.

If an A is last in the argument, all alarms will be cleared.

If an A is not supplied, only acknowledge alarms will be cleared.

Historical FLM and SCADA rows will be purged at the same time, as configured by the "RETAIN_HISTORY_RECORDS" ces_parameters entry. This defaults to purging rows that are over 4 weeks old.

Set the time out as the number of seconds for control zone transferring. If one user sends out a request and the other user doesn't response in the number of seconds, it will be time out. The default number is 300 seconds or 5 minutes. 

Connect to the DBService started with the -service <name> option. For example, if you started:

Then you would specify:

to connect to it.

Do not automatically remove the Instruct conditions when a requested SCADA control response is received. This is not recommended behavior.

Allows DDService to process delegated zones. Without any parameters, defaults to exclusive owner mode in each delegated zone, where only the user who created the zone may operate devices in it.

With -delegate ncg, allows all users with authority over the NCG to operate interior devices. With -delegate crew, prevents all users from operating devices in the zone while a crew is assigned. Once a crew has been released, authority falls to an authorized operator, either the one specific owner (if simply -delegate crew is specified), or to the group of authorized users (if -delegate ncg crew is used).

Condition classes to skip when populating the Look Ahead Conditions table.

This option will set the maximum number of study sessions allowed. Since each study session takes MTService and PFService memory to hold the Network solution, this number should be set to a point before the services become too large for the operating system. Defaults to 50 if not specified.

Do not generate alarms for SCADA events. Use this option to avoid duplication when the SCADA interface passes all alarms to DDService.

This option will override the wait period for a telemetered device when it has been opened/closed. The telemetered device is defined as having an entry in the digital_measurements table, but not in the controls table.

When manually operated, the digital measurement of attribute 0 remains the status reported via the SCADA interface.

Prevents removal of tags from devices in a grounded (or earthed) segment.

Use this option to enable web service based SCADA interfaces. These have to be asynchronous messages because they cannot subscribe to isis process groups.

Set the control zone management mode to subscription mode which allows multiple users to own a zone. The default mode without this option is exclusive mode which means any time any zone can only owned by one user.

Switch on summary objects - conditions can be then be mapped to more a second device for the purpose of summarizing conditions on  objects held on other maps.

The NCG to use for system alarms.

Check that device CLOSE operations will not connect two hot phases.

Enable control zone authorizing in DDService.

Connect to the DBService started with the -service <name> option. For example, if you started:

Then you would specify:

to connect to it.

Set grouping parameters for the passes name/value pairs. This configuration is uncommon. Available names:

Do not automatically calculate ERTs for jobs. Only allow users and/or interfaces to assign ERTs.

Do not broadcast outages. Only used when interfacing with external OMS interfaces.

Do not group outages. Only used when interfacing with external OMS interfaces.

Connect to the DBService started with the -service <name> option. For example, if you started:

Then you would specify:

to connect to it.

Allow devices with conditions to be deleted and reported. If not set, the build will abort when attempting to delete devices with conditions. Takes a space-separated list of condition names.

Allow devices which are off-nominal to be deleted and reported. If not set, the build will abort when attempting to delete devices with off-nominals.

Allow devices of the configured classes which are off-nominal to be deleted and reported. If not set, the build will abort when attempting to delete devices with off-nominals. Takes a space-separated list of device class names.

Specify destinations to be used for error logging.

string

A list of desired error logging destinations. Options:

D - database

E - standard error (MBService log file)

F - patch file (in $OPERATIONS_MODELS/errors/)

B - CMMS message broadcast

S - System log (syslog directory)

N - No destinations

The various destinations should be strung together: SED

When performing model builds, don't assign new generic nodes when the number of connections to a node changes.

Use the feeder_ncg table to identify a new NCG value if an alternate view with a new partition is promoted

Signifies that JMService is not being used in this system. Also used for model build environments, or for initial builds.

MBService is in an initial model build where all services are not required.

Generates preliminary maps after a patch is applied.

Generate a report of all changes made for the patch.

If this option is not on the command line, no report will be made. The report will be in readable form and found in file "data/reports/Patch#.report".

As the Model Build Service (MBS) updates the model and generates updated map files (.mad files), if -export is set, MBService will also generate export .mb files for external systems to pick up the latest model definition. These export files will be placed in the $OPERATIONS_MODELS/export directory and there will be a 1:1 relationship to the MBS generated .mad files.

If -export is set, a second option, -exportxml, is available to include an .xml formatted export file in the same location, $OPERATIONS_MODELS/export. An xml schema file for the .xml export is available in this location $NMS_BASE/product/sql/mb.sql.

Auto-populate the SORT_ID attributes of all switches in each feeder-based geographic partition.

That is, starting from the FID object, MBService will assign integers to each downstream switch, and populate the SORT_ID attribute with the switch ID and the parent switch’s ID, separated by the ‘‑’ sign.

For example, a breaker would be ‘00000‑00000,’ a downstream recloser would be ‘00001‑00000,’ and a fuse downstream of the recloser would be ‘00002‑00001,’ and a transformer downstream of the fuse would be ‘00003‑00002,’ etc.

The appropriate columns must be in the attribute tables, and the DEVICE_ATTRIBUTES must be configured correctly to save the SORT_ID attribute. The customer must also have feeder-based partitioning.

Connect to the DBService started with the -service <name> option. For example, if you started:

Then you would specify:

to connect to it.

This flag allows projects to propagate the GROUND color through feeder heads. Note that grounded and energized produces a FAULT color, whose behavior is undefined about feeder heads. Also note that this decreases MTService performance, as it now potentially needs to solve an entire island, instead of a single feeder.

Loop processing is a significant expense during topology processing. If loop colors are not necessary, this option is used to disable all loop processing.

Add any SND connected to a device to the list of downstream affected customers in Look Ahead.

Accepts a space-delimited list of transformer classes, which MTService will test against the nominal model. If any instance of the listed classes is found to be partially energized, MTService will print a log warning describing the problem, along with the alias into the log file.

MTService will then continue to operate under the assumption that the devices are incorrectly modeled and should only have the hot phases available. This prevents difficult situations within outage management where SNDs can never be reenergized after outages, due to modeling errors.

Note that this only executes on startup, not after model builds. That is, when a map is rebuilt, MTService must assume that it has been corrected, and cannot afford to resolve the nominal network and recheck for disconnected transformers.

This option should be removed as soon as the model has been cleaned, since it impairs MTService startup performance considerably.

Disable complex HV/LV network protector processing.

Cache aggregate definitions for performance in the Feeder Focus operation.

Builds an AliasCache of the specified devices.

ALIAS_MAPPING.DB_TYPE values to load.

Used to allow the system to start up before loading device alias information. For example, if the services take 8 minutes to launch, then a -delay 10 could be used to delay alias caching.

Specifies the "db_types" to ignore when caching aliases; db_types include DNO, OPS, DDB, and RTI_SP.

Cache object locations.

Creates an array of size (n) to store device aliases. This helps when the same alias is looked up repeatedly.

Do not query aliases for the specified class names.

Seconds for initialization retry (minimum 5 seconds).

Enable debugging of mru cache statistics.