Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
All development is being done in Ascii by stack products. Install actions are not being developed specifically for z/OS and are not handling the IBM-1024 encoding. Following lines need to be added to the launchConfigManager.sh script: FILE_ENCODING=ISO8859-1 and -Dfile.encoding="$FILE_ENCODING" \ These should appear at the end of the file to look like this: FILE_ENCODING=ISO8859-1 # called without an action registry defined ${JAVA_EXE} \ $JVM_EXTRA_CMD_ARGS \ -DWAS_HOME=${WAS_HOME} \ -Dwas.install.root=${WAS_HOME} \ -Dfile.encoding="$FILE_ENCODING" \ -DWS_CMT_LOG_HOME=${LOG_HOME} \ -DWS_CMT_LOG_NAME=${LOG_NAME} \ -DWS_CMT_LOG_LEVEL=3 \ -DWS_CMT_CONF_DIR=${ACTION_REPOSITORY} \ -classpath ${CONFIG_MANAGER_CLASSPATH} \ -Dws.ext.dirs=${WAS_EXT_DIRS} \ com.ibm.ws.install.configmanager.launcher.Launcher \
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 for z/OS that configure stack * * products. * **************************************************************** * PROBLEM DESCRIPTION: The augmentation customization jobs * * that are generated by the Profile * * Management for z/OS do not support * * ASCII file encodings. * **************************************************************** * RECOMMENDATION: * **************************************************************** The config actions that are run during profile augmentation for some stack products are not designed to run with an EBCDIC file encoding. Significant rework and testing can be required to get these config actions to run on the z/OS platform.
Problem conclusion
The zAugmentProfile.sh script, which is used to invoke profile augmentation on the z/OS platform, was updated such that profile augmentation can be run with either an EBCDIC (IBM-1047) or an ASCII (ISO8859-1) file encoding. Each stack product can then specify the file encoding for profile augmentation, with EBCDIC being the default file encoding. APAR PM57985 is currently targeted for inclusion in Service Level (Fix Pack) 8.0.0.3 of WebSphere Application Server V8.0. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PM58071
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-13
Closed date
2012-03-13
Last modified date
2012-08-09
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
R800 PSY
UP
Document Information
Modified date:
28 October 2021