On Pages 23 & 24 of the DB2 Web Query Redbook, it identifies the following jobs as running on the system to support DB2 Web Query:
EDAPTH
EDAPLOG
EDAPGWY
TSCOM3
JSCOM3
HLISNK
QP0ZSPWP
WQLQI7
QSQSRVR
Have there been any changes in the job names with the new releases or new PTFs?
If so, will the list in the Redbook be updated on its next release?
Eric - yes, this section has been updated. I have copied/pasted a portion of it below:
The following jobs run on your server when the Reporting Server is running. For all jobs, the start time of the job is the start time of the Reporting Server.
• EDAPTH: There is one job that helps with the workspace process.
• EDAPLOG: There is one job that contains startup information.
• EDAPGWY: There are three of these jobs, which are listener jobs, one each for HTTP, TCP, and Java. These jobs receive incoming requests and hand off work to the TSCOM3 jobs.
• TSCOM3: By default, four of these jobs are running. These jobs accept the request from the EDAPGWY job and translate the DB2 Web Query request into SQL. One TSCOM3 job does not correspond to one user; one TSCOM3 job can service several users. For this reason, the design of these jobs contributes to the scalability of the product. They are referred to as “agents.”
• JSCOM3: There is one job, which services Java processes.
• HLISNK: There is one job, which is an internal server process.
• WQLWI7: This job is for integrated application server jobs. Four of these jobs should be running whenever DB2 Web Query is active.
• QSQSRVR: This i5/OS native prestart job handles SQL requests that are made over CLI. This job does the actual database work of optimization and returning the result.
With the exception of the WQLWI7 jobs, these jobs will run in the QSYS work subsystem. However, it is possible to customize your system such that the QSQSRVR jobs run in a different subsystem. The WQLWI7 jobs will run in the QHTTPSVR subsystem.
Another way to look at the jobs is via their ports. When running, DB2 Web Query will be active on ports 11331 to 11339. When first started, ports 11336 and 11338 may not start until the first user hits the Web Query login page. Port 11339 is used for the Report Broker add-on product. Therefore, if you do not have that product installed, this port will not be active. At the time of publication, port 11337 is not used.
You can look at active ports by using the NETSTAT command and taking option 3. Once the display is up, use F14 to display port numbers. As you scroll down, you will see the local port column is ordered descending. Scroll down until you reach a local port of 11331 to see these connections.
