Manage DFWFPROC Jobs :: DataFlux® Data Management Server 2.7: Administrator's Guide

Overview

The DFWFPROC process runs real-time process services, batch jobs, and profile jobs. Batch and profile jobs are handled independently of process services.

For batch and profile jobs, the DataFlux Data Management Server starts a new DFWFPROC process and assigns the job to that process. Log entries record job status: start, running, finished successfully, or terminated due to error. This information is displayed in the Monitor folder in DataFlux Data Management Studio.

You can also configure the DataFlux Data Management Server to collect job run statistics for batch and profile jobs. The statistics are parsed from job run log files by the SAS Job Monitor (in SAS Environment Manager.) The Job Monitor can examine log entries that are collected during job runs. To learn more about using the SAS Job Monitor, see Collect Job Status Information with the SAS Job Monitor.

The default directories for process services, batch jobs, and profile jobs are located in install-path/var.

Limit the Number of Jobs and Queue Job Run Requests

To manage server performance, you can use DMSERVER/JOBS_MAX_NUM to control the number of jobs (batch and profile) that can run simultaneously. When the maximum number of active jobs is reached, you can choose to refuse additional job run requests, or to enqueue job run requests using DMSERVER/JOBS_QUEUE. Using the queue, the server honors all job run requests in the order in which they were received, as the number of active jobs drops below the specified limit. By default, the server accepts all job requests and does not use a queue.

In DataFlux Data Management Studio, queued job run requests are displayed in the job’s Run History tab. To display the Run History tab, you expand the DataFlux Data Management Servers riser, expand the server’s entry in the tree list, and click the job. In the Run History tab, the Status column displays Queued. When you right-click a queued job in the Run History tab, the only action that does not generate an error message is Stop. Stopping the job removes the job run request from the queue.

Similarly, when your SOAP clients submit SOAP commands for enqueued jobs, SOAP Fault messages are returned for all commands except those that stop the job.

Reference for DFWFPROC Configuration Options

Use the following configuration options to manage your DFWSVC processes. These options are specified in install-path/etc/dmserver.cfg.

Configuration Option	Description
DMSERVER/JOBS_MAX_NUM	Specifies the maximum number of batch jobs and profile jobs that are allowed to run simultaneously. The default value is 10. If a new job request exceeds the limit, and if DMSERVER/JOBS=YES, then the job run request is placed in a queue. If DMSERVER/JOBS=NO, then an error message is displayed and the new job is not executed.
DMSERVER/JOBS_QUEUE	Allows or denies the server the ability to queue batch job run requests when the number of running jobs exceeds the value of the DMSERVER/JOBS_MAX_NUM option. A value of YES queues job run requests and sends clients a success response, as if the job had begun to run. As running jobs finish or are canceled, queued jobs run and the queue is cleared. This option does not apply to profile jobs. The default value is NO.
DMSERVER/JOBS_ROOT_PATH	Specifies the location of the root directory for the job and service subdirectories. The default object root directory is `install-path\var`. The subdirectories for jobs and services are: `data services`, `process services`, and `batch jobs`.