Db2 has no shortage of ways to tell you something has gone wrong. For experienced mainframers, codes such as -911, -805 and -818 can be instantly recognizable…and sometimes memorable for all the wrong reasons.
But knowing the number is only part of the challenge. Can you tell a missing package from a mismatched DBRM? A NULL assignment problem from a missing indicator variable? Or a deadlock or timeout that rolls back the unit of work from one that leaves the next move to the application?
Test your knowledge of some of Db2 for z/OS’s more familiar errors, troublesome situations, and SQLCODE oddities!







0 Comments