Before you begin
This task describes the steps to STEPLIB the WebSphere Application Server for z/OS load data sets. Because different versions of WebSphere Application Server for z/OS share many common module names (such as SBBOLOAD), only one version of WebSphere Application Server for z/OS can have its modules in LPA/LNKLST at a time on a given system. You must place the modules for any other version of WebSphere Application Server for z/OS on that system in STEPLIB.
The STEPLIB data sets effectively override the data sets that are in LPA/LNKLST, which means:
The WebSphere Application Server for z/OS load data sets that must be configured before you can load them from STEPLIB are:
The decision to STEPLIB the WebSphere Application Server for z/OS load data sets is a decision that affects an entire node. A node can be defined in the following ways:
Use the following steps to STEPLIB your WebSphere Application Server for z/OS load data sets:
Steps for this task
Note: All nodes in the same cell on the same LPAR share the same location service daemon. Therefore, if you have configured any nodes together in this manner, they will all have to be run from the same STEPLIB.
Example: If your WAS_HOME directory name is /WebSphere/V5R1M0/AppServer, then you need to update the "OS/390)" section of /WebSphere/V5R1M0/AppServer/bin/setupCmdLine.sh to include the following STEPLIB setup:
STEPLIB='<high-level qualifier>.SBBOLOAD':$STEPLIB STEPLIB='<high-level qualifier>.SBBOLD2':$STEPLIB STEPLIB='<high-level qualifier>.SBBOLPA':$STEPLIB export STEPLIB
Note:
Do not modify setupCmdLine.sh except as directed by product documentation or by service personnel. In particular, do not move lines around or comment them out unnecessarily, as this can cause problems with post-installer scripts that update setupCmdLine.sh and other files. If you need to remove data set names from the STEPLIB variable, be sure to leave at least one STEPLIB=line in the OS/390 section: STEPLIB=$STEPLIB