Product library, directories, subsystem, job queue, job description, and output queues

This page describes the product library, directories, subsystem, job queue, job description, and output queues that WebSphere Application Server and WebSphere Application Server Network Deployment use on your iSeries server.

• Product library and directories
• Subsystem
• Job queue
• Job description
• Output queue

Product library and directories

All editions of WebSphere Application Server, V6 for OS/400 use the library and directories listed here:

• QWAS6 library
  Product library.

• /QIBM/UserData/WebSphere/AppServer/V6 directory
  Root directory for user data which is common to all editions of WebSphere Application Server V6.

• /QIBM/ProdData/WebSphere/AppServer/V6/Base directory
  Root directory for the WebSphere Application Server and WebSphere Application Server - Express products. Product data which is shared by all WebSphere Application Server profiles is stored here. Additionally, the master copies of the files which make up an profile are stored here. Files under this directory structure should not be modified.

• /QIBM/UserData/WebSphere/AppServer/V6/Base directory
  Root directory for WebSphere Application Server Base and Express edition profile information. If the -profilePath option is not specified when creating a profile, the profile is created under this path.

• /QIBM/ProdData/WebSphere/AppServer/V6/ND directory
  Root directory for the WebSphere Application Server Network Deployment product. Product data which is shared by all WebSphere Application Server Network Deployment profiles is stored here. Additionally, the master copies of the files which make up an profile are stored here. Files under this directory structure should not be modified.

• /QIBM/UserData/WebSphere/AppServer/V6/ND directory
  Root directory for WebSphere Application Server Network Deployment profile information. All profiles of Network Deployment are created under this directory structure.

Subsystem

All editions of WebSphere Application Server, V6 for OS/400 use the QWAS6 subsystem. The subsystem description for QWAS6 is located in the product library, QWAS6. The application server, node agent and deployment manager processes run in this subsystem.

Job queue

All editions of WebSphere Application Server, V6 for OS/400 use the QWASJOBQ job queue. The job queue is located in the product library, QWAS6. The application server, node agent, and deployment manager processes are all submitted to this job queue when you invoke the startServer, startNode, or startManager scripts. The QWASJOBQ job queue is associated with the QWAS6 subsystem.

Job description

All editions of WebSphere Application Server, V6 for OS/400 use the QWASJOBD job description. The job description is located in the product library, QWAS6. The application server, node agent, and deployment manager processes use this job description when submitted to run in the QWAS6 subsystem.

The QWASJOBD job description has the following default settings:

                            Display Job Description                                                              System:   MYISERIES
 Job description:   QWASJOBD       Library:   QWAS6

 User profile . . . . . . . . . . . . . . . . . . :   QEJBSVR
 CL syntax check  . . . . . . . . . . . . . . . . :   *NOCHK
 Hold on job queue  . . . . . . . . . . . . . . . :   *NO
 End severity . . . . . . . . . . . . . . . . . . :   30
 Job date . . . . . . . . . . . . . . . . . . . . :   *SYSVAL
 Job switches . . . . . . . . . . . . . . . . . . :   00000000
 Inquiry message reply  . . . . . . . . . . . . . :   *RQD
 Job priority (on job queue)  . . . . . . . . . . :   5
 Job queue  . . . . . . . . . . . . . . . . . . . :   QWASJOBQ
   Library  . . . . . . . . . . . . . . . . . . . :     QWAS6
 Output priority (on output queue)  . . . . . . . :   5
 Printer device . . . . . . . . . . . . . . . . . :   *USRPRF
 Output queue . . . . . . . . . . . . . . . . . . :   QWASOUTQ
   Library  . . . . . . . . . . . . . . . . . . . :     QWAS6
 Message logging:
   Level  . . . . . . . . . . . . . . . . . . . . :   4
   Severity . . . . . . . . . . . . . . . . . . . :   0
   Text . . . . . . . . . . . . . . . . . . . . . :   *SECLVL
 Log CL program commands  . . . . . . . . . . . . :   *NO
 Accounting code  . . . . . . . . . . . . . . . . :   *USRPRF
 Print text . . . . . . . . . . . . . . . . . . . :   *SYSVAL

 Routing data . . . . . . . . . . . . . . . . . . :   QCMDI

 Request data . . . . . . . . . . . . . . . . . . :   *NONE

 Device recovery action . . . . . . . . . . . . . :   *SYSVAL
 Time slice end pool  . . . . . . . . . . . . . . :   *SYSVAL
 Job message queue maximum size . . . . . . . . . :   *SYSVAL
 Job message queue full action  . . . . . . . . . :   *WRAP
 Allow multiple threads . . . . . . . . . . . . . :   *YES
 Initial ASP group  . . . . . . . . . . . . . . . :   *NONE
 Spooled file action  . . . . . . . . . . . . . . :   *SYSVAL
 Text . . . . . . . . . . . . . . . . . . . . . . :   WEBSPHERE JOB DESCRIPTION        

The Request data parameter allows you to specify information to start a WebSphere Application Server profile when the QWAS6 subsystem is started. For more information on how to start an application server when the subsystem starts see Start the WebSphere Application Server environment. You can modify the job description if the values do not meet your requirements. However, not change the Allow multiple threads value. Because the WebSphere Application Server processes contain a Java virtual machine that is multi-threaded, this value must be *YES.

Output queues

All editions of WebSphere Application Server, V6 for OS/400 use the QWASOUTQ output queue. The output queue is located in the product library, QWAS6. By default, this output queue stores joblogs for these processes:

• The application server process
• The node agent process
• The deployment manager process

This queue also stores other spooled files. The public authority to the output queue is *USE. This setting ensures that the user profile that is specified for the USER parameter (on the SBMJOB command) has the necessary authority to the output queue when it submits the WebSphere Application Server job to the job queue. The default user profile is QEJBSVR.

You might want to clear the output queue periodically if the number or size of the spooled files becomes large.