IQL exception doesn't trigger after upgrade to R19

Document ID : KB000072519
Last Modified Date : 02/03/2018
Show Technical Document Details
Issue:
The customer has an IQL exception that no longer works in r19. It is an exception that should trip if an active thread extends beyond 5 minutes without a commit. 
Environment:
CA Sysview for DB2 for z/OS 19.0 plus current maintenance.
DB2 v11
Cause:
The exception does not match the definition, because the ID in the exception ouptut is too short. The output text must start with an eight character ID padded on the right side with blanks if needed.  
Resolution:
Ensure the exception matches the definition.  In this particular scenerio, the ID in the exception output was too short. The output text must start with an eight character ID padded on the right side with blanks (as needed). By specifying in the IQL 'ESTARTW ' instead of 'ESTARTW'  proved corrective.  

 
Additional Information:
The reason it used to work in r18, but not in r19 is that r18 uses a blank to separate fields in the output (ESTARTW<blank>D=...) but r19 uses a different character.