A fix is available
APAR status
Closed as program error.
Error description
Starting and Stopping an application on a z/OS may result in an inconsistent application state between the Servants & Adjunct regions. The application state can only be made consistent after a server restart. . Set Custom Properties "com.ibm.ws390.management.proxy.ApplicationMgrMBeanProxy.zos.pre FilterCheck" to "true". . There are two way in doing so: o At the CELL level o At the AppServer level . At the AppServer Level ====================== # From the AdminConsole. Select the AppServer and under "Server Infreastructure" select "Process Defination" # Then select the "Control" and "Custom Properties " # Then "NEW" and "ADD" com.ibm.ws390.management.proxy.ApplicationMgrMBeanProxy.zos. preFilterCheck with a value of true # Save your change by selecting "Apply" . Application servers > server1 > Process Definition > Control > Custom Properties > com.ibm.ws390.management.proxy.ApplicationMgrMBeanProxy.zos.preF ilterCheck .. At the Cell Level ================= # From the Environment tab select WebSphere Variables # create a new variable IBM_JAVA_OPTIONS and set the value of this variable to -Dcom.ibm.ws390.management.proxy.ApplicationMgrMBeanProxy.zos.pr eFilterCheck=true # Then save you change
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.1 * * * **************************************************************** * PROBLEM DESCRIPTION: The ApplicationMgr did not provide a * * facility for maintaining a consistent * * application stop state between * * regions on z/OS. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** Runtime components can control whether applications should start or stop by installing a DeployedApplicationFilter with the ApplicationMgr. On z/OS, each region has it's own set of runtime components and installed DeployedApplicationFilters. When an application is stopped on all regions, it is possible for some regions to agree to the application stop while others don't. This results in an inconsistent application state across the regions.
Problem conclusion
A flag has been introduced to enable a new behavior that will attempt to maintain a consistent application state among the regions on z/OS. A servant region will first be asked whether the application can stop, before an application stop is issued to all the regions. APAR PM04092 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.29 of WebSphere Application Server V6.1. 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
PM04092
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-22
Closed date
2009-12-24
Last modified date
2010-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BBGUBINF BBOUBINF
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK53194
UP10/01/15 P F001
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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022