To answer this question, let's go through each option to understand why it is correct or incorrect:
Option A) Avoid having to bind a large number of DBRM members into a plan - This option is incorrect because using a package does not necessarily avoid the need to bind a large number of DBRM (Database Request Module) members into a plan. A package is a container that holds the compiled SQL statements and associated access paths, but it still requires binding.
Option B) Minimize fallback complexities if changes result in an error - This option is incorrect because using a package does not specifically minimize fallback complexities. Fallback complexities are related to the process of reverting to a previous version of the program or application if changes result in an error, and using a package does not directly address this.
Option C) Avoid cost of a large bind - This option is incorrect because using a package does not necessarily avoid the cost of binding. Binding is still required for a package in order to compile the SQL statements and create the access paths.
Option D) Time consumption is reduced - This option is correct because using a package can reduce the time consumption in certain scenarios. When a package is bound, the SQL statements and access paths are already compiled and stored, which can save time during execution as the statements do not need to be recompiled each time they are executed.
The correct answer is D) Time consumption is reduced.