This topic applies only on the z/OS operating system.

Link pack area, link list, and STEPLIB

By placing load module data sets in the link pack area (LPA) and system link list, you can obtain improved MVS™ system performance and some virtual storage savings.

Product data sets

You can place only one set of WebSphere® Application Server for z/OS® load modules (any release) in the link pack area and link list because the same load module names are used across releases. For each application serving environment, the Customization Dialog is used to specify whether the environment's product data sets are already in the link pack area and link list or require loading from STEPLIB.

If load modules for a previous version of WebSphere Application Server for z/OS are in the system link pack area and link list, you must run the new version of WebSphere Application Server for z/OS from STEPLIB. If no previous version is in the system link pack area and link list, then you can choose a set of WebSphere Application Server for z/OS product libraries and place them in the link pack area and link list.

Recommendations:
  • Choose the WebSphere Application Server for z/OS product data sets that your production application serving environment will use.
  • Plan to load SBBOLPA and SBBOLOAD into the system link pack area. This will require approximately 8K of common storage below the 16M line and between 20M and 40M of extended common storage.
  • Plan to load SBBOLD2 into the system link list. You cannot place this data set in the link pack area.

System data sets

The WebSphere Application Server for z/OS customization process assumes that the following data sets are in the system link list:
  • SCEERUN
  • SCEERUN2
  • System SSL (SGSKLOAD or SIEALNKE)

If these data sets are not in the link list, be sure to follow the optional customization steps that direct you to add these data sets to STEPLIB concatenations in WebSphere Application Server JCL, and in the setupCmdLine.sh script. Certain Language Environment® load modules can be placed in the link pack area, providing performance improvements. For more information see the Language Environment® Customization manual for your z/OS release.

In z/OS Version 1 Release 6, the contents of the System SSL data set, SGSKLOAD, were merged into the SIEALNKE system data set.
  • If you chose to place SGSKLOAD in the link list or link pack area on your pre-z/OS Version 1 Release 6 systems, then place SIEALNKE in the link list or link pack area on your z/OS systems at Version 1 Release 6 and above. This will allow you to share WebSphere Application Server cataloged procedures across your z/OS systems.
  • If you chose not to place SGSKLOAD in the link list or link pack area on your pre-z/OS Version 1 Release 6 systems, then you will need to make separate copies of the WebSphere Application Server cataloged procedures to use on your z/OS systems at Version 1 Release 6 and above.
Select one of the following options.
  • If SIEALNKE is in the link list or link pack area on your z/OS systems at Version 1 Release 6 and above, remove SGSKLOAD from the STEPLIB concatenation in each cataloged procedure, and remove SGSKLOAD from the STEPLIB variable in each <WAS_home>/bin/setupCmdLine.sh script for those nodes running on z/OS Version 1 Release 6 (or above) systems.
  • If SIEALNKE is not in the link list or link pack area on your z/OS systems at Version 1 Release 6 and above, change the SGSKLOAD reference in the STEPLIB concatenation in each cataloged procedure to SIEALNKE, and change the SGSKLOAD reference in the STEPLIB variable in each <WAS_home>/profile/default/bin setupCmdLine.sh script to SIEALNKE, for those nodes running on z/OS Version 1 Release 6 (or above) systems.

STEPLIB statement in setupCmdLine.sh

Each WebSphere Application Server for z/OS node home directory uses a setupCmdLine.sh shell script to set environment variables during the execution of administrative scripts. One of the functions of this shell script is to set the STEPLIB variable, which provides STEPLIB capability when running a file system executable file.

During initial node configuration, the Customization Dialog sets the value of the STEPLIB variable in setupCmdLine.sh to the same list of data sets as the STEPLIB concatenation in the node's cataloged procedures. You might need to update this shell script (which resides in WAS_HOME/profile/default/bin for each node) for a variety of reasons. Update the shell script if you do any of the following:
  • Change which WebSphere Application Server for z/OS product code level is in the system link pack area and link list.
  • Apply maintenance and you will need to change which WebSphere Application Server for z/OS product code level a cell is using.
    Note: All nodes in a cell on the same system must use the same product code level.
  • You will need to add additional STEPLIB data sets. (For example, for DB2® or CICS® interfaces.)
To update STEPLIB in setupCmdLine.sh, edit the copy of the script in each affected WAS_HOME/profile/default/bin directory and find lines like the following:
	STEPLIB='WAS.V60.TEST.SBBOLD2':$STEPLIB
	STEPLIB='WAS.V60.TEST.SBBOLOAD':$STEPLIB
	export STEPLIB
Add or remove lines from this concatenation as needed. Be sure to update each node's setupCmdLine.sh script, including the one for the deployment manager.

Switching between LPA/LNKLST and STEPLIB

If you decide to move a particular level of WebSphere Application Server for z/OS product code (previously run from STEPLIB) into the system link pack area and link list, perform the following steps:
  1. Identify the application serving environments making use of these product libraries. (That is, the ones that have cataloged procedure STEPLIB statements for these particular SBBOLPA, SBBOLOAD and SBBOLD2 data sets.)
  2. Make sure that no other version of WebSphere Application Server for z/OS is in either the link pack area or link list.
  3. Place SBBOLPA in the link pack area. Place SBBOLOAD and SBBGLOAD in either the link pack area or link list, and place SBBOLD2 in the link list.
  4. Edit all WebSphere Application Server for z/OS cataloged procedures that use these data sets, removing SBBOLPA, SBBOLOAD and SBBOLD2 from any STEPLIB in which they appear. In the cataloged procedures generated by the Customization Dialog, the proclib members that will require editing are the INCLUDE JCL members that have names ending in "Z".
  5. For each of the application serving environments that use these data sets, remove SBBOLOAD, SBBGLOAD and SBBOLD2 from the STEPLIB statement in the WAS_HOME/profile/default/bin setupCmdLine.sh script in each WebSphere Application Server home directory.
If you no longer want to run a particular level of WebSphere Application Server for z/OS product code from LPA / link list, and you want to run it from STEPLIB instead, perform the following steps:
  1. Identify the application serving environments that make use of these product libraries. (That is, the ones that do not have cataloged procedure STEPLIB statements for SBBOLPA, SBBOLOAD and SBBOLD2.)
  2. Edit all WebSphere Application Server for z/OS cataloged procedures for these application serving environments. In the cataloged procedures generated by the Customization Dialog, the proclib members that will require editing are the INCLUDE JCL members that have names ending in "Z".
    1. Add SBBOLPA, SBBOLOAD and SBBOLD2 to the STEPLIB concatenation in all location service daemon cataloged procedures.
    2. Add SBBOLOAD, SBBGLOAD and SBBOLD2 to the STEPLIB concatenation in all controller and servant cataloged procedures.
  3. For each of the affected application serving environments, add SBBOLOAD and SBBOLD2 to the STEPLIB statement in the WAS_HOME/profile/default/bin setupCmdLine.sh script in each WebSphere Application Server home directory.
  4. Modify IPL procedures so that the WebSphere Application Server for z/OS data sets are no longer in the system link pack area and link list.
  5. Ensure that you continue to load a copy of the BBORTSS5 load module (release independent) into the system link pack area. You can load this module from any Version 5.x or Version 6.0 SBBOLPA data set.



Related concepts
Product data sets
[z/OS] Cataloged procedures
Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=cins_lpa
File name: cins_lpa.html