Preparing the z/OS operating system for installation

Use this task to prepare your z/OS® target systems for WebSphere® Application Server for z/OS.

1. Identify the first z/OS target system on which you plan to create a WebSphere Application Server for z/OS application serving environment.
2. Print off a copy of Checklist: Preparing the base z/OS operating system.
   Use this worksheet to identify which of the following steps have been completed for the target system and record information you will need during product configuration.
3. Prepare z/OS operating system settings.
   See Preparing z/OS to run WebSphere Application Server for detailed instructions.
4. Prepare z/OS sysplex settings.
   See Preparing the sysplex on z/OS for detailed instructions.
5. Prepare the z/OS job entry subsystem (JES2 or JES3).
   See Preparing JES2 or JES3 for detailed instructions.
6. Identify TCP/IP resources you want to use and prepare your network.
   See Preparing TCP/IP on z/OS for more information.
7. Set up Resource Recovery Services (RRS).
   See Preparing Resource Recovery Services (RRS) for more information.
8. Set up your SAF-compliant security package.
   See Preparing the security server (RACF) if you will use the z/OS Security Server. If you will use another SAF-compliant security product, consult the product's manufacturer for assistance.
9. If you are using a DB2 database, set up DB2 for concurrency control management.
   If your installation uses typical DB2 defaults for U-lock management and lock size, certain WebSphere Application Server applications that use container-managed Enterprise beans (CMP beans) might encounter deadlocks. The likelihood of encountering deadlocks is entirely dependent on the design and execution pattern of the applications. The potential for deadlocks increases with the number and frequency of applications driving concurrent transactions that update the same areas of the DB2 database. If, given the workload for your applications, the potential for deadlocks is high, consider using the following DB2 settings:

   RRULOCK(YES) 
   LOCKSIZE(ROW)

   For additional details, see the information about settings for the internal resource lock manager (IRLM) in your DB2 Installation Guide.

   Your applications might qualify for the optimistic approach to concurrency control management. To determine whether your applications can use optimistic concurrency control, see the article about concurrency control in the z/OS view of the WebSphere Application Server documentation.

10. Repeat these steps for each z/OS target system on which you plan to run WebSphere Application Server for z/OS.
11. Keep the worksheets you filled out as you will need some of the information you recorded on them during product configuration.