APAR status
Closed as canceled.
Error description
Warning message msgiew2651i for the amode of db2 modules or message msgIEW2654i for the rmode of the DB2 modules being link edited may be issued when applying ptf or apar maintenance. This message is only a warning unless other linkedit messages such as msgiew2660i are also issued to indicate an error. The msgiew2651i is issued because db2 csects are built using default amode and rmode parms and these defaults are generally the most restrictive values (ie amode 24 / rmode 24). The db2 product relies on jclin files to set the proper amode and rmode for its load modules. The following messages appear with DFSMS V1 R1: MSGIEW2646I ESD RMODE(24) CONFLICTS WITH USER-SPECIFIED RMODE(ANY) FOR SECTION __(mod)__. MSGIEW2651I ESD AMODE 24 CONFLICTS WITH USER-SPECIFIED AMODE 31 FOR ENTRY POINT __(csect)__. Binder APAR OW12778 upgraded the above error messages from informational (ending in i) to warning (ending in w) and generating a RC4. For DB2 modules, msgIEW2651w for amode and msgIEW2646w for rmode with RC4 is okay and the message can be ignored unless other linkedit messages are received. To confirm a module has been replaced and is at the correct AMODE/RMODE, check the reports following the IEWL XREF: SAVE OPERATION SUMMARY Disposition REPLACED SAVE MODULE ATTRIBUTES AMODE should be 31 RMODE should be ANY These reports follow each module's linkedit XREF. See DFSMS APARs OW05347 & OW12778 and SMP/E APAR IR29060 for details on using a new parm: COMPAT(LKED | PM1). Using parm COMPAT(LKED) will cause different messages to be generated which have a RC0 but still flag the statements as having conflicting AMODEs or RMODEs. Coding this new parm has be acceptable to many binder customers and does not adversely affect DB2. Additional Info: msgiew2646i msgiew2651i amode rmode esd msgiew2646w msgiew2651w binder iewl r310 r410 Read apartext of PN50045 plus BINDER info II07297 ii07696 IEW2646W message, and the return code 4 is not part of any of the PTFs being applied APAR OA12355. That APAR indicates that the binder is issuing message, and giving a return code of 4 when COMPAT=LKED is specified but the message is still occurring
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
closed for db2info retention
APAR Information
APAR number
II07039
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1993-06-07
Closed date
1996-12-20
Last modified date
2006-01-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 December 2020