1-2-3 Three basic subsystems for running server jobs
Page 1 of 1
1-2-3 Three basic subsystems for running server jobs
Three basic subsystems for running server jobs
1. QSYSWRK
This subsystem is for system work (not work done on behalf of a specific user) and those servers that have a limited number of server jobs that will be active at any point in time. It's also used for daemon or listening jobs that pass their work off to a server job that runs in a different subsystem. We shouldn't use this subsystem for custom-server jobs.
2. QUSRWRK
This subsystem is for user work (work done on behalf of a specific user) and intended to be used when there can potentially be a large number of user jobs. The jobs that run in this subsystem should also allow subsystem configuration by the IBM i system administrator to optionally run these jobs in user-defined subsystems.
3. QSERVER
This subsystem is for file-serving work only. The daemon jobs for the database server, file server and NetServer run in this subsystem. Some of the prestart server jobs run in this subsystem by default also, but they can be configured to run in a different subsystem. We shouldn't use this subsystem for our custom-server jobs.
1. QSYSWRK
This subsystem is for system work (not work done on behalf of a specific user) and those servers that have a limited number of server jobs that will be active at any point in time. It's also used for daemon or listening jobs that pass their work off to a server job that runs in a different subsystem. We shouldn't use this subsystem for custom-server jobs.
2. QUSRWRK
This subsystem is for user work (work done on behalf of a specific user) and intended to be used when there can potentially be a large number of user jobs. The jobs that run in this subsystem should also allow subsystem configuration by the IBM i system administrator to optionally run these jobs in user-defined subsystems.
3. QSERVER
This subsystem is for file-serving work only. The daemon jobs for the database server, file server and NetServer run in this subsystem. Some of the prestart server jobs run in this subsystem by default also, but they can be configured to run in a different subsystem. We shouldn't use this subsystem for our custom-server jobs.
Similar topics
» How to hide the running jobs( submitted ones)
» Access AS/400 when QINTER and other Interactive subsystems are down
» JOBQ attached to multiple subsystems.
» Handling Jobs
» find jobs held
» Access AS/400 when QINTER and other Interactive subsystems are down
» JOBQ attached to multiple subsystems.
» Handling Jobs
» find jobs held
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|