WAS.ERROR.LOG Logstream Not Found after Customization of a new Deployment Manager Cell
 Technote (troubleshooting)
 
Problem(Abstract)
After customizing a new deployment manager cell, users may see the following error in the DMGR joblog:

IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM WAS.ERROR.LOG DID NOT SUCCEED FOR JOB WADMI2. RETURN CODE: 00000008 REASON CODE: 0000080B
DIAG1: 00000008 DIAG2: 0000F801 DIAG3: 05030004 DIAG4: 05020010

The 0x80B error implies that the logstream does not exist.
 
Cause
There are currently no customization options to define an error logstream for a deployment manager cell. This is as designed, as it was assumed users would install a base application server node initially, and create an error logstream during that customization that would be used later when creating a deployment manager cell.

The deployment manager code falls back on the default name of the logstream ( of WAS.ERROR.LOG) if none has been specified for the "ras_logstreamName" in the environment variables for the cell. This is the reason for the error message.

The message will be displayed if either the base appserver logstream is being used with a name other than WAS.ERROR.LOG, or no base appserver logstream has been created.

It should be noted that the design team is currently reviewing this, and in the next version of WebSphere, there will be an option to customize a logstream specifically for a deployment manager cell.

 
Resolving the problem
Users should use the base appserver customization job BBOERRLG to create the logstream (if one has not been created already) and change the value of "ras_logstreamName" to the name desired for the logstream.
 
 
 


Document Information


Current web document: swg21217928.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Install
Operating system(s): z/OS
Software version: 6.0.2
Software edition:
Reference #: 1217928
IBM Group: Software Group
Modified date: Sep 23, 2005