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

An i5/OS platform uses different configurations than installations of WebSphere Application Server on other platforms.

This topic describes the product library, directories, subsystem, job queue, job description, and output queues that WebSphere Application Server uses on the i5/OS platform.

Product library and directories

In a default installation, all editions of WebSphere Application Server for i5/OS use the following library and directories:

QWAS61 library
Product library
/QIBM/UserData/WebSphere/AppServer/V61 directory
Root directory for user data that is common to all editions of WebSphere Application Server V61.
/QIBM/ProdData/WebSphere/AppServer/V61/Express directory
Root directory containing product data that is shared by all WebSphere Application Server profiles. Additionally, the master copies of the files, which make up a profile, are stored here. Do not modify files under this directory structure.
/QIBM/UserData/WebSphere/AppServer/V61/Express directory
Root directory for profile information. If the -profilePath option is not specified when creating a profile, the profile is created under this path.

Subsystem

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

Job queue

All editions of WebSphere Application Server V61 for i5/OS use the QWASJOBQ job queue. The job queue is in the QWAS61 product library. 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 QWAS61 subsystem.

Job description

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

The QWASJOBD job description has the following default settings:

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

 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  . . . . . . . . . . . . . . . . . . . :   QWAS61
 Output priority (on output queue)  . . . . . . . :   5
 Printer device . . . . . . . . . . . . . . . . . :   *USRPRF
 Output queue . . . . . . . . . . . . . . . . . . :   QWASOUTQ
   Library  . . . . . . . . . . . . . . . . . . . :   QWAS61
 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

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

Output queues

All editions of WebSphere Application Server V61 for i5/OS use the QWASOUTQ output queue. The output queue is in the QWAS61 product library. By default, this output queue stores job logs for these processes:

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.




Related reference
Related information
Starting the WebSphere Application Server environment
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 8:21:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-express-iseries&topic=WelcAdrobjIs
File name: welc_adrobj_is.html