PQ72577: Using defaults when cannot read current.env causes problems in different areas.

APAR status
Closed as fixed if next.

Error description
During start up of a Daemon, the following error occurred in
System Management and caused it end abnormally:

RRSAF IDENTIFY failed with RC=12,REASON=00F30006.

This indicates that there is a problem with DB2 subsystem.
However, the problem was that the current.env for System
Management server had permissions bits set to 640 so SM server
Local fix
could not read it.  Instead, it was using the defaults, which
included a different DB2 subsystem name that the customer had
configured.
For each variable that we can't find a customized value, we take
defaults and show it in the output as follows:
variableXX: NOT SET, DEFAULT=xyz.

However, we need at least a message that would inform the
customer that this is taking place, since most likely this is
not something the customer intends to do.
LOCAL FIX:
None.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Various problems can result during the  *
*                      start of a WebSphere server if the      *
*                      configuration file is unavailable or    *
*                      unreadable because the defaults which   *
*                      are taken for many variables may be     *
*                      inappropriate for a given               *
*                      configuration.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere servers should recognize mandatory configuration
variables and prevent the server from attempting to start if
these variables are not set.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 months.
APAR information
APAR number PQ72577
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2003-03-27
Closed date 2003-04-02
Last modified date 2003-04-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R401 PSN    UP


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 #: PQ72577
IBM Group: Software Group
Modified date: Apr 2, 2003