Today’s Friday APAR may seem small but I’ll bet the issue it fixes had caught many a dynamic SQL user……
Prior to applying APAR PM35207, if a dynamic SQL statement contained a non-blank character before the actual SQL text, a non-cached PREPARE was always preformed. Like I said, this may seem trivial… unless you decide to lead off your dynamic SQL statement with a comment.
That’s right, one of the non-blank characters that could cause a non-cached PREPARE is a /* */ combination… an SQL comment.
However, after applying APAR PM35207, the dynamic statement cache will cache an SQL statement that is proceeded by an SQL comment string… /* */
It’s just that simple… and definitely makes this a fix I would put on my list to apply sooner than later.
Unfortunately, this APAR is still marked OPEN… so make sure at least add it to your watch list.