ABENDA03 BBOU0006E minor code=C9C2040F, BBOU0707W and BBOU0164W
 Technote (FAQ)
 
Problem
The Naming Server in WebSphere® Application Server for z/OS® V4.0.1 ended abnormally on startup. The following Warning Message is issued:
BBOU0707W Function vfprintf failed with RC=-1. System determined REASON=EDC5133I No space left on device.
Note: this particular error could occur for any server.
 
Cause
ABENDA03 is received because Naming has already established the connection to LDAP and DB2® when the exception for minor code C9C2040F is issued. In this case, the exception occurred on the main thread and WebSphere Application Server exits rather than abending during exception processing. When an exception occurs on the main thread, WebSphere Application Server receives the ABENDA03 from MVS instead of WebSphere Application Server abending and letting MVS ABEND the other threads.

The device that is being referred to in message "System determined REASON=EDC5133I No space left on device' is dev/null. WebSphere Application Server uses the vprintf message to format WebSphere Application Server errors and informational messages. Since WebSphere Application Server messages can have variable fillin text in the messages, there is no way to know how much storage to obtain to build the messages. WebSphere Application Server uses a temporary file called /dev/null. This is a special unix file that this problem is associated with.

 
Solution
This problem can be resolved by deleting /dev/null then recreating it using the UNIX cp command. The server should come up normally.

In one case, after an IPL, /dev/null was an actual file instead of a special characters file. When it was restored, the WebSphere Application Server address spaces came up successfully. In this case the /dev/null was deleted and recreated and the WebSphere Application Server address spaces came up successfully.

For message BBOU0707W, "REASON=EDC5113I Bad file descriptor." can also appear instead of the "REASON=EDC5133I No space left on device." and is another symptom of the same problem.

In V5, the BBOU0006E message would be BBOO0006E and message BBOU0707W would be BBOO0164W with the same text as the V401 messages.

The processing of the messages in V5 and use of /dev/null for fillins is the same in V5 as it is in V401. Minor code C9C2040F is issued for V401 and V5.

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Crash
Operating system(s): z/OS
Software version: 5.1
Software edition:
Reference #: 1175394
IBM Group: Software Group
Modified date: Jul 28, 2004