Responding to Message MSGIGGN311E RSN00000001 BBO.SBBOLPA CAN NOT BE PDSE
 Technote (troubleshooting)
 
Problem(Abstract)
While running IBM® WebSphere® Application Server for z/OS® on a z/OS V1R2 system, a customer received the following message:

MSGIGGN311E RSN00000001 BBO.SBBOLPA CAN'T BE PDSE

The customer had placed BBO.SBBOLPA in IEALPA00 which is recommended in the z/OS documentation. However since this is a PDS-E, IPL/NIP rejects it because the dataset must be a partitioned dataset (PDS) in order for it to be put in LPAlist.
 
Cause
Dataset was type PDSE
 
Resolving the problem
Add the SBBOLPA library to LPA.

Notes:

1. You must load members dynamically into LPA because they reside in PDSEs, and OS/390® or z/OS cannot load members of a PDSE at system initialization time. For example, issue:

SETPROG LPA,ADD,MASK=*,DSNAME=hlq.SBBOLOAD
SETPROG LPA,ADD,MASK=*,DSNAME=hlq.SBBOLPA


where hlq is the high-level qualifier for your WebSphere Application Server for z/OS data sets.

Make sure your LPA is large enough to hold the WebSphere Application Server for z/OS modules. See your WebSphere Application Server for z/OS documentation for recommendations for using memory.

2. Purge modules with the same name as those from BBO.SBBOLPA, BBO.SBBOLOAD, or BBO.SBBOLD2 that are already in the LPA.

3. Use the COMMNDxx member of SYS1.PARMLIB (after z/OS R1.2) to load WebSphere Application Server for z/OS modules into LPA after IPL is complete. You can add the 'SETPROG=LPA,...' command in the COMMNDxx member to have the WebSphere Application Server for z/OS modules added to LPA during IPL.
 
 
 


Document Information


Current web document: swg21061692.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Install
Operating system(s): z/OS
Software version: 5.0
Software edition:
Reference #: 1061692
IBM Group: Software Group
Modified date: Mar 27, 2006