disable_spatial
Use the disable_spatial command to remove all resources that enable IBM® Spatial Support for Db2 for z/OS® to store spatial data and support operations that are performed on this data.
If you did not define any spatial columns or import any spatial data, you can invoke this command to remove all spatial resources from the subsystem. Because of the interdependency between spatial columns and type definitions, you cannot drop the type definitions if columns of those types exist. If you already defined spatial columns and still want to disable the subsystem, you must specify a value other than 0 (zero) for the -force parameter to remove all spatial resources in the subsystem that do not have dependencies on them.
Authorization
The user ID under which the command is invoked must have SYSADM authority.
Command syntax
DSN5SCLP /disable_spatial DALLAS
[-force force]
Parameter descriptions
- -force
- Specifies that you want to disable a subsystem for spatial operations,
even though you might have database objects that are dependent on
the spatial types or spatial functions. This parameter is optional.
If you specify a value other than 0 (zero) for the -force parameter, the subsystem is disabled and all resources for IBM Spatial Support for Db2 for z/OS are removed (if possible). If you specify 0 (zero), or do not specify this parameter, the subsystem is not disabled if any database objects are dependent on spatial types or spatial functions. Database objects that might have dependencies include tables, views, constraints, triggers, generated columns, methods, functions, procedures, and other data types (subtypes or structured types with a spatial attribute).
Example
Example 1
DSN5SCLP /drop_spatial DALLAS +
-force 0
Example 2
DSN5SCLP /drop_spatial DALLAS +
-force 1