Message C9C21030 (Attempt to queue work to WLM failed) while attempting to bring up BBOASR2.
 Technote (FAQ)
 
Problem
Message C9C21030 (Attempt to queue work to WLM failed) while attempting to bring up BBOASR2.
 
 
Solution

-Verify the WLM Application Environment is AVAILABLE and not STOPPED.

To check the status of the applenv, issue the MVS console command:

D WLM,APPLENV=*

To re-enable the applenv after determining why the server region could not be started:

V WLM,APPLENV=xxxxxxxx,RESUME

where xxxxxxxx is the applenv name.

-The WLM application environment name must match the generic server name (server name in the Administration Application (SM EUI)). For example, the WLM application environment default for the Naming server is CBNAMING, which is also the default for the generic server name for Naming.

The WLM applenv name not matching the generic server name is one cause for a server region not being able to start. Some other possible causes could be a JCL error for the server region proc, typos in CLASSPATH or LIBPATH for the server potentially causing the JVM not to be initialized, etc.

If after resuming the applenv, it goes into the stopped state again, you must determine the reason for why the server region will not start by looking at the job output of the server region. WLM will attempt to start a server region 3 times. Upon the 3rd failure, it changes the state of the applenv to stopped so no more server regions will start. This is done so that system resources will not be consumed trying to continually start a server region that has a problem with it. Correct the problem with the server region, then resume the applenv again.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Install
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1050851
IBM Group: Software Group
Modified date: May 18, 2002