There are two sets of
permissions involved with the SAS Accelerator Publishing Agent software.
The first set of permissions
is needed by the person who publishes the
SAS_COMPILEUDF and
SAS_DELETEUDF functions and creates the
SASUDF_COMPILER_PATH and
SASUDF_DB2PATH global variables.
These permissions must
be granted before the
%INDB2_PUBLISH_COMPILEUDF and
%INDB2_PUBLISH_DELETEUDF macros are run. Without these permissions, running
these macros fails.
The following table
summarizes the permissions that are needed by the person who publishes
the functions and creates the global variables.
|
|
Authority Required to
Grant Permission
|
|
CREATEIN permission
for the SASLIB schema in which the SAS_COMPILEUDF and SAS_DELETEUDF functions are published and the SASUDF_COMPILER_PATH and SASUDF_DB2PATH global variables are defined
|
System Administrator
or Database Administrator
Note: If you have SYSADM or DBADM
authority or are the DB2 instance owner, then you have these permissions.
Otherwise, contact your database administrator to obtain these permissions.
|
GRANT CREATEIN ON SCHEMA SASLIB
TO compiledeletepublisheruserid |
CREATE_EXTERNAL_ROUTINE permission to the database in which the SAS_COMPILEUDF and SAS_DELETEUDF functions are published
|
GRANT CREATE_EXTERNAL_ROUTINE ON
DATABASE TO
compiledeletepublisheruserid |
The second set of permissions
is needed by the person who publishes the scoring models. The person
who publishes the scoring model functions is not necessarily the same
person who publishes the
SAS_COMPILEUDF and
SAS_DELETEUDF functions and creates the
SASUDF_COMPILER_PATH and
SASUDF_DB2PATH global variables. These permissions are most likely needed by the
scoring model developer. Without these permissions, the publishing
of the scoring model functions fails.
Note: Permissions must be granted
for every scoring model publisher and for each database that the scoring
model publishing uses. Therefore, you might need to grant these permissions
multiple times.
After the DB2 permissions
have been set appropriately, the scoring model publishing macro should
be called to register the scoring models.
The following table
summarizes the permissions that are needed by the person who publishes
the scoring models.
|
|
Authority Required to
Grant Permission
|
|
EXECUTE permission
for functions that have been published.
This enables the person
who publishes the scoring models to execute the SAS_COMPILEUDF and SAS_DELETEUDF functions.
|
System Administrator
or Database Administrator
Note: If you have SYSADM or DBADM
authority, then you have these permissions. Otherwise, contact your
database administrator to obtain these permissions.
|
GRANT EXECUTE ON FUNCTION
SASLIB.* TO
scoringpublisheruserid |
CREATE_EXTERNAL_ROUTINE permission to the database to create scoring model
functions
|
GRANT CREATE_EXTERNAL_ROUTINE ON
DATABASE TO
scoringpublisheruserid |
CREATE_NOT_FENCED_ROUTINE permission to create scoring model functions that
are not fenced
|
GRANT CREATE_NOT_FENCED_ROUTINE
ON DATABASE TO
scoringpublisheruserid |
CREATEIN permission
for the schema in which the scoring functions are published if the
default schema (SASLIB) is not used
|
GRANT CREATEIN ON SCHEMA
scoringschema TO
scoringpublisheruserid |
READ permission to
read the SASUDF_COMPILER_PATH and SASUDF_DB2PATH global
variables
Note: The person who ran the %INDB2_PUBLISH_COMPILEUDF macro
has these READ permissions and does not need to grant them to himself
or herself again.
|
Person who ran the %INDB2_PUBLISH_COMPILEUDF macro
Note: For security reasons, only
the user who created these variables has the permission to grant READ
permission to other users. This is true even for the user with administrator
permissions such as the DB2 instance owner.
|
GRANT READ ON VARIABLE
SASLIB.SASUDF_DB2PATH TO
scoringpublisheruserid
GRANT READ ON VARIABLE
SASLIB.SASUDF_COMPILER_PATH
TO scoringpublisheruserid |