See, once a package is in the skeleton pool it will stay there (assuming that it's not invalidated through, for example, an ALTER of an object on which the package depends) until the DB2 subsystem is stopped (as it might be, on occasion, for application of software maintenance) or until DB2 steals the space in the skeleton pool occupied by the package in order to make room for another package that has to be brought in from SPT01.

the thread persists through the commit that marks the end of a DB2 unit of work.

Some thread types persist through commits, and some do not.

The EDM pool is in the DB2 database services address space (aka DBM1).

The size of the skeleton pool within the EDM pool is determined by the value of the EDM_SKELETON_POOL parameter in the DB2 subsystem's ZPARM module.

This happens everytime i try to click on Edit/Delete on the Gridview.

NET, like how to insert, delete and update record in Grid View control.

I am having trouble Editing, Deleting the records from the Gridview as my application keeps erroring out at the Row Editing event.

Although I am trying to use the "Edit, Delete" function from the Design view of the Gridview. I used the Select tab, Update tab & Delete tab in the sqldatasource configuration.

After the package has been loaded into the skeleton pool, it is copied from there into another part of the DBM1 address space, called a local agent pool, that is associated with the thread through which the native SQL procedure's CALL got to DB2.

That memory-to-memory copy operation is part of the process of allocating the package to the thread.

What can we say about the "stay resident" characteristic of a native SQL procedure's executable (its package)?