Start CERTMON from TACL using the installed program file. Guardian RUN options select the process name, primary CPU and asynchronous execution. CERTMON options follow the closing slash:
RUN <install-subvolume>.CERTMON / NAME $ACMON, NOWAIT, CPU 0 / --datastore <datastore-subvolume> --backupcpu 1 --log <log-file>
Service options
|
Option |
Meaning and constraints |
|---|---|
|
|
Required datastore location. |
|
|
Optional decimal backup CPU. It must be in the configured range and differ from the primary CPU. Omission starts without a configured backup. |
|
|
Optional signed license location. Omission loads LICAC in the program subvolume. |
|
|
Process-log configuration. Default |
|
|
Optional positive polling interval for a logging configuration file. Requires |
Option names are case-insensitive. Single-value options accept either --name value or --name=value. A multi-field inline log configuration uses space-separated values after --log; when using --log=<value>, supply the configuration as one value. Duplicate options, unsupported options, missing required values and invalid CPUs or locations cause startup failure.
Start, inspect and stop
Follow Create the datastore and start CERTMON for complete procedures. Connect with CERTCOM and inspect STATUS MONITOR, DETAIL, STATUS PROCESS * and STATUS SCHEDULER, DETAIL.
STOP MONITOR, DRAIN allows accepted work to finish; DRAIN is the default. STOP MONITOR, NOW requests immediate shutdown. Follow the maintenance plan and inspect active work before either operation. Restart with the approved RUN command after shutdown completes.
Startup diagnostics
Startup errors return a nonzero completion code and an explanatory message. Check the datastore schema, license eligibility, process/CPU selection, log destination and process log. Look up logged codes in the Event Message Reference. CERTCOM's command diagnostics use a separate catalog.
Scheduler configuration is stored in the datastore and managed through CERTCOM; it is separate from RUN options.