A fix is available
APAR status
Closed as program error.
Error description
The following messages are returned when using VSAM striping for active logs in the non-data sharing DB2 subsystem: (It can also occur on a non striped active log.) IEC161I 052(011,DFN2MSTR)-084,IE417FN2,LOGMAS3,SYS00030,,, 995 IEC161I DF2N.DFN2.LOGCOPY1.DS31,DF2N.DFN2.LOGCOPY1.DS31.DATA, IEC161I CATALOG.DF2N.SGQDY5Q The same messages were not issued in a data sharing environment.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All non-data sharing users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: MSGIEC161I RC052 received from a * * third-party vendor product attempting * * to read an active log data set from * * a DB2 subsystem running in non-data * * sharing mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 is running in non-data sharing mode, the active log data sets are allocated with DISP=OLD. This can prevent another product from reading the active log data sets while DB2 is up, even if the VSAM SHROPTIONS are defined to allow multiple readers. In data-sharing mode, DB2 will allocate the active logs with DISP=SHR so that peer members in the data sharing group can access the log data sets while DB2 is up. The vendor has requested that DB2 allocate the logs with DISP=SHR in non-data sharing mode, to be consistent with data sharing mode.
Problem conclusion
Although it is not recommended that an application attempts to read the active log data sets while DB2 is up, DB2 has agreed to allocate the active logs with DISP=SHR in non-data sharing mode to be consistent with data sharing mode. Unpredictable results can occur when reading the current active log data sets. The preferred method is to use the IFI READS facility for IFCID 306 to read log records from the active log data sets when DB2 is active.
Temporary fix
Comments
APAR Information
APAR number
PK64576
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-16
Closed date
2008-06-09
Last modified date
2008-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK37178 UK37179
Modules/Macros
DSNJDS01
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 July 2008