The DROP ACCESS MODULE access module management statement deletes an access module and its definition from the dictionary. It is also a CA IDMS extension of the SQL standard.
To issue a DROP ACCESS MODULE statement, you must hold the DROP privilege on or own the access module named in the statement.
►►─── DROP ACCESS MODULE ─────────────────────────────────────────────────────► ►─┬────────────────┬─ access-module-name ────────────────────────────────────► └─ schema-name. ─┘ ►─┬─────────────────────────────┬────────────────────────────────────────────► └─ VERSION am-version-number ─┘ ►─┬────────────┬─────────────────────────────────────────────────────────────►◄ └─ PRESERVE ─┘
Specifies the name of the access module being dropped. Access-module-name must identify an access module defined and stored in the dictionary.
Identifies the schema associated with the specified version of the named access module.
If you do not specify schema-name, it defaults to the current schema associated with your SQL session.
Specifies the version number of the access module being dropped.
If VERSION is not specified, am-version-number defaults to 1.
Directs CA IDMS to retain privileges held on the access module being dropped. If you subsequently create a new access module with the same name as the access module being dropped, the preserved privileges will apply to the new access module.
If you do not specify PRESERVE in a DROP ACCESS MODULE statement, CA IDMS deletes all privileges held on the access module if CA IDMS internal security is in effect.
Dropping an Access Module
The following DROP ACCESS MODULE statement deletes version 1 of the SALES001 access module from the dictionary but retains privileges held on the access module:
drop access module test.sales001 preserve;
|
Copyright © 2014 CA.
All rights reserved.
|
|