PM02082: DEPLOYMENT MANAGER AND NODEAGENT MAY FAIL TO START WITH IGVDGNPP TOOL ACTIVE ON Z/OS. AN 0C4 IS SEEN ON THE WEBSPHERE TCB.

Fixes are available

APAR status

Closed as program error.

Error description

On a WebSphere z/OS system, if the IGVDGNPP (formerly known as
PRIMEPSA) tool is active, the deployment manager and node agent
address spaces may fail to start. There is a hang during
initialization caused by an 0c4 on a websphere TCB. The 0c4
causes the address space to hang. The failing TCB has the
following traceback,

Function
--------
_TDUMP
j9dump_create
doSystemDump
protectedDumpFunction
j9sig_protect
runDumpAgent
triggerDumpAgents
dumpCrashData
j9sig_protect
structuredSignalHandler
masterSynchSignalHandler
__zerro
__zerros
CEEHDSP
CEEOSIGJ
CELQHROD
CEEOSIGG
CELQHROD
CF_TCP_Connection::init_As_Client(CF_ConnectionData*)
CF_TCP_Request::connect(int,CF_ConnectionData*)
Java_com_ibm_ws_tcp_channel_impl_ZAioTCPChannelCPPUtilities
connect
.
.

The exception is on "CF_TCP_Connection::init_As_Client".
Investigation shows that the WebSphere code incorrectly fetches
a IGVDGNPP value and used it as an address. This apar will fix
this problem.
-----

An additional symptom experienced with a
wsdamin thin client failure shows the following in
sysout.

-----
 BBOO0037E Function IWMMCHST failed with RC=8, REASON=00000820.
Trace: 2010/05/21 15:06:21.159 01 t=7C00F8 c=UNK key=P8
(0000000A)
  Description: Log Boss/390 Error
  from filename: ./bboowchn.cpp
  at line: 123
error message: BBOO0037E Function IWMMCHST failed with RC=8,
REASON=00000820.
----

Native Stacktrace from wsadmin abend dump shows:
------------
j9dump_create
doSystemDump
protectedDumpFunction
j9sig_protect
runDumpAgent
triggerDumpAgents
abortHandler
__zerro
__zerros
CEEVROND
CEEHDSP
CEEVH2OS
pthread_kill
abort
recursiveCrashHandler
masterSynchSignalHandler
__zerro
__zerros
CEEVROND
(unknown)
CEEKTBCK
(unknown)
CEEVH2OS
infoForModule
j9sig_info
j9sig_info_count
dumpCrashData
j9sig_protect
structuredSignalHandler
masterSynchSignalHandler
__zerro
__zerros
CEEVROND
CEEHDSP
CEEHRNUH
Java_com_ibm_ws_util_ZPerformanceBlock_setActive
RUNCALLINMETHOD
callStaticObjectMethodA
ZIOPChannelBridge::outbound_connect(ORB_Request*,BOSS_IOR*)
ORB_Request::ziop_cr_sclt_locate_request(ORB_Request::Outbound_L
ocate_St
atus*)
ORB_Request::comm_outbound_locate()
Java_com_ibm_ws390_orb_ClientDelegate_createRequestCFW
SIDECARINVOKEREFLECTCONSTRUCTOR
JVM_NewInstanceFromConstructor
Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0
SIDECARINVOKEREFLECTMETHOD
JVM_InvokeMethod
Java_sun_reflect_NativeMethodAccessorImpl_invoke0
SIDECARINVOKEREFLECTMETHOD
JVM_InvokeMethod
Java_sun_reflect_NativeMethodAccessorImpl_invoke0
RUNCALLINMETHOD
gpProtectedRunCallInMethod
signalProtectAndRunGlue
j9sig_protect
gpCheckCallin
callStaticVoidMethod
JavaMain
CEEVROND
CEEOPCMM
---

