Product library, directories, and subsystems

This page describes the product library, directories, subsystem, job queue, job description and output queue that WebSphere Application Server - Express uses on your iSeries server.

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

Product library and directories

WebSphere Application Server - Express for iSeries uses the library and directories listed here:

• QASE51 library
  Product library.

• /QIBM/ProdData/WebASE51 directory
  Product root directory.

• /QIBM/UserData/WebASE51 directory
  Instance root directory.

• /QIBM/ProdData/WebASE51/ASE directory
  Root directory for the WebSphere Application Server - Express product. Product data which is shared by all WebSphere Application Server - Express instances is stored here. Additionally, the master copies of the files which make up an instance are stored here. Files under this directory structure should not be modified.

• /QIBM/UserData/WebASE51/ASE directory
  Root directory for WebSphere Application Server - Express instances. All WebSphere Application Server - Express instances are created under this directory structure.

Subsystem

WebSphere Application Server - Express for iSeries uses this subsystem. The subsystem description is located in the product library, QASE51.

• QASE51 subsystem
  WebSphere Application Server - Express subsystem. The application server processes run in this subsystem.

Job queue

WebSphere Application Server - Express for iSeries uses this job queue. The job queue is located in the product library, QASE51.

• QASE51 job queue
  WebSphere Application Server - Express job queue. The application server process is submitted to this job queue when you invoke the startServer script. The QASE51 job queue is associated with the QASE51 subsystem.

Job description

WebSphere Application Server - Express for iSeries uses this job description. The job description is located in the product library, QASE51.

• QASE51 job description
  WebSphere Application Server - Express job description. The application server process uses this job description when submitted to run in the QASE51 subsystem.

  The QASE51 job description has the following default settings:

                              Display Job Description
                                                               System:   MYISERIES
   Job description:   QASE51       Library:   QASE51
  
   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  . . . . . . . . . . . . . . . . . . . :   QASE51
     Library  . . . . . . . . . . . . . . . . . . . :     QASE51
   Output priority (on output queue)  . . . . . . . :   5
   Printer device . . . . . . . . . . . . . . . . . :   *USRPRF
   Output queue . . . . . . . . . . . . . . . . . . :   QASE51
     Library  . . . . . . . . . . . . . . . . . . . :     QASE51
   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 . . . . . . . . . . . . . . . . . . . . . . :   APPLICATION SERVER - EXPRESS 5.1 JOB DESCRIPTION        
          

  A WebSphere Application Server - Express instance can be started automatically when the QASE51 subsystem is started by specifying the following command in the Request data parameter (set to *NONE by default.)

  QSYS/CALL PGM(QASE51/QASESTRSVR) PARM('-instance' '/QIBM/UserData/WebASE51/ASE/myInstance'
       '-server' 'myServer')

  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 multi-threaded, this value must be *YES.

Output queue

WebSphere Application Server - Express for iSeries uses this output queue. The output queue is located in the product library, QASE51.

• QASE51 output queue
  WebSphere Application Server - Express output queue. By default, this output queue stores joblogs for the application server 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 - Express 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 too large.