Why does the SCM command show a message indicating RBNDRQRD Rebind Required ?

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Cross Enterprise Application Performance Management (APM)
• SYSVIEW Performance Management
• NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

Description

SCM is reporting the following message.

datestamp timestamp RBNDRQRD Rebind Required Pln pppppppp Cn
SERVER P ssssssss Col xxxxxxxx Inv Selects n

When the message is selected, CA Insight Performance Monitor for DB2 is connected. However there is no indication why the message is issued or the exception or where to look for the actual cause.

Solution

The message originates from IFCID 224 which was introduced with DB2 5.0. It tracks the DB2 release with which each plan is bound and issues the RBNDRQRD message if that release is different that the current release. CA Insight Performance Monitor for DB2 is just passing along the info from DB2.

In terms of the application, it does not mean that existing applications will not run. It does mean that they will not take advantage of any improvements in the optimization code on the new release, and thus can't be guaranteed to be performing in the most optimal way. Ideally, the solution is to rebind all the plans when the DB2 release is upgraded.

In many cases, this is not a trivial task. As an interim solution until the plans can be rebound, these exceptions can be stopped, so as to minimize both seeing these messages and having the exception processor absorb so much CPU time in generating them. This can be achieved by commenting out the RBNDRQRD section of the APPLEXCP member in the CA Insight Performance Monitor for DB2 REQUESTS library.

Environment

Release: FAQSO.00200-11.6-SYSVIEW-Performance Management
Component: