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. Preparing your z/OS environment. Complete these steps:
Check
off |
Item |
|
Check
that all the maintenance suggested in the PSP bucket WASAS700 subset
H28W7000 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 dataset, 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. Preparing
your DB2 subsystem. Complete these
steps:
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. Verifying your UNIX System Service configuration. Complete these steps:
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
- SHRLIBRGNSIZE: 67000000 (134000000 recommended)
|
|
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. Planning your SMP/E tasks. Complete
these steps:
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 datasets. 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 dataset describes a PDSE format dataset.
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 datasets for receive and apply processing. |
|
_________________________________________________________________
- Plan for the Profile Management Tool.
Table 5. Planning for the Profile Management
Tool. Complete these steps:
Check
off |
Item |
|
Install
the WebSphere Customization Tools. |
|
Make
sure that you have an FTP server running on your target z/OS system. |
|
Complete
the worksheets for each area before beginning. |
|
- Check your TCP/IP configuration.
Table 6. Checking your
TCP/IP configuration. Complete these steps:
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.
You can run the following script to verify the same TCP/IP configuration.Example: This
example shows you how to run the code. #!/bin/sh
JAVA_HOME=/usr/lpp/zWebSphere/V7R0/java
cat <<%% >jhometest.js
print("Get Local Host\n");
var localhost = java.net.InetAddress.getLocalHost();
var localipString = localhost.getHostAddress();
print("IP Address: " + localipString + "\n");
print("Get Host Name By Address using " + localipString + "\n");
var host = java.net.InetAddress.getByAddress(localhost.getAddress());
var hostname = host.getCanonicalHostName();
print("Host name: " + hostname + "\n");
print("Get Host Address By Name using " + hostname + "\n");
print("Host address: " + host.getHostAddress() + "\n");
quit();
%%
$JAVA_HOME/bin/jrunscript jhometest.js
rm jhometest.js
|
|
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 7. Verifying that
security is in place. Complete these steps:
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 datasets 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. |
|
Verify
that the authorization bits for the WebSphere Application
Server for z/OS HFS (default name is /usr/lpp/zWebSphere/V7R0)
file are correctly set up for the WebSphere Application
Server for z/OS configuration group. |
|
_________________________________________________________________
- Verify that product code is consistent.
Table 8. Verifying that product code
is consistent. Complete these steps:
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.