Fixes are available
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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
BBORBLOG may complete with RC=8, and the following errors when the NOFORMAT option is used: BBOO0088E Program BBORBLOG encountered an error writing to file associated with DD:BBOLOG. BBOO0089E Program BBORBLOG terminated due to errors. Browse file output may be truncated. The issue happens when BBORBLOG is invoked with NOFORMAT option and encounters a very long line, that cannot be accomodated by a LRECL of 4096. However, the invocation is successful if it is invoked with option 80 , where a CR/LF is entered after 80 characters.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application Server * V6.1.0 * **************************************************************** * PROBLEM DESCRIPTION: The Log Browse Utility (BBORBLOG) * * failed to format an error log using the * * NOFORMAT option * **************************************************************** * RECOMMENDATION: * **************************************************************** BBORBLOG completed with RC=8 and the following messages when the NOFORMAT option was used: BBOO0088E Program BBORBLOG encountered an error writing to file associated with DD:BBOLOG. BBOO0089E Program BBORBLOG terminated due to errors. Browse file output may be truncated. The NOFORMAT option does not wrap the records written to the output data set. A record was read from the log stream that exceeded the logical record length used for the output data set. The attempt to write the large record to the output data set resulted in the above return code and messages.
Problem conclusion
The BBORBLOG utility was updated to truncate records that exceed the LRECL for the output data set when the format option of NOFORMAT is specified. Also, two additional optional keyword parameters have been added to the Log Browse Utility: "reclen" and "outdsn". The following is the help information from BBORBLOG: BBORBLOG <stream name> <format option> <reclen=nnnn> <outdsn=xxxx> <stream name> - stream name to browse - required parameter <format option> - browse file formatting option - Valid values are 80 and NOFORMAT. The default value is 80. <reclen=nnnn> - record length for output dataset. Optional keyword parameter. Default depends on the "format option" value. <outdsn=xxxx> - non-fully qualified output dataset name. The default is the stream name. The following message will be issued if BBORBLOG detects an incorrect value for the "reclen" parameter: BBOO0366E Input to program BBORBLOG specifies incorrect reclen value. Valid range is from 80 to 32752. Explanation: The user did not specify a proper value for the reclen= parameter to the indicated program. Valid values are from 80 to 32752. Programmer response: Rerun the program specifying an appropriate value. APAR PK91010 requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/library The following changes to the WebSphere Application Server Version 6.1 Information Center will be made available in January 2010. Step 4 within the "Viewing error log contents through the Log Browse Utility (BBORBLOG)" topic will include the following Version 6.1.0.29 statements: [Fix Pack 29 or later] You can use the outdsn parameter to specify a name for the output data set before you save it. For more information on this parameter, see the usage information on the BBORBLOG log browse utility. [Fix Pack 29 or later] If you use the outdsn parameter to specify a unique output data set name the current view of the log stream is not deleted. The "Saving your BBORBLOG browser output" section of the "Error log stream record output" topic will include the following statements for V6.1.0.29: [Fix Pack 29 or later] You can use the outdsn parameter to specify a name for the output data set before you save it. For more information on this parameter, see the usage information on the BBORBLOG log browse utility. [Fix Pack 29 or later] If you use the outdsn parameter to specify a unique output data set name the current view of the log stream is not deleted. The "Using the log browse utility (BBORBLOG)" topic will include the following new parameters for Version 6.1.0.29: [Fix Pack 29 or later] reclen: This optional keyword parameter specifies the formatted record length for the output data set. When you use this parameter, it must follow the log stream name and format option parameters in order. However, if you specify this parameter, the format option is an optional positional parameter. If you specify NOFORMAT for the format option parameter, the default value is 4096. If the format option parameter value is 80, this parameter value defaults to 80. The value range for this parameter is 80 to 32752. [Fix Pack 29 or later] outdsn: This optional keyword parameter is the non-fully qualified data set name for the output data set. When you use this parameter, it must follow the log stream name and format option parameters in order. The default value for this parameter is the name of the log stream. The following information is an additional example for Version 6.1.0.29: [Fix Pack 29 or later] You can also invoke the browser using the following commands: ex 'BBO.SBBOEXEC(BBORBLOG)' 'bbo.bossxxxx NOFORMAT reclen=5200 outdsn=bbos001.stc00123.bborblog' ex 'BBO.SBBOEXEC(BBORBLOG)' 'bbo.bossxxxx NOFORMAT outdsn=bbos001.stc00456.bborblog' ex 'BBO.SBBOEXEC(BBORBLOG)' 'bbo.bossxxxx 80 reclen=200' APAR PK91010 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
PK91010
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-07-09
Closed date
2009-09-22
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:
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.
Document Information
Modified date:
29 December 2021