PQ81454: gsk_initialize errors in Daemon when Global Security enabled | |||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description With Global Security enabled, the customer noticed the following error in the Daemon server: . BBOO0036E FUNCTION gsk_initialize FAILED WITH RC=-99 . followed by successful initialization message: . BBOO0246I INITIALIZATION COMPLETE FOR DAEMON . Everything seems to be working fine (access to admin console, applications using SSL). . We were attempting to start Daemon with SSL enabled, but it was not configured correctly. Daemon was started successfully, but is not secured. If Daemon needs to be secured, additional steps need to be followed. This is in addition to securing other servers (DMgr, app servers, Node Agent). . We are adding new functionality that will allow customers to disable security just for the daemon. . Note: If gsk errors come out in any other WebSphere server than Daemon, they need to investigated to ensure the servers are secured. . MD18030(?)Local fix 1. Ignore the message. Daemon is not secured. OR 2. Secure Daemon. Follow the steps in the InfoCenter: http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp In the left panel: WAS for z/OS -> Installing -> Security -> Implementing security considerations... -> Setting up WAS for z/OS security -> Setting up SSL security for WebSphere App Server -> Daemon SSL.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Customer gets the following msg in * * Daemon log when Global Security is * * Enabled in the Application Server but * * SSL was not configured for the Daemon: * * BBOO0036E FUNCTION * * gsk_environment_init FAILED WITH RC= * * 202 * **************************************************************** * RECOMMENDATION: * **************************************************************** This error indicates that SSL was not configured properly for the Daemon.Problem conclusion Temporary fix Comments If SSL is required for the Daemon be sure to configure SSL for the Daemon to correct the problem. If SSL is not required the message can be ignored. The information to configure the Daemon with SSL can be found in the InfoCenter at the following URL: http://wasinfo.raleigh.ibm.com/help/ index.jsp?topic=/com.ibm.websphere.zseries.doc/ info/zseries/ae/csec_daemonssl.html 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 release within the next 18 months.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PQ81454.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ81454
IBM Group: Software Group
Modified date: Jan 12, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.