When you submit a job from the SAS^® Grid Manager Client Utility (SASGSUB) with the WATCHOUTPUT option, SAS Workload Orchestrator host machines that run the job might experience delays or have an INACTIVE status in the web interface of SAS Workload Orchestrator.

This issue occurs because the following actions take place:

1. The SAS Grid Manager STDIO Redirector that provides the standard out (stdout) and standard error (stderr) to the grid client utility also sends the output to its own stdout.
2. The grid client utility script captures all stdout/stderr from the process that it launches in its debug file and then outputs that file at the end of the script to be captured by the grid provider.
3. SAS Workload Orchestrator captures all stdout/stderr from the process that it launches.

When the WATCHOUTPUT option is used for jobs that run for a very long time, a large amount of log lines may be generated and captured by SAS Workload Orchestrator. SAS Workload Orchestrator includes all of that stdout information whenever it sends job status information back to the master node. Creating the JSON for all of the stdout lines can take a long time if there are a lot of stdout lines. The thread that creates the job information is the same thread that creates the host status information. Therefore, long delays between host status updates can cause a host to be determined to be inactive.

Click the Hot Fix tab in this note to access the hot fix for this issue.

The hot fix enables you to choose whether the data is sent both to stdout and to the grid client utility.

Operating System and Release Information

A fix for this issue for SAS Workload Orchestrator 9.46 is available at: