QPWFSERVSO - what is it's purpose?

[Mr. K.V.B.L.]

On one of our systems we have 359 of these jobs running. I'm not sure if that's normal or not.

1. What system request starts them?
2. Do they go away on their own if they're no longer needed?
3. Is there a code problem that is not closing resources properly and thus making the job hang around longer than it needs to?

We also have 184 QSQSRVR jobs in the system. Don't know if I should be concerned about those.

[jse...@yahoo.co.nz]

On Thursday, June 12, 2014 2:33:05 AM UTC+12, Mr. K.V.B.L. wrote:
> On one of our systems we have 359 of these jobs running. I'm not sure if that's normal or not.
>
> 1. What system request starts them?

These are started by a request to the file server (such as someone connecting via netserver or using i access and navigating into the File Systems link).

> 2. Do they go away on their own if they're no longer needed?

They are prestart jobs so the system will maintain them as per the SBS definition.

> 3. Is there a code problem that is not closing resources properly and thus making the job hang around longer than it needs to?

Would think this unlikely but if you have an exit program associated with them, it's possible I guess, though I would think a problem with an exit would cause the connection to hang.

> We also have 184 QSQSRVR jobs in the system. Don't know if I should be concerned about those.

The knowledge centre indicates these are SQL server related jobs.