PQ67872: THE RESPONDER TEXT OF APAR PQ60198 NEEDS TO BE CLARIFIED. | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as documentation error. Error description The responder text of apar PQ60198 lists some changes which must be made to the EXEC statement of the J2EE Server startup proc. This text states that the following should be specified: . PARM= ENVAR("_EDC_UMASK_DFLT=xxx") . This text should be clarified to explain exactly how and where this parameter should be coded. If this parameter is coded incorrectly, it could cause major problems in attempting to get your J2EE server started. A sample EXEC statement that was used successfully following the application of PQ60198 follows: . //BBSxxxxS EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT, // PARM='ENVAR("_EDC_UMASK_DFLT=007")/ &PARMS &IWMSSNM' . APAR PQ60198 also made a documentation change to the WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-04) document, so this text should be clarified in Chapter 8 of this document as well.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: Text in the WebSphere for z/OS books * * Installation and Customization, and * * Assembling J2EE Applications, should * * be updated to clearly illustrate how to * * code the UMASK parameter on the EXEC * * statement for a J2EE server. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere for z/OS Installation and Customization, and Assembling J2EE Applications, both contain text that explains how to use the UMASK parameter to set permissions for temporary application files so that a J2EE server has the authority to remove those temporary files. Both books should be updated with a sample EXEC statement to clearly illustrate how to code the UMASK parameter. Incorrectly coding the parameter could cause major problems when customers attempt to start the J2EE server.Problem conclusion This APAR requires changes to documentation. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/ WebSphere Application Server V4.0.1 for z/OS and OS/390 Installation and Customization (GA22-7834-06) will be changed as follows: Chapter 2. Preparing the base z/OS or OS/390 environment Subtopic "Setting permission for files created by applications" Update the recommendation on page 37, by adding the example: Recommendation: A umask value of 007 will cause files to be created with permission bits set to 770. This is the IBM-recommended value. Example: //BBSxxxxS EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT, // PARM='ENVAR("_EDC_UMASK_DFLT=007")/ &PARMS &IWMSSNM' WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-05) will be changed as follows: Chapter 8. Creating a J2EE server run-time environment Subtopic "Steps for creating JCL procedures for the control and server regions" In Step 2 on page 136, update the recommendation on page 137, by adding the example: Recommendation: IBM recommends that you use a umask value of 007, which means that files created by applications running in the server region will have permission bits set to 770. Other umask values of the form x0 x are acceptable. Example: //BBSxxxxS EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT, // PARM='ENVAR("_EDC_UMASK_DFLT=007")/ &PARMS &IWMSSNM'Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: 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 #: PQ67872
IBM Group: Software Group
Modified date: Jan 14, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.