This topic describes the jobs used by an application server and how you can monitor jobs by using iSeries command language (CL) commands.
Each application server instance consists of one or more jobs. These jobs run in the QASE51 subsystem. The job name is the first 10 characters of the application server name. If the first 10 characters do not provide a valid iSeries job name, the application server runtime creates a valid job name. If the runtime cannot create a valid job name for the application server, the application server will not start.
The application server provides the runtime environment for server-side Java components. The application server plug-in interfaces with the Web server to handle client requests for server-side resources and route them to their application server for processing.
If using the IBM Developer Kit for Java JDBC driver for database access, your instance uses one or more QSQSRVR jobs that run in the QSYSWRK subsystem. To determine what QSQSRVR job your application server job is using, view the server job log. For each JDBC connection obtained, the message SQL7908 with message text similar to the following:
Job 163707/QUSER/QSQSRVR used for SQL server mode processing.
If you are using the IBM Toolbox for Java JDBC driver for database access, your instance uses one or more QZDASOINIT jobs that run in subsystem QUSRWRK.
Depending on which Web server you are using to serve Web resources, your instance uses jobs from the Web server instance:
IBM HTTP Server (powered by Apache)
Each HTTP Server (powered by Apache) instance consists of two or more
jobs that run in the QHTTPSVR subsystem. The name of each job is
the same as the name of the HTTP Server instance. The application
server plug-in code runs in the second job listed for HTTP Server
(powered by Apache) instance.
OS/400 command language (CL) commands for monitoring
Use iSeries CL commands to monitor jobs that run in your application server environment. You can view the job logs, display message details, and view spooled files associated with the jobs. The job logs and associated spooled files for the jobs can contain valuable information for determining the root of a problem.
This table lists some iSeries commands that you can use to monitor application server jobs:
Task | iSeries command and description |
---|---|
Work with active application server jobs | For application server jobs that run in the QASE51 subsystem: WRKACTJOB SBS(QASE51) |
Work with all jobs with a specific name | This command lists all jobs, active or not, named job_name. The jobs are listed by date, most recent first: WRKJOB JOB(job_name) This command is very useful when an application server ends abnormally or fails to start successfully. For example, if an application server started then ended immediately, you could do the following with the job log:
|
Work with a specific job | This command displays the Work with Job screen for the specified job: WRKJOB JOB(job_number/job_user/job_name) This command is useful when you know the fully qualified job information for the job. |
View the job log for an active application server job |
|
Work with application server jobs that run under the QEJBSVR user profile | WRKUSRJOB USER(QEJBSVR) |
Delete spooled files for QEJBSVR user profile | DLTSPLF FILE(*SELECT) SELECT(QEJBSVR) |
View the spooled files for a job |
You can view ended jobs by using the Work with User Jobs (WRKUSRJOB) or Work with Job (WRKJOB) commands. |