A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DDF_COMPATIBILITY=IDNTFY_V11_PRIOR_VER ZPARM is not honored in V11 NFM *************************************************************** Additional Symptoms and Keywords: SQLCODE -4743 SQLCODE4743 SQL4743N SRCN4743 DDF_COMPATIBILITY IDNTFY_V11_PRIOR_VER
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 11 Distributed Data Facility (DDF) * * users. * **************************************************************** * PROBLEM DESCRIPTION: A behavior change in the DSN6FAC * * DDF_COMPATIBILITY IDNTFY_V11_PRIOR_VER * * specification is required to help * * users compensate for errors in remote * * client application environments while * * operating in V11 New Function Mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** Users have observed unexpected behavior in remote client application environments where remote client environment related changes are necessary in order to tolerate or correct the situation. In this particular reported case, a remote client application environment detects that DB2 11 has been migrated to V11NFM and will therefore start issuing queries for session special register values, even if they're only available with package(s) bound with an APPLCOMPAT V11R1 value. An SQLCODE -4743 condition may be returned to the client application if the package is actually bound with APPLCOMPAT V10R1. An updated client driver level is required to resolve the condition. Note: Users can also bind the client packages with APPLCOMPAT V11R1 to avoid exposing the client driver error. Users require a DB2 11 for z/OS method to compensate for the condition until the necessary remote client environment changes can be implemented. The IDNTFY_V11_PRIOR_VER keyword of the DSN6FAC DDF_COMPATIBILITY system parameter could potentially provide the necessary compensation but this value has no effect when DB2 11 for z/OS has already been migrated to V11NFM. The value of the IDNTFY_V11_PRIOR_VER keyword would be improved if it can be made to be also effective for NFM environments.
Problem conclusion
To help users bridge the gap until the remote client application environment adjustments can be made, DB2 is being changed to extend the effect of the DSNZPARM DSN6FAC DDF_COMPATIBILITY IDNTFY_V11_PRIOR_VER keyword to NFM environments. DB2 will identify itself and its DRDA functionality, as relative to the prior version that DB2 was migrated from, while operating in any of the V11 migration environment modes: CM, ENFM, CM*, ENFM*, and now NFM. This specification can be changed on-line. This specification allows remote client application environments to believe that they are still operating with the prior version of DB2 where the applications are known to behave correctly. Users should understand that these specifications are only intended to be a temporary measure until the remote client application environment can be modified to tolerate the condition. Once the effect of DSN6FAC DDF_COMPATIBILITY IDNTFY_V11_PRIOR_VER is no longer required, a new or updated ZPARMs module without the IDNTFY_V11_PRIOR_VER setting must be created and brought on-line. ** WARNING WARNING WARNING ** If DB2 11 currently operates in V11NFM and the subsystem parameter module (ZPARM) specifies the DSN6FAC DDF_COMPATBILITY parameter that includes the IDNTFY_V11_PRIOR_VER keyword, you must take action before this APAR change is applied. Prior to this APAR, the IDNTFY_V11_PRIOR_VER keyword is ignored in V11 New Function Mode operating environments. With the APAR applied, the IDNTFY_V11_PRIOR_VER keyword will now be recognized in V11NFM operating environments. Therefore, to maintain current V11NFM behavior, users must remove the IDNTFY_V11_PRIOR_VER keyword before this change is applied. Create a new, or alter the existing, ZPARM module to eliminate the use of the IDNTFY_V11_PRIOR_VER keyword. This new, or changed, ZPARM module can then be activated on-line. Once operating in V11NFM without the IDNTFY_V11_PRIOR_VER keyword, the APAR change can be applied.
Temporary fix
Comments
APAR Information
APAR number
PI84560
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-07-14
Closed date
2017-08-02
Last modified date
2017-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI49277
Modules/Macros
DSNLTEXC DSN6FAC
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI49277
UP17/08/17 P F708
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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2017