1.in the dbrm path will be set along with timestamp for the sql statements.during bind plan an optimal path iss chosen.my ques is for every sql statement will there be a path or for all the sql statements only 1 path will b there.
2.actually in which part does the timestamp mismatch occur.during precompilation stage timestamp is set for sql codes in dbrm and modified source program.does the timestamp mismatch occur while the precompilation stage itself or at some other process like bind or execution stage.
1) For each Sql statement encountered an optimal path is chosen.
2) The timestamp mismatch is observed during the execution stage.The timestamp mismatch occurs due to the following reason.
On Compilation the current Timestamp is associated with the DBRM.Later when the DBRM is bound to a package or plan the current timestamp is also associated with the same.
If any changes are made in the DBRM the recmpilation is done during which the original Timestamp gets replaced with the latest one.If such a source program is directly executed without rebinding to the plan or package, Timestamp mismatch occurs.
One small suggestion. If you are not concerned with environment, you counld quote LEVEL parameter to avoid such TIMESTAMP Mismatch ( -818 ) error during BIND / RUN phase.
It does do the TIMESTAMP, Authorization checks and other relevant checks either during BIND or during RUN phase depending on VALIDATE parameter in your DB2 BIND JCL.
Hope this helps....