An access plan or access package contains information needed by DB/2 to process the SQL statements in a .SAM and access the database as efficiently as possible. The access plan is created and stored in  IBM DB/2 system tables when DB/Assist performs a bind to the database with the .BND file that is generated during the DB/Assist compile process.  Alternatively, once the .BND file has been created by DB/Assist, it is possible to create the Access plan by manually performing a BIND within the DB/2 command line interpreter whilst connected to the required database, or by programmatically using the ESL routine EBD2Bind.

If a database has changed significantly, for example the database has been populated or new indexes have been added, then you should re-create the Access plan by performing the bind operation. The "re-binding" will ensure that DB/2 uses the most efficient method to process the requirements of each SQL statement held within the .BND file. If the requirements of each SQL statement have not changed, nor have SQL statements been added or deleted, there is no requirement to re-compile your ESL Applications to allow for the new Access plan.