PQ57053: IMPROVE INSTRUCTIONS FROM ISPF CUSTOMIZATION DIALOG, AND CORRECTI&C GUIDE WITH REGARD TO ADDING WEBSPHERE MODULES TO LPA | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Step 8 of the Instructions that are generated by the ISPF ISPF Installation Dialogs, (member BBOINSTR in dataset "xxx.yyy.CNTL"), are confusing and should be improved. In addition there is a section in the Installation and Customization Manual that discusses placing WebSphere modules in LPA or Link List which also has incorrect information. . Step 8 in BBOINSTR discusses placing the WebSphere modules in LPA or Link LIst. There is a RULE: statement in this set of instructions which reads: RULE: These data sets are PDSEs and cannot be added to members LPALSTxx or IEALPAxx. . This rule is confusing, since the instructions are also telling you to install the modules into LPA or Link List. . The wording of this RULE needs to be changed to inform the customers that the fact that they are PDSE's prevents the data- sets from being ADDED to these specific ParmLib members, but that the customer could use a COMMNDxx ParmLib member, and enter a 'SET PROG=xx' command from the COMMNDxx member, to place the WebSphere Modules into LPA during the IPL process. . The Installation and Customization Manual, (GA22-7834-02), Chapter 5, "Performing advanced tasks", Section: "Steps for customizing base z/OS or OS/390 functions on the other systems in the sysplex", Step 5, Note 'c', says: "We recommend that you update automation to load WebSphere for into LPA after an IPL. COMMNDxx is not appropriate for this task commands execute prior to DFSMS services being made available." . This statement is no longer correct. You CAN use a COMMNDxx member, which has a 'SET PROG=yy' command, to add the WebSphere modules to LPA during the IPL.Local fix Add a 'SET PROG=xx' statement to a COMMNDxx Parmlib member, to have the WebSphere modules placed into LPA during IPL. You could also add the WebSphere modules to LPA using the SETPROG LPA,ADD,MASK=*,DSNAME=yyyy.SBBOzzzz where the DSNAME points to the datasets that you want to add to LPA.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: The restriction in the customization * * instructions and Installation and * * Customization publication of NOT being * * able to use COMMNDxx to issue SET * * PROG=yy to get WAS modules into LPA * * during IPL is INCORRECT. * * is INCORRECT. * **************************************************************** * RECOMMENDATION: * **************************************************************** Instruction 8 in the customization instructions and Installation and Customization incorrectly recommend that you update automation to load Websphere for z/OS modules into LPA after an IPL, but that COMMNDxx is not appropriate for this task because the commands execute prior to DFSMS services being made available.Problem conclusion Modifications have been made to the customization instructions (BBOINSTR) and the Installation and Customization publication to read: RECOMMENDATION: For automation, if you want to ensure WebSphere for z/OS modules are loaded into dynamic LPA and available after an IPL, create a new PROGxx member with the SETPROG LPA commands and invoke the PROGxx member from PARMLIB COMMNDxx. APAR PQ57053 requires a change to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/ Document Name: WebSphere Application Server V4.0.1 for z/OS and OS/390: Installation and Customization Document Number: GA22-7834-02 On page 229, change the table notes in Table 35 to the following: RULE: These datasets are PDSEs and cannot be added to members in LPALSTxx or IEALPAxx. RECOMMENDATION: For automation, if you want to ensure WebSphere for z/OS modules are loaded into dynamic LPA and available after an IPL, create a new PROGxx member with the SETPROG LPA commands and invoke the PROGxx member from PARMLIB COMMNDxx. EXAMPLE: SETPROG LPA,ADD,MASK=*,DSNAME=hlq.SBBOLOAD SETPROG LPA,ADD,MASK=*,DSNAME=hlq.SBBOLPA where hlq is the high-level qualifier for your WebSphere for z/OS datasets. NOTE: If using SETPROG on a running system, be sure to purge modules with the same name as those from BBO.SBBOLPA, BBO.SBBOLOAD, or BBO.SBBOMIG that are already in the LPA. ATTENTION: Be sure that the size of your LPA can hold the WebSphere for z/OS modules. See "Recommendations for using memory" on page 49. APAR PQ57053 is associated with SERVICE LEVEL W401037 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ64636 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ57053
IBM Group: Software Group
Modified date: May 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.