Previous Topic: Prepare for Live Data

Next Topic: Implement Security

Starting Your Product › How to Configure Without CA MSM › Required Manual Configuration › Grant Access to Additional Users

Grant Access to Additional Users

This step outlines the tasks necessary to grant additional user IDs access to the JARS/OLF tables.

A. Authorize user ID:

For DB2, the new user must be granted EXECUTE access on the plans that were created when the bind procedure was run. The plan names are CAISSQL2, CAISSQL3, and CAISSQL9. The following SQL statement grants execute access to user ID C0001:

GRANT EXECUTE ON PLAN CAISSQL2, CAISSQL3, CAISSQL9 TO C0001;

For CA Datacom, create a schema for the new user. Member CAKRSCH can be used. Be sure to customize CAKRSCMA; change the user ID to the new user ID.

B. Grant access to a user ID:

To reflect the user ID requiring grant access, customize the CAJRSQL library member CAKRCR87. To conform to your standards for the data center, edit the CAJRJCL library member CAKRGRNT. To make sure that the job completed with a condition code of 0, submit the job and review the output.

Note: When the database security is not turned on, SQL error -559 is returned. This error occurs, when attempting to grant other users access to JARS/OLF tables. You can proceed to the next step when this error occurs.

C. Establish synonyms:

Important! Execute this step by the user ID requiring the synonyms.

Member CAKRSYN establishes synonyms. This member uses input member CAKRCR84 to complete this process. To confirm your data center standards, EDIT CAKRSYN. Verify the owner ID of the tables you are creating synonyms for is reflected in CAKRCR84. The last SQL statement in member CAKRCR84 performs an insert into the options table to set up the default options for the new user. Change the first variable in the VALUES operand to the name of the new user ID. This variable appears in the statement directly after the word VALUES as illustrated in the following example:

INSERT INTO OWNERID.OPTTABS VALUES ('NEWUSER','BOTH','NOREV',...

Replace the OWNERID in this statement with the user ID (OWNER) that was originally used to create the tables. Replace the NEWUSER with the new user ID.