NGL commands

NGL supports console commands to stop, start, or refresh the NGL agents for a specific NGL product instance identifier (PIID).

Table 1 lists the commands that are available for the NGL. In this table, the dbcssid value indicates the DBC subsystem ID under which the NGL is running, and the piid value indicates the NGL PIID.

Table 1. NGL commands

Command

Description

/dbcssid NGL,STOP,piid

Stops the NGL agent for the specified piid

/dbcssid NGL,START,piid

Starts the NGL agent for the specified piid

/dbcssid NGL,REFRESH,piid

Stops and then starts the NGL agent for the specified piid

/dbcssid NGL,DUMP,piid

Takes a dump of the NGL address space and any connected client address spaces

Use when BMC Support directs you to do so.

/dbcssid NGL,CMD,piid,LIST LOGSET {logset_name}

Lists all active logsets and provides status information such as logfile time span and record count information

logset_name is optional. If logset_name is omitted, all logsets are displayed.

/dbcssid NGL,CMD,piid,DISPLAY LOGSET logset_name

Displays the defined logset characteristics to NGL

logset_name is required.

Note

For DOM users, this information should match the output group definition in the optionset.

/dbcssid NGL,CMD,piid,STATUS LOGSET {logset_name}

Displays insert and retrieval statistics for a logset

logset_name is optional. If logset_name is omitted, all logsets are displayed.

Note

For information on the Data Collector STATUS command, see STATUS

/dbcssid NGL,CMD,piid,ARCHIVE LOGSET logset_name {logfile_name}

Use ARCHIVE with logfile_name to archive a logfile if NGLARCH has failed and the logfile requires another archive.

logset_name is required. logfile_name is optional. If logfile_name is included in the ARCHIVE command, the named logfile is archived.

Some products include options that you can use to configure NGL for use with that product. For additional information about using NGL with a particular product or solution, see your production documentation.