Restricting access of plans or packages to particular systems
If you use controls in an application program, you can limit the access of a plan or package to the particular systems for which the application program is designed.
About this task
Db2 does not ensure that only specific
programs are used with a plan, but program-to-plan control can be
enforced in IMS and CICS®. Db2 provides
a consistency check to avoid accidental mismatches between program
and plan, but the consistency check is not a security check.
You can use the ENABLE and DISABLE options on the BIND and REBIND subcommands to restrict access of plans and packages to a particular system.
Examples
- Example
- The ENABLE IMS option allows the plan or package to run from any IMS connection. Unless other systems are also named, ENABLE IMS does not allow the plan or package to run from any other type of connection.
- Example
- DISABLE BATCH prevents a plan or package from running through a batch job, but it allows the plan or package to run from all other types of connection.
You can exercise even finer control with the ENABLE and DISABLE options. You can enable or disable particular IMS connection names, CICS application IDs, requesting locations, and so forth. 