Accepted Solutions
When using Prognosis Threshold or Command functions to run a command (eg, a shell command, a batch file or a script) on the target system (either local Windows server, or remote Nonstop/Unix server),
if the command fails to run, the PrognosisCommandLog(CMDLOG) and PrognosisCommandOutput (AUTOOUT) records can be used to troubleshoot the problem.
Create a display document with these two records and launch it on the target server where the command is to be run, then start the Threshold or the Command document on the target server, or on the Management server if the Threshold or Command are designed to run locally. The display with the CMDLOG and AUTOOUT records will show the command details and its execution result, from ths output it is easy to spot the cause of the failure, eg login denied, file not found, parameter incorrect etc.
When using Prognosis Threshold or Command functions to run a command (eg, a shell command, a batch file or a script) on the target system (either local Windows server, or remote Nonstop/Unix server),
if the command fails to run, the PrognosisCommandLog(CMDLOG) and PrognosisCommandOutput (AUTOOUT) records can be used to troubleshoot the problem.
Create a display document with these two records and launch it on the target server where the command is to be run, then start the Threshold or the Command document on the target server, or on the Management server if the Threshold or Command are designed to run locally. The display with the CMDLOG and AUTOOUT records will show the command details and its execution result, from ths output it is easy to spot the cause of the failure, eg login denied, file not found, parameter incorrect etc.
