Manage the DFWFPROC Process

The DFWFPROC process runs real-time process services, batch jobs, and profile jobs. Process services are handled independently of batch and profile jobs, by a pooler. The DataFlux Data Management Server requests a new process from the pooler. The server then sends the process the service name and input parameters so that the process can load and run the service.

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.

To manage server performance, you can use DMSERVER/MAX_JOB_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.

You can unload idle DFWFPROC processes for real-time process services, batch jobs, and profile jobs using the SOAP command UnloadProcesses, as described in Apply SOAP Commands and WSDL Options. To unload processes manually, follow these steps:

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