and the java stacktrace from wsadmin abend dump
---
com/ibm/ws/util/ZPerformanceBlock.setActive
com/ibm/ws/util/ZPerformanceBlock.driveStateChange
com/ibm/ws390/ziop/ZIOPConnectionMap.mapConnection
com/ibm/ws390/ziop/ZIOPConnectionMap.finishConnect
com/ibm/ws390/ziop/ZIOPConnectionMap.findOrCreateConnection
com/ibm/ws390/ziop/ZIOPChannelBridge.outboundConnect
com/ibm/ws390/orb/ClientDelegate.createRequestCFW
com/ibm/ws390/orb/ORB.rir_cfw_request
com/ibm/ws390/orb/ORB.resolve_initial_references_remote_host
com/ibm/ws390/orb/ORB.locateUsingBootstrap
com/ibm/ws390/orb/ORB.objectURLToObject
com/ibm/rmi/corba/ORB.string_to_object
com/ibm/ws/naming/util/WsnInitCtxFactory.stringToObject
com/ibm/ws/naming/util/WsnInitCtxFactory.getCosRootContext
com/ibm/ws/naming/util/WsnInitCtxFactory.getRootContextFromServe
com/ibm/ws/naming/util/WsnInitCtxFactory.getRootJndiContext
com/ibm/ws/naming/util/WsnInitCtxFactory.getInitialContextIntern
com/ibm/ws/naming/util/WsnInitCtx.getContext
com/ibm/ws/naming/util/WsnInitCtx.getContextIfNull
com/ibm/ws/naming/util/WsnInitCtx.lookup
com/ibm/ws/naming/util/WsnInitCtx.lookup
javax/naming/InitialContext.lookup
com/ibm/ws/management/connector/rmi/RMIConnectorClient.reconnect
com/ibm/ws/management/connector/rmi/RMIConnectorClient.reconnect
com/ibm/ws/management/connector/rmi/RMIConnectorClient.<init>
sun/reflect/NativeConstructorAccessorImpl.newInstance0
sun/reflect/NativeConstructorAccessorImpl.newInstance0
sun/reflect/NativeConstructorAccessorImpl.newInstance
sun/reflect/DelegatingConstructorAccessorImpl.newInstance
java/lang/reflect/Constructor.newInstance
com/ibm/websphere/management/AdminClientFactory.createAdminClien
com/ibm/websphere/management/AdminClientFactory.access$000
com/ibm/websphere/management/AdminClientFactory$1.run
com/ibm/ws/security/util/AccessController.doPrivileged
com/ibm/websphere/management/AdminClientFactory.createAdminClien
com/ibm/ws/scripting/CommonScriptingObject.connectToAdminService
com/ibm/ws/scripting/CommonScriptingObject.<init>
com/ibm/ws/scripting/AdminControlClient.<init>
com/ibm/ws/scripting/AbstractShell.createControlClient
com/ibm/ws/scripting/AbstractShell.run
com/ibm/ws/scripting/WasxShell.main
sun/reflect/NativeMethodAccessorImpl.invoke0
sun/reflect/NativeMethodAccessorImpl.invoke0
sun/reflect/NativeMethodAccessorImpl.invoke
sun/reflect/DelegatingMethodAccessorImpl.invoke
java/lang/reflect/Method.invoke
com/ibm/wsspi/bootstrap/WSLauncher.launchMain
com/ibm/wsspi/bootstrap/WSLauncher.main
com/ibm/wsspi/bootstrap/WSLauncher.run
-------

Local fix

The servers will start when IGVDGNPP or PRIMEPSA is not active

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: The Deployment Manager and Nodeagent    *
*                      may fail to start with IGVDGNPP active. *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
With the IGVDGNPP tool active on a z/OS system the
WebSphere Application server may abend with a ABEND0C4 or
ABENDS0C4 ocurring in BBOOWCA or BBGOWCA.

Problem conclusion

The null pointer references resolving to PSA areas detected by
IGVDGNPP are corrected by checking for a stored null value
in the target fields.

APAR PM02082 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.11 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM02082
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-24
Closed date
2010-01-19
Last modified date
2010-07-02

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM02083 PM02087

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK57722
UP10/06/17 P F006

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PM02082: DEPLOYMENT MANAGER AND NODEAGENT MAY FAIL TO START WITH IGVDGNPP TOOL ACTIVE ON Z/OS. AN 0C4 IS SEEN ON THE WEBSPHERE TCB.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY UK57722

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?