Before you begin
To implement WebSphere Application Server for z/OS, you must implement
the necessary features, subsystems, and resources required for the runtime
environment. This section provides checklists for tasks you should verify
before running your WebSphere Application Server for z/OS system to prevent
the most common errors encountered during the installation.
Before
you begin: Perform the following steps to ensure problem avoidance, checking
off each item as you complete it:
- Prepare your z/OS environment:
Table 1.
Check
off |
Item |
|
Check
that all the maintenance suggested in the PSP bucket WASAS601 subset H28W601
has been applied. |
|
Make
certain your address space is large enough. Some WebSphere Application Server
for z/OS servers must be able to get a 1GB virtual region to run any workload.
Make sure that your installation exits (IEFUSI) do not limit the virtual region
size. We recommend that you specify REGION=0M so as not to limit their size. |
|
Add
another local page data set, two if your system does any paging of the WebSphere
Application Server for z/OS server address spaces. |
|
_________________________________________________________________
- Prepare your DB2 subsystem (if you will use DB2):
Table 2.
Check
off |
Item |
|
Increase
the MAX USERS (CTHREAD) and MAX BATCH CONNECT (IDBACK) in your DB2 environment
settings. Use the sample job in DSN710.SDSNSAMP(DSNTEJ6Z) to display the
"ZPARMS" settings of the running system. (An alternative is to use the DB2
Control Center to display these parameters.) |
|
Define
at least 200 buffers to the DB2 BP32K buffer pool. Use this command to display
the current bufferpool allocations: -dis bpool(active)detail.
Verify JDBC 2.0 functionality. The JDBC IVT sample01 JAVA application does
not exercise JDBC 2.0 drivers nor the RRS attach facility. A modified version
that tests these functions can be found in the DB2 Conundrum white paper at
http://www.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/WP100217. (This
will also verify that the DSNJDBC plan is bound correctly and that it matches
the .ser file.) |
|
Verify
the level of DB2 code running on your system with the DSNTEJ6U sample job
or run the DSNUTILB utility with the DIAGNOSE DISPLAY MEPL command.
The module names, dates, and PTF number on the right of the report are in
EBCDIC. |
|
Make
sure that any updates to the DB2 ERLY code are installed, and that you have
IPLed your system to activate them. |
|
Check
the JDBC service installed on your system. Use the following Java program
to display the service level:export LIBPATH=/usr/lpp/db2/db2710/lib:$LIBPATH>
java -cp /usr/lpp/db2/db2710/classes/db2j2classes.zip
COM.ibm.db2os390.sqlj.util.DB2DriverInfo
The typical output message looks like this:DB2 for OS/390 SQLJ/JDBC Driver build version is:DB2 7.1 PQ54756
|
|
_________________________________________________________________
- Verify your UNIX System Service configuration:
Table 3.
Check
off |
Item |
|
Specify
enough threads, files, and processes in your BPXPRMxx member of parmlib. Here
is a starting list if you do not have it set up yet:
- MAXTHREADS:10000
- MAXTHREADTASKS:5000
- MAXFILEPROC:10000
- MAXSOCKETS in the AF_INET domain:12000
|
|
If you
have an exit that checks for valid accounting codes, you might need to specify
an accounting value for spawned address spaces. Use the _BPX_ACCT_DATA= variable
in the was.env file. |
|
Ensure that the user ID associated
with running the installation jobs that run the BPXBATCH shell scripts has
an OMVS segment that directs PROGRAM('/bin/sh') to use the z/OS shell rather
than the tcsh (C) shell (at '/bin/tcsh'). These particular shell scripts will
not run from the tcsh shell. |
|
_________________________________________________________________
- Plan your SMP/E tasks:
Table 4.
Check
off |
Item |
|
You
can install WebSphere Application Server for z/OS into an SMP/E environment
(SMP/E 3.1 or later) separate from the one you use for z/OS. This includes
target and distribution zones, as well as HFS data sets. We recommend that
you use a separate environment, but you should enable the cross-zone checking
so that any prerequisite service requirement can be checked between the WebSphere
Application Server for z/OS and z/OS SMP/E zones. |
|
Verify
that the DDDEF for the LTS data set describes a PDSE format data set. This
will avoid LINK-EDIT errors during the SMP/E processing. |
|
You
should carefully read the WebSphere Application Server for z/OS: Program
Directory. This is a very large product and you have to make sure
that there is sufficient space in all target and temporary data sets for receive
and apply processing. |
|
_________________________________________________________________
Plan for the ISPF Customization dislog
- Plan for the ISPF Dialog considerations:
Table 5.
Check
off |
Item |
|
Do not
use ISPF Dialog in Split Screen mode. You might not see everything on one
screen. Keep in mind that there might be parameter values outside of the visible
portion of your screen and that this might cause some of the WebSphere Application
Server for z/OS installation options to be set to default values, which might
not be what you want. |
|
Turn
off PFSHOW on the ISPF Dialog screen. As with the split screen problem, there
might be parameter values outside the visible portion of your screen and this
might cause some of the WebSphere Application Server for z/OS installation
options to be set to default values, which might not be what you want. |
|
You
need to use a screen size of at least 32 lines to be able to invoke ISPF Dialog. |
|
You
might want to consider starting with new CNTL and DATA data sets as output
of the "Generate the Jobs Stream" function. During this task, you get a large
number of confirmation messages for every successful generated job. It is
very easy to overlook an error message during this process. Unfortunately
this sometimes causes the job generation process to stop without recreating
all JCL. When you run the jobs you might run "old" JCL and this will result
in unpredictable problems. |
|
- Verify your WLM environment:
Table 6.
Check
off |
Item |
|
Verify
that WLM is running in goal mode with the D WLM,SYSTEMS command. |
|
_________________________________________________________________
- Check your TCP/IP configuration:
Table 7.
Check
off |
Item |
|
Telnet
into UNIX Systems Services and issue these commands to verify that you can
find your host name by IP address or IP host-name:
- Get the local host name: hostname
- You will get a response such as: sc49.itso.ibm.com
- Use the output from the hostname command for the following nslookup command.
- Get host address by name: nslookup sc49.itso.ibm.com
- Get host name by address: nslookup 9.12.6.15
- You will get a response such as in the previous nslookup display.
There is also a small Java program, InetInfo.java, that you can run to
verify the same TCP/IP configuration. See techdocs for the program at http://www.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/TD100609.Example: This example shows you how to run the InetInfo Java code. JAVA4 @SC42:/u/java4>export PATH=/usr/lpp/java/IBM/J1.3/bin
JAVA4 @SC42:/u/java4>java InetInfo
get Local Host
IP Address:9.12.6.27
get Host Name By Address using 9.12.6.27
Host Name:wtsc42oe.itso.ibm.com
get Host Address By Name using wtsc42oe.itso.ibm.com
Host Address:9.12.6.27
|
|
Issue
the hometest command from TSO. It should show the correct
TCP Host name, corresponding IP address(es), and HOME IP addresses. If it
does not produce the correct results, then TCP/IP is not configured correctly. |
|
If the
fully qualified TCP/IP HostName is greater than 24 characters, then a DNS
will be required. Otherwise, the /etc/hosts file can provide the naming lookup. |
|
Verify
that the DNS name you are using is definitive (authoritative) in your installation. |
|
_________________________________________________________________
- Verify that security is in place:
Table 8.
Check
off |
Item |
|
Check
that the location service daemon has access to parmlib concatenation to retrieve
CTRACE settings in the CTIBBOxx member. |
|
Verify
that all WebSphere Application Server for z/OS servers must have READ access
to any data sets or files in their JCL procedures. |
|
Verify
that your installation has the RACF list-of-groups turned on. (SETROPTS LIST
will show you if turned on or off.) Without this list of groups turned on,
an ID cannot belong to more than one group and ASSR1 associates with only
WSSR1 instead of both WSSR1 and WSCFG1. Use the command SETROPTS GRPLIST to
turn on the list of groups. |
|
Define
the profile BPX.SAFFASTPATH in the FACILITY class to enable SAF fastpath support. |
|
If you
do not load SBBOLOAD into LPA, you must add it to the program control list
in the RACF PROGRAM class. (With z/OS Version 1.2, you can use the FACILITY
class profile BPX.DAEMON.HFSCTL class. This will cause only HFS files to be
checked for program control.) |
|
Verify
that the authorization bits for the WebSphere Application Server for z/OS
HFS (default name is /usr/lpp/zWebSphere/V6R0) file are
correctly set up for the WebSphere Application Server for z/OS configuration
group. |
|
_________________________________________________________________
- Verify that product code is consistent:
Table 9.
Check
off |
Item |
|
After
any maintenance has been applied, verify that the code loaded in LPALIB or
LNKLST is synchronized with the code in the product file system. Check the
location service daemon job log to verify that the correct maintenance level
is in use. |
|
_________________________________________________________________
You are done when you have checked all the applicable items.