HP Integrity NonStop H-Series Guía de usuario descargar pdf (Pagina 343)

HP NonStop Shadowbase Command Definitions

SOLV Manager (File Chaser) Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

334

 STARTED: The SOLV Manager was started via the

START command, but has not received the RUN

command yet.

 UNKNOWN: The SOLV Manager did not respond

within AUDMON’s timeout limit and AUDMON could not

determine its current state. Check the EMS log for

messages with more information on the state of the

SOLV Manager.

4. The next lines contain information about the SOLV process running

under SOLVMGR

 SOLV – the process name identifying the specific SOLV started

by SOVMGR and its state. The states can be the same as

those for SOLVMGR above.

 Additional information about the SOLV process.

 LOAD FILE: The name of the current source file that

SOLV is currently processing.

 NEXT LOAD FILE: If available is the name of the

next files that SOLV will process once the current file has

been completely loaded.

 CONSUMER: This is the name of the HP

Shadowbase Consumer that is receiving the source file

events from SOLV

 MARKER PREFIX: Is the prefix of the files used to

maintain SOLV restart information for active loads and

historical information about completed loads. There are

three marker files that are created by a consumer and

used by SOLV. They are named using the prefix append

with the letters A, U, and H. The audited (A) file contains

restart data for audited files and tables. The unaudited

(U) contains restart data for unaudited files and tables.

The history (H) file contains archived results for

completed loads.

STOP SOLVMGR Command

The STOP SOLVMGR command stops a SOLV Manager. The syntax is:

STOP { [ SOLVMGR ] [<audmon_name>.]<solvmgr_name> }

{ [ SOLVMGR ] [<audmon_name>.]* }

[!]

audmon_name

1 2 ... 338 339 340 341 342 343 344 345 346

Sin comentarios

HP Integrity NonStop H-Series Guía de usuario Pagina 343