Fixes are available
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Executing the AdminTask.extractConfigProperties with -selectSubTypes JavaProcessDef on WebSphere Application Server z/OS results in a configuration property file that contains 3 JVM process (control, servant, and adjunt). Validating the property file with the AdminTask.validateConfigProperties command results in ADMG0811I: Changing value for this property processType. New value specified is Servant. Old value was Control.
Local fix
The issue can be worked around currently by making a manual update to the properties file after it is extracted and adding the processType to the ResourceId in the header infomation for each JavaProcessDef. For example if the following is extracted: ----------------------------------------------------------- # # SubSection 1.0.12.0 # Process definition section # ResourceType=JavaProcessDef ImplementingResourceType=Server ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName }:JavaProcessDef=AttributeInfo=processDefinitions # # #Properties # executableTarget=com.ibm.ws.runtime.WsServer executableName="${JAVA_HOME}/bin/java" stopCommand="STOP BBOS001; CANCEL BBOS001" stopCommandArgs={} terminateCommand=FORCE BBOS001 workingDirectory="${USER_INSTALL_ROOT}" #required startCommandArgs={AMODE=64,JOBNAME=BBOS001,ENV=WAS00.NDN1.BBOS00 1,REUSASID=YES} executableArguments={} startCommand=START N700ACR executableTargetKind=JAVA_CLASS #ENUM(EXECUTABLE_JAR|JAVA_CLASS),default(JAVA_CLASS) terminateCommandArgs={} processType=Control # # SubSection 1.0.12.0.2 # Environment properties # ResourceType=JavaProcessDef ImplementingResourceType=Server ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName }:JavaProcessDef=AttributeInfo=environment(name,value) # # #Properties # was.com.ibm.websphere.zos.jvmmode=64bit ---------------------------------------------------------------- Then each of the 'ResourceId' lines above should have the processType appended. In this case the two lines starting with 'ResourceId' from the above set of properties would be changed to: ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName }:JavaProcessDef=processType#Control
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0, V8.0, and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: The JavaProcessDef subtype was not * * extracted properly on a * * AdminTask.extractConfigProperties(). * **************************************************************** * RECOMMENDATION: * **************************************************************** When multiple regions exist such as the Servant and Adjunct regions, there was no way to specify a particular JavaProcessDef in properties file based configuration.
Problem conclusion
The Server.properties file running properties file based configuration now has uses processType as the key for JavaProcessDef. APAR PM61995 is currently targeted for inclusion in Fix Packs 7.0.0.25, 8.0.0.5, and 8.5.0.1 of WebSphere Application Server. 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
PM61995
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
2012-04-06
Closed date
2012-06-15
Last modified date
2012-11-02
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK81738
UP12/10/04 P F210
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
Modified date:
28 October 2021