1. Likewise, /customerinfo/addr/city as well as /customerinfo/*/city return the city.

2. The new element "POBox" does not appear in the updated document because its parent element "addr" is deleted.

3. Simulates writing size bytes starting at address addr, generates any Purify errors that write would cause, and calls purify_stop_here upon error.

4. A rename example is shown in Update 7, which renames the "addr" element to "address."

5. Simulates reading size bytes starting at address addr, generates any Purify errors that read would cause, and calls purify_stop_here upon error.

6. This requires DB2 to navigate down into the "addr" subtree of the document to look for phone elements at any level of the document. This is avoidable overhead.

7. As another example, consider a single update statement that deletes the "addr" element and also inserts a new element "POBox" into /customerinfo/addr.

8. The info column has the addr element with the following definition. (You can find the complete schema under the sqllib/samples/db2sampl directory).

9. The Exception DSISR/ISISR,srval,virt addr will contain the same information as that shown in the exception structure.

10. Prints specific details about the memory at location addr, including its location (stack, heap, text) and, if it is heap memory, then the call chains of its allocation and free history.

11. In this example, we specify an input parameter named addr of type Address_t.

11. Wish you will love and make progress everyday!

12. The simplest is purify_watch(addr), which sets a read-write watch point on four bytes starting at the given address.

13. Prints the memory state of size bytes starting at memory address (addr), as explained previously in the Application programming interface section